Iseries

Enterprise class business server and the successor to the AS/400. AS/400 stood for Application System and used single system, including hardware, operating system and database, with common business languages and advanced display technology, to create a system specifically for businesses. iSeries enhances this by giving businesses the ability to integrate and consolidate mutiple operating systems to give businesses choice of applications, as well as reliability, TCO, and ROI. While iSeries still is used to describe both hardware and software, the operating system i5/OS, the successor to OS/400 can now be run on either iSeries, i5 hardware or pSeries, successor to the RS/6000. Both systems run on RISC based POWER5 processor(s). iSeries is still categorized or labelled as a midrange server, due to its original minicomputer origins, but today's iSeries server models range from small one processor systems up to 64 processor mainframe-sized systems.

Five Architecture Principals

  • technology independence
  • object-based design
  • hardware integration
  • software integration
  • single-level store
Fortress Rochester: The Inside Story of the IBM iSeries

System Highlights

  • Extremely reliable 9th Generation 64-bit object oriented operating system with a integrated database
    • 99.98% Average Yearly Up Time
    • 64-bit RISC since 1995
    • iSeries object based system enhances system security
      • Objects can only do what they are designed to do and security not only is effective on the current system, but objects transfered to other iSeries systems retain the same security.
        • In comparison, other systems use file based systems, and a database is a seperate piece of software.
    • DB2 RDBMS integrated with the operating system and optimized at the hardware level.
      • "Automation of many of the common DBA tasks required by other RDBMS's is a cornerstone of DB2 UDB for iSeries lower cost of ownership"
  • Virus resistant
    • OS/400 i5/OS is often thought of as virus proof due to security features and design of the operating system.
      • With the additional capability of running or sharing files with other operating systems, a virus stored on the IFS (Unix like directory system), which most likely wouldn't effect the i5/OS operating system directly, could be shared to other systems. Systems affected by a virus that are using a shared directory(s) from a iSeries, with sufficient privileges, could damage or destroy iSeries files. Hence it is now referred to as virus resistant.
    • Standguard Virus scan capability is now included with the operating system, provided by Bytware, Inc and based on McAffee's virus scan.
    • StandGuard Anti-Virus
  • Single Level Storage
    • All storage(Main memory and disk drives(DASD)) are viewed as a single storage space maintained by the operating system.
    • iSeries has the concept of disk pools or Auxillary Storage Pools(ASP) where groups of disks can be maintained. iSeries has one primary ASP called the System ASP, which for many systems is the only ASP used.
      • Additional ASPs can be created if desired, designated basic and indepenent.
      • Independent Auxillary Storage Pools Clustering Support
  • Jobs are performed in Subsystems
    • Subsystems virtually divide system processing resources to enhance performance and control of all processes. Basic Subsystems are provided and Administrators can add subsystems as required. Subsystems are set up to run jobs automatically, control the number of jobs that can run and have seperate memory resources allocated, all of which can be adjusted as needed.
      • Basic subsystems:
        • QBASE (Controlling Subsystem)(Used with Basic system configuration)
        • QCTL (Controlling Subsystem)(QCTL is more common as it allows for individual configuration)
        • QINTER (Interactive 5250 Jobs)
        • QBATCH (Batch processing)
        • QSPL (Spool or Printing)
        • QCMN, QSERVER (File Server)
        • QSYSWRK (System Work)
        • QUSRWRK (User Work)
      • Other Subsystems
        • QHTTPSVR (Web Server)
        • QSNADS (SNA Subsystem)
      • Memory Pools are used to assign specific Primary Storage resources to specific subsystems
  • As well as the 1 to 64 primary processors, the iSeries' Input/Output devices processing is controlled by IOPs or Input Output Processors, the same as used by mainframes. This allows the primary processors, to not have to waste processing time, supporting slower functions.

