JCL repository data sets (EQQJSnDS)

Take special care when allocating the JCL repository data sets. The following information describes the allocation and use of these data sets.

HCL Workload Automation for Z maintains its own copy of JCL in the JCL repository data set for every job that it submits in the current plan. It uses a primary and alternate data set for the JCL repository, EQQJS1DS and EQQJS2DS. It reorganizes the JCL repository data set that is in use by copying it to the alternate data set and then switching over to use the newly copied data set. The value you specify on the MAXJSFILE keyword defines whether the JCL repository should be automatically copied and determines how often the automatic copy process should occur.

Use the EQQPCS01 sample job created by the EQQJOBS installation aid to allocate the JS data sets. This job allocates the JS data sets with the SPANNED attribute and maximum record size 180000. This limits the maximum number of JCL statements to 2249 for any one job. If you run jobs with a greater number of JCL statements, increase the record size. Calculate the required record size, in bytes, by multiplying the number of JCL statements in your largest job by 80, and add an extra 80 bytes for the header record. If you define your JS file without SPANNED, the greatest maximum record size that you can specify is 32760 bytes. This lets you store a job with up to 408 JCL records. If you define the JS data sets with SPANNED, the maximum record size you can specify is slightly less than a control area (CA). If you use the EQQUX002 exit, the largest job that can be returned by this exit is 7599 JCL records. Consider this, when you define the maximum record size of the JS data sets.