Verification Output Notes

Job steps are enumerated from the beginning of the job, after all procedures are expanded. The EXEC PROC= command is counted first, as a separate step. Thereafter, all steps inside the invoked procedure are enumerated. The number of job steps, then, is the number of all EXEC commands processed during job execution.

No relationships are generated for EXECs to internal procedures.

For steps placed directly in a job, the Step Full Name attribute of the Data Connector object generated from DD statements is <execName> if specified, or “Ln <line-number>” if <execName> is empty. For steps within procedures, the following is the path to the step from the EXEC PROC= command placed inside the job through all intermediate procedures:

     <jobExecName>[/<ProcName>.<procExecName>]…

The parser creates an artificial program entity that defines the inputs and outputs for each sort utility invocation. The program has a name of the form JCLFileName.JobName.StepName.SequenceNumber, where SequenceNumber identifies the order of the step in the job. For every sort invocation in the program, you can view data structures for sort input and output records and the data movements between them in the HyperCode for the JCL file.

An invoked program is known as a system program if it is defined with a sort utility alias in Sort Program Aliases in Workspace Options > Verification > Settings for the JCL file type, or specified in the \<Enterprise Analyzer Home>\Data\Legacy.xml.