PM01857: PSSR SUPPORTS A HISAM DATABASE.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Enable use of a HISAM unloaded data set as input to PSSR
  without regenerating DBD.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM IMS High Performance Load   *
  *                 for z/OS Version 2 Release 1 (FMID=H1IM210). *
  ****************************************************************
  * PROBLEM DESCRIPTION: PSSR supports a HISAM database.         *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR enables the use of a (S)HISAM unloaded data set as
  input to PSSR without regenerating DBD.
  

Problem conclusion

Temporary fix

Comments

• ========================
  = Documentation Change =
  ========================
  IMS High Performance Load for z/OS Version 2 Release 1 User's
  Guide SC18-9222-04 ( SC18922204 ) should be changed as follows:
  ================================================================
  1.0 General information
  1.1 IMS HP Load overview
          :
    Physical Sequence Sort for Reload sorts an unloaded database
    data set that is produced for an HDAM database to reduce the
    elapsed time required to reload the database. It also sorts an
    unloaded database data set for
  | an HDAM, a PHDAM, a HIDAM, a PHIDAM, a HISAM, or a SHISAM
  | database.
  
  ----------------------------------------------------------------
  3.0   Physical Sequence Sort for Reload
  3.1   Introduction
  3.1.1 Program functions
  
    PSSR sorts an unloaded database data set created from
  | an HDAM, a PHDAM, a HIDAM, a PHIDAM, a HISAM, or a SHISAM
  | database.
  
  ----------------------------------------------------------------
  3.1.2 Typical benefits
    Typical benefits of using PSSR are the following:
     - Reducing elapsed time to reload a database
       - Converting DB organization to HDAM-type
         - Non-HDAM to HDAM
         - Non-PHDAM to PHDAM
       - Converting DB organization to HIDAM-type
         - Non-HIDAM to HIDAM
         - Non-PHIDAM to PHIDAM
  |    - Converting DB organization to HISAM-type
  |      - Non-HISAM to HISAM
  |      - Non-SHISAM to SHISAM
       - Changing HDAM randomization parameters (HDAM/PHDAM)
  
  ----------------------------------------------------------------
  3.1.4  Restrictions
  
  DELETE:
  | PSSR can process only HDAM, HIDAM, PHDAM, or PHIDAM. But, PSSR
  |  can accept as its input, an unloaded file that is created by
  | the IMS HD Reorganization Unload utility from HDAM, HIDAM,
  | HISAM, PHDAM, or PHIDAM. To do so, you must regenerate the DBD
  |  as HDAM, HIDAM, PHDAM, or PHIDAM DBD before running PSSR.
  DELETE:
  
  | PSSR can process HDAM, HIDAM, HISAM, SHISAM, PHDAM, or PHIDAM.
  
  ----------------------------------------------------------------
  3.2.4.1   SYSIN data set (Used by FABSPSSR)
  3.2.4.1.2 Format
       :
  | For a HIDAM, a HISAM, or a SHISAM database, specify a SYSIN
    data set as shown in Figure 23.
  
  ----------------------------------------------------------------
  3.2.4.1.3 SORT control statement
          :
     - The FIELDS=(5,20,BI,A) operand is required for an HDAM
       database. For
  |    a HIDAM, a HISAM, or a SHISAM, the FIELDS operand must be
  
           FIELDS=(5,XXX,BI,A)
           (XXX=KEYLEN + 10)
  
  ----------------------------------------------------------------
  3.2.4.4   CTL data set (Used by FABSPSSR)
  3.2.4.4.3 Record format
       :
    Position Description
       :
    The parameters at positions 34 and 51 are not effective for a
  | HIDAM, a HISAM, or a SHISAM database.
  
  ----------------------------------------------------------------
  3.2.4.5 SORTCNTL data set (Used by FABSPSSI)
  3.2.4.5.1 Function
     :
   If you do not specify SORTCNTL, PSSR sets default values for
   DFSORT:
     ____________________________________________________________
    |                                                            |
    |   HDAM:                                                    |
    |     :                                                      |
    |                                                            |
  | |   HIDAM, HISAM, or SHISAM:                                 |
    |                                                            |
  | |     SORT FIELDS=(5,nnn,BI,A),FILSZ=E9400000                |
    |                                                            |
    |     MODS E15=(FABSRT15,50000,,N),E35=(FABSRT35,50000,,N)   |
    |                                                            |
    |                                                            |
    |   PHDAM:                                                   |
    |      :                                                     |
  
  ----------------------------------------------------------------
  3.2.5   Output
  3.2.5.1 SORTOUT data set for non-HALDB processing
  3.2.5.1.1 Function
       :
    This data set contains most or all of the database segments,
    sorted in the physical (hierarchical) sequence for HDAM, or
  | sorted into root key sequence for HIDAM, HISAM, or SHISAM.
  
  ----------------------------------------------------------------
  3.2.5.1.2 Format
        :
    ALL database records are placed in the SORTOUT data set for
  | HIDAM, HISAM, or SHISAM processing.
    SORTOUT is a sequential data set that can be on tape or disk.
  
  ----------------------------------------------------------------
  3.2.5.2  SORTOUT2 data set for non-HALDB processing
  3.2.5.2.1 Function
         :
  |  If the database is a HIDAM, HISAM, or SHISAM database,no
     data is contained.
  
  ----------------------------------------------------------------
  3.2.5.11   PR8 data set
  3.2.5.11.3 Control Card Format report
  
    This report (see Figure 29) describes the fields on the
    records in the CTL data set. It is printed for the convenience
    of the user.
        :
       *** LEADING ZEROS REQUIRED IN ALL NUMERIC FIELDS
  |    *** *1 : NOT APPLICABLE FOR (P)HIDAM OR (S)HISAM
       *** *2 : NOT APPLICABLE FOR PHIDAM
       >>> DB STATEMENT **** SECOND LINE ****
       COLUMNS 11-18: PARTITION SELECTION EXIT NAME
  
  ----------------------------------------------------------------
  APPENDIX1.3.3   Messages
  APPENDIX1.3.3.2 PSSR messages
  
  | FABS3514E AN INCORRECT SORT EXIT FOR THE DATABASE ORGANIZATION
  
  | Explanation: The specified name of a sort exit module is not
  | applicable for the database organization, or the database
  | organization is not supported by PSSR.
    System Action: PSSR issues a user 3514 abend.
    Programmer Response: Correct the error and rerun the job.
  | Problem Determination: Ensure that database organization is
  | appropriate and whether the sort exit module that is specified
  | in the SYSIN / SORTCTL DD is applicable for the database
  | organization.
  ======================= 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:

  UK52914

Modules/Macros

•    FABSCOMD FABSCOM0 FABSHDTS FABSMAIN FABSRT15
  FABSSC01 FABUCHG
  

Fix information

• Fixed component name

  IMS HIGH PERF L

• Fixed component ID

  5655E0700

Applicable component levels

• R210 PSY UK52914

     UP09/12/17 P F912

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.