The daily edition.

Scope: Rocket Enterprise Developer 12.0 for Eclipse on Linux/UNIX; Enterprise Server JCL support.

A submitted JCL job does not run merely because it has entered the spool. Enterprise Server uses specialized service execution processes (SEPs), and the job’s class must match an available SEP:

• A batch initiator SEP executes the job. Its configured class must match the CLASS on the JCL JOB statement.
• A batch printer SEP processes output. Its class must match the job’s MSGCLASS or the applicable SYSOUT class.

Consequently, execution capacity and output-processing capacity are independent. A job can execute successfully yet leave output waiting because no suitable printer SEP is available. Conversely, a job can remain in the input queue because no initiator supports its job class. SEPs for JCL

The spool queues reveal which gate a workload has reached. Input contains jobs waiting to start—usually because an initiator for the correct class is unavailable. Active contains running jobs. Within Complete, the Output filter shows output waiting to be printed, again usually because a printer for the correct class is unavailable. Dispatch represents a transient condition where work has been scheduled to a batch or printer process but has not yet been actioned. Managing and Viewing Spool Queues

ESCWA’s JES Control page can start an initiator or printer dynamically. Specify the supported classes, choose the SEP type, and start it. The operational nuance is important: a dynamically created SEP exists only until the Enterprise Server region stops. Rocket also permits permanent SEP definitions, so dynamic initiation is useful for temporary capacity or diagnosis but does not itself establish persistent restart-time configuration. JES Control

Enterprise Server also lets an operator change a queued job’s Class or Priority after submission. In Server Explorer, open Show Spool, select the job, edit those fields, and apply the changes. Rocket states that either property can change the order in which jobs run. Changing the class therefore offers a documented way to redirect queued work toward an available initiator class without editing and resubmitting the original JCL. Update control information for a job

Takeaway: When JCL appears “stuck,” distinguish input scheduling from output scheduling: check JOB CLASS against initiator classes and MSGCLASS/SYSOUT against printer classes before treating it as a job failure.