The +CONTROLPREFIX parameter allocates INFO and OUTPUT data sets with the provided prefix string, instead of using the prefix value specified by WORKPREFIX. Using +CONTROLPREFIX allows these two data sets to be in a different SMS pool because they stay on the system for the number of days specified with the parameter OUTPUTAGE, while the other data sets are deleted upon successful completion of the job.
You can set the value of the +CONTROLPREFIX parameter by using the XSUTGLOB-global-variable-definition-automation-control-point.
The value is defined as follows:
| Any valid MVS high-level qualifier (HLQ) or supported variable. You can use any of the following symbolic variables:
| |
|---|
| Db2 group attachment name or Db2 subsystem ID (up to four characters) | | Db2 data-sharing group name (up to eight characters) In a non-data-sharing environment, &GROUP contains the Db2 subsystem ID (up to four characters). | | The Db2 subsystem name or group name specified on the PARM=name attribute | | The version (for example, 1210) of BMC AMI Utility being executed | | The first three characters of the version (for example, 121) of BMC AMI Utility being being executed | | The first two characters of the version (for example, 12) of BMC AMI Utility being executed. | | The value of the USER1(userVariable) parameter | | The value of the USER2(userVariable) parameter |
The HLQ is appended to a unique timestamp-based identifier, and the data set suffixes. |
|---|
InformationExample
+CONTROLPREFIX(ADMIN.NGT)
In this example, the data sets should begin with ADMIN.NGT:
- ADMIN.NGT.tttttttt.uuuuuuuu.INFO001 (information data set for BMC AMI Utilities)
- ADMIN.NGT.tttttttt.uuuuuuuu.OUT001 (output data set for BMC AMI Utilities)
