HCL Technologies Ltd.

An Introduction to the AS/400 / iSeries / i5 Mid-Range System (Part 1)

Joy Patnaik

Agenda
Introduction to AS/400, iSeries and i5 Getting Help Commands and Nomenclature of Commands Objects Signing-On

What is an AS/400?
Application System/400 - mid-range application system from IBM
Mid-Range - Between microcomputers and mainframe computers in terms of processing speed, storage capacity and the number of users that can be supported at once.

Expansion of S/38 architecture

Also provided application program compatibility with S/36.

Provides robust support for Multi-user, multi-tasking, security, availability and ease of operation

History of AS/400
AS/400 - result of the Silver Lake project at IBMs Rochester centre (1988)
Jul 1969 IBM introduces S/3 (System 3) IBM makes its debut in systems smaller than mainframes Jan 1975 IBM introduces S/32 32 KB RAM, 13 MB HDD, KBD, Monitor of 240 characters (6 lines x 40 col) Apr 1977 IBM introduces S/34 256 KB RAM, 14 GB HDD, multiple workstation support, support for printers, max 8 local users at a time Oct 1978 IBM introduces S/38 Architecture change, 32 MB RAM, 14 GB HDD, 256 local workstations May 1983 IBM introduces S/36 7 MB RAM, 1.4 GB HDD, 72 local workstations Jun 1988 IBM introduces the first AS/400 (AS stands for Application System, Expansion of S/38 architecture, Provided Application compatibility with S/36)

History continues
Enhanced Series or e-series
1994 development began Foresaw potential of Internet Announced August 1997 New n-way processors up to 12-way First package machine
A server configured and preloaded with SAP software

Moving from AS/400 to iSeries, then to i5

iSeries name introduced in 2000 i5 name introduced in 2004
Based on 64-bit microprocessor (POWER5) From OS/400 to i5/OS V5R3 From DB2/400 to DB2 UDB for iSeries Run i5/OS, Linux, Windows and UNIX (AIX) on a single server
Enables server consolidation aided by legendary availability

Capacity On-Demand (CoD) Computing resources permanent and temporary for immediate and future needs

Why does a company use an AS/400?

Cost effective Reliable Easily upgraded as business grows Supports state-of-the-art technology Doesnt require a large support staff Fully integrated hardware and software components
database,security, communication and internet components

Technology-Independent (TIMI)

System Architecture - 1
Single-Level Storage
No distinction between disk storage (DASD) and main memory One large storage area combining disk storage (DASD) and main memory = single address space = Single-level storage. Object must be in memory to use or operate on OS/400 enjoys very large virtual memory. This enables programs and users asking for data by name / pointer and not by address (Capabilitybased addressing scheme)

Technology Independent Machine Interface (TIMI)

Enables business to exploit changes to hardware and software technology without causing disruption to existing applications Technology neutral architecture (more details in next slide) Application does not deal with storage device specifics

System Architecture - 2
AS/400 machine - defined as a software interface in a Layered Architecture
HLL (High-Level Language programs) ISS (Integrated System Services) / OS/400 MI (Machine Interface) Defines a logical (rather than physical) machine LIC (Licensed Internal Code) / VMC (Vertical Microcode) / IMPI (Internal Machine Program Instruction) / Operating System Supervisor Insulates higher layers from any hardware change SLIC (System Licensed Internal Code) / HMC (Horizontal Microcode) True microcode (control solid state circuits) Solid State Hardware

System Overview
Application Software Application Software OS/400 Machine Interface (MI) Vertical Licensed Internal Code (VLIC) Internal Microprocessor Interface (IMPI) Horizontal Licensed Internal Code (HLIC) System Licensed Internal Code (SLIC) OS/400 Machine Interface (MI)

Object Based Kernel

Hardware CISC Processor 48-bit Addressing

Hardware RISC Processor 64-bit Addressing

AS/400 Architecture Used in 48-bit CISC-based Systems T 1.1 - AS/400 layered software architecture.

