V2.0.0.

3
Student Notebook

Uempty Unit 2. iSeries Overview and Concepts

What This Unit is About

This unit introduces the basic concepts of the iSeries. This material is
a review of some of the basic concepts that are taught in the
prerequisite course, the iSeries System Operator Course.

What You Should Be Able to Do

After completing this unit, you should be able to:
• Describe iSeries system architecture
• Describe iSeries system objects
• Explain the syntax of iSeries commands
• Explain the concepts of libraries, library list and jobs
• Explain the concepts of printing on iSeries
• Explain the device description and creation

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Unit Objectives
After completing this unit, you should be able to:
Describe iSeries system architecture
Describe iSeries system objects
Explain syntax of iSeries commands
Explain concepts of libraries, library list and jobs
Explain concepts of printing on iSeries
Explain device description and creation

Figure 2-1. Unit Objectives OL197.0

Notes:
The material presented in this unit will review some of the basic concepts you will need to
successfully complete this course. You should already have a general understanding of
these concepts from either personal experience or from having attended the iSeries
System Operators Course.

2-2 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty 2.1 iSeries Overview

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

iSeries Advanced Integrated Architecture

Application Software Application Software

iSeries

iSeries
Hardware

Hardware

Traditional System Architecture iSeries Architecture

Figure 2-2. iSeries Advanced Integrated Architecture OL197.0

Notes:
Many functions that have traditionally been performed by system control programs or
add-on programs are integrated into the licensed internal code so that they can be
performed more efficiently.
The iSeries system insulates users from hardware characteristics through the layered
machine architecture. This layered architecture raises the level of the machine interface,
creating a high-level machine instruction set that is independent of the underlying hardware
implementation.

2-4 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Single-Level Storage

Virtual Address Space With Objects

PROGRAM DATA DATA PROGRAM DATA PROGRAM

PROGRAM PROGRAM DATA DATA DATA

DATA PROGRAM DATA PROGRAM DATA

JOB QUEUE OUTPUT QUEUE
PROGRAM DATA
USER PROFILE LIBRARY

Main Auxiliary
Storage Storage

Figure 2-3. Single-Level Storage OL197.0

Notes:
All system storage (whether main storage or disk storage) is addressed in the same way.
This single, device independent addressing mechanism means that objects are referred to
by name or name and library, never by disk location. All objects are created as if they
reside in a 18,446,744,000,000,000,000 byte address space.
The iSeries system's virtual addressing is independent of an object's physical location, and
the type, capacity, and number of disk units on the system.
What this means is that application programs do not require modification in order to take
advantage of new storage technologies. Users can leave all storage management entirely
to the machine.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

iSeries Devices

INPUT PROCESS OUTPUT

Processing
Unit

Figure 2-4. iSeries Devices OL197.0

Notes:
The following devices can be attached to your iSeries system:
• Printers
• Workstations
• Tape units
• CD-ROMs
• Remote controllers
• Personal computers (PCs)
Your system receives data (input) from several devices including each workstation, disk,
tape, and CD-ROM attached to the system. The processing unit (which is contained in the
system unit) processes the data (that is, it performs operations on the input such as adding
numbers together or comparing two values to determine if they are the same). The iSeries
system then saves the data (output) to disk or tape or it sends the output to a printer or
workstation.

2-6 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Sample Configuration

iSeries System SDLC

(Montreal) communications
line
Workstation
LAN adapter Tape unit Diskette unit CD-ROM unit
controller

Console Order Entry

Token Ring Shipping and Receiving Modem
Display
Display Controller
Display Display Paris

Display
Accounting

Display Printer Printer

Printer Printer

Figure 2-5. Sample Configuration OL197.0

Notes:
This visual shows a sample iSeries configuration which is the physical and logical
arrangement of devices and programs that make up a data processing system. This
configuration is simple so that it can be easily understood and read. Every iSeries
configuration varies depending on the needs of the business.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Software Overview

Application
Support

