Workflow Management for Operators
Operators can alter how JES3 processes jobs, but they might not get explicit JES3 messages or instructions from programmers for some situations. Messages generally indicate that a problem or potential problem was recognized by JES3. System programmers might know overall job mix, but might not see day-to-day job mixes that affect intermittently system efficiency.
With JES3, operators have ways of searching for potential workflow
problems. They can use commands to learn:
- What jobs JES3 has read, but has not begun processing
- What resources are required for a job
- What jobs JES3 has processed and has scheduled for processing
- What jobs are processing on each processor
- Job names, job numbers, job priorities, region sizes, whether jobs are being held up, and what JES3 routines have yet to process jobs
- How much output data is ready for printing or punching
- Determine why a job is not being scheduled for processing
Operators can then use JES3 commands to:
- Suspend further processing of jobs.
- Change the attributes of a job.
- Cancel jobs.
- Resume processing of suspended jobs.
- Limit the number of jobs in execution.
- Change (dynamically) how JES3 is to process and manage the job workload.