AS/400 Architecture Used in 64-bit PowerPC RISCbased Systems

AS/400 Features - 1
Several choices of models
can balance between requirement and financial budget.

64-bit processor
64-bit memory addressing means large working storage memory provides enhanced arithmetic capabilities

OS/400
Object-based OS

Hot-Plugging
Add or Remove an I/O device/card without shutting down the server

AS/400 Features - 2
Single Level Storage
Auxiliary storage is treated as an extension of the working storage OS/400 enjoys very large virtual memory

Integrated RDBMS
DB2/400 provides a high level of security as the control to DB2/400 is controlled by OS/400

Double Byte Character Set

Allows users to generate characters more than EBCDICs usual set AS/400 is used to represent more than 50 languages in the world

AS/400 Features - 3
Most secured operating system of industry
Various logs and Audit trails makes system C2 level secured.

LPAR
Logical Partitioning offers multiple environments on same server
User can run Windows NT, LINUX

Multi-threaded environment
Multiple subsystems manage concurrent jobs.

AS/400 Key Advantage

Software

Applications do not have to be changed or recompiled with the operating system changes and/or hardware changes.
No-pain

versions No-pain transition from older CISC (Complex Instruction Set Computing) microprocessor architecture to newer RISC (Reduced Instruction Set Computing) architecture in 1995 CISC Instruction length variable RISC Equal instruction length From 48-byte to 64-byte word size

transition from older OS/400 versions to later

IBM AS/400 Help

F1 = HELP Field-level Help Extended Help Info Centre of IBM
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rzahg /rzahgictoc.htm

Naming of Commands - 1
Based on English! Combination of Verb and Noun
CRTLIB

Create

Library

Naming of Commands - 2
Typically start with the following verbs:
CL Verb
CALL GO CPY CRT DSP

English
Call Go to Copy Create Display

Description
Executes a program Executes a Menu Copies a file Creates an object Displays something about an object Works with an object

WRK

Works With

Naming of Commands - 3
Some typical nouns
CL Noun
LIB LIBL OUTQ JOBQ FD F USRPRF

English
Library Library List Output Queue Job Queue File Desc File User Profile

Description
Object that holds Objects List of Libraries for a Job Object that stores Spool Files Object that stores Batch Jobs to be processed Description of file Object that stores data Object that lists attributes about a Sign On Id

Command Help
How do I find the exact syntax (including keywords) of a command?
Answer: Use AS400 Menus Use AS400 Prompts (F4)
by pressing F4 at a Command line by typing command and pressing F4

How do I find the Keywords to a command?

Answer: Type the command and press F4

CL Commands (Examples)
AS400 Menus
Menu
MAIN PROGRAM MAJOR CMDCPY CMDDSP CMDWRK CMDLIB CMDMSG CMDOUTQ CMDUSRPRF

Description
Main Menu Programmers Menu Sorts Commands Copy Commands Display Commands Work With Commands Library Commands Message Commands Output Queue Commands User Profile Commands

* (Asterix)
When

used before an AS/400 word, indicates that the word is a special value.
eg. CRTLIB LIB(MOOGK1) TYPE(*TEST)

When

used at the end of a word, indicates a generic combination of alphanumerics (wildcards).

eg. WRKLIB SIMON*

Use of the ?
Entering

a command to see all possible values for a parameter. F4 does the same

What is an Object?
OS/400 object is a named unit exists (occupies space) in storage operations are performed on it by the operating system.
Has

a Description Has an Object Type

Object Structure
Object name, type, owner, library, Object etc. Header Portion This could be a files data, program statements, etc. Function Portion of Object

Object Properties

Name Type Owner name Creation time Save time Text description

Library Attributes Creation date Save date Off-line size Change date

Object Types
Object

Type is assigned to the Object at time of creation

eg. CRTLIB creates objects with a type of *LIB

Certain

types of commands only work with certain types of Object Types

eg. DSPUSRPRF

Object Types - Examples