Programming
Support

Operating
System/400

Licensed Internal
Code

Figure 2-6. Software Overview OL197.0

Notes:
In addition to knowing which devices are attached to your system and how to operate them,
you should also be familiar with your system software (or programs). A program contains a
set of instructions that allows you to perform one or more related tasks.
There are four primary categories of programs in the iSeries which build on each other.
These are illustrated in the above graphic, and they are (top to bottom) the application
support, the programming support, Operating System/400, and finally the Licensed Internal
Code (LIC).

2-8 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Licensed Internal Code

A group of programs located

in storage that allow OS/400
to run on different iSeries
system models.

Figure 2-7. Licensed Internal Code OL197.0

Notes:
Licensed Internal Code is often referred to as LIC. It is provided by IBM and is pre-installed
on your iSeries system prior to the system being shipped.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Operating System/400 (OS/400)

Set of programs that control the

OS/400 operation of an iSeries system

Provides support for:

Control Language and Menus Device Management

System Operator Services Save/Restore Services
Work Management Data Management
Security Message Handling
Programmer Services Communications

And more....

Figure 2-8. Operating System/400 (OS/400) OL197.0

Notes:
You can think of OS/400 as the brain of the iSeries system. It is a group of system
programs that control the overall operation of the iSeries system. For example, OS/400
allows multiple interactive and batch jobs to run concurrently. It provides the interface
which allows operator control of those jobs and allows security to be set up on your system.
OS/400 is provided by IBM and comes pre-installed on your iSeries system.
Although not all OS/400 functions are needed in every installation, the full range of
functions is available on every iSeries system.

2-10 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Programming Support

Java

ILE ILE
RPG C

VisualAge ILE
C++ COBOL

WebSphere
Development
Studio Client
SQL

Figure 2-9. Programming Support OL197.0

Notes:
In addition to languages such as Java, C++, ILE RPG, ILE C, and ILE COBOL, there are
tools that aid you to edit source programs, to design screen displays and menus, and to set
up test files.
The WebSphere Development Studio Client product (WDSC) consists of the following
workstation tools:
1. CODE/400
2. VisualAge RPG
3. WebSphere Studio for iSeries
4. VisualAge for Java for iSeries
5. IBM Distributed Debugger

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

All Software on a System

Figure 2-10. All Software on a System OL197.0

Notes:
This is the iSeries Navigator view of all software on a system. You can display this by:
1. Expand system folder under My Connections
2. Expand Configuration and Service
3. Expand Software
4. Click Installed Products
The DSPSFWRSC (Display Software Resources) CL command allows the user to show,
print, or write to an output file the list of installed software resources.

2-12 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
iSeries Objects

Library
*LIB
File Program
*FILE *PGM

User Profile Output Queue

*USRPRF *OUTQ

Message Queue
*MSGQ

Command Job Queue

*CMD *JOBQ

Job Description Subsystem Description

*JOBD *SBSD

Figure 2-11. iSeries Objects OL197.0

Notes:
Every iSeries object has a name, occupies storage and is stored within a library. Each
object can be created and deleted with CL commands.
There are many types of objects on the system.
Each object type has its own identifier. The identifiers for the objects, as well as the objects
themselves, are shown on the visual. For example, the identifier for file is *FILE, for a
program is *PGM, and so on.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Object Identification (1 of 2)

Library, Name, Type

Library
QSYS

Library Library
PAYROLL OPRLIB

Program File File File

MASTER MASTER MASTER ACCOUNTS

Figure 2-12. Object Identification (1 of 2) OL197.0

Notes:
OS/400 uses the object name + library name + object type to uniquely identify objects on
the iSeries. The graphic above demonstrates this. There are 2 objects named MASTER in
library PAYROLL. One is a program (*PGM) and the other is a file (*FILE).
A library is an object used to group related objects and to find objects by name. Thus, a
library is a directory to a group of objects.

2-14 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Object Identification (2 of 2)

Figure 2-13. Object Identification (2 of 2) OL197.0

Notes:
The above iSeries Navigator panel shows the name, type, properties and other
characteristics of each object.
The QSYS.LIB file system supports the iSeries server library structure. This file system
gives you access to database files and all of the other iSeries server object types that the
library support manages within the system and basic user ASPs.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

CL Command Structure

Command Name Parameter

CRTLIB LIB(PAYLIB)
Action Item Keyword Value
Abbrev.

Figure 2-14. CL Command Structure OL197.0

Notes:
All iSeries system functions are controlled with a single language, called Control Language
(CL). CL commands have a special structure and have parameters to tell the system how
to perform requested functions.
Individual commands can be executed by anyone authorized to use a command, on the
command line, within a job stream or a program, and in any type of job. Even when a menu
option is used to perform a system function, one or more CL commands are executed by
OS/400. There are over 1200 commands available on the iSeries.
Each command consists of a command name followed by zero, one or several (up to 75)
optional parameters.
• A command name consists of two abbreviated parts: an action and an object on which
the action is performed.
• A parameter also has two parts: a keyword followed by a value in parentheses.
Commands can be entered from the command line, via the command entry display, or a
program.

2-16 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Library

Object Name Type Location

FILEC *FILE ##
PROGA *PGM @@
DSPJOB *CMD %%

PROGA
FILEC

DSPJOB

Figure 2-15. Library OL197.0

Notes:
A library is a special type of object which contains a named set of objects and is used to
group objects. Basically, it is a directory to other objects. It is not an allocation of space as
on some other systems.
The only way an object can be located and used is through the library which points to it.
The objects to which a library points are not physically in the library. In fact, they are not
necessarily stored next to one another (contiguously) on disk.
There are many libraries on the iSeries system. Objects are normally organized by library
(either by IBM or the administrator) based upon their relationship to one another. Here are
some examples of how objects can be organized:
• For security
• For backup
• By application
• By owner
• By object type: program vs. files
• By use: production vs. test

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Simple Name Versus Qualified Name

SIMPLE NAME: PGM1

VS.

QUALIFIED NAME: LIB1/PGM1

Library Object
Name Name

Figure 2-16. Simple Name Versus Qualified Name OL197.0

Notes:
When an object is referred to simply by its name, the system will use the library list to locate
the object.
When an object is qualified, by also using the library name, the system is able to go
directly to the object without searching the library list.

2-18 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Library List

QSYS *LIBL
System Libraries QSYS2
(15 maximum) QHLPSYS
QUSRSYS

QRPGLE
Product Libraries QCBLLE

PAYLIB *CURLIB *USRLIBL

Current Library
QGPL
User Libraries QTEMP
(250 maximum) PAYTSTLIB

ONE ASSOCIATED WITH EVERY JOB

Figure 2-17. Library List OL197.0

Notes:
The iSeries system uses a library list to find the files and programs you need when you run
applications. The library list is a list of libraries the system searches sequentially for objects
needed by the user. It has two parts; the system portion and the user portion.
The system portion is specified in the QSYSLIBL system value. The system portion is
used for Operating System/400 libraries. The default for this system value does not need to
be changed.
The user portion is provided by the QUSRLIBL system value, the initial library list
specified in the user's job description, or commands after the user is signed on. If you have
an initial library list, it overrides the QUSRLIBL system value. Application libraries should
be included in the user portion of the library list.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Your Job's Library List is Built at Sign On

} }
QSYSLIBL QSYS
QSYS2 System
QSYS
QHLPSYS Part
QSYS2
QHLPSYS QUSRSYS

}
QUSRSYS Program
Product
Part
QUSRLIBL Current

}
FREDLIB USER PROFILE
QGPL Library

}
CURLIB(FREDLIB)
QTEMP
QGPL User
Job Descr INLLIBL 1 2

}
QTEMP Part
QGPL
PAYLIB
QTEMP SIGN ON
PAYLIB
CURRENT LIBRARY FREDLIB
1 The job description can override system value QUSRLIBL
2 Value entered on Sign On panel overrides value in profile

Figure 2-18. Your Job's Library List is Built at Sign On OL197.0

Notes:
The library list is not a permanent structure. One is built for a job when it starts and is
deleted at EOJ.
Note: A job is any piece of work accomplished on the iSeries.
Your library list can be modified after sign on through the use of CL commands:
CHGSYSLIBL (Change System Library List) Changes the system libraries

CHGCURLIB (Change Current Library) Changes the current library

ADDLIBLE (Add Library List Entry) Changes the user libraries

RMVLIBLE (Remove Library List Entry) Changes the user libraries

CHGLIBL (Change Library List) Changes the user libraries

EDTLIBL (Edit Library List) Changes the user libraries

2-20 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Finding an Object

Simple Name: CALL PAY02

Qualified Name: CALL PAYTSTLIB/PAY02

QSYS INQLIB Job's Library List

QCWW QCXXX PAY77 AP60 QSYS

QSYS2 System Libraries
QHLPSYS
QCZZZ QCYYY PAY99 AP55 QUSRSYS

QRPG Product Libraries

QCBL
PAYTSTLIB PAYLIB Current Library
PAYLIB
AP55 PAY02 PAY01 PAY04
QGPL User Libraries
QTEMP
PAYTSTLIB
PAY01 AP05 PAY02 PAY05
INQLIB

Figure 2-19. Finding an Object OL197.0

Notes:
Which copy of the program PAY02 will be run when it is called using the simple name?

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Types of Jobs

Job--A unit of work to be done by the system

User Jobs

Interactive
System Jobs
Batch Autostart
Spooling

Communication

Qualified Job Name--Consists of Three Parts:

Job Number User Name Job Name
003945 / SMITH / PRTINV

Figure 2-20. Types of Jobs OL197.0

Notes:
A job is the basic unit of work on the system. Every job has a unique name, made up of a
system assigned sequential number, the name of the user running the job, and a user
assigned job name.
Spooling jobs are system provided print programs (writers) that run similar to batch jobs
and print spooled printer output. Using work management, you can control these writers.
Interactive jobs are workstation jobs, started when a operator signs on the workstation
display and ended when the user signs off the workstation display.
Traditionally, batch jobs are run by submitting requests for processing of data by programs
that do not need to interact with the user. These requests are placed on a job queue and
run when system resources become available.
Communication jobs are those which are started by a request made over a
communication line from another system.

2-22 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty Autostart jobs are specified to start automatically when its associated subsystem is
started. Autostart jobs typically do such things as set up or clean up after an application,
perform backups of data files, start devices, or vary on or off communication lines.
Every job on the iSeries must be associated with a job description.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Starting and Ending a Job

JOB TYPE START END

Interactive Sign-on Sign-off

Batch Placed on jobq EOJ

Autostart Start subsystem EOJ

Communication Request from remote Same as batch or

system interactive
Spooling Start writer command End writer command

Figure 2-21. Starting and Ending a Job OL197.0

Notes:
Different types of jobs start and end in different ways.
Each time a user signs on to a workstation, a new interactive job begins. That job
continues until the user signs off.
A batch job begins when the job leaves the job queue.
An autostart job begins when its associated subsystem is started and ends when the job
ends.
A communication job begins with a request from a remote system and depending upon
whether it is an interactive or batch job, ends when the user signs off or the job ends.
A spooling job begins when the printer writer is started and ends when the printer is
ended.

2-24 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Job Control Summary

SBMJOB

JOBQ
BATCH

OUTQ WRITER PRINTER

INTERACTIVE

CALL
WKRJOBQ WRKACTJOB WRKOUTQ WRKWTR
WRKSPLF

WRKUSRJOB
WRKSBMJOB
or
iSeries Navigator

Figure 2-22. Job Control Summary OL197.0

Notes:
On this visual, the term job means user jobs; active batch and interactive jobs, jobs on job
queues, and jobs on output queues. After a job has started, you can locate that job, monitor
its status and activity, and change the way it processes as well as changes some of its
printing characteristics now and in the future.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Job Properties (1 of 2)

Figure 2-23. Job Properties (1 of 2) OL197.0

Notes:
Job attributes from the job description and user profile appear in a job's properties. To view
this information follow these steps:
1. Expand the system you want to explore
2. Expand Work Management
3. Click Active jobs

2-26 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Job Properties (2 of 2)

Figure 2-24. Job Properties (2 of 2) OL197.0

Notes:
The details of specific jobs can be found on the following tabs:
• General - the job description name being used by the job and the subsystem that is
controlling it
• Performance - the memory pool that the job is using and job performance statistics.
• Printer Output - properties that affect the printed output of the job are listed here and
can be viewed or changed
• Messages - lists the messages sent to and from this job that are to be handled
• Job Log - information detail to be kept for the job
• Server - information about server jobs
• Security - provides the user profile for the job
• International - properties that relate to text, character format and language associated
with the job are listed here and can be viewed or changed

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

• Threads - properties that relate to threads for a currently active job or one that is in a
job queue are listed here and can be viewed or changed
• Other - properties that relate to the accounting code, DDM connections, and switch
settings are listed here and can be viewed or changed

2-28 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
What Is a Job Description?
Display Job
Description

System: DALLAS
Job Description: QDFTJOBD Library: QGPL

User profile............................... : *RQD

CL syntax check............................ : *NOCHK
Hold on job queue.......................... : *NO
End severity............................... : 30
Job date................................... : *SYSVAL
Job switches............................... : 00000000
Inquiry message reply..................... : *RQD
Job priority (on job queue).............. : 5
Job queue.................................. : QBATCH
Library................................. : QGPL
Output priority (on output queue)......... : 5
Printer device............................. : *USRPRF
Output queue............................... : *USRPRF
Library................................. :

More....

Message logging:
Level..................................: 4
Severity...............................: 0
Text...................................: *SECLVL

Figure 2-25. What Is a Job Description? OL197.0

Notes:
A job description is an object that contains a set of information (attributes) that specifies
how a job should be run on the iSeries system. There are many job descriptions on every
iSeries.
Each job run on an iSeries system must have a job description associated with it. Each job
description can have multiple jobs associated with it.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Job Description Attributes

A job description contains a specific set of job-related attributes :
Initial library list
Which job queue to use
Scheduling priority
Routing data
Message queue severity
Output queue information
User parameter
The attributes determine how each job is run on the system.
QDFTJOBD is a system-supplied job description in library QGPL.

Figure 2-26. Job Description Attributes OL197.0

Notes:
The job description holds properties that the job will use as it goes through the work
management life cycle. These properties include the user profile the job will start to run
under, the request data (which tells the job what it will do), and the initial user portion of the
library list, as well as others. The job description also holds information that tells the job
which job queue to enter and the routing data. The routing data is later used by the
subsystem to find the routing entry that contains information needed for the job to start
running. The output queue is also defined within the job description, tells where printer
output (also called spooled files) from a job will go.

2-30 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Message Summary
Messages
Send, display, respond, and remove
Informational, break, or inquiry
Message Queues
Allocate and change delivery mode
Break, notify, hold, and default

Figure 2-27. Message Summary OL197.0

Notes:
Messages are used to communicate with the system, other users, monitor system activity,
and control jobs. The two main types of messages are informational and inquiry messages.
A workstation can communicate with a lot of different message queues that exist on the
iSeries system. The system has message queues for each device configured to the
system, a queue for the system operator (QSYSOPR), and application and system
programs have program and job message queues. Message queues are created when a
workstation device description is created, a user profile is created, or with the Create
Message Queue (CRTMSGQ) command.
Message queue modes determine how a message will be delivered. There are four
delivery modes:
• Break mode (*BREAK) - When a message is received that is equal to or exceeds the
severity filter, the terminal alarm will sound and the message will be displayed
immediately.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

• Notify mode (*NOTIFY) - The default mode for workstation and user message queues.
The message is held in the message queue and the message light will come on.
• Hold mode (*HOLD) - The user is never notified of messages that arrive in the message
queue. It is the responsibility of the user to periodically look in the queue for messages.
• Default mode (*DFT) - Any messages requiring a reply are answered with the default
reply set up for the message. Information only messages are ignored.

2-32 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Basic Message Queue Communication

{ }
PROFILE
DSP01 OPR01

CRTDEVDSP: CRTUSRPRF
User
OPR01 Message
Queue
DSP01

Workstation
Message
Queue

CRTMSGQ: ARDEPT QSYSOPR System Supplied

User Created System Operator

Message Queue Message Queue

Figure 2-28. Basic Message Queue Communication OL197.0

Notes:
The visual depicts some of the commands that are associated with and use message and
message queue information.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Which Output Queue?

Job Description

Job's Process
Access Group (PAG)
OUTQ ( *USRPRF
name )
Program
User Profile
Output to
Printer
Default
Output Queue
OUTQ ( *WRKSTN
name )
File
Device Description
Printer
File OUTQ ( *DEV
name )

SPOOL(*YES) PRTDEV
( *SYSVAL
name )
OUTQ
( *JOB
name ) System Value

QPRTDEV ( PRT01
name )

Figure 2-29. Which Output Queue? OL197.0

Notes:
As each job starts, work management checks the objects (job description, user profile, then
workstation device description) and system value (QPRTDEV) in the order shown on the
visual determine whether a valid output queue name or printer device is defined. Once a
valid output queue or printer device is encountered, the search ends.
If the job description, user profile and workstation device description all contain default
entries for the output queue and printer device, the printer name in the QPRTDEV system
value will be used. By default, this system value contains the name of the first printer
configured on the system (usually PRTO1).

2-34 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Creating Device Descriptions

Automatic - QAUTOCFG = '1'

Local workstation controllers
Local tape drives
Local diskette drives
Local printers
Local display station
Local area network

Manual
Remote devices
Communications

Figure 2-30. Creating Device Descriptions OL197.0

Notes:
Communicating with the iSeries requires the use of configuration objects which usually
include:
Line descriptions - Line descriptions define the physical interface between the local
system and the remote system, controller, or network and the protocol used for
communications. Line descriptions can also include information about the line speed,
whether the line is switched or nonswitched, and the network address or telephone number
of the local system.
Controller descriptions - The controller description describes the characteristics of the
remote system, controller, or network that is to communicate with the local system.
Controller descriptions can describe an actual physical controller or logically represent the
connection to another system or network.
Device descriptions - The device description describes the characteristics of the physical
or logical device that is to communicate with the local system. Device descriptions can
describe a physical device or logically represent a communications session or a program
running on another system.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

These descriptions can be configured either automatically or manually through the use of
CL commands.
To automatically configure your local controllers and devices, use the system value
QAUTOCFG. If you do not change the system value QAUTOCFG (or ’automatic
configuration’) yes, the system continues to automatically configure any local controllers
and devices you attach. This includes any new local workstation controllers and tape
controllers, and any new twinaxial display stations, twinaxial printers, tape units, diskette
units, optical units, and media library devices.
Also, the system automatically assigns names to all your local devices. Depending on what
you selected on the Device configuration naming option on the Set Major Options display,
the system either uses one of the following: a normal naming convention, the System/36
style naming convention, or the naming convention that is based on the device address.
The Device configuration naming option allows you to change the system value
QDEVNAMING, which controls automatic configuration names for your devices.

2-36 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Automatic Configuration Naming Conventions

Device *Normal *S/36 *DEVADR

Workstation Controller CTL01 CTL01 CTL01

Display Stations DSP01, DSP02 W1, W2 DSP(CPA)*

