Job statement information used in panels

Some of the HCD tasks, invoked from the dialog, generate batch jobs. These batch jobs use EXEC procedures as shown in Table 1.

The first time you use a task that generates an HCD batch job, you must specify a JOB control statement for the job. This statement can contain user-specific information, such as an account number and SYSOUT class. For example:

You need to specify the statement only once; it is saved in your user profile and reused for all subsequent HCD batch jobs that you request (in this and following HCD sessions) until you change it. HCD does not validate the JOB statement.

With JCL overwrite statements you can modify the EXEC procedures that are invoked by the job.

Notes:

A batch job requires a region size large enough to contain the HCD code (4M bytes) as well as the IODF (or two IODFs when you compare two IODFs).
A batch job to build an IOCDS must run on the processor on which the IOCDS is to be updated, except for processors configured in a System z cluster.
A batch job generated by HCD cannot run when the HCD dialog has exclusive access to the same IODF that the batch job uses. You can release the IODF by changing to another IODF or by ending the HCD session.
To use the HCD profile options (e.g. UIM_LIBNAME=*) for a batch job that is started from the dialog, you need to allocate the HCD profile data set to xx.HCDPROF, where xx is the job step name.
In a sysplex environment, use the JOBPARM parameter to specify in which system of the sysplex you want the batch job to run. For additional information, see How to invoke HCD batch utility functions.

Table 1 lists the HCD tasks that use batch jobs. It also lists their job step names, and EXEC procedure names.