| Job Output | ||
|---|---|---|
 |  | |
| Job Output | ||
|---|---|---|
| | | |
|
Entire document Available as PDF |
Table of Contents
For the purposes of this chapter, hardcopy output refers to printed, plotted, or microfiche output. Other types of output (such as tape or disk data sets) are discussed in the relevant IBM and CNS manuals. See the "Recommended References" chapter in the CNS General Information: CNS Software and Software References document (D0009).
Printed output at the SSRB can be
high-speed line printer
IBM 3130 laser printer
Standard output is printed on high-speed line printers in all upper case at 8 lines per inch on the white side of 14-7/8" x 11" computer paper. Output printed on different paper (for example, bond paper or gummed labels) or using different print bands is called special-forms output. Special forms are discussed in detail in document D0077, Special Forms Output.
Most jobs that generate printed output can be set up to produce output directly to CD-ROM. Contact the CNS Support Desk for specific information on this service.
High-speed line printer output, special-forms output and plotted output are picked up from the SSRB lobby. Output is filed in numbered bins according to the last three digits of the JES2 job number. This number is displayed on your screen when the job is submitted through an interactive terminal and accepted by JES2. Microfiche and batch-job output with a header of INSIDE can be picked up at the Tape Librarian's window, 102C SSRB. To pick up output at the Tape Librarian's window after 4:00 p.m. and on weekends and holidays, call the Shift Supervisor at 392-2291.
Printed output from jobs without a ROUTE statement is sent back to the site or node from which it was submitted. For jobs using ROUTE statements, output is sent to the destination on the ROUTE
statement. If a job has an invalid ROUTE statement, it will print at the site from which it was submitted.
Printed output for jobs routed to a remote-batch station should be picked up at that site.
Output routed to CNS's central site (NER.R0) will be filed in the SSRB lobby. Exceptions are jobs that specify a header of INSIDE (see the following section). IBM 3130 output is packaged in a "shrink-wrap" bag to keep the pages together.
Output that is too bulky to fit into the bins is placed on the shelves below the bins. Unclaimed printed output is recycled after three days (excluding weekends and holidays).
Printed output has several sections, which are described in the "Description of Printed Output" section below.
Printed output for z/OS (OS/390) batch jobs has the following parts, in this order:
Header page
JES2 statistics
Input JCL and JCL overrides
System substitution JCL
For each step:
Allocation messages
Step execution messages
Disposition messages
EXCP count
Step termination message
Estimated execution charges
User output (in DD order, not open order)
Trailer page, including output charges
If multiple copies are requested, all output specified, with the exception of the header and charge pages, will be repeated. The "Multiple Copies" section below described how to request more copies.
The header page enables the operators to separate and file output. It contains the job name, the name you specified in the "your name" field on the JOB statement, the JES2 job number, the userid, and the date and the time the job was
printed. Two header fields appear at the top of the first page of output. The uppermost field on the page is the HEADER1 field; the field below it is the HEADER2 field. The HEADER1 field contains the job name (the name you supplied after the initial // on
the JOB statement). HEADER2 can vary. When your batch job routes output directly to a printer, the HEADER2 field contains the job number, unless you specify a header of "INSIDE". See "Specifying a Header of INSIDE" for
more information. Output routed to CNS's printers from any other node will have NET.JOB in the HEADER2 field. This cannot be changed.
By default, the HEADER2 field of printed output contains a number corresponding to the following format:
Jnnnnn c
In this format,
Jis for z/OS (OS/390) batch job output
nnnnnis the job number
cis the output class (normally A for printer output)
This allows output to be filed in the SSRB lobby under the last three digits of the z/OS (OS/390) batch job number.
There may be certain output documents that you do not want filed in the SSRB lobby for security reasons, such as grade reports or information requiring a non-disclosure agreement. Changing the HEADER2 option to INSIDE
will cause these jobs to be filed behind a locked door inside the operations area at SSRB. When you come to pick up your output, you will be asked by the operator for your job number and account number.
You can use the following JOBPARM statement to change the header to INSIDE. These jobs are filed inside the operations area.
/*JOBPARM HEADER=INSIDE
The system log contains a record of messages generated by the job and printed on the system operator's console. All messages are time stamped, and the heading line contains the date the job began execution. Some of the messages on the log are
generated by JES2 and are preceded by the characters $HASP. Other messages are directed to the job by the system operator while the job is executing. These messages are preceded by the letter N.
All other messages are generated by the operating system or the job itself. Note that the system log can be suppressed by specifying the appropriate JOB or JOBPARM statement parameter. We do not recommend this,
however, because the log can contain useful information if the job does not run successfully.
System messages are generated by the operating system Job Scheduler during its processing of the job. They normally include a listing of the JCL statements in the job and messages generated during step initiation and termination, including I/O
device allocation and de-allocation. JCL errors are noted here, also. Most of these messages have a standard identifier (such as IEF2371) to help you look them up in the IBM system messages manuals.
In the job's JCL listing, the first three columns identify the types of JCL statements. The following table describes how to identify the types of JCL statements in your job listing.
Table 4. Identifying JCL Statements in Job Output
COLUMNS | |
| Input JCL you have provided | |
| Cataloged procedure statements | |
| Cataloged procedure statements you override | X / |
| Cataloged procedure statements that the system considers comments | X X * |
| Comment statements | * * * |
| In-stream procedure statements | + + |
| In-stream procedure statements you override | +
/ |
| In-stream procedure statements the system considers comments | + + * |
System messages produced can be controlled to some degree by the use of the MSGLEVEL parameter on the JOB statement. The second subparameter of the MSGLEVEL parameter specifies what
allocation/termination or recovery messages are to be printed.
The allocation message appears as follows:
IEF237I ### ALLOCATED TO ddn
In this message, "###
The "ddn DD statement defining a data set calling for a device (except for a DD statement containing the SYSOUT
parameter).
The output produced by the job follows the system messages. Each printed output data set (specified by a SYSOUT=A DD statement) is printed separately, rather than all data sets intermixed chronologically. In
general, data sets are printed in step order. Within each step they are printed in the order in which the DD statements occur.
Occasionally, the output for a job might need to be interrupted by the operator (for example, to change the paper on the printer). In this case, the output will be printed in several sections. Check to see that you have all of the output you are expecting when you pick up your output.
Charges related to the execution of a job are printed after the system messages. Charges are broken down as described in the "Userid Accounting" section of the CNS General Information: CNS Computing Services and Facilities manual (D0007). Charges for output are listed on the trailer page for the job.
Multiple copies of printed output can be requested in two ways. To get multiple copies of the whole job, specify the number of copies in the COPIES operand on the JOB or JOBPARM statement.
To get multiple copies of selected data sets only, or to get different quantities of different data sets, omit the multiple copies field on the JOB statement. Instead, specify multiple copies on the DD statement for
each data set for which multiple copies are desired. To get multiple copies on standard forms, the DD statement would be modified as follows:
//ddname DD SYSOUT=A,COPIES=nn
ddnameis
the same as on the replaced DD statement
nnis the number of copies of this data set to be printed for each copy of the job produced. The maximum is 99 per job.
For example, to request two printed copies of a data set on standard forms, the copies operand on the JOB and JOBPARM statements would be omitted and the DD statement would be coded as
follows:
//ddname DD SYSOUT=A,COPIES=2
To get multiple copies of data sets on special-forms paper, see document D0077, Special Forms Output.
If you specify copies on the JOB or JOBPARM statement (mm) and on a SYSOUT DD statement (nn), you will receive mm copies of the whole job, each
copy containing nn copies of the SYSOUT data set. The end result will be mm TIMES nn copies of the SYSOUT data set!
When a job is deleted from the system by the operator, you, or JES2, printed output is produced; however, it differs somewhat from that described above.
If the job is cancelled after execution has begun, the header and trailer page and the system log, system messages, and charge pages are still printed but the output is not. Charges are computed in the normal manner. An example of a job that might be cancelled during execution is a job that requests an operator reply; WTORs (Write To Operator for Replies) are not allowed at CNS.
If the job is cancelled before execution or because of a job control statement error, only a listing of the input JES2 control statements and JCL is produced with a header page, but no charge is assessed. Error messages are printed to show the reason for deletion. A description of the possible messages follows.
The ROUTE statement is invalid. The correct format is
/*ROUTE PRINT node.location
Call the CNS Support Desk if you cannot determine the correct location.
The SETUP statement is invalid. Check for the following errors:
a SETUP statement was included in a quick batch (Class Q) job
More than one SETUP statement was included for the same type of device
an invalid number of units was specified for a tape SETUP statement
The wrong password was used or the password was misspelled.
The JOB statement is invalid. Check for the following errors:
the job name contains illegal characters or is more than eight characters long,
the JOB statement has illegal syntax,
a numeric field contains non-numeric characters or is too long,
the "your name" field is longer than 20 characters,
an execution cutoff of 9999 was specified.
The preceding statement indicates that a continuation statement is to follow, but the next statement was not a valid statement continuation. Check for the following errors:
the continuation statement was omitted or was coded incorrectly,
the statement is complete, but has a comma following the last parameter.
If this message follows one of the messages above, or if there is no previous message, the job was cancelled by the system or by an operator. This can be done to a job that has been in the system for ten days or longer or for a job that requests non-existent services or services not allowed for that job's class, priority, or access number.
This message will be generated if the job name field of the JOB statement contains a jobname that begins with $$$$$. In addition, jobs with names of CICSTEST, CICSVS, or other reserved names will not be executed.
Not enough money existed under the userid to cover the largest charge possible for the job. The largest charge is computed from the cutoff values for execution time, lines printed, and copies specified on the JOB statement.
An ABEND is an ABnormal END during program execution. Below are listed some of the more common ABENDs. Descriptions of how to fix these are in IBM manuals.
Tape description on the DD statement does not match the tape format.
Missing DD statement or I/O attempt on an unopened file.
In FORTRAN, trying to store into someone else's area of main memory or a missing DD statement (quite often a subscript is bad); in COBOL, moving data to an unopened file.
Subscripting, not only outside the array, but completely outside of the machine.
Misaligned COMMON in FORTRAN or COBOL STOP RUN without exiting SORT.
In COBOL, blanks in a numeric field.
STAE control block limit exceeded (36).
Data set requested on the DD statement was not found.
Not enough time alloted on the JOB statement.
Ran off the end of the tape.
Not enough lines specified on the JOB statement.
Not enough main memory. Increase REGION size.
Module not found. Possibly typing error in program name.
Enough main memory to get the program loaded but not enough for buffers.
Security access has not been allowed.
Invalid control block; most likely a DCB or DEB
Ran out of space on a disk data set.
If you receive these codes and need an explanation of how to correct them, contact the CNS Support Desk.
If you have a Class Q or U problem, your output will probably be very short. The first page of the output will be titled "JES2 JOB LOG ...." Look at the next page for the following error message:IEFC612I PROCEDURE
xxxx WAS NOT FOUND
You have tried to run a program or procedure that is not available under the either Class Q or Class U. Find out which class supports the program or procedure you want to use. If you are sure that the program you are trying to run really is in Class Q or U, then check to make sure that you spelled it correctly. Class Q and Class U support only a limited number of procedures.
The following processors and programs run under CLASS Q and CLASS U respectively:
ASSIST, PLC, SAS, SPITBOL, SPSSQ, WATFIV, WPASCAL
CHRGLIST, CARDLIST
We offer the following suggestions to help you locate your output:
Use a unique job name.
When you submit your job, write down the job name, JES2 job number, and date and time of submission. If you need to ask an operator to help you locate the output, the operator will need the job name, job number, and time and date of submission.
Before you submit your job, make sure you have included a valid ROUTE PRINT statement in your JCL.
Output is filed by the last three digits of the JES2 job number. If your output is not in the properly numbered output bin, check neighboring bins, check the shelves below the proper bin, or check to make sure that the job has completed processing.
Unclaimed output is recycled after three days (excluding weekends and holidays).
| | | |
| z/OS Batch Jobs |  | How to Cancel Jobs |