II14638: IEC161I 120-053 AFTER REDEFINING VSAM KSDS, AIX, VRRDS ON Z/OS 1.10 AND ABOVE (5695DF106 CISIZE CASIZE)

APAR status

• INTRAN

Error description

• Reference: z/OS V1R10.0 Migration  GA22-7499-14
  Section: 9.2.8 DFSMSdfp: Accommodate changes in the CA sizes
  assigned to newly allocated VSAM data sets
  
  MSGIEC161I RC120 RSN053, MSGIEC161I 120-053,
  DFS0730I O,DC; DFHFC0964 8502,0008,00DC:
  DSI555I RC = X'08', ERRCODE = X'DC'
  
  Any of the above can occur on z/OS 1.10 after moving a
  VSAM data set with DFDSS or other tools that cause reallocation
  of the cluster. This is because the CISIZE of the INDEX may
  change due to the CA size of the DATA changing.
  
  The above mentioned migration guide states:
  z/OS V1R10 includes a change in control area (CA) size
  selection for all new allocations of VSAM data sets on any
  volume type (not only extended address volumes). The system
  selects a control area size of 1, 3, 5, 7, 9, or 15 tracks.
  Previously, the system selected from a wider variety of
  possible CA sizes. As previously, you cannot explicitly
  specify control-area size. Generally, the primary and
  secondary space  allocation amounts determine the CA size. For
  requests where either the  primary or secondary allocation
  amount is smaller than one cylinder, the  system might adjust
  the primary and/or secondary quantity. The system might also
  select a CA size that is different from what was selected in a
  prior release. For example, a TRK(24,4) request results in a
  control area of 5 tracks, and primary and secondary amounts
  of 25 and 5 tracks, respectively.
  
  Steps to take:
   CA size is derived from the requested primary and secondary
   allocation. Because the CA size is computed differently in
   z/OS V1R10, adjust any primary and secondary allocation
   requests to accommodate the CA size you rely upon.
  
   If you have any programs that depend upon a specific CA size
   that is no longer supported, change the programs to accept a
   CA size of 1, 3, 5, 7, 9, or 15 tracks.
  
  Tip: A tool can help you perform this migration action. The tool
  is available from the FTP site ftp.software.ibm.com in the
  directory  servers/storage/support/software/dfsms/ as
  INDXCI10.JCL.CNTL.TRSD.  Download the tool in binary mode to a
  data set with the following  attributes: LRECL=1024,
  BLKSIZE=6144, RECFM=FB, and DSORG=PS.
  After  downloading, unterse it either with AMATERSE or TRSMAIN.
  The tool consists  of a REXX exec and JCL to execute it in
  batch.
  Reference the z/OS 1.10 Migration book for more information.
  
  Also, for more information about CA sizes and allocating space
  for a VSAM data set, see z/OS DFSMS Using Data Sets, SC26-7410.
  

Local fix

• Adjust the primary and secondary allocation requests to
  accommodate the CA size you rely on.
  

Problem summary

Problem conclusion

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