Overview of control statements

IMS HP Load supports various options to control the behavior of IMS HP Load jobs.

Subsections:

Control statements for process control

The following table lists the keywords that you can specify for the process control.

Table 1. IMS HP Load control statements for process control
Keyword Accepted values Default Description
BMSETDSG n or (n1, ..., n10)

n=value or *

* Specifies the threshold value that is used to set the bitmap block. See BMSETDSG control statement.
BYTELIMIT DBD

NOLIMIT

nnnnnnnn

DBD Specifies the maximum number of bytes for a database record that can be inserted into the root addressable area. See BYTELIMIT control statement.
CHKEMPTYUL YES

YES,WARN

YES,WARN,n

NO

YES,WARN,4 Specifies whether to check if the unloaded data set contains segment data. See CHKEMPTYUL control statement.
CHKTRAIL YES

YES,WARN

YES,ERROR

NO

YES,WARN Specifies whether to check for the existence of the trailer record. See CHKTRAIL control statement.
CHKUPDT YES

YES,ABEND

YES,WARN

NO

NO Specifies whether the check for an update is done between unload and reload processes. See CHKUPDT control statement.
COMPAUTH YES or NO NO Specifies whether to call the segment compression exit in supervisor state. See COMPAUTH control statement.
COMPRESS YES or NO YES Compresses segments during reload. See COMPRESS control statement.
DATXEXIT YES or NO NO Controls the IMS/ESA® Year 2000 Exit Tool support. See DATXEXIT control statement.
EXTENT 1–120 120 Specifies the maximum number of extensions of the OSAM data set that can be created. See EXTENT control statement.
FRSPC YES or NO YES Secures free space factors. See FRSPC control statement.
GDGBASE YES or NO NO Specifies whether to create a GDG base entry. See GDGBASE control statement.
GDGLIMIT nnn 10 Specifies the maximum number of GDS that can be associated with the GDG that is to be created. See GDGLIMIT control statement.
HPIO YES or NO YES Specifies whether IMS HP Load uses the High Performance I/O Driver for output data. See HPIO control statement.
INPUT DFSUINPT, exitname,L DFSUINPT Specifies the input data set, the user exit routine, and its language. See INPUT control statement.
ITKBLOAD library_name or *NO *NO Specifies the library name of IMS Tools KB. See ITKBLOAD control statement.
ITKBSRVR server_name or *NO *NO Specifies the XCF group name of the IMS Tools KB server. See ITKBSRVR control statement.
OADSPR YES or NO NO Specifies whether to reduce the usage of data space to process (P)HDAM OA. See OADSPR control statement.
PAD X'00'-X'FF' X'00' Specifies the padding character to fill out the segments to adjust to the length defined in the DBD definition. See PAD control statement.
PROGMON 0–999999 0 Monitors job progress. See PROGMON control statement.
RAAFORMAT YES or NO YES Formats the HDAM RAA®. See RAAFORMAT control statement.
RECNUM nnnnnnnnnn (none) Specifies the number of unload records that are to be reloaded. See RECNUM control statement.
RMBSEGSZ YES or NO NO Specifies how IMS HP Load calculates the database record size to determine whether to put the records into the overflow area. See RMBSEGSZ control statement.
SEARCH 0–999

-999–-0

