One of jcl Learning

Jcl must be stored as a member in the partition data set (PPS. When allocating a data set to jcl, the format must be fixed length (recfm = FB) and the record length is 80 bytes (lrecl = 80 ).

 

Jcl can be submitted in three ways:

1. On the jcl editing page, use the sub command to submit

2. on the member list page, use sub to submit before jcl member.

3. Use the TSO command Tso submit 'cn0003. Test. jcl (jcl1) 'to submit.

 

TSO sdsf st to view the returned results ,? View the details of jcl. In the result, the three ddnames of jesmsglg, jesjcl, and jesysmsg are available in all jcl results.

Jesmsglg, which stores the return values and statistical information of each step;

Jesjcl: stores the jcl statements submitted by the user;

Jesysmsg, which stores detailed information that occurs when Jes runs jcl.

 

Roles of job statements

Provide the accounting information of jcl;

Execution features are defined;

Determine the level of system information and the number of jcl statements;

Hold a job;

Specifies the priority of a job;

Restrict the use of system resources.

 

The job name ranges from 1 ~ It consists of 8 characters, indicating a job. When a job is submitted, the system generates a job number for the job, which is unique throughout the system. Because the system cannot run two jobs with the same job name at the same time, the jobs that run at the same time cannot have the same name.

 

Job name job ([Account-number] [, accounting-information]…) Programmer name

The job statement has two positional parameters:

Accounting information. The number of characters in all accounting information cannot exceed 143 characters.

Programmer name. It cannot exceed 20 characters. If it contains spaces or special characters, it must be enclosed in single quotes.

 

Keyword parameters in job

1. addrspc

Specifies the storage type required for a job. There are two sub-parameters: virt and real. Vrit indicates the virtual page storage of job requests, while real indicates the real storage space of job requests. The default value is virt (addrspc = virt ).

2. bytes

Specify the maximum number of kilobytes of output data sets of the print job. This parameter also specifies how the system outputs the job when the maximum number of bytes is exceeded. These methods include canceling a job (dumping or not dumping) or continuing the job and issuing a warning message that exceeds the maximum number of bytes to the operator.

3. Class

The class parameter specifies the job category. You can select 36 job classes in jcl with a letter ~ Z table and number 0 ~ 9. Jobs of the same category are waiting for execution in the same input queue.

 

 

4. typrun

It is used to process a job that requests special processing.

For example, if typrun = scan, the request system only checks the jcl syntax of the job and does not assign devices to the job if it is not executed.

 

 

Exec statement

A job can have a maximum of 255 exec statements.

The exec statement has two location parameters: PGM and Proc. Each exec statement has only one PGM or proc parameter.

1. PGM

The PGM parameter is used to specify the name of the program to be executed. The program is stored as binary executable code in the member of a partition dataset (PPS. The system searches for the members referred to by PGM and loads and executes the members specified by the joblib dd statement in the job or the PPSS defined by the steplib dd in the job, or the default TPSs. The call methods of the program name are divided into direct call and indirect call.

2. PROC

Specifies the name of the process to be run in the job step.

(1) The name of a member in the cataloguing process is an alias. The cataloguing process specifically writes process statements to a dataset which is catalogued in the system.

(2) The PROC in the stream defined in this JCL. In-stream PROC is a process defined between PROC and PEND in JCL.

3. COND

Test the return code executed in the previous job step to determine whether to execute the job step. You can perform a test on the return code of a specific job step to test the Returned Code after each execution. If the test conditions are not met, the system executes this job step. If the test conditions are met, the system does not execute this job step. The COND parameter in the first EXEC statement in the job will be ignored by the system. (When the test conditions are met, the system does not terminate the JOB normally. Instead, the JOB is skipped and the JOB continues to execute the next JOB step.