PK58598: IPR DRIVER SPACEALLOC SUPPORTS SMS MULTI-VOLUME OSAM

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• IPR Driver does not allocate the shadow data set automatically
  for multi-volume OSAM data set:
  HPSG0400E SHADOW SPACE FOR DDNAME=XXXXXXXX CANNOT BE ALLOCATED
  (MUL-VOL OSAM)
  This APAR removes this restriction if the volumes are
  SMS-managed.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IPR Driver of IMS Parallel      *
  *                 Reorganization for z/OS Version 3 Release 2  *
  *                 (FMID=H25N320)                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: IPR Driver does not allocate the        *
  *                      shadow data set automatically           *
  *                      for multi-volume OSAM data set.         *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR provides the following enhancements of the SPACEALLOC
  of IPR Driver to delete and allocate the DASD space
  for each shadow data set within the IPR job step:
  
  1. If the volumes are SMS-managed, the restriction
     for the multi-volume OSAM data set is removed.
  2. If the OSAM original data set is defined as a large format
     data set in z/OS V1R7 or later, the parameter DSNTYPE=LARGE
     is added to the SVC 99 new allocation command.
  3. If NAMESWAP=YES is specified, the command to delete the old
     temporary data set with suffix '.T' is generated
     automatically.
  4. If a multi-volume OSAM shadow data set is not allocated
     correctly, the HPSG0408I message is issued.
  

Problem conclusion

Temporary fix

Comments

• ========================
  = Documentation Change =
  ========================
  IBM IMS Parallel Reorganization for z/OS User's Guide
  (SC18-9228-03) should be changed as follows:
  ================================================================
   2.0 IMS Parallel Reorganization Driver
   2.7 Control statements
   2.7.8 Description of control statements
          for Reorganization Manager
   2.7.8.30 SPACEALLOC control statement
  
  
   The SPACEALLOC control statement 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 in the HPSGAMSA data set,
   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
   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.
  
  |Automatic shadow space allocation
  
   If you do not specify the HPSGAMSA DD statement, IPR Driver
   automatically attempts 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 sets are
   included. For HALDB, the commands for the shadow ILDS
   are included unless ILDSBLD=NO is specified.
  |If NAMESWAP=YES, the commands to delete the old temporary
  |data set with suffix '.T' are added.
  
   Notes:
    1. If a new shadow data set is already allocated or the VSAM
    shadow data set with the REUSE option remains (4),
    it is used without reallocating.
  | 2. The primary space quantity for an OSAM shadow data set
  | is determined by adding up the space allocated in the first
  | three extents of the original data set. Therefore, the space
  | allocated for the shadow data set will generally not match
  | the space that was specified for the original data set.
  
  D If the old data set with the shadow name remains (4) and
  D it is not a VSAM data set with the REUSE option, IPR Driver
  D generates the commands to delete and allocate new space.
  D The volume list and the SMS classes are derived
  D from the old data set.
  
  D If the data set with the shadow name does not exist,
  D IPR Driver generates the commands for allocation.
  
   If the original data set is not SMS-managed
  |and the old data set with the shadow name remains (4),
  |the volume list is derived from the old shadow data set.
  |If the old shadow data set is not found, 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 number of
  |volumes and the SMS classes are derived from the original
   data set and the volumes are assigned by SMS.
  
   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 and the volumes are not SMS-managed.
  |   If the volumes are SMS-managed, IPR Driver attempts to
  |   allocate the shadow data set. The SMS storage class
  |   must have the guaranteed space attribute.
    - 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" in topic 2.8.2.5.
  
  (4) 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.
  
  ---------------------------------------------------------------
   2.8.2.5 Result of Shadow Space Allocation report
  
   Figure 30 shows the report that is 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.
  
  (In Figure 30, the command:
    "DELETE (TESTDS.OIFC3338.DDHD0011.T) PURGE CLUSTER"
   and its response from the IDCAMS program will be added.)
  ---------------------------------------------------------------
   10.0 Messages and codes
   10.3 Messages
   10.3.2 HPSG messages
  
  (The HPSG0400E message is modified and the HPS0408I message
  added.)
  
  ---------------------------------------------------------------
    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
  | NON-SMS MUL-VOL OSAM
  |   The original is a multi-volume OSAM data set
  |   on non-SMS managed volumes.
    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 for all shadow
   data sets in the HPSGAMSA data set.
  ---------------------------------------------------------------
  | HPSG0408I INCORRECT MUL-VOL OSAM DATA SET:DSN=dsname
  |
  | Explanation A primary extent should be allocated on each
  | volume of multi-volume OSAM data set, however, it was not
  | allocated on the second volume of the data set dsname.
  | System action: The IPR Driver continues its processing.
  | Programmer Response:  If the volumes are SMS-managed,
  | the SMS storage class should have the guaranteed space
  | attribute. Otherwise, the data set should be allocated
  | as described in IMS Administration Guide: Database Manager.
  ---------------------------------------------------------------
  ================= End of Documentation Change ==================
  

APAR Information

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

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

  UK33229

Modules/Macros

• HPSGCM00 HPSGGDLB HPSGGIOB HPSGGIO0 HPSGGRGB
  HPSGIDA  HPSGIDAD HPSGIDA0 HPSGMPE0 HPSGMSGT HPSGODA0 HPSGRA00
  HPSGRA40 HPSGRA50 HPSGRA60 HPSGRE00 HPSGRS00 HPSGRX00 HPSGTJ00
  HPSGTM00 HPSGTU10
  

Fix information

• Fixed component name

  IMS PARALLEL RE

• Fixed component ID

  5655F7400

Applicable component levels

• R320 PSY UK33229

     UP08/01/30 P F801

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.