Programming Environment

  • The iSeries TIMI enforces the use of a virtual instruction set for all user mode programs - it is not possible for such programs to utilise the instruction set of the underlying CPU - thus ensuring hardware independence, system reliability and security. Therefore the iSeries can be regarded as the precursor (and possibly inspiration) of modern virtual machine based environments such as SmallTalk, Java and .NET. The iSeries's instruction set defines all pointers as 128-bit to allow seamless transition from older to new processor generations.
  • iSeries programs use externally described files, which have the benefit of allowing a single change to a file without requiring changes to the programs, which use the file.
    • Note: By default iSeries uses commitment control, which tracks any changes to a file, so any program which uses that file would need to be recompiled.
  • Programming references names of objects, but all storage is maintained by the operating system. A library list, which is similar to the path statement in Windows, holds administrator defined libraries. To temprarily add additional libraries or schemas, use the command ADDLIBLE. A program referencing an object(file) will then be able to find it.
  • Commands in the Command Language(CL) are promptable and most provide cursor sensitive help to make entering parameters easier. A command consists of a three letter verb and a subject part. This is intended to make it easy to understand CL code. Examples:
    • CRTUSRPRF - Create user profile
    • DLTLIB - Delete library
    • CPYF - Copy file
    • Unlike other systems which use help files or man files, iSeries commands are promptable.
      • Interactive prompting is done by using PF4 key, within programs use ?
  • It was designed as the successor of the IBM System/38 and the IBM System/36. The programmers that worked on OS/400, the operating system of the AS/400, did not have a UNIX background. Dr. Frank Soltis, the head architect, says that this is the main difference between this and any other operating system.
Despite the lack of "UNIX-Y" background, the AS/400 has over the years, picked up the programming/runtime model found on UNIX, Linux, and PC systems. Traditional AS/400 programming is a "one-stop shop", where a programmer writes computer code, compiles the code, and then executes the code. There is no link step that is found in other environments. However, in 1995, that changed. IBM re-christened the one-stop shop programming style "OPM" (for Original Programming Model) and introduced a new language paradigm called "ILE" (for Integrated Language Environment). ILE had significant enhancements over OPM, including the ability to create modules (similar to .obj or .lib files), and then bind (link) the modules together into a single executable. The executable could be created as a program or a service program (service programs are similar to .lib or .dll files). The real power of the ILE environment is in the "integrated" aspect, however. Modules in ILE-compliant languages (RPG, COBOL, C, C++, and CL) could be created and bound together. For the first time, AS/400 programmers could exploit the strengths of each ILE-compliant language and create programs. Also, with the introduction of service programs, standard routines could be externalized more easily, and increase modularity. To ensure proper migration to the ILE environment, OPM RPG and COBOL programs could be migrated to ILE easily.
  • i5/OS is also well regarded for its tuned Java implementation, including specific hardware optimizations
    • Interoperation with the Java language is also supported, though not as tightly as to the ILE languages. The iSeries Java implementation is distinguished by the depth of its embedment in the operating system.
  • Support for Unix style scripting and programs
    • PASE
      • Portable Application Solutions Environment allows you to port AIX applications to the ISeries server with minimal effort
        • AIX programs are binary compatable with i5/OS when using i5/OS's PASE (Portable Applications System Environment). PASE is essentially "an operating system within an operating system", supporting the most recent stable version of AIX. Binaries need to be re-compiled on the AIX system, with 16-bit (quadword) pointer alignment enabled. Once the program is compiled with this option, the executable can be FTP-ed to the ISeries, and executed under the PASE Korn Shell.
        • One use of PASE is to be able to use X(X Window System) the Unix/Linux GUI X on ISeries
    • Qshellis a Unix command environment based on POSIX and X/Open standards

Directories and File Sharing

  • Originally the AS/400 used database, with QDLS to support its office software and folders, which could be used for file sharing. This was changed to the Integrated File System(IFS), which is a much more Unix like directory structure to enhance support for stream file data, programming, file serving and sharing such as used by Unix, Linux and Microsoft files
    • / "root" The primary directory
    • /QSYS.LIB Library file system
      • DB2 Database
        • Libraries(or Schemas), Physical Files(or Tables), Logical Files(or Views), Access Paths(or Indexes), Programs, display files, system files and more
    • /QOpenSys Open systems file system Open system (computing)
      • Compatible with UNIX-based open system standards, such as POSIX and XPG
    • /UDFS User-defined file system
    • Independent ASP QSYS.LIB
    • /QDLS Document library services file system
      • Old folder system
    • /QOPT Optical File System
      • Access to stream data that is stored on optical media.
    • /QNetWare Novell NetWare file system
    • /QNTC iSeries NetClient file system
    • /QFileSvr.400 OS/400 File Server file system
      • Access file systems that reside on remote iSeries servers.
    • /NFS Network File System
  • Command Examples
    • Display the root IFS directory
      • CL(Command Language) WRKLNK /
      • or (using QShell) ls /
    • To Start QShell and copy a file from a Windows server to ISeries home directory
      • STRQSH
      • cp /qntc/awindowserver/myshare$/text.txt /home/johndoe/

