1 / 126

Introduction to iSeries

Introduction to iSeries. Mandy Shaw Version 0.3, 14 June 2006. Agenda. iSeries in context Architecture The iSeries environment Windows, Linux and AIX integration Security DB2/400 Disk and tape storage, backup and recovery, data storage Programming the iSeries

zed
Download Presentation

Introduction to iSeries

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction to iSeries Mandy Shaw Version 0.3, 14 June 2006

  2. Agenda • iSeries in context • Architecture • The iSeries environment • Windows, Linux and AIX integration • Security • DB2/400 • Disk and tape storage, backup and recovery, data storage • Programming the iSeries • Printing and electronic output • Day-to-day operation, licensed programs, fixes and support, sources of information • Communications

  3. Introduction to iSeries iSeries in context

  4. iSeries: an industry phenomenon • Optimised, integrated business computing for mid-enterprises • Enduring and unique software-based, hardware-independent architecture avoids all costly technology transitions • Easy to manage, secure, highly reliable • Successful in business solutions driven mid market • Far lowest total cost of ownership amongst midrange systems

  5. IBM midrange systems

  6. i570 i595 Open Virtualised Autonomic Integrated i520 i550

  7. Some iSeries applications Green screen (5250) application Domino (iSeries as application server) .Net fat client or Web application (iSeries as database server and/or application server) Sametime (iSeries as application server) Linux, AIX and Windows workloads J2EE applications on Tomcat or WebSphere Feeds from iSeries database to decision support tools such as Excel

  8. Introduction to iSeries Architecture

  9. Architecture: agenda • Hierarchy of microprocessors • Layered architecture • Single level storage • Object orientation • Built in database • Logical partitioning • iSeries workloads: traditional, Windows, Linux on Power, Linux on Intel, AIX stand-alone, AIX within OS/400, Java and WebSphere, Domino • WebFacing • i5 models and editions

  10. Hierarchy of microprocessors Disk IOP Tape IOP LAN IOP CPU(s) Pentium IXS (xSeries IOP) I/O Adapter (IOA) 2-line WAN IOP IOA Control of peripheral devices is not the CPU’s responsibility, being carried out by specialised input/output processors (IOPs).

  11. iSeries - an enduring architectureeliminates technology transition costs MyPgm LDAP Open Interfaces Printing and eOutput Applications Development Systems Management OLTP and OLAP Complete “Operating System” Technology Independent Machine Interface (TIMI) System Licensed Internal Code - SLIC Microcode LPAR TCP/IP DB2 UDB/400 Security Java Virtual I/O Communications Linux AIX iSeries Hardware 64-bit RISC PowerPC

  12. Single level storage Applications access objects by name Operating system accesses pages by virtual address Microcode translates virtual address to physical address Microcode handles all paging

  13. Object orientation Methods applicable to object Everything stored on iSeries is an object. Each object has a fixed object type determining the methods that may be used on it. Examples: • *PGM - program • *FILE - database or device file • *USRPRF - user profile • *JOBQ - batch job queue X Content of object (in this case, program instruction stream) Edit Create Delete Debug Run

  14. iSeries - an enduring architectureeliminates technology transition costs System/38, 1978 MyPgm CISC AS/400, 1988 MyPgm RISC AS/400, 1995 iSeries, 2000 i5, 2004 No need even to recompile, since the program object encapsulates its own TIMI ‘source code’ which can be automatically re-translated by OS/400 as necessary MyPgm

  15. What can your iSeries do? OS/400 OS/400 Linux on PowerPC AIX Windows 2000/3 Linux on Intel Domino DB2 UDB AIX app (PASE) WebSphere Java One box to house, manage and maintain Flexible use of disk, tape, memory, CPU, … Secure and resilient integration Capacity Upgrade on Demand for CPU and memory

  16. Logical partitioning (OS/400, Linux on PowerPC, AIX) OS/400 V5R3 PST OS/400 V5R2 OS/400 V5R3 GMT Linux on PowerPC AIX iSeries layered architecture gives high resilience No additional software costs OS/400 level (n-1 to n+1, but hardware dependent) Time zones Development, production, test DMZ separation Gigabit virtual LAN available Fractions of a processor Dynamic resource allocation Linux and AIX partitions need only CPU and memory

  17. Windows integration (IXS and IXA) iSeries Integrated xSeries Server Intel server within iSeries Processor and memory on card Uses OS/400 disk, tape and LAN resources Has own monitor, mouse and keyboard Windows 2000 or 2003, or RedHat Linux Fully certified by Microsoft for Windows User profile and database integration Gigabit virtual LAN available [Windows only at present] Manage from OS/400 iSeries Integrated xSeries Adapter Separate xSeries box IXA card links it to iSeries via HSL Leverage increasing xSeries power Has own memory, processor, cards Uses xSeries and/or OS/400 tape and LAN Uses OS/400 disk Windows 2000 or 2003, or Suse or RedHat Linux Otherwise same as IXS Windows 2000/3 Linux on Intel iSeries server IXA in supported xSeries server

  18. Linux on IXS/IXA • Linux on PowerPC (i.e. in an iSeries partition) is tried and tested, but vendor support for PowerPC Linux can be a problem. Linux on IXS/IXA gets round this. • Seen by some IBMers as a stepping stone to PowerPC Linux, rather than as a solution in its own right. • PowerPC Linux is more flexible: Intel Linux requires IXS/IXA hardware, and processor and memory allocation are not dynamic. • VMWare ESX is not yet supported. • Linux on IXS/IXA has been available only since the autumn of 2004, with no production deployment in the UK as yet. • Logicalis view: great future, but not ready yet.

  19. Examples: Logicalis DMZ server Win2K Quickplace MySQL External Domino email protected by Norton Anti-Virus with live update PASE PHP Customer apps – WebSphere Apache AS/400 model 170, 1GB memory, V5R2, IXS card

  20. Services organisation: Before Sage Line 50 Access database and corporate application No DNS or DHCP User desktop Hand-held Terminal Message Server and gateway File and print Telephone Email server Fax

  21. Internet facing External Web browser user Access database and corporate application Web server Internet email gateway External email senders and recipients Email server Proxy server External Web sites User Web browser DMZ Internet Internal

  22. After LPAR 1 - Production LPAR 3 – Linux Firewall and Proxy Server LPAR 4 - DMZ Email: Domino Fax: Domino Fax Server SMTP: Domino Corporate app: IXS Additional apps Web server: Apache, potential for WebSphere applications DB2 Sage Line 50: IXS Hand-held terminal gateway: IXS Telephones: IXS DNS DHCP LPAR 2 – Linux Guest File server: Samba

  23. Web serving and Web enablement • Native • Resilient, high performance Java Virtual Machine • WebSphere Application Server • Apache Web server • Apache Tomcat • WebFacing • Portal • PowerPC Linux • WebSphere Application Server • LAMP (Linux, Apache, mySQL, PHP) • AIX • WebSphere Application Server, Apache Web server • Other Unix Web environments • IXS/IXA • WebSphere Application Server, Apache Web server • Microsoft Web environments

  24. Possible configurations MZ Web browser – Intranet user Web browser –Extranet or external user Apache on iSeries DMZ Firewall Tomcat or WebSphere Application Server Apache on iSeries, or Apache on xSeries (Windows or Linux) WebFacing, JDBC or WebSphere MQ INTERNET Firewall Internal databases and RPG-based applications Other external data or transaction sources and targets Internal 5250 application user

  25. WebFacing Use of WebFacing removes normal 5250 application cost implications

  26. i5 models and editions i550 i570 i595 • Enterprise Edition • Allows interactive (5250) workload • BRMS for backup and recovery • Additional IBM software • e.g. 20 users of Portal • Standard Edition • Only WebFaced interactive workload • Base OS/400 software only i520

  27. Introduction to iSeries The iSeries environment

  28. The iSeries environment: agenda • Objects and libraries • Integrated Filing System • Work management • Instructing the iSeries • iSeries Navigator • CL commands

  29. Integrated Filing System • One integrated structure • QSYS.LIB = libraries, objects and members • QDLS = traditional 8.3 folder/document tree • QNTC = Windows Network client – sees contents of your Windows servers • includes file system level view of IXS/IXA • QFILESVR.400 = Remote IFS – sees contents of other iSeries systems • QOPT = your iSeries’ CD drive • QIBM/ProdData and QIBM/UserData used by many IBM products including WebSphere • Qxxx used by other IBM products • Other root folders • use Unix naming conventions, e.g. case-sensitive • Can define shares using NetServer and map them as network drives from Windows

  30. Jobs • All work progresses through the machine as a series of jobs. Jobs can have various sources. The most important types of job are:

  31. Interactive Jobs • An interactive job is one which starts when a user signs onto a display station (i.e. a terminal emulation session). It is ended when the user signs off; if he signs on again, another interactive job is initiated.

  32. Server Jobs • A server job runs continuously on the iSeries waiting for requests from clients (typically PCs). • Examples of server jobs are: FTP server; database server (used by ODBC applications). • Typically, server jobs are listening on TCP/IP ports. • Server jobs vary in the way in which they are started.

  33. Batch Jobs • A batch job carries out processing that requires no input from a client or display station (for example, the generation of a report by an application). • A batch job is normally placed on a job queue via the SBMJOB command, which has many parameters, of which the following are the most important: • CMD - the CL command to be executed • JOB - the job name to be used for the batch job • JOBD - the job description to be used for this job • The job description specifies the job queue on which the job is to be placed, together with a lot of detailed information about the job - the default output queue for its spooled output, for example.

  34. Print Writers (Spool Jobs) • These connect physical printers to output queues, and print spooled output as it arrives.

  35. Job tuning depends on job type. IBM ships sensible defaults for traditional workloads.

  36. Control Language, commands and menus ... DCL &INPUTFILE *CHAR 30 ... MONMSG (CPF0001 CPF0006) EXEC(GOTO VALID) ... CHGVAR &INPFILLIB %SST(&INPUTFILE 11 10) ... OVRDBF FILE(INPUT) TOFILE(&INPFILLIB/&INPFILOBJ) + MBR(&INPFILMBR) ... FTP RMTSYS(&HOST) OVRPRTF FILE(QSYSPRT) SPLFNAME(FTPBATCH) CPYF FROMFILE(&OUTFILLIB/&OUTFILOBJ) + TOFILE(QSYSPRT) FROMMBR(&OUTFILMBR) DLTOVR FILE(*ALL) RETURN /************************************************************/ VALID: RCVMSG MSGTYPE(*DIAG) MSGDTA(&LMSGDTA) MSGID(&LMSGID) + MSGF(&LMSGF) SNDMSGFLIB(&LMSGFLIB) ...

  37. iSeries Navigator

  38. Introduction to iSeries Windows, Linux and AIX integration

  39. c: drive hot swap Network Storage Space NWSSTG3 d: drive Network Storage Space NWSSTG2 c: drive Network Storage Space NWSSTG1 IXS/IXA running Windows 2000/2003 • Network storage spaces allocated from iSeries single level storage • Easy creation and linking from iSeries Navigator • Then manage like normal Windows volumes • Linux and AIX: network storage space for each filesystem • Major performance and availability advantages

  40. RMVLNK OBJLNK('/mysqlbackup/notabilitydb.sql') MONMSG CPFA0A9 /* File not present - ignore */ SBMNWSCMD CMD('net use y: \\cat34\root') SERVER(WWW1) AUTDMN(*LOCAL) SBMNWSCMD CMD('c:\mysql\bin\mysqldump -uroot notabilitydb + >y:\mysqlbackup\notabilitydb.sql') + SERVER(WWW1) AUTDMN(*LOCAL) SBMNWSCMD CMD('net use y: /delete') SERVER(WWW1) AUTDMN(*LOCAL) /* Check success by making sure file now exists */ DSPLNK OBJ('/mysqlbackup/notabilitydb.sql') OUTPUT(*PRINT) SNDDST TYPE(*LMSG) TOUSRID((SHAWM CATALYST)) + DSTD('MySQL dump successfully created') + LONGMSG('MySQL dump successfully + created') SUBJECT('MySQL dump + successfully created') • Virtual LAN • Performance, resilience • N.B. not yet supported for Linux on Intel • User profile/password synchronisation • easy management, resilience • Instruct server from iSeries (e.g. from WRKJOBSCDE) • easy management, resilience

  41. Introduction to iSeries Security

More Related