iwsz job submission order best practices

IBM Systems

© 2015 IBM Corporation

IBM zMiddlewareIT Service Management

IWSz Job Submission orderBest Practices

Domenico ChillemiIBM Executive IT [email protected]

IBM Systems


zMiddleware IT Service Management

What to submit first

Time constraints and dependencies in the plan of course

BUT

Under the same «ready» conditions?

– Very important to determine the right submission order

– Priority is not enough

Resources availability is a key factor!

– Internal IWSz special resources, tapes and parallel servers

– External resources determined by integrations

• WLM, Omegamon, System Automation, etc...

Events can affect job submission order

2

IBM Systems



Ready list urgency

List of operations ready to be started

– Computer & Non Reporting Workstations

– Status is the same for all operations in the list

– No time and dependencirs constraints

IWSz checks the most urgent operation

– Based on several criteria

Comparison done inside same conditions operations

IWSz estabilishes an order checking all definitions plus

internal and external rules

3

IBM Systems



IWSz ordering criteria

When there are time dependent operations and

dependencies, ordering criteria are not needed

Under the same «ready» conditions, IWSz determines

order through the following criteria in cascade

1. Operations with an urgent flag set on

• Priority 9 defined for the operation

• Missed deadline for the operation

2. Latest start time

• Calculated by IWSz while current plan is being created

3. Operation priority less than 9

4. Shortest estimated duration

• Refer to smooting factor and feedback limit for automatic calculation

4

IBM Systems



When an operation can start

Even if previous criteria are performed

– Resources must be available

• Internally defined

• Externally determined (for example Waiting for Scheduling Environment)

– Extended status

• Set against a resource unavailability

• Identifies which type of resource the operation is waiting for

Events can affect the criteria

– A locked operation can join the ready list when an event unlocks

conditions preventing its submission

5

IBM Systems



Manual interventions Manual interventions can affect the ordering criteria

Possible affecting actions

– MH action

• Hold status manually set locks the operations even if belonging to the ready

list, and can be unblocked not necessarily by hand

– MR action

• Release status manually set makes IWS recalculate the ready list and reapply

ordering criteria

– EX status

• Forcing execute manually immediately includes the related operation in the

ready list, prioritizing its submission

– Dynamic current plan and JCL changes

• Dependency change, time dependent flag change, etc...

• JCL changes in the JS can count, for example forcing a JCL error

6

IBM Systems



Noping and un-noping operations

Any operation can be nullified in IWSz

– NP in IWSz panels nullifies the operation

• The operation remains nullified until it will be ready to start

• When it is ready to start, it is placed in the ready list and follows order criteria

• When IWS decides to start it effectively, it behaves as a non reporting

operation and automatically completes

– //*OPC NOP in the JCL nullifies the operation as well

At any time, if a nullified operation is not started yet

– It can be un-noped

• Using IWSz panels

• Deleting the //*OPC NOP jobcard in the JCL

7

IBM Systems



8

Thank You

iwsz job submission order best practices

Technology