Running the HCI

The HCI can be submitted as a batch job or a started task. See the following sample JCL.

Batch Job Execution

Customize the HCI batch job execution JCL example, shown here, for your installation.

Batch Job Execution JCL

Example

//*
//* Place your JOB statement here
//*
//STEP1    EXEC PGM=HCIMMAIN,DYNAMNBR=125,
//             REGION=0M
//STEPLIB DD DISP=SHR,DSN=CPWR.SLCXAUTH
//HCIJCL   DD SYSOUT=(A,INTRDR)
//HCIPRINT DD SYSOUT=*,FREE=CLOSE,SPIN=UNALLOC
//SYSPRINT DD SYSOUT=*
//ABNLIGNR DD DUMMY
//IDIOFF   DD DUMMY

Started task execution

Store the started task JCL in SYS1.PROCLIB or an installation appropriate procedure library. Tailor the HCI started task execution JCL example, for your site.

Started Task Execution JCL

Example

//HCIPROC PROC
//STEP1    EXEC PGM=HCIMMAIN,DYNAMNBR=125,
//             REGION=0M
//STEPLIB DD DISP=SHR,DSN=CPWR.SLCXAUTH
//HCIJCL   DD SYSOUT=(A,INTRDR)
//HCIPRINT DD SYSOUT=*,FREE=CLOSE,SPIN=UNALLOC
//SYSPRINT DD SYSOUT=*
//ABNLIGNR DD DUMMY
//IDIOFF   DD DUMMY

JCL notes

This section describes the HCI execution JCL.

JOB Statement

Your installation's requirements for the JOB statement dictate how it must look. Ensure that you specify REGION=0M on the JOB statement as well as later on the EXEC statement. Because the HCI is a long-running address space, either specify a job CLASS that will not time out, or specify TIME=NOLIMIT.

EXEC Statement

In order for the HCI to manage its environment efficiently, code REGION=0M and TIME=NOLIMIT on the EXEC statement. The HCICNGCA element attributes give you the opportunity to limit the amount of virtual storage consumed by the HCI so there is no reason to limit the storage with the REGION parameter as well. The HCI abends if it issues a request for virtual storage and that request is not satisfied due to the REGION limit. Coding TIME=NOLIMIT allows the HCI to remain executing for as long as you desire.

//STEPLIB DD

We recommend that you place the HCI load modules in a data set named in the //STEPLIB (or //JOBLIB) DD statement. Although you may install the HCI into a LINKLIST data set, we do not recommend that you do so. By using a //STEPLIB DD statement, you isolate your site's installation from problems caused by future releases of the HCI. All data sets in the HCI //STEPLIB data set must be APF-authorized.

//HCIPRINT DD

The //HCIPRINT DD statement is an output data set that can name a SYSOUT class which contains diagnostic information previously written to the system console. Additional information concerning the HCI, including an XML representation of your configuration, can be found in this data set as well. If you contact BMC Support for any reason, have the contents of this data set available.

//HCIJCL DD

The //HCIJCL DD statement is an output data set which must be coded exactly as shown. This is the data set to which the HCI writes JCL statements to be submitted via the Server Activation Facility.

Starting the HCI Automatically at IPL Time

You may place the PROC that starts the HCI into the list of procedures, which are automatically started by z/OS at IPL time. However, ensure that VTAM, TCP/IP, VSAM, RACF and the BMC AMI License Management System are all initialized before starting the HCI.