Power Systems

What is Work Management?

Module 5 © Copyright IBM Corporation 2008 1

 Power Systems
More User
Single User Enviroment Multi User Enviroment

Application Application

OS OS

...

Performance? Security? Availability?

Module 5 © Copyright IBM Corporation 2008 2

 Power Systems
More Applications

App 1 App 2 ... App N App 1 App2 ... App N

OS 1 OS 2 OS N OS

... ...

Performance? Security? Availability?

Maintenance?

Module 5 © Copyright IBM Corporation 2008 3

 Power Systems
Reality is more complex!
Performance? Security? Availability?
Maintenance?

...

Module 5 © Copyright IBM Corporation 2008 4

 Power Systems
Work Management
Running Multiple Applications in a single OS Instance

Performance
App 1 App2 ... App N (or how to share ressources)

OS Security Lecture 4

Availability

Do not
... confuse
work management
and
LPAR!

Module 5 © Copyright IBM Corporation 2008 5

 Power Systems

Process Scheduling

Module 5 © Copyright IBM Corporation 2008 6

 Power Systems
Introduction to Scheduling

• Bursts of CPU usage alternate with periods of I/O wait

– a CPU-bound process
– an I/O bound process Scheduling? Time slice?
Memory management?
Source: Andrew S. Tanenbaum: Modern Operating Systems 2th Edition

Module 5 © Copyright IBM Corporation 2008 7

 Power Systems
Scheduling Algorithm Goals

Source: Andrew S. Tanenbaum: Modern Operating Systems 2th Edition

Module 5 © Copyright IBM Corporation 2008 8

 Power Systems
Diagram of Process State

• As a process executes, it changes state

– new: The process is being created
– running: Instructions are being executed
– waiting: The process is waiting for some event to occur
– ready: The process is waiting to be assigned to a processor
– terminated: The process has finished execution

Source: Silberschatz, Galvin and Gagne: Operating System Concepts - 7th Edition

Module 5 © Copyright IBM Corporation 2008 9

 Power Systems
Preemptive and Non-preemptive
Scheduling
•CPU scheduling decicions may take place, if a process
(1) switches from running to waiting state
(2) switches from running to ready state
(3) switches from waiting to ready state
(4) terminates

•When scheduling take place only under (1) or (4) the

scheduling scheme is non-preemptive or preemptive.
• Examples:
 non-preemptive: Windows 3.1
 preemptive: Windows 95 or later, Mac OS X

Source: Andrew S. Tanenbaum: Modern Operating Systems 2th Edition

Module 5 © Copyright IBM Corporation 2008 10

 Power Systems
Context Switch

• When CPU switches to another process, the system

must save the state of the old process and load the
saved state for the new process
• Context-switch time is overhead; the system does no
useful work while switching
• Time dependent on hardware support

Source: Silberschatz, Galvin and Gagne: Operating System Concepts - 7th Edition

Module 5 © Copyright IBM Corporation 2008 11

 Power Systems
Process Control Block (PCB)

•Information associated with each

process:
 Process state
 Program counter
 CPU registers
 CPU scheduling information
 Memory-management information
 Accounting information
 I/O status information

Source: Silberschatz, Galvin and Gagne: Operating System Concepts - 7th Edition

Module 5 © Copyright IBM Corporation 2008 12

 Power Systems
Single Process Execution
 CPU–I/O Burst Cycle –
Process execution
consists of a cycle of
CPU execution and I/O
wait

 CPU burst distribution

Source: Silberschatz, Galvin and Gagne: Operating System Concepts - 7th Edition

Module 5 © Copyright IBM Corporation 2008 13

 Power Systems

CPU Switch From Process to Process

Source: Silberschatz, Galvin and Gagne: Operating System Concepts - 7th Edition Efficient process scheduling?
Module 5 © Copyright IBM Corporation 2008 14
 Power Systems
Scheduling Criteria

• CPU utilization – keep the CPU as busy as possible

• Throughput – # of processes that complete their
execution per time unit
• Turnaround time – amount of time to execute a
particular process
• Waiting time – amount of time a process has been
waiting in the ready queue
• Response time – amount of time it takes from when a
request was submitted until the first response is
produced, not output (for time-sharing environment)

Source: Silberschatz, Galvin and Gagne: Operating System Concepts - 7th Edition

Module 5 © Copyright IBM Corporation 2008 15

 Power Systems

Scheduling in Interactive Systems