Networking Support

  • Support for thin, thick, web based and client server applications
  • Apache HTTP Server webserver with web based GUI administration
    • "The iSeries support for Apache fully integrates the Apache open source commands and functionality with native iSeries security and objects, making it one of the most versatile, stable, and secure Apache servers in the marketplace."

System Consolidation

  • Dynamic LPAR(logical partition) allows iSeries servers to run up to 254 instances of i5/OS, AIX and/or Linux operatings systems at the same time. Partition shares of cpu and disk storage can be adjusted while still active. Other possible benefits include shared system administration, security, virtual networking, and device sharing.
  • Windows/Linux Integration on ISeries
    • Supports Microsoft Windows and Linux on internal/externally attached servers.
      • The lack of LPAR support for Microsoft Windows is due to Windows inability to run on Power based processors
    • Integrated xSeries Server (Up to 60) - Internal single cpu blades IXS
    • Integrated xSeries Adapter (Up to 57) - Externally supports multiple cpu servers running Windows or Linux IXA
      • External servers are configured without disk drives, instead use the iSeries storage
      • External servers are connected to the iSeries using HSL(High Speed Lines) 1GB/sec or newer lines which are 2 GB/sec lines, which are the same type of lines iSeries uses to connect to iSeries expansion towers

iSeries Access

Where Numerous other 5250 products can give you some are all of the above functions, IBM's product comes with the following system management software
    • Single or multiple system administration using text or iSeries Navigator web based or client based(Windows/Linux) GUI software and Wireless Administration.
      • iSeries Console this software is run on the primary or controlling console, which is attached directly to the server and is used for system administration. iSeries Console is used to give an administrator a remote 5250 console as well as a virtual control panel. The Virtual control panel gives the administrator power on/off, system display for IPL (Initial Program Load) status and trouble shooting and the option to set different IPL settings.
      • iSeries Navigator for GUI based Administration
        • Some Functions available:
          • Database Administration and SQL Script Support
          • File Sharing Support
          • Security
          • System Moniters
          • System Services

System Name Change

AS/400 was renamed iSeries in 2000.
  • The reasoning behind this was for two reasons:
    • The introduction of the V5R1(currently V5R3) operating system and 800 line of servers, which introduced significant advances in capabilities, beyond the traditional database and green screen displays of the AS/400.
    • IBM renamed all systems, with the intention that all its server lines would increasingly be able to work together and share capabilities. (iSeries, pSeries, xSeries, zSeries)

A Misunderstood System