3 Sets the space search boundary. See SEARCH control statement.
SEQERROR ABEND or SAVE ABEND Handles key sequence errors. See SEQERROR control statement.
SORT YES, NO, or COND NO Specifies whether to run physical sequential sort before loading with (P)HDAM. See SORT control statement.
SORTHIDAM YES or NO NO Specifies whether to run the sort processing before loading a HIDAM or PHIDAM. See SORTHIDAM control statement.
TWINSTAT YES or NO NO Prints statistics about the twin chained segments in the Segment Statistics report. See TWINSTAT control statement.
USEREXIT exitname (none) Specifies the name of the user exit routine. See USEREXIT control statement.
USERHDR element (none) Specifies the name of the element of the header portion of the unloaded record. See USERHDR control statement.
USERHDRX exitname (none) Specifies the name of the user header conversion exit routine. See USERHDRX control statement.
WF1DSN data_set_name or GDG_base_name.&GDG (none) Specifies the data set name for the DFSURWF1 data set when dynamically allocating the data set. See WF1DSN control statement.
WF1REC YES or NO YES Specifies whether to create WF1 records that are written to the DFSURWF1 output work data set. See WF1REC control statement.
WF1SPACE CYL or TRK, primary_alloc, secondary_alloc (none) Specifies the space parameter for the DFSURWF1 data set when dynamically allocating the data set. See WF1SPACE control statement.
WF1UNIT unit_name SYSALLDA Specifies the device for the DFSURWF1 data set when dynamically allocating the data set. See WF1UNIT control statement.
WF1VOL volume_name or * (none) Specifies the volume names for the DFSURWF1 data set when dynamically allocating the data set. See WF1VOL control statement.
WFPHLQ hlq (none) Specifies the high-level qualifier for the WFP data sets. See WFPHLQ control statement.
WFPSPACE CYL or TRK, primary_alloc, secondary_alloc (none) Specifies the SPACE parameter for the WFP data sets when allocating WFP data sets dynamically. See WFPSPACE control statement.
WFPUNIT unit_name SYSALLDA Specifies the device for the WFP data sets when allocating WFP data sets dynamically. See WFPUNIT control statement.
WFPVOL volume_name or * (none) Specifies the volume names for the WFP data sets when allocating WFP data sets dynamically. See WFPVOL control statement.
WFPVOLCNT nnn (none) Specifies the volume count for the WFP data sets when allocating WFP data sets dynamically. See WFPVOLCNT control statement.
ZIIPMODE COND or NEVER NEVER Specifies whether to offload eligible workloads to zIIP processors. See ZIIPMODE control statement.

Control statement for performance

The following table lists the keywords you can specify for performance improvement.

Table 2. IMS HP Load control statements for performance
Keyword Accepted values Default Description
BUFFERNO (Note 1) 5–32767 N/A Sets the number of IMS HP Load buffers. See BUFFERNO control statement.
DBIOBUF 1–999 30 (for VSAM)

15 (for OSAM) (Note 2)

Sets the number of VSAM/OSAM buffers. See DBIOBUF control statement.
DBRLBUF See Note 1 1–999 45(Note 2) Sets the number of IMS HP Load buffers. See DBRLBUF control statement.
Notes:
  1. DBRLBUF and BUFFERNO are mutually exclusive.
  2. For HISAM, the default value for DBIOBUF is 15, and the default value for DBRLBUF is 2.

Control statements for reloading a HALDB database

The following table lists the keywords you can specify when reloading a HALDB database.

Table 3. IMS HP Load control statements for reloading a HALDB database
Keyword Accepted values Default Description
DELOLPART NO or YES NO Effective only when IMS HP Load is called from IMS Online Reorganization Facility. Specifies whether IMS HP Load deletes unloaded records that will not be reloaded to the HALDB partitions identified by the LPART statement. See DELOLPART control statement.
ILDSBLD C

YES

YES,COND

YES,DSPR

NO

YES,COND Specifies whether to build ILDS and how to build it during reorganization. See ILDSBLD control statement.
ILEDATAC data_class_name (none) Specifies the data class (DATACLAS) for HPSRILEA and HPSRILEB. See ILEDATAC control statement.
ILESTORC storage_class_name (none) Specifies the storage class (STORCLAS) for HPSRILEA and HPSRILEB. See ILESTORC control statement.
LPART (partname,nnn), (part1,..,partn), or *ALL  N/A Specifies the HALDB partitions to load. See LPART control statement
PARTINIT NO

YES

YES,PINITON

YES,UNLOAD

YES,LPART

YES,ALL

NO Initializes partitions not populated by any segment during reload. See PARTINIT control statement.
PARTSTAT YES or NO YES Generates the statistics report for the partition. See PARTSTAT control statement.
REPAIRILK NO or YES NO Specifies whether to reassign indirect list keys (ILKs). See REPAIRILK control statement.

Control statements for performance diagnosis

The following table lists the keywords that you can specify for performance diagnosis.

Table 4. IMS HP Load control statements for performance diagnosis
Keyword Accepted values Default Description
DBDSNAP YES or NO NO Generates the DBD Snap report. See DBDSNAP control statement.

Control statement syntax

A keyword and its associated value can be coded in a free format (columns 1–72) provided these syntactical coding rules are followed:

  • A keyword and its value must be on a single control statement.
  • A keyword must be separated from its associated value by an equal sign (=). The equal sign must not be preceded by blanks, and not be followed by blanks; that is, a null value is not allowed.
  • A comment line must begin with an asterisk (*) in column 1.
  • You can abbreviate YES as Y and NO as N.