+LOGPDS
The +LOGPDS parameter overrides the log partitioned data set name contained in the product configuration load module set and lets you define the partitioned data set that stores diagnostic information if a BMC AMI Utility abends.
During BMC AMI Utilities execution, the data set name is allocated to the LOGPDS DD. If the +LOGPDS parameter contains variables, the product resolves these before the allocation.
Related topics
The dataSetName can contain the following variables:
Variable | Description |
|---|---|
&ATTACH | Db2 group attachment name or Db2 subsystem ID (up to four characters) |
&GROUP | 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). |
&SSID | Db2 subsystem name or group name specified on the PARM=name attribute |
&SUBSTR | See &SUBSTR |
&VER | Version (for example, 1310) of the BMC AMI Utility being executed |
&VER3 | First three characters of the version (for example, 131) of the BMC AMI Utility being executed |
&VER2 | First two characters of the version (for example, 13) of the BMC AMI Utility being executed. |
&USER1 | Value of the USER1(userVariable) parameter |
&USER2 | Value of the USER2(userVariable) parameter |
You can allocate the LOGPDS DD to a JES SYSOUT class or a dummy data set instead of to a PDS:
- To allocate to a JES SYSOUT class, the dataSetName should be a single character (A–Z, 0–9, or *).
- To allocate to a dummy data set (DD DUMMY), the dataSetName should contain DUMMY.
- If a BMC AMI Utility detects that the LOGPDS DD is allocated to a JES SYSOUT class or DD DUMMY, the utility writes to the LOGPDS DD and to the BMC AMI Utilities JOURNAL data set.