OA47508: IDCAMS ALLOCATE BEHAVIOR CHANGES AFTER OA42679

APAR status

• Closed as documentation error.

Error description

• OA42679 (1.12, 1.13  & 2.1), and OA49981 (2.2) changes the TSO
  interface IDCAMS invokes for processing the ALLOCATE command
  from the Terminal Monitor Program (TMP) to Service Facility
  (TSF).  TMP references in the Access Method Services manuals
  need to be removed as well as documentation of the changes of
  behavior to expect when using the ALLOCATE command.   Such
  changes include:
  
  - TSO environment established by Allocate will now only be
  terminated at step end.  This may affect applications running
  ALLOCATE via the PPI in which the step may continue to perform
  other processes and additional allocations.
  
  - To ensure a prefix is not prepended to a dataset name,
  quotes should be used to create a specific DSN.  The way TSF and
  TMP generate prefix names are different and thus a prefix may be
  added to an unquoted DSN where prior to the APAR it had not.
  
  
  Please also reference supporting apars OA43330 and OA45876
  
  CATKEYS: IDC2015 IDCALLOC IDCPPI IDCINFO
  

Local fix

• make changes to applications invoking the ALLOCATE command
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IDCAMS ALLOCATE with APAR OA42679.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: IDCAMS ALLOCATE with OA42679 changes    *
  *                      the way it invokes TSO/E causing        *
  *                      differences such that you must specify  *
  *                      the data set name explicitly with       *
  *                      quotes so that the default prefix       *
  *                      is not prepended to the data set name.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  IDCAMS ALLOCATE with OA42679 changes the way in which the
  data set name is treated.
  

Problem conclusion

• Beginning in APAR OA42679 (PTF is applicable to z/OS V2R1,
  V1R13, and V1R12), IDCAMS changed the way it invoked TSO/E
  to issue an IDCAMS ALLOCATE command.  IDCAMS now uses the TSO/E
  SERVICE Facility (TSF) to invoke ALLOCATE,rather than running
  ALLOCATE under the TSO/E TMP (Terminal Monitor Program)
  IKJEFT01.
  In this new environment, the default prefix used is the userid.
  So now, with IDCAMS APAR OA42679 applied, you must specify the
  data set name explicitly with quotes in the ALLOCATE command so
  that the default prefix is not prepended to the data set name as
  a high level qualifier.
  If you have a RACF TSO segment, there is no change in behavior.
  So, the key difference is that running an IDCAMS ALLOCATE the
  old way with a RACF defined user with no TSO segment would have
  resulted in a null prefix, whereas the new way defaults to the
  prefix equal to the userid.
  Note:When the quotes are not specified within the DATASET
  parameter in the IDCAMS ALLOCATE command, and if you do not have
  a RACF TSO segment, the following message is missing after APAR
  OA42679 and a userid as a prefix is added.
  IKJ56644I NO VALID TSO USERID, DEFAULT USER ATTRIBUTES USED
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels