PK11477: IPR DRIVER INVOKES IDCAMS TO DELETE/DEFINE SHADOW DATA SETS

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• IPR Driver invokes IDCAMS to DELETE/DEFINE shadow data sets.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IPR Driver of IMS Parallel      *
  *                 Reorganization for z/OS Version 3 Release 1  *
  *                 (FMID=H25N310)                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR provides a new SPACEALLOC     *
  *                      control statement for IPR Driver.       *
  *                      SPACEALLOC=YES specifies to reallocate  *
  *                      the DASD spaces of the shadow data sets *
  *                      within the IPR Driver job-step.         *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR provides a new control statement SPACEALLOC.
  
  If you specify the HPSGAMSA input data set which contains
  the IDCAMS DELETE and DEFINE CLUSTER commands for each shadow
  data set, IPR Driver invokes the IDCAMS program internally
  with the commands. You can specify ALLOCATE commands
  for OSAM shadow data sets in the HPSGAMSA data set.
  
  The HPSGAMSA DD statement is not specified in the JCL stream,
  IPR Driver generates the commands automatically based on the
  attributes of the original data sets. If the old data sets
  with shadow names remain, the volume list and the SMS classes
  are derived from the old data sets.
  

Problem conclusion

Temporary fix

Comments

• ========================
  = DOCUMENTATION CHANGE =
  ========================
  IMS Parallel Reorganization for z/OS Version 3 Release 1
  User's Guide (SC18922801) should be changed as follows:
  ================================================================
  Chapter 2. IMS Parallel Reorganization Driver
  2.6     JCL Requirements
  2.6.2   DD Statements
  2.6.2.1 DD Names Common to All Processing Options
  (The new HPSGAMSA DD is added.)
  |HPSGAMSA DD (Input,LRECL=80,RECFM=FB,Optional)
  | Defines an optional data set that contains IDCAMS command
  | for deleting and allocating the DASD spaces of
  | the output data sets.  For details, see
  | "SPACEALLOC Control Statement".
  ================================================================
  (This new control statement is added.)
  |2.7.8.xx SPACEALLOC Control Statement
  |
  | The SPACEALLOC control statements specifies whether
  | to delete and allocate the DASD space for each shadow data set
  | within the IPR job-step.
  |
  | This control statement is optional.
  | This control statement is used if DYNALLOC=(,YES,) or
  | DYNALLOC=(,,YES) is specified.
  |
  | If you do not explicitly specify this control statement,
  | SPACEALLOC=NO will be used. In this case, an IDCAMS step
  | to allocate the DASD space is needed in separate
  | from the IPR step.
  |  ________________________________________________________
  | |                      _ NO  ___                         |
  | | >>__SPACEALLOC=_____|__YES  __|_____________________>< |
  | |________________________________________________________|
  |
  | If you specify SPACEALLOC=YES, each shadow data set can be
  | deleted and allocated within the IPR Driver job step.
  | You can specify the IDCAMS commands, otherwise IPR Driver
  | generates the commands automatically.
  |
  | - If you specify the HPSGAMSA DD statement which specifies
  | the data set containing the IDCAMS commands for the shadow
  | space allocation, IPR Driver passes the commands to
  | the IDCAMS program.
  |
  | Note: If the IDCAMS returns the non-zero condition code,
  |       IPR Driver terminates the reorganization processing.
  |       Specify 'SET MAXCC=0' after the DELETE command
  |       in case the used shadow data set does not exist.
  |
  | - If you do not specify the HPSGAMSA DD statement,
  | IPR Driver automatically generates the commands
  | to delete and allocate the DASD space for each shadow
  | data set based on the attributes of its original data set.
  | For the volume list and the SMS classes,see the notes below.
  | If DYNALLOC=(,,YES) and INDEXBLD=YES,NEW, the commands for
  | the shadow secondary index data set are included.
  | For HALDB, the commands for shadow ILDS are included
  | unless ILDSBLD=NO is specified.
  |
  | Notes:
  | 1. If a new shadow data set is allocated already or
  |    the used VSAM shadow data set with the REUSE option
  |    remains(*1), it is used without reallocating.
  |
  | 2. If the old data set with the shadow name remains(*1)
  |    and it is not a VSAM data set with the REUSE option,
  |    IPR Driver generates the commands to delete and
  |    allocate new shadow data set. The volume list and
  |    the SMS classes are derived from the old data set.
  |
  | 3. If the data set with the shadow name does not exist,
  |    IPR Driver generates the commands for allocation.
  |    - If the original data set is not SMS-managed,
  |      the volume list is derived from the original data set.
  |      You should take care whether there is enough available
  |      space on the volumes.
  |    - If the original data set is SMS-managed, the SMS classes
  |      are derived from the original data set and the volumes
  |      are assigned by SMS.
  |
  | *1: If DISPOLDDS=NEWSHADOW is specified, the input original
  |    data sets are renamed to the shadow names during the name
  |    swapping and the data sets with the shadow names remain.
  |
  | Restriction: IPR Driver does not generate the commands
  | automatically for the following data sets:
  |    - Shadow data set if its original is an OSAM multi-volume
  |      data set.
  |    - Output secondary index data set if INDEXBLD=YES,CURRENT
  |    - Output secondary index data set if INDEXBLD=YES,NEW and
  |      its original data set is not found.
  |
  | The result of this processing is shown in
  | "Result of Shadow Space Allocation report".
  ================================================================
  2.8 Reports and Statistics
  2.8.2 HPSOUT2 Data Set
  (This new report is added.)
  |2.8.2.X Result of Shadow Space Allocation report
  |
  |Figure xx shows the report that produced when SPACEALLOC=YES
  |is specified in the REORG control statement block.
  |The report contains the result of deleting and allocating
  |the DASD space for shadow data set.
  |
  | (Here, this figure omitted.)
  | Figure XX. Result of Shadow Space Allocation report
  ================================================================
   2.10 Examples
  |2.10.2.X  Using SPACEALLOC=YES control statement
  |
  | In this example, we assume that the database to be reorganized
  | is an HDAM database that has two secondary indexes but has
  | no logical relationship.
  |
  | The JCL statements shown in Figure XX does not include
  | the IDCAMS step for allocation of the shadow data sets.
  |
  | //REORG  EXEC PGM=HPSGMAIN,PARM='DBD=dbdname,DBRC=Y'
  | //STEPLIB  DD DISP=SHR,DSN=HPS.SHPSLMD
  | //         DD DISP=SHR,DSN=IIU.SIIULMOD
  | //         DD DISP=SHR,DSN=IMS.SDFSRESL
  | //IMS      DD DISP=SHR,DSN=IMS.DBDLIB
  | //HPSIN    DD *
  | (REORG)
  |     IMSCMD=YES
  |     INDEXBLD=YES
  |     SPACEALLOC=YES
  |     NAMESWAP=YES
  |     NAMESWAPFAIL=WTOR
  |     DISPOLDDS=NEWSHADOW
  | /*
  | Figure XX. Reorganizing a database that has secondary indexes
  |
  | Here, SPACEALLOC=YES is specified and the HPSGAMSA DD
  | statement is not specified. The commands to delete and
  | allocate the DASD spaces for all shadow data set, including
  | the shadow secondary index data sets, are generated
  | automatically and processed within this step.
  |
  | If the old data set with the shadow name remained,
  | the volume list same as one of the data set is specified
  | on the command to allocate the new shadow data set.
  |
  | DISPOLDDS=NEWSHADOW specifies to rename each input original
  | data set to the shadow name during name swapping.
  | The DASD space of the data set will be used for
  | the new shadow data set in the next reorganization job.
  ================================================================
  Appendix E. Messages and Codes
  E.3         Messages
  E.3.2       HPSG Messages
  ----------------------------------------------------------------
  |HPSG0112E DYNAMIC ALLOCATION FAILED FOR DDNAME=ddname RC=rc,
  |          RSN=xxxx,yyyy,zzzz
  |Explanation: An attempt of dynamic allocation with
  |a disposition of NEW for the data set that is identified
  |by the DD name ddname failed. The value rc is the return code
  |from SVC99,  xxxx is the S99ERROR contents, yyyy is the S99INFO
  |contents, and zzzz is the S99ERSN contents.
  |System Action: The IPR Driver task or the subtask that issued
  |the dynalloc request abends with a completion code of U0112,
  |and the IPR Driver job step ends with a return code of 16.
  |Programmer Response: Correct the error, and rerun the job.
  |If the error cannot be resolved, keep the dump produced
  |at the time of error and contact IBM Software Support.
  |Problem Determination: For the return code and the reason codes
  |from the DYNALLOC macro, see MVS Authorized Assembler
  |Services Guide.
  ----------------------------------------------------------------
  |HPSG0313I IDCAMS SERVICE ENDED WITH ERROR CC=cc (command)
  
   Explanation:  An error occurred when the program IDCAMS was
   called to perform command.
  |The decimal value is the condition code returned by IDCAMS.
   System Action: The IPR Driver continues processing.
   Programmer Response: Confirm the reason of the error shown
   in the following messages or in the appropriate report
   about the result of the IDCAMS commands.
  ----------------------------------------------------------------
  |HPSG0398I HPSGAMSA DATA SET IS USED FOR ALLOCATING SHADOW SPACE
  |Explanation: The IDCAMS commands specified in the HPSGAMSA data
  |set are used, to delete and define the shadow data sets,
  |by the IDCAMS program.
  |System Action: IPR Driver continues processing.
  |Programmer Response: None.
  ----------------------------------------------------------------
  |HPSG0399I AUTOMATIC SHADOW SPACE ALLOCATION IS ATTEMPTED
  |Explanation: The commands to delete and allocate the DASD space
  |for the shadow data sets are generated and issued automatically
  |The result of this processing is shown in the Result of Shadow
  |Space Allocation report.
  |System Action: IPR Driver continues processing.
  |Programmer Response: None.
  ----------------------------------------------------------------
  |HPSG0400E SHADOW SPACE FOR DDNAME=ddname CANNOT BE ALLOCATED
  |           (reason)
  |Explanation: IPR Driver does not support to generate
  |the command to delete and allocate the data set indicated by
  |ddname because one of the following reasons.
  | Reason            Meaning
  | MUL-VOL OSAM      The original is an OSAM multi-volume
  |                   data set.
  | NO MODEL S-IDX    This secondary index is original or
  |                   shadow whose original data set
  |                   is not found.
  |System Action: The IPR Driver ends with a return code of 8.
  |Programmer Response: Specify the IDCAMS commands in the
  |HPSGAMSA data set.
  ----------------------------------------------------------------
  |HPSG0402I DYNAMIC ALLOCATION COMPLETED SUCCESSFULLY
  |Explanation: The dynamic allocation for the OSAM shadow
  |data set shown in the Result of Shadow Space Allocation report
  |completed successfully. The shadow data set is cataloged.
  |System Action: The IPR Driver continues processing.
  |Programmer Response: None.
  ----------------------------------------------------------------
  |HPSG0452E ALLOCATING SHADOW SPACE FAILED
  |Explanation: An error occurred while allocating space
  |for the shadow data sets.
  |System Action: The IPR Driver ends with a return code of 8.
  |Programmer Response: See the messages that were issued from
  |the IDCAMS program, and identify the cause of the error.
  |The messages are printed in the Result of Shadow Space
  |Allocation report. If the IKJ56220I message is issued,
  |specify the DYNAMNBR parameter on the EXEC statement
  |for IPR Driver.
  ----------------------------------------------------------------
  ======================= End of Doc-Change ======================
  

APAR Information

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

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

  UK09660

Modules/Macros

• HPSGCM00 HPSGCM20 HPSGCSC1 HPSGGDLB HPSGGIOB
  HPSGGIO0 HPSGGRGB HPSGGRMB HPSGGRM0 HPSGICS  HPSGICSD HPSGICS0
  HPSGIDA  HPSGIDAD HPSGIDA0 HPSGLINK HPSGMSGT HPSGRA00 HPSGRA20
  HPSGRA50 HPSGRA60 HPSGRA70 HPSGRI00 HPSGRM00 HPSGRP00 HPSGRR00
  HPSGRS20 HPSGSTMT HPSGTM00 H25N310J
  

Fix information

• Fixed component name

  IMS PARALLEL RE

• Fixed component ID

  5655F7400

Applicable component levels

• R310 PSY UK09660

     UP05/12/03 P F512

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.