The AS/400 has often been a misunderstood or misrepresented system. The original System 38 and AS/400 designs and technologies were based on the Dr. Franks Soltis's Five Principles, which described basic capabilties a modern operating system should include. Mainframe, Unix, VAX and PC Systems have advanced considerably since the late 70's and numerous applications have been written for these platforms, but in many ways still do not match many of the capabilities of the iSeries. The AS/400 and now iSeries has often been presented with the terms like old, slow, expensive, proprietory technology and close to its end of life. The following sections will attempt to show that these terms are not accurate.
  • Old
    • Where today's news talks about x86 CISC computers and operatings systems moving to 64-bit computing and over the next few years 64-bit applications will become available, as the new advance in computer technology, lets remember that 64-bit computing is not a new concept.
      • Where most operating systems require extensive changes, as well as rewriting their applications to use the more advanced hardware, the AS/400 in 1995 went to 64-bit RISC with a single upgrade and when the applications were restored to the new hardware, became 64-bit at the same time.
      • The design which made this possible is still in place, so if 128-bit based systems were created, could make them just as easily available.
      • This is not by chance, but this capability was designed into the original system design, by seperating the i5/OS System Licensed Internal Code (SLIC)(Kernel) and i5/OS System Services, by use of the TIMI(Technologically Independent Machine Interface). This Virtual seperation of the operating system design allows hardware advances to be easily added, by only requiring changes in the SLIC code, but not requiring rewrites or changes to the operating system services or programs.
    • Were modern programming has evolved to use Object-oriented programming in languages such as Java. The design of the System/38 up to iSeries operating system, database, security and the supported programs has always been based on object oriented design.
    • Where virtual computing is becoming more common to describe certain new technologies in the computer industry, the entire OS/400, i5/OS design has been based on virtual concepts. Virtual storage, virtual objects for communications.
      • A user need only reference an objects name and use standard commands to manipulate an object, without having to known specifics of what kind of device, where it is located, what settings does it have.
    • Where some systems are incorporating certain functionality with databases, for the most part the database system is actually a software package running seperately on the system and operating system programs are stored as seperate files. ISeries designs have always been combined with the database, to include system performance, combined security and operating system programs are located within database libraries/schemas. i5/OS could be viewed as a operating system/database and then later incorporated more common directory structures to be compatible with other systems and files.
      • DB2 leads the industry in database capabilities and compliance with standards, if not sales. The iSeries design enhances this by combining it with the operating system.
    • Many of the functions that are manual tasks on other systems are automated on iSeries.
    • ISeries has in depth management and logging capabilities and detail, many of these concepts were inspired by the in depth managment and batch processing capabilities used by mainframes.
    • The ability to run other operating systems is optimized with the host operating system and hardware, it is not just software allowing one OS to run on top of another as with other solutions such as VMware and Xen.
    • Often represented as being a text only system.
      • ISeries does have extensive text based menus and commands, which were considered extremely user friendly when the AS/400 was introduced. Text based displays are still often the method of choice to quickly achieve certain results, as is true with other operating systems.
      • The ease of creating terminal displays, has not been equalled in any other operating system.
      • Often viewed as a RPG only system, which is untrue, but RPG's strength has been it requires much less code to achive the same results as other computing languages, for business type programming.
      • Today's iSeries has incorporated GUI based system management, client software, wizards, web hosting and industry standard support for client based graphical applications and supports running other GUI based operating systems.
  • Slow
    • This idea is based on the original designs as a business focused computer and database server, where the processors used and designs were to enhance business types of processing and not high speed scientific calculations.
    • Also as certain technologies from other operating systems became the industry standard, there was some difficulty incorporating them, but services on the iSeries of today are at the same capability as other systems.
    • Today's ISeries is designed to support the same businesss applications as well as other types of applications and operating systems. It now runs off of Power5 processors, the same as IBM's Unix servers, and in a number of categories, sets industry standards for processing capabilities.
  • Expensive
    • When compared to low-end single function servers the price is much higher, but when you take mutiple applications and systems that most IT departments support and count the cost of all the small servers, databases, networks and support costs involved and compare it to the cost when consolidating on a single iSeries, iSeries has shown superior TCO(Total cost of ownership) in multiple studies, when compared to Windows, Linux and Unix based systems.
      • "the iSeries beat out both Standard Intel Architecture Servers (SIAS) running a variety of server operating systems (i.e., Windows 2000, Novell Netware, UNIX, and Linux) and traditional UNIX servers on several fronts, including reliability and availability"
      • Often Grid computing is referenced as a cheaper solution, but iSeries is capable of particpating in a grid as well.
      • 'Is IBM's iSeries the right choice for your enterprise?'
    • iSeries has even been shown to reduce the costs of maintaining the same applications, when taking them from standalone systems to the same system sharing resources on iSeries.
  • Proprietory Technology
    • iSeries has continually increased its capabilities to support open source operating systems and programming, well as supporting other truly proprietory systems.
    • At the same time still supporting older proven and useful computer languages.
    • iSeries is often viewed as only sold by IBM and uses IBM only equipment. IBM uses many independent vendors to sell the iSeries and add on equipment, as well being numerous vendors who sell equipment which is not created by IBM, which can be run on a iSeries.
    • Part of the benefit of running iSeries, is the hardware and software have been fully tested together, before being sold.
  • Close to its end of life
    • This has often been an arguement used by competitors and others as a reason to use other systems.
    • Though not selling as well as it has in the past, IBM continues to spend money on enhancing this system and encouraging software vendors to make their applications, iSeries compatible.
    • All comments that have been made public recently, indicate there are no plans to discontinue this system now or in the near future and in fact has recently begun a new large campaign to restore interest in this system.

External References

AS/400 References

Pre-AS/400 History

 

<< PreviousWord BrowserNext >>
tribeca
clarkston
sunnyside
hong kong philharmonic orchestra
unionville
class (philosophy)
cayley graph
hairspray (musical)
teknap
sydney symphony orchestra
possessions of sweden
bailiff (channel islands)
nvu
saint barthlemy, landes
closed form
the call of the wild
gibson girl
doug
central lithuania
denise bloch
theos multi user basic
the happiest millionaire
dungeon
lothar bisky
pete's dragon
a woman's right to choose
leon brittan
vicente guerrero
petra pau
westland affair
gesine ltzsch
westland whirlwind (rotary wing)
institute of physics
market drayton
georges prtre
take two interactive
blore heath
rockstar games
barking
audley's cross
makarios iii
mucklestone
fritz reiner
desenrascano
Copyright 2005-2009 OnPedia.com. All Rights Reserved