A scheduling algorithm with four priority classes

Source: Andrew S. Tanenbaum: Modern Operating Systems 2th Edition

Module 5 © Copyright IBM Corporation 2008 16

 Power Systems

Scheduling in Batch Systems

Three level scheduling

Source: Andrew S. Tanenbaum: Modern Operating Systems 2th Edition

Module 5 © Copyright IBM Corporation 2008 17

 Power Systems

Example: IBM i

aka i5/OS, OS/400

Module 5 © Copyright IBM Corporation 2008 18

 Power Systems

5.1 Operator‘s View

Module 5 © Copyright IBM Corporation 2008 19

 Power Systems

Job

Qualified job name

000578 AS24xx DSP01

J o b  num b e r Us e r  nam e J o b  nam e

Module 5 © Copyright IBM Corporation 2008 20

 Power Systems

Job Types
System jobs

Q...
S po o ling User jobs

I nt e r ac t ive

A ut o s t ar t

Bat c h

Co m m unic at io n

Module 5 © Copyright IBM Corporation 2008 21

 Power Systems
Job Properties

Module 5 © Copyright IBM Corporation 2008 22

 Power Systems

The Life Cycle of a Job

Submit Job queue Subsystem Memory pool Output

Module 5 © Copyright IBM Corporation 2008 23

 Power Systems

Work Management Objects

SYSTEM NETWORK
OS/400 VALUES ATTRIBUTES

SUBSYSTEM SBSD

JOB WORK JOBD

THREAD ENTRIES

ROUTING CLASS
ENTRIES

POOLS PROGRAM

Module 5 © Copyright IBM Corporation 2008 24

 Power Systems

System Values

Module 5 © Copyright IBM Corporation 2008 25

 Power Systems
Network Attribute
Current System Name ABC

Local Network ID APPN

APPN Node type *ENDNODE

Alert Status *OFF

Alert Primary Focal Point *NO

Message Queue/Obj. Dist. QSYS/QSYSOPR

Output Queue/Obj. Dist. QGPL/QPRINT

Action for DDM Request *OBJAUT

PC Support Request Access *OBJAUT

Module 5 © Copyright IBM Corporation 2008 26

 Power Systems
Job Queue
Job queue priority
Job queue 1 JOB2 HIGH
JOB5
JOB1 (2)
2 JOB1
JOB2 (1) JOB4
JOB3 (4)
3
JOB4 (2)
JOB5 (1)
JOB6 (4) 4 JOB3
JOB6
.
.
.
LOW
Module 5 © Copyright IBM Corporation 2008 27
 Power Systems
Job Description
Display Job Description
System: HYDRA
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...
Press Enter to continue.

F3=Exit F12=Cancel

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

Module 5 © Copyright IBM Corporation 2008 28

 Power Systems
User Profile
Display User Profile - Basic

User profile . . . . . . . . . . . . . . . : AS2401

Storage information:
Maximum storage allowed . . . . . . . . : *NOMAX
Storage used . . . . . . . . . . . . . . : 312
Storage used on independent ASP . . . . : *NO
Highest scheduling priority . . . . . . . : 3
Job description . . . . . . . . . . . . . : QDFTJOBD
Library . . . . . . . . . . . . . . . . : QGPL
Accounting code . . . . . . . . . . . . . :
Message queue . . . . . . . . . . . . . . : AS2401
Library . . . . . . . . . . . . . . . . : QUSRSYS
Message queue delivery . . . . . . . . . . : *NOTIFY
Message queue severity . . . . . . . . . . : 00
Output queue . . . . . . . . . . . . . . . : AS24OUTQ
Library . . . . . . . . . . . . . . . . : AS2401
Printer device . . . . . . . . . . . . . . : *WRKSTN
More...
Press Enter to continue.

F3=Exit F12=Cancel

Module 5 © Copyright IBM Corporation 2008 29

 Power Systems
Job Processing
SBMJOB

Job Subsystem Output WRITER

queue pool queue
Batch
Sign-on PRINTER
Interactive

WRKJOBQ WRKACTJOB WRKOUTQ WRKWTR

WRKSPLF

WRKUSRJOB
WRKSBMJOB

Module 5 © Copyright IBM Corporation 2008 30

 Power Systems
Subsystems
A specialized environment for handling a certain type
of work or function, such as:

INTERACTIVE

BATCH SPOOLING

COMMUNICATIONS

Module 5 © Copyright IBM Corporation 2008 31

 Power Systems