*CMD
*LIB *FILE

*PGM

Command Library File Program

(These and other Object Types will be covered in more detail in later sessions. For now think of Objects as the basic building blocks of the AS/400. Anything that isexistent on the AS/400 including anything that you create for an application - is an Object)

Object Attributes
*FILE

Physical

Logical

Display

Printer

ICF

Source

Data

Screen

Menu

Members

Common Features of an Object - 1

Each

object has a name Each object has a set of attributes that describe it
Specific

values are assigned for those attributes

Generally,
However,

objects are independent of all other objects.

some objects must be created before other objects can be created; For example, a logical file cannot be created if the physical file it must be based on does not exist.

Common Features of an Object - 2

Objects

must be created before other operations that use the object are performed. Objects have either a simple, qualified, or generic name.
Will

be covered in more detail in subsequent sessions

Storing Objects - 1
All

non-Library objects are stored in Libraries (containers of objects)

Special

Rule : QSYS library contains all other libraries

Some

objects cannot be stored in userprovided libraries.

Example

: *AUTL (Authorization List)

Storing Objects - 2
When

a user creates an object and a library qualifier can be specified but is not, the object is stored in the user's current job library.
The

user profile for each user specifies the user's current library. The current library will be QGPL if it is not specified otherwise.

Client Access
Windows-based software to access the AS/400 Simulates 5250 terminals of the AS/400 Has 24 function keys
F1-F12 and Shift-F1 thru Shift-F12

Can be customized for keys

The Sign-on Screen

First level of security Keeps out unauthorized people Requires valid user-id and password Can specify initial program to execute (and where to pick-up that program from)

The Sign-on Screen

Main Menu

Major Menu

Verb Menu

Clear Commands Menu

Clear Physical File Command

? in Member Parameter

Definition of the Member Parameter (Field Level Help)

Definition of the CLRPFM Command (Extended Help)

CL Syntax
Command-name (space) parameter

Commands not Requiring Parameters

WRKJOB WRKACTJOB WRKSBMJOB

Keyword vs Positional Notation

Keyword WRKOUTQ OUTQ(PRT01) CRTLIB LIB(MOOGK10) + TEXT(Cindys Library)
Positional

WRKOUTQ PRT01 CRTLIB MOOGK10 *PROD Cindys Library

System Request - 1
System Request System: Select one of the following: 1. 2. 3. 4. 5. 6. 7. Display sign on for alternative job End previous request Display current job Display messages Send a message Display system operator messages Display work station user BIGBLUE

10. Start system request at previous system 11. Transfer to previous system 13. Start system request at home system 14. Transfer to home system 90. Sign off More... Selection ______ F3=Exit F12=Cancel (C) COPYRIGHT IBM CORP. 1980, 1998. Figure 2.4 System Request Menu

System Request - 2
Option #1 This option displays a sign on screen for an alternative job. After signing on to an alternative job, you can than use this option to toggle between your primary and secondary job. (Note: only one session is active at a time.) This message CANCELs your previous command (action). This option allows you to display your current job information. This option allows you to display messages that have been sent to you. This option allows you to send a message. This option lets you display message on the QSYSOPR (the system operators) message queue. This option allows you to display information about the jobs running from your workstation. These options apply to networks of systems and may not be displayed on your system. This option allows you to sign-off of the session.

Option #2 Option #3 Option #4 Option #5 Option #6

Option #7 Option #10, 11, 13, and 14 Option #90

AS/400 Operations
OS400 Command Structure Message Handling Managing Devices Handling Spooled Files and Printing Functions Operating System, Licensed Program Products, and PTFs Security Starting and Stopping the AS400 Work Management and Performance Working with Jobs

Basic Troubleshooting, Problem solving, and Using Electronic Customer Support

Subsystems

The AS/400 is Green Screen Usually !

Green screen v.s. GUI (Graphical User Interface
You cant point and click! You must use the TAB keys to go from field to field

In recent OS versions, GUI interfaces have been made easier to implement