JES2 control statements
Lines in a job that start with /* and a keyword, which give instructions to JES2 rather than to z/OS.
Also written JECL, /*JOBPARM, /*ROUTE, /*OUTPUT, SYSAFF, /*XEQ
Most JCL is read by z/OS. JES2 control statements are read by JES2. They begin with /* followed by a keyword, and they go after the JOB statement. They are sometimes called JECL, job entry control language.
Some common ones: /*JOBPARM sets job options, such as SYSAFF to choose which system in a sysplex runs the job, or LINES to limit printed output. /*ROUTE sends the job's output, or the job itself, to another place. /*XEQ names another JES2 node where the job should run. /*OUTPUT sets options for printed output.
A plain /* on its own is different. It marks the end of instream data, not a JES2 control statement.
Many of these functions now have JCL equivalents, such as the JOB statement's SYSTEM and SCHENV parameters and the OUTPUT statement, so newer jobs use them less. You will still find them in older jobs. Sites using JES3 have their own control statements, which start with //*.
Where can I learn this hands-on?
Right here, at ZedBank. You take a junior job at a simulated bank and learn each part of the work by doing it, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- JES2The job entry subsystem: the part of z/OS that queues jobs, decides when they run, and collects their output.
- JOB statementThe first statement in every job, giving it a name and telling the system who is running it and how to treat it.
- JCLJob Control Language: the language used to tell the mainframe what programs to run, in what order, and with what files.
- NJENetwork Job Entry: the JES feature that sends jobs, output and files between separate mainframe systems.
- Job classA single-character label on a job that tells the system what kind of work it is and how to schedule it.