Storage Pools

• Logical Areas of Main Storage for Jobs:

– POOL SIZE sets amounts of storage *SPOOL POOL (4)

– Noncontiguous pages *INTERACT POOL (3)

– Deallocated when set to *NOSTG (No
storage) *BASE POOL (2)

– PAGING is restricted to pool

– ACTIVITY LEVEL determines how many job
threads may have main storage *MACHINE POOL (1)
– Two types of pools: SHARED AND
PRIVATE

Module 5 © Copyright IBM Corporation 2008 32

 Power Systems
Subsystem Description (1/4)
Display Subsystem Description
Subsystem description: QINTER System: ABC
Status: ACTIVE Library: QSYS

Select one of the following:

1. Operational attributes
2. Pool definitions
Operational Attributes
3. Autostart job entries
4. Work station name entries
Maximum jobs in subsystem *NOMAX
5. Work station type entries
6. Job queue entries Sign-on display file QSYS/QDSIGNON
7. Routing entries
8. Communications entries
9. Remote location name entries Pool Definitions
10. Prestart job entries
Pool Storage
30. All of the above ID Size (KB)

1 *BASE
Selection or command
==>____________________________________________________________________
2 *INTERACT

Module 5 © Copyright IBM Corporation 2008 33

 Power Systems

Subsystem Description (2/4)

Display Subsystem Description
Subsystem description: QINTER System: ABC
Status: ACTIVE Library: QSYS

Select one of the following:

1. Operational attributes
WORKSTATION Entries
2. Pool definitions
3. Autostart job entries Type Jobd Name Jobd
4. Work station name entries
*ALL *USRPRF DSP03 *USRPRF
5. Work station type entries
6. Job queue entries
7. Routing entries Job Queue Entries PRESTART Job Entries

8. Communications entries Jobq Prog Jobd

9. Remote location name entries
10. Prestart job entries QBATCH PROG01 JOBDAPPC

30. All of the above AUTOSTART Job Entries Communication Entries

Job Jobd Dev Jobd

Selection or command
==>____________________________________________________________________
START STARTJD *ALL *USRPRF

Module 5 © Copyright IBM Corporation 2008 34

 Power Systems
Subsystem Description (3/4)
Display Subsystem Description
Subsystem description: QINTER System: ABC
Status: ACTIVE Library: QSYS

Select one of the following: Routing Entries

1. Operational attributes
2. Pool definitions SEQNBR CMPVAL CLASS PGM POOL ID
3. Autostart job entries
4. Work station name entries 10 QCMDB QBATCH QCMD 1
5. Work station type entries
6. Job queue entries 50 QCMDI QINTER QCMD 2
7. Routing entries
8. Communications entries 9999 *ANY QBATCH QCMD 1
9. Remote location name entries
10. Prestart job entries
Class Information
30. All of the above QBATCH QINTER

Run Priority 50 20
Selection or command
==>____________________________________________________________________
Time Slice 5000 ms 2000 ms

Purge *NO *YES

Wait Time 120 sec 30 sec

Module 5 © Copyright IBM Corporation 2008 35

 Power Systems

Subsystem Description (4/4)

Display Subsystem Description
Subsystem description: QINTER System: ABC
Status: ACTIVE Library: QSYS

Select one of the following:

1. Operational attributes Job queue entries in subsystem description
2. Pool definitions
JOBQ JOBQA JOBQB JOBQC
3. Autostart job entries
SEQNBR 1O 20 30
4. Work station name entries MAXACT *NOMAX 1 1
5. Work station type entries MAXPTY1 *NOMAX *NOMAX *NOMAX
6. Job queue entries . : : :
7. Routing entries MAXPTY9 : :

8. Communications entries
JOB 2 JOB 4 JOB 5
9. Remote location name entries JOB 1 JOB 3
10. Prestart job entries

Jobs 1 to 5 have equal priority.

30. All of the above
Which jobs run concurrently if the subsystem description has:

?
Selection or command MAXJOBS = 2
MAXJOBS = 3
==>____________________________________________________________________
MAXJOBS = 4
MAXJOBS = *NOMAX

Module 5 © Copyright IBM Corporation 2008 36

 Power Systems
Batch Job Routing
SBMJOB CMD(CALL PRPROC) RTGDTA(QCMDB) JOB(PAY) JOBQ(QBATCH)

