Work Management

Presented By

Mohammad Sohel Parvez

Senior Principal Officer
IT Division, Head Office
IFIC Bank Ltd.
JOB
 JOB Life Cycle

1. When a job is submitted to iSeries:

► it is created and enters the system.

►At this time, the properties are given to the job.
►Once the job receives its job description and determines its properties,
it moves to the job queue, where it waits to enter the subsystem.
 JOB Life Cycle

2. Job queues are work entry points through which batch jobs enter the
system. They can be thought of as waiting rooms for a subsystem. A
number of factors affect when the job is pulled off the job queue into
the subsystem:
► such as the job priority on the job queue,
►the sequence number of the job queue,
► the maximum number of active jobs.

When all of these factors work together, the job will be pulled off the job
queue to start running in the subsystem.
 JOB Life Cycle

3. When the job enters the subsystem it becomes active. Until a job gets
its activity level and memory from a memory pool, it cannot run. The job
uses several pieces of information before it can receive memory to run.
The subsystem description like the job description, carries information,
such as which memory pool to use, the routing entry, the maximum
number of active jobs, and the number of active jobs currently in the
subsystem.
 JOB Life Cycle

4. Memory is a resource from the memory pool that the subsystem uses
to run the job. The amount of memory from a memory pool, as well as
how many other jobs are competing for memory, affects how efficiently a
job runs. Subsystems use different memory pools to support different
types of jobs that run within them. The subsystem gives the memory pool
the information it needs to process the order in which jobs are allocated
memory, and the memory pool allocates memory for the job to run to
completion.
 JOB Life Cycle

5. A printer output for a job (also called spooled files) is sent to an output
queue where it waits to be sent to a printer or file. The output queue is
similar to the job queue in that it controls how the output is made
available to the printer. The output queue allows the user to control what
files are printed first.
JOB Types
JOB’s Duration
JOB Processing Method
Interactive and batch jobs
1. A user signs on to a display station.

2. The i5/OS operating system runs the job and can generate
printed output that is placed in a spooled file and put on an
output queue. An output queue contains reports waiting to
print.
3. This job waits on the output queue until prior jobs are
printed.

4. The spooled output file is printed.

5. The user either signs off the system, which ends the
interactive job, or stays signed on, in which case the job keeps
running.
Interactive and batch jobs
1. A batch job can be initiated via the Submit Job (SBMJOB)
command. Client-side requests, such as those submitted via
iSeries Navigator, are also handled as batch jobs.

2. A batch job is submitted to a job queue. The i5/OS operating

system places the jobs on the job queue in the order in which
they were received.

3. The job waits on the job queue until the subsystem that is
monitoring the job queue has the resources needed to run the
job.

4. Then, the job runs and generates printed output that is

placed in a spooled file and put on an output queue. The output
queue is similar to the job queue, containing printed output
waiting its turn to print.

5. The spooled output can then be printed.

 JOB Name

Each job has a system-unique identifier, called a qualified job name, that
consists of three parts (or qualifiers):

❶ A unique six-digit job number assigned by the system

❷ A user name, that is the user ID under which the job was started
❸ A job name set by the user for submitted jobs or assigned as the name of
the device used to connect for interactive login jobs
 JOB Description

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.
JOB Description Attributes
● Run-time attributes
● Job description name
● Job Date
● Format User ID
● Job queue
● Job queue priority
● Job queue status
● Output queue
● Print device
● Output queue priority
● Routing data
● Accounting code
● Message logging level
 JOB – User Profile Relation

Every job run within the i5/OS operating system is associated with a
specific user. A user’s profile contains a great deal of information about
the user and which types of jobs he or she can run.
 JOB – WRKJOBD
Work with Job Descriptions

Type options, press Enter.

1=Create 2=Change 3=Copy 4=Delete 5=Display

Job
Opt Description Library Text

_ QAMTJOBD QSYS Job description to allow multiple threads.

_ QCTL QSYS Controlling Subsystem Job Description
_ QDIRJOBD QSYS Job description for Directory Services
_ QESAUTON QSYS Job Description for Automatic Problem Notificati
_ QFSIOPWK QSYS File Sever I/O Processor job description
_ QIMGJOBD QSYS PostScript interpreter job description
_ QIZAJOBD QSYS UPGRADE ASSISTANT FOR OS/400 JOBD
_ QIZAJOBR QSYS UPGRADE ASSISTANT FOR OS/400 JOBD
_ QJSCCPY QSYS COPY SCREEN
_ QLPINSTALL QSYS Job description for LP Install
More...
Parameters for options 1, 2, 3 and 5 or command
===>_________________________________________________________________________
F3=Exit F4=Prompt F5=Refresh F9=Retrieve F11=Display names only
F12=Cancel F16=Repeat position to F17=Position to F24=More keys
Job Queue
 Job Queues - Batch Only

• Holding place for jobs.

• Job queue ordered by priority.
• Jobs with same priority execute first-in-
first-out (FIFO).
 Create Job Queue - CRTJOBQ
Create Job Queue (CRTJOBQ)

Type choices, press Enter.

Job queue . . . . . . . . . . . _________ Name

Library . . . . . . . . . . . *CURLIB Name, *CURLIB
Text 'description' . . . . . . . *BLANK
WRKJOBQ
Jobs on JOBQ
Scheduling Jobs
User Jobs
 Work With Active Jobs
Work with Active Jobs BIGBLUE
07/03/99 17:47:11
CPU %: .0 Elapsed time: 00:00:00 Active jobs: 112

Type options, press Enter.

2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...

Opt Subsystem/Job User Type CPU % Function Status

_ QBASE QSYS SBS .0 DEQW
_ QBATCH QSYS SBS .0 DEQW
_ QCMN QSYS SBS .0 DEQW
_ QCTL QSYS SBS .0 DEQW
_ QSYSSCD QPGMR BCH .0 PGM-QEZSCNEP EVTW
_ QINTER QSYS SBS .0 DEQW
_ QPADEV0004 DAWSON#M INT .0 CMD-WRKACTJOB RUN
_ QPGMR QSYS SBS .0 DEQW
_ QSERVER QSYS SBS .0 DEQW
More...
Parameters or command
===>_________________________________________________________________
F3=Exit F5=Refresh F7=Find F10=Restart statistics
F11=Display elapsed data F12=Cancel F23=More options F24=More keys
DSPJOBLOG
Job, Queues and Subsystem
SBMJOB <job name>

JOBQA JOBQB JOBQC

JOB7
.empty.
JOB5 JOB6

Subsystem QBATCH
MAXACTJOB = 3
Currently running:
JOB1, JOB2, JOB3
Jobs, Queues, and Printer Writers
Jobs, Queues, and Printer Writers
 Subsystem

A subsystem is a single, predefined operating environment through

which the system coordinates the work flow and system resources. Each
job, as it starts, is assigned to a subsystem.
 Subsystem
The subsystem description is an object that defines the environment that
the jobs that run in the subsystem need in order to run most efficiently.
 Subsystem Description Cmd
There are a number of commands used with the subsystem descriptions:

Change Subsystem Description - CHGSBSD

Create Subsystem Description - CRTSBSD
Delete Subsystem Description - DLTSBSD
Display Subsystem Description - DSPSBSD
Print Subsystem Description - PRTSBSDAUT
Work with Subsystem Description - WRKSBSD

The most useful is the WRKSBSD command because from this display you
can create, change, delete, display, or work with subsystem jobs, or you can
start or stop a subsystem.
Subsystem by IBM
 Subsystem by IBM
Subsystem Functions
QCTL QCTL is the controlling subsystem.
QINTER An interactive subsystem used to sign on to all display stations
except the system console.
QBATCH Use QBATCH to process batch jobs.
QSYSWRK runs certain system functions
QSPL Used for for spooling functions
QCMN Runs communication functions
 Subsystem by IBM
Work with Subsystems
System: IFICTSDV
Type options, press Enter.
4=End subsystem 5=Display subsystem description
8=Work with subsystem jobs

Total -----------Subsystem Pools------------

Opt Subsystem Storage (M) 1 2 3 4 5 6 7 8 9 10
ATMLIVE .00 2
FIRCOBATCH .00 2
QBATCH .00 2
QCMN .00 2
QCTL .00 2
QHTTPSVR .00 2
QINTER .00 2 3
QMQM .00 2
QSERVER .00 2
QSPL .00 2 4
QSYSWRK .00 2
QUSRWRK .00 2
Q1ABRMNET .00 2
REPEQNLIV .00 2 3

Bottom
Parameters or command
===>
F3=Exit F5=Refresh F11=Display system data F12=Cancel
F14=Work with system status