5722-SS1 IBM Operating System/400 (OS/400 and i5/OS)

IBM United States Sales Manual
Revised:  February 07, 2012.

Table of contents
TOC Link Product Life Cycle Dates TOC Link Description
TOC Link Program Number TOC Link Technical Description
TOC Link Abstract TOC Link Planning Information
TOC Link Product Positioning TOC Link Publications
TOC Link Highlights TOC Link Security, Auditability, and Control

Product Life Cycle Dates
Program NumberVRM Announced Available Marketing Withdrawn Service Discontinued
5722-SS16.01.02008/01/292008/03/21 - -
5722-SS15.04.02007/04/102007/04/20 2011/05/272013/09/30
5722-SSC5.04.02007/04/102007/04/20 - -
5722-SSB5.04.02007/04/102007/04/20 - -
5722-SS15.03.02004/05/042004/06/03 2008/01/042009/04/30
5722-SS15.02.02002/06/042002/08/30 2005/10/012007/04/30
5722-SS15.01.02001/04/232001/05/25 2003/11/212005/09/30

Back to topBack to top
Program Number
  • System i Operating System (5722-SS1)
  • i5/OS Application Server (5722-SSB)
  • i5/OS Licensing by User (5722-SSC)

Back to topBack to top

System i operating system continues to evolve to meet the customer's demands. There is now a lower priced entry into the market with i5/OS Licensing by User and offering the higher end an option to license i5/os partitions without the need to use the i5/OS database called i5/OS Application Server.

i5/OS Licensing by User (5722-SSC)

i5/OS Licensing by User delivers a more flexible approach to licensing help to meet the changing needs of innovative companies. Small-to-medium business clients can now tap into the full performance of POWER5 technology, enabling the deployment of additional solutions, while benefiting from the legendary capabilities of the System i platform. i5/OS Licensing by User enables you to better align the cost of i5/OS with the value it delivers by purchasing the software for the number of users on your system. i5/OS Licensing by User is offered for the new models 515 and 525.

With the new flexibility and performance capabilities that i5/OS Licensing by User unlocks for models 515 and 525, you can deploy new solutions simply, without the need for additional servers and the complexity associated with an Intel-based environment. The simplified offering structure, with a reduced number of configurations and options, speeds the selection, configuration, and ordering of these models.

i5/OS Application Server (5722-SSB)

A new i5/OS license for additional processors on System i models 550, 570, and 595 offers a reduced i5/OS entitlement charge for System i processors. The processors are assigned to logical partitions (LPARs). These LPARs host applications that access DB2 data residing and managed in other partitions as well as applications that do not execute DB2 function in i5/OS within the partition at all.

Using the new i5/OS Application Server processor entitlement offering, you can now leverage the benefits of i5/OS work management, security, and scalability in new applications even more affordably. Additionally, you can manage these applications with the same resources and skills that support their other i5/OS business applications.

The i5/OS Application Server license entitlement can support partitions that run products such as Lotus Domino and Sametime, which do not require DB2 UDB to execute. License entitlement is also ideal for Web application serving workloads such as Java language business applications running under WebSphere Application Server or even PHP or Apache-based applications running on i5/OS. These applications typically access DB2 data only in other i5/OS partitions or servers.

V5R4 continues its history of a complete integrated business system.

The new release of i5/OS(R), the integrated and reliable operating system for the IBM System i5 offerings, delivers many enhancements to a broad user community with significant improvements in the following areas:

  • Integrated middleware
  • Simplified IT infrastructure
  • Security and compliance
  • Business resiliency

i5/OS operating system is designed, built, and tested as an integrated offering, which enables you to manage your business rather than your servers. The integrated nature of i5/OS operating system helps simplify the deployment, management, and serviceability of hardware and software solutions running on the system. Key technologies integrated within i5/OS operating system include:

  • DB2 relational database
  • Robust security and compliance capabilities
  • Advanced networking technology
  • WebSphere application server
  • Straightforward system management of functions and interfaces

Combined with System i5 hardware, the resulting integrated hardware and software offering simplifies application deployment and helps reduce your business operational costs. This offering delivers solutions that are simpler and more cost effective to deploy in businesses of all sizes, especially small and mid-sized businesses.

i5/OS operating system also includes mainframe-class work management and virtualization capabilities designed for the requirements of large enterprises. The robust and consistent base for ISV innovation and unparalleled binary compatibility leverage the long-term investments of both the business customer and application solution providers.

V5R4 runs on the following:

  • iSeries models 270, 800, 810, 820, 825, 830, 840, 870, 890, SB2, and SB3

  • eServer i5 models 520, 550, 570, and 595

  • System i5 models 520, 550, 570, and 595

  • IBM eServer p5 model 9117-570 or 9119-590 servers configured with 1.65 GHz POWER5 processor or the p5 model 9119-595 server configured with 1.65GHz or 1.9GHz POWER5 processors.

V5R4 can be upgraded from V5R2 and V5R3.

Next Generation of Operating System

IBM i5/OS(TM) V5R3, is the next generation of OS/400.

You are familiar with OS/400. i5/OS is a different name for the same operating system. It is a premier integrated operating system that builds upon and extends the capabilities of OS/400. It runs on IBM eServer iSeries servers and IBM AS/400 models 720, 730, 740, 170, SB2, SB3, 250, 270, 800, 810, 825, 870, 890 and IBM eServer i5 models 520 and 570.

To enjoy the advantages, you can upgrade to i5/OS V5R3 from OS/400 V5R2 and V5R1.

With the release of Operating System/400 (OS/400) V5R3, the iSeries delivers self-managing, mainframe-class technology -- simplicity to an otherwise complex world.
Back to topBack to top

Product Positioning

Back to topBack to top

  • Licensing by User offered on models 9407-515 and 9406-525

  • Application Servers oferrs a i5/OS partition license at a reduced price

  • Single Integrated Operating System for All Models

  • Linux Support

  • Investment Protection

  • Enterprise Identity Mapping (EIM)

  • Network Computing

  • OS/400 Portable Application Solutions Environment (OS/400 PASE)

  • Logical Partitions (LPAR)

  • Client/Server Support

  • Integrated DB2 Universal Database (UDB) for iSeries

  • Transaction Processing

  • Batch Processing

  • Ease of Installation, Use, and Maintenance

  • Extensive Run-time Application Function

  • Productive Application Development Environment

  • Integrated Language Environment (ILE)

  • Enabling Technologies

  • Openness

  • Optical Support

  • High System Availability

  • Systems Management

  • Electronic Customer Support

  • Comprehensive Security for System Resources

  • Interfaces to System Functions

  • Enhanced Printed Output

  • Multiple Operating Environments

  • Connectivity to Remote Devices, Systems and Networks

  • National Language Versions and Multilingual Support

The IBM Operating System/400 licensed program provides system support for all models of IBM iSeries and AS/400 RISC systems. The single Operating System spanning all models of hardware represents a significant protection of customer investment in skills and applications. OS/400 benefits are:

  • Supports the highest number of commercial host and client/server business applications (including 64-bit) available in the industry.

  • Provides ease of implementation, management and operation in one totally integrated operating system.

  • Optimizes commercial and client/server environments with excellent performance across the system models.

  • Enables low total cost of ownership through its many integrated functions and ease-of-use.

  • Customers can consolidate their systems. Consolidation provides the potential to reduce the costs associated with installing, operating, and maintaining numerous different computer systems while preserving the customer's investment in applications, operations, and end-user knowledge.

Back to topBack to top

Single Integrated Operating System for All Models:

All functions of the OS/400 follow a consistent design philosophy; this consistency is one of the cornerstones of iSeries and AS/400 ease- of-use. The ease-of-use translates into higher productivity for its users and easier systems management. The Operating System/400 licensed program includes everything described in this document. Some important characteristics are:

  • Object-Oriented Architecture

    All system and user resources are stored on the system as "objects," having a consistent architecture. Every object includes a description containing such information as the name of the creator and current owner, date created, object size (in bytes), date of last save, date of last reference, volume identifier of the media on which the save occurred, and text describing the object.

  • Library Support

    A library is a directory to objects (for example, programs and files), allowing a convenient grouping of the objects for either application or control purposes. Options exist to display, delete, or change objects in a library or to move or copy an object from one library to another. This function makes systems management of authorization to objects easier. The normal method of processing is to use a list of libraries to control how the system accesses objects. A library can also be secured to prevent unauthorized users from accessing any objects.

  • Single-Level Storage

    Object placement on different disk units is controlled by the system. The auxiliary storage disk units contribute to an overall pool of storage called single-level storage. It is not necessary to be concerned with the size of individual objects or where they are placed; the libraries are used to locate any object. The architecture provides additional disk allocations automatically as an object (for example, a physical or logical file) grows in size. You need to monitor only the overall use of auxiliary storage. This contributes significantly to the ease of operating the iSeries or AS/400 system. Auxiliary storage capacity can be added as needed without changing current application programs.

  • Message Handling

    Messages are displayed for various system and user operations. Message handling functions allow feedback for successful operations or to identify error conditions. Messages can be defined and sent between users, between users and applications, or between applications. Message replies can be sent; a "break" option allows immediate interruption of the end user's activities.

  • Job Accounting

    The system supports multiple levels of job accounting and captures job-related information through the assignment of account codes to users. The accounting information on defined units of work is recorded in a journal receiver and may be accessed and processed by user-written programs.

  • Device Support

    The operating system supports use of:

    • Virtual optical device support

    • Tape and optical devices for data interchange and save/restore functions. A high level language (HLL) program or the copy command can read or write directly to a specific device.

    • A optical device for software and PTF distribution

    • Virtual tape device support is added in V5R4

    • A range of work station printers for data processing or text quality output. Graphics (bar codes and images) may be printed with these devices.

    • A range of work station displays, attached locally or remotely. Some devices support graphical data display.

  • Display Data Management

    Interactive applications are supported by a screen definition language that provides greater flexibility in designing the "look and feel" of interactive interfaces. In addition, many attributes of the screen can be controlled outside application programs to simplify the development effort and improve programmer productivity (for tasks like validation of keyed input and punctuation of numeric output). Cursor-sensitive help information may be designed into user applications, including use of hypertext and index search function that allows easy access to descriptions of system functions.

  • Data Areas

    The operating system supports local and global data area objects that allow storage of up to 2,000 bytes of information. Global data areas can be accessed and updated by various programs within a single job or across jobs. A local data area can also be used to pass information between programs operating within a job or to programs the job has submitted to batch. Data areas are also directly supported by some HLLs.

  • Data Queues

    The operating system supports a call interface to send and receive information from a data queue object. This is designed to handle job-to-job communication with a high volume of requests.

  • Work Management

    The work management function eases the job of systems management by giving the operator control of the activities of a job and of its performance characteristics. Work management supports concurrent execution of batch jobs, interactive jobs, and non-conversational transactions on the system. Each job is protected from other jobs on the system; however, job-to- job communication is allowed.

    Different levels of interfaces to work management allow users to operate with the system defaults or tailor specific functions. Automatic tailoring of the execution environment to the CPU model, size of main storage, and configured devices can be done using an option. This automatically-established execution environment should provide good performance for many installations, although better performance may be achieved in some installations by explicitly changing some of the execution environment attributes.

    In addition, there is an option to allow the system to dynamically adjust the execution priority of jobs that are forced to wait for an opportunity to use the CPU. This is designed to prevent high priority jobs from monopolizing the CPU at the expense of all other jobs in the system.

  • Save/Restore

    Save is the capability of making a backup copy of objects or members on tape, optical, or online save file. Restore is the capability to copy saved objects back to the original or a different system. Objects saved on V5R3 systems can be restored on V5R1, V5R2, and V5R3 systems. The OS/400 save/restore functions are designed to ease the job of systems management.

    Saves can be done by library, object, changed object, or for all auxiliary storage, without regard to library or object contents. The system is available when saving documents and folders during normal operations; however, documents being updated during the save process are not saved.

    "Save while active" enables objects to be saved while they are being used by applications. The system ensures the entire object saved to the save media is consistent with the status of the object when the save operation was initiated. However, it is the user's responsibility to establish an application synchronization point either by temporarily quiescing the application for the time required to initiate the save operation or using journal/commit for all processes which impact any objects related to the save operation.

    Copying to a save file allows an unattended, off-shift save with a subsequent copy to media when the system operator is available.

  • Remote or Timed IPL

    Key to convenient system management is the capability to power on the system manually or automatically, at a specific time of day, and from a remote location. Power down of the system can be done by a command executed interactively or under program control.

  • Multiple Concurrent Tasks at the Same Work Station

    Up to 16 different functions can be active as a result of a single sign-on to a work station. To switch from one function to another requires pressing an "interrupt" key and then selecting a new function from a menu. This can significantly increase the productivity of users who perform a variety of tasks of short duration (for example, interrupting an order entry application to switch to an unrelated inquiry application to answer a telephone request). It is also possible to sign on to the same workstation a second time and have two different sessions active, with up to 16 active functions in the second session.

  • Performance Information

    A user can manually collect system performance data for a single time period or automatically collect data on a weekly schedule using a set of commands/menus. This systems management function provides data to assist the user in workload scheduling, system tuning, performance reporting, performance- problem analysis, and capacity planning. The user can also work with this data using the Performance Tools for iSeries licensed program.

    In addition, Performance Management iSeries (PM iSeries), can be used to help plan for and manage the growth and performance of the system. It gathers performance measurement information and produces trend reports to help the customer decide when a hardware upgrade is warranted. Additional analysis of PM iSeries data is provided by IBM for a fee.

    For example, the data provided by PM iSeries can provide the information necessary to tune the system, schedule jobs, manage the overnight workload, and by using the trending data the customer can determine when a resource constraint will occur. The customer can then manage the system so as to provide consistent service levels to their end users.

  • Copy Facility

    The copy facility copies data from one file to another. The files may be input from the database, or tape and be output to the database, tape or printer. Various options control format and record selection.

  • OS/400 Query Support

    Applications may use OS/400 functions to display a list of queries for selection to execute or delete and to display a list of files available to query.

    Some query capability is provided directly by OS/400. It includes processing database files, default output formatting, and windowing left and right for results that exceed the width of the screen. Extensive query capability is available with Query for iSeries (5722-QU1) licensed program and DB2 Query Manager and SQL Development Kit for iSeries (5722-ST1) licensed program.

i5/OS Licensing by User

IBM adds the flexibility of i5/OS Licensing by User on System i models 515 and 525. This new licensing approach aligns software value with an associated price (separate from hardware), enabling you to license the i5/OS software specifically for the number of users deriving value from the i5/OS operating system. This new flexibility broadens the appeal of the i5/OS operating system as the preferred operating system for a diverse portfolio of applications to satisfy your business solution needs.

For the models 515 and 525, i5/OS licensing is now available as processor entitlements and user entitlements:

  • Each i5/OS processor must have one i5/OS processor entitlement.
  • Each i5/OS user must have one i5/OS user entitlement.

Refer to the following table for i5/OS user entitlement offerings by model:

|                          | Model 515       |  Model 525     |
|                          |Maximum Users    |Maximum User    |
|                          | is 40           |is unlimited    |
---------------------------|-----------------|--------------- |
|i5/OS User Entitlements   |                 |                |
|(block of users)          |Five i5/OS Users |Ten i5/OS Users |
|i5/OS User Entitlements   |                 |                |
|(unlimited users)         |        N/A      |Unlimited i5/OS |
|                          |                 |  Users         |
|i5/OS External            | Unlimited       | Unlimited      |
|Access Entitlements       | External        | External       |
|                          | Users           |  Users         |

i5/OS processor entitlements

You must obtain one i5/OS processor entitlement for each processor used for the i5/OS operating system by purchasing a feature to authorize a processor (through a software key).

The requirement for an i5/OS processor entitlement is consistent with previous entitlement requirements. i5/OS processor entitlements may be included in a hardware and software package or can be purchased as needed. With the introduction of i5/OS Licensing by User, the price of i5/OS processor entitlements is significantly reduced. This new entitlement structure enables you to purchase the appropriate number of users and align the total price with the value delivered.

i5/OS user entitlements -- New offerings

An i5/OS user is a person who accesses the i5/OS operating system via one or more connections, exchanging credentials (form of user identification) directly with i5/OS operating system or indirectly through application or middleware software supported by the i5/OS operating system.

You can choose from three new offerings for i5/OS user entitlements:

  • i5/OS user entitlements (block of users)

  • i5/OS user entitlements (unlimited users)

  • i5/OS external access entitlements

i5/OS user entitlement

To authorize access to i5/OS operating system, for users who are employees or similar personnel of your enterprise or individuals to whom you provide hosted services, obtain one i5/OS user entitlement for each user. You have two options for obtaining i5/OS user entitlements:

  • Block of users:

    Purchase an i5/OS user entitlement for each user. User entitlements are purchased in blocks to entitle a specific number of users to use the i5/OS operating system.

  • Unlimited users:

    Purchase an i5/OS User Entitlement for unlimited users. An unlimited i5/OS user entitlement can be purchased to authorize an unlimited number of users to use i5/OS operating system on a machine. This feature is available only for the model 525.

External users

To authorize access to i5/OS for users external to your enterprise, such as customers or business partners who are not employees or similar personnel of your enterprise or Individuals to whom you provide hosted services, obtain one i5/OS user entitlement for each user.

You have two options for obtaining i5/OS user entitlements:

  • Block of users:

    Purchase an i5/OS user entitlement for each user. User entitlements are purchased in blocks to entitle a specific number of users to use the i5/OS operating system.

  • External access entitlements:

    Purchase an i5/OS external access entitlement to entitle an unlimited number of users, external to your enterprise, to use the i5/OS operating system on a machine.

New License Management for i5/OS

License Management for i5/OS requires three Software License Keys for model 515 and 525:

  • i5/OS version
  • Quantity of i5/OS processor entitlements
  • Quantity of i5/OS user entitlements

Software License Keys for the i5/OS version and i5/OS processor entitlements are unchanged.

What's new

You will receive a Software License Key from IBM that contains the quantity of i5/OS users entitled on your model 515 or 525. Software License Manager/400 (SLM/400) assists license compliance by counting the number of activated processors and enabled user profiles. These quantities are then compared to the quantities of i5/OS entitlements, entitled via the Software License Key.

IBM may audit your compliance with these terms upon reasonable advance notice to you.

New Software Maintenance (SWMA) for i5/OS and Select Programs

Software Maintenance for i5/OS and Select Programs is sold on a per processor basis. You are encouraged to purchase SWMA for each i5/OS processor entitlement:

  • A quantity of 1 x three-month SWMA or 1 x one-year for the i5/OS operating system is included at no additional charge with model 515

  • A quantity of 1 x one-year of SWMA for the i5/OS operating system is included at no additional charge with model 525

When you acquire a model 515 with a three-month SWMA, you have the option to purchase an extension to your three-month SWMA to either one or three years of coverage:

  • One-year extension (5733-SPM)
  • Three-year extension (5733-SPO)

If you choose not to extend your three-month SWMA coverage at the time that you acquire your model 515, you may renew for one or three years at the end of the initial three months. If you choose not to renew at this time, you will be charged for Maintenance After License (5733-MAL) at your next purchase of SWMA on the System i platform.

Investment Protection:

OS/400 continues to utilize emerging technologies such as open distributed computing, object-oriented programming, client/server support, multimedia support, and sophisticated application development tools. iSeries Advanced Application Architecture provides the support necessary for observable programs developed on prior versions to be automatically translated the first time they are used on the current version/release. This helps to protect the customer's investment, and their applications can continue to evolve on the iSeries. Selected objects created on the current release can be used on prior releases.

The state-of-the-art code optimization provided by ILE C is important in taking advantage of the performance offered by the 64-bit PowerPC processor. ILE offers many advantages over previous program models, such as binding, modularity, common run-time services, and state-of-the-art code optimization.

Adaptive e-transaction Services

With V5R3, we are specifically optimizing the operating system to adapt seamlessly to and process different transaction types, both traditional and e-business -- simple, predictable transactions or multidimensional transactions spawn multiple tasks.

This self-optimizing capability of OS/400 to manage transactions of all types gives you potential performance gains for your Web serving or day-to-day business applications. Furthermore, the iSeries is optimized for highly scalable WebSphere and Java transaction performance with no programming changes required.

Enterprise Identity Mapping (EIM)

Self-management capability is enhanced with EIM. EIM gives you and your business partners a technology that maps a user identity on one system to the user's identity on another system. The operating system and applications can equate jsmith on iSeries to janesmith on zSeries.

Identity mapping information is available to customers and ISVs through APIs available on all IBM eServer platforms.

EIM, along with Network Authentication Service (NAS) provides the building blocks for single signon support for iSeries. EIM provides the userid mapping capabilities necessary to support a true single signon solution available on the iSeries system.

Java/XML Enhancements

Versions of the core Java runtime environment and WebSphere Application Server are now available, as well as J2EE (Java 2 Enterprise Edition) compliance.

J2EE represents an emerging suite of standard requirements placed on Java application servers like WebSphere. The Java Virtual Machine (JVM) supports the emerging Java Debug, Performance Profiling, and Wire protocols that enable third-party tools to work with the iSeries JVM, along with iSeries specific instrumentation for memory leak detection and enhanced debug. With this release, the suite of XML enablers can stay in step with the latest XML standards. The support for XML schemas is a key XML enabler extensions provided in this release.

In V5R2, the iSeries supports the industry-standard JavaMail program interface used by applications to access or send e-mail using POP, IMAP, or SMTP protocols.

IBM Toolbox for Java

IBM Toolbox for Java is available with V5R2.

Enhancements include:

  • A set of classes for accessing data from a wireless device.
  • An updated JDBC driver that supports JDBC 3.0
  • The ability to use a Kerberos ticket when authenticating to the server.
  • A system debugger to graphically debug C, C++, Java, and RPG programs on the iSeries.

Network Computing:

The network computing capabilities of the iSeries or AS/400 system allow electronic business to be carried out over the Internet and intranets. The following functions of the OS/400 operating system, in concert with the security and reliability of the iSeries and AS/400 system help make it a market leader in network computing.

  • Support for Lotus Domino for iSeries (powered by Apache)
  • Support for Lotus Enterprise Integrator for iSeries
  • Java for iSeries
  • HTTP Server for iSeries
  • WebSphere for iSeries
  • Network Security
  • Net.Data
  • Directory Server on the iSeries or AS/400
  • Virtual Private Networks

Continuous Availability

V5R2 delivers on the promise and potential of switched disk clustering and Independent Auxiliary Storage Pool (IASP) technology introduced in V5R1. V5R2 extends the IASP support to applications that use the traditional library-based file system and database files.

IASPs enable the segmentation of physical and logical storage into isolated and independent subsets within OS/400 single-level storage. IASPs can be brought online and offline independently on a single system and switched between multiple systems in an iSeries cluster.

The iSeries clustering and IASP capabilities are similar to the High-Availability Cluster Multiprocessing (HACMP) functions on the IBM eServer pSeries.

IASPs provide a data center solution for switching storage that can reduce downtime for operating system and hardware maintenance and unplanned outages, and can also be used for database segmentation and workload switching.

To define switchable independent ASPs, you must have high- availability (HA) switchable resources (OS/400 Option 41) installed on your system.

Enhancements to Cluster Resource Services and APIs help expand the number of Cluster Proven applications, particularly Web serving and legacy/batch applications, and make clustering easier for customers.

Disk Migrate While Active with OS/400 V5R2 further enhances availability by supporting concurrent migration of most of the disk subsystem data during normal operations. This capability is available through the Start ASP Balancing (STRASPBAL) command with options to mark and move data off disk subsystems.

Journal performance can be substantially improved in some environments by installing and enabling the HA Journal Performance (OS/400 option 42) feature. Two options enhance journal performance:

  1. Journal Caching can help to substantially reduce the number of synchronous disk write operations performed in batch applications and reduces overall elapsed batch execution time.

  2. Journal Standby allows you to achieve fast failover in a high availability environment and enable journal support on your target iSeries machine well in advance of the failover event without incurring the normal performance impact associated with journaling. This should be especially attractive in shops that need 24x7 operation, have lots of journaled tables, and need more rapid failover/role-swap times.

iSeries Linux Integration - V5R3

Support for larger virtual disk drives and graphical server management is provided.

The virtual disk drive support is enhanced to increase the maximum size of a single virtual disk drive from 64 GB to 1000 GB. The maximum total amount of disk capacity that can be allocated to a Linux server has increased from 4 TB to 64 TB.

The Windows Administration function in iSeries Navigator can now be used to start and shut down Linux servers. The Windows Administration function can also be used to create, delete, link, and unlink virtual disk drives for Linux servers.

For the latest information on iSeries Linux support, refer to:



One of the most important developments in business computing in recent years is the arrival of Linux. iSeries V5R2 enhances Linux support with:

  • Dynamic allocation of virtual processor units
  • Shared read-only virtual disk
  • Linux library support for 64-bit Linux applications
  • iSeries Navigator enhancements for Linux
  • ODBC connectivity to DB2 UDB for iSeries
  • iSeries Support for Windows Network Neighborhood (iSeries NetServer) to allow Linux SAMBA to access the Integrated File System
  • Output queues on the iSeries.

In addition, Linux distributions for iSeries include native I/O support for fiber channel and multiport serial device drivers.

iSeries Linux now supports IBM Java 1.3.1.

Logical Partitions (LPAR)

LPAR allows for the simultaneous running of multiple independent systems -- each with processor, memory, and disk resources -- within an iSeries. This capability was first introduced in V4R4, updated in V4R5, and is enhanced with V5R1 and V5R2.

LPAR enhancements for selected iSeries Models 8xx and 270 and AS/400 Models 7xx, 6xx, and Sx0 include:

  • Dynamic movement of processor, memory, and interactive performance between partitions running OS/400 V5R1

  • iSeries Navigator support to create and manage partitions including scheduled movement of resources

  • Innovative Virtual LAN support to establish multiple, high-speed TCP/IP communication connections between partitions without additional communication hardware

LPAR enhancements for selected iSeries Models 8xx and 270 include:

  • Support for Linux running in a secondary partition.

  • Granularity of processor movement reduced to 1% of each processor.

  • Support for up to four partitions per processor up to a maximum of 32 partitions on iSeries Model 8xx. The primary partition must be OS/400 V5R1. The secondary partitions may be a combination of OS/400 V5R1 and Linux.

  • Extension of partition support to the iSeries Model 820 uniprocessors hardware feature numbers: 2435, 2436, and 2456, and Model 270 feature numbers: 2431, 2432, 2434, 2452 and 2454.

  • Support for up to four partitions on Model 270 hardware feature numbers: 2431, 2432, and 2452, up to two of which can be OS/400 V5R1 partitions and up to three can be Linux partitions. Support for up to eight partitions on Model 270 hardware feature numbers: 2434 and 2454, up to two of which can be OS/400 and up to seven can be Linux partitions.

  • The minimum partition processor requirement is reduced to 10% of a processor including the primary partition.

Linux Logical Partitioning

Logical Partitioning supports additional Linux partitions on iSeries servers with one to four processors. With an OS/400 V5R2 primary partition, the maximum number of Linux partitions per processor is increased. The number of OS/400 partitions per processor remains at four. The maximum number of partitions on iSeries servers with four or more processors remains at 32.

With this enhancement, iSeries servers can support the consolidation of additional workloads and leverage the dynamic processor movement and virtual managed storage support to further reduce management costs.

|            |    Maximum    |    Maximum    |     Maximum    |
|  iSeries   |     Total     |    OS/400     |      Linux     |
| Processors |  Partitions   |  Partitions   |    Partitions  |
|     1      |      10       |       4       |        9       |
|     2      |      20       |       8       |       19       |
|     4      |      32       |      16       |       31       |
|   >=8      |      32       |      32       |       31       |

The increased number of partitions per processor is available on the following servers:

  • Model 270 with the following processors:
    • 2431
    • 2432
    • 2434
    • 2452
    • 2454

  • Model 820 with the following processors:
    • 2435
    • 2436
    • 2437
    • 2438
    • 0150
    • 0151
    • 0152
    • 2456
    • 2457
    • 2458

  • Model 840 with the following processors:
    • 0158
    • 0159
    • 2461
    • 2352
    • 2353
    • 2354

  • Model 890 with the following processors:
    • 0197
    • 0198
    • 2487
    • 2488

These LPAR functional enhancements require an OS/400 V5R1 primary partition.

Multiple OS/400 versions (V4R4, V4R5, and V5R1) are supported within a partitioned environment depending on the iSeries or AS/400 model and processor feature.

Logical partitions let you run multiple independent OS/400 instances or partitions (each with its own processors, memory, and disks) in an n-way symmetric multiprocessing AS/400e 6xx, Sxx, or 7xx model. You can now address multiple system requirements in a single machine to achieve server consolidation, business unit consolidation, mixed production/test environments, and integrated clusters.

Each partition's system values can be set independently. Partitions have different system names and may have a different primary/secondary national language, or be operated using different time zones. This flexibility is ideal for banks and other multinational companies that want to centralize operations in a single location yet retain the national characteristics of each system. Logical partitions are also ideal for companies that want to run mixed interactive and server workloads in a single AS/400. Logical partitions allow the interactive performance of an AS/400 to be flexibly allocated between partitions.

All V4R4 systems have a primary partition with all resources initially allocated to it. Creating and managing secondary partitions is performed from the primary partition. Processors, memory, and interactive performance between partitions can be moved with only an IPL of the affected partitions. IOP resources can be moved without IPL.

Logical partitions operate independently. Communication between partitions is achieved with standard LAN/WAN facilities. You can install OptiConnect software for high-performance communications between partitions with out the need for additional OptiConnect hardware.

OS/400 is licensed once for the entire system by its normal processor group, regardless of the number of partitions. License management across partitions is not supported. OS/400 V4R4, or later, must be installed on each partition. Previous releases are not supported on a logical partition.

Logical Partitioning

OS/400's superior dynamic logical partitioning is enhanced with extensive graphical workload management tools enabling multipartition management with customizable views for enhanced operator productivity. In addition, system administrators can export and save partition configuration data to simplify the management and reconfiguration of partitioned servers.

Logical partitioning supports the IBM iSeries 890. Customers can install OS/400 V5R2 in the primary partition or any secondary partitions. Existing customers with OS/400 V5R1 can add OS/400 V5R2 in secondary partitions to complete their release upgrade tests.

i5/OS Application Server processor entitlements

IBM adds the flexibility of application server licensing by processor on System i Models 550, 570, and 595. This new licensing approach more closely aligns actual use of software functions with an associated price, enabling you to license your i5/OS software, specifically for nondatabase work. This new flexibility broadens the appeal of i5/OS as the preferred operating system for a diverse portfolio of applications that can satisfy business solution needs.

For models 550, 570, and 595, i5/OS licensing is now available with two types of processor entitlements:

  • Processor using DB2 for i5/OS function must have one i5/OS processor entitlement. A minimum of one of these entitlements is included with each System i (5722-SS1). You can purchase additional processor entitlements (5722-SSA) as needed.

  • Each i5/OS processor not using DB2 for i5/OS function must have one i5/OS Application Server processor entitlement (5722-SSB). You can purchase these entitlements as needed for processors doing nondatabase work.

Entitlement details

An i5/OS Application Server processor entitlement allows the use of i5/OS operating system, except for restrictions on the use of the integrated database, DB2 for i5/OS.

Under this entitlement, you are entitled to use DB2 for i5/OS only if its use is for:

  • IBM software product that already includes DB2 entitlement in its license agreement

  • i5/OS operating system to perform function in support of i5/OS operating system

  • Minor, incidental purposes and is not intended for productive use of DB2 for i5/OS for the storage, retrieval, and management of data

The use of this i5/OS Application Server processor entitlement for a partition restricts any other i5/OS entitlements for that partition in the same manner as this entitlement.

Entitlement price

To obtain an i5/OS Application Server entitlement for a processor that does not use the functions of DB2, purchase the i5/OS Application Server processor entitlement feature under PID 5722-SSB.

With the introduction of i5/OS Application Server processor entitlements, the price of a processor entitlement is significantly less than an i5/OS processor entitlement that includes DB2 for i5/OS function. With this new processor entitlement structure you can purchase entitlements for those processors that do not do DB2 work, thus aligning i5/OS price with i5/OS function.

License management of entitlements

License Management for i5/OS requires only one Software License Key to manage processor entitlements.

Model 550
                  No charge    Priced
                  Entitlement  Entitlement    Entitlement
KEY    PID       Feature      Feature        Description
 ----   ------    -----------  -----------    -----------------------
 5051   5722-SS1    1507       ----           i5/OS processor
 5051   5722-SSA    ----       1538           Additional i5/OS processor
  NA    5722-SSB     ---       1592           i5/OS Application Server
                                              processor entitlements

Model 570
                  No charge    Priced
                  Entitlement  Entitlement    Entitlement
KEY    PID       Feature      Feature        Description
 ----   ------    -----------  -----------    -----------------------
 5051   5722-SS1    1516       ----           i5/OS processor
 5051   5722-SSA    ----       1539           Additional i5/OS processor
  NA    5722-SSB     ---       1595           i5/OS Application Server
                                              processor entitlements

Model 595
                  No charge    Priced
                  Entitlement  Entitlement    Entitlement
KEY    PID       Feature      Feature        Description
 ----   ------    -----------  -----------    -----------------------
 5051   5722-SS1    1526       ----           i5/OS processor
 5051   5722-SSA    ----       1540           Additional i5/OS Processor
  NA    5722-SSB     ---       1598           i5/OS Application Server
                                             processor entitlements

DB2 partitions:

For those customers who purchase i5/OS Processor entitlements, a Software License Key (5051) is generated that contains the quantity of processors entitled for DB2 use.

Enter the i5/OS processor entitlement key (5051) in each partition that requires DB2 function. Software License Manager/400 (SLM/400) assists with license compliance by counting the number of activated processors available to a partition used for DB2 work. This value is compared to the 5051 key quantity to determine license compliance.

Nondatabase partitions:

For those customers who purchase i5/OS processor entitlements and i5/OS Application Server processor entitlements, only one Software License Key (5051) is generated by IBM that contains the total quantity of processors entitled for both DB2 and non-DB2 use.

Enter the i5/OS processor entitlement key (5051) in every partition, including those partitions that require DB2 function and those that do not.

Software License Manager/400 (SLM/400) assists license compliance by counting the number of activated processors available to a partition that will not be used for DB2 work. This value is compared to the key quantity (total quantity of i5/OS processor entitlements plus i5/OS Application Server processor entitlements) to determine license compliance.

Software Maintenance (SWMA) for entitlements

Software Maintenance for System i is sold on a per processor basis. You are encouraged to purchase SWMA for each i5/OS processor entitlement and i5/OS Application Server processor entitlement on the System i server.

One year of Software Maintenance for i5/OS is included with an i5/OS Application Server processor entitlement. Renewals and three-year extensions are done under the normal SWMA for i5/OS and Select Programs offering.

Entitlement upgrades

No upgrades are offered from i5/OS Application Server processor entitlements to i5/OS processor entitlements.

Entitlement transfers

For capacity backup (CBU) models that are paired with a primary machine, the transferability terms for optional i5/OS Processor entitlements also apply to i5/OS Application Server processor entitlements.

Support for Lotus Domino for iSeries:

With Domino for i5/OS, IBM combines the iSeries value proposition of integration, ease-of-use, reliability and scalability with this outstanding messaging and collaboration software offering. Domino for i5/OS is designed to integrate with many built-in i5/OS services including security, backup and recovery, directory, systems management, iSeries Navigator, Java Virtual Machine, and IBM DB2 Universal Database for iSeries. In addition, deploying Domino on i5/OS provides the following value:

Reliability and Availability

The unique subsystem architecture of i5/OS isolates Domino applications from each other and from other work, which means the applications stay up and running, consistently. And if a problem occurs, i5/OS automatically stops and restarts a Domino server -- safely and quickly -- without affecting other activity on the server.

Scalability and Performance

On V5R4 i5/OS servers, you can grow your Domino workload with the same operating system and the same skills. With the combination of advanced scalable technology and architectural advantages for Domino server, iSeries achieved a Notesbench audit of 250,500 mail and calendar users. And, with Domino 7, most customers will see even further scalability along with a reduction in CPU utilization with the same number of R6Mail users.

Mixed workload

With Domino partitioning and i5/OS subsystems, customers can safely, reliably run multiple instances of Domino doing different types of Domino applications on the same server footprint. And, on traditional iSeries servers, customers can combine Domino with other non-Domino work, like ERP applications.

Speed of deployment

IBM eServer iSeries' reputation for speedy deployment extends to Domino. Because so much is built-in and "pre-integrated" into i5/OS, the administrator has less work to do when the iSeries server arrives. Administrators can move quickly to the task of delivering services to end users.

Ease of administration

iSeries has a "built for business" design. The capabilities an administrator needs are integrated and consistent, which means less money spent on people managing servers and more time available to deliver real value to the business. Integration Domino takes advantage of many built-in i5/OS services, including

  • DB2 UDB
  • Security
  • Backup and recovery
  • Directory
  • Systems management
  • iSeries Navigator
  • Java
  • TCP/IP

And, all these services and capabilities are included with i5/OS at no additional charge.

With Domino 7 for i5/OS, customers can take advantage of the HTTP Server (powered by Apache) to forward HTTP traffic to their Domino 7 servers. This is an alternative to exclusively using the built-in HTTP server provided with Domino. If you have existing Domino servers using older versions of the IBM HTTP Server plug-in, you can upgrade them to the new plug-in using the IBM Web Administration for iSeries interface. On iSeries, all disk units attached to a system are treated as a single logical disk unit. The operating system places data across the disk units to optimize performance and disk utilization. Ease of use also extends to performance management; a new feature starting with Domino 6 is the ability to integrate Domino with Collection Services. This i5/OS service can run continuously and store broad statistics about system performance. By integrating this service with Domino, you can store Domino statistics within this system repository. Domino for iSeries applications can take advantage of direct real-time access to DB2 Universal Database for iSeries, with or without programming. ODBC drivers and additional middleware communications layers are unnecessary when the application code runs on the server rather than the client.

Further information can be found on the Internet at the following Web site:


In addition, many separately purchased IBM products extend the capabilities of Domino. The following Domino extended products are currently available on i5/OS:

  • IBM Lotus Enterprise Integrator (LEI)
  • IBM Lotus Domino Document Manager (Domino.Doc)
  • IBM Lotus QuickPlace
  • IBM Integrated Domino Fax for iSeries
  • IBM Lotus Workflow
  • IBM Lotus Sametime

For more information about the extended products available on i5/OS, see:

http://www.ibm.com/servers/eserver/iseries/domino/ related.html

Java for System i

Java is the preferred language for network computing and can be used for stand-alone applications or client/server applications running over the Internet. Remote Method Invocation (RMI) is built into the iSeries Java software and can be used to communicate with the Toolbox for Java support running on any platform.

IBM has integrated a Java-compatible Java Virtual Machine (JVM) under the iSeries Machine Interface (MI) to optimize Java software performance on an iSeries system. In addition, the Developer Kit for Java and Toolbox for Java are included with every OS/400 shipped. They are also preloaded on iSeries systems but must be separately installed when upgrading to the current OS/400 operating system on existing RISC systems.

Java is a complete computing environment, setting standards for program portability and programmer productivity. It includes three primary functions and capabilities:

  1. An Object-Oriented Programming Language, developed at Sun Microsystems

  2. A Java Virtual Machine (run-time environment) that can be integrated in Web browsers (such as Netscape Navigator and Microsoft Internet Explorer), and operating systems (such as OS/400)

  3. A standardized set of Class Libraries (packages), that support:
    • Creating GUIs
    • Controlling multimedia data
    • Communicating over networks
    • Accessing data in stream files and relational databases

Java provides an object-oriented programming environment that is dramatically simpler than C++. Other aspects of the iSeries Java implementation provide improved scalability compared to other Java platforms owing to JVM enhancements and synergy with iSeries's object-based architecture.

Java's primary benefit is its ability to develop portable client/server applications using the Internet and intranets, whose "objects" can run on many different platforms in the same network. Java programs are compiled into platform-independent object code, known as byte-codes, which is executed by the runtime support (JVM) on each platform. The iSeries JVM supports three modes of execution:

  1. Interpreted. The byte-codes are sequentially read and executed by the JVM.
  2. Just in Time compilation (JIT). The byte-codes are compiled into machine instructions at runtime, utilizing many optimizations.
  3. Direct Execution (DE). The byte-codes are compiled prior to execution utilizing complex optimizations.

A Java SSL package on iSeries leverages the integrated SSL function built into the iSeries. You can easily build more secure client/server applications using Java. All data exchanged between the client and the server can be encrypted using the SSL protocol.

The Developer Kit for Java facilitates the creation of Java applets, servlets, and full-scale applications. It includes a collection of development tools, help files, and documentation for Java programmers. As Sun Microsystems, Inc. rolls out Java technologies and provides updates, the Developer Kit will also be updated. iSeries system support of Java will be made available over several releases, and applications written using the Developer Kit are portable.

In V5R1, options for Java 1.1.8 and Java2 Standard Editions (J2SE) 1.2.2 and 1.3.0 are shipped with the Developer Kit for Java, providing concurrent support for all three major versions of Java (1.1, 1.2, 1.3).

This updated version of the Developer Kit for Java includes performance improvements yielding up to 50% improvements over V4R5, including:

  • Improved garbage collection parallelism.
  • Improved code optimizations and object allocations, including cross-jar inlining.
  • JDBC and floating-point improvements.

Several limits to growth have been enhanced, most notably, the maximum object size has increased from 16 MB to 4 GB (4GB - 8KB).

iSeries Navigator enhancements include support for displaying the properties of Java classes and jar files, the ability to compile Java files, interactive support for Input and Output, as well as automating RAWT connections when launching Java programs from iSeries Navigator.

For additional JDK support information, including service requirements, refer to the online publication "IBM Developer Kit for Java" available from the iSeries Book Server at URL:

http://publib.boulder.ibm.com/pubs/html/iseries/ infocenter

The IBM Toolbox for Java enables a Java servlet, applet, Java Server Page (JSP), or application to easily access iSeries data. It is a collection of classes that represent iSeries data, providing familiar iSeries client/server program interfaces for Java programs. The Toolbox also provides a set of GUI classes. These classes use the access classes to retrieve data, then present the data to the user.

The Toolbox supports the Secure Sockets Layer (SSL) specification. When using the Toolbox functions to access an iSeries system running OS/400 V4R4, or later, an SSL connection can be used providing data encryption and server authentication.

IBM Toolbox for Java provides access to the following iSeries system resources:

  • Connections to the iSeries
  • Security
  • Digital certificates stored on the iSeries
  • iSeries user and group information
  • Database access via JDBC
  • Database access via Record-Level File Input/Output
  • iSeries program call
  • iSeries command call
  • iSeries Integrated File System
  • iSeries print resources, including spooled files
  • iSeries message queues
  • iSeries data queues
  • iSeries user spaces
  • Data description and conversion
  • iSeries active job information
  • iSeries message files
  • iSeries data areas
  • iSeries system values
  • Authority on an iSeries object
  • Information about jobs running on the iSeries
  • Information on users on the iSeries
  • iSeries system status

The IBM Toolbox for Java includes:

  • A user interface framework to provide a productive development environment for building graphical panels. The framework automatically handles the exchange of data. The developer only needs to create one or more data beans and bind them to the panel components using tags defined by the Panel Definition Markup Language (PDML).

  • A user interface framework to create a platform and technology independent representation of graphical panels based on the Extensible Markup Language (XML). Also included is a pure Java framework for interpreting the XML and constructing user interface panels based on the Java Foundation Classes (JFC).

  • A resource script converter to convert Windows dialogs to equivalent Java panels defined in XML.

  • A GUI builder tool (a WYSIWYG GUI editor) to develop Java GUIs.

  • A program-call framework, provided via a program call markup language (PCML) -- a tag language used for supporting the program call function of the toolbox. The language fully describes all parameters, structures, and field relationships necessary to call an iSeries program.

The Toolbox runs on Java compatible JVMs running 1.1.8, 1.2.2, or 1.3. Toolbox source is available via the JTOpen project. For more information, access the Toolbox web page at:


Functional enhancements in V5R1 include:

  • A set of classes in the resource package providing a generic framework and consistent programming interface for working with various iSeries objects.

  • Bidirectional text conversion between iSeries and Java formats is supported.

  • JDBC 2.0 Optional Package extensions are supported.

  • A set of classes in the report writer package provide a programming interface for creating formatted documents in Adobe's PDF format or documents that can be sent directly to HP PCL printers attached directly to the iSeries or to the network.

  • A new set of print classes that enable Java applications to write data to iSeries spool files in the form of records and use existing iSeries formatting tools to format the records of data to be printed.

  • Classes are included to work with iSeries environment variables.

  • Classes in the HTML package are improved to increase the variety of HTML tags you can include in your Java programs.

  • Classes are included to configure AS/400 NetServer.

Performance enhancements in V5R1 include:

  • The performance of converting text between Unicode and EBCDIC is improved.

  • Classes are included to manage a pool of connections to the iSeries.

  • When running on a V5R1 or later iSeries JVM, CommandCall, and ProgramCall now optionally stay on thread instead of performing the function via a call to a server Job.

  • The performance of listing files in the integrated file system of the iSeries is improved.

i5/OS V5R4 JDK 6


JDK includes these new collection interfaces:

  • Deque: Double ended queue supports element insertion and removal at both ends. Extends the Queue interface.

  • BlockingDeque: Deque with operations that wait for the deque to become non-empty when retrieving an element, and wait for space to become available in the deque when storing an element. Extends both the Deque and BlockingQueue interfaces. (This interface is part of java.util.concurrent.)

  • NavigableSet: SortedSet extended with navigation methods reports closest matches for given search targets. A NavigableSet can be accessed and traversed in either ascending or descending order. This interface is intended to supersede the SortedSet interface.

  • NavigableMap: SortedMap extended with navigation methods returns the closest matches for given search targets. A NavigableMap can be accessed and traversed in either ascending or descending key order. This interface is intended to supersede the SortedMap interface.

  • ConcurrentNavigableMap: ConcurrentMap that is also a NavigableMap. (This interface is part of java.util.concurrent.)

The following concrete implementation classes are added:

  • ArrayDeque: Efficient resizable-array implementation of the Deque interface

  • ConcurrentSkipListSet: Concurrent scalable skip list implementation of the NavigableSet interface

  • ConcurrentSkipListMap: Concurrent scalable skip list implementation of the ConcurrentNavigableMap interface

  • LinkedBlockingDeque: Concurrent scalable optionally bounded FIFO blocking deque backed by linked nodes

  • AbstractMap.SimpleEntry: Simple mutable implementation of Map.Entry

  • AbstractMap.SimpleImmutableEntry: Simple immutable implementation of Map.Entry

These existing classes are retrofitted to implement these new interfaces:

  • LinkedList: Deque
  • TreeSet: NavigableSet
  • TreeMap: NavigableMap

Two new methods are added to the Collections utility class:

  • newSetFromMap(Map): Creates a general-purpose set implementation from a general-purpose map implementation.

  • asLifoQueue(Deque): Returns a view of a Deque as a last- in-first-out (LIFO) queue.

JConsole enhancements

The Java SE platform includes a graphical monitoring tool called JConsole. The tool implements the Java Management Extensions (JMX) API, which enables you to monitor the performance of a Java Virtual Machine (JVM) and any instrumented applications. Introduced in Java 2 Platform, Standard Edition 5.0, JConsole became an officially supported feature of J2SE 6.

The following enhancements are made to the JConsole tool:

  • JConsole Plugin support enables you to build your own plug-ins to run with JConsole; for example, adding a custom tab to access MBeans for your applications.

  • Dynamic attach capability enables you to connect JConsole to any application that supports the dynamic Attach API, which was also added in Java SE 6.

  • Enhanced user interface makes data more easily accessible.

  • New Overview and VM Summary tabs make for a better presentation of general information about your JVM.

  • Improved presentation of MBeans make it easier to access the operations and attributes of your MBeans.

Monitoring and management API enhancements

J2SE includes an API to allow you to monitor and manage the JVM and other applications in the package java.lang.management.

The J2SE 6 platform includes the following enhancements to this API.

  • Support for java.util.concurrent locks

  • The java.lang.management package adds new classes and methods for obtaining the list of locks owned by a thread and to report which stack frame locked a monitor:

    • New LockInfo class

    • New MonitorInfo class

    • New ThreadInfo methods getLockInfo(), getLockedMonitors() and getLockedSynchronizers()

    • New ThreadMXBean methods dumpAllThreads() and getThreadInfo(long ids, Boolean lockedMonitor, Boolean lockedSynchronizers)

Java instrumentation

The following functions are added to the java.lang.instrument package:

  • Support for retransformation of class files; to facilitate dynamic transformation of classes that are already loaded, the following methods are added:

    • Instrumentation.retransformClasses(Class...)

    • Instrumentation.addTransformer(ClassFileTransformer, Boolean)

    • Instrumentation.isModifiableClass(Class)

    • Instrumentation.isRetransformClassesSupported()

    These methods are suited to operations such as adding instrumentation to methods whose classes have already been loaded. Support for retransformation means that access to the original class file is no longer required in order to instrument loaded classes. They enable the easy removal of applied transformations and are designed to work in multi-agent environments.

  • Support for instrumenting native methods. The following methods enable native methods to be instrumented by including a JVM-aware mechanism for wrapping the native method.

    • Instrumentation.setNativeMethodPrefix(ClassFileTransformer, String)

    • Instrumentation.isNativeMethodPrefixSupported()

  • Support for appending to class loader search. The following methods enable instrumentation support classes to be defined in the appropriate class loader.
    • Instrumentation.appendToBootstrapClassLoaderSearch(JarFile)
    • Instrumentation.appendToSystemClassLoaderSearch(JarFile)

HTTP Server for iSeries:

HTTP Server for iSeries provides World Wide Web (WWW) server capability integrated with OS/400 security, enabling exploitation of the Internet for marketing and merchandising. The HTTP Server allows iSeries systems attached to a TCP/IP network, such as the Internet or an intranet, to provide objects at the request of any local or remote Web browser. HyperText Markup Language (HTML) documents, index (directory) files, plain text, video, Java, graphics, and audio objects can be served from iSeries file systems. Multiple HTTP Servers are supported to balance content and workload. A Web browser can be used to administer and configure these servers. With V5R3 and later, the HTTP server is based on the open source Apache server, see below for details.

Apache, a freeware HTTP server, is open-source software that implements the industry-standard HTTP/1.1 protocol with a focus on being highly configurable and easily extendible. It is built for several server platforms and distributed under the Apache Software License by the Apache Software Foundation.

The IBM HTTP Server (powered by Apache) for iSeries provides:

  • Graphical interface -- a full-function, task-oriented, web-based user interface for administration and configuration of servers, including task-based wizards for configuration ease of use.

  • Migration wizard -- aids in the migration of your customized original server configuration to a configuration for HTTP server (powered by Apache).

  • The HTTP Server (powered by Apache) supports Secure Sockets Layer (SSL) security protocols for data encryption and server certificate authentication, which requires one of the following:
    • Cryptographic Access Provider 128-bit for iSeries (5722-AC3) (1)

    (1) Approved for export by the U.S. Government.

  • Authentication using LDAP, iSeries user profiles and validation lists. You can associate client certificates with iSeries user profiles and validation lists, allowing users seamless access to your Web servers resources without having to sign on. Client and server authentication with SSL V2, V3, and TLS is supported.

  • Full, native SSL support, including client authentication and association between client certificates and validation lists or iSeries user profiles. You can configure the SSL cipher suite and configure a minimum encryption level in order to require your clients to use the proper level of security when accessing your HTTP server.

  • Authorization features -- support for denying specific users, groups, or hosts

  • Digital ID -- authentication requires SSL client authentication for HTTP Server client certificates. This offers resource protection with:
    • Valid client certificates
    • Client certificates with certain distinguished names values
    • Client certificates associated with iSeries and AS/400 user profiles
    • Client certificates associated with iSeries and AS/400 validation lists

  • Built in proxy function with proxy cache -- your HTTP Server for iSeries can be configured as a proxy server. Proxy server caching provides improved web performance by caching frequently accessed pages in the proxy cache.

  • Static local file caching -- provides the web administrator a configuration mechanism to choose which files to load into the server cache at server start up.

  • Dynamic local file caching -- Server automatically caches frequently served static web pages to provide better performance without manual configuration.

  • CGI support for C, C++, RPG, COBOL, REXX, and CL

  • CGI APIs (except QzhbCgiParse, QzhbChiUtils, and QtmhCvtDB) -- APIs available to the CGI programmer for greater function and flexibility

  • Net.Data support -- scripting language that enables the dynamic generation of Web pages using data from a variety of data sources

  • Persistent CGI support -- provides the CGI programmer the ability to write CGI programs that maintain state across a session.

  • Support for CGIs running in named activation groups -- provides improved CGI performance

  • Configuration, instance, and group file APIs -- provides the ability to manage HTTP server and group file configuration through application programming

  • Global and instance-specific configuration settings -- provides for greater flexibility in the HTTP server configuration.

  • WebServer Search engine support -- allows you to perform full text searches on html and text files stored in an iSeries file system from any Web browser

  • Support for most iSeries file systems -- allows you to store the objects to be served most file systems supported by the iSeries integrated file system.

  • LDAP support -- allows the HTTP server to use LDAP to store configuration information. LDAP integration allows you to use directory services for server configuration and authentication

  • Support for TRCTCPAPP -- tracing mechanism improves serviceability of the HTTP server (powered by Apache)

  • User-defined methods -- enables web tools such as Netscape Composer.

  • Headers control -- ability to control expires and other headers

  • URL rewriting -- allows you to set up rules to rewrite requested URLs on the fly

  • Virtual hosting, including IP address-based virtual hosting, name- based virtual hosting, and dynamic virtual hosting -- allows more than one Web site on one system or Web server.

  • Control number of CGI jobs started with server (and user profile) -- improves performance by allowing the web administrator to configure the number of CGI jobs to start during server start up.

  • More customization of directory listings -- provides more options for serving customized directory listings from the server, including fancy indexing support.

  • Support for configuration files in threadsafe IFS file systems -- allows you to customize where to store HTTP server configuration files

Web Administration GUI

The Web Administration GUI included in the IBM HTTP Server for iSeries adds support for:

  • WebSphere Applicatoin Server -- support to setup up a WebSphere Application Server server via browser-based administration with easy-to-use wizards for creating HTTP and application server instances, deploying J2EE applications, and management of HTTP and application servers and their applications.

  • WebSphere Portal - an easy-to-use interface to set up WebSphere Portal server (Express and Enable) via a wizard that walks the user through the necessary steps to create and configure all the necessary servers, deploy the Portal EAR files, and perform other setup necessary to get Portal up and running.

  • Workplace - an easy-to-use interface to set up a Workplace server (Workplace Services Express or Workplace Collaboration Services) via a wizard that walks the user through the necessary steps to create and configure all the necessary servers, deploy the portlets and perform other setup necessary to get Workplace up and running using LDAP and DB2.

  • The retrieval and display of HTTP Server Statistical information via the user's Web Browser -- used to track cached and non-cached data sent and received to a particular HTTP server. Statistical subsets indicate whether the data has been handled by the IBM HTTP server (powered by Apache), a CGI program, an application server, or a user module.

  • Web Performance Advisor - advice on how to improve your Web server's performance. The Web Administration GUI quickly guides you through a simplified view of the many i5/OS and Web server configuration options that you can change to improve performance.

  • Web Performance Monitor - provides monitoring the performance usage of your Web transactions across the various jobs running on your i5/OS system. Web based applications use multiple i5/OS jobs, such as the HTTP server job, application server job, database job.

The IBM HTTP Server for iSeries adds support for:

  • An update to IBM HTTP Server (powered by Apache) to a new release of the Apache 2.0 HTTP Server.

  • CGI enhancements for running an initialization URL at startup and ability to set CGI jobs' library list.

  • Kerberos authentication. This enhancement offers Windows clients using Active Directory and Kerberos login a single sign-on between a Windows desktop and Microsoft Internet Explorer accessing HTTP Server on iSeries. Enterprise Identity Mapping (EIM) can be used in this environment.

  • Enhancements to make porting user modules to iSeries easier.

  • Enhancements to allow a CGI programs to run in more than language, from a single HTTP server.

  • Support for performance metrics using ARM (Application Response Measurement).

  • Spport for LDAP groups for user authentication

Network Security:

Security Enhancements

For V5R2, many security enhancements are implemented. These include the following, and are discussed in more detail in the Supplemental Information section:

  • Enhancements to iSeries Kerberos support
  • Enhancements for Digital Signatures
  • Implementation of new Java Security standards
  • Firewall friendly Virtual Private Networks (VPN)
  • Enhancements for Cryptographic Accelerators

Support for Hardware Cryptographic Accelerators

Encryption is a key e-business security mechanism. The Cryptographic Accelerator is targeted to high transaction rate, secure Web applications using SSL, or Transport Layer Security (TLS). When installed, it is automatically used by the system to off-load compute-intensive public-key processing to improve cryptographic performance for transactions using SSL/TLS.

Web Services and SOA for i5/OS (5722-SS1 Option 3)

The i5/OS operating system integrates a Web services server for Integrated Language Environment (ILE) and enables the latest SOA technologies on i5/OS. This SOA-ready system embeds a Web Services server directly into i5/OS and enables the programming model to leverage the latest advancements for SOA.

Integrated Web services server for ILE

The integrated Web services server is an ILE starting step for Web Services and SOA on the System i platform. This server is an i5/OS functional enhancement making Web Services and SOA interoperability easier. The Web services server supports the consumption and externalization of services within the ILE programming environment. The Web Services server embeds a Web service engine and run time integrated within the System i architecture.

With ILE enablement i5/OS is one of the first systems to interoperate with many SOA technologies and products such as WebSphere Enterprise Service Bus and WebSphere Process Server. Two major components simplify the integration of ILE with SOA, Web services, and Web 2.0 on the System i platform:

  • Integrated Web services server

  • Integrated Web services client

The integrated Web services server greatly simplifies the process of externalizing ILE business logic as a service via the Web Administration for i5/OS GUI. This simplification has been accomplished by abstracting the hidden complexities of Web services and extending the ILE programming model to allow a System i administrator to directly externalize various ILE business tasks as services In fact, the externalization of RPG and COBOL business logic as a service is now an administrative task on i5/OS. The integrated Web services client for ILE includes an internal engine that supports the ILE environment to act as a client available to the ILE programming languages on System i, including RPG, COBOL, C, and C++.  

Integrated Web services server

This Web service engine or run time is integrated in i5/OS to externalize ILE business logic (RPG or COBOL) as a service. i5/OS integrates a Web services run time into the operating system and enables SOA technologies directly for interaction with the operating system. This integration opens the i5/OS system to a variety of Web service client implementations, including RPG, COBOL,C, C++, Java, .NET, PHP, WebSphere Process Server, ESB, and Web 2.0.

  • Acts as easy initial step on path towards Web services and SOA on System i platform

  • Supports enablement of ILE service program and programs as services

  • Automatically generates and binds service information when compiling the ILE program or service program

  • Uses the Web Administration for i5/OS GUI (shipped with the latest update to PTF SF99114):

    • Create Web services server with a few easy steps

    • Select and deploy ILE programs and service programs as services

    • Easily view and manage all services available on the system

  • Uses administrative task to export ILE (RPG,COBOL) program or service program business logic

  • Externalizes business tasks as a Web service natively on ILE (services provider)

  • Opens ILE (RPG and COBOL) to business logic for a variety of Web service clients, including RPG, COBOL, C, C++, Java, .NET, PHP, and more

  • Enables i5/OS to be SOA ready for service deployment

  • Does not require new skills or tools for ILE enablement

  • Uses and enhances existing System i development skills to interact with Web services and integrate SOA

  • Dynamically generates WSDL representation for client invocation of ILE program/service programs.

  • Helps ILE programmers externalize a program or service program as a service

  • Uses fast interoperability of ILE programming architecture for minimal consumption of System i resources

  • Integrates into i5/OS with PTFs for 5722-SS1

Integrated Web services client for ILE:

The client delivers a mechanism to generate service artifacts and allow ILE (RPG, COBOL, C, and C++) to act as a services consumer. It can call a variety of Web service implementations, including RPG, COBOL, C, C++, Java, PHP, .NET, WebSphere Process Server, ESB, Web 2.0, and so on.

  • Supports enablement of ILE program to consume services

  • Invokes Web service client from ILE programs (RPG, COBOL, C, and C++)

  • Enables ILE programmer to consume services from a program or service program.

  • Uses ILE enablement to bind and call a service directly from an i5/OS program or service program

  • Leverages WSDL to generate proxy client code to be integrated in a program or service program

  • Uses and enhances existing System i development skills to interact with Web services and SOA

  • Uses quick interoperability of ILE programming architecture for minimal consumption of System i resources with a small system footprint

  • Ships as PTF delivery for 5722-SS1 Option 3

  • Supports Web service client module for C, C++, RPG, and COBOL

  • Supports document style literal only

  • Complies with Web Services Invocation (WSI) 1.1 basic profile

  • Supports Secure Sockets Layer(SSL) for ILE service

  • Implements staged development for ILE:

    • Generate proxy code

    • Examine proxy code

    • Integrate proxy code into ILE source code

    • Compile and bind program or service program

    • Run ILE program or service program as a Web service client

WebSphere Application Server V6.1 Feature Pack for Web Services

The Feature Pack extends the capabilities of WebSphere Application Server V6.1 on System i to enable Web services messages to be sent asynchronously, reliably, and securely, focusing on interoperability with other vendors. They are optionally installable product extensions that offer targeted, incremental new features.

Interoperable, reliable Web services

  • Through support for key Web services standards, you can send messages:

    • Reliably: Be confident that your message will reach its destination.

    • Asynchronously: Communicate reliably even if one of the parties is temporarily off- line, busy, or unobtainable.

    • Securely: Rest assured your messages are not vulnerable to attack.

    • Interoperably: Use other vendors' offerings with confidence.

  • Easy to implement.

    Programming model enhancements simplify application development through a standard, annotation-based model to develop Web service providers and clients. A common set of binding rules for XML and Java makes it easy to incorporate XML data and processing functions in Java applications, and a further set of enhancements help you send binary attachments, such as images or files, along with your Web services requests easily and reliably.

  • Consumable and extensible.

    Simplified management using Web services profiles makes it easy to configure and reuse configurations, so you can introduce new Web services profiles seamlessly in the future. These configurations are captured in a grouping called policy sets that enable you to select and associate with an application different qualities of service. You can configure the policy sets to allow only those capabilities within a given WS-Interoperability (WS-I) profile, thereby ensuring that the only configurable portions are those you choose. WS-I is an open industry organization chartered to promote Web services interoperability across platform systems, and programming languages.

For more information on WS-I, visit


For more information, visit


WebSphere ESB

WebSphere ESB is a flexible connectivity infrastructure for integrating applications and services, designed to enable the development of an SOA. Built on top of WebSphere Application Server, WebSphere ESB delivers a standards-based connectivity and integration solution that allows you to create and deploy interactions quickly and easily between applications and services, with a reduced number and complexity of interfaces. You can focus on your core business, rather than on your IT. WebSphere ESB includes platform support for System i to leverage native i5/OS.

New features include the following:

  • Leveraging of WebSphere Application Server for other solutions, in addition to inheriting new features and benefits introduced in WebSphere Application Server V6.1

  • Support for i5/OS and remote DB2 support for System i systems to enable integration with i5/OS applications and leverage relational database management servers running on i5/OS

You can visit:


WebSphere Process Server

WebSphere Process Server helps ensure that the processes you design in WebSphere Business Modeler or WebSphere Integration Developer are executed consistently, reliably, securely, and with transactional integrity. Built on open standards, it deploys and executes processes that orchestrate services (people, information, systems, and trading partners) within your SOA or non-SOA infrastructure. When combined with the power of WebSphere Business Monitor, processes can be optimized to meet changing business requirements, giving the business a competitive advantage. WebSphere Process Server is built on, and contains, WebSphere ESB functions. WebSphere Process Server includes platform support for System i server to leverage native i5/OS.

New features in WebSphere Process Server V6.1 leverage:

  • WebSphere Application Server in addition to inheriting new features and benefits introduced in WebSphere Application Server V6.1

  • Native i5/OS by running on the System i platform

  • Relational database management servers with DB2 support

You can visit


WebSphere Integration Developer

WebSphere Integration Developer is the "one tool, one set of skills" solution for end-to-end integration in your SOA. This Eclipse-based tool builds SOA-based business process management and integration solutions across WebSphere Process Server, WebSphere ESB, and WebSphere Adapters. It simplifies integration with rich features that accelerate the adoption of SOA by rendering existing IT assets as service components, encouraging reuse and efficiency. It enables integration developers to assemble complex business solutions -- whether processes, mediations, adapters, or code components -- with minimal skills. You can construct process and integration solutions using drag-and-drop technology to define, in a visual way, the sequence and flow of business processes. WebSphere Integration Developer supports development deployment to WebSphere ESB on i5/OS and WebSphere Process Server on i5/OS.

New features in WebSphere Integration Developer include:

  • Increased developer productivity with ease-of-use enhancements

  • Enhanced human workflow

  • Improved business-driven development capabilities

  • Better connectivity

You can visit



I5/OS integrated Web application server (5722-SS1)

The integrated Web application server integrates an OSGi-based Web servlet container with the i5/OS operating system. This Web container includes the basics for applications to be up and running quickly and effectively on the Web. The integrated Web application server is a good place to prototype new applications or run existing small footprint or low-use applications. For applications that require a high degree of scalability, WebSphere Application Server Express is recommended. The integrated Web application server can be considered an "on ramp" to the more scalable solution. This Web container is easy to use and configure, does not require any additional products to install, and uses minimal system resources. The integrated Web application server can be completely administered using the Web Administration for i5/OS GUI. You can create, start, stop, and manage servers u9sing this commonly available interface.

Benefits of the server include the following:

  • OSGi-based Web servlet container

  • Support for JDK 1.5 run by default on IBM technology for Java (32-bit)

  • Support for DB2 for i5 using Toolkit for Java or Java native implementations

  • GUI to manage all aspects of the integrated Web application server:

    • Wizard to create a new server instance

    • Wizard to deploy applications to the instance of choice

    • Interface to manage applications, server properties, and database connection information

    • Ability to view all servers on the System i platform; start, stop, or delete servers in one easy-to-use display

Security Enhancements


In V5R1, enabled applications on OS/400 act as a Kerberos client by processing a Kerberos ticket granted by a Kerberos server somewhere in the network. In V5R2, iSeries continues to improve its interoperability with Kerberos environments. Server applications within OS/400 are enhanced to allow OS/400 itself to act as a Kerberos client greatly improving interoperability with Microsoft and other Kerberos-based authentication systems.

In V5R3, support is available on iSeries to run a Key Distribution Center (KDS) or Kerberos server on iSeries. this KDS support is available and runs in the PASE environment.

Digital Signatures

Digital signatures on OS/400 objects helps enhance the integrity of software and data. Business Partners, customers, and IBM can sign information to provide improved integrity in their products. Digital signatures help to identify data tampering, virus introduction, or any other modification to an object. The signature also helps to identify the originator of the data or software. The infrastructure and APIs for signing some objects, including programs, were provided in V5R1 and OS/400 itself was signed. In V5R2, in addition to support for command objects, support was added to allow non-objects to be signed. This non-object support can be used to write applications that sign items like digital receipts and B2B transactions.

Java Security

Java Generic Security Services (JGSS) is a Java standard (JSR 000072). In V5R2, the APIs are added to the iSeries Developer Kit for Java. The JGSS APIs enable Java applications to access either Java-based or native OS/400 Kerberos (client) security services. JGSS compliments the existing OS/400 GSS support by providing support for Java applications. Integration of JGSS with the existing OS/400 native GSS APIs means better performance, serviceability, and administration.

Java Generic Security Services (JGSS)

Using JGSS, you can write Java applications that make use of Kerberos.

JGSS consists of:

A security framework with a set of APIs allows Java applications to use security services such as authenticating a principal identity, delegating rights to a peer, and applying message confidentiality and integrity. This allows source level portability of applications to different environments.

Security mechanisms, or providers, are used by the framework to provide concrete implementations. An example of a security mechanism is Kerberos V5.

JGSS on OS/400 is shipped with a Java Kerberos provider and an OS/400 provider. The OS/400 provider allows Java applications to utilize the OS/400 Network Authentication Service (NAS) functionality and uses the same NAS configuration files and tools. NAS provides Kerberos functionality to C/C++ programs. NAS also interoperates with Enterprise Identity Mapping (EIM) to provide single sign-on capabilities.

This function is available today via PTFs SI04497 and SI04498.

Firewall Friendly VPN

Network Address Translation, or NAT is a technology used in many networks and firewalls. Until now, NAT did not allow end-to-end security using the IPSec protocol. UDP encapsulated IPSec is a new standards-based protocol that solves this problem. With UDP encapsulation, end-to-end IPSec security is possible to systems anywhere in your network further reducing the risk associated with doing business on the Internet.

In V5R2 support for UDP encapsulated IPSec was added to OS/400. OS/400 supports this function as a client for UDP encapsulation. That is, it can only initiate UDP encapsulated traffic.

IP Networking Security Enhancements

In addition to "Firewall Friendly VPN," several other key enhancements support IP network security. These include:

  • Configuring IP packet rules can be a very difficult task, requiring detailed knowledge of how TCP/IP and associated protocols work. In V5R2, wizards added to the packet filtering support in iSeries Navigator allow the most common filtering configurations to be easily configured by even novice-level network administrators.

  • Configuring the required IP filtering rules in support of VPN is eliminated in the majority of cases. This includes the "implicit IKE rules" that allows IKE (UDP 500) traffic without explicitly coding the required filter rules and no need to explicitly code IPSec policy filters.

Transport Layer Security (TLS)/Secure Sockets Layer (SSL) support for server authentication is added to the native FTP Client allowing secure sessions with compatible servers (including the native FTP server with TLS/SSL support added in V5R1). This support allows you to specify whether FTP session data, including the login ID and password used for authentication, is encrypted.

Support for X.509 certificates can be used by the Web Server, Secure Sockets Layer, IPSec, Client Access Express, and other applications. The user interface is easier to use.

Global Server Certificate support is added to the certificate services available on the iSeries and AS/400. The Web Server and other applications use certificates for network and Web-based security.

The following services support SSL:

  • HTTP Server
  • LDAP Server
  • Telnet Server
  • FTP client and server
  • Management Central
  • DDM and DRDA
  • iSeries Access servers
  • iSeries Navigator

With SSL support, these services can establish secure communications sessions with their corresponding clients. Data exchanged between the clients and servers are encrypted and therefore not subject to eavesdropping.

Network Authentication Service Server - V5R3

The previous support for Network Authentication Services (NAS) on iSeries consists of the GSS API suite and Kerberos Version 5 APIs. The iSeries NAS support (originally delivered in V5R1) enables iSeries applications and services to request and validate Kerberos tickets created by a Key Distribution Center in the network.

In this release, support for a Key Distribution Center is delivered on iSeries via the pSeries NAS product running in the PASE environment. This program is delivered on iSeries via the 5722-AC3 (Crypto Access Provider) program. The Key Distribution Center support provides the ability to create and manage tickets in your network.


Net.Data is a server-side scripting language that extends Web servers by enabling the dynamic generation of web pages using data from a variety of data sources. The data sources can include relational and non-relational database management systems such as DB2, (DRDA)-enabled databases, and flat file data. Net.Data applications can be rapidly built using a scripting language that is simple yet powerful. Net.Data allows reuse of existing business logic by supporting calls to applications written in a variety of programming languages, including Java, C, C++, RPG, COBOL, CL, REXX and others.

WebServer Search Engine:

The iSeries WebServer Search Engine allows you to perform full text searches on html and text files stored in an iSeries file system from any Web browser.

The iSeries WebServer Search Engine features include:

  • Indexes documents for fast searching - the iSeries WebServer Search Engine indexes html or text files into a format that allows a large number of documents to be searched quickly. Multiple indexes can be created and documents from multiple directories can be placed in a single index.

  • Exact word indexing -- the iSeries WebServer Search Engine uses an exact word indexing scheme rather than a keyword indexing scheme used by many search engines. All words are indexed; nothing is left out. Exact word indexing provides for faster index building and more precise searching than keyword indexing, but does require additional disk space. Documents are searched using consecutive character matching which is essential for proper support of double byte languages.

  • Advanced search functions -- the iSeries WebServer Search Engine supports advanced search capabilities such as exact search, fuzzy search, wild card search, proximity search, English word stemming, case sensitive search, boolean search and document ranking.

  • Customizable search forms -- the search forms and search results form are completely customizable by the end user using the Net.Data scripting language. This gives the user the ability to specify the type of search to be done and how the results are to be displayed. The information that can optionally be displayed on the results page include:
    • Number of documents satisfying the search
    • Number of occurrences of the search term
    • Number of documents returned on this page
    • he URL associated with each document
    • The document's ranking, last modified date and size.

      Any and all of this information can be displayed however the user wishes.

  • Web based administration -- administration of the search indexes is handled as part of the IBM HTTP Server Configuration and Administration Web pages. The search administration forms allow you to create and delete search indexes, update search indexes when documents are modified and view the status of an index.

  • Multiple language support -- the iSeries WebServer Search Engine supports multiple national languages including double byte languages Chinese, Japanese, and Korean.

The iSeries WebServer Search Engine can be used instead of the NetQuestion search engine.

Triggered Cache Manager

Triggered Cache Manager (TCM) provides a mechanism to cache dynamically-generated Web pages. TCM allows a Web designer to build dynamic pages and "push" them to an external cache. TCM controls update of the cached pages, and will only update the cache when the underlying data changes, thereby improving the performance of a Web site. Triggered cache manager is packaged as an option of IBM HTTP Server for iSeries.

Lightweight Directory Access Protocol (LDAP) on the iSeries:

OS/400 provides an LDAP-accessible directory server and corresponding APIs that communicate with other LDAP directory servers. APIs are provided for both OS/400 and Windows applications written in C, and C++. LDAP-enabled applications, such as Internet mail clients, can access, update, and manage the iSeries directory.

You can develop OS/400 applications to use LDAP for managing distributed information across the Internet and intranets using LDAP directories for both IBM and non-IBM platforms. iSeries user information, such as e-mail addresses, is accessible to mail clients and other LDAP applications.

Virtual Private Networks:

iSeries virtual private networking support is based on industry standards that include:

  • IP Security Protocol (IPSec)
  • Internet Key Exchange (IKE)
  • Layer 2 Tunneling Protocol (L2TP)

The iSeries virtual private network (VPN) solution applies to these environments:

  • Intranets - secure connections within an intranet

  • Extranets or ValueNets - secure connections between intranets of different companies

  • Remote office or branch office - secure connections between intranets of the same company

  • Mobile workers - secure connection from a mobile worker, using different Internet service providers (ISPs) to an intranet


In Version 5 Release 1, option 33 is renamed to OS/400 Portable Application Solutions Environment (OS/400 PASE). Prior to Version 5 Release 1 Option 33 was named AS/400 PASE.

OS/400 PASE supports the AIX 5L 5.1 application environment, which includes support for 32 and 64-bit applications. Additionally, OS/400 PASE (OS/400 option 33) is packaged as a no-charge feature of OS/400, enabling use of OS/400 PASE by operating system functions or other IBM software such as Tivoli Storage Manager.

V5R2 OS/400 PASE includes Linux library support based on AIX 5L. Many Linux-developed applications can be ported to the POWER PC architecture through a recompile. Most Linux applications that can be ported to AIX 5L can be easily ported to OS/400 PASE providing a more integrated and scalable solution.

V5R2 includes support to build OS/400 PASE programs without compiling on a separate AIX system. OS/400 PASE (OS/400 option 33) now includes a number of application development utilities such as make, ld (linker), and as (assembler). Header files for OS/400 PASE C and C++ programs are now included in System Openness Includes (OS/400 option 13). OS/400 application developers can compile C and C++ applications using compilers provided separately by IBM. Also, the iSeries System Debugger supports debugging for OS/400 PASE applications. OS/400 PASE can also run many open source tools compiled for AIX PowerPC (including the gcc compiler).

The OS/400 PASE application environment includes PTY/TTY device driver support, which makes it easier to port applications that require terminal support.

V5R2 supports OS/400 PASE programs to launch the iSeries integrated JVM, as well as support for the integrated JVM to run native methods implemented as procedures in an OS/400 PASE executable. This support makes it easier to port AIX applications that use a combination of Java and C/C++ code to OS/400 PASE.

OS/400 PASE is an integrated component of OS/400 that provides in Version 5 Release 1 a subset of AIX 4.3.3 functionality to support running UNIX* applications. OS/400 PASE is supported on all iSeries models, as well as any AS/400e server models 6xx or Sxx, or later.

OS/400 PASE exploits the hardware's capability to switch between OS/400 and AIX runtime modes within an OS/400 job. This allows applications deployed using OS/400 PASE to run directly on the hardware and take advantage of OS/400 services such as file systems, security and DB2 Universal Database. OS/400 PASE applications can also be integrated with Java(**), Lotus Domino and OS/400 Integrated Language Environment (ILE) applications.

OS/400 PASE is not an operating system and does not provide support for developing UNIX applications. Any changes or additions required to port UNIX applications to OS/400 PASE are compiled and linked on a workstation running a level of AIX that is supported by OS/400 PASE.

Applications deployed using OS/400 PASE run in a normal OS/400 job and are managed using standard OS/400 operations. Serviceability, backup and restore, and other administrative tasks are performed using standard OS/400 operations and system management facilities.

Significant enhancements to OS/400 PASE in Version 5 Release 1 include:

  • Support of the AIX 4.3 64-bit application model

  • National Language Version (NLV) enablement, including translated message catalogs for IBM-supplied runtime libraries and utilities

  • Documentation for OS/400 PASE runtime, shells, and utilities in the IBM iSeries Information Center

  • Header and export files for OS/400 PASE extensions packaged with option 33. This provides a single repository where files necessary to compile and link OS/400 specific changes to the application can be copied to the AIX workstation.

  • SQL Call Level Interface (CLI) server mode support

  • Additional locales, including but not limited to:
    • th_TH.TIS-620
    • Ja_JP.IBM-943
    • Zh_CN.GBK
    • Zh_TW.big5

  • Additional runtime APIs, including but not limited to:
    • mkfifo
    • mmap() and munmap()
    • mprotect()
    • msync()
    • recvmsg() and nrecvmsg()
    • sendmsg() and nsendmsg()
    • syslog()

  • Additional utilities, including but not limited to:
    • mkfifo
    • nohup
    • qsh (runs the OS/400 Qshell interpreter)
    • syslogd

  • version of AIX C++ runtime

  • version of AIX FORTRAN runtime

More information on OS/400 PASE can be found at:

http://www.redbooks.ibm.com (search on PASE)


IBM iSeries Information Center

Client/Server Support:

iSeries system resources are provided for client/server solutions via:

  • iSeries Support for Windows Network Neighborhood (iSeries NetServer)
  • Client Access Express for Windows
  • Integration for Windows Server

iSeries Support for Windows Network Neighborhood (iSeries NetServer):

The iSeries Support for Windows Network Neighborhood allows personal computers running Linux/Samba, Windows 95, Windows 98, Windows NT 4.0, and Windows 2000, Windows 2000 Terminal Server Edition, Windows XP, Windows Server 2003 software to seamlessly access data and printers managed by the iSeries or AS/400 system.

This support does not require any additional software to be loaded on the personal computer. It takes advantage of the native file sharing protocol delivered with Linux/Samba, Windows 95, Windows 98, Windows NT 4.0, and Windows 2000, Windows 2000 Terminal Server Edition, Windows XP, and Windows Server 2003. It does not require any software on the iSeries or AS/400 system other than the OS/400 operating system. The only prerequisites for this support are that the AS/400 system and the personal computer be configured with TCP/IP, and that the file sharing protocol on the personal computer be configured to use TCP/IP.

Any data available through the iSeries Integrated File System (including database, stream files, and CD-ROM) and any Output Queues on the iSeries or AS/400 system can be shared with the network by the iSeries or AS/400 system administrator. All administration of this function is through the iSeries iSeries Navigator program.

The AS/400 Support for Windows Network Neighborhood program complies with the "Common Internet File System" (CIFS) standard currently proposed by Microsoft.

V5R4 enhanced the scalability and performance of the iSeries NetServer. The server now supports running client connections in a single job using multiple threads. This provides for greater scalability and also improves the performance in most aspects of iSeries NetServer operation.

iSeries NetServer

iSeries NetServer can operate as the Logon Server for Windows clients. The iSeries can be used to authenticate logging onto Windows, provide the home directory, and logon scripts to the Windows user. Additionally, Windows user profiles including Desktop, Start Menu, Favorites, and policies can be stored and retrieved from an iSeries server. A Windows NT or Windows 2000 server is no longer needed in the network to provide these functions.

in V5R2, iSeries NetServer support using Kerberos version 5(v5) for user authentication. This allows for a seamless single signon configuration for iSeries NetServer clients.

iSeries has enhanced the allowable characters in a password and the length of a password to be more compatible with Windows. This helps customers who like to have their Windows and iSeries passwords match. AS/400 NetServer also provides support for the NTLMV2 password hash that the Windows PCs can be configured to use to provide better password protection on the network.

User IDs longer than 10 characters are truncated to 10 characters when checking for an iSeries user ID. A userid such as Administrator on Windows would be the same as ADMINISTRA on the iSeries. This should help compatibility between Windows and iSeries user IDs.

An iSeries NetServer Setup Wizard is part of iSeries Navigator that guides you through setting up your AS/400 NetServer based on the types of iSeries Access clients being used. This Setup Wizard also helps the user configure logon support.

iSeries NetServer supports access to files larger than 2 GB in the Integrated File System.

Client Access Express for Windows

In V5R4, Operations Console now supports the use of IOP-less Ethernet adapters. System models 520, 550, and 570 will use the provided embedded 1 GB Ethernet adapters. System model 595 may use the IOP-less 5706 and 5707 Ethernet adapters.

Client Access Express for Windows provides TCP/IP connectivity to users running Microsoft Windows 95, 98, Me, NT 4.0, and 2000. Client Access Express provides an all-inclusive client solution for accessing and using resources from your Windows desktop or from a Windows server. It includes 5250 emulation, access to DB2(R) Universal Database (TM) (UDB) for iSeries through its Data Transfer, and utilizes IBM iSeries Support for Windows Network Neighborhood (AS/400 NetServer) for working with the OS/400 Integrated File System and printers. It also has a variety of middleware, such as ODBC, for using and developing client applications to access OS/400 resources; and iSeries Navigator, the OS/400 GUI, for administering iSeries and AS/400e servers.

Client Access Express also includes PC5250 display and printer emulation and Data Transfer; however, those components can only be used if the iSeries Access Family product (5722-XW1) is installed on the iSeries server. The other functions of Client Access Express are included with OS/400.

Client Access Express for Windows

  • Runs on Windows 95, 98, Me, NT 4.0, NT 4.0 TSE, 2000
  • TCP/IP connectivity
  • Secure Sockets Layer (session encryption for the Internet)
  • Utilizes iSeries NetServer for File and Print serving
  • Middleware for PC-to-iSeries applications (ODBC, OLE DB, ActiveX)
  • iSeries and AS/400e server administration (iSeries Navigator, Management Central)
  • PC Network Administration (Policy Administration, Application Administration, silent install, auto-update PC code)

This Windows client is designed to take advantage of the latest technologies in the iSeries servers and Microsoft operating systems. Client Access Express (referred to as "Express client") uses the built- in functions of the Windows desktop to enable users to quickly and easily connect to iSeries servers, and also utilizes powerful iSeries functions, such as iSeries NetServer, to provide PC users network print and file serving capabilities. Some highlights of the Express client content are:

  • Runs on PCs having Microsoft Windows 2000, NT 4.0 (Workstation or Server), Me, 98, 95, and NT 4.0 Terminal Server Edition (TSE) operating systems installed. Refer to the following web page for further information on Windows 2000 and Windows Me support:

http://www.ibm.com/eserver/iseries/ clientaccess/win2000.htm

  • Supports TCP/IP connectivity

  • Provides enhanced network security through Secure Sockets Layer (SSL) for client functions

  • Utilizes iSeries NetServer for PC file serving and network print support

  • Contains client/server application enablers for iSeries and AS/400e servers (such as OLE DB provider, ODBC driver, ActiveX Automation Objects, Remote Command, and Data Queues)

  • Delivers the latest GUI for new OS/400 (R) functions through its iSeries Navigator function

  • Improves administration of PC users from a central iSeries server through Microsoft System Policy support and iSeries Navigator Application Administration

Many customers need PC alternatives that are easy to administer centrally (such as something that can be downloaded into a browser or JVM at each use, but can be maintained on the server). Client Access Express has central administration built into its design. When customers installed the previous Client Access clients, they probably did this by getting the Client Access PC CD-ROM (or creating diskettes) and going to each PC and installing the client code. Since the Express client is exploiting the capabilities of the iSeries NetServer, any PC running TCP/IP can directly connect to the folder in the iSeries file system where the Express client is installed and start the installation/migration from there. Furthermore, by combining the use of Client Access options (such as silent install, tailored install, CWBBACK, CWBREST), iSeries server administrators can set up the Express client, selecting only those functions they want their users to have; and then users simply make a TCP/IP connection to the server, start a command, and get the Express client installed on their PCs. And once Express is installed on a PC, it will periodically check the server to see if newer code (service packs or new releases) is in the Express folder; and if there is, it will automatically update the end user's PC. The Express client service pack PTFs can be applied to the Client Access Express install image. Then when users install Client Access Express from the server to the PC using iSeries NetServer, the Client Access Express product with the service pack included can be installed in one step. So although Client Access still ships a PC CD-ROM that contains the Express client software, the need for this PC CD-ROM for install is minimized.


The Express client supports TCP/IP connectivity and uses the standard TCP/IP program shipped with the Microsoft operating systems (other Winsock-compatible stacks can also be used). The Express client provides:

  • Simple communications setup. Simply select the Express client application you want to run, and then enter the iSeries server name you want to connect to and your user ID and password. The Express client then initiates a TCP/IP session, and the application is connected to the server.

  • Multiple user ID support using a single copy of Client Access. This is valuable when using the NT 4.0 server or Windows 2000 server in a multi-user environment, where each is using a different application.

Additionally, the following environments, which do not actually need Client Access installed on the user desktop, are also supported:

  • Microsoft Windows NT 4.0 Terminal Server Edition (TSE) and Windows 2000 Terminal Services: this environment enables the Windows NT or Windows 2000 server to be used as a gateway between end users and the server. This capability is particularly advantageous to Network Station (TM) users who would like to use iSeries Access functions such as PC5250 and ODBC. For detailed information on environments and functions supported, refer to Information APAR II11373 on the iSeries Access Web site.

  • Microsoft Windows 2000 Server and NT 4.0 Server with Microsoft Internet Information Server (or IIS). This support provides access to the DB2 UDB for iSeries from Web pages. For information on how to publish iSeries data on the Web from Microsoft's 2000 Server or NT Server running IIS using Active Server Pages (ASP), refer to the following Web site:

    http://www.ibm.com/eserver/iseries/ clientaccess/3tier/


The iSeries server is designed to protect its resources and data by requiring users to provide a valid user ID and password. The Express client uses TCP/IP Secure Sockets Layer (SSL) Version 3.0 to encrypt information sent between the iSeries server and the desktop. It also uses iSeries Server Authentication to assure connection to the intended server. SSL encrypts all information sent between the iSeries server and the desktop. The Express client offers the flexibility to choose what is encrypted. For example, you may want to encrypt data transmitted via Data Transfer but find it unnecessary to encrypt data sent to your PC printer via PC5250 printer emulation.

Use of SSL requires that one of the Client Encryption products, 5722-CE2 or 5722-CE3, be installed on the iSeries server, and then installed to the connected Client Access Express PCs.

Client Access Express supports the enhanced password rules, that were introduced in V5R1, allowing case sensitive user profile passwords up to 128 characters in length with a larger character set.

Network File and Print Serving

iSeries NetServer is being used to satisfy file and print serving needs for end users. iSeries NetServer unites Integrated File System (IFS) and iSeries printers into the Microsoft Network Neighborhood. User benefits include increased stability at startup and shutdown of the PC and better control of user visibility to resources. The only directories or printers that can be seen by end users are those set up as "shared" by an administrator or resource owner. NetServer allows the administrator or owner of a resource to control its visibility to end users. Creating a "share" enables viewing of that resource. If no share exists, users will not see the directories or printers.

Desktop users can fully satisfy their file and print serving needs through the iSeries NetServer function. Therefore, all the file and print serving functions that exist in the other iSeries Access clients are not included with the Express client. To use the iSeries NetServer, only the Client for Microsoft Networks (shipped with Microsoft operating systems) needs to be installed on the PC.

iSeries NetServer file and printer "shares" are easy to create, locate, and manage by using the iSeries Navigator printer list and file systems list. The current file shares can be listed separately to make it easy to quickly explore the contents of a file share or map a drive to it. File shares now support EBCDIC to ASCII conversion.

The AFP Workbench Viewer is also provided so iSeries spooled files (AFP and SCS) or PC files (such as GIF, TIFF, and JPEG formats) can be viewed directly by a PC user. The AFP Viewer provides many end-user productivity aids, such as ability to zoom in or search for specific portions of a stored document.

Central Administration of PC Users

Client Access Express was designed with administration in mind. iSeries administrators want to make PC installation easier, control which functions users may install, control which functions users may run, and be able to preconfigure Client Access connections so unskilled users do not need to do configuration. Client Access Express meets these needs by delivering:

Microsoft System Policy Support. Each time a PC is started, system policies are downloaded from a server to the PC and enforced through Microsoft System Policies. Client Access provides policy templates for use with the Microsoft System Policy Editor. Administrators can create, edit, and change policy information and could, for example:

  • Prevent a specific user from running the Client Access Data Transfer to upload or download data. Users can be restricted from creating a new file, but they can be allowed to append data to an existing file or allowed to use only predefined transfer requests. Additionally you could restrict users from running batch uploads/downloads, GUI uploads/downloads, autostart uploads/downloads, use of the Excel add-in, or restrict which server a request may be run against in networks with multiple iSeries servers

  • Restrict the use of iSeries Navigator

  • Limit the number of PC5250 sessions a user can start on a per server basis

  • Restrict ODBC driver or OLE DB usage on a per server basis

  • Disable users from changing their passwords or modifying the password expiration warning time frame

  • Preconfigure a user's iSeries server connectivity; then when the user starts a Client Access function, only preconfigured systems would be available for use

  • Define policies by connection environment. For example, when a user is connecting from the "home" environment, SSL is required. However when using an "office" environment, SSL is not needed.

Each time a PC is started, the system policies are downloaded from the server to the PC. Policy restrictions can be enforced on a per user or per PC basis. This function can be used with any supported OS/400 release.

iSeries Navigator Application Administration Operations Navigator provides an Application Administration function that can be used rather than Microsoft System Policies for administering the network. Whereas Microsoft System Policy restrictions are downloaded to the desktop and managed through the Microsoft Windows registry, Application Administration restrictions are maintained in the OS/400 user profile, and this customization then "roams" with the user. Administrators can identify--

  • which iSeries Navigator functions can be used
  • which first-level and most second-level folders can be accessed

and can control use of other applications registered to Operations Navigator, such as:

  • restrict or control usage of PC5250, Data Transfer, ODBC, OLE DB, and Remote Command functions similar to what is provided via System Policies.
  • restrict or control access to third-party plug-ins through Application Administration.

Each time a PC user connects to an iSeries server, Application Administration checks the OS/400 user profile to determine which Client Access functions can be used.

iSeries Server Administration and Operations - Operations Navigator and Management Central

iSeries Navigator

Features to improve ease of use and capability, include:

  • User-defined PEX (Performance Explorer) events including key server jobs used by e-business applications

  • Transaction management capability is added for B2B transactions

  • Synchronization of time across multiple servers for System Monitor graphing consistency

  • The ability to more easily verify a valid connection to the Management Central server and detect errors in configuration

  • Options for automatic restart of a monitor after system IPL and retry after connection error

  • Management Central functions are SSL enabled for highly secure transmissions

  • More fully featured drag and drop support in Management Central

  • Enhancements to the PTF management tools allow management of PTF groups across multiple iSeries systems

  • New work management functions such as system status

  • Database support such as Database Navigator and SQL Visual Explain is improved by using a new technology for better map layout and control, multiple databases on a system by using independent disk pools, and database transaction support to view DB transaction for a job, see a job associated with a transaction, and lock holders for an object and the transactions using the lock space.

  • Wizards to create logical partitions, IPv6 and IPv4 configuration, interfaces, and routes; and Enterprise Identity Mapping configuration

  • Support to run a Windows command on your Integrated xSeries Server

  • Enhancements to BRMS

  • In addition, system administrators can export and save partition configuration data to simplify the management and reconfiguration of partitioned servers

  • iSeries Navigator V5R2 contains new self-optimizing index advisors within Visual Explain, which provide advice on creating indexes and collection statistics for a given SQL query called Automatic Index Advisor

Systems management function delivered in V5R1 via easy-to-use iSeries Navigator GUI include:

  • Work management (Active jobs, subsystems, job queues, memory pools)

  • Backup and Recovery (BRMS GUI plug-in)

  • Logical Partitions (LPAR)

  • System values, including system comparison and update via Management Central

  • Distributed user/group administration via Management Central

  • Licensed program and fix creation, distribution, and installation via Management Central

  • Enhancements to performance monitors and collection services to graph extended time periods

  • Monitors and events for managing jobs and messages

  • Complete DASD management: Disk balancing, compression, management of disk pools, and units

  • Simple two-node cluster configuration

  • Integrated xSeries Server: Windows user/group and disk administration

  • Database Navigator gives you a pictorial view of the database showing the relationships between objects

  • Graphical command prompting

  • TaskPads, a user interface extension that allows easy access to key administrative tasks

Other ease-of-use initiatives for V5R1 include the addition of numerous GUI extensions to existing iSeries Navigator functions, the creation of numerous configuration and administration wizards (many of which are in the new GUI areas listed above), and a new iSeries Information Center -- online documentation available on the Web or CD.

Management Central-Pervasive

Management Central-Pervasive (MC-Pervasive) allows iSeries network administrators to keep an eye on their iSeries or AS/400 servers while they are away from their workstation or office. Using an internet capable cellular phone, PDA with a wireless modem, or a Web browser, administrators can monitor and manage their iSeries systems.

V5R1 enhancements for MC-Pervasive include:

  • Additional support for system performance monitoring

  • Monitor specific jobs and servers on multiple systems

  • Monitor message queues on multiple systems

  • Hold, release or end a job on any end point system

  • Run commands on any system or group of systems

  • Manage Integrated xSeries Servers
    • View status of Integrated xSeries servers
    • Startup/Shutdown of Integrated xSeries servers
    • Run Windows commands
    • Monitor Integrated xSeries events (routed to an iSeries message queue)

  • Read-only mode for selected users

These additional V5R1 enhancements are available via an English-only PTF. Customers interested in using Pervasive need to refer to the following IBM Web site to obtain the PTF numbers to load the code and MRI for Pervasive:

http://www.ibm.com/servers/eserver/ iseries/sftsol/pervasive.htm

iSeries Navigator is the graphical interface for administering and operating iSeries servers. Its highly productive and easy-to-use interface also simplifies the abilities of end users to work with iSeries resources. With each release of OS/400 you also see a release of iSeries Navigator as it continues to expand its capabilities to meet the needs of iSeries administrators and operators. For example:

  • Management Central allows easy management of multiple iSeries and AS/400e servers by sending single requests through one server acting as a central server. Management Central can be used to:
    • Collect performance data on iSeries servers in the network. This function can be scheduled to occur when most convenient for the customer, either as a one-time operation or regularly on set dates and times.
    • Distribute and install OS/400 software fixes (PTFs) throughout the network
    • Gather iSeries hardware and software inventory across the network and access it from the central server.
    • Execute commands on one or multiple systems with a single request.
    • Select objects in an OS/400 file system and create packages that can then be distributed to systems throughout the network, again with one request to a single system or groups of systems.
    • Manage distributed users and groups

  • Management Central is integrated into the main iSeries Navigator window. Similarly, utilities for defining, verifying, and changing iSeries server connections, formerly launched from the Client Access folder, are now available through iSeries Navigator.

  • Folders in the Integrated File System (IFS) can be created, deleted, and renamed. File system objects can be cut, copied, pasted, and dragged or dropped between servers and PCs. User Defined File Systems (UDFS) are also included.

  • iSeries Navigator also provides interfaces to work with large objects (LOBs) in the database, use the DATALINK data type to extend the types of data that can exist in the database, and create user- defined SQL functions

  • Support is also provided for creating procedures, managing SQL indexes, and capturing and viewing SQL performance information. A utility for running SQL statements on the iSeries server is significantly enhanced to allow sets of statements to be easily entered, run, and saved as SQL script documents.

  • iSeries Navigator provides the graphical interface for iSeries TCP/IP capabilities. Virtual Private Networks (VPN) can be set up for secure connections across a public network. Point-to-Point configuration is enhanced to support ISDN and L2TP.

  • Selected server software can run in customer-defined subsystems. In addition a simplified interface for working with server jobs has been provided.

  • The plug-in support allows anyone to extend their capabilities. Plug-ins can be written in Java (TM) or Visual Basic. Additional enhancements have been made for plug-ins to attach anywhere in the iSeries Navigator function tree and be controlled by Application Administration.

  • Work Management - view and manage active jobs, subsystems, job queues, memory pools

  • DASD Management - through iSeries Navigator users can view and manipulate large DASD configurations. This includes the ability to view subsets of all disk units, view disk units in a physical and logical hierarchical layout, and sort the disk units by various criteria such as size, resource name, or associated controller. Performing disk maintenance, such as adding and replacing disk units, has been simplified as iSeries Navigator provides wizards to do these tasks

  • Working with DB2 UDB for iSeries
    • Database Navigator gives a pictorial view of the database showing the relationship between objects.
    • Visual Explain provides a pictorial view of query optimization, and allows users to easily get information for improving query performance.
    • Display currently executing SQL statements for a job.
    • Tables, views, and indexes have a description window which displays, and in some cases allows changing, the attributes of these important objects.

  • Integrated xSeries Server Administration. The Integrated xSeries Server can be managed through the iSeries Navigator. These Windows servers can be stopped, started, changed, and listed to view their status, and their attributes can be managed.

iSeries Navigator - V5R3

Tasks from the Web

  • Access core systems management tasks from your browser

  • Access multiple systems through one iSeries from a Web browser

  • Embed these tasks into your Web applications

Management Central

  • Management Central has made significant enhancements that enable you to manage many more endpoints simultaneously from a V5R3 central management server. Improvements in scale can be seen with pre-V5R3 endpoints talking to a V5R3 management server. Although, you will see the best results when running V5R3 on both the server and the end point systems. Greatest improvements in scale can be seen where large amounts of data is being transferred, such as inventory collection or fix distribution.

  • Management Central central servers can now be made highly available in V5R3. For customers working with a High Availability Business Partner, Management Central data, and objects on the central server can be managed for high availability along with other cluster proven data and solutions.

  • Synchronize functions

    • Key functions, such as EIM and Kerberos, can be synchronized across a group of end point systems.

  • Collection Services categories

    • Two categories were added to the Data to Collect dialog: one for cross-partition data and another one for data port services data.

  • New System Monitor properties fields

    • Fields related to multipath disk units and remotely mirrored independent auxiliary storage pools are added to these System Monitor metrics: Disk Arm Utilization (Average), Disk Arm Utilization (Maximum), Disk Storage (Average), and Disk Storage (Maximum).

    • New method for calculating CPU utilization in partitions

  • Electronic Service Agent is integrated into the base OS/400 operating system


Windows Administration

  • Support to start and shut down for Linux servers in logical partitions

  • Support to create, delete, link, and unlink disk drives for Linux servers in logical partitions

  • Additional properties for integrated Windows servers

  • View information for Windows disk drive volumes

  • Support Windows and Linux disk drive maximum size of 1,000 GB

  • Allow enrolled OS/400 users to have a different name on Windows than on OS/400

Directory Service

  • Administer the directory server from one common Web GUI

  • The Performance property page allows you to specify cache settings for the server

  • New Password property page security enhancements

  • The Connect to Directory Server Kerberos authentication

  • Search property page allows you to control sorted/paged search results, restricts access to ACL attributes on entries


  • Configure an SNTP server to use your iSeries for time synchronization across your network

iSeries NetServer

  • The General > Next Start property page allows you to select both encrypted passwords and Kerberos V5 as the authentication method

Enterprise Identity Mapping (EIM)

  • Work with digital certificates as a type of user identity

  • EIM now has mapping policy support for defining many-to-one mappings through policy associations

  • EIM now enables you to test your EIM mappings

Configuration and Service

  • Additional System Values

    • Auditing, Date and Time, Jobs, Performance, Security, Save and Restore

  • Time Management

    • From the Time Management function, you can manage time zones and adjust system time

  • Disk Management

    • Configure and manage geographic mirroring for independent disk pools.

    • Print the Graphical View for records and reference.

    • Optimize parity sets for availability.

    • Retrieve disk unit logs to gather information about specific disk units.

    • View multipath disk unit connections from several input/output processors on an iSeries server to a single disk unit in the Enterprise Storage Server.


  • Enhanced usability through restructured views -- objects are now organized by container for convenient access

  • Table reorganization is enhanced to allow suspending and resuming a table reorganization as well as viewing the progress of the reorganization

  • Management of check pending constraints is improved with the ability to directly repair object in check pending status from iSeries Navigator

  • Manage the relational database directory of remote databases

  • Run SQL Scripts allows launch of the iSeries Graphical Debugger to debug stored procedures and allow font selection while editing

  • Visually explain customization for SQL Query Engine (SQE)

  • GUI support is added for the new DB2 UDB for iSeries function, including items such as creation of Partitioned tables and Sequence Objects

Integrated File System

  • New security page

    • Sets scanning settings for objects created in files and folders. Also specifies auditing value, change options, user ID, and primary group ID.

  • Ability to make objects savable

  • Ability to set objects created in a folder to be scanned

  • Restrict rename and unlink

  • User Defined File Systems (UDFS) enhancements
    • Setting objects to be scanned
    • Restricting rename and unlink
    • Specify a default file format for UDFS
    • User and group ID settings can now be changed on a mounted UDFS

Intelligent Agents

Intelligent Agents provide system administrators with an easy way to manage many Agent Building and Learning Environment (ABLE) agents running on different systems. This includes:

  • An agent framework for building agents that enable autonomic computing

  • A standards-based, scalable agent platform with security and other agent services

  • An administrative console for managing deployed agents

AFP Manager

Extended capabilities

  • Intelligent routing lets you specify any combination of stream file, spooled file, or e-mail for the PDF output files.

  • Respool the input file (or a segment of the input file) as AFP for print or fax.

  • Specify a PDF administrator to receive e-mailed failure messages with the PDF file attached for simplified reprocessing.

  • Encryption options for the e-mailed PDF.

  • PDF mapping objects let you access functions that require a mapping program without having to write a program.

Backup and BRMS

  • Restore printer output and archive objects

  • Perform a fully automated backup in BRMS

  • New Global Policy Properties for maintenance, retrieval, and network options

  • Manage your BRMS devices -- any stand-alone devices, media libraries, and Tivoli Storage Manager (TSM) servers used by BRMS

  • A new Reclaim wizard enables you to reclaim old fragmented tape volumes and make them usable again

  • View or save selected BRMS reports in HTML

  • Backup policy now allows omits of folders, libraries, and library objects

  • Enhanced search of backup history

Advanced Job Scheduler

  • Advanced Job Scheduler for Wireless -- Work with Advanced Job Scheduler using a wireless device such as a PDA

  • Automatically notify a specified recipient via e-mail and attach printer output in PDF format to e-mail messages

  • New job properties

    • Local data area

    • Command step

    • Create and work with job documentation

  • New Advanced Job Scheduler properties

    • Fiscal calendar

    • Data libraries

    • Skip count feature

    • Multiple scheduling environments

    • Skip dependency

    • Monitor jobs not started within time limit

    • Report distribution

Usability Enhancements

  • Choose to automatically open task results window when starting a task

  • Connection status dialog for connecting to the central system

  • Ability to edit IP address of endpoint system

  • Auto reset your file and message monitors after a command is run

  • Exporting inventory to a new format type to support Unicode

  • Performance advisor designed to help determine why you're experiencing slow performance

  • More complete search results when searching for users across systems

  • Copy from Media enhancement allowing concurrent copying from different systems

  • Printer Output and Messages folder now include many usability enhancements

  • TCP/IP Enhancements

    • Enhancements to SNTP and SMTP server support

    • Addition of CIMOM server support

    • Addition of significant new Quality of Service (QoS) function

    • eCare connectivity enhancements (for setting up connection to IBM support)

Operations Console

Operations Console is Windows-based communications software that provides a single connectivity solution for all platform management applications including legacy 5250 console support, a remote control panel GUI, and iSeries Navigator/Management Central. Connectivity choices include null-modem, cable-connected async communications, dial-up async communications, and Ethernet/Token-Ring Local Area Networking with V5R1. Additional features include:

  • A simplified setup and configuration process that checks PC software requisites and troubleshoots connectivity problems

  • Remote "Virtual" control panels for LPAR secondary partitions

  • Enhanced security model with data encryption and PC device authentication for LAN environments

PC5250 supports the LAN connectivity option of Operations Console and supports a version of SSL implemented by Operations Console that supports device authentication, but without the use of certificates.

Operations Console on V5R2

The Model 825 has an integrated Ethernet port.

In V5R2, Operations Console can utilize this through LAN connectivity. If you choose this connectivity type, connect your Operations Console PC to the integrated Ethernet port -- no confusion on where to plug in the console.

The remote control panel function is re-introduced in V5R2. The parallel port cable was withdrawn from marketing in mid-2002, but due to popular demand, a new and improved cable and software brings back this function. The software will be available via PTFs and a new V5R2 iSeries Access for Windows service pack.

The new Remote Control Panel parallel port cable is supported only with the V5R2 version of iSeries Access for Windows running on the Operations Console PC. Both V5R1 and V5R2 versions of OS/400 are supported. If you are using V5R1 of OS/400, you may not have the V5R2 version of iSeries Access for Windows.

These functions are available in V5R2 and only require the hardware to work. For additional information refer to:


V5R4 iSeries Access and Operations Console

iSeries Access for Windows, which includes the iSeries Navigator and Operations Console functions, now also runs on AMD 64-bit and Intel Extended Memory 64 Technology (EMT64T) processors. For Operations Console, IOPLess LAN support means that the system console can now plug into an integrated port on the System i5 product. Additional IOAs, and in some cases additional IOPs, are no longer required, saving slots for other purposes. Enhancements are also made to the ODBC, OLE DB, and .NET providers.

Operations Console - V5R3

  • A new function consisting of control panel functions 65 and 21 aids in the recovery or debug of Operations Console problems. The user can:

    • Change the console mode value (between twinax, direct-attach Operations Console, LAN-attach Operations Console, and HMC).

    • Clear the LAN adapter's associated data used for Operations Console or the service tools server.

    • Deactivate and reactivate the LAN adapter associated data used for Operations Console or the service tools server.

    • Dump all the flight recorders commonly associated with Operations Console. This includes the ability to dump information from other partitions for use by the primary partition console.

All of the above functions can also be done on an SST screen via native macro.

Remote Control Panel (RCP) can now be connected directly to secondary partition (previously, it had to connect through the primary). However, the RCP cannot be used to power on a partition from a powered- off state when used in this way.

Operations Console enhancements:

  • If Operations Console fails (that is, temporary network error), the console is activated with no action required by the administrator.

  • An administrator can identify which PC currently controls the console.

  • The administrator can take away control of the console from another PC.

  • The console type is always enforced (if choosing LAN, only LAN is used for console).

  • If console type is not set, the user is prompted to set it.

  • Restrict console adapters to specific slots to control which PC will be the console

  • Option to do Ops Console server configuration through SST (not just through DST).

  • LAN connected RCP has an SRC history option so that past SRCs can be viewed through the RCP.

The use of Universal Serial Bus (USB)-to-serial adapter support is added to the Operations Console. The adapter can be placed between the console's serial cable, at the PC end, and the PC's USB port, instead of the console cable going to a serial port. For restrictions, refer to the InfoCenter articles on Operations Console.

Application Enablement

To assist programmers in the development of client/server applications, Client Access is positioned as the application enablement middleware for PC-to-iSeries programming. A variety of key enablers is provided for accessing iSeries resources, such as:

  • ODBC Driver -- an industry-standard database access interface for Windows users which provides SQL access to iSeries database information. The ODBC Driver supports the Microsoft ODBC 3.5 Specification.

  • OLE DB Provider -- OLE DB is part of Microsoft's universal data access standard for Windows users. OLE DB is defined as a multi-platform access method for relational and non-relational data. iSeries Access provides an OLE DB provider (driver), so any client/server application written to this interface can be used to access iSeries resources. The OLE DB provider can be used for record level, SQL calls, Data queues, Remote commands, Stored procedures, CL Commands, and Distributed program calls.

  • ActiveX automation objects -- are designed for developing client/server applications between the PC and the iSeries server. Objects are provided for working with iSeries servers using iSeries Access data queues, remote commands, and distributed program calls. Many popular client languages, such as Visual Basic, Delphi, PowerBuilder, and Visual C++ support ActiveX automation objects. Data manipulation objects are also included to make it easy to handle code page conversions. Online help (including example code) is provided and can be accessed from object browsers. New in V5R1 is Data Transfer ActiveX support.

  • IBM Toolbox for Java -- includes a series of low-level APIs for accessing iSeries data and resources from a Java program. It also includes a set of GUI classes to present iSeries data to the user from a Java program. The GUI classes use the Java Swing 1.0 (JFC 1.1) framework. The Toolbox for Java is a separately installable option of Client Access install. Once installed through iSeries Access, future updates to the Toolbox for Java will be delivered to PC users through iSeries Access service packs.

  • A Client Access Express Toolkit. The Toolkit help file contains useful links to PC files and Web sites where sample programs, documentation, headers, libraries, and a variety of sample programs are provided using Visual Basic, Delphi, PowerBuilder, Visual C++, Lotus 1-2-3 (R), and Internet Explorer, so programmers can easily start building applications using the Express client APIs. The Express toolkit is delivered as an optionally installable component of Client Access Express.

National Languages

iSeries Access supports multilingual environments, which means individual users can use different languages (provided those languages, are installed on the iSeries server). Additionally a configuration option is provided which allows users to override the default keyboard and translation defaults that do not meet their needs.

DBCS-specific Support

  • Client Access can support both PC and PS/55 workstations concurrently on a single iSeries server when the primary language is DBCS.

  • When iSeries Access is used with English DBCS Machine Readable Information (MRI), the user can input or output user data in Chinese, Korean, or Japanese. The character sets that can be used in user data is determined by the PC used. DBCS and Katakana characters are not supported for folder and document names.

  • The iSeries Access Family supports both IBM DBCS PC code page and National Industry DBCS PC code page for China, Taiwan and Korea.

    • The People's Republic of China National Standard graphic character set (GB) is supported. Users of iSeries Access Family may select either code page dependent upon the code page supported on the client PC.

    • Taiwan Industry Standard graphic character set (Big-5) is supported. Users of iSeries Access may select either code page dependent upon the code page supported on the client PC.

    • Republic of Korea National Standard graphic character set (KS) is supported. Users of iSeries Access may select either code page dependent upon the code page supported on the client PC.

For more details, refer to the iSeries Access Web site at



  • The Client Access Express Toolkit is provided "as is".

Packaging and Ordering

For information on what is delivered with iSeries Access Family orders and the OS/400, refer to the following web page:

http://www.ibm.com/eserver/iseries/clientaccess/ packaging.htm

For information on how to acquire the latest versions of the clients or the Client Access Family, refer to the following web page:

http://www.ibm.com/eserver/iseries/ clientaccess/caorder.htm

The V5R1 Client Access Express Setup Guide (SC41-5507) is available on the PC-CD ROM which contains the Express client software. The PC-CD ROM is entitled "iSeries Setup and Operations".

Windows Server Integration Enhancements(V5R1)

iSeries is enhanced with additional Windows server integration facilities. These enhancements enable iSeries to support larger and more complex Windows applications and offer additional tools to help reduce the cost of managing Windows server environments.

Attachment of N-Way xSeries Servers

iSeries supports the attachment of n-way xSeries servers via the High Speed Link. With the Integrated xSeries Adapter, selected xSeries servers running Windows 2000 Server can be utilized to extend Windows application scalability, while retaining the storage consolidation and systems management advantages of the Integrated xSeries Server.

Enhanced Hardware Support

Enhancements for the Integrated xSeries Server includes support for up to 32 servers on selected iSeries models, support for the 1 Gb Ethernet LAN adapter, and support for the iSeries DVD device.

iSeries Navigator Support for Windows Disk and User Management: Additional facilities have been added to Operations Navigator for managing Integrated xSeries Servers and xSeries servers directly attached to iSeries via the Integrated xSeries Adapter. In addition to server management, iSeries Navigator supports disk and user management for these Windows servers. Enhancements include the capability to create, delete, copy, link, unlink, and show status for Windows server disks. Administrators can also manage OS/400 user profiles that are enrolled into a Windows server environment.

Increased Storage Capacity and Availability

iSeries storage area network support for Windows servers has also been enhanced. For Windows 2000 Servers, the number of storage spaces that can be defined has increased from a maximum of 16 to 32. With a storage space supporting up to 64 GB of disk, each Windows server can access approximately 2 TB of disk space. Up to 16 of these storage spaces can be added without requiring a shut down of Windows 2000 Server.

Improved Availability via Independent Auxiliary Storage Pools (IASPs)

With the introduction of IASPs, additional availability options are available for the integrated Windows environments. Since the Windows operating system and data can be installed in an IASP, the storage spaces associated with Integrated xSeries Servers or direct attached xSeries servers can be switched to another iSeries server with a duplicate hardware environment.

For more information, refer to Hardware Announcements dated April 23, 2001.

Integration for Windows Server:

iSeries Windows Integration

iSeries Integrated xSeries Server and Integrated xSeries Adapter offerings support Virtual Ethernet LAN, Microsoft Cluster Services, and Automatic Cartridge Loader support.

With this release, new xSeries models are now supported using the Integrated xSeries Adapter. For the latest information on supported models, see:

http://www-1.ibm.com/servers/eserver/iseries/ windowsintegration/

The iSeries Virtual Ethernet LAN introduced in V5R1 to enable high- speed communications between OS/400 and Linux partitions within the iSeries server is extended to support Integrated xSeries Servers and xSeries servers attached with Integrated xSeries Adapters. With this support, Windows servers can communicate with each other and with OS/400 and Linux partitions over the fast, more secure, and reliable Virtual Ethernet LANs.

iSeries Windows integration supports the Microsoft Cluster Services. With the clustering support provided in Windows 2000 Advanced Server, two Integrated xSeries Server or two xSeries servers attached with Integrated xSeries Adapters can form a cluster and utilize the sixteen new shared storage spaces available with V5R2. In the cluster environment, if there is an outage on one of the Windows servers, the storage spaces can be switched to the second Windows server and the applications can be automatically restarted to reduce the length of the system outage.

Customers who have systems with large amounts of data often have Auto Cartridge Loader (ACL) tape devices (3570, 3580, and 3590) with the ability to automatically load another tape cartridge. Support is now added in the Windows integration support to handle commands for ACLs. Multiple tape cartridges can be accessed during backup/restore operations initiated from the Windows

The software previously included in OS/400 option 29, Integration with Windows NT Server, is shipped automatically with OS/400, and is titled: Integration for Windows Server. When a system upgrade occurs, this program will be installed automatically in AS/400s that currently have OS/400 option 29 installed. Option 29 will be deleted when the system upgrade occurs.

AS/400 Integration for Windows Server contains a base program with two options to allow an iSeries with multiple Integrated xSeries Servers installed to have a combination of servers with either Windows NT Version 4.0 or Microsoft Windows 2000.

  • Option 1 contains the support for Integrated xSeries Servers to run:
    • Microsoft Windows NT Server Version 4.0
    • Microsoft Windows NT Server Terminal Server Edition Version 4.0.

  • Option 2 contains the support for the Integrated xSeries Server to run:
    • Microsoft Windows 2000 Server and Terminal Server Services.

iSeries Windows Integration - V5R3

The IBM iSeries Integrated xSeries Server and Integrated xSeries Adapter offerings support larger virtual disk drives and allow users who are enrolled from OS/400 to Windows to take advantage of Enterprise Identity Mapping (EIM).

The virtual disk drive support is enhanced to increase the maximum size of a single virtual disk drive from 64 GB to 1000 GB. This allows Windows servers to have disk volumes over 64 GB without needing to create volume sets that span multiple disk drives. The maximum total amount of disk capacity that can be allocated to a non-clustered Windows server has increased from 2 TB to 32 TB. For a server that uses Microsoft Clustering Service, the maximum disk capacity has increased from 3 TB to 48 TB.

Users enrolled to the Windows environment from OS/400 can now take advantage of EIM. User enrollment support for EIM allows easier setup for Windows single sign-on and allows enrolled OS/400 user profiles to be different than Windows users profiles. In addition, enrolled users can now manage their Windows passwords in Windows. These enhancements allow more flexibility in managing user accounts enrolled from OS/400 to Windows.

For the latest information on iSeries Windows integration, refer to

http://www.ibm.com/servers/eserver/ iseries/windowsintegration/

Integrated Save/Restore of Windows Files from AS/400

The save and restore capabilities of Windows servers are enhanced to enable individual file backup and recovery through the AS/400. The support is enabled through the AS/400 NetClient file system (QNTC) of the Integrated File System. The function enables customers to incorporate incremental saving of files and the Windows registry associated with an Integrated Netfinity Server into their existing AS/400 backup procedures. In addition, the registry and files saved through this method can be individually restored if needed. Saving of Windows server files in this manner can be used with full AS/400 system save procedures for disaster recovery.

iSeries Navigator Support for Windows Server Management

iSeries Navigator, the GUI for managing the AS/400, is enhanced to manage Windows servers installed on Integrated xSeries Servers. The capability has been added to start, stop, and display the status and properties of the server, which is installed with either Windows NT Version 4.0 or Windows 2000.

Increased Drive Size

AS/400 storage available to the Integrated Netfinity Server is increased from 8 GB per drive to 64 GB per drive. The system drive remains at a maximum of 8 GB. The increase in storage size enables almost 1 TB of storage available per Windows server.

System Drive Installation

The Windows server installation has been enhanced to enable the system disk to reside on the C drive. The change was made to conform more closely with other PC server implementations of Windows servers.

Shared LAN Adapter Support Not Available

For the AS/400e servers 8xx, 270, SB2, and SB3, LAN adapters can no longer be shared between AS/400 and Windows servers on the Integrated Netfinity Servers on AS/400. AS/400 and the Integrated Netfinity Server each require their own LAN adapters if LAN connectivity is required for both environments.

Integrated Netfinity Server Hardware

The new Integrated Netfinity Server for AS/400 includes an Intel 700 MHz Pentium III processor and support for up to 4 GB of memory. The faster processor and increased memory capacity provide increased performance and capacity for Windows applications. This version of the Integrated Netfinity Server is supported on the AS/400e 8xx, 270, SB2, and SB3 servers.

AS/400 Client Access Connectivity via X.25 PAD:

This is an attractive solution for customers using X.25 Packet Assembler / Disassembler (PAD) switching with large numbers of individual remote geographically dispersed PCs, who need to connect to the AS/400 system for terminal emulation or file transfer/mail type of functions. Many customers choose X.25 as their WAN connectivity solution of choice due to tariffing costs and the stability of the X.25 network technology and standards. With X.25 the system administrator can manage concurrent remote PCs via a single X.25 line versus many ASCII controllers/lines/modems. This reduces customer cabling complexity and external modem management while providing the additional error recovery built into an X.25 network.

X.25 PAD, together with AS/400 Client Access, offers the data reliability of SNA, the connectivity, flexibility, and availability of X.25 networking, along with all of the functional capabilities of AS/400 iSeries Access Family.

iSeries Access for Wireless

Increase your business productivity without spending more time in the office or at the desk. Wireless access to administration functions and business solutions can help. This product supports administration of OS/400 and application development for intended wireless devices such as personal digital assistants (PDA) and Internet-enabled phones. New, consistent branding and consolidation of development tools exist for creating wireless solutions.

iSeries Access for Wireless includes:

  • An OS/400 administrator interface, previously called Management Central-Pervasive, is enhanced and consolidated as part of iSeries Navigator.

  • The IBM Toolbox for Java 2 Micro Edition is used by developers to rapidly develop Java applications to access iSeries data and resources. This micro edition extends its capabilities to wireless devices. This edition also includes the Java Data Base Connection (JDBC) driver to access DB2 UDB for iSeries.

Through simplified yet highly secure access to information and function, iSeries Access for Wireless provides what you need to make your workforce truly mobile.

Integrated DB2 Universal Database for iSeries

DB2 Universal Database (UDB) for iSeries is fully integrated into the OS/400 operating system software. It is not a separate product. DB2 UDB for iSeries offers state of the art database functions and open-systems, standards based technology, while providing the maturity, stability, and ease of use that has become the trademark of the iSeries system.

DB2 UDB for iSeries can be used for both transaction processing and complex decision support applications. Advanced parallel processing and advanced query optimization techniques support queries of large decision support databases for applications such as business-to-business, Business Intelligence, CRM, and other e-business applications.

An integrated iSeries database offers many advantages. As an integrated part of OS/400, DB2 UDB for iSeries is installed with the system providing automatic bring up and recovery functions when the system is IPLed. Integration also allows the database commands and user interfaces to have a look and feel that is consistent with the rest of the system. For example, database objects are automatically included as part of the system-wide cross reference facilities and the basic system administration commands and graphical user interfaces for save, restore, security, and object management can be used to administer the database. This allows the database to exploit new system functions and hardware for improved availability, recovery, security, concurrency, and performance as they are introduced.

The database also takes advantage of the unique capabilities of the iSeries system such as single-level storage and the object-based design. This means administrators don't need to review table space allocations and extents, rebind applications for database changes, update statistics, or balance indexes. Such tasks are automatically performed by the databases.

Conformance to industry database standards, advanced functions, and distributed data capabilities with supporting performance allows DB2 UDB for iSeries to operate equally well with centralized database applications, or as the database server in complex heterogeneous client/server networks. DB2 UDB for iSeries' unique combination of function and reliability make the AS/400 the ideal database server for many customers' needs.

DB2 UDB for iSeries Enhancements (V5R1)

  • Improved distributed database support. DRDA running over TCP/IP allows transactions, which span databases, to be committed or rolled back by using two-phase commit protocols. Another key DRDA enhancement is the ability to return multiple result sets from iSeries servers to clients for improved performance.

  • Enhancements to move more business logic into the database. Triggers can be written in the SQL language. SQL triggers can be specified at the column, row, and statement level. The number of triggers allowed on a single table, whether written in SQL or a high-level language, is increased to 300. Triggers on read or fetch actions have also been added. Triggers can also be suspended. In addition, user-defined functions can be written in Java and the SQL built-in functions TIMESTAMPDIFF, PI, SPACE, GRAPHIC, MIDNIGHT_SECONDS, JULIAN_DAY, DAYOFWEEK_ISO, and WEEK_ISO are added.

  • Improvements in query support are added. Join operators are enhanced by the addition of RIGHT OUTER JOIN and RIGHT EXCEPTION. Scalar subselects, subselects that return a single column for a single row, can also be specified in the select list.

  • iSeries Navigator is enhanced with a Database Navigator interface that displays the relationship among relational objects such as tables, views, and indexes. Another enhancement to the iSeries Navigator interface is the ability to generate the SQL statements used to create a database object regardless if it was created with SQL or not.

  • Data definition language (DDL) is also enhanced. A new LIKE clause on CREATE TABLE provides a way to create a table with column definitions like another table or tables. New journal entries are added in V5R1 for DDL operations enabling third-party code to use these entries to replay DDL operations.

  • The maximum size of large objects stored in a column is increased from 15 MB to 2 GB and the maximum total size for all large objects for a table row is increased from 1.5 MB to 3.5 GB. The size of a single non-distributed table is also increased to 1 TB. In addition, DB2 UDB for iSeries supports the ability to optionally minimize the size of journal entries.

  • For B2B between iSeries and Microsoft Windows clients, the ODBC driver for DB2 UDB for iSeries is enhanced with ODBC 3.5 support and support for Microsoft Transaction Server (MTS). MTS support enables DB2 UDB for iSeries to participate in transactions involving two-phase commit coordinated through MTS. ODBC 3.5 support also delivers support for Unicode.

  • Performance enhancements to DB2 UDB for iSeries were also added for V5R1.

    • The maximum number of rows that should be returned by a query can be specified.

    • Optimization of queries involving more than 32 files is improved.

    • Pattern and escape character on a LIKE predicate can be specified as expressions and they no longer are a cause for making an open data path (ODP) for a cursor nonreusable.

    • Estimates of key ranges are cached to improve query optimization time.

Description of DB2 Universal Database for iSeries:

Independent Databases

Support for independent DB2 UDB for iSeries databases via Independent Auxiliary Storage Pools, or IASP, gives you additional availability and server consolidation options. Multiple DB2 UDB for iSeries databases within a single instance of the operating system allows for application flexibility and server consolidation by providing separate named database spaces. For instance, a company could have each of its regions share the same applications on a single instance of OS/400, each with their own copy of the DB2 UDB for iSeries schemas (libraries). Each region sees only the database objects for that region. Different users on the same system can connect to the appropriate database for their region. Independent Switchable databases enable access to your data during scheduled and unscheduled downtime without requiring redundant data collection.

DB2 UDB for iSeries Standards Support

V5R2 furthers DB2 UDB for iSeries' position in support of many industry standards and DB2 UDB for iSeries family compatibility. Benefits include:

  • More application and tool availability
  • Easier application or database portability
  • Improved interconnectivity to many different platforms/databases
  • Better use of available skills in the workforce

In addition to the traditional database interface and language support, DB2 UDB for iSeries provides a robust SQL-based database required by today's Enterprise Application Systems while leveraging the strengths of the IBM eServer iSeries.

Additional enhancements in V5R2 make it easier for you to transition from traditional database interfaces to the SQL world. A unique advantage for iSeries customers is that you can choose from a mixed environment of traditional and SQL facilities based on requirements, skills, or existing applications.

Query optimization technology within DB2 UDB for iSeries is improved in V5R2 to deliver improved performance in certain query/SQL environments.

Industry Standard and DB2 UDB for iSeries Family SQL Enhancements in V5R2

  • JDBC 3.0 (JDK 1.4)
  • The Open Group's Distributed Transaction Processing: The XA Specification
  • JTA (Java Transaction API) 1.0.1
  • ODBC and JDBC drivers for Linux
  • User-Defined Table functions
  • Savepoints
  • Common Catalog Views
  • UNION in Views
  • IDENTITY columns and ROWIDs
  • CREATE TABLE AS (subselect) (support in SQL equivalent to DDS Field Reference)
  • SQL Source Code Debugger
  • Additional SQL Enhancements in conformance with the ISO and ANSI SQL Core Standard

DB2 UDB for iSeries - V5R3

In an on demand world, standards and globalization are important for integration and openness. Application portability through standards and the flexibility to access the database via numerous client interfaces from Linux partitions and Windows systems allows both the application provider and the customer with the most flexibility possible.

DB2 UDB for iSeries embodies that flexibility through the support of its traditional database interface along with enhancing the SQL-based database required by today's Enterprise Application Systems. Enhancements to the RPG SQL Pre-compiler help customers and ISVs to more easily make use of both interfaces.

Enhancements that promote globalization and portability through adherence to standards:

  • UTF-8 and UTF-16 support within the database
  • SEQUENCE Object support enabled DB2 to handle key value (eg, order id) generation on behalf of your application
  • EXCEPT/INTERSECT SQL set operators
  • New BINARY/VARBINARY data type support
  • More robust error handling with GET DIAGNOSTICS SQL statement
  • Encryption capabilities enhanced with DB2 Family Column Encryption functions
  • Native Microsoft .NET provider
  • CLI Column-wise binding
  • Materialized Query Tables (MQTs) are available as a technology preview with the ability to create and refresh MQTs
  • Additional SQL enhancements that satisfy ISO and ANSI standards

Performance improvements to DB2 UDB for iSeries include the following:

  • Parallel Concurrent table reorganize
  • SQL Query Engine enhancements with performance improvements on a variety of customer queries, typically longer complex queries with attributes such as subqueries, views, common table expressions and derived tables
  • Star Join enhancements
  • Faster SQL Deletes
  • Faster Stored Procedure Call Processing as a result of enhanced job level caching
  • OnDemand Stats Generation

Server consolidation and enterprise growth are improved by increasing limits on the system and providing additional Migration Toolkits for moving data and queries from other databases. Examples of increased limits:

  • 1.7 TB Tables
  • Partitioned Table support
  • Larger decimal precision
  • 256 tables (members) in a view

Integrated File System

Enhanced data management and performance for the Integrated File System is rolled out with a new directory implementation that provides significantly enhanced directory performance, scalability, robustness, and recoverability. That, combined with the journaling and improved caching techniques, provides the system with a faster, safer, more reliable file system.

Note that the Integrated File System directory enhancements are available in V5R1 and will ship when ready. Watch for APAR II13161 at:


  • Relational Model

    DB2 UDB for iSeries is a relational database by design but may be viewed by users in terms of either a relational model or a file model, depending on choice of interface. Those choosing the relational model see tables and views while those using the file model see physical and logical files. The data resides in tables or physical files but may be seen in different sequences, with omissions or additions in logical views. Productivity of doing program maintenance is increased because programs that use a logical view of the data need not change when the physical data is updated.

  • File-and database-oriented interfaces

    The same copy of data may be shared by applications using file and database interfaces. This data sharing, along with the data mapping features of views and logical files, reduces the need for redundant copies of data.

  • Structured Query Language (SQL) standards conformance

    Supplies the industry standard database access language for consistent data access across heterogeneous platforms, conforming to the IBM, ANSI X3.135.1999, ISO 9075-1999, FIPS 127-2, JIS, and the Open Group SQL standards. Support is provided for embedded static, dynamic, and extended dynamic SQL. ANSI-and ISO-defined SQL procedures are also supported.

  • Large object support

    DB2 UDB for iSeries can store and manipulate data fields up to 2 GB. The maximum size for all LOB columns in a row is 3.5 GB. With its LOB support, you can look to DB2 UDB for iSeries as a platform for building applications that hold new data such as very large text, image, and audio.

  • DATALINK data type

    The DATALINK data type extends the types of data that can be stored in database files. The actual data stored in the column is only a pointer to the object such as an image file, a voice recording, or a text file. The method used for resolving to the object is to store a uniform resource locator (URL). This means that a row in a table can be used to contain information about the object in traditional data types, and the object itself can be referenced using the DATALINK data type.

    Datalinks also allow the referenced object to be "linked" to the database to prevent modification or deletion of the object while it is linked to the database file. This relationship is maintained by having the database interact with the file system that contains the object.

  • User-defined types

    User-defined types are derived from existing predefined types such as integer and character. You can create your own types for strong typing and creating functions for different types. You can call a function for each row of a result set and return a value based on the user-defined type.

  • User-defined functions

    You can define your own functions to use within SQL itself. This saves you time in reusing common building blocks that you develop. User-defined functions can be created in C, C++, Java, RPG, COBOL, PLI, CL and SQL.

  • Declarative referential integrity

    Provides SQL database integrity support intrinsic to the database, eliminating the need to code integrity constraints into each application program. This support ensures database consistency by preventing conflicting data from being entered into the database.

  • User-accessible logs

    Journal entries (i.e., records of database changes) can be searched and viewed interactively, and may be retrieved by a user program for further processing or analysis. This can lead to improved security and/or database integrity and is also an important component for open access to the database.

  • Column-level security

    Access to individual table columns can be controlled for each user.

  • Row-level locking

    Individual rows (i.e., records) are locked from simultaneous, conflicting access as appropriate to the type of processing being done. Using commitment control, the user can define a group of records all of whose locks are held until the user application declares a multiple change transaction complete.

  • Data striping

    Data is automatically distributed over all available disk units within a set defined by the user. This can improve the performance of applications that make heavy use of a single database file or table.

  • Stored procedures

    Provides the ability to distribute the application workloads between clients and servers. The ability to split an application program by executing the processing logic on the server and the presentation logic on the client can provide increased performance over traditional requester access. These improvements can be dramatic for applications requiring intermediate processing of data, which can be performed at the server locally, instead of remotely at the client. Stored procedures can be written in C, C++, CL, COBOL, FORTRAN, JAVA, PLI, REXX, and RPG. Stored procedures can also return result sets either as cursors that are left open or arrays. Result sets can be fetched similar to reading rows from a table.

  • Triggers

    Provides for automatic program/procedure execution, based on user specified rules, before and/or after database modifications. SQL triggers can be specified at the column, row, and statement level. Triggers can also be created in HLL languages such as C, RPG, COBOL, and C++.

  • Joins

    DB2 UDB for iSeries supports a wide range of joins. This includes RIGHT, RIGHT OUTER, RIGHT EXCEPTION, LEFT, LEFT OUTER, LEFT EXCEPTION, and CROSS JOINs. This allows users to develop and use more efficient reports.

  • Alter Table

    The Alter Table function enhances database administration while improving SQL standards conformance. This function allows the user to add a column, drop a column, or change a column's attributes for an existing database table.

    End-user productivity can be greatly enhanced with this standard conforming function for database changes and administration. Both SQL and traditional systems interfaces are provided.

  • DB2 Call Level Interface to ODBC

    Support of the DB2 Call Level Interface (CLI) allows users to easily access DB2 UDB for iSeries SQL functions directly from high-level languages (HLL) without performing an SQL precompile. DB2 CLI also provides full Level 1 Microsoft ODBC support plus many Level 2 functions. ODBC and DB2 CLI are based on the X/Open and SQL Access Group Call Level Interface specifications.

    DB2 CLI is supported on several other database platforms, which makes SQL application portability to and from the DB2 UDB for iSeries platform even easier. DB2 CLI supports an option for database serving for multiple users (server mode). With server mode:

    • Each connection runs under a different user profile. When not using server mode, all connections run under the profile of the requesting job.
    • Multiple connections to the same relational database (data source). When not using server mode, a particular job can only have one connection to a particular database at any one time.
    • Each connection contains its own transaction, which can be committed or rolled back independently. When not using server mode, all connections are part of a single transaction.
    • Greater total number of allocated handles. In regular mode, the limit is 500 total handles per job. In server mode, the limits are 500 statement handles per connection and 40,000 total handles per job.
    • Multiple connections operate simultaneously if the application is using threads and not sharing connections handles across threads. When not using server mode, all SQL statements in a job are single- threaded, even if the requests come from different threads.

  • Access to data areas and data queues

    DB2 UDB for iSeries includes support for transparent remote access to data areas and data queues. Applications that use data areas or data queues for interprocess communications can be distributed across multiple iSeries systems, providing new options as users move into distributed iSeries networks and multi-tiered application models. Additional data queue support is included in MQSeries for iSeries, a separately-licensed program, 5733-A38.

  • Two-phase commit transaction management

    Allows applications to access multiple heterogeneous databases simultaneously in complex client/server and peer to peer environments using APPC sync point protocols and TCP/IP with DRDA.

  • System-wide database catalog

    Allows applications to query information concerning all database objects on a system using a single system catalog, instead of requiring separate catalog accesses for each SQL collection.

  • Multiple-level concurrency control

    Provides read stability, cursor stability, uncommitted read, repeatable read, and no commit isolation levels with row-level locking to support large numbers of users in complex application scenarios.

  • National Language Support (NLS)

    Allows customers to interact with DB2 UDB for iSeries and store data in their preferred language, character set, and sort sequence. The ability to store double-byte graphic characters and compare data in different character sets is also provided. Coded Character Set Identifications (CCSID), including UCS-2 (ISO 10646 Unicode), can be specified at the file or column level.

  • Defining Database Objects

    Database objects can be created with the iSeries Navigator graphical interfaces, with SQL, or with DDS. The DB2 Query Manager and SQL Development Kit for iSeries (5722-ST1) provides precompilers, interactive query and report writing tools for iSeries. SQL operations issued from the various interfaces supported by the database (ODBC, CLI, JDOC, OLE DB, SQLJ) can also be used to create database objects.

  • Traditional System Interface

    In addition to SQL, DB2 UDB for iSeries supports a system interface consisting of a full set of system commands and other non-SQL facilities that let users access and modify database data.

    Access paths may be defined for files to allow access in either keyed or arrival sequence order. Access paths are maintained when a change to the data occurs, allowing multiple users to be immediately aware of changes in the database and to access the current information in their required sequence.

    DDS can define a field reference file, a form of data dictionary, that describes the attributes of all data fields for use by multiple applications. It contains all attributes and descriptive information about the data. The field reference file ensures consistency in field names and defined attributes, resulting in significant benefits to application design, maintenance, standardization, and programmer productivity.

    The database supports record additions, updates, deletions, initialization, and reorganization. A full range of processing options is available for HLL programs such as sequential or random access (by key or relative record number), and retrieval of next and previous record. Many database functions can be described dynamically and performed externally to the HLL program, thus maximizing programmer productivity.

  • Distributed Database Support

    OS/400 supports distributed relational database using SQL. This support allows read and write access from an iSeries system to another iSeries system or to any other database supporting the Open Group DRDA architecture including DB2 UDB for OS/390 and z/OS, DB2 UDB for Windows, and DB2 UDB for AIX. DB2 Relational Connect, a feature of DB2 UDB for Windows and UNIX servers, allows access to additional database such as Oracle, Microsoft SQL Server, and others. An iSeries system can connect to a system running DB2 Relational Connect to access data in the databases accessible by DB2 Relational Connect.

    Distributed file access between an iSeries system, CICS, PCs, System/36, and System/38 is also available using Distributed Data Management, included in OS/400. This support allows access to remote files by applications using file and database interfaces.

    The SQL Client Integration API allows providers of gateways and client/server solutions to integrate their products with DB2 UDB for iSeries.

  • National Language Capability

    Data in multiple national languages may reside in the same table and be accessed across the distributed database platforms.

High Performance Database Server:

The high performance iSeries system is an ideal platform for a database server. In addition, DB2 UDB for iSeries offers superior performance for both centralized and distributed client/server database access, making the AS/400 the database server of choice for many computing needs. The following DB2 UDB for iSeries functions are available to enhance application performance:

  • Advanced SQL optimizer

    Converts SQL requests into optimally efficient database access methods using proven mathematical rules as well as query specific cost estimates. Optimal performance is maintained over time by the automatic rebind feature, which redetermines access methods based upon changes to the database objects and statistics. The optimizer also detects changes in the number of processors on each query. So when processors are moved to an LPAR or when Vertical Capacity Upgrade on Demand adds additional processors, the query plan is automatically reoptimized if necessary.

  • SQL Encoded Vector Indexes (EVIs)

    This type of index can be created through SQL and may improve query performance -- especially for long-running queries against large files using many selection criteria. An EVI has several advantages over a traditional index with the same keys:

    • Precise statistics about the distribution of key values are automatically maintained and can be accessed much more quickly by the query optimizer than traditional indexes.
    • EVIs can be built much faster and take significantly less storage than traditional indexes. Less storage means less main storage is necessary to run the query.
    • The query optimizer can scan EVIs and dynamically build bit maps much more quickly than from traditional indexes.

  • Explain Function

    Examines and reports the access method used by individual SQL queries. The output can be examined to determine whether the access method generated for the query could be improved by query and/or database changes.

  • Multiple isolation levels

    Four record locking options are available to fine tune application performance:

    • Read Stability (*ALL) locks all rows read during transaction and maintains locks until the transaction ends.

    • Repeatable Read (*RR) locks all rows read during remote unit of work and maintains locks until the unit of work ends.

    • Cursor Stability (*CS) maintains locks on the current and previously changed rows only, which can offer increased performance for multiple applications contending for the same rows.

    • Uncommitted Read (*CHG) offers higher performance by not acquiring or examining database locks for read-only operations.

    • No Commit (*NONE) provides the highest performance of the four isolation levels, by not examining locks and disabling transaction management: the ability to either COMMIT or ROLLBACK a transaction.

  • Block INSERT and FETCH

    Provides applications with the ability to store and retrieve arrays of data directly, instead of one row at a time.

  • Automatic record blocking

    Improves client/server performance by returning rows to the client in blocks rather than individually. Subsequent record access of the current block can then be performed locally at the client without accessing the server. This ability is provided for all isolation levels.

  • Parallel data access

    Queries returning or requiring DB2 UDB for iSeries to process large amounts of data require significant I/O activity. Due to the iSeries' single-level store architecture, this data is often spread across many physical devices. The parallel data access feature allows multiple internal DB2 UDB for iSeries tasks to be activated for each physical device, allowing DB2 UDB for iSeries to transfer data from disk to memory faster than with a single task I/O architecture.

  • Query Governor

    Long-running queries can have negative performance effects for other users of a database. The governor facility allows a time limit to be set for a query, so as to avoid a single query from consuming unusually large amounts of resources, negatively affecting the performance of other users. Before the query is started, its run time is estimated, and if the estimate exceeds the specified time limit, the query is not started. This is advantageous over similar functions on other databases that let the query run for a portion of time and then stop it since no unnecessary processing of the query occurs.

  • Scalability

    DB2 UDB for iSeries supports very large database environments. Some scalability limits are a single tube can be up to 1 TB and 4.2 billion rows. Distributed tables can be up to 32 TB.

    DB2 SMP and DB2 Multisystem support enable both horizontal and vertical growth.

Ease of Use and Management:

The iSeries' reputation for usability and maintainability is unsurpassed in the industry. This is due in part to the tight integration of OS/400 and DB2 UDB for iSeries. Users do not have to learn separate operating system and database functions, nor are they burdened with maintaining the complex interfaces between multiple layers of software. In addition to seamless integration, a rich set of utilities continue to be provided for easy management of DB2 UDB for iSeries databases. Some of these utilities include:

  • iSeries Navigator

    iSeries Navigator Database is a graphical interface that you can use to perform many of your common administrative database options. From iSeries Navigator you can create, change, delete, move and copy database objects. You can enter data into tables, view table contents, run SQL scripts, graphically display the relationships of your database objects, regenerate SQL from existing database objects, graphically display your query optimization with Visual Explain, monitor database performance, and perform other database management tasks.

  • Online backup and restore

    Allows database maintenance to be performed while users are accessing and changing the database, providing around-the-clock operation.

  • Object level recovery

    Allows restoration of a single file when necessary; it is not necessary to restore the entire database to recover a single table.

  • Roll forward and backward recovery

    Allows database changes made after the last backup to be reapplied after a restore, or recent changes to be backed out if the database needs to be returned to a specific state. This can be done for a specific user, time, or job.

  • Audit trail

    Maintains a record of database changes such as the user, program, and job making the change.

  • Performance tuning and trace

    Analyzes processor and disk workloads for improved performance. The integrated nature of the database allows the entire system to be tuned - not only the database.


Support for portability and interoperability is delivered by incorporating popular database standards and transmission protocols. DB2 UDB for iSeries provides support for:

  • ANSI X3.135.1999, ISO 9075-1992, FIPS 127-2, JIS, and The Open Group Structured Query Language (SQL)

  • The Open Group's Distributed Relational Database Architecture (DRDA) Distributed Unit of Work - Application Directed

  • Microsoft's Open Database Connection (ODBC)

  • The Open Group's Call Level Interface (CLI)

  • The Open Group XA Resource Manager Support

  • SQLJ

  • XML

  • JDBC

  • OCE DB and ADO

  • US Government CZ

  • UCS-2 (Unicode or ISO 10646)

  • Euro Character support

Supported transmission protocols for the iSeries include:

  • Transmission Control Protocol/Internet Protocol (TCP/IP)
  • Advanced Program-to-Program Communication (APPC)
  • Advanced Peer-to-Peer Networking (APPN)

This support allows customers to exploit the maturity and stability of the iSeries database server with a wide range of client and network applications.

Industry-Leading Application Support:

Over 20,000 commercially available iSeries application solutions take advantage of the power, flexibility, and ease of use of the DB2 UDB for iSeries database manager. These applications are written for a wide range of industries and users: from the small business with base accounting needs to the large corporation with complex computing environments. Over 3,000 client/server applications are available, including SAP R/3.

In addition, DB2 UDB for iSeries' support of popular database standards combined with the iSeries system support of popular transmission protocols makes the wide range of client and network applications.

Related Products:

DB2 UDB for iSeries is integrated directly into the OS/400 operating system. It includes all the support necessary for new and existing database applications to run on the iSeries system. Refer to


System/38 versions of these utilities are available in System/38 Utilities for AS/400 (5722-DB1).

Application development facilities are provided in the optional DB2 Query Manager and SQL Development Kit for AS/400 . This product includes Query Manager, an interactive panels and query builder for user-developed report generation, and Interactive SQL, a prompted interface for running and testing SQL queries. For the application developer, the SQL Development Kit provides SQL precompilers and tools to assist in developing custom SQL applications in languages such as C, C++, RPG, and COBOL. Once created, the applications and queries can be run on any iSeries system.

Data File Utility (DFU), a part of IBM WebSphere Development Studio for iSeries (5722-WDS) can be used to create and maintain database applications.

IBM Query for iSeries (5722-QU1) provides reporting on databases.

OS/400 - DB2 Symmetric Multiprocessing: expands on the parallel capabilities of DB2 UDB for iSeries. This separately priced feature of OS/400 improves the performance of the database for the iSeries system. This improved performance is critical, especially in a data warehouse or decision support environment. The performance gains provided by this feature help to allow for better and more effective business decisions to be made in a timely manner.

OS/400 - DB2 Symmetric Multiprocessing further enables DB2 UDB for iSeries with symmetric multiprocessing (SMP) on any of the iSeries N-way systems. SMP capabilities have existed since the introduction of the AS/400 N-way architecture. This form of SMP allowed multiple database operations to take place simultaneously on multiple processors. Each database operation would run on a single processor, thus optimizing DB2 UDB for iSeries for online transaction processing. With the availability of OS/400 - DB2 Symmetric Multiprocessing, DB2 UDB for iSeries also becomes optimized for decision support processing. DB2 UDB for iSeries is one of the few databases that can take full advantage of an SMP architecture for online transaction processing environments and decision support environments.

With the introduction of DB2 Symmetric Multiprocessing for OS/400, a single database operation can run on multiple processors at the same time or, in other words, in parallel. These database operations are typically queries. However, parallel processing is also supported for import and export between DB2 UDB for iSeries and other databases.

Parallel index build capability is included in DB2 Symmetric Multiprocessing (SMP). An index build can utilize multiple processors at the same time, or in other words, work on multiple parts of the index in parallel. This allows significant performance increases in cases where an index is created or rebuilt.

For queries, both SQL and native database interfaces are supported.

To achieve this parallelism involving multiple processors, an individual query is split into many smaller subtasks. Each subtask can run independently on a separate processor. Once the subtasks are complete, the results of each subtask are then combined to form the complete query result. Because of the advanced, single-level store architecture of OS/400, these subtasks can efficiently process information on the behalf of a user query request.

Those queries, which include table scans, index scans, joins, or group-by operations, will realize the greatest performance benefit from SMP database parallelism.

This process of splitting queries to run in parallel allows for significant performance increases. These performance increases become more pronounced with the addition of more processors. For example, if a query is running in 20 seconds on an iSeries with a single dedicated processor, adding a second dedicated processor along with the DB2 Symmetric Multiprocessing feature may allow this query to run in approximately 10 seconds. Adding two additional processors may allow this query to run in approximately five seconds.

The previous example illustrates something that is very important with database parallelism -- how scalable is the technology. Scalability will govern how much benefit is gained from adding additional processors. Perfect scalability allows for four processors to run a query in one- fourth the amount of time that a single processor could, as shown in the previous example. The advanced architecture of the iSeries system and of OS/400 have enabled DB2 Symmetric Multiprocessing to show industry leading scalability across all iSeries N-way systems.

DB2 Symmetric Multiprocessing can be configured differently for each user of the system. This allows a system administrator to have the greatest control over how parallelism is used on a system and thus greater control over how system resources are used. Part of this enablement process allows the selection of just how much parallelism is used, or in other words, how many subtasks are used for each query. Using fewer subtasks than processors available will allow a greater amount of the total system resources to be used by other users. Using more subtasks than processors available, allows an individual user to use more of the total system resources. This flexibility is needed to allow administrators to balance the needs of all system users with the available resources.

OS/400 - DB2 Multisystem:

OS/400 - DB2 Multisystem can be ordered as a separately priced feature of OS/400.

The iSeries system and OS/400 - DB2 Multisystem provide a scalable solution for data warehousing that spans from the smallest datamart to the largest enterprise data warehouse. DB2 Multisystem allows multiple iSeries systems to be connected to allow the processing power and storage capacity of all of the systems to be used. From a database perspective, these interconnected iSeries systems will appear as a single, large system.

Integrated File System (IFS):

The Integrated File System (IFS) allows libraries/objects, folders/documents, or LAN Server/400 file system data to be accessed in a consistent manner. A separate subsystem can be allocated specifically for file serving, and a set of commands are provided to make it easy to move one's PC data from the folders directory (i.e., shared folders) to the "root" file system directory. The major benefits for using the new file system directory are increased performance over shared folders and providing system users easier access to PC information.

IFS integrates the existing AS/400 library/objects, folders/documents, and shared folders into a single hierarchical name space and file system with simple command interfaces for file management and improved levels of performance. OS/400 file systems include:

  • "Root" file system: OS/2, DOS, and Windows compatible
  • QOpenSys file system: POSIX, XPG, UNIX compatible
  • Library file system (QSYS.LIB)
  • QFileSrv.400 file system
  • QOPT file system
  • QNTC
  • Network file system (NFS)
  • UDFS: user defined file system - mountable file system that is OS/2/DOS and Windows compatible

User applications can store and manipulate stream file sizes up to 256 GB in the root ('/'), QOpenSys, and user-defined file systems.

The Integrated File System supports a set of industry standard APIs to the byte stream file system and the hierarchical directory. The APIs provide a common directory for existing objects and extended attributes supporting PC file systems. Examples of byte stream file system objects on the system are: documents and byte stream files. Examples of hierarchical directory objects on the system are: libraries/contexts, folders and directories. IFS is compatible with and can coexist with previous releases.

Starting in V5R3 iSeries now possesses the ability to allow integrated file system objects to be scanned. This support creates flexibility for iSeries users by: allowing scans for various items; users decide when the scan should occur; users decide what actions to take bases on the results of your scan. For more information about scanning, see the iSeries Info Center.

Library File System (QSYS.LIB)

  • The QSYS.LIS file system supports the iSeries server library structure. This file system provides you with access to database files and all of the other iSeries server object types that the library support manages in the system and basic user ASPs.

  • Supports all user interfaces and programming interfaces that operate on iSeries server libraries and objects in those libraries.

  • Supports all programming languages and facilities that operate on database files

  • Provides extensive administrative support for managing iSeries server objects

  • Supports stream I/O operations on physical file members, user spaces, and save files

QFileSrv.400 Client File System Support:

Using IFS commands and APIs, users can perform such tasks as determining what is in a directory that resides on a target system, or use the APIs to copy files from one system to another.

In addition, PC and Linux/Samba users using iSeries NetServer can access the QFileSrv.400 file system allowing access to data on multiple iSeries systems with just one communications connection.

The QFileSrv.400 file system operates between iSeries systems that are connected by standard communications facilities using the APPC or TCP/IP protocols.

QOPT File System Support:

Using IFS commands and APIs, the QOPT file system provides access to stream data that is stored on optical media.

In addition, QOPT:

  • Provides a hierarchical directory structure
  • Is optimized for stream file input/output
  • Supports data stored in stream files


i5/OS includes a file system, QNTC, that connects the iSeries to a Windows File Server as a client. This includes Windows NT and higher, iSeries NetServer, and Linux/Samba.

  • Using IFS commands and APIs provide access to the QNTC.
  • Industry standard protocols, NetBIOS over TCP/IP, are used as a transport mechanism.
  • Industry standard messaging protocols, Common Internet File System (CIFS), also know as Server Message Block (SMB), are used.
  • By allowing access to data stored within a Windows domain, the iSeries system can become a mechanism for distribution of applications and data within the domain.
  • The file system can also be used by any iSeries application that can use data as formatted on the Windows server, such as Java applications.
  • It allows access to data on both stand-alone Windows NT servers and the iSeries Integration with Windows Server.
  • Windows NT 4.0 and later are supported.

    Note:The QNTC file system lets you share data with servers that can communicate using the Windows NT LM 0.12 dialect.

Network File Server (NFS)

  • The NFS file system provides the user with access to data and objects that are stored on a remote NFS server. An NFS server can export a network file system that NFS clients will then mount dynamically.

  • In addition, any file system mounted locally through the Network File System will have the features, characteristics, limitations, and dependencies of the directory or file system it was mounted from on the remote server. Operation on mounted file systems are not performed locally. Requests flow through the connection to the server and must obey the requirements and restrictions of the type of file system on the server.

Integrated File System (IFS) and selected Industry Standards:

IFS and selected standards provide portability and interoperability functions that support the integration of the entire customer enterprise in a heterogeneous networked environment. The challenge of implementation is accomplished through the traditional AS/400 strengths such as ease of use, security and system integrity. The customer's investments in existing systems, networks, applications, data and people are preserved.

The iSeries system provides support for source code portability of many OS/2, DOS, NT and UNIX based applications over a wide variety of systems by providing a set of standard interfaces between applications and operating system functions. With V3R1, the AS/400 system supports over 70% of the POSIX 1003.1 APIs. Together with BSD Sockets, TCP/IP and UNIX Spec 1170 support, we have nearly doubled UNIX C portability to the AS/400. With V3R1, the AS/400 system complies with selected elements of:

  • POSIX IEEE 1003.1 (ISO/IEC 9945-1)
  • POSIX IEEE 1003.1a
  • POSIX IEEE 1003.1b (formerly 1003.4)
  • POSIX IEEE 1003.1c (formerly 1003.4a)
  • FIPs 151-1
  • X/Open CAE Specification, System Interfaces Definitions, System Interfaces and Headers Issue 4 (XPG4)
  • Berkely Software Distribution (BSD) Sockets Version 4.3
  • USL 1170 Specification (X/Open UNIX Extensions)
  • USL System V Interface Definition Third Edition
  • ISO/IEC 10646-1

To enhance application program distribution and data interchange on the AS/400 system, unlabeled 1/4" and 8mm tape media have been added. The tape media is compatible with POSIX, XPG, and UNIX support.

Transaction Processing:

Most systems today support a variety of transaction processing requirements ranging from interactive to batch. But not all systems provide this support in the same manner.

Support for all transaction processing environments such as native OS/400 interactive, System/38, System/36, Batch and Client/Server are all integrated into OS/400. There is no separate software to purchase and the interface to these transaction processing environments is the same interface used for all other parts of the operating system, so consistency is maintained.

The transaction processing functions of OS/400 provide for flexible implementation of your workloads. Through the use of priorities a certain group can be ensured first processing in the system, or by simply adjusting resource allocation a given batch job can be allowed to run to completion without interruption from an interactive job.

OS/400 offers comprehensive transaction processing capabilities coupled with the ability to run applications migrated from other systems and it provides this with no additional software or integration required.

Using CICS for AS/400, a separately-licensed program (5769-DFH), customers can port System/390 CICS applications to AS/400 without excessive cost of code conversion.

Batch Processing:

Jobs that do not require user interaction can be processed as batch jobs. A batch job is typically a low priority job which may require a special system environment in which to run in order to reduce contention for system resources.

Most batch jobs are submitted to the system through job queues. The job queue may or may not be active at the time of submission. If inactive, the jobs await its activation. Jobs can be placed on job queues from an existing job, such as:

  • an interactive job
  • database file
  • a job schedule entry

Submitted jobs can be specified to run:

  • immediately (as soon as all previous jobs in the job queue have completed)
  • one time only, on a specified date/time
  • daily (or on certain days of the week), at a given time
  • weekly, on a given day of the week, at a given time
  • monthly, on a given day of the month, at a given time

Batch job processing can be controlled from any work station, and each job queue can be controlled separately, including:

  • Activating/de-activating
  • Holding/releasing

For example, during heavy interactive use, batch jobs can be submitted to an inactive job queue to be run later when adequate system resources are available.

Multiple batch jobs can be run simultaneously on a single system, with the number depending upon the availability of the resources each requires and the impact on other jobs running on the system at the same time, for example, interactive jobs. In general, as more CPU, memory, and DASD resources are available, more batch jobs can be run simultaneously.

XML Enablers

Extensible Markup Language (XML) is one of the key technologies fueling growth of e-business and mobile e-business solutions. XML is becoming the standard way to represent data in a portable, reusable format for use in a number of solutions ranging from B2B solutions that link together trading partners to pervasive computing applications, which connect mobile devices such as cell phones to core business solutions.

IBM and iSeries are committed to supporting XML. This support is demonstrated by the suite of XML application enablers delivered with OS/400 in V5R1, providing a core of XML services for applications to build on. The XML application enablers provided in V5R1 include:

  • XML parsers for use with Java and C++ applications. XML parsers are a common building block that XML-based solutions use to work with data in XML format.

  • XML parsing interfaces for procedural languages such as RPG, COBOL, and C. These interfaces open the realm of XML to existing solutions, providing an easy path to extend these solutions with XML support.

  • Extensible Stylesheet Language (XSL) processor used to apply XSL stylesheets to transform an XML document into another markup language format. XSL stylesheets are the standard way to convert data between two XML document types and are commonly used to convert XML data to HTML for presentation in a Web browser environment.

Enterprise Identity Mapping (EIM)

For V5R2, self-management capability is enhanced with EIM. EIM gives you and your business partners a technology that maps a user identity on one system to the user's identity on another system. The operating system and applications can equate jsmith on iSeries to janesmith on zSeries.

Identity mapping information is available to customers and ISVs through APIs available on all IBM eServer platforms.

Java/XML Enhancements

New versions of the core Java runtime environment and WebSphere Application Server are now available, as well as J2EE (Java 2 Enterprise Edition) compliance.

J2EE represents an emerging suite of standard requirements placed on Java application servers like WebSphere. The Java Virtual Machine (JVM) supports the emerging Java Debug, Performance Profiling, and Wire protocols that enable third-party tools to work with the iSeries JVM, along with iSeries specific instrumentation for memory leak detection and enhanced debug. With this release, the suite of XML enablers can stay in step with the latest XML standards. The support for XML schemas is a key XML enabler extensions provided in this release.

In V5R2, the iSeries supports the industry-standard JavaMail program interface used by applications to access or send e-mail using POP, IMAP, or SMTP protocols.

IBM Toolbox for Java

A new version of the IBM Toolbox for Java is available with V5R2.

Enhancements include:

  • A set of classes for accessing data from a wireless device.
  • An updated JDBC driver that supports JDBC 3.0
  • The ability to use a Kerberos ticket when authenticating to the server.
  • A system debugger to graphically debug C, C++, Java, and RPG programs on the iSeries.

OS/400 Cluster Resource Services

Clustering, initially introduced in V4R4, expands the underpinning to improve overall availability of your critical resources beyond what you can achieve in a single system environment. Additional significant functions are expanded with V5R1 that allow even more flexibility and improved availability. New capabilities include:

  • Independent Auxiliary Storage Pools (IASPs) - allow you to take data offline and bring data online independent of the System ASP and other User ASPs.

  • System services in support of Option 41, HA Switchable Resources - allows you to define device domains and to use resilient device cluster resource groups containing Independent ASPs.

  • HSL OptiConnect is supported as a cluster communications fabric (in addition to what was previously supported).

  • Options to adjust the tuning and configuration parameters of your cluster to better match your communications environment.

  • Journaling of IFS objects, data areas and data queues, and options to reduce the amount of data journaled.

HA Switchable Resources, OS/400 Option 41

HA Switchable Resources, a new chargeable option of OS/400, gives you the capability to achieve a highly available environment using switchable resources. The resources are physically switched between systems so that only one copy of the resource is required. Included as part of Option 41 are:

  • Switchable Independent ASPs - allows you to move the data to a backup system to keep the data constantly available. The data is contained in a collection of switchable disk units such as an I/O tower.

  • IBM Cluster Management Utility - allows you to create and manage a simple two-node, switched disk cluster. The utility includes wizards and help text that simplify the tasks involved in defining and managing the cluster.

To define switchable independent ASPs or to use the IBM Cluster Management Utility, you must have OS/400 Option 41, HA Switchable Resources installed on your system. You also must have a valid license key for Option 41.

For information on HA Switchable Resource hardware features, refer to Hardware Announcements dated April 23, 2001.

Independent Databases

Support for independent DB2 UDB for iSeries databases via Independent Auxiliary Storage Pools, or IASP, gives you additional availability and server consolidation options. Multiple DB2 UDB for iSeries databases within a single instance of the operating system allows for application flexibility and server consolidation by providing separate named database spaces. For instance, a company could have each of its regions share the same applications on a single instance of OS/400, each with their own copy of the DB2 UDB for iSeries schemas (libraries). Each region sees only the database objects for that region. Different users on the same system can connect to the appropriate database for their region. Independent Switchable databases enable access to your data during scheduled and unscheduled downtime without requiring redundant data collection.

DB2 UDB for iSeries Standards Support

V5R2 furthers DB2 UDB for iSeries' position in support of many industry standards and DB2 UDB for iSeries family compatibility. Benefits include:

  • More application and tool availability
  • Easier application or database portability
  • Improved interconnectivity to many different platforms/databases
  • Better use of available skills in the workforce

In addition to the traditional database interface and language support, DB2 UDB for iSeries provides a robust SQL-based database required by today's Enterprise Application Systems while leveraging the strengths of the IBM eServer iSeries.

Additional enhancements in V5R2 make it easier for you to transition from traditional database interfaces to the SQL world. A unique advantage for iSeries customers is that you can choose from a mixed environment of traditional and SQL facilities based on requirements, skills, or existing applications.

Query optimization technology within DB2 UDB for iSeries is improved in V5R2 to deliver improved performance in certain query/SQL environments.

Industry Standard and DB2 UDB for iSeries Family SQL Enhancements in V5R2

  • JDBC 3.0 (JDK 1.4)
  • The Open Group's Distributed Transaction Processing: The XA Specification
  • JTA (Java Transaction API) 1.0.1
  • ODBC and JDBC drivers for Linux
  • User-Defined Table functions
  • Savepoints
  • Common Catalog Views
  • UNION in Views
  • IDENTITY columns and ROWIDs
  • CREATE TABLE AS (subselect) (support in SQL equivalent to DDS Field Reference)
  • SQL Source Code Debugger
  • Additional SQL Enhancements in conformance with the ISO and ANSI SQL Core Standard

Integrated File System

Enhanced data management and performance for the Integrated File System is rolled out with a new directory implementation that provides significantly enhanced directory performance, scalability, robustness, and recoverability. That, combined with the journaling and improved caching techniques, provides the system with a faster, safer, more reliable file system.

Note that the Integrated File System directory enhancements are available in V5R1 and will ship when ready. Watch for APAR II13161 at:


Ease of Installation, Use, and Maintenance:

  • EZ-Setup

    EZ-Setup code is delivered as part of Client Access Express. The code runs on a PC under Windows 95, Windows 98, Windows NT 4.0, or Windows 2000 and requires the Operations Console cable be connected to the host iSeries.

    EZ-Setup has three components:

    • EZ-Setup Wizard
    • Guided Setup
    • The Next Step

    EZ-Setup Wizard reduces both the number of decisions you need to make during setup and the amount of installation information you need to enter. The interface is all graphical.

    Guided Setup is a collection of HTML pages for the same tasks as those in the EZ-Setup Wizard. You read the information using a browser and enter AS/400 commands to perform tasks.

    The Next Step is a set of HTML pages that you read and then perform the task. Topics include Exploring iSeries Navigator, Setup Printing, Create User Profiles, Install Additional Software, Define System Cleanup Options, Create a System Backup and more. Use Next Step after the EZ-Setup Wizard or Guided Setup is complete.

  • Table-driven Design

    Operating system installation and modification are table-driven to allow easy and quick tailoring of basic system operations. This results in less effort required for initial installation and system maintenance which provides better system uptime. The installation of OS/400 software involves copying the system objects from the distribution media onto the system auxiliary storage and then changing variables in external tables (System Values) to tailor operations in the following areas:

    • Security and auditing
    • Storage allocation and use
    • System operation
    • Messages and logging
    • System date and time
    • Numeric editing
    • Default job library list

  • Automatic Configuration for Local Devices

    The user can request that locally-attached devices be automatically configured. Local displays and printers can be added, changed or removed without affecting users signed on to displays connected to other controller ports.

  • iSeries Navigator

    iSeries Navigator is an integrated graphical interface developed to assist users performing iSeries tasks and working with iSeries system resources. iSeries Navigator provides Windows 95/NT and Windows 2000 desktop integration and interfaces for doing the following AS/400 administrative tasks:

    Management Central -- enables administrators or system operators to manage AS/400 systems in their network from a central AS/400 server. This includes the following functions:

    • Manage end point systems
    • Create and manage AS/400 system groups
    • Monitor system -- view real-time performance information about systems being managed. Allows administrators and operators to easily gather, analyze, and react to performance information. Monitor information about your AS/400, such as the CPU utilization, interactive response time, and disk space utilization. Other functions include:
      • Monitor multiple systems or system groups
      • Establish thresholds for each monitor
      • Execute programs automatically when threshold events occur
    • Collection Services -- provides more control in data collection; the user defines when (scheduled or immediate), how (individually or together), what (e.g., IOP or CPU information may be collected at different intervals without collecting DASD information), and how the data is managed. This increased control results in reduced overhead.
    • Management Central system group functions for:
      • object packaging and distribution
      • remote commands
      • PTF compare and distribution
      • inventory collection and search (hardware, software, fixes)
      • scheduled tasks
    • Messages -- send, view, and manipulate messages on AS/400 systems; properties of a message can be displayed and replied to.
    • Printers -- view and manipulate printers on the AS/400 system
    • Printer Output -- work with printer output that is waiting to be printed (i.e., open, hold, release, move, delete, etc.). Users can also change the properties of the output (i.e., printer, number of copies, priority, form type, etc.). Output can be moved to other queues using drag-and-drop operations. Output can also be copied to your PC using drag-and-drop.

      A subset of the Advanced Function Presentation Workbench product called the AFP Viewer is included with the printer output capability. The AFP viewer provides powerful viewing capabilities. The viewer allows users to view the contents of AS/400 printer output from the Printer Output list.

    • Jobs -- perform actions against or change the properties of jobs on AS/400 systems
    • Hardware and Software Inventory -- Multiple Systems --

      With a graphical interface, you can schedule regular inventory collections of hardware, software, and PTF information for a group or network of AS/400s.

    • Network Configuration:
      • Configure TCP/IP using a wizard to simplify the steps
      • Set up TCP/IP security
      • Configure point-to-point connection profiles and modems
      • Configure and monitor Client Access and TCP/IP servers, including:
        • DNS -- set up the domains and hosts
        • DHCP -- set up the subnets, classes, and clients
        • NFS (AS/400 Network File System server) -- manage the exports and netgroups
        • iSeries NetServer (iSeries Support for Windows Network Neighborhood) -- view the server statistics, the shared objects for a session, and sessions using a shared object
        • DCE
        • Directory server (Lightweight Directory Access Server, LDAP) -- Configure the server and publish user information to an LDAP directory
      • Internet Administration -- manage the following internet configuration functions:
        • IBM Firewall for AS/400
        • Net.Commerce
        • Digital Certificate Manager
        • Internet Connection Server for AS/400 (V4R1 and V4R2 only)
        • IBM HTTP Server for AS/400 (V4R3, or later release)
        • IBM Payment Server for AS/400
        • IBM Network Station Manager
    • Security Configuration, Resource Security and Security/Audit Policies -- Configure the AS/400 security using a wizard which asks questions about your AS/400 system and then recommends how to configure base system security. Reports for both the administrator and end users are fully NLS-enabled and are saved as text files that can be processed by an editor or word processor. Some or all of the recommendations can be automatically applied, and there is an option to reset the security configuration to what it was before the changes were made. Resource Security enables control of user and object information such as user's authority, public authority, owner, primary group, authorization list, default public authority for newly created objects (libraries only), and sensitivity level (QDLS objects only). Security/Object Policies can be changed easily.
    • User and Group Administration -- create, change, or delete AS/400 users with the click of a mouse and easy-to-use dialog boxes. Users can be added to a group through drag-and-drop operations. Users can also be copied to other AS/400s using drag-and drop.
    • Database Administration:
      • Set up ODBC configurations for other PCs in the network
      • Create and change database object definitions
      • Control access to database objects
      • Backup database objects
      • Organize file data to enhance performance
      • Copy object definitions and data
      • Display data in tables and views
      • Manage journal objects
      • Update table contents
      • Manage remote journals
      • Manage aliases
      • Copy and move tables between systems
    • File System Administration -- work with file system properties; filter the objects shown in the file system; open AS/400 objects using PC programs
    • Backup Support -- schedule daily, weekly, and monthly backups of remote AS/400 systems. Through easy-to-use panels, select what should be backed up, when to schedule it, and where to save it.
    • Application Administration -- control a user's access to functions in iSeries Navigator for each AS/400
    • Object Packaging -- The object packaging and distribution graphical interface makes it easy to send objects from any file system to one or more AS/400s in a network. You can also restore, take snapshots of, and version packages of objects, and post execution of commands. You can perform these functions on a group or network of AS/400s and schedule them to occur at a time most convenient for your staff.
    • PTF Management for a Distributed Environment -- The easy-to-use wizards simplify PTF management in a distributed environment. They walk you through the process of comparing the PTF levels of multiple AS/400s to a model system that has a proven set of PTFs already installed. You then distribute and install any missing PTFs on the remote AS/400s by simply identifying the system or group of systems to be updated. You can run AS/400 commands as part of completing PTF installations or as part of normal day-to-day operations.

    Third Party Plug-In Support -- allows other applications to "plug-in" by adding new folders and objects to the iSeries Navigator window or by extending existing objects with new menu items or properties.

    iSeries Navigator also provides function to make managing your AS/400 easier and more productive. These functions include:

    • Create shortcuts -- to AS/400 functions on your desktop (e.g., create a shortcut which brings up the list of messages for the system operator)
    • Auto-refresh -- set up a folder to automatically refresh the contents after a period of time.
    • Find -- an AS/400 object
    • Print Details -- Print the right pane of iSeries Navigator on your PC printer
    • Cancel Request -- Cancel a request for data from the AS/400

    Product Positioning for Management Central and Performance Management/400

    Management Central Monitors are provided with the base operating system, and can be used to drive real time automation tasks. Customers can monitor and display short term trends in specific performance metrics and have the ability to set triggers, so that when a floor or a ceiling threshold is reached, a user defined action can be invoked: alarms to alert the operator of this occurrence, or an automated response can be executed. Management Central system Monitors were not designed to perform analysis of performance or capacity.

    Performance Management iSeries (PM iSeries) software assists customers by helping them plan for and manage system resources through ongoing analysis of key performance indicators on a regularly scheduled basis. PM iSeries uses software and procedures to automate performance utilization and capacity usage reports. PM iSeries helps the user maximize application and hardware performance (using performance trend reports), and better understand (using capacity usage reports) how the business trends relate to the timing of required hardware upgrades such as CPU, memory, or disk. PM iSeries is designed for medium/long term performance analysis and trending, not real-time monitoring and automation.

    The System Monitors and Performance Management iSeries functions are designed to complement each other, with one providing real time monitoring and automation and the other focused on trending/analysis to insure performance.

    Cross partition, multi-OS support with PM iSeries - V5R3

    IBM Performance Management for IBM eServer iSeries (PM iSeries) is an integrated OS/400 capability that helps to ensure your iSeries server is available when needed without disruption.

    An automated OS/400 systems management function, PM iSeries is enhanced with V5R3 to help you more easily manage your iSeries in a dynamic, multi-OS, multipartition, capacity on demand processing environment.

    PM iSeries triggers collection services to gather non-proprietary performance and capacity data from your iSeries server and then, at your option, sends that data to IBM for analysis. In return, summary reporting and future system sizing capabilities are provided to you. Previously, PM iSeries ran at a partition level only and supported only the OS/400 operating system. To receive any kind of a "cross partition view," the user had to activate PM iSeries in all partitions and manually assimilate the results.

    Now, in combination with the availability of the IBM Director option of the IBM Virtualization Engine, PM iSeries support for a multipartition, multi-OS type (including OS/400, Linux and AIX 5L) is available with V5R3. PM iSeries provides summary reporting on your total system CPU utilization versus allocated, configured, and reserved Capacity Upgrade on Demand processors. Additionally, your summary multipartition, multi-OS type data can be passed easily to the IBM eServer Workload Estimator to help you assess any subsequent system needs.

  • Operations Console

    The AS/400 supports a new directly-attached, full-function 5250 PC console that includes a graphical control panel application. The user interface of the control panel application resembles its hardware counterpart. The console emulator application (PC5250) serves as the console "device" of the AS/400, therefore it permits the entry of restricted- state commands as SAVSYS and RCLSTG. The graphical control panel application permits remote entry of most of the functions supported by the hardware control panel mounted on the front of AS/400 system units. Control panel functions such as power up/down, re-IPL, mode changes, etc. are supported.

    The console and control panel applications can be used together or separately, but each requires its own direct cable attachment to an AS/400 system. Each cable must be purchased separately from IBM for the AS/400 model being used. Both cables are only available in a single length of 6 meters. The tables below list the cables available for each supported AS/400 model.

                    Cables for the console application
    |                  |              |  Part   |      |               |
    | AS/400 Models    | I/O Features | Number  | CIN  | Description   |
    | 600/620/S10/S20/ | 2721/2745    | 97H7557 | 0367 | 36 pin PCI    |
    |  150/170/720     |              |         |      |               |
    | 640/650/S30/S40/ | 9699         | 97H7556 | 0328 | 36 pin square |
    |  SB1/730/740     |              |         |      |               |
    | 4xx/5xx (Note 1) | 2609/2612    |         |      |               |
                    Cables for the control panel application
    |                  |  Part   |      |                              |
    | AS/400 Models    | Number  | CIN  | Description                  |
    | 600/620/S10/S20/ | 97H7591 | 0381 | Connects to 9-pin D-shell    |
    |  150/170/720     |         |      |   labeled MI/J19             |
    | 640/650/S30/S40/ | 97H7584 | 0380 | Connects to 9-pin D-shell on |
    |  SB1/730/740     |         |      |   lower left side of HW panel|
    | 4xx/5xx (Note 1) |         |      |                              |
    Note 1: For 4xx/5xx systems upgraded to V4R3, or later release,
            the cables required for the console and control panel
            applications are available in RPQ 843964.

    Remote capabilities:

    The direct-attach Operations Console can also serve as a gateway for a remote, dial-in Operations Console. The remote Operations Console can also be configured to run the 5250 emulator application and/or the graphical control panel application. Both applications in general make it possible to perform the majority of system operations tasks, for example back-up and recovery, with the AS/400 systems and the managing staff in physically separate locations. The connection between the remote and direct-attach Operations Consoles uses Windows dial-up networking (PPP) with the direct-attach Operations Console utilizing Windows NT Remote Access Service (RAS) for access.

    Software Requisites:

    The applications are included on the AS/400 Client Access for Windows 95/NT CD-ROM shipped with OS/400 V4R3, or later release. The Operations Console applications are installed and used on PC's using the Windows NT Workstation 4.0 with Service Pack 3 (required for the direct-attach Operations Console when it serves as a remote console gateway) or Windows 95/98 operating systems. OS/400 V4R3 or later release, is always required for direct/remote 5250 console attachment, however the control panel application will function as a stand-alone application with any IMPI or RISC "black-box" system. The table below illustrates the supported OS/400 levels and the possible iSeries and AS/400 models supported for each application.

                Supported OS/400 versions and AS/400 models
    | Operations Console application | OS/400 version   | AS/400 Models    |
    | 5250 console device emulator   | V4R4, or later   | 6xx/Sxx/150/170/ |
    |                                |                  |  4xx/5xx/7xx/8xx |
    | Graphical control panel        | V3R0.5, or later | 6xx/Sxx/150/170/ |
    |                                |                  |  4xx/5xx/7xx/8xx |
    |                                |                  |  2xx/3xx         |
    |                                |                  |   (Note 1)       |
    Note 1: Valid OS/400 level/hardware model combinations are not listed
            for brevity, but any supported combination will work.

  • Operational Assistant

    Operational Assistant (OA) presents a group of tasks, commonly done by an application end user or system operator, in easily understood non-technical terms. Users unfamiliar with the AS/400 system, its terminology, and sequence of steps to do a task are relieved of these complexities.

    User productivity is improved by operational assistant making it easy to do tasks such as managing printer output, managing batch jobs, sending and answering messages. Systems management is facilitated by using OA to enroll and delete users on the system, to back up libraries, and automatically clean up job logs, history log files, and system journals. The system administrator is also assisted in setting up and scheduling simple backups, managing users signed on to the system, understanding the status of the system and managing the system's disk space.

    The operational assistant function can be accessed in four ways:

    • Information Assistant

      Information Assistant options provide one-stop shopping for a user's AS/400 information needs. A menu provides selectable options to inform the user about where to look for information, how to submit comments on information, and highlights about what is new in the current release of the AS/400 system. In addition, access to searching the help index, starting online education and starting the question and answer function is provided. Information Assistant options are accessed from the AS/400 Main Menu, the Operational Assistant Information and Problem Handling menu, or by typing GO INFO on the command entry line.

    • Existing system commands, which have the parameter, ASSISTANCE LEVEL (basic, intermediate, or advanced)

    • An attention program that brings up the OA main menu

    • Application programs that use the OA programming interfaces

  • Menu Interface

    System-supplied menus to most system functions provide a task- oriented approach so that a user unfamiliar with control language can set up and use Operating System/400. The menus use an object-oriented approach by providing list of objects for the user to work with. A fast path gives quick access to system functions for the more experienced users.

  • Online Help

    The AS/400 help facility provides comprehensive explanations of display functions to help users be more productive. The index search facility can be used to request help for a task that involves multiple displays. Index search includes many synonyms so that users may ask for information in their own words or in the terms used by the system.

    The help information provided is determined by the current location of the cursor on the display. It may be specific to a field or line on the screen, or to extended help on the use of the display as a whole.

  • System Operation

    System operational functions can be performed on an attended, partially attended, or a predominantly unattended basis. System operator functions can be interactively entered or executed under program control. Printer paper and media handling are manual functions. Various displays are provided to allow for control of jobs, spooling operations and communication lines.

  • Problem Determination

    Job Trace Facility

    A job trace facility introduces several trace facility including four new CL commands (STRTRC, ENDTRC, PRTTRC, and DLTTRC) and includes the following enhancements:

    • Significantly improved performance, particularly when tracing ILE programs

    • Improved reporting information, including finer time granularity and additional I/O information

    • Eliminates the need to STRSRVJOB on jobs to trace

    • Can trace multiple jobs with one command, including a generic job set

    • Increased buffer size for collecting trace information to 4 GB

    Several system functions provide assistance in problem determination including dedicated and system service functions, messages, help information, and problem analysis commands.

    A useful function in problem determination is copying a screen image from one work station for display on another work station. This is especially useful when used in conjunction with remote service support.

  • Improved Software Problem Isolation and Data Collection

    User-friendly, easy-to-use OS/400 tools provide customers with the ability to collect problem data at a central site. This OS/400 support for software problem isolation and data collection enables customers to recreate software problems, save the results, and then view the data from a central site. Initiation of the tools can be done locally or remotely.

  • System Detected Software Problems

    Symptom strings are automatically created by the OS/400 licensed program at the time an error occurs, thus making management of problems in the system easier and recovery quicker. The automatic generation of symptom string data improves in the rate at which customers can find appropriate PTFs for problems. Problem resolution time is decreased when failure data is collected at the time of occurrence thus reducing the need for failure recreation.

  • Programming Temporary Fixes (PTFs)

    PTFs (including licensed internal code changes) may be loaded and applied using a command. Deferred PTFs can be applied only at IPL time, but an option allows this to be done unattended. PTFs can be shipped to a central site, either on media or electronically, and may then be packaged and distributed to remote or DSLO license sites, either on media or electronically. With the exception of the loading of media, the handling of PTFs can be automated for remote sites.

    V5R1 introduced several changes for PTF management:

    • The ability to electronically download Group PTFs from IBM Service.

    • Two new commands are available to manage cover letters on the system. Copy PTF Cover Letter (CPYPTFCVR) and Display PTF Cover Letter (DSPPTFCVR). These allow users to copy cover letters from media without having to load the PTFs and provide the capability to filter the list of cover letters based on a set of attributes and status for example, view all the cover letters that have special instructions.

    • Progress indicators during PTF load and apply processing, include progress indicators when PTFs are being applied or removed during the IPL.

    • PTFs can now be defined to have a new attribute called preconditions. A precondition identifies a job, subsystem, or object that cannot be active when the PTF is applied or removed immediately. The system will detect this and prevent the PTF from being processed when the precondition is active.

    • The following APAR and PTF prefix changes are made for V5R1:

      • The APAR prefix changes from SA to SE for software APARs

      • The PTF prefix changes from SF to SI for PTFs associated with the new SE APARs.

      • MA APAR prefixes and MF PTF prefixes are not changed.

      • The reserved PTF numbers (SF99nnn, SF98nnn, SF97nnn, SF96nnn, and SF95nnn) are not changed for V5R1.

    V5R2 changes include:

    • New functions available to view and manage PTF groups using system commands and APIs. Management Central functions were also changed to support sending and installing PTF groups.

    • Provided the ability to install PTFs from a virtual optical device

    V5R3 changes include:

    • Enable the ability to automate most of the cumulative PTF package special instructions.

    • Improved the performance of the IPL during the PTF apply processing step.

    V5R4 enhancements include:

    • Incremental improvements in reducing the number of delayed PTFs

    • Provided capability to save PTF information as part of new Save System Information function

    • Improved SNDPTFORD processing when using a Universal Connection:

      • Significantly increased the size of PTF orders that can be downloaded immediately.

      • Provided new special values for ordering PTF groups and cumulative PTF packages.

      • Provided the ability to download PTFs as an optical image

    • Reading AS/400 Books Online

      Softcopy publications are shipped on machine-readable CD-ROM medium as a no-charge feature of OS/400. The books may be downloaded from the medium and are then available for search and/or display from either programmable or nonprogrammable workstations.

      Downloading can be done from either the system CD drive or a programmable workstation with a CD drive attached. It is not necessary to download the books since all workstations can access the system CD drive to read them directly.

      On a programmable workstation, either the Library Reader licensed program (included on the medium with the books) or the BookManager READ licensed program is used to search/read the books.

      On a nonprogrammable workstation, the InfoSeeker function of OS/400 is used to search/read the books.

      The design of the softcopy library allows you to:

      • Install only those books that you need for your installation
      • Create customized bookshelves that contain only those books that you use most frequently
      • Search quickly for a word or phrase across a book, bookshelf, or the entire library
      • Select and jump directly to a topic
      • Look only at information that has been changed in the current release
      • Copy or print topics from a book
      • Copy coding examples to AS/400 files

      With the BookManager BUILD products (available for OS/2, VM, and MVS platforms), users can create their own softcopy books.

    Directory Services

    OS/400 Directory Services in V5R1 supports IBM SecureWay Directory Version 3.2. Examples of IBM SecureWay products dependent on the directory for some of their distributed functions are:

    • WebSphere Commerce Suite
    • WebSphere Application Server
    • SecureWay Policy Director
    • IBM MQ Series
    • IBM HTTP Server

    Version 3.2 of the IBM SecureWay Directory provides the following industry-leading innovations:

    • Support for Kerberos protocol (server and client) - supporting authentication utilizing Kerberos.

    • GSKit 4.0 - the server and client is upgraded to use GSKit 4.0 as the SSL provider.

    • Fine grain access control - allows the management of access down to the individual attribute level. A directory administrator may now control who may see individual attributes for each entry within the directory.

    • "Unlimited" Connections - allows a much larger number of clients to connect to a server, which reduces the number of servers required.

    • Transaction support - allows an application interface to include more than a single LDAP operation in a transaction with the server.

    • Event notification - allows a server to notify a registered client that an entry in the directory tree has been changed, added or deleted, at or below the specified DN(s) for the event types of interest.

    In addition to the IBM SecureWay Directory V3.2 updates, the following enhancements are made for Directory Services on OS/400:

    • Security auditing was added to LDAP for administrators that want to audit LDAP operations to the server.

    • The Directory Services server is automatically configured on the system when either the directory server or publishing is not already configured and when no LDAP DNS information can be found.

    • Directory Services has moved to the base operating system. OS/400 - Directory Services, option 32, still exists for compatibility, but the LDAP function is in the base.

    iSeries Directory Services Enhanced for V5R2

    IBM Directory Server V4.1 provides an LDAP identity infrastructure as the foundation for deploying comprehensive identity management applications and advanced software architectures like Web services.

    New for IBM Directory Server V4.1

    • Dynamic Groups -- Groups defined using a search expression. When an attribute is added to a directory entry, the entry automatically becomes a member of the group.

    • Nested Groups -- Nesting enables the creation of hierarchical relationships to define inherited group membership. A nested group is defined as a child group entry whose distinguished name (DN) is an attribute contained within a parent group entry. A new attribute explicitly distinguishes nested groups from ordinary members. The members of a group may also be querried.

    • Sorted Search -- The sorted search control allows a client to receive search results sorted based on a list of criteria, where each criteria represents a sort key. This moves the responsibility of sorting from the client application to the server where it might be done more efficiently.

    • Paged Search -- The paged results control allows you to manage the amount of data returned from a search request. You can request a subset of entries (a page) instead of receiving all the results at once. Subsequent search requests display the next page of results until the operation is canceled or the last result is returned.

    • Improved Performance -- Performance is improved for search, bind, and compare operations. Multiple clients can search and update their directory entries simultaneously.

    • Special Characters in Distinguished Names (DN) -- A DN may now contain the following special characters: commas, equals, plus, less than, greater than, pound, semicolon, backslash, and quotation marks.

    iSeries Directory Services has IBM Directory Server V4.1 function via PTFs for V5R2. The iSeries Directory Services Web site has more information about the PTFs:


    For more information, refer to IBM Directory Server V4.1 release notes (PDF, 86 KB) at:


    For V5R3 enhancements goto:

    http://www.ibm.com/eservers/iseries/ ldap/whatsnew5.3.htm

    Internet Printing

    Print and e-Print for iSeries

    V5R1 provides a wide range of new capabilities that enable the iSeries to address the print and communications requirements of e-business and network applications. Those capabilities include:

    • Support for PDF
    • Dynamic e-mail of printed output
    • Internet Print Protocol (IPP)
    • New printing architectures for Java applications
    • Support for Unicode
    • Comprehensive transforms for printed data

    These enhancements are available with OS/400, PSF/400, and a new iSeries product, InfoPrint Server for iSeries.

    Internet Printing Server for iSeries

    The Internet Printing Protocol (IPP) defines an industry-standard method of delivering print jobs using Internet technologies providing for Web-enabled print around the world. The IPP protocol was developed by the Printer Working Group, a consortium of all major companies involved in network printing. IPP is fast becoming the single standard interface for printing on the Internet, with broad vendor implementation and customer acceptance.

    The IPP Server for iSeries, included in OS/400, provides an IPP Version 1.0 compatible print server for the iSeries. This means the iSeries will accept IPP print requests and then serve the print file to the designated printer via traditional means. Thus, even if a printer does not actually support IPP, the iSeries will accept IPP requests for that printer and then print to that printer with other protocols. The IPP Server for iSeries allows business travelers, telecommuters, and anyone working remotely to submit and manage print jobs on a distant iSeries.

    V5R2 added support for IPP connection to network printers that support IPP. OS/400 sends printer output to these printers with an IPP connection.

    IPP is built on top of HTTP, which in turn runs over TCP/IP. Customers can use the same print solution on local area networks, intranets, and the Internet. The same process used to send a print document to the department printer down the hall can be used to send the document to the corporate printer across the country.

    The IPP Server for iSeries provides security features for user authentication and encryption of print jobs using Secure Sockets Layer 3 (SSL).

    PSF/400 Enhancements

    The iSeries printer file and Data Description Specifications (DDS) are enhanced to enable you to:

    • Specify whether line data print applications that use a page definition should have their output converted to Advanced Function Printer Data Stream (AFPDS) before the data is placed on OS/400 spool

    • Specify extended color models with COLOR, BOX, and LINE keywords

    • Specify shading with the BOX keyword

    • Use constant text with POSITION keyword

    • Specify horizontal font point size (in addition to vertical point size) on FONT, FNTCHRSET, CDEFNT, and IGCCDEFNT keywords

    • Specify Australian Postal and Royal Mail (Dutch KIX extension) barcodes; allow barcode height to be specified in inches or centimeters

    PSF/400 is also enhanced to provide:

    • New printer timer on the PSF configuration object that allows you to specify how long to wait for a response from a TCP/IP attached printer and new options on automatic session recovery.

    • An option to use DBCS simulation fonts instead of the DBCS raster fonts specified in the data stream when printing the spooled file. DBCS simulation fonts are outline fonts positioned like raster fonts. This allows the use of outline fonts to print applications that use DBCS raster fonts.

    • Enhancements to line data processing and page definitions to support record formatting. Record format page definitions allow an application to specify a format identifier with each set of object data written out. The format identifier specifies a specific layout format (similar to a DDS record format) in a page definition.

    • Enabling function to convert spool files to Portable Data Format (PDF) and store the resulting PDF in the Integrated File System (IFS). The PDF file may optionally be e-mailed using the OS/400 system distribution directory. This function also requires InfoPrint Server for iSeries.

    New support for LDAP Directories

    New support has been added to allow information about iSeries printers and NetServer print shares to be published into LDAP directories. This allows the user to write applications that query the LDAP directory for iSeries printer information such as a printer's location or capabilities. It also allows the user to configure iSeries printers directly on their Windows 2000 desktop by using the Add Printer wizard available in Windows 2000 and specifying that the information necessary to configure the printer be obtained from the Windows 2000 Active Directory.

    Unicode (UCS-2) Print Data Streams, Fonts, and Printers

    This support gives OS/400 users the ability to print Unicode (UCS-2) data on existing printer hardware. Support for Unicode printing is limited to Unicode code points that represent font glyphs. Any Unicode semantics are lost. Two methods are provided to achieve Unicode printing for DDS printer files:

    • Unicode data can be mapped to selected single-or double-byte EBCDIC encodings before placing the data onto spool.

    • Alternately the Unicode data can be spooled directly into AFP files to be processed by PSF/400 or Host Print Transform, using the AFP Unicode Font resource product (5799-GHJ) via a PRPQ available through your IBM representative.

    Enhanced Chinese Language Support

    OS/400 V5R1 provides enhanced Chinese language support. In addition to existing GB 2312 and GBK character support, OS/400 V5R1 is enabled to support 6,582 Unicode Extension-A and 1,948 non-Han characters (Mongolian, Uygur, Tibetan, and Yi). Customers who plan to use this enhanced language support must apply PTF SE01058.

    Extreme Support Personalized (ESP)

    The iSeries Extreme Support Personalized (ESP) initiative helps you easily manage your system, streamline your support, and reduce risk for your business. ESP is total solutions support, personalized for you in the form you need it. ESP involves support over the Internet, voice, and on-site support, along with support integrated into the product.

    Function previously announced and available via a PTF is now part of OS/400 V5R1.

    In V5R1, new ESP capabilities include Internet support and support integrated into OS/400.

    More Flexibility for Universal Connection

    IBM gives you more options for Electronic Customer Support (ECS) and Electronic Service Agent (TM) connectivity through Universal Connection. In addition to dial-up support over TCP/IP via ATT Global Network Services, with V5R1 the Universal Connection also supports Internet connections using a Virtual Private Network (VPN). This can be used for:

    • Direct Internet connection through the integrated modem with an Internet Service Provider (ISP) of your own choosing or through higher speed connections (T1, T2, Ethernet-attached cable or DSL modems).

    • Connection through a firewall via your Virtual Private Network (VPN) gateway.

    IBM offers connections through VPN to provide secure connections over the Internet.

    The Universal Connection enables a variety of ESP support tools that report inventories of software and hardware on your machine to IBM so you can get personalized electronic support based on your system data. This helps streamline your support process so you can spend more time running your business rather than maintaining your systems. You control the transmission of data to use (what and when it is sent) and we secure your customer data behind a firewall and use the data to appropriately provide you our world class, personalized support. Personalized data enabled by the Universal Connection includes:

    • Electronic Service Agent (TM) Inventory: Collects machine inventory of hardware, installed software, performance data, and fix levels. This information enables us to:
      • Simplify hardware and software upgrades
      • Assist you in the placement of new I/O features
      • Identify fixes that apply to your system
      • Provide you proactive advice on how you can avoid performance problems through an analysis of your current system performance

    • Electronic Customer Support (ECS): Allows you to electronically report problems and receive fixes that apply to your system from your iSeries.

    • Electronic Service Agent Problem Reporting: Allows for real-time monitoring of system hardware to automatically report critical errors and monitor for pending errors.

    The ability to configure VPN connections is enabled in Client Access Family Service Pack 1, available at:


    To take advantage of these capabilities, use the EZ Setup wizard at system setup, or use the ESP wizard, located under Management Central in iSeries Navigator.

    For additional detail on these new ESP functions, refer to:

    http://www.as400service.ibm.com/supporthome.nsf/ document/20965550

    Software Inventory Utility (SIU)

    SIU is a Web-based tool that simplifies some software upgrade orders. If the customer has Software Subscription and is registered through IBM Electronic Services, they can use SIU to directly order release upgrades based on the software subscription they have and the products they want upgraded.

    SIU is updated to reflect new or changed iSeries and AS/400e software. Refer to the availability schedule for product support updates and V5R1 support, and to learn more about SIU at:


    To use SIU, go to:


    Extensive Run-time Application Function:

    Operating System/400 is a functionally-rich platform for applications. Because it is enabled to run a wide range of applications, customers can easily grow their application base as their business needs grow. The extensive run-time function integrated into the OS/400 licensed program enables application programs created with the following languages, utilities, and support to run without the corresponding licensed programs:

    • ILE RPG for AS/400
    • RPG/400
    • IBM System/36-Compatible RPG II
    • IBM System/38-Compatible RPG III
    • ILE COBOL for AS/400
    • COBOL/400
    • IBM System/36-Compatible COBOL
    • IBM System/38-Compatible COBOL
    • ILE C for AS/400
    • SAA AD/Cycle C/400
    • System C/400
    • VisualAge C++ for AS/400
    • AS/400 BASIC
    • AS/400 Pascal
    • AS/400 PL/1
    • Structured Query Language (SQL) (part of DB2 Query Manager and SQL Development Kit for AS/400)
    • Query for AS/400
    • Data File Utility (DFU)
    • DFU and Query (part of System/38 Utilities for AS/400)

    For other separately-licensed programs, please refer to the Programming Requirements section for the specific program.

    Productive Application Development Environment:

    Operating System/400 includes many functions to assist in programming the system. These functions, along with the WebSphere Development Studio (5722-WDS), provide a productive application development environment. This environment supports a hierarchical approach to application development which can increase programmer productivity. The programming functions included in OS/400 are:

    • Interactive Debug

      These facilities increase programmer productivity by providing assistance in creation and maintenance of programs written in RPG/400, COBOL/400, C, C++, CL, and Pascal. Debugging of batch or interactive jobs can be done at any time; no special compilation is needed. Included are:

      • Breakpoints
      • Conditional breakpoints
      • Display/change program variables at breakpoint
      • Statement trace

    • Command Prompting

      Productivity of users executing commands is increased by command prompting. Each system and user command can be prompted for help with parameters. Parameters can be filtered based on values previously entered or predetermined parameters. Online help explains parameters and values.

    • Cross-Reference Facility

      Programmer productivity is increased by relieving the burden of cross-referencing. The system has the capability to cross-reference files to related programs and fields to related files.

    • Programmer Menu

      Using this menu, creation and maintenance of objects require minimal use of system commands.

    • Interactive Data Definition Utility (IDDU)

      IDDU assists in the creation of database files by creating IDDU data dictionaries, defining files, record formats, and fields. Programmer productivity is thus enhanced by using IDDU. It is an alternative to using Data Description Specifications (DDS). Easy-to-use functions within IDDU assist in the creation of files with existing field definitions.

    Integrated Language Environment (ILE):

    The Integrated Language Environment (ILE) is an architectural enhancement to the AS/400 system to meet the challenge of providing new function and greater application design flexibility. ILE exploits modern high-level language (HLL) technology while maintaining compatibility with existing applications.

    The AS/400 system's ability to integrate multiple applications from multiple independent sources is improved. Each application is allowed to define its own boundaries. Multiple applications within the same job each have their own commitment control in effect for data base management. This is accomplished through improved isolation in data and commit scooping.

    ILE provides a common framework for ILE-conforming languages in the areas of program activation, storage management, condition management, and program debugging. ILE also defines calling conventions for access to ILE bindable APIs and provides consistency and improved performance for interlanguage communication.

    ILE-conforming languages are:

    • ILE C for AS/400
    • ILE C++
    • ILE COBOL for AS/400
    • ILE RPG for AS/400
    • ILE Control Language (CL)

    New elements introduced by ILE:

    • ILE Program Binder

      The Integrated Language Environment introduces a new step in the application development process: binding. The purpose of binding and the Program Binder is to create program objects in such a way that efficient external calls may be performed.

      ILE compilers create modules (object type *MODULE), and the Binder is used to bind several modules together to form a program object. Note that these ILE program objects are logically as well as physically different from unbound program objects.

      Modules from any of the ILE compilers (C, C++, CL, COBOL, and RPG) can be bound together permitting applications to be created entirely in ILE which provides a greater level of environment consistency and isolation from other applications.

    • ILE Message Handling

      With ILE, the concepts of a message and an exception are unified; both are sent at the same time. Although this exception model is applicable to both ILE and non-ILE programs, the concepts of monitoring for and handling an exception are significantly different between the two.

    • ILE Source Debugger

      The ILE Source Debugger is used to debug all bound programs and service programs. It allows debugging to be done in terms of the source associated with a program. It cannot be used with non-ILE programs which must be debugged using the system debugger (for Old Program Model programs) or the EPM debugger (for Extended Program Model programs).

      A debugger API is provided, allowing compilers and other pre- processors which contribute to module creation to create debug view information associated with a module object. The API allows source debuggers to be built for the AS/400 system.

      The nonprogrammable workstation ILE Source Debugger is shipped with OS/400 and is therefore available to all AS/400 customers.

    • ILE Dynamic Screen Manager

      The ILE Dynamic Screen Manager (DSM) offers versatility and adaptability in generating screens during application execution with a set of bindable Application Program Interfaces (APIs). DSM enables ILE developers to create screens and windows dynamically, no longer requiring predefined static screens. This provides improved programmer productivity over using UDDS to perform low-level screen I/O operations and greater flexibility in controlling the screen appearance dynamically for the application. The DSM support falls into the following categories:

      • Low level services - provides a simple API interface to the UDDS commands, greatly simplifying applications that require low-level control of the screen.
      • Window services - supports the dynamic creation, drawing, selection, moving, and re-sizing of one or more windows on the screen. Data and fields can be defined inside the windows.
      • Session services - provides support for dynamically placing data inside an area of a window and scrolling the data, similar in concept to subfiles.

    Seamless OPM/ILE Debug and Watch Support:

    The OS/400 system debug support is enhanced to provide seamless debug across OPM (Old Program Model) and ILE (Integrated Language Environment) programs. OPM languages supported: COBOL, RPG, and CL. New support is also provided for OPM and ILE debug support to watch the contents of a variable and break when the variable changes.

    The seamless debugger enhancements include:

    • A single user interface (SUI) for debug of both ILE and OPM
    • A single API for debug of ILE and OPM
    • New source-level debug support for OPM programs:
      • Display Module Source screen to set and display breakpoints, turn on step, and display variables using source and listing views of the OPM program the same as ILE source debug support
      • System-supported Step Into and Step Over in OPM programs
      • Step Into OPM from ILE and into ILE from OPM (mixed calls)
      • Expression evaluation support similar to ILE
    • Seamless Watch support across OPM and ILE

    Enabling Technologies:

    OptiConnect for AS/400:

    OptiConnect for AS/400, a separate feature of OS/400, provides high- speed transparent access to data through fiber optic bus connections and performance enhancements to AS/400 Distributed Data Management (DDM). The major advantages of OptiConnect for AS/400 are realized by customers who are rapidly approaching system capacity limits, and/or who want to implement distributed database application servers within a data center or short-distance campus environment.

    With OptiConnect for AS/400 customers can offload the database application CPU cycles of up to 13 AS/400 systems. Customers wishing to implement distributed application servers can also benefit from using OptiConnect for AS/400.

    When used with the ObjectConnect for AS/400 facility, OptiConnect for AS/400 provides a high-efficiency migration aid for the AS/400 Advanced Series.

    The mechanism used by OptiConnect for AS/400 to access database files on connected systems is modeled after DDM. Just as DDM uses a DDM file and APPC communications to redirect file access operations, OptiConnect for AS/400 uses DDM files and a specialized transport service to redirect file access operations to a target system. Because OptiConnect for AS/400 operates only among systems sharing the same bus (connected with fiber optic cables), it can achieve transport efficiencies not possible with more general purpose, wide-area communications protocols.

    ObjectConnect for AS/400:

    ObjectConnect for AS/400, an integrated function of OS/400, simply and efficiently moves individual objects, entire libraries, or entire Integrated File System (IFS) directories from one AS/400 system to another over a standard communications connection or over a high-speed fiber optic bus. Systems can be connected via standard APPC (using APPN), TCP/IP communications lines (using AnyNet), or a fiber optic bus (using OptiConnect for AS/400). The economy of not requiring intermediate save file procedures and copies to distribution queues saves DASD and improves performance in a manner that is non-disruptive to system operations.


    • OS/400 Single UNIX Specification Functions Enable Application Portability:

      Through support of X/Open single UNIX specification (formerly Spec 1170) interfaces, AS/400 provides most of the commonly-used system interfaces used by commercial client/server applications today. The support includes functional enhancements that reduce the cost of porting applications to the AS/400 system.

      These functions allow AS/400 C application developers to build applications using system interfaces and C runtime functions that are portable to other operating systems.

      Functions included in OS/400 are:

      • environment variables
      • semaphores
      • shared memory
      • message queues
      • signals
      • process-related APIs including the "spawn()" function that provides an alternative to the "fork()" function (implementation based on POSIX 1003.4b draft 7)
      • miscellaneous C runtime functions

      Additional functions are available in the Common Programming API (CPA) Toolkit, a separate feature of OS/400:

      • Threads (implementation based on POSIX 1003.1c draft 4)
      • Thread support for ANSI C file I/O
      • Thread support for OS/400 Integrated File System (IFS) I/O
      • Thread support for sockets I/O
      • Thread support for sockets network functions

      The functions in CPA are based on industry standards from POSIX (Portable Operating System Interface) and the single UNIX specification. These standards enable source code portability of applications over platforms such as OS/400, OS/2, AIX, MVS and other, non-IBM, operating systems.

    • Distributed Computing Environment (DCE) Base Services for OS/400:

      DCE Base Services for OS/400, a separate licensed program offering (LPO, 5798-TBF), provides a comprehensive, integrated set of services to support client/server applications based on remote procedure call. DCE services include a network-wide security and naming facility for large scale distributed systems. DCE services enable a high degree of transparency across dissimilar platforms in terms of location in the network (services can be anywhere in the network), worldwide authentication (user identification and validation) and remote function invocation across system platforms.

      DCE Base Services for OS/400 provides the key functions of OSF's Distributed Computing Environment (DCE) Version 1.0.2. It provides function for building DCE RPC distributed applications including OSF DCE Time Services, Security Client functions, and Cell Directory Client functions. Client/server application enabling is simplified with automatic data conversion between unlike systems and location independence for client applications. TCP/IP communications protocol is supported.

      With these capabilities applications can transparently support the distributed client/server environments across a variety of systems including: OS/400, OS/2, AIX, MVS, and other, non-IBM, operating systems.

    • Pthread (POSIX-based) APIs:

      Pthread APIs, previously shipped as a separate product (PRPQ 5799-XTH), are now included in OS/400. They allow Business Partners or AS/400 application developers to take advantage of new system support for kernel threads. Creating an AS/400 thread is faster than creating an AS/400 job and is a more efficient way to spin off portions of application or server processing into parallel tasks.

      The Pthread APIs are based on open APIs described in the ANSI/IEEE Standard 1003.1, 1996 Edition (also known as ISO/IEC 9945-1: 1996) and the Single UNIX Specification, Version 2, 1997 standards.

    Optical Support:

    OS/400 Support for Plasmon G-Series - V5R3

    OS/400 V5R3 enhances support of Plasmon G-Series for IBM OS/400 optical libraries. The maximum number of drives supported increases from six to 12 and the bulk media loader and bar code features are enabled. These enhancements build off V5R1 and V5R2 support for Plasmon optical libraries with 14x (9.1GB) Magneto-Optical drives ranging from 104 slots to 638 slots providing storage capacities from 946GB to 5.8TB.

    • 3995 Optical Library Dataserver Support

      The 3995 Optical Library Dataserver is a direct-or LAN-attached device that can store up to 188GB of data on optical disks. Both Write Once Read Many (WORM) and Rewritable media are supported. It provides the high capacity, online storage required for image, data archive and retrieval, workflow, and microfiche replacement applications.

      Hierarchical File System (HFS) APIs and the Integrated File System (IFS), integrated in OS/400, allow for easy integration of optical storage into existing or new AS/400 applications using the 3995.

      In addition, objects may also be saved to and restored from the 3995 using system commands. HFS APIs support direct-and LAN-attached 3995s; IFS and the Save/Restore commands support only direct-attached 3995.

    • CD-ROM Drive Support

      CD-ROM technology is based on creating a CD-ROM master, and then stamping quantities at very low cost. Support of the system-attached CD-ROM drive allows AS/400 users and software vendors to support new applications or existing 3995 applications to access information stored on CD-ROMs, such as catalogs, educational materials, directories, and historical data. Applications can be written to access data directly from CD-ROM using Hierarchical File System (HFS) APIs or the Integrated File System (IFS).

      OS/400 Restore commands support reading from CD-ROM so any AS/400 object that can be restored can be distributed on this convenient and inexpensive media.

    High System Availability:

    The AS/400 system is one of the most reliable computers in the industry. However, to ease system management and minimize recovery, customers must follow a sound backup plan and choose some of the following functions as appropriate:

    • A backup power source is recommended to avoid or reduce system downtime in the event of utility power loss -- either a battery backup feature on those models where available, or a vendor-supplied uninterruptible power supply. The battery backup feature on the system unit supplies power for a few minutes; for continuous operation in the event of longer power outages, a vendor-supplied uninterruptible power supply should be used. A feature of the operating system allows notification to a user program of a loss of utility power.

    • Continuous Availability Clustering (V4R4) enables you to set up an environment with availability approaching 100% for your critical applications and your critical data. AS/400 high-availability business partners and ISVs complete the solution with easy to use cluster management, robust data resiliency, and resilient applications that take advantage of the new technology.

      AS/400 cluster architecture supports 128 nodes, using any combination of the existing OptiConnect WAN and LAN connectivity options to build the cluster.

      • OptiConnect hardware, fully supported as an ordered system feature, is an attractive connectivity method for high-end and mid-range models.

      • Ethernet and token-ring LANs are ideal for connecting low-end AS/400 models into the cluster.

      All systems are managed from a single workstation containing the high availability business partner cluster management application.

      OS/400 V4R4, or later must be installed on each node in the cluster.

    • Database file changes should be journaled to enable forward or backward recovery. "After" images are always journaled enabling forward recovery; an option is available to also journal "before" images enabling backward recovery. When a file is journaled, the system ensures that any changes to the data are written to the journal. It is possible to "mirror" a journal to a remote system. Possible benefits include:
      • Maintaining duplicate databases on separate systems
      • Reducing the time and effort required by customers to reconcile source and target databases following a system failure
      • Offloading journal save operations

    • Access paths changes should be journaled to enable faster recovery in the event of abnormal system termination. An access path being maintained at the time the system terminates is placed in an invalid state. Using the journaled changes, the system can quickly make the access path operational instead of requiring a rebuild of the entire access path.

      System-Managed Access Path Protection (SMAPP) provides automatic system journaling of access paths to try to achieve a user-specified time for access path recovery in the event of abnormal system termination. Target recovery time may be specified either system-wide or by ASP.

      With SMAPP enabled, the system estimates the time required to rebuild each access path and then automatically determines which access paths to protect to meet the user-specified recovery time. New access paths are automatically considered for protection.

      SMAPP provides the most efficient means of journaling because it journals only what is necessary to protect access paths and it takes advantage of this information to reduce both CPU usage and the I/O associated with journaling. Customers who have employed little or no journaling support in the past will benefit from a dramatic reduction in the time it takes to recover their access paths.

      Automating this chore and the associated responsibilities of creating and managing journals, allows the customer to concentrate on setting access path recovery policy and lets the operating system handle the burden of putting this policy into practice.

    • A single transaction may involve several database changes. Use of commitment control allows the application program to treat all changes for a transaction as a single group - to be either committed in the event of normal completion or backed out in the event of abnormal completion. An application programmer can easily provide for recovery at a transaction boundary using HLL statement to request commitment or rollback. Commitment control requires journaling.

    • User Auxiliary Storage Pools (ASPs) allow most object types to be confined to a user-defined set of DASD units. The objects can be recoverable quickly and completely after a DASD failure by reloading only the user ASP DASD units rather than the entire system.

      Once a user ASP is established, disk units may be added to it dynamically, without having to stop normal business processing, including mirroring or RAID-5 protection, if specified.

      Object types not supported in user ASPs include:

      • Spooled output files
      • Selected printer objects
      • Unfilled mail documents
      • Filed documents that do not reside in a folder

    • Checksum protection protects against loss of data in the event of a single disk failure within an ASP. The checksum facility automatically rebuilds the data on the failed disk unit for both system and user-defined auxiliary storage pools.

    • Disk mirroring, in most cases, allows the system to continue to operate after a disk unit or disk attachment failure occurs. Mirroring is specified on an ASP basis and requires duplicate disk devices of the same capacity. The entire system or one or more ASPs may be mirrored. If the entire system is mirrored, double the disk capacity is needed. When mirroring is started, the system automatically selects disk mirror pairs that provide the best path protection for the hardware configuration of the system. To increase the path protection, additional controllers and IOPs should be considered.

      Mirrored protection is an alternative for checksum protection on an ASP basis; IBM recommends only one of these methods be used on a given ASP. Mirrored protection does not remove the need for a proper backup strategy to protect against catastrophes or the possibility that both units of the mirror may fail. When one unit of the pair fails, the system is exposed to a failure until the repair action occurs and mirroring is resumed.

      Mixing of 9337 RAID and non-RAID DASD within a mirrored ASP is supported. DASD data loss protection for mixes of DASD that use RAID-5 array techniques, called "device parity", with other non-device parity DASD units is accomplished by allowing RAID DASD units to be configured into mirrored ASPs. When this is done, each of the non-RAID DASD units will have a mirrored partner while DASD with RAID will be self-protected. With this solution, the system will be able to continue running for any single DASD device failure. This OS/400 support is for the RAID protected DASD as implemented on the IBM 9337 Disk Array Subsystem.

    • Concurrent DASD maintenance is supported only on a properly-configured AS/400 9406 mirrored system or mixed mirrored and device parity protected system. With a proper configuration, it is possible for the system to operate successfully while experiencing a DASD failure and subsequent repair action. Diagnosis and repair may require active mirrors to be temporarily suspended. Some users may prefer to defer maintenance until all normal operations are completed. In some conditions (for example an IOP failure), the repair action requires that the system be powered off.

    • As of V4R3, concurrent maintenance is included for I/O cards, power, and other components contained in expansion towers. You can power off an expansion tower and add, remove, replace, upgrade, move, or swap a card or other component without stopping or powering off your system. Applications that use hardware resources in that expansion tower may need to be stopped and restarted. When the expansion tower is powered back on, new or changed hardware resources are automatically recognized and associated with existing resource names, if appropriate, to preserve existing configuration information and to allow applications to immediately use these resources without having to IPL.

    • Save-While-Active (SWA) allows one or more libraries to be saved while operations, including changes, continue against the libraries. During a short period of quiesced operation, a checkpoint is taken of all libraries being saved before the first save operation begins, so that all libraries are in sync.

    Systems Management:

    OS/400 system management functions include Simple Network Management Protocol (SNMP) APIs and access to additional management information.

    The new SNMP APIs for managing applications have the ability to manipulate management data via local or remote SNMP agents. Using AnyNet/400 support, information can be retrieved from systems on SNA or TCP/IP networks, thus making it easier to discover and manage potential problems anywhere within the network.

    An SNMP agent responds to an SNMP manager's requests. Most SNMP agents are extendable, and APIs are provided that allow the dynamic addition of sub-agents to show additional information needed to make good management decisions.

    OS/400 also supports a Host Resources Management Information Base (MIB) for hardware and software inventory of an AS/400 system. The APPN MIB includes APPN physical ports (APPC lines) and link stations (APPC controllers). These allow more AS/400 management information to be accessible to applications using SNMP.

    Independent Software Vendors (ISVs) can use the SNMP APIs to write AS/400 management applications to collect inventory data, monitor and change resources in the network and a variety of other tasks. They can also write sub-agents that allow access to additional AS/400 management information from management applications running on other platforms.

    Two APPC Applications Suite applications are included in OS/400: APING and APPC Remote Execution (AREXEC).

    • APING provides a simple way to test the connectivity between two APPN systems; it works like the TCP/IP PING command.
    • With AREXEC, commands can be run on another system supporting AREXEC, such as OS/2 or RS/6000, and commands from other systems can be run on AS/400.

    Electronic Customer Support:

    Electronic Customer Support is an integrated approach to helping users service and support single or complex systems and networks. It is menu-driven, supported by online help text, and includes locally available functions and access to remote marketing support systems and IBM service support.

    Simplicity and ease-of-use characteristics mean that configuring and supporting systems requires limited data processing knowledge or experience. Additionally, electronic customer support enables third party software and support organizations to support systems and networks from a central site, providing business solutions and partnerships that improve service and support to IBM AS/400 customers. The following are the systems management capabilities of electronic customer support:

    • Resource management and configuration management
    • Problem management, network management, and change management
    • Online and remote technical support
    • Electronic hardware and software service support
    • Remote marketing support

    Comprehensive Security for System Resources:

    The many levels of security available with OS/400 ease the job of system security management. The level of security is set simply using a System Value, as follows:

    • Password security (level 20): Passwords must be used. However, any user can perform any function.

    • Resource security (level 30): Passwords are required and object usage can be controlled. Users can be restricted to specific functions.

    • Resource security and operating system integrity (level 40): Passwords are required and object usage can be controlled. Users can be restricted to specific functions. Use of unsupported system interfaces is restricted.

    • Enhanced system integrity (level 50): Parameter validation into the operating system and restrictions on use of user domain objects. This enables the AS/400 system to operate at the C2 level of trust as defined by the US Government publication DOD 5200.28-STD, "Department of Defense Trusted Computer System Evaluation Criteria" (Orange Book).

    The OS/400 operating system is distributed with the security level set to 40.

    You should verify with solution providers that their applications will run at security level 40. If applications do not run at this level, a lower security level can be set. For considerations on moving to security level 40, refer to the Security section in the manual "Tips and Tools for Securing Your AS/400" (SC41-5300).

    Access to system resources is controlled by giving each user a tailored menu from which to select functions. It is also possible to secure individual system resources and user resources using a combination of public authority (for any user) and private authority (for specific individuals). Facilities are provided to:

    • Grant authority to a group of users who all have the same authority to a group of objects.

    • Exclude individual users from authority granted to the public.

    • Automatically sign off users after a specified period of inactivity.

    • Maintain an audit log of security-related events. Examples include:
      • Actions of a specified user
      • Actions against a specified object
      • Actions against spooled files
      • Actions against jobs
      • Invalid sign-on attempts
      • Attempt to access non-authorized objects
      • Changes in security-related System Values

    The discrete object and data authorities are:

    • Object Existence (user can delete the object)
    • Object Management (user can change the object description)
    • Operational (user can use the object)
    • Read (user can read existing data)
    • Update (user can update existing data)
    • Add (user can add new data)
    • Delete (user can delete existing data)

    Interfaces to System Functions:

    • Control Language (CL)

      The control language provides a consistent interface to all system functions. Thus, a programmer can tailor solutions using system functions without the end user or operator seeing what is being executed. The control language provides rich function and a consistent set of terminology and syntax. User-written commands can also be created. Most commands can be executed interactively, in a compiled CL program, or in a high-level language program. The ease of using CL and its rich function make it a productivity aid for programmers. CL programs allow the use of variables, error handling and access to the database. Programming functions include reading and writing to a display or database file, IF/THEN/ELSE logic, calling or being called from another program, and so on.

    • Data Description Specifications (DDS)

      DDS can be used to describe attributes of display, printer, database, and Intersystem Communications Function (ICF) files. These file descriptions can then be used in high level language programs.

    • User Interface Manager (UIM)

      Most OS/400 display panels are coded in a tag-based language which enables description of the content of a panel without specifying the format of the panel; the UIM controls the format. This can enhance ease-of-use by enforcing consistency in panel appearance as well as matching the "look and feel" of most IBM-supplied AS/400 panels. The UIM tag language supports displays and printers, and the resulting panel groups can be used by all AS/400 high-level languages, including Control Language (CL), using CALL-level interfaces.

      The UIM supports four common panel types: menus, information displays, list displays, and entry displays, and for these provides consistent placement and format for many panel elements, such as:

      • Panel name
      • Panel title
      • Separator lines
      • Column headings
      • Entry fields
      • Command line
      • Message line
      • Function keys
      • Pop-up windows
      • Menu bars
      • Pull-down menus

      It also provides automatic and consistent use of:

      • Color
      • Underline (input fields)
      • Reverse image (error fields)
      • Date and time
      • Number pages (printer output)

    • Consistent Program Structure

      Programs can be written in either a high-level language or control language. Programs written in one language can call and pass parameters to a program written in the same or a different language. All system and user programs are re-entrant, and each user executes the same "read only" object code of a program with the system maintaining separate, unique work areas for each job and each program within the job. In addition, only those portions of the object code actually in-use are required to be in main storage. These two factors can increase the number of programs concurrently operating in the available main storage.

    • Query Management

      The SAA query common programming interface (CPI) can be used to import and execute queries generated in other SAA environments. Query management may also be used to imbed query and report writer function into AS/400 applications or send them to other SAA environments for execution. Query management is a productivity aid for the application programmer.

    • Procedures Language 400/REXX

      REXX is an easy language to learn. It facilitates writing clear, structured, interpreted procedures. REXX can provide the data manipulation and procedural logic framework for OS/400 commands and conventional calls to other high-level language and CL programs.

      The REXX interpreter implements the SAA level 1 definition of Procedures Language and the SAA level 2 definition except for native language support for stream I/O. Thus, it provides a more portable procedural alternative to OS/400 CL programming. It reduces programming investment for users who require applications that execute in several SAA environments. REXX also helps protect the programming investment for users who have already developed REXX procedures for other SAA environments. They simply replace embedded environment commands with OS/400 commands to port procedures to an AS/400 system. Procedures Language 400/REXX also supports DBCS for Asian language users.

    • Sort

      The sort utility supports sorting and merging of database files. Selection and sorting using the sort utility has performance advantages over the use of database access paths for certain applications. The sort utility can

      • Sort up to eight input files to produce a single output file containing record images (full record sort).
      • Sort a single physical database input file with arrival sequence to produce an output file of four-byte binary relative record numbers that refer to the input file (address sort).
      • Sort files and produce accumulated totals (summary sort).
      • Copy up to eight input files to produce a single output file with records in the same order as they were encountered in the input files (merge).

    • Application Programming Interfaces (APIs)

      There are literally hundreds of OS/400 APIs providing access either to functions and data not available through any other interface, or levels of performance not available through other interfaces. These CALL-level interfaces are intended for use by independent software vendors and IBM Business Partners whose applications require these functions and data. A complete list is in "System API Reference", SC41-5801.

    • Double Byte Character Set Support

    • Euro Currency Support

      AS/400 can input, display, print, and process the euro currency sign for both the host and PC client computing environments. This support includes, but is not limited to the addition of:

      • Euro country extended code pages (CECPs) and CCSIDs.
      • Euro keyboard types, including device configuration and device controller changes.
      • Euro font and glyph support.

      Updates to external display, print, and client function may need to be obtained from other vendors.

      This phase of euro support is only for those countries that use the "Latin 1"-based alphabet. This includes those countries initially participating in the European Monetary Union and other selected countries.

      For the latest available information and a roadmap to euro currency sign support on the AS/400, please see the following Web site:


    Printed Output Support:

    Print Services Facility For OS/400 - V5R3

    Print Services Facility for OS/400 (PSF/400) is the integrated AFP (Advanced Function Presentation) system manager and IPDS (Intelligent Printer Data Stream) printer driver for IBM eServer iSeries. V5R3 enhancements include continued Unicode implementation, support for TruType and OpenType fonts, capabilities to import network standard image and graphic formats directly into IBM eServer iSeries documents, and enhanced support for full color. Both OS/400 and PSF/400 are enhanced to add these functions. The result is an output architecture that supports a much broader range of document content and function.

    PSF/400 V5R3 also supports new IBM eServer iSeries printers.

    Print Services Facility implements phase II of Unicode. Unicode is the emerging text encoding standard that uses a expanded 16-bit data address to represent nearly all of the characters in the all the world's languages in one interface. Phase II of the Unicode comprises most of the world's languages except those that require complex text support. With Unicode, applications that require multiple languages are greatly simplified.

    With V5R3, TrueType and OpenType fonts can be specified directly in IBM eServer iSeries output. These fonts can be cataloged in the Integrated File System and referenced with the FONTNAME keyword. The InfoPrint Fonts product (5648-E77) has a font installer program that enables simple installation of TruType and OpenType fonts. AFP, TruType, and OpenType fonts can be intermixed on the same page. The ability to use TruType and OpenType fonts greatly expands the universe of fonts available for IBM eServer iSeries applications while providing for flexibility and consistency among various organization documents.

    Full color and image capabilities are extended with V5R3. Full process color debuted in V5R2 with the implementation of high- resolution, highly-compressed AFP color (called IOCA Function Set 45, or FS45, of the AFP image object architecture). With V5R3, PSF/400 supports the new OS/400 capabilities to import network or Web standard graphics objects directly into IBM eServer iSeries documents. These graphic or image object types reside on the Integrated File System and are referenced with the AFPRSC keyword. The ASCII formats supported are:

    • JFIF (JPEG File Image Format, commonly referred to as jpeg)
    • TIFF (Tag Image File Format)
    • EPS (Encapsulated Postscript)
    • EPSTR (EPS with transparency)
    • PDFSPL (PDF single page)
    • PDFSPOTR (PDF single page with transparency)
    • PCLPO (PCL page object)

    The AFP objects types that can be imported directly from the Integrated File System are:

    • BCOCA (AFP barcode object)
    • GOCA (AFP graphics object)
    • IOCA (AFP image object)

    These object types are stored in a new structure within the AFP data stream called an object container. Object containers support a mixture of EBCDIC and ASCII-encoded data within the same document or report.

    Document content within object containers also integrates with the PDF services support in InfoPrint Server for IBM eServer iSeries (5722-IP1). For example, a full color logo can be pulled directly from an Integrated File System directory into an IBM eServer iSeries document then passed to InfoPrint Server and converted into PDF for distribution.

    Support for the following IBM eServer iSeries printers (as IPDS printers) is added with PSF/400 V5R3:

    • IBM InfoPrint 1312 Printer
    • IBM InfoPrint 1332L Printer
    • IBM InfoPrint 1354 Printer
    • IBM InfoPrint 1354L Printer
    • IBM InfoPrint 1372 Printer
    • IBM InfoPrint Color 1354L Printer
    • IBM InfoPrint 2060ES Printer
    • IBM InfoPrint 2075ES Printer
    • IBM InfoPrint 2090ES Printer
    • IBM InfoPrint 2105ES Printer
    • IBM 4247 IPDS

    • Integrated Print Support

      This integrated operating system function supports printing of text, images, graphics, bar codes, electronic forms, multiple fonts, logos, signatures, and more, thus providing the basis for business solutions like business reports, preprinted forms, customer statements and invoices, and letters. Double Byte Character Set (DBCS) documents that enable printing of Chinese, Korean, Japanese, or Thai characters are also supported.

      OS/400 supports IBM and non-IBM printers, which have a wide variety of price, function, speed, and use. Flexible connectivity options allow them to be attached:

      • to the system
      • directly to a Token-Ring or Ethernet LAN
      • to a client (e.g., personal computer)

      OS/400 can generate SCS, IPDS, AFPDS and S/390 line data natively, based on a user specification. The SNA Character String, or SCS datastream, is a text only data stream often used for printing job logs, program listings and OfficeVision for AS/400 documents. The IPDS and AFPDS datastreams provide support for graphics, barcodes and advanced page formatting. In addition, AFPDS allows natively-generated data to be printed using all points addressability (APA), host-resident downloadable fonts, and support for overlays (e.g., electronic forms) and page segments which can be merged with user data for printing.

      OS/400 also provides facilities to allow system and client applications to create a spool file containing a user-defined datastream for printers whose characteristics are unknown to the system. These USERASCII print files can be directed to local or remote printers.

      Utilizing AFP and SCS print drivers for Windows and OS/2, client applications can generate print output destined for system and production printers. OS/400 can also act as a print server to System/370 or System/390. This includes support of AFPDS and 1403 data for printing on an AS/400 system.

    • Host Print Transform

      Most printers are designed to work with a specific datastream, so OS/400 includes a function to automatically transform the program generated datastream to that required by the printer to which it is sent. It is not necessary for the application to generate the correct datastream; the system will automatically transform it as necessary at print time.

      Host Print Transform (HPT), a key component of the AS/400 print server strategy, provides the ability to transform host-generated EBCDIC datastreams to ASCII-based datastreams accepted by many popular laser and impact printers commonly found in client environments. The transformation is based on user-definable workstation customization objects which provide a high degree of flexibility and control over the output generated. Workstation customization objects are provided for over 125 popular IBM and non-IBM ASCII printers.

      The following datastreams can be transformed into ASCII:

      • SCS, including imbedded IPDS images
      • AFPDS, including barcodes, images, overlays, and page segments, can be transformed into:
        • Hewlett Packard PCL
        • Lexmark PPDS
        • HP LaserJet TIFF Packbit

      An API brings the capabilities of Host Print Transform to the AS/400 application developer. For example, an application program can utilize the HPT API to convert an AFPDS spoolfile to a TIFF image, and then present this image on a IBM 3489 InfoWindow II display.

      OS/400 HPT has been enhanced to generate the ASCII datastream for DBCS printers from a DBCS SCS datastream. Supported ASCII datastreams are IBM's PAGES, IBM non-PAGES, and Epson's ESC/P, Canon LIPS3, and NEC 201PL. The IBM PAGES datastream can also be printed from the AFPDS datastream. The ASCII datastream can be directed to LAN printers utilizing TCP/IP Line Print Requester (LPR) support. ASCII DBCS datastreams spooled via the TCP/IP Line Print Daemon (LPD) can also be directed to LAN-and workstation-attached printers without conversion.

      Workstation customization objects are provided for a number of popular DBCS printers from various vendors, such as IBM and Epson, and support various languages including Japanese, Simplified Chinese, Traditional Chinese, and Korean. These objects can be modified to support unique language or datastream requirements.

      In V5R1 Host Print Transform has been enhanced to support EBDIC data streams in spooled files containing Unicode-encoded data. With V5R2, Host Print Transform supports spooled files with True Type fonts, allowing users to take advantage of the large selection of True Type fonts available from various sources. With V5R3, Host Print Transform supports spooled file with languages that use complex text such as Arabic, Hind, and Thai.

    • Print Spooling Support

      Printing, a relatively slow process, can be done most efficiently when it is done independently from the application that created the output. Spooling (Simultaneous Peripheral Operations Online) provides this support with the following functions:

      • Output can be queued until a printer is available, with user specified priority
      • Print writers transfer output from queue to printer
      • Spool separator page format can be controlled by the user for specific printers
      • Spool files can be held, released, deleted, re-prioritized, moved from one queue to another, and displayed (EBCDIC-based files only)
      • Spool files can be sent to output queues on other AS/400 systems
      • User can specify form type, number of copies, and subset of pages to print
      • Spooling can be controlled from any work station and can be established as an environment for an individual
      • With AS/400 Client Access, a separately-licensed program (5769-XW1 or 5769-XY1), spool files can be manipulated from a client workstation within a native client environment
      • System security controls access to spool control functions, output queues and devices.
      • Spooling environment can be started automatically when the system is started
      • Printing can be restarted at a specific page in the event of printer failure
      • Printer Load Balancing

        Local and remote output queues permit more than one active writer, allowing spooled output on one output queue to be printed on multiple printers. In addition, a limit can be placed on the size of spooled files printed during a specified time period. With these features, large print jobs can be deferred to print during non-peak hours.

        With V5R3, spooled files and output queues can be placed into an independent auxiliary storage pool (independent ASP).

    • Network Printing Support

      Distributed print support provides connection to LAN-attached ASCII printers and support for Advanced Function printers. It also facilitates the distribution of printed output throughout AS/400 networks.

      The AS/400 system provides a seamless path for customers to direct printed output through an AS/400 network and to other print servers. An output queue can be specified as "remote", and output spooled to a remote queue is automatically sent to the specified destination system for printing. SNA or TCP/IP protocols (LPR/LPD) can be used to transport the spool file and its attributes to the remote system.

      These remote print functions are integrated with the display passthru function to allow the customer to specify an output queue on the local system for use during the session. Spooled output generated at the target (remote) system is automatically sent to the output queue on the source (local) system for printing.

      Output routed to IBM mainframe computers, which function as print servers, can be sent directly to a specified printer. The job class and a Forms Control Buffer (FCB) can also be specified from the AS/400, greatly improving the AS/400 systems capability as a System/390 print client.

      Most of today's printing is done on printers attached directly to the LAN, so that they can be shared between client, LAN and AS/400 applications. LAN attached printers can also support high-volume electronic printing. Output files can be sent to:

      • Client Access/400 attached ASCII printers
      • LAN attached IPDS printers directly, with complete print management
      • LAN attached ASCII printers
      • IPDS and PCL printers attached to WARP and AIX Servers
      • Printers managed by the Netware integrated Server
      • Other printers using Network Print Server APIs.

    • Print Services Facility for AS/400 (PSF/400)

      For many businesses today, the printed output from an application program is the primary way that business communicates regularly to its customers. Whether it's a well-organized, easily readable customer statement, or an insurance policy with customized information for each client, the printed document plays an important role in building and maintaining customer satisfaction.

      IBM's Advanced Function Printing (AFP) is an architecture that integrates high-function page printers and print software to:

      • Enable state-of-the-art documents that can give your business a competitive edge with electronic forms

      • Provide sophisticated print formatting capabilities external to application programs

      • Replace traditional labor-intensive print operations with a system managed process

      Print Services Facility for AS/400 is the AFP system software for AS/400 printers that use the Intelligent Printer Data Stream (IPDS) protocol. It has been an integrated component of the OS/400 operating system since V1R2. PSF/400 is functionally integrated into the operating system, but is enabled through a separately-billable feature of OS/400. PSF/400 allows AS/400 users and applications to take full advantage of IPDS printer capabilities, including:

      • Replace pre-printed forms with electronic forms, called overlays

      • Format multiple pages of output, or multiple records, onto a single printed page

      • Include compressed image data from programs such as Workfolder Application Facility/400 and Facsimile Support/400, and have the images decompressed and printed by an IPDS printer

      • Download fonts from AS/400 host libraries to printers for a greater choice of type styles, or to ensure font consistency across printers

      • Process AFP applications that have been sent to the AS/400 from S/390 and other environments.

      Access to many AFP capabilities has been incorporated into the familiar AS/400 print interfaces -- Printer Files and Data Description Specifications (DDS) for Printer Files. Using Printer File parameters you can:

      • Include an electronic form on each page of a job, including different forms on the front and back sides

      • Specify the names of a Page Definition or Form Definition to be used to format the print job. Page and Form definitions are the AFP resources used to format AFP print output in S/370 and AIX. Page and Form definitions are processed by PSF/400 from the spooled file, and so are completely external to the application program.

        Capabilities that have recently been added to AS/400 Page Definition processing include the ability to specify fields of data to be generated as IPDS barcodes, and the ability to position print lines relative to one another on the printed page. This give applications that produce line data much greater flexibility in report formatting, and lets the application data drive the format.

      • Select media handling options such as paper drawer, output bin and duplex printing

      • Specify that output can be saddle-stitched, edge-stitched, or corner-stapled

      • Print 2, 3, or 4 pages per side while by-passing OS/400's automatic page size reduction. This allows you to take advantage of printers with larger paper sizes than 8 1/2 x 11 inches.

      Using DDS to format application output you can:

      • Position "floating" overlays and page segments anywhere on a page to create sophisticated customer-oriented documents
      • Include boxes and lines dynamically anywhere in the output
      • Use "Invoke Medium Map" to change paper handling options such as duplex/simplex, N-up (multiple pages per side) formatting, page rotation, selection of electronic forms, and input paper drawers anywhere in the print job
      • Select different fonts and text rotations for different fields of data
      • Switch between simplex and duplex printing within a spooled file
      • Force printing on a new sheet of paper anywhere in a spooled file
      • Direct pages of a spooled file to a specific output bin
      • Include tabbed insert pages from a finisher anywhere in the spooled file available through the DRAWER keyword
      • Specify z-fold options for any page within a spooled file
      • Include an overlay and specify the orientation in which the overlay is printed

      PSF/400 also provides data stream transforms and AFP print resource management to ensure that applications and their AFP resources print consistently on all of the printers managed by PSF/400. PSF/400 manages all printers whose device descriptions specify a device type of *IPDS and AFP(*YES). PSF/400 can transform and print the following data streams and formats on the AS/400 system:

      • IBM's Mixed Object Document Architecture (MODCA) data stream, also called the Advanced Function Printing Data Stream (AFPDS)
      • EBCDIC line printer data generated from a S/390 environment.
      • SNA Character Stream (SCS) and IPDS
      • Postscript Level I (plus color)
      • Tag Image File Format (TIFF)
      • Bitmap (BMP)
      • Graphics Interchange Format (GIF)

        PSF/400 includes an automatic interface to print data stream and image transforms in OS/400. PSF/400 detects the input data stream and transforms it for printing on any AFP printer.

      PSF/400 supports the entire family of IBM IPDS printers and IPDS printers from other vendors. PSF/400 is required to provide full function support for the following advanced printers:

      • IBM 3112, 3116, 3812, 3816, 3912, 3916, 3930, and 4028
      • IBM Network Printer 12, 17, and 24
      • IBM 4224, 4230, 4234, 6400, 6408, 6412, and 4247
      • IBM 3130*, 3160*, 3820*, 3825*, 3827*, 3828*, 3829*, 3831*, 3835*, 3900*, 3935*, InfoPrint 20*, InfoPrint 32, InfoPrint 60*, InfoPrint 3000*, and InfoPrint 4000*

        * Require PSF/400 to attach to the AS/400 system.

        The above list includes printers that can attach to AS/400 via Twinaxial, SNA or TCP/IP. For detailed information about printer attachments refer to the Sales Manual information for each printer.

      AS/400 products that complement PSF/400 for developing AFP applications include:

      • Advanced Function Printing Utilities/400, licensed program 5716-AF1. AFPU provides the ability to print AS/400 database files in various formats with a wide range of fonts and bar codes on printers driven by PSF/400, and to create AFP overlays.

      • AFP PrintSuite for AS/400, program offering 5798-AF4. PrintSuite is a collection of AFP application enabling tools that allow programmers and non-programmers to enhance the formatting of application output external to the application program logic.

      • IBM AFP Font Collection, program product 5648-B45. Font Collection is a comprehensive suite of AFP fonts and font editing programs that allow customers to select from among the thousands of typefaces available in Adobe Type 1 format for their print application formatting.

      For detailed information about AFP support in AS/400, refer to the following documents:

      • AS/400 Printer Device Programming (SC41-3713)
      • AS/400 DDS Reference (SC41-3712)
      • AS/400 Printing III Redbook (GG24-4028)
      • AS/400 Printing IV Redbook (GG24-4389)
      • AS/400 Printing V Redbook (SG24-2160)
      • Guide to Advanced Function Presentation (G544-3876)
      • AS/400 Guide to AFP and PSF (S544-5319)

    Print Services Facility/400 Update

    with V4R5, customers ordering any of the four OS/400 priced features for Print Services Facility/400 (PSF/400) are shipped a CD-ROM (LK2T-9270) at no additional cost that provides consistent fonts for printing on 240 dpi or 300 dpi printers using raster fonts, or on any AFP printer that supports outline fonts. Included on the CD-ROM are Helvetica and Times New Roman typographic typefaces. The typefaces provide support for high quality printing with international language capabilities, including support for the euro currency sign. Double-byte fonts for printing Japanese, Korean, Simplified and Traditional Chinese are not on the CD-ROM.

    Supported Protocols and Networks:

    Following is the list of protocols and networks supported by the Operating System/400. This support provides a basis for integration of customer business systems, and thus, business solutions.

    • Integrated Services Digital Network (ISDN) (support withdrawn in V5R3)
    • T1/E1/J1 and Fractional T1 Networks (high bandwidth communications)
    • IBM Token-Ring (IEEE 802.5 and 802.2) LANs
    • FDDI/SDDI LANs (100 Mbps medium)
    • Ethernet Version 2 or IEEE 802.3 LANs
    • Virtual Ethernet
    • Asynchronous Transfer Mode (ATM) (withdrawn in V5R3)
    • Asynchronous Communications (Async)
    • Binary Synchronous Communications (BSC)
    • Synchronous Data Link Control Communications (SDLC)
    • X.21 Networks
    • OptiConnect

    Details about the protocols and networks available with OS/400 follow:

    • Integrated Services Digital Network (ISDN)

      AS/400 communications support includes integrated services digital network (ISDN) basic rate interface (BRI) adapter, which can support two independent 64 kbps full duplex data channels and one 16 kbps signalling channel. The ISDN BRI adapter implements the ISDN data link control (IDLC) protocol. X.25 communications over the ISDN B-channel is also supported.

      Support for ISDN is withdrawn in V5R3.

    • T1/E1/J1 and Fractional T1 Networks

      T1/E1/J1 and Fractional T1 Network connections are supported using the V.35 line adapter and six-line communication controller at speeds up to 640k bps for one line per controller; 512k bps each for two lines per controller and 384k bps each for three lines per controller. SDLC protocol is supported allowing APPN and SNA networks to be connected. V.35 input is required on DSU, MUX or CBX type DEC equipment interfacing to T1 Network facilities.

    • IBM Token-Ring, FDDI/SDDI, and Ethernet/IEEE 802.3 LANs

      The AS/400 system directly connects to the IBM Token-Ring LAN (either 4 or 16 Mbps), to FDDI/SDDI LANs (Fiber Distributed Data Interface/Shielded - twisted - pair Distributed Data Interface), and to Ethernet/IEEE 802.3 CSMA/CD LANs.

      AS/400 LAN attachment features are configured and appear to the system as types of communication lines. OS/400 supports multiple concurrent SNA communication sessions with a variety of IBM products over both LAN types. TCP/IP sessions are also possible over both IBM Token-Ring and Ethernet/IEEE 802.3 LANs

      The maximum number of SNA controllers supported per LAN attachment on each system is 256.

    • Virtual Ethernet

      Virtual Ethernet is an internal Ethernet network used to connect partitions in an LPAR environment. This allows applications in one partition to communicate with application in a different partition without having the data physically exit the system.

    • Async, BSC, and SDLC Communications

      BSC, Async, and SDLC support provides the user with the ability to communicate with other systems and devices that use the comparable protocol. Asynchronous communications to other systems and to Async/ASCII devices such as terminals, printers and plotters requires user-written application programs. Async support may be run on an X.25 packet-switched data network. An integrated PAD (packet assembler/disassembler) is provided that supports CCITT recommendations X.3, X.28, and X.29. Async communications supports full-duplex operation.

    • X.21 Networks

      The AS/400 system provides an interface for attachment to an X.21 leased or circuit-switched network using either X.25 or SDLC communications.

    • X.25 Networks

      The AS/400 system provides an attachment and support for full- duplex, X.25 packet-switched data networks, using either:

      • Non-switched line, through an X.21 or X.21.bis (V.24 or V.35) interface, or
      • Public switched telephone network (PSTN) facilities, on a V.25 bis autodial or V.25 bis/RS-366 parallel autodial interface. Bandwidths up to 256 Kbps are supported with a maximum packet size of 4096 bytes.

        The OS/400, when used in conjunction with the AS/400 X.25 Communications Feature, is certified by the Department of Defense Data Network (DDN). The X.25 packet network is used by the TCP/IP protocols.

    • OptiConnect

      The iSeries system supports an OptiConnect bus that provides a high speed connection between iSeries systems over the OptiConnect bus.

      Network Management Facilities:

      Several communications and systems management functions are available to manage the AS/400 system. Some are integrated into the Operating System/400 and some are separately-priced features. These functions help manage and control local systems and distributed systems that may operate within a network controlled by a host System/370 or by another AS/400 system.

      Functions available for the AS/400 system are:

      • Systems Management in TCP/IP Networks
      • Alerts Support to NetView, System/36, System/38, AS/400
      • IBM Token-Ring Network Management Support
      • Distributed Host Command Facility (DHCF)
      • Link Problem Determination Aid (LPDA)
      • Distributed System Node Executive (DSNX)

      More detail about network management facilities for AS/400 follow:

      • Systems Management in TCP/IP Networks

        The protocol for systems management used in TCP/IP networks is Simple Network Management Protocol (SNMP). It is the industry standard for managing networks in the worldwide TCP/IP Internet environment. Support for SNMP protects the customer's investments in industry standard management applications and allows the AS/400 system to interoperate with other manufacturers' systems management products.

        Elements provided with OS/400 include SNMP agent, SNMP framework, and TCP/IP protocol support. The TCP/IP communications protocol includes network management capabilities to support SNMP control.

        The SNMP management function is split between two kinds of entities, named the "manager" and the "agent." The SNMP agent function runs on the AS/400 system and allows it to be managed by network management stations that have implemented the SNMP manager function.

        The OS/400 SNMP agent provides configuration, performance, and problem management data concerning TCP/IP to an SNMP manager.

        Management Information Bases supported include:

        • MIB-II
        • Transmission Groups
        • APPN
        • Private

        The SNMP framework provides support for SNMP applications on the iSeries system, including:

        • Management applications that access SNMP management data throughout the network
        • SNMP sub-agent support, which provides the ability to dynamically add sub-agents that can supply additional management data
        • Networking software management and system setup. Several TCP/IP management enhancements in V5R1 give the network administrator more control when monitoring their TCP/IP network and troubleshooting networking problems. The enhancements include:
          • A graphical version of network status (NetStat) that includes the ability to map a socket connection to a list of jobs for that connection.
          • The ability to trace the route a TCP/IP packet will take through the network (TrcRoute - includes a TrcRoute CL command).
          • Address resolution protocol (ARP) cache monitoring.

      • Alerts Support to NetView*, System/36, System/38, AS/400

        Alerts are messages that comply with System Network Architecture (SNA); they are sent from systems within a communications network to a central management site, called the problem management focal point. Alerts carry information about a problem and suggest corrective actions to the problem management focal point operator. Alerts can be used to monitor unattended systems and devices and control system resources.

        Alerts may be sent to other AS/400 systems, System/36s, System/38s or System/370s. An AS/400 system can act as the generating and sending point for an alert, as a node that forwards alerts to the focal point, or as the problem management focal point that receives alerts.

        When an AS/400 system is the problem management focal point for a network, the operator can display, delete, receive, forward, log, or hold alerts for forwarding. When operating within a network with a System/370 host system, alerts may be forwarded to the NetView(TM) licensed program on the System/370, which has focal point capabilities.

      • IBM Token-Ring Network Management Support

        This integrated support aids the AS/400 operator in managing an attached token ring local area network. The support provides monitoring and active management for the token ring. Functions include:

        • Notification of hard (permanent loss) or soft (impending loss) errors
        • Query of individual LAN station for profile information
        • Force a station off the ring if an unacceptable number of errors are occurring because of that station.
        • Display and print of LAN topology.
        • Generation of alerts for LAN errors.
        • Display of the table for soft error conditions

        Networks of multiple token ring LANs (bridged networks) may require more extensive network management support than these functions provide.

      • Distributed Host Command Facility (DHCF)

        The OS/400 distributed host command facility allows the users of display stations of a System/370, using the host command facility (HCF) companion program under ACF/VTAM to:

        • Interactively operate and control an AS/400 system as if attached as a remote AS/400 work station
        • Use the operations and service facilities of any AS/400 system in the HCF/DHCF network to do remote problem analysis on any AS/400 system in the network
        • Access and control applications, for which they have proper authority, on each AS/400 system in the network
        • Perform problem determination and error diagnostics on any AS/400 system in the network. This includes interactive examination of the system's error log, running and displaying storage dumps and traces, and looking at and responding to unique system messages from the AS/400 system.

      • Link Problem Determination Aid (LPDA)

        The OS/400 LPDA and LPDA-2 functions provide data about network components to aid in network problem determination. These architectural network commands are issued to determine which of the various network components might be causing an error. The commands include requests for modem and line status and receive tests for IBM signal converter products (modems).

        The LPDA-2 commands are an extension to the standard LPDA commands. They can be initiated concurrently with other activity on the line. The commands include transmit and receive test and line analysis. The results of the LPDA-2 tests may be presented to the user's display or printer. The data presentation is similar to those panels available on the System/370 NetView(TM) licensed product.

      • Distributed Systems Node Executive (DSNX)

        The OS/400 distributed systems node executive (DSNX) support allows the AS/400, System/36 and IBM PCs and PS/2s to be part of a SNA network in which distribution of data--including files, programs, IBM software, procedures--is centrally controlled by the System/370 focal point. The controlling System/370 product is NetView* Distribution Manager (NetView/DM). Interaction between NetView/DM and DSNX provides the control functions required for change management within a network of distributed systems. AS/400 DSNX support operates with either NetView/DM on MVS or DSX V3R2 on VSE.

        The interaction of NetView/DM and DSNX provides functions such as:

        • Retrieval of data from the AS/400, System/36, PC, or PS/2
        • Distribution of data objects (files)
        • Distribution of user applications and application changes (programs)
        • Distribution of IBM software (microcode, operating system and licensed program products)
        • Messages from NetView to system operator
        • Installation of all software and data on the distributed systems
        • Distribution of jobs to the distributed systems
        • Job initiation on the distributed systems

        The AS/400 DSNX can act as an end node (the target system for an action) or as an intermediate node (gateway) between NetView/DM and other AS/400 systems, System/36s or IBM PCs and PS/2s. When acting as an intermediate node, AS/400 can distribute to a list of other systems on the network.

        Once AS/400 DSNX support is activated, no operator interaction is required on the AS/400. The NetView/DM host system controls all transfers of information between the distributed systems and the NetView/DM host.

        AS/400 DSNX support allows for either synchronous or asynchronous connection to the NetView/DM host. When acting as a synchronous node (referred to as DIRECT NODE support), the AS/400 keeps the line active (session established) until all requests are complete on the AS/400.

        Centralized problem management is also available using System Manager for iSeries, a separately-licensed program, (5722-SM1).

      Communications Facilities:

      Following are the supported communications facilities in OS/400. These facilities protect customer investment in equipment and applications by enabling communications between diverse resources.

      • TCP/IP Support
      • X.21 Short Hold Mode (SHM) and Multiple Port Sharing (MPS)
      • Remote Work Station Support
      • Intersystem Communications Function
      • Advanced Peer-to-Peer Networking (APPN)
      • Dependent Logical Unit Requester (DLUR)
      • Advanced Program-to-Program Communication (APPC)
      • SNA Upline Facility to System/370 IMS and CICS Hosts
      • Binary Synchronous Communications Equivalence Link (BSCEL)
      • ICF Retail Communications Support
      • ICF Finance Communications Support
      • Non-ICF Finance Communications Support
      • SNA Distribution Services (SNADS)
      • SNA Primary Logical Unit 2 Support
      • SNA/Management Services Transport
      • Distributed Relational Database Support
      • Object Distribution Facility (ODF)
      • Display Station Pass-through
      • Distributed Data Management (DDM)
      • SNA Passthrough
      • IBM Network Routing Facility (NRF) Support/400
      • Autodial Support
      • 3270 Device Emulation
      • 3270 SNA API Support for IBM 3278 Model 3, 4, and 5
      • ISDN Support (withdrawn in V5R3)
      • 5394/5494 SNA Backbone Support
      • File Transfer Support
      • Interactive Terminal Facility (ITF)
      • SAA Common Programming Interface for Communications (CPI-C)

      Details about the communications facilities available with OS/400 follow:

      • TCP/IP Support

        TCP/IP for expanding Internet/intranet solutions:

        TCP/IP is fundamental to the new network computing paradigm and much of the new AS/400 e-business infrastructure runs exclusively on TCP/IP including Lotus Domino, Java, Web serving and IBM Network Stations. AS/400 has excellent TCP/IP support built into its operating system and recent AS/400 TCP/IP enhancements make AS/400 an even more powerful e-business server.

        Enterprise-class TCP/IP for real business networks:

        TCP/IP has become an extremely popular protocol and can be regarded as the de facto standard for computer networking. AS/400 comes with a complete and robust suite of TCP/IP protocols, servers and services. It is easy to implement full-featured intranets by simply cabling iSeries systems and workstations together and starting the desired services. In most cases, no additional software or hardware is required.

        TCP/IP is an internationally standardized protocol. TCP/IP and its constituent protocols are standardized by the Internet Architecture Board. The standards specifications are provided in documents called RFCs (Request for Comments). There are hundreds of RFCs available today. The iSeries conforms to the appropriate RFCs for the protocols, servers and services listed below which are all included with iSeries at no additional cost:

        Performance of the TCP/IP protocol stack on the iSeries continues to be improved. The result is significant improvements in capacity for TCP/IP users and stability of TCP/IP connections.

        In addition, the AS/400 TCP/IP protocol stack contains two new performance-related TCP/IP Request for Comments (RFCs):

        • RFC 1191 - Path MTU Discovery
        • RFC 1323 - TCP Extensions for High Performance

        The implementation of these RFCs improves TCP/IP performance in many environments.

        TCP/IP Protocols:

        • TCP/IP base protocol support
          • Transmission control protocol (TCP)
          • User datagram protocol (UDP)
          • Internet protocol V4
          • Internet Protocol V6 Application Development Platform
          • IP Security Protocol (IPSec)
          • Internet Key Exchange (IKE)
          • Internet control message protocol (ICMP)
          • Address resolution protocol (ARP)

        • Network Quality of Service (QoS)

          iSeries gives you the ability to control and manage TCP/IP traffic in the network and take advantage of the leading-edge networking Quality of Service (QoS) functions contained in routers and switches. The iSeries QoS functions for managing TCP/IP traffic give you the ability to drop, mark, and shape TCP/IP traffic based on the QoS policy being applied. In addition, QoS admission control capability is added for controlling bandwidth management requests. The QoS functions supported are:

          • Resource Reservation Protocol (RSVP) including an iSeries RSVP agent
          • RSVP APIs (X/Open Standard APIs) for applications
          • Differentiated Services (DiffServ)
          • QoS policies based on the TCP/IP 5-tuple (Source IP address, Destination IP address, Source Port, Destination Port, and Protocol), address ranges, and wild-cards. This support includes a policy agent, and a wizard-based GUI in iSeries Navigator for configuring the QoS policies.
          • QoS monitoring APIs and a GUI for monitoring the effectiveness of your QoS policies.

        • AnyNet
          • Sockets over SNA
          • APPC over TCP/IP

        • Simple Network Management Protocol (SNMP)

        • NETwork STATus (NETSTAT)

        • Connection Verification (PING)

        • Dynamic IP Routing (RIP)

        • Virtual IP Addresses (VIPA)

        • Proxy Address Resolution Protocol (Proxy ARP)

        • Application programming interfaces (APIs) - SOCKETS and RPC

        • Serial Line Internet Protocol (SLIP)

        • Point-to-Point Protocol (PPP)

        • Layer 2 Tunneling Protocol (L2TP)

        • SOCKS proxy enablement

        • UDP multicast support

        TCP/IP Servers and Services:

        • GUI configuration support
        • File Transfer Protocol (FTP) client and server
        • Simple Mail Transfer Protocol (SMTP)
        • Post Office Protocol (POP) Version 3 server
        • HTTP Server (V4R3, or later release)
        • Web-based Administration server
        • Network File System (NFS) client and server
        • Domain Name System (DNS) server
        • Dynamic Host Configuration Protocol (DHCP) server
        • Simple Network Time Protocol (SNTP) client and server
        • IP Printing to HP-compatible network printers
        • Line Printer Requester (LPR) and Line Printer Daemon (LPD)
        • TELNET client and server
        • Remote EXECution (REXEC) client and server
        • Remote IPL support
          • BOOT-P Server
          • TFTP Server
        • ARP Management tool
        • Trace Route tool
        • Userdefined servers

        AS/400 also support a full range of physical interfaces:

        • IBM token-ring LAN
        • Ethernet LAN
        • Ethernet 100Mb LAN
        • Gigabit Ethernet
        • Distributed data interface (DDI - fiber or stp)
        • Frame relay
        • Wireless (LAN)
        • X.25 (PVC and SVC)
        • X.25 over ISDN (withdrawn in V5R3)
        • Integrated PC Server LAN
        • Asynchronous support
        • Synchronous support
        • Twinax

        TCP/IP Protocol Descriptions:

        • IP V6

          In V5R2 support for Internet Protocol Version 6 was provided. IP V6 is know as the next generation IP protocol. It uses a 128 address as opposed to the 32 bit address currently used in IP V4. One of the key requirements of IP V6 is to resolve IP address duplication issues. The IP V6 in V5R2 is an application development platform.

        • TCP/IP base protocol support

          AS/400 natively supports all the base TCP/IP communications protocols. TCP/IP applications are typically implemented to the SOCKETS API which support both TCP (connection-based) and UDP (connection less) applications. As an alternative to the SOCKETS API, applications can be implemented to Remote Procedure Call (RPC) which is based on SUN version 2 of NFS. The base protocols of IP, ICMP and ARP are fully supported as are the security protocols IPSec and IKE. AS/400 TCP/IP conforms to all relevant RFCs. Its communications performance characteristics are equal to or better than SNA in most cases.

        • AnyNet

          AnyNet/400 provides two API/protocol combinations:

          • Sockets over SNA
            • AnyNet/400 Sockets over SNA allows applications written to the sockets interface to communicate between AS/400 systems in an SNA environment. AnyNet/400 provides this with little or no change to application programs. AnyNet/400 Sockets over SNA is compatible with AnyNet/2 and AnyNet/MVS and thus provides connectivity to workstation and host environments.

          • APPC over TCP/IP
            • AnyNet/400 APPC over TCP/IP allows any OS/400 APPC application using ICF or CPI-C to communicate between AS/400 systems across a TCP/IP network. AnyNet/400 provides this with little or no change to application programs. AnyNet/400 APPC over TCP/IP is compatible with AnyNet/2 and AnyNet/MVS and thus provides connectivity to workstation and host environments.

        • Simple Network Management Protocol (SNMP)

          Simple Network Management Protocol (SNMP) provides a means for managing an Internet environment. SNMP is used in each node of a TCP/IP network that is monitored or managed by an SNMP manager. An AS/400 SNMP agent provides support for the exchange of network management messages and information among hosts. OS/400 supports Management Information Base II (MIB-II).

        • NETwork STATus (NETSTAT)

          NETwork STATus (NETSTAT) allows a system administrator to monitor and control the network status of an AS/400 system running TCP/IP or APPC over TCP/IP applications. AS/400 NETSTAT provides information about the status of TCP/IP network interfaces, routes, and connections on a local AS/400 system. Using NETSTAT, you can end TCP/IP connections, IP over SNA connections, and APPC over TCP/IP connections.

        • Networking Software Management and System Setup

          Several TCP/IP management enhancements in V5R1 give the network administrator more control when monitoring their TCP/IP network and troubleshooting networking problems. The enhancements include:

          • A graphical version of network status (NetStat) that includes the ability to map a socket connection to a list of jobs for that connection.

          • The ability to trace the route a TCP/IP packet will take through the network (TrcRoute - includes a TrcRoute CL command).

          • Address resolution protocol (ARP) cache monitoring.

        • Connection Verification (PING)

          Connection Verification, also called PING (Packet Internet Groper), allows you to verify your connection to a remote system. These connection verification commands use the Internet Control Message Protocol (ICMP) to send data to an Internet address and wait for a response. On AS/400, you can use either the Verify TCP/IP Connection (VFYTCPCNN) command or the PING command.

        • Dynamic IP routing (RIP)

          Routing Information Protocol (RIP) is a dynamic IP routing protocol that communicates with adjacent routers, informing each other of their respective network connections. Dynamic routing protocols make network maintenance easier and improves network performance and reliability. AS/400 includes both RIP Version 1 and RIP Version 2. Version 2 of RIP adds security and efficiency features.

        • Virtual IP Addresses (VIPA)

          All the iSeries to be known by a single IP address, even when it is attached to multiple networks. Common uses of VIPA are for load balancing and fault tolerance.

        • Proxy Address Resolution Protocol (Proxy ARP)

          Proxy ARP is an IP networking technique that allows one machine, the proxy agent, to answer ARP request on behalf of another machine. It is useful for SLIP, PPP and twinax connections because it can make devices appear to be all logically on the same local LAN subnet thus avoiding the need to implement either dynamic routing protocols or static route definition.

          In V5R2, Proxy ARP was extended to support Virtual IP Addresses.

        • Application programming interfaces (APIs) -- SOCKETS and RPC

          Many times an enterprise has unique interoperability requirements for its private networks. The enterprise must provide its own applications to fulfill these unique requirements. AS/400 provides programming interfaces to accomplish this.

          The Sockets APIallows distributed applications to exchange data locally and over networks. Both connection-oriented and connectionless communications are supported by the Sockets API. In addition to IP, you use the Sockets API to write applications that communicate over Internetwork Packet Exchange (IPX) protocols directly.

          Also, available to distributed application developers is the Remote Program Call (RPC)interface. This approach views remote applications essentially as callable programs.

          In addition, both JAVA and Lotus Domino provide various programming options for implementing distributed applications over TCP/IP networks.

        • Network Security and VPN

          iSeries VPN (Virtual Private Networking) support, is enhanced with additional security, greater reliability, improved performance, and is easier to use. iSeries Navigator is redesigned to intuitively navigate VPN configurations, and you can use the VPN wizard to setup and implement your network security policy. Digital certificates add a scalable and secure mechanism for cryptographic operations, and in V5R1 you can use them in your VPN configurations to authenticate the identities of the VPN end points. An integral part of iSeries VPN is IP Packet Filtering, and in V5R1 this component allows filter activation and deactivation on a per- interface basis.

          In V5R2 support was added to iSeries VPN to allow it to initiate connections across firewalls that are performing network address translation (NAT). This function is referred to as UDP encapsulation.

        • Serial Line Internet Protocol (SLIP)

          The TCP/IP SLIP provides TCP/IP connectivity over an asynchronous link, such as a simple modem pair over a telephone line protocol such as RS-232. Full-fledged asynchronous connectivity is supported rather than just terminal emulation. With SLIP, the more cost-effective, stand-alone dial-up servers can support a multiplicity of dial-up clients for single iSeries installations. Also, the iSeries system can dial attach to the Internet via the IBM Global Network (IGN) or other Internet access service provider.

        • Point-to-Point Protocol (PPP)

          Point-to-Point Protocol (PPP) is an open protocol for wide area network TCP/IP connectivity that can support both dial and leased lines. It can be used to extend an enterprise intranet across multiple locations. It is also the defacto standard for connecting to the Internet through an Internet Service Provider (ISP). When used as a dial-up protocol, PPP is a more robust alternative to SLIP (Serial Line Internet Protocol).

          PPP's IDSN support enables AS/400 to attach to ISDN switched networks. This provides higher bandwidth access to networks than is possible with current modems over analog telephone lines.

          ISDN is no longer supported starting with V5R3.

          Using PPP, the iSeries provides an excellent integrated solution for remote LAN access and as a remote office gateway into an organization's intranet.

          PPP includes Radius client support and DHCP proxy client support.

          iSeries supports PPP over Ethernet (PPPoE) for connection originating from the iSeries server. This support allows a PPP connection to be established over an Ethernet LAN adapter attached to a DSL modem. Once this connection is established between the iSeries and the ISP, individual users on the LAN can access the ISP over the iSeries PPoE connection. iSeries also supports the PPP Multilink Protocol (MP). The PPP MP groups PPP links together to form a single virtual link. The aggregation of multiple links increases the total effective bandwidth between two systems. iSeries also supports Bandwidth on Demand using PPP MP. Additional PPP users can be dynamically added as needed when bandwidth needs increase and removed when bandwidth requirements decrease.

        • Layer 2 Tunneling Protocol (L2TP)

          Layer 2 Tunneling Protocol (L2TP) is an enhanced link protocol that provides a multi-hop virtual circuit through the Internet. L2TP is also known as Virtual PPP since it creates a virtual circuit at a link layer and then utilizes Point-to-Point Protocol (PPP) to complete the connection at the network layer. L2TP is typically used in conjunction with Virtual Private Networks (VPN) to provide a secure connection over the Internet.

        • SOCKS proxy enablement

          With iSeries Socks Client support, iSeries TCP/IP client programs (e.g., TELNET and FTP client) are able to communicate with server programs that are running on systems outside the IBM Firewall. iSeries client programs can use the Socks proxy support on the IBM Firewall to transmit data packets to external servers. By funneling these requests through the firewall proxy, the customer's secure internal network continues to be protected from data packets coming from an unsecured network. Once configured, iSeries Socks Client support is transparent to TCP/IP client programs and works for all client programs written to a sockets interface.

        • UDP multicast support

          UDP multicast support is enabled on iSeries. Applications written using this support will make better use of the bandwidth thus reducing network costs. This represents another improvement to the overall TCP/IP enablement package for iSeries which can be accessed through the industry standard sockets API.

        TCP/IP Servers and Services Descriptions:

        • GUI configuration support

          TCP/IP networking on iSeries is easier than ever to administer and manage. iSeries TCP/IP configuration can be managed through all graphical user interfaces which are integrated with iSeries Navigator. Included is a graphical wizard that provides simplified step-by-step guidance for configuring TCP/IP. In addition, a service to centrally administer all workstation configuration data for IP networks is included with OS/400. This service is based on an Internet standard called Dynamic Host Configuration Protocol (DHCP) and dynamic DNS. In addition, managing e-business data flow over TCP/IP is provided via the Internet standard referred to as Quality of Service (QoS). iSeries intranets have never been easier.

        • File Transfer Protocol (FTP) client and server

          File Transfer Protocol (FTP) allows users to send or receive copies of files to or from systems across a TCP/IP network. FTP also provides functions for renaming, adding, and deleting files.

          OS/400 TCP/IP supports the following FTP functions:

          • Secure Sockets support for the FTP server and client

          • Allow administrators to limit some or all FTP functions by user profile without requiring writing an exit program

          • Transferring database files of up to one terabyte

          • Transferring save files and members in physical files, logical files, distributed data management files, and source physical files

          • Transferring hierarchical file system files including Client Access for AS/400 files and document library object files

          • Transferring binary files "as is"

          • Using exit points to pass control to exit programs for anonymous FTP and security controls

          • Sending text files in EBCDIC format or converting them to ASCII (the default format)

          • Creating and deleting libraries, files, and members using AS/400 FTP server subcommands

          • Creating and deleting folders and directories using AS/400 FTP server subcommands

          • Running FTP unattended in batch mode

          • Converting double-byte character set (DBCS) data from AS/400 EBCDIC code pages to and from Internet ASCII code pages

          • Using coded character set identifier (CCSID) support

          • Support for popular graphical FTP clients and Web server development tools. This enhancement includes support for UNIX format file listings from the AS/400 FTP server.

          • Ability to use directories other than database libraries as the initial working directory for the AS/400 FTP server.

          • Options to create new database files using the system or user default CCSID.

          • Ability to transfer files larger than 2 GB in all file systems that support these file sizes.

          • Ability to transfer database files containing null field data.

        • Simple Mail Transfer Protocol (SMTP)

          Simple Mail Transfer Protocol is used to send or receive electronic mail. For consistency with other AS/400 mail functions, SMTP interoperates with Systems Network Architecture (SNA) Distribution Services (SNADS) through AnyMail/400. SNADS and AnyMail/400 are part of OS/400.

          SMTP supports the following functions:

          • Sending and receiving mail objects up to two gigabytes

          • SMTP as an intermediate TCP/IP hop on an SMTP distribution

          • Support for MIME partial (fragmented) messages: splitting and re-assembly

          • Support for sending Internet mail through a firewall

          • Excellent mail exchange interoperability between SMTP and OfficeVision
            • Converting data (including DBCS) from AS/400 EBCDIC code pages to and from Internet ASCII code pages
            • Optional automatic enrollment of senders of incoming mail, in the system distribution directory and alias tables
            • OfficeVision for AS/400 notes, messages and attachments
            • MIME messages to and from OfficeVision for AS/400 documents: FFT and PC Files

          • Sending and receiving documents and messages using AS/400 commands. (Users can send and receive SMTP messages by using the send, receive, and query distribution commands (SNDDST, RCVDST, and QRYDST), or by using the Post Office Protocol (POP3) server.)

          • Increased simultaneous connection support; AS/400 SMTP is no longer restricted to a maximum of 16 inbound and 16 outbound simultaneous mail connections. You can tune SMTP depending on the mail load on your system, thus enabling greater scalability.

          • Enhanced domain name system resolver support; the AS/400 SMTP client processes all mail exchanger (MX) records returned by a domain name server query. This means less undelivered mail when sending to large Internet Service Providers.

          • Option to enable journaling for mail delivery status tracking and mail statistics.

          • Option to require all mail received by AS/400 SMTP to be processed by the AS/400 Mail Services Framework (MSF) to improve security.

          • Enhancements for automated retry of mail when dial-up connections are established and finer granularity of mail delivery retry timing.

          • Enhanced blacklist support

          • Dial-up mail retrieval support for mail handling (SMTP service extensions)

          • Multiple domain support for servicing mail

          Like TELNET and FTP, SMTP supports both client and server functions on AS/400. AS/400 can serve as a mail gateway to Interconnect SNADS, and TCP/IP SMTP electronic mail networks.

        • Post Office Protocol (POP) Version 3 server

          The Post Office Protocol (POP) Server is the iSeries implementation of the POP3 mail server. This server enables iSeries to act as a POP server for any client that supports the POP mail protocol, including major e-mail clients, such as Netscape and Eudora, running in Windows, AIX, and Macintosh. The POP server allows users to exchange mail, including Multipurpose Internet Mail Extensions (MIME) mail.

        • TCP/IP Simplification Extensions

          OS/400 Domain Name System (DNS) services are based on the widely used industry-standard DNS reference implementation known as BIND version 8.2. Topping the list of enhancements are the dynamic update capabilities, which transforms the DNS into a Dynamic DNS (DDNS). iSeries supports an integrated Dynamic IP solution that automatically manages TCP/IP addresses and their associated DNS host names on your network. The iSeries Dynamic Host Configuration Protocol (DHCP) server allows DDNS to be configured to send dynamic DNS update transactions.

        • Internet Printing

          V5R1 provides a wide range of capabilities that enable the iSeries to address the print and communications requirements of e-business and network applications. These capabilities include:

          • Support for PDF
          • Dynamic e-mail of printed output
          • Internet Print Protocol (IPP)
          • Printing architectures for Java applications
          • Support for Unicode
          • Comprehensive transforms for printed data

          These capabilities are available with OS/400, PSF/400, and InfoPrint Server for iSeries (a separately orderable product).

        • Directory Services

          OS/400 Directory Services supports IBM SecureWay Directory Version 3.2. Examples of IBM SecureWay products dependent on the directory for some of their distributed functions are:

          • WebSphere Commerce Suite
          • WebSphere Application Server
          • SecureWay Policy Director
          • IBM MQSeries
          • IBM HTTP Server

          Version 3.2 of the IBM SecureWay Directory provides the following industry-leading innovations:

          • Support for Kerberos protocol (server and client) - supporting authentication utilizing Kerberos.

          • GSKit 4.0 - the server and client are upgraded to use GSKit 4.0 as the SSL provider.

          • Fine grain access control - allows the management of access down to the individual attribute level. A directory administrator can control who sees individual attributes for each entry within the directory.

          • "Unlimited" Connections - allows a much larger number of clients to connect to a server, which reduces the number of servers required.

          • Transaction support - allows an application interface to include more than a single LDAP operation in a transaction with the server.

          • Event notification - allows a server to notify a registered client that an entry in the directory tree is changed, added or deleted, at or below the specified DN(s) for the event types of interest.

          Directory Services on OS/400 updates include:

          • Security auditing is added to LDAP for administrators who need to audit LDAP operations to the server.

          • The Directory Services server is automatically configured on the system when either the directory server or publishing is not already configured and when no LDAP DNS information can be found.

          • Directory Services is included in OS/400. OS/400 - Directory Services, option 32, still exists for compatibility, but LDAP function is in the base operating system.

          The HTTP Server allows AS/400 systems attached to a TCP/IP network, such as the Internet or an intranet, to provide objects at the request of any local or remote Web browser. HyperText Markup Language (HTML) documents, index (directory) files, plain text, video, Java, graphics, and audio objects can be served from AS/400 file systems.

          You can use IBM Net.Data for AS/400 (which comes with OS/400) to access DB2 UDB for AS/400 data using SQL and to create interactive Web applications by using "macros" to add logic, variables, program calls, and report writing to HTML.

          The HTTP Server supports Secure Sockets Layer (SSL) security protocols for data encryption and server certificate authentication, which requires one of the following:

          • Cryptographic Access Provider 128-bit for AS/400 (5769-AC3)

        • Web-based Administration server

          The Administration server is a special-purpose HTTP server that provides a browser-based interface for managing the IBM HTTP servers as well certain other products.

        • Network File System (NFS) client and server

          The Network File System (NFS) includes both server and client file serving support, as well as integrated file system file support. This file serving support enables broad multivendor file system interoperability.

        • Domain Name System (DNS) server

          DNS is the standard distributed naming service for intranets and the Internet. It is used by applications to map human-readable names into machine- readable IP addresses (e.g., the host portion of URLs into the corresponding 32 bit IP address for IP V4 or 128 bit IP address for IP V6). This improves ease-of-use in referencing resources on the network. For example, it converts www.as400.ibm.com to

          OS/400 includes a full-function DNS server. It can be configured for primary, secondary and caching roles. DNS configuration data from other platforms can easily be migrated to the AS/400 DNS server. In addition, a migration utility that moves existing AS/400 host table information into the DNS configuration databases is provided.

        • Dynamic Host Configuration Protocol (DHCP) server

          Deploying DHCP to centrally control all TCP/IP workstation configuration tasks can dramatically reduce the cost of managing a TCP/IP network. DHCP is a standard protocol supported natively by most popular workstations including Windows 95/NT, UNIX and IBM Network Station. Using DHCP, all IP configuration data (IP addresses, subnet masks, default routers, etc.) are dynamically assigned when new workstations are added to the network. Furthermore, DHCP can automatically recover and recycle network resources when workstations are removed from the network. These capabilities eliminate the time-consuming and error-prone task of manual workstation configuration.

          OS/400 includes a full-function DHCP server with an intuitive GUI administrative interface. OS/400 also comes with a DHCP relay agent (also called a BOOT-P relay agent) which can be deployed to route DHCP requests from multiple subnetworks to one or more central DHCP servers.

        • Single Network Time Protocol (SNTP)

          iSeries supports SNTP as both a client and server. As a SNTP client the iSeries can retrieve a time value from an extended time source and modify the system clock. As a server the iSeries can be used to provide time values to clients.

        • IP Printing to HP-compatible network printers

          The AS/400 has a built-in print driver for direct IP printing to HP PCL/PJL compatible network printers. Automatic conversion of SNA Character String (SCS) and Advanced Function Printing (APF) print data into HP Printer Control Language (PCL) is done using the AS/400 Host Print Transforms. In addition to direct support of a variety of network printers from HP, IBM and other vendors, the PJL support also can monitor status from those printers.

          Printing for TCP/IP networks can also be implemented using the Printer Passthru function available in Client Access (see the Telnet description for more details).

        • Line Printer Requester (LPR) and Line Printer Daemon (LPD)

          Line Printer Requester (LPR) and Line Printer Daemon (LPD) allow users to print a spooled file from any system in a TCP/IP network. LPR is the sending or client portion of the spooled file transfer. LPD is the receiving or server portion of the spooled file transfer. On AS/400, the Send TCP/IP Spooled File (SNDTCPSPLF) CL command allows you to print a spooled file on a remote system, and specify appropriate printing operations. You can send files to AS/400 systems and non-AS/400 systems.

        • TELNET client and server

          The TELNET protocol allows a system (the TELNET client) to access and use the resources of a remote system (the TELNET server) as if the TELNET client's workstation were locally connected to the remote system. AS/400 TELNET provides both the TELNET client and the TELNET server functions.

          The TELNET protocol provides a mechanism for the client and server to negotiate options that control the operating characteristics of a TELNET connection. Among other things, these negotiations involve determining the best terminal type supported by both the client and server. Depending on the terminal type negotiated, the AS/400 TELNET client operates in one of the following full-screen modes: 3270, 5250, VT100 or VT220. The AS/400 TELNET server operates in ASCII line mode or in one of the following full-screen modes: 3270, 5250 or VT100. The functions available in a TELNET session depend on the operating mode.

          Security and automation features are included in the AS/400 TELNET 5250 server:

          • Registered TELNET server exits for both session initialization and session termination. These exits require only that a customer-written user exit program be registered at the proper exit point. No changes are needed for the connecting TELNET client emulator, so existing clients can immediately benefit from this feature.

          • Virtual Device selection by the attaching client (or a registered TELNET server exit program) provides for more traditional job-routing to preferred subsystems and allows for associated work management tuning. With Virtual Device selection, preferred code page, character set, and keyboard attributes can be established on a per session basis, thereby offering greater flexibility in national language support.

          • Printer Passthru support consists of two new terminal types (IBM-3812-1 and IBM-5553-B01) which provide additional printer support for the TCP/IP environment. This support allows the TELNET server to provide the client with the flexibility to dynamically create and/or select a virtual printer device through enhanced negotiation, or via assignment by the initialization exit program.

          • TELNET Session disconnect/reconnect (QDEVRCYACN) is enabled for display sessions that use "consciously selected" device names.

          • TELNET and Virtual Terminal API Connected Display sessions are subject to the settings of QINACTITV (INACTive Interactive job Time-out Value) which specifies when the system takes action on inactive interactive jobs.

          • Automatic sign-on (optional bypass of the sign-on procedure) is enabled for TELNET display sessions which have specific settings for the QRMTSIGN system value.

          • TELNET server supports secure TELNET sessions via SSL.

          • TELNET Server supports single signon capabilities using enterprise identify manager (EIM) and Network Authentication Services (NAS) which is IBM's implementation of Kerberos.

        • Remote EXECution (REXEC) client and server

          The REXEC server allows you to issue AS/400 commands from other systems across IP networks. REXEC is a standard TCP/IP protocol support by many other systems including UNIX. When you issue a command, that command along with authentication information (profile and password) are sent to the AS/400 REXEC server. The server authenticates the user, executes the command and returns the results. The AS/400 REXEC server includes exit points so additional security measures can be added if desired.

          AS/400 also has an REXEC client capability so commands to other systems can be sent from an AS/400. The command RUNRMTCMD (Run Remote Command) is used to issue an REXEC client request.

        • Remote IPL support

          The AS/400 BOOTstrap Protocol (BOOT-P) server enables the central management of TCP/IP workstations such as the IBM Network Station. It can centrally manage workstation configuration information such as IP addresses, mask, default router address, etc. The DHCP server provides similar function but with more capabilities so it is generally preferable to use DHCP rather than BOOT-P.

          The Trivial File Transfer Protocol (TFTP) is used by thin clients such as the IBM Network Station to receive their initial program load. The AS/400 TFTP server includes an extension called broadcast TFTP that dramatically improves load time when many Network Stations are requesting loads simultaneously (e.g., after a power outage).

        • TCP/IP Packet Security

          Selectively limits or journals network access to applications and services with additional protection for AS/400 systems that run sensitive applications or act as Web servers.

          TCP/IP packet security also helps protect an entire subnetwork when the AS/400 acts as a casual router.

        • TCP/IP Address Mapping and Hiding

          When the TCP/IP addressing schemes of networks conflict, or you need to hide all or part of the network topology, network address translation (NAT) capabilities provide a solution. In addition, TCP/IP masquerading allows all the computers on one network to access servers on another network by sharing a single TCP/IP address. Masquerading is particularly useful when connecting to another network, such as the Internet, using a dial-up link.

        • TCP/IP Dial-on-Demand (DOD) Networking

          Connections are made only when there is a need to communicate. Dial-on-Demand is supported on all switched network types and is particularly well-suited to ISDN with its fast call setup time. It is also valuable for burst and infrequent traffic patterns -- especially if you have more remote locations than physical lines. With Dial-on-Demand, modem and telephone line resources are not committed until an application attempts to communicate with a remote site. Thus, a small number of physical resources can dynamically serve a large number of remote networks.

        • TCP/IP Integrated Load Balancing

          Virtual IP Addressing creates a virtual TCP/IP address that is not associated with a physical network interface. This virtual address on the AS/400 system can be reached from the network through all installed physical interfaces. This allows use of a single IP address with load balancing over multiple physical interfaces and can dramatically increase capacity for high-volume AS/400 e-business servers.

        • User Defined Servers

          User defined servers allows you to add custom servers to the iSeries. This enables you to perform administrative tasks such as starting, stopping, and monitoring servers in the same way as you would administer servers that are included on the iSeries.

      • X.21 short hold mode (SHM) and multiple port sharing (MPS)

        SHM and MPS are supported to take advantage of the fast call set-up and clearing characteristics of X.21 SHM/MPS.

      • Remote Work Station Support

        Work stations from the 5250 family of displays and printers (as well as programmable work stations that emulate the 5250) are supported by 5250 remote controllers. Programs written for interactive applications need not be aware of the work station location (local or remote).

      • Intersystem Communications Function

        The intersystem communications function provides the application interface for the AS/400 system communications support. The following communication types are supported through this interface:

        • Advanced program-to-program communications/advanced peer-to-peer networking (APPC/APPN)
        • SNA upline facility (SNUF)
        • BSC equivalence link (BSCEL)
        • Asynchronous communications
        • INTRA for intra-system communications and testing of programs

        The application program uses high-level language operations and communications functions to communicate with a remote system. Either externally described data or system-supplied formats (compatible with System/36 SSP-ICF operations) can be used.

        Support functionally equivalent to that known on the System/36 as ICF INTRA support is also provided. This intrasystem communications function allows communications between applications running on the same AS/400 system as if they were using a communications line. This allows:

        • Developing and testing ICF communications applications before communications facilities are installed.
        • Breaking up an application into more manageable pieces by having some of the work done in independent processes.

      • Advanced Peer-to-Peer Networking (APPN)

        APPN provides a way to easily establish and maintain a network of AS/400 Systems, System/36s, and other IBM systems. The AS/400 user can install and maintain a complex network of interconnected systems without requiring highly skilled programmers. Configuration and maintenance of the network is done by the controlling nodes that make up the network. Systems that use CPI-C, APPC, DDM, display station pass-through, SNA distribution services (SNADS), SNA backbone, file transfer support, electronic customer support, and AS/400 Client Access can take advantage of APPN networks.

        APPN support allows LAN-based AS/400 systems to establish a direct LAN session without being defined to one another. The configuration of 2.1 type PCs on a LAN is significantly reduced using APPN and auto configuration support. An APPN network may be established spanning LAN and remote communication facilities while providing a seamless appearance to nodes in the network.

        APPN multi-network connectivity provides APPN session paths between adjacent APPN networks of dissimilar network identifications. Therefore, established APPN networks having unique network identifications can be connected, a large APPN network may be partitioned for operational control, and service providers may connect to client APPN networks. The SNA Network Registry is available to register customer network names. To prevent name conflicts between attached networks, the networking customer can obtain a unique, registered network identifier (NETID) from their IBM branch office representative.

        Back-up APPN network node support provides dynamic switching of an AS/400 APPN end node to a back-up network node server upon link failure for sending network management alerts to the network management focal point.

        High Performance Routing (HPR) includes three significant enhancements to APPN to improve network reliability and performance for customers with medium to large SNA networks.

        • HPR automatically reroutes around failures.
        • HPR automatically increases network throughput by recognizing and using under utilized links.
        • HPR automatically adjusts to network congestion, lowering and raising the rate at which it sends your data to avoid timeouts.

      • Dependent Logical Unit Requestor (DLUR)

        AS/400 DLUR support provides existing SNA end users the benefits of subarea APPN migration without changing their existing SNA devices and applications on the AS/400 system. This is a cost savings allowing hundreds of device and application sessions to be converted with a single system upgrade. No application rewrites, no device upgrades, and no rewiring is required.

        Additional AS/400 benefits include the ability to distribute intelligence (applications) to AS/400 DLUR nodes. Controllers and routers do not have the capability to handle application as well as an AS/400 server. PC servers do not have the capacity to handle the number of devices/applications you can distribute to an AS/400 system. In addition, the AS/400 system supports a broader mix of downstream connections, applications, and devices than other servers.

        Upgrading subarea SNA to APPN provides significant advantages to current and potential users connected to subarea SNA networks including:

        1. APPN supports existing subarea SNA based applications and devices, the cost to move to APPN is much less than converting their networks to other protocols which require application rewrite and often replacement of existing hardware.
        2. Greatly reduces configuration requirements in complex networks with auto-configuration of dependent LUs and bound sessions in VTAM domain and cross-domain networks.
        3. Greatly increased network management (session tracking extends well beyond current subarea boundary connections)
        4. Combined with APPN HPR towers, you can see significant network performance improvements and link outage error recovery

      • Advanced Program-to-Program Communication (APPC)

        APPC allows a program on one system to communicate with a program on a remote system so that users can run applications and have access to functions not available on the local system. AS/400 APPC is based on SNA LU-6.2 and PU Type 2.1 and is designed to provide a common session protocol for both document interchange and distributed data processing.

        Customers using APPC/ICF, CPI-C, DSPT, DDM, SNA/DS, or any other application using APPC LU-6.2 have the option to enable session level compression which significantly reduces traffic on the slower speed communications lines such as SDLC and X.25.

        APPC uses one of two compression algorithms, Run Length Encoding (RLE) or Lempel-Zev (LZ). RLE uses String Control Bytes (SCBs) to encode duplicate repetitive bytes of data. LZ assigns codes to represent unique character strings which are stored in tables.

        For security reasons, user passwords are not transmitted in clear text. Protected passwords are built based on the real password and sent to a peer system when the peer system supports the password substitution function.

      • SNA Upline Facility to System/370 IMS and CICS Hosts

        The SNA upline facility provides the AS/400 user with communications to:

        • CICS/VS (as LU-0) and IMS/VS (as LU-P)
        • CICS/DOS/VSE (as an IBM 3790)
        • CICS/OS/VS (as an IBM 3790)

        This provides for program-to-program communication between AS/400 and System/370 programs and supports customers migrating from SNA upline facility on System/36.

      • Binary Synchronous Communications Equivalence Link (BSCEL)

        BSCEL provides systems management on the AS/400 system by enabling one program to start another program on another system, also having BSCEL support. The other system can be IBM AS/400 System, IBM System/36, or IBM System/34.

        BSCEL support also allows a program to communicate to other systems and devices using the binary synchronous communications (BSC) protocol. It is a program-to-program function.

      • ICF Retail Communications Support

        The user interface for retail communications support is the intersystem communications function (ICF) file interface used by high- level languages. The ICF retail communications support provides business solutions through the capability to attach retail controllers (3651, 3684, 4680, and 4684) to the AS/400 system with the following connectivity:

        • 3651, 3684 -- SNA LU-0 LU-1 LU-2 / SDLC
        • 4680 -- SNA LU-0 and LU-6.2 / SDLC and X.25.
        • 4684 -- SNA LU-0 LU-2 / X.25 and Token-ring

        Communication with the remote change management server on a 4684 Retail Controller is enabled by the ICF retail communications support, which allows a maximum of 32 logical units active concurrently through a 4684 Retail Controller description.

        ICF retail communications support includes a retail pass-through utility and retail point-of-sale data translation routines. When the AS/400 system is functioning as an in-store processor, the retail pass-through utility is an application that bridges the SNA LU-0 secondary session with the host system (e.g. System/370 running NDM, CICS, or ADCS using VTAM/NCP) and the LU-0 primary session with the retail point-of-sale controller. The retail pass-through utility uses the AS/400 SNA upline facility (SNUF) for the SNA LU-0 secondary session to communicate with the host (e.g., System/370).

      • ICF Finance Communications Support

        The user interface for finance communications support is the intersystem communications function (ICF) file interface used by high- level languages. The ICF finance communications support provides business solutions with its capability to attach finance controllers (3601, 3694, 4701, and 4702) to the AS/400 system with the following connectivity:

        • 4701, 4702 -- SNA LU-0, LU-2 / SDLC
        • 3601, 3694 -- SNA LU-0 / SDLC
        • 4701, 4702 -- SNA LU-0, LU-1, LU-2 / X.25

        The ICF finance communications support enables the AS/400 user to explicitly configure a financial branch system services (FBSS) controller, thereby providing the following connectivity:

        • SNA LU-0, LU-6.2, LU-1, LU-2 / SDLC
        • SNA LU-0, LU-6.2, LU-1, LU-2 / X.25
        • SNA LU-0, LU-6.2, LU-1, LU-1 / Token-Ring LAN

        The ICF finance communications support provides the capability for the attachment and configurability of the IBM Personal Banking Machines (4730, 4731, 4732, and 4736 and the IBM Self-Service Transaction Station (4737) on the AS/400 system. The Personal Banking Machines can be attached to the AS/400 system with the following connectivity:

        • 4730, 4731, 4732, 4736 -- SNA LU-0 / SDLC

        Indirectly through a 4702 Controller.

        The Self-Service Transaction Station (4737) is configured on the AS/400 system as a financial branch system services (FBSS) controller, thereby providing the following connectivity:

        Directly using

        SNA LU-0, LU-6.2 / SDLC
        SNA LU-0, LU-6.2 / X.25
        SNA LU-0, LU-6.2 / Token-Ring LAN

        Indirectly through a 4702 Controller

      • Non-ICF Finance Communications Support

        The finance support provides an application programming interface and the capability to attach to AS/400 Systems:

        • The 4701/4702 Finance Communication Controllers using SNA/SDLC and SNA/X.25 communications lines, and
        • The 3694 Document Processors using SNA/SDLC communication lines.

        Ease-of-use features are provided that allow communication with the IBM finance communication system online terminal support, IBM finance communication system advanced branch controller system (ABCS) or equivalent support, in the 470X controller. This finance support is based on System/38 Finance. The 470X Control Unit can be programmed to perform 3270 emulation. IBM 4704 devices can be used to emulate 3270 displays, or IBM 3278, 3279, and 3287 devices can be attached to the controller using device cluster adapter (DCA) ports.

      • SNA Distribution Services (SNADS)

        The OS/400 SNADS support is an integrated queued asynchronous connection to a SNADS network and remote document libraries. It provides routing, sending, and receiving operations for users to exchange distributions containing documents, messages, data, or objects with other users in the SNADS network. SNADS uses a system distribution directory to direct distributions to users in a local system or to other systems in a SNADS network.

      • SNA Primary Logical Unit 2 Support

        SNA Primary LU-2 (3270 type terminal) support improves the AS/400 participation in an SNA backbone network. It enables any LU-2 terminal user in the network to access either any AS/400 system or any S/390 (R) system in the network with the same user and network interface. AS/400 application programs written for 5250 displays may also be accessed by a LU-2 terminal through the network with this new SNA Primary LU-2 support.

        This will protect the investment in the SNA backbone network, installed AS/400 systems, and installed S/390 systems. It also provides a central point of control for network management and distribution. The IBM Network Routing Facility licensed program is not needed with this support.

        SNA Primary LU-2 support enhancements provide for attachment of more than one Network Control Program (NCP) Communication Controller. Each controller may be in the same or different subarea. Previously, some customers were restricted by a limitation of 253 sessions. Now theoretically up to 60,000 SNA LU-2/1 application primary sessions may be configured on an SDLC link between an AS/400 system and an NCP Communications Controller, and up to 6000 SNA LU-2/1 application primary sessions may be configured for each IBM TR/LAN attaching an AS/400 system and NCP Communications Controller.

        In addition, the AS/400 shared line support is enhanced with this new SNA Primary LU-2 capability. LU-2/1 application primary sessions, APPN/APPC sessions, SNUFs sessions, 3270 Device Emulation sessions, and DSNX sessions may all share the same SDLC link between an AS/400 system and an NCP Communications Controller.

        The AS/400 system's ability to connect 3270 work stations to an APPN network is greatly improved. AS/400 systems with APPC, CPI for communications and using APPN networking may now add OS/400 application primary sessions to the AS/400 system in the SNA subarea network environments. This increases use of the AS/400 system as a distributed system and/or a central site processor.

        At least one VTAM host using VTAM V3R4 and its companion release of NCP V5R4 is required for OS/400 SNA Primary LU-2 support. Included with this is support for DBCS displays and printers.

        Also, with SNA Primary LU-2 support, user and network interface routing is handled directly by NCP and the controllers in the network.

        OS/400 SNA Primary Logical Unit (PLU) support in Version 2 Release 3 significantly improves the initial and ongoing configuration effort for large networks. It exploits the use of dynamic LU definition and independent LU extended bind capability in attached NCP controllers which significantly reduces NCP configuration of AS/400 systems. Furthermore, OS/400 allows auto-create and auto-delete of configuration control blocks needed by the AS/400 application program for its LU-2 terminal and LU-1 printer sessions. Auto-create/delete are selectable device configuration options of OS/400 configuration support allowing for flexible application and network design. LU-2 terminals of 24x80 screen size are supported.

        Also, there are several LU-1 (3270 type printer) operational enhancements. LU-1 SCS printer sessions are supported by OS/400 for application initiation, a terminal's associated printer, an auto-LOGON printer, and a designated network printer thru terminal input to an application. Printing may be done directly by the application program or spooled using the AS/400 spool writer facility. In addition, LU-1 SCS session primary applications may have printer output directed to an AS/400 system printer.

      • SNA/Management Services Transport

        The SNA/Management Services Transport support, enables the OS/400 licensed program to send and receive management services data with other systems in an SNA network that provide support for the SNA/Management Services architecture. This includes other systems using OS/400, NetView and OS/2 licensed programs. An Application Programming Interface (API) is also provided to enable AS/400 customers and business partners to use this support in their network and systems management applications.

      • Distributed Relational Database Support

        The Remote Unit of Work function described in Distributed Relational Database Architecture (DRDA) is a function of the operating system that supports distributed relational access to data on remote systems. These remote systems must be connected by a communications network and must also support DRDA. The Remote Unit of Work also supports SAA Character Data Representation Architecture (CRDA) and is used with Distributed Data Management (DDM) architecture to provide distributed relational access to remote databases. DRDA compliant access is provided by other DB2 family members.

        AS/400 DRDA support in V4R5 is enhanced to provide password encryption using a standardized encryption algorithm that provides more secure password transmission between AS/400 systems and other members of the DB2 family. The algorithm used is the Diffie-Hellman encryption algorithm. With it, the client and server exchange connection keys based on shared, private, large integers. The connection keys are used by the client to encrypt the password and the server to decrypt the password with 56-bit Data Encryption Standard (DES).

      • Object Distribution Facility (ODF)

        The object distribution facility gives users or applications the capability to distribute objects across a network. Information such as data files, source code, and print files can easily be exchanged between peer-connected systems (AS/400 system, System/36 and System/38) using SNA distribution services (SNADS). This capability protects customer investment in systems, data, and applications, while providing improved productivity through data access.

        When coupled with DSNX, ODF can redistribute files and programs received from a System/370 host to another system. For example, a DSNX distribution from a System/370, using NetView distribution manager, can be sent to an AS/400 system, which in turn can forward the distribution to System/36s or other AS/400 systems.

      • Display Station Pass-through

        Display station pass-through allows a user attached to a local AS/400 system to be connected to a remote System/36, System/38 or another AS/400 system, to sign-on to that system, and to execute applications or perform network management functions as if connected directly to the remote system. An options is provided to eliminate the requirement to sign on at the target system. System/36 and System/38 users can also sign-on to an AS/400 system and perform the same functions.

        AS/400 users passing through to a remote AS/400 can have their printed output automatically printed on their local system. Exchange of printed data for System/36 and System/38 users passing through to a remote AS/400 may be accomplished using the object distribution facility and a user written program.

      • Distributed Data Management (DDM)

        DDM is a function of the operating system that supports distributed file and distributed relational access to data on remote systems. These remote systems must be connected by a communications network and must also be using DDM. For example, distributed file access is provided by System/36, IBM System/38, CICS/VS, or another IBM AS/400 System. SAA Distributed Relational Database Architecture (DRDA) and SAA Character Data Representation Architecture (CDRA) are used with DDM to provide distributed relational access to remote databases.

      • SNA Passthrough

        SNA Passthrough provides SNA controllers and T2.1 nodes attached to AS/400 system an unedited unaltered session to S/390 system. VTAM signon screen is displayed on supported devices attached to AS/400 system. The following sessions can be established using this support.

        • LU-6.2 sessions; to the AS/400 target or a passthrough session
        • LU-0 thru LU-3 sessions; passthrough sessions only

      • IBM Network Routing Facility (NRF) Support/400

        IBM NRF Support/400 is programming that enables connectivity between AS/400 system and the Network Routing Facility LPP operating on the IBM 3745 Communications Controller. LU-2 (3270-type) terminals and LU-1 SCS printers attached to an NRF node may be session partners to an AS/400 application host.

        Session partner routing using NRF gives the appearance to the AS/400 application host that the terminals attached to NRF are directly connected. The NRF session between the terminal and the AS/400 application host is routed thru the SNA subarea without going to the System/390 host.

      • Autodial Support

        Autodial support is provided on the AS/400 system so that users can communicate with other systems by automatically dialing remote systems under control of an application program or procedure. Serial autodial using the V.25 bis command set is available for synchronous, bisynchronous, and asynchronous communications using one communication line. The IBM and attention command sets are also available for asynchronous communications. The IBM 5853 modem, the IBM 7855 modem, and other equivalent V.25bis modems can take advantage of this autodial support.

      • 3270 Device Emulation

        3270 device emulation allows any AS/400 printer or 5250 display to emulate an IBM 3278 (Model 2 or 5) or 3279 model S2B display station, or IBM 328x printer. Host DBCS applications also can be accessed using an SNA connection. Up to 254 concurrent sessions can be active to the System/370 per SNA connection. The 3270 extended field attributes are translated into the appropriate AS/400 5250 display attributes. Up to 255 input fields per 3270 application screen can be active when displayed on local 5250s. Any remaining 3270 input fields can be accessed by a scrolling function.

      • 3270 SNA API Support for IBM 3278 Model 3, 4, and 5

        This support enables System/370 application programs that were written for IBM 3270 Model 2 thru 5 display stations to be accessed at the 3270 data stream interface level by AS/400 application programs. In addition, 3270 data stream extended attributes are supported by the AS/400 3270 SNA API for 3278 Models 2 thru 5.

      • 5394/5494 SNA Backbone Support

        OS/400 SNA support provides connectivity for 5250 sessions between an AS/400 system and a 5394 Remote Control Unit (with RPQ 8Q0775), a 5494 Remote Control Unit, and with a System/370 subarea using a subarea controller (37XX). Customer investment in SNA backbone networks is protected because no changes are required to AS/400 applications programs to use the 5x94 SNA support. The LU-4 and LU-7 sessions are encapsulated with LU-6.2. APPC sessions are supported as parallel LU-6.2 sessions on the same link as the LU-6.2 encapsulated sessions.

      • File Transfer Support

        The AS/400 user can access file transfer to exchange System/36 data and library members and AS/400 database file members with other AS/400 systems and System/36s. This can be accomplished by using async, BSCEL, or APPC/APPN support. The user interface to this support is callable subroutines from RPG and COBOL programs.

      • Interactive Terminal Facility (ITF)

        ITF allows an AS/400 user, using asynchronous support, to send and receive data through applications such as electronic message services. ITF also exchanges files and library members with other ITF users. ITF can also send DW/36 documents, but it cannot receive documents from other ITF users.

      • SAA Common Programming Interface for Communications (CPI-C)

        SAA CPI-C support provides for program to program communications in the SAA environments of OS/400, OS/2, VM/ESA, VSE/VSA, and MVS/ESA (IMS, CICS, TSO). Because it is an architected, call level interface, applications written to it are portable and protect customer investment in communications programming. The CPI-C is accessible from every SAA language (RPG/400, FORTRAN/400, C/400, and Procedure Language/400 REXX).

        Communications support architected for CPI-C is provided by communications logical unit type 6.2 (LU-6.2). On an AS/400 system, the CPI-C provides an application with transparent access to LU-6.2 session services (commonly known as APPC), to low entry networking (LEN) nodes (type 2.1 nodes), to all APPN networking function, and to data link controls (SDLC, Token Ring, and X.25).

        The source or target for SAA CPI-C applications may be MVS/ESA, VM/ESA, VSE/ESA, CICS/ESA or IMS/ESA nodes. The CPI-C program-to-program session is supported across the SNA subarea and onto APPN networks using any LEN node and APPN application system.

        The AS/400 CPI-C implementation provides the following CPI-C conformance classes, as defined by X/Open's "Developer's Specification for CPI-C":

        • Conversations
        • LU-6.2
        • Recoverable Transactions
        • Data Conversion Routines
        • Security

      • National Language Versions and Multilingual Support

        The following national language versions are available from the program libraries indicated.

                             ||    Program Library Supported     |
                             || SMS- | SMS- | SMS- | SMS- | SMS- |
                             || B    | E    | C    | J    | A    |
                             || USA  | EURO | CAN  | JPN  | AUST |
        |o Albanian          ||  --  | *P/S |  --  |  --  |  --  |
        |o Arabic            ||  --  | *P/S |  --  |  --  |  --  |
        |o Belgian Dutch     ||    S | *P/S |  --  |  --  |  --  |
        |o Belgian English   ||    S | *P/S |  --  |  --  |  --  |
        |o Belgian French    ||    S | *P/S |  --  |  --  |  --  |
        |o Brazilian         ||  --  | *P/S |  --  |  --  |  --  |
        |  Portuguese        ||      |      |      |      |      |
        |o Bulgarian         ||  --  | *P/S |  --  |  --  |  --  |
        |o Canadian French   ||    S |  P/S | *P/S |  --  |  --  |
        |o Chinese           ||    S |    S |    S |   S  | *P/S |
        |  Simplified DBCS   ||      |      |      |      |      |
        |o Chinese           ||    S |    S |    S |   S  | *P/S |
        |  Traditional DBCS  ||      |      |      |      |      |
        |o Croatian          ||  --  | *P/S |  --  |  --  |  --  |
        |o Czech             ||  --  | *P/S |  --  |  --  |  --  |
        |o Danish            ||    S | *P/S |  --  |  --  |  --  |
        |o Dutch             ||    S | *P/S |    S |  --  |  --  |
        |o English U/L SBCS  || *P/S |  P/S |  P/S |  P/S |  P/S |
        |o English U/C SBCS  ||  --  | *P/S |  --  |  --  |  P/S |
        |o English U/L DBCS  ||  P   |  P/S |  --  |  P/S | *P/S |
        |o English U/C DBCS  ||  P   |  P/S |  P-  |  P/S | *P/S |
        |o Estonian          ||  --  | *P/S |  --  |  --  |  --  |
        |o Farsi             ||  --  | *P/S |  --  |  --  |  --  |
        |o Finnish           ||    S | *P/S |  --  |  --  |  --  |
        |o French            ||    S | *P/S |    S |    S |    S |
        |o French MNCS       ||  --  | *P/S |    S |  --  |  --  |
        |o German            ||    S | *P/S |    S |    S |    S |
        |o German MNCS       ||  --  | *P/S |    S |  --  |  --  |
        |o Greek             ||  --  | *P/S |  --  |  --  |  --  |
        |o Hebrew            ||  --  | *P/S |  --  |  --  |  --  |
        |o Hungarian         ||  --  | *P/S |  --  |  --  |  --  |
        |o Icelandic         ||  --  | *P/S |  --  |  --  |  --  |
        |o Italian           ||    S | *P/S |    S |    S |    S |
        |o Italian MNCS      ||  --  | *P/S |    S |  --  |  --  |
        |o Japanese DBCS     ||    S |    S |    S | *P/S |    S |
        |o Korean DBCS       ||    S |    S |    S |   S  |  P/S |
        |o Lao               ||  --  |  --  |  --  |  --  |  P/S |
        |o Latvian           ||  --  | *P/S |  --  |  --  |  --  |
        |o Lithuanian        ||  --  | *P/S |  --  |  --  |  --  |
                             ||    Program Library Supported     |
                             || SMS- | SMS- | SMS- | SMS- | SMS- |
                             || B    | E    | C    | J    | A    |
                             || USA  | EURO | CAN  | JPN  | AUST |
        |o Macedonian        ||  --  | *P/S |  --  |  --  |  --  |
        |o Norwegian         ||    S | *P/S |    S |  --  |  --  |
        |o Polish            ||  --  | *P/S |  --  |  --  |  --  |
        |o Portuguese        ||    S | *P/S |    S |  --  |  --  |
        |o Portuguese MNCS   ||  --  | *P/S |    S |  --  |  --  |
        |o Romanian          ||  --  | *P/S |  --  |  --  |  --  |
        |o Russian           ||  --  | *P/S |  --  |    S |    S |
        |o Serbian           ||  --  | *P/S |  --  |  --  |  --  |
        |o Slovakian         ||  --  | *P/S |  --  |  --  |  --  |
        |o Slovenian         ||  --  | *P/S |  --  |  --  |  --  |
        |o Spanish           ||    S | *P/S |    S |    S |    S |
        |o Swedish           ||    S | *P/S |    S |  --  |  --  |
        |o Thai              ||  --  |  --  |  --  |  --  | *P/S |
        |o Turkish           ||  --  | *P/S |  --  |  --  |  --  |
        |o Vietnamese        ||  --  |  --  |  --  |  --  |  P/S |
           o SMS-B    Software Manufacturing Solutions - USA
           o SMS-E    Software Manufacturing Solutions - Europe
           o SMS-C    Software Manufacturing Solutions - Canada
           o SMS-J    Software Manufacturing Solutions - Japan
           o SMS-A    Software Manufacturing Solutions - Australia
           o '*'   This is the primary library for this NLV.
           o PRI   Primary language feature number
           o SEC   Secondary language feature number
           o P/S   Primary and secondary language supported
           o DBCS  Double-Byte Character Set
           o SBCS  Single-Byte Character Set
           o MNCS  Multinational Character Set

        Multilingual support allows multiple users on the same system to be operating in different languages. This means that system messages, displays and help information as well as user applications can be presented to the end user in his national language.

        Not all licensed programs are translated into all languages nor are all national language versions available from all program release support centers. Contact your IBM representative for more information.

      • Information about Secondary National Languages

        The national language in which the licensed programs is ordered is considered the primary national language. Any other languages are secondary languages. Users can switch among the languages as necessary.

        The executable code is shipped with the primary language. When a secondary language is ordered, a separate tape containing only the translated machine-readable information (MRI) is sent to the customer. The primary language MRI and the national language MRI are installed in separate libraries on the AS/400 system. Each secondary NLV is shipped on a separate tape. Multiple NLVs can be installed on a single AS/400 system.

        Each secondary language is ordered only once per system, not for each licensed program. The secondary language is selected by a feature code of the Operating System/400 (5769-SS1). The secondary language tape contains national language MRI for the products that have been translated for customers by the country translation centers. For products not translated, US English MRI is included. All of the MRI is contained on a single tape volume.

        The Language Dictionaries for AS/400 licensed program (5716-DCT) includes the available national language dictionaries used by IBM OfficeVision for AS/400, and therefore it is not included in secondary national language tapes. AS/400 Client Access installation diskettes are not included with the secondary national language versions. All other support and service activities are only in US English. Regardless of the NLV, all system commands are in US English. Thus, a single set of system commands works in all national language environments.

        To properly display all of the national language characters, the workstation (display and keyboard) must be capable of supporting the desired national language. When a personal computer is used as a workstation supported by the AS/400 Client Access licensed program, its keyboard can be redefined for a national language, specifying the language keyboard type, so that a special language keyboard is not required.

        Each secondary language NLV is shipped from the program library without publications. It is the user's responsibility to determine whether the information in the data base is English or the secondary language. The system does not automatically know which device was used to enter the data. For example, if Spanish information is displayed by an application on an English work station, not all of the Spanish characters are shown correctly. For this reason, it is recommended that Spanish information be kept in one data base and accessed by a Spanish work station, and English information be stored in a separate data base and accessed by an English work station. This example applies also to the other national languages.

        Although translated MRI for multiple products is included on the distribution tape for a secondary language, the customer may use the MRI only for the products for which he is licensed.

      • Universal Coded Character Set Support

        Many customers are doing business in a worldwide environment. It is too costly and time consuming for them to redesign and rewrite an application each time they need to support users in another national language or culture. These applications require the ability to store and process character data from more that one national language. For example, a database file may need to contain customer names in English, German, Greek, Arabic, Japanese and Thai characters. Also, this capability must be available in a client/server environment and in a network of heterogeneous systems that are exchanging character data via customer applications.

        The Universal Coded Character Set (UCS) is an emerging global character encoding, developed jointly by the industry (UNICODE 1.1) and the International Organization for Standardization (ISO). ISO/IEC 10646-1 defines a code page (UCS-2) encompassing the characters used by all currently significant languages, a rich set of scientific and publishing symbols, and a variety of script languages. This common code page, spanning the character sets of many languages, can ease the application development and management issues historically found in multiple code page system environments and networks. This capability is provided in OS/400 with the UCS2 Level 1 support for database that permits characters of any national language to "coexist" in database files.

        UCS2 support also includes character and UCS2 compatibility in comparisons and assignments in SQL, Query for AS/400, and Query Manager. Query for AS/400 and Query Manager also implicitly convert UCS2 data to EBCDIC before displaying and printing so that it can be displayed and printed on existing devices.

      • Locale Support of Cultural Values

        There are also "cultural values" that change from one national language to another, and OS/400 simplifies the tasks that an application must perform to provide local cultural values. This support can be used whether or not an National Language Version (primary or secondary) is installed for that language on the AS/400. Examples of cultural values are:

        • date and time format
        • currency symbol
        • sort (collating) sequence

        Locale support allows for the creation, deletion, and access of locale-based information. C-applications can access locale information via C-runtime functions. Non-C applications can retrieve locale information via APIs.

      • Bidirectional Language Support

        A series of routines transform physical order to logical order. Culturally correct BiDi language support requires that the flow of text, left to right or right to left, be determined by the character entered or displayed at the workstation or printer device. However, the data must be stored in DB2 UDB for AS/400 (or any file system) in the sequence the characters were entered and not how they were displayed.

      International Components for Unicode

      The International Components for Unicode, option 39 of OS/400, is a C and C++ library that adds robust and full-featured Unicode support. It provides internationalization utilities for writing global applications in ILE programming languages.

      As companies weave e-Commerce on a global scale into their fundamental business processes, their prospective customers, established customers, and active business partners can take advantage of increased revenue, decreased expenses, and better customer communications and savings through software internationalization.

      Software internationalization is the development process using libraries, like the International Components for Unicode (ICU) libraries, that enable one single program to work with text in any language, for any place in the world. For example, instead of having software versions for ten different countries, you can use the ICU support to create one version that can work seamlessly and transparently in ten different and unique countries.

      The ICU components are an integral part of software development because they hide the cultural nuances and technical complexities of locale-specific software requirements. These complexities provide critical functionality for applications but they do not burden the application developer with the tremendous effort and high cost to build them.

      For more information about ICU, refer to:


      IBM Business Solutions V1 - V5R3

      IBM Business Solutions is a set of enterprise Web applications available for iSeries servers. Each application is an integrated solution to a common business need that works in conjunction with your existing applications, server components, and enterprise data. They help demonstrate the value of integrated e-business solutions, increase worker productivity, provide services that virtually any business may find useful, and are easy to understand and use.

      Enterprise Web applications must be deployed into an application server before they can be used. Deployment of such applications may be tricky, which is why deployment wizards for the applications provided by IBM Business Solutions are added to the new Web Administration GUI provided by IBM HTTP Server (powered by Apache). The new Web Administration GUI now includes setup and deployment wizards that make the enterprise Web applications provided by IBM Business Solutions ready to use immediately, with WebSphere applications servers you may have already, or with new WebSphere application servers.

      The following describes each of the enterprise Web applications.

      IBM Telephone Directory V5.2

      At its core, IBM Telephone Directory V5.2 is a Web-based business application with an online telephone directory (or "white pages"). It can search, view, and manage information in a directory. Personnel information is managed securely by the OS/400's lightweight directory access protocol (LDAP) server. Another suggested use for the IBM Telephone Directory, particularly for customers with very few employees, is to manage lists of vendors, suppliers, and partners all accessible via Internet, extranet, or intranet.

      IBM Telephone Directory may be used with a directory you may have already set up for your existing applications, a new directory set up by the new Web Administration GUI (described previously), or the IBM Welcome Page application (described below).

      V5.2 of the IBM Telephone Directory application now includes integration with Lotus Sametime servers and Enterprise Identity Mapping domain servers.

      You can:

      • Search by name, job responsibilities, e-mail address, telephone number, department, and division

      • View organizational structure (report-to chart, department listings)

      • Store personalized information (picture)

      • Initiate chat sessions with colleagues using Lotus Sametime technology

      • Add entries to Lotus Sametime contact lists (or Notes "buddy lists")

      • View and self-manage EIM registries

      IBM Survey Creator V1

      IBM Survey Creator V1 is a Web-based business application that can be deployed into a WebSphere Application Server for iSeries. This browser-based application is ready to use for creating, configuring, and managing surveys.

      Web user authentication related information is managed securely by the OS/400 LDAP server.

      The survey application offers multiple question and answer formats to choose from for configuring the content of a survey.

      Information relating to the configuration of a survey, and its subsequent results from users who take the survey, are stored in an IBM DB2 Universal Database on the iSeries.

      You can:

      • Define a list of people in your company that are allowed to conduct online surveys

      • Create and edit surveys

      • Conduct online anonymous surveys

      • Conduct online surveys where survey takers are required to identify themselves (using LDAP authentication)

      • View survey results

      IBM Welcome Page V1.1

      IBM Welcome Page V1.1 is a Web-based business application whose purpose is twofold. First, it provides a starting point for non-administrators, possibly you and your colleagues, with links to the other business applications provided by IBM Business Solutions -- a simple welcome page specifically for business applications. Second, it provides administrative interfaces used for set up and configuration of the other business applications.

      Administrative interfaces, called "Administrator Pages," offer a GUI for setup of new or existing LDAP directories as well as management of directories (LDAP), SSL communication, Sametime, and EIM configuration properties to be used by the other business applications. It offers links to administrative interfaces provided specifically by the other business applications.

      Non-administrative interfaces simply include a welcome page with links to the other business applications.

      The following Administrative interfaces are provided:

      • Set up new or existing LDAP directories for business application data

      • Manage directory LDAP, SSL, Sametime, and EIM configuration properties for all business applications

      • Link to administrator pages provided specifically by the other business applications (if any)

      Non-administrative interfaces:

      • View a menu of available business applications -- Links are shown only for application installed and online/active.

      iSeries Web Technical Support - V5R3

      iSeries Web technical support features assist you in the maintenance of your iSeries system.

      Proactive fix notification -- Now you can be notified when a cumulative or group PTF becomes available. A new proactive fix notification tool sends you an e-mail to inform you of new fixes to help keep your iSeries system up to date. You can subscribe to all of the V5R1, V5R2, and V5R3 PTF groups, cumulative PTF packages, High Impact/Pervasive PTFs (HIPER) as well as any PTFs marked defective. Your preferences are maintained using your IBM web registration ID.

      Improved web-based fix ordering -- Fix information and ordering is available from one convenient place for OS/400, AIX, Linux, cluster software, xSeries, zSeries, TotalStorage, and other products. Features include fix description search and immediate viewing of detailed fix information (size, for example) for most products.

      Customized cumulative PTFs -- Now you can limit cumulative PTF orders to the fixes you need to bring your system up to a selected package level using your system inventory. Your order will be sent to an FTP server ready for you to download at a convenient time.

      Improved online software problem reporting -- Software Service Request provides an improved method reporting and managing software problems on the Web. You can now use one Web application to report problems with IBM-supported software running on iSeries and pSeries. You can create problems with user-defined names, view and update problems and generate reports.

      Communications trace analyzer tool -- The Intelligent Communications Trace Analyzer can diagnose many common connection, performance, and security problems from an iSeries TCP/IP or Trace Connection (TRCCNN) trace. You can download the tool from the Web.

      Web site navigation improvements -- The Web site navigation is organized by product and task to more quickly locate the relevant information. Now if you are trying to plan, upgrade, or solve a problem with your hardware or software, you are presented with information relating to those tasks.



      and select the iSeries support news archive link for more information.

      Business Continuity - V5R3

      Output Queues in Independent Disk Pools

      Clustering has been enhanced in V5R3 to provide support for output queues in independent disk pools. This provides data resilience for spooled output and gives you more flexibility in adapting your application environment for use with independent disk pools.

      Cross-Site Mirroring (XSM)

      Independent disk pools can now be used in a cross-site mirroring (XSM) environment. Cross-site mirroring, combined with a new geographic mirroring function, enables you to generate a mirror copy of an independent disk pool on a system that is (optionally) geographically distant from the originating site. As data is written to the production copy of an independent disk pool, the operating system mirrors that data to a second copy of the independent disk pool through another system. This process keeps multiple identical copies of the data.

      The geographically mirrored independent disk pool maintains all of the benefits of an independent disk pool, while providing more flexible cluster configuration options and protection against local disasters or other failures of the original copy of the data. If a failover or switchover should occur, the backup server can seamlessly take on the role of the primary server and will then own the production copy of the independent disk pool.

      Geographic mirroring is a subfunction of cross-site mirroring (XSM), which is part of OS/400¨ Option 41, HA Switchable Resources.

      Enhanced Disk Protection Options

      If you use device parity protection with a V5R2 input/output adapter (IOA) and OS/400 V5R2 or later, you can choose if you want your parity sets to be optimized for performance, capacity, or a more balanced configuration. At V5R3, a parity set can now also be optimized for availability. Optimizing for availability offers a greater level of protection by allowing a parity set to remain functional in the event of a SCSI bus failure.

      Multipath support for IBM(R) TotalStorage(R) Enterprise Storage Server(R) (ESS)

      At V5R3, up to eight connections can be defined from multiple input/output processors on an iSeries server to a single logical unit number (LUN) in the IBM TotalStorage Enterprise Storage Server (ESS). Each connection for a multipath disk unit functions independently. Multiple connections can provide uninterrupted access to the disks in an ESS even if a single path fails.

      Save-While-Active Enhancements

      At V5R3, for applications that use commitment control, the save- while-active function supports a new option that allows you to complete a save operation without waiting for transaction boundaries . Previously, if you tried to save all objects at transaction boundaries and the applications did not reach commitment boundaries within a specified time, the save operation would fail. The new option allows the save-while-active function to be used to eliminate the save-outage where the volume or duration of the transactions may have previously caused the save operation to fail while waiting to reach commitment boundaries.

      Recovering a file saved with partial transactions uses your journaled changes to complete or rollback partial transactions in order to reach commit boundaries and bring the restored file to a consistent state.It is recommended that you use Backup, Recovery, and Media Services (BRMS) (5722-BR1) to automate your backup and recovery operations. BRMS automatically applies changes to objects with partial transactions and restores them to a usable state.

      Integrated File System Save/Restore Enhancements

      • Performance improvements for SAV and RST operations

      • Name pattern (PATTERN) parameter to make it easier to include or omit a subset of objects

      • Scan objects (SCAN) parameter for use with virus protection program

Back to topBack to top
Technical Description
TOC Link Operating Environment TOC Link Hardware Requirements TOC Link Software Requirements

Operating Environment

Hardware Requirements

i5/OS V5R4 will run on the following hardware:

  • iSeries models 270, 800, 810, 820, 825, 830, 840, 870, 890, SB2, and SB3

  • eServer i5 models 520, 550, 570, and 595

  • System i5 models 520, 550, 570, MMA and 595

  • pSeries models 570, 590, and 595

V5R3 run on iSeries models 170, 250, 270, SB2, SB4, 7xx and 8xx. Also i5 models 520, 550, 570 and 595. In addition, i5/OS will also run on p5 models 9117-570, 9119-590, and 9119-595 configured with a 1.65 GHZ processor.

V5R2 runs on iSeries models 150, 170, 250, 270, 6xx, Sxx, 7xx, and 8xx.

V5R1 runs on all iSeries and AS/400 RISC systems.

V5 requires a minimum main memory size of 128 MB and recommended minimum disk size of 8 GB.

For OS/400 V5, an additional 90MB of free disk space is required as compared to V4R5 for V5 installation and an additional 270 MB of free disk space is required as compared to V4R4 for V5 installation. The total disk space for OS/400 will vary from approximately 350 MB to 1 GB.

Before installation of OS/400 refer to the "Memorandum to Users".

Hardware and Software Requirements for Client Access Express Client:

Client Access Express for Windows

Client Access Express for Windows can be installed on systems with OS/400 V4R5 or later, and requires 112 MB on the server for its install image.

Many functions of the Express client are included with OS/400. However, the PC5250 display and printer emulation and Data Transfer functions can only be used if the Client Access Family product (5722-XW1) is installed on the iSeries server.

Once the Express client is installed on the PC, the client can connect to OS/400 V4R4 or later.

PC Requirements

  • Client Access Express without iSeries Navigator:
    • Windows 98/98/Me/NT 4.0: Pentium(R) 100 MHz and at least 32 MB of memory
    • Windows 2000: Pentium 133 MHz and at least 64 MB of memory

  • Client Access Express with iSeries Navigator:
    • Windows 95/98/Me: Pentium 200 MHz and at least 64 MB
    • Windows NT 4.0/2000: Pentium 200 MHz and at least 96 MB, 128 recommended

Hardware Requirements for Integration for Windows Server:

  • iSeries Server Requirements

    • Integration for Windows Server can be used with the following RISC models of the iSeries and AS/400 systems: 8xx, 270, SB2, and SB3

    • Integration for Windows Server requires an Integrated Netfinity Server feature using a Pentium processor.

Software Requirements

Some OS/400 functions are separate OS/400 features, and some OS/400 functions are optionally installable.

Backward Object Support

Supported objects created with OS/400 V4R4 can be saved and subsequently restored and used on the following OS/400 releases: V4R4 and V4R5 Standard TGTRLS support is used to implement this function.

Program objects must be created as observable.

Software Requirements for EZ-Setup Wizard:

EZ-Setup Wizard requires Windows operating system component Dial-Up Networking Version 1.2, or later. The Wizard checks for the presence of the correct version of Dial-Up Networking and provides details on obtaining and installing it, if necessary. However, to prepare ahead of time, follow these instructions:

  • Windows NT: Remote Access Service from the Windows NT CD; then apply Windows NT Service Pack 3, or higher. Download this software from the Microsoft home page at:

  • Windows 95, older versions before OSR2:

    Download the Dial-Up Networking upgrade from the Microsoft home page at:


  • Windows 98, or newer versions of Windows 95 (OSR2, or later):

    Use Dial-Up Networking from the Windows CD.

Back to topBack to top
Planning Information

Customer Responsibilities

Refer to the "Memorandum to Users" (shipped with the machine readable material and available from your IBM representative) for information necessary to plan the installation process, including estimation of the time required.


Beginning with V3R6, all of the TAATools (about 300 tools) in the QUSRTOOL example library are no longer shipped with OS/400. The TAA Tools examples provided in earlier releases of OS/400 may still be used on V3R6, or later release. These earlier versions of the TAATools were provided on an as-is basis, and some may need code alterations to operate correctly on V3R6, or later release. If you wish to bring an earlier version of TAATools forward to V3R6, or later release, and they were created with the default of no observability, you will need to either recompile with observability on your current release or restore the source and recompile on the desired release.



  • i5/OS supports a maximum of 32 processors per partition.

  • Client Access Express Client:

    Client Access Express runs on Microsoft Windows 95, 98, NT 4.0, and 2000 operating systems. It can be used to connect iSeries and AS/400 systems running OS/400 V4R4, or later.

  • Operations Console - Remote Control Panel:

    The iSeries servers 270, 820, 830, and 840 use a new interface to connect the Remote Control Panel. The Remote Control Panel uses a parallel interface, Enhanced Parallel Port (EPP), to connect. The PC used must have an EPP capable port.

    The EPP support for the Remote Control Panel is only available with Windows NT Workstation* and Windows 2000 Professional*.

Performance Considerations


Back to topBack to top

Soft copy publications are shipped on CD-ROM. With the initial order, a two-CD kit (Information Center and Information Center: Supplemental Manuals) is shipped with OS/400. Additional copies of CD-ROMs are available for a fee by ordering SK3T-4091 through Puborder. The CD-ROMs contain all of the technical information for iSeries including information for programs that may not have been ordered.

The Information Center can be displayed, using a Web browser on a PC, or can be selectively installed on your iSeries system. The Information Center Supplemental Manuals contain PDF that can be viewed using Adobe Acrobat reader. The contents on the Information Center and Information Center Supplemental Manuals CD-ROMs are also available on the Internet at:


Back to topBack to top
Security, Auditability, and Control

This program uses the security and auditability features of the OS/400 operating system.

The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.


(R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

** Company, product, or service name may be a trademark or service mark of others.

Windows is a trademark of Microsoft Corporation.

UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.
 © IBM Corporation 2012.
Back to topBack to top

Share this page

Digg Linked In

Contact IBM