DFSMSdfp: Accommodate change for data set name prefix in IDCAMS ALLOCATE
Description
With IDCAMS APAR OA42679 and TSO/E APAR OA43330 applied, the IDCAMS ALLOCATE command is changed in the way that it starts TSO/E to allocate a data set. IDCAMS processing now uses the TSO/E Service Facility (TSF) to allocate a data set, rather than running the ALLOCATE command under the TSO/E terminal monitor program (IKJEFT01). With this change, the user ID assigned to the IDCAMS batch job is treated as the default data set prefix. That is, the user ID for the IDCAMS batch job is appended to the data set name as a high-level qualifier, if you specify the data set name on the DATASET keyword without quotation marks and the user ID does not have a RACF TSO segment.
Previously, the IDCAMS ALLOCATE command used a null prefix for the allocated data set, if you specified the data set name on the DATASET keyword without quotation marks and the user ID did not have a RACF TSO segment.
- Before this change, TSO runs under the UADS user. If the data set name is specified without quotation marks on the DATASET keyword, and the user has a UADS PROFILE PREFIX(prefix), the prefix is used as the data set prefix. Otherwise, the user ID is used as the data set prefix.
- After this change, the user ID is always used as the data set prefix. Therefore, if the user ID and UADS PROFILE PREFIX(prefix) are different, the high-level qualifier for the data set is changed.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
| Element or feature: | DFSMSdfp |
|---|---|
| When change was introduced: | z/OS V2R1 and z/OS V1R13, both with APARs OA42679 (DFSMS) and OA43330 (TSO/E) applied. |
| Applies to migration from: | z/OS V2R1 and z/OS V1R13, both without APARs OA42679 (DFSMS) and OA43330 (TSO/E). |
| Timing: | Before the first IPL of z/OS V2R2. |
| Is the migration action required? | Yes, if you use IDCAMS ALLOCATE, do not specify the data set name in quotation marks on the DATASET keyword, and the user ID assigned to the IDCAMS batch job does not have a RACF TSO segment. |
| Target system hardware requirements: | None. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | None. |
| Restrictions: | None. |
| System impacts: | Failure to include the data set name in quotation marks can result in allocation errors. |
| Related IBM® Health Checker for z/OS® checks: | None. |
Steps to take
Check for JCL and programs that use the IDCAMS ALLOCATE command. Ensure that the data set name is specified in quotation marks on the DATASET keyword. Doing so ensures that the user ID is not appended to the data set name as a high-level qualifier.
When the IDCAMS ALLOCATE command is run by a user with a RACF TSO segment defined, no change is required.
Reference information
Documentation APAR OA47508 describes these changes. For more information about the IDCAMS utility, see z/OS DFSMS Access Method Services Commands.