Printers PRT01, PRT02 P1, P2 PRT(CPA)*

Diskette Drive DKT01 I1

Tape Drive TAP01 T1

SYSTEM VALUE: QDEVNAMING

* C=Controller P=Port A=Device Address

Figure 2-31. Automatic Configuration Naming Conventions OL197.0

Notes:
Automatic configuration uses one of three methods for naming your local controllers and
devices. The graphic above shows the normal naming convention (*NORMAL), the
System/36 style naming convention (*S36), and the naming convention that is based on
the device address (*DEVADR).
If you decide to manually configure the local devices, you should be aware of the
PRTDEVADR command.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

PRTDEVADR (CTL01)

Figure 2-32. PRTDEVADR (CTL01) OL197.0

Notes:
The Print Device Addresses (PRTDEVADR) command provides a printed list of addresses
and related information for devices attached to a local or remote work station controller. For
each device attached to the work station controller named in the controller description
(CTLD parameter), the output shows the name of the device, its port and switch setting, its
type and model number and shared session number.
Example
PRTDEVADR CTLD(CTL01)
This command prints device address information for the devices that are attached to the
CTL01 work station controller. This information is necessary when manually creating locally
attached device descriptions to preclude using duplicate addresses.

2-38 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Additional Objects Required for Remotes

Remote
Workstation *CTL
Controller CRTCTLRWS
Line
iSeries
*DEV
Display
*LIN CRTDEVDSP

CRTLIN x x x

*DEV
Printer CRTDEVPRT

Figure 2-33. Additional Objects Required for Remotes OL197.0

Notes:
There are a number of commands you can use to create the additional objects required for
remote devices. The graphic above shows some of these commands.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

How the Pieces Fit Together (1 of 3)

MSG
Device
Description
Device
Description
Aut Keyword
Aut Keyword

MSG
User Profile
*WRKSTN
OUTQ *DEV
name

Figure 2-34. How the Pieces Fit Together (1 of 3) OL197.0

Notes:
A device description is software that identifies a piece of hardware to the system. A User
profile is software that identifies a user to the system. Device configuration for local devices
may be created automatically by the system but user profiles must be created by a User
with *SECADM special authority.

2-40 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
How the Pieces Fit Together (2 of 3)

User Profile
.

current library
.

initial program
.

initial menu
.

authorizations
special
user class
password

Figure 2-35. How the Pieces Fit Together (2 of 3) OL197.0

Notes:
The User profile controls much of what a user can do on the system. This will be discussed
during the Security unit.

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

How the Pieces Fit Together (3 of 3)

Job Description JOBQ

.

. batch jobs
job queue awaiting execution
.

output queue
.

.
Main Storage
library list
.

.
MSGQ OUTQ
messages output
awaiting view awaiting print

User Workstation

Figure 2-36. How the Pieces Fit Together (3 of 3) OL197.0

Notes:
The general properties of a job determine how the system runs each job. Some of the
properties are grouped together in the Job Description for easier multiple job management.
The system knows what properties to get and when, based on how the job properties are
specified.

2-42 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
V2.0.0.3
Student Notebook

Uempty
Lab Exercise

LAB EXERCISE

Figure 2-37. Lab Exercise OL197.0

Notes:

© Copyright IBM Corp. 1995, 2003 Unit 2. iSeries Overview and Concepts 2-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook

Unit Summary
Having completed this unit, you should be able to:
Describe iSeries system architecture
Describe iSeries system objects
Explain syntax of iSeries commands
Explain concepts of libraries, library list and jobs
Explain concepts of printing on iSeries
Explain device description and creation

Figure 2-38. Unit Summary OL197.0

Notes:
The material presented in this unit reviewed some of the more basic concepts you learned
from on-the-job experience or through the iSeries System Operators Course. A good
understanding of these concepts is necessary to complete the remainder of the course
material.

2-44 iSeries System Administration and Control © Copyright IBM Corp. 1995, 2003
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.