SYSIN (Job Input) Transmission

Store-and-Forward Transparency

All sections in the job header are forwarded without change. As an intermediate node, no sections are added to the job header. The operator at the store-and-forward node can change the execution node of the job and this will be updated in the job header.

Job Header

The job header is created as soon as the job enters the VSE/POWER system. The header is used to store job-specific data (such as execution destination, default print and punch routes, etc.). Segmented job headers are supported up to the maximum allowed by the architecture.

VSE/POWER Section

The VSE/POWER section contains information specific for VSE/POWER's usage. For example, the due date information which specifies the date and time a job should be processed.

Job Trailer

The job trailer is built as soon as the job enters the VSE/POWER system. Because VSE/POWER doesn't use a lot of the counts that JES2 and JES3 use for scheduling purposes, the majority of the fields in this record are not used and are set to defaults.

Data Set Header

Record Characteristics Change Section. This section is put into the job stream as soon as VSE/POWER determines that the stream may contain records greater than 80 bytes. This means that when a SYSIN stream is read from a diskette with a header that says 128 bytes, the record characteristics change section is sent directly after the job header. There is also a VSE/POWER section appended to this section to allow the transmission of the diskette address used when reading the file.

Notification

When a job is first read in by VSE/POWER, the node and userid for notification are stored in the job header record if “NTFY=” was specified on the JCL JOB statement.

If the job header contains a notify userid and the job is transmitted from its originating node for execution on another node, the job transmitter of each intermediate node will issue a message to the user indicating that the job has been transmitted.

When the job completes execution, the execution processor on the execution node will issue a notification message to the user specified by the notify userid field and by the originating node field.