SUBSYSTEM QBATCH
MONITOR Subsystem Description
PAY JOBQ
PROGRAM Max Jobs - *NOMAX QBATCH
Job Queue Entry
Job Queue Max Act Max Pty(n)
QBATCH 1 *NOMAX

Routing Entry
SEQNBR CMPVAL PGM CLASS POOL
9999 *ANY QCMD QBATCH 1
CLASS
QGPL/QBATCH
Run Priority
CALL PRPROC

QSYS/QCMD
*BASE JOB MSGQ
PAY
PRPROC

Module 5 © Copyright IBM Corporation 2008 37

 Power Systems
Interactive Job Routing
QINTER
Subsystem Description
Attributes
Storage Pools MAXJOBS(*NOMAX)
Job Description
ID Storage USERLIB/USERJOBD
1 *BASE Sign-on Display File
2 *INTERACT (QSYS/QDSIGNON) User Name
Job Queue
Work Station Entry Job Priority
User Work Station Job Description Output Priority
Password LWS1 *USRPRF Routing Data (QCMDI)
Request Data
Routing Entry
Initial Library List
SEQNBR CMPVAL PGM Class Pool More . . . .
50 QCMDI QCMD QINTER 2
CLASS
User Profile = XYZ QSYS/QCMD QGPL/QINTER

PASSWORD = XXXXXX USERPGM Run

INLPGM = USERLIB/USERPGM Priority
JOBD = USERLIB/USERJOBD *INTERACT

Module 5 © Copyright IBM Corporation 2008 38

 Power Systems
Operator‘s View
Main Storage
7
CLASS PROFILE
Priority Initial Program
PROG1

6 Job Description

4 QCMD
5 1

SBS
SBSD
3 Monitor JOBD
2
Job
Routing Description
OS/400
Routing

Module 5 © Copyright IBM Corporation 2008 39

 Power Systems

5.2 System’s View

Job Structure and Task Dispatching

Module 5 © Copyright IBM Corporation 2008 40

 Power Systems
Three-level Hierachy of Work
• Process
– MI System object called process-control space (PCS)
– Tie together the resources for program invocation
– Consists of
• A executable program (can be shared)
• Program‘s data
• State informations
– Could also be defined as a program in execution
• Job
– OS/400 object that contains a process structure to manage system
resources
• Thread
– A portion of a process
– A process may have more than one thread
– Each thread consists of
• Set of registers representing the state of the processor
• A control stack
• Automatic program storage (local variables)
– System resources allocated to the process are shared with other
threads within the process

Module 5 © Copyright IBM Corporation 2008 41

 Power Systems
Permanent Job Structure Objects
WCBT
JOBMSGQ JOB on JOBQ
Job JOBMSGQ
Message Job
WCBTE Queue Message
JOBMSGQ JOB active in
Queue Subsystem
SCB
SCB
JOBQ
LDA Spool SCB
Control Spool
Block Control
Block
LDA
WCBTE Local LDA
JOBMSGQ Data Local
SCB Area Data
SBSD Area
LDA
PCS
PCS
Process
Control
Space
WCBT – Work Control Block Table
WCBTE – Work Control block Table Entry

Module 5 © Copyright IBM Corporation 2008 42

 Power Systems
Temporary Job Structure Objects
WCBT Process Access Group
Control Field File

Process Static Storage A B

Control ___ ___
Space O O
___ ___
D D
___ ___
Thread ___ ___ P P
Control
Space
(for initial
thread)

SCB LDA
JOBMSGQ

QTEMP TDE

Thread Control Space

(for secondary thread) TDE

Thread Control Space

(for secondary thread) TDE
ODP – Open Data Path
TDE – Task Dispatching Element

Module 5 © Copyright IBM Corporation 2008 43

 Power Systems
Open Data Path (ODP)

Control Field File

X A
O
D
P
UFCB

Create
Duplicate
Job X

O
#1 D
Open A P

UFCB – User Field Control Block

Module 5 © Copyright IBM Corporation 2008 44

 Power Systems
Open Data Path Sharing
Control Field File
X Static Storage A A
___ ___ O O
___ ___
SHARE(*NO) D D
___ ___
___ ___ P P

Pgm #1
Open file A
Job X Call Pgm #2 Job Y
Call Pgm #2
Open file A
Return

Y Static Storage A
___ ___ O
SHARE(*YES) ___ ___
D
___ ___
___ ___ P

Control Field File

Module 5 © Copyright IBM Corporation 2008 45

 Power Systems
Thread-control Space (TCS)
• are temporary SLIC objects
• will be recycled at process level or at systems level
when process ends
Storage vector table
Segment header

Stack control block

Nonresident lightweight MI automatic storage

Process control block (system state)

Event monitors

MI automatic storage
(user state)
Stack frames

Source: Frank G. Soltis, Fortress Rochester, Fig. 13.5

Module 5 © Copyright IBM Corporation 2008 46

 Power Systems
Task Dispatching Queues

TDQ description Pointer

Highest

TDE description Pointer Priority

TDE description Pointer Priority

Priority
TDE description Pointer Priority

TDE description Pointer Priority

Lowest
Module 5 © Copyright IBM Corporation 2008 47
 Power Systems

Send/Receive Queues

• Data structure used as “mailbox” for tasks

• SEND MESSAGE enqueued a SRM
• Execute a RECEIVE MESSAGE operations to
obtain a message (dequeing)
● If no message is available the task has to wait

SRQ SRM CHAIN TDE CHAIN

SRM KEY1 SRM CHAIN MSG

PRIORITY TDE CHAIN STATUS TDE

SRM KEY2 SRM CHAIN MSG

SRQ – Send/Receive Queue

SRM – Send/Receive Message
RECM – Recieve Message
SENDM – Send Message

Module 5 © Copyright IBM Corporation 2008 48

 Power Systems
RECM
TDQ TDE CHAIN Instruction Stream

TDE PRIORITY TDE CHAIN STATUS RECM OP 1 OP2

TDE PRIORITY TDE CHAIN STATUS

KEY

SRQ SRM CHAIN TDE CHAIN

SRM KEY1 SRM CHAIN MSG

PRIORITY TDE CHAIN STATUS TDE

SRM KEY2 SRM CHAIN MSG

PRIORITY TDE CHAIN STATUS TDE

Key Comparison

Module 5 © Copyright IBM Corporation 2008 49

 Power Systems
If RECM Is Unsatisfied
TDQ TDE CHAIN Instruction Stream

INSTR

TDE PRIORITY TDE CHAIN STATUS

SRQ SRM CHAIN TDE CHAIN

SRM KEY1 SRM CHAIN MSG

PRIORITY TDE CHAIN STATUS TDE

SRM KEY2 SRM CHAIN MSG

PRIORITY TDE CHAIN STATUS TDE

PRIORITY TDE CHAIN STATUS TDE

Module 5 © Copyright IBM Corporation 2008 50

 Power Systems
SENDM (1/2)
TDQ TDE CHAIN Instruction Stream

TDE PRIORITY TDE CHAIN STATUS SENDM I OP 1

TDE PRIORITY TDE CHAIN STATUS

SRM KEY2 SRM CHAIN MSG

SRQ SRM CHAIN TDE CHAIN

SRM KEY1 SRM CHAIN MSG

PRIORITY TDE CHAIN STATUS TDE

PRIORITY TDE CHAIN STATUS TDE

Module 5 © Copyright IBM Corporation 2008 51

 Power Systems
SENDM (2/2)
TDQ TDE CHAIN Instruction Stream

TDE PRIORITY TDE CHAIN STATUS INSTR

TDE PRIORITY TDE CHAIN STATUS

TDE PRIORITY TDE CHAIN STATUS Priority

TDE PRIORITY TDE CHAIN STATUS

SRQ SRM CHAIN TDE CHAIN

SRM KEY1 SRM CHAIN MSG

SRM KEY2 SRM CHAIN MSG

Module 5 © Copyright IBM Corporation 2008 52

 Power Systems
Task States

TDQ TDE CHAIN

TDE PRIORITY TDE CHAIN STATUS Active

TDE PRIORITY TDE CHAIN STATUS

TDE PRIORITY TDE CHAIN STATUS

Ready
TDE PRIORITY TDE CHAIN STATUS

Wait
SRQ SRM CHAIN TDE CHAIN

PRIORITY TDE CHAIN STATUS

SRM KEY1 SRM CHAIN MSG

PRIORITY TDE CHAIN STATUS

SRM KEY2 SRM CHAIN MSG

Module 5 © Copyright IBM Corporation 2008 53

 Power Systems
States of Tasks

1. Initiate task (start work) Ready (ineligible)

2. Run task (dispatch task)
3. Suspend task (work done)

2.
6. 1.

Wait Suspended

5. 4. 3.

1. Preempt task (by another task)

2. Wait(for I/O or another task)
Running (active)
3. Signal (task is done waiting)

Module 5 © Copyright IBM Corporation 2008 54

 Power Systems
Thread States and Transitions
Long NO W-I
Wait Ineligible
Act Level
State Open State
YES W-A I-A

A-A A-I
1 2 3 Other
Jobs
Active State Ineligible
Activity NO
Levels

A-W TSE
Prime
Task Send/
Dispatching Receive
Queue Queue

Module 5 © Copyright IBM Corporation 2008 55

 Power Systems

Observing Thread State Transitions

Work with System Status ABC
06/21/XX 10:11:12
% CPU used . . . . . . : 61.7 Auxiliary storage:
% DB capability . . . :
Elapsed time . . . . . : 00:06:30 System ASP . . . . . . . . . : 3258 M
Jobs in system . . . . : 494 % system ASP . . . . . . . . : 18.6657
% perm addresses . . . : Total . . . . . . . . . . . : 3258 M
% temp addresses . . . :
Permanent . . . . : 3.063 Current unprotect used . . . : 437 M
Temporary . . . . : 3.962 Maximum unprotect . . . . . .: 437 M

Type changes (if allowed), press Enter.

System Pool Reserved Max Active -->Wait --> Active -->

Pool Size (M) Size (M) Active Wait Inel Inel
1 3.61 2.26 +++ 7.5 .0 .0
2 3.97 0 10 .4 .0 .0
3 .23 0 3 .0 .0 .0
4 8.19 0 25 88.4 .0 .0

Bottom
Command
===>
4=Prompt F5=Refresh F9=Retrieve F10=Restart
F11=Display pool data F12=Cancel F14= Work with subsystems F24=More Keys

Module 5 © Copyright IBM Corporation 2008 56

 Power Systems
Active-to-Wait
Active-to-Wait
Long Act
Wait JOBA Level A-W
State Open?
Yes

1 2 3
Activity Active
Levels JOBA JOBB JOBC State
Prime
TDQ
JOBA
JOBB A-W
JOBC

PAG

Module 5 © Copyright IBM Corporation 2008 57

 Power Systems
Wait-to-Ineligible

NO
Long W-I
Act
Wait JOBA Level JOBA
State Open?

Ineligible
YES
State

1 2 3
Activity Active
Levels JOBD JOBB JOBC State

Module 5 © Copyright IBM Corporation 2008 58

 Power Systems
Wait in Activity Level
Long
Wait JOBA
State

1 2 3
Activity Active
JOBB JOBC
Levels State

Prime
TDQ

JOBB
JOBC Send/ Receive
Queue

Module 5 © Copyright IBM Corporation 2008 59

 Power Systems
Active-to-Ineligible

Ineligible JOBC
State

1 2 3
JOBB A-A A-I
Other
Jobs
Prime Ineligible?
TDQ
JOBA
JOBB TSE
JOBC

Module 5 © Copyright IBM Corporation 2008 60

 Power Systems
Dynamic Priority Scheduling

New algorithms on RISC systems

• No job can monopolize the CPU
– Jobs not using CPU have their DELAY COST
increased
• Low-priority jobs have a chance to progress
• iSeries server optimization for batch
• Interactive job priority lowered when batch
demand is high
Can be turned on/off
• QDYNPTYSCD and QDYNPTYADJ

Module 5 © Copyright IBM Corporation 2008 61

 Power Systems
Delay Cost Curves
Delay Cost
6
10-1 Priority 0-9
ri ties
Pri
o
s 1 7-22
ritie
Prio

ties 2 3-35
Pri o ri

3 6-46
Priorities

Priorities 47-51
Priorities 52-89
Priorities 90-99

Time (Millions of cycles)

Module 5 © Copyright IBM Corporation 2008 62

 Power Systems

Multi-Processor Considerations (1/2)

Dispatching the first n top TDEs on the TDQ?

Cache Affinity
STOP and
Performance?!

Module 5 © Copyright IBM Corporation 2008 63

 Power Systems

Multi-Processor Considerations (2/2)

Task Dispatching is based on priority, cache affinity

and eligibility

Three bits in a TDE

• Eligibility bit
– one bit for every processor
– indicates that a task is eligible to run on on corresponding processor
• Active field
– one bit for every processor
– indicates on which processor the task is currently running
• Affinity field
– one bit for every processor
– Indicates on which processor the task was currently running

Module 5 © Copyright IBM Corporation 2008 64