IBM Support

PM46445: ENABLE DELETE/DEFINE OF DBDS WITHIN HP LOAD STEP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Enable delete/define of DBDS within HP Load step.
    

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: Enable to delete/define DBDS within HP  *
    *                      Load step.                              *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    This APAR introduces the DDEFPDS DD statement for specifying the
    IDCAMS command for deleting and defining database data sets
    during reload.
    
    DDEFPDS DD defines an optional data set that contains the IDCAMS
    commands for deleting and defining the database data sets to be
    processed by HP Load. IMS HP Load searches for the delete and
    define statements for each database data set in the member that
    has the same name as the database DD name.
    
    To use the new function, the followings are required:
    - All the libraries of STEPLIB must be authorized through
      Authorized Program Facility (APF).
    - Program HPSRRC00 must be specified on the EXEC statement.
    - Specify IDCAMS DELETE/DEFINE statements in a PDS member that
      has the same name as the database DD name, and specify the
      PDS in the DDEFPDS DD statement.
    
    When you DELETE/DEFINE HALDB DBDS, it is strongly recommended
    that the input unloaded data set is created by IMS HP Unload
    with the CHECKREC=YES option, and the unloaded data set must not
    be concatenated.
    Otherwise, you must specify the partitions to be loaded by
    using LPART statement to put the reorganized partitions on
    HP Load.
    

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:
    ================================================================
    
    2.2.2 JCL requirements
    :
    |DDEFPDS DD
    |  Defines an optional data set that contains the IDCAMS
    |  commands for deleting and defining the database data sets to
    |  be processed by HP Load. IMS HP Load searches for the delete
    |  and define statements for each database data set in the
    |  member that has the same name as the database DD name.
    |
    |  The member must contain only the delete and define
    |  statements.
    |
    |  Requirements:
    |  - To delete and define database data sets by specifying this
    |    DD statement, the load module library of STEPLIB must be
    |    authorized through Authorized Program Facility (APF).
    |  - Program HPSRRC00 must be specified on the EXEC statement.
    |
    |  - To delete and define HALDB data sets by specifying this DD
    |    statement, the input unloaded data set must be created by
    |    IMS HP Unload with the CHECKREC=YES option.
    |    The unloaded data set must not be concatenated.
    |
    |HPSRAMSO DD
    |  Defines the output data set for the Result of Database Data
    |  Set Allocation report. The data set can reside on a tape,
    |  a direct-access device, or it can be routed through the
    |  output stream. If the DD statement is not coded, it is
    |  dynamically allocated to the SYSOUT stream of the output
    |  class that is specified by the MSGCLASS parameter on the JOB
    |  statement.
    :
    2.2.3.18 PARTINIT control statement
    :    __________________________________________________________
       |                                                          |
       |                   _NO_________________                   |
       |                   |       _,PINITON_  |                  |
       |>>____PARTINIT=____|_YES__|__________|_|________________><|
    |  |                          |_,UNLOAD__|                    |
    |  |                          |_,LPART___|                    |
       |__________________________________________________________|
    :
    | LPART
    |   Specifies that initialization of a HALDB partition is to be
    |   done when the partitions to be loaded are specified by the
    |   LPART control statement.
    :
    2.2.3 Control statements
    
    | LPART control statement
    |
    | Specifies the HALDB partitions to load.
    | This control statement is optional.
    | This control statement does not have a default.
    | This control statement is not applicable to Load API.
    |    __________________________________________________________
    |   |                                                          |
    |   |>>____LPART=___ _*ALL_______________ __________________>< |
    |   |               |_partname__________________|              |
    |   |               |               _,1____     |              |
    |   |               |_(__partname__|_______|__)_|              |
    |   |               |              |_,nnnn_|    |              |
    |   |               |_partlist__________________|              |
    |   |__________________________________________________________|
    |
    | *ALL
    |    Specifies to load all the partitions.
    |
    |    Use this option only when you reorganize the entire
    |    database and the input unloaded data set contains data for
    |    all the partitions.
    |
    | partname
    |    Specifies the name of the partition to load, or the first
    |    partition of several sequential partitions to load.
    |
    | nnnn
    |    Specifies the number of sequential partitions to load.
    |    If this parameter is not specified, the default value of 1
    |    is assumed.
    |
    | Important: The processing order of the partitions is
    |  determined by the HALDB partition selection exit routine or
    |  the HALDB high key values. The processing order does not
    |  depend on the partition names. When you process multiple
    |  partitions, be aware of the order that they are processed.
    |
    | Example: The following statements have the same meaning:
    |               LPART=PARTA
    |               LPART=(PARTA)
    |               LPART=(PARTA,1)
    |
    | partlist
    |    Specifies a list of the partition names to load. The names
    |    must be separated by commas and enclosed in parentheses.
    |    You can specify up to 1001 names by using multiple
    |    statements as follows:
    |
    |                LPART=(part1,part2,part3,part4,part5)
    |                LPART=(part6,part7,part8,part9,part10)
    |
    |    You can specify non-sequential partitions.
    |
    |    The processing order of the partitions is determined by the
    |    HALDB partition selection exit routine or the HALDB high
    |    key values. The specified order in the list does not affect
    |    the processing order.
    |
    | Use the LPART statement to specify the partitions to load
    | when one or more of the following conditions are met:
    |    - When you create database data sets by using the DDEFPDS
    |      DD statement (IDCAMS commands) and the input unloaded
    |      data set was not created by IMS HP Unload with
    |      the CHECKREC=YES option.
    |    - When you create database data sets by using the DDEFPDS
    |      DD statement (IDCAMS commands) and if you have added new
    |      partitions after unloading the database.
    |    - When you have added new partitions after unloading the
    |      database, and you have one or more empty new partitions
    |      that you want to process with the PARTINIT=YES,LPART
    |      option (specifies to initialize the empty partition.)
    | To avoid errors, consider specifying this statement only one
    | or more of these conditions are met.
    |
    | Note: If the unload data sets contain segments for the
    | partitions that are not specified on the LPART control
    | statement, IMS HP Load issues an HPSR3768W message and
    | continues processing.
    
    | 2.2.4.3 HPSRAMSO data set
    |
    | This data set contains the Result of Database Data Set
    | Allocation report.
    |
    | The following figure shows an example of the Result of
    | Database Data Set Allocation report. This report contains the
    | results of the IDCAMS commands that were issued to allocate
    | database data sets.
    
    ========================================
    > 7.0 Troubleshooting
    >> 7.2 Messages and codes
    >>> 7.2.3 Messages
    >>>> 7.2.3.1 IMS HP Load messages
    
    | HPSR0130W EMPTY PART xxxxxxx IS NOT INITIALIZED BECAUSE NO
    | SPECIFICATION ON LPART
    |
    | Explanation: In the reload process, IMS HP Load found no
    | segments in the unloaded data set for the indicated partition.
    | Although PARTINIT=YES,LPART was specified, IMS HP Load did not
    | initialize the empty partition because the partition was not
    | specified on the LPART control statement.
    |
    | System action: IMS HP Load continues processing and sets a
    | return code of 4.
    |
    | User response: If the partition database data set is deleted
    | or defined before the reload, you must initialize it by
    | DFSUPNT0 before using it.
    
    | HPSR0131E PARTITION (partname) IS SPECIFIED MORE THAN ONCE ON
    | THE LPART STATEMENT
    |
    | Explanation: The indicated partition is specified more than
    | once on the LPART control statement. A partition name that is
    | already specified cannot be specified again.
    |
    | System action: Processing stops.
    | User response: Correct the parameter error, and rerun the job.
    | Problem determination: None.
    
    | HPSR0132E UNDEFINED PARTITION NAME (partname) IS SPECIFIED ON
    | THE LPART STATEMENT
    |
    | Explanation: The indicated partition name is specified on the
    | LPART control statement. However, the partition is not defined
    | in the DBRC.
    |
    | System action: Processing stops.
    | User response: Ensure that the partition (partname) is
    | specified correctly and that the partition is defined in the
    | DBRC. Correct the error and rerun the job.
    
    | HPSR3767E THE IDCAMS PROGRAM RETURNED AN ERROR
    |
    | Explanation: The IDCAMS program that was internally called by
    | IMS HP Load  returned an error return code. The detailed error
    | messages are shown in the Database Data Set Allocation report.
    |
    | System action: IMS HP Load issues a user 3767 abend.
    | User response: Check the IDCAMS messages in the report,
    | correct any errors, and rerun the job.
    | Problem determination: None.
    
    | HPSR3768W THE RELOADED PARTITION (partname) IS NOT SPECIFIED
    | ON THE LPART STATEMENT
    |
    | Explanation: The partitions to be reloaded are specified on
    | the LPART control statement. However, IMS HP Load reloaded the
    | indicated partition, which is not specified on the LPART
    | control statement.
    |
    | System action: IMS HP Load continues processing.
    | User response: Ensure that the LPART statement contains all
    | the partitions that you want to reload. If necessary, correct
    | the LPART statement and rerun the job.
    | Problem determination: None.
    
    | HPSR3769E PARTINIT=YES,LPART CANNOT BE SPECIFIED BECAUSE LPART
    | STATEMENT IS NOT SPECIFIED
    |
    | Explanation: PARTINIT=YES,LPART is specified; however, the
    | LPART control statement is not specified. To specify
    | PARTINIT=YES,LPART, you must also specify the LPART control
    | statement.
    |
    | System action: IMS HP Load issues a user 3769 abend.
    | User response: Correct the control statement, and rerun the
    | job.
    | Problem determination: None.
    
    | HPSR3777E DDEFPDS CANNOT BE USED BECAUSE AT LEAST ONE LIBRARY
    | IS NOT AUTHORIZED
    |
    | Explanation: Database data sets cannot be created by using the
    | DDEFPDS DD statement, because at least one library is not APF
    | authorized.
    |
    | System action: IMS HP Load issues a user 3777 abend.
    | User response: To use the IDCAMS commands with the DDEFPDS DD
    | statement, APF-authorize all the libraries that are in the
    | STEPLIB DD concatenation, and rerun the job.
    | Problem determination: None.
    

APAR Information

  • APAR number

    PM46445

  • Reported component name

    IMS HIGH PERF L

  • Reported component ID

    5655E0700

  • Reported release

    210

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function

  • Submitted date

    2011-08-25

  • Closed date

    2011-10-25

  • Last modified date

    2011-11-02

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

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

    UK73194

Modules/Macros

  • FABFDIAG FABFLINK HPSRAMS0 HPSRFCA0 HPSRHTBL
    HPSRMSGT HPSROPT  HPSROPTA HPSROPTS HPSRPC00 HPSRRLDA HPSRRLDB
    HPSRRLD2 HPSRRLD7 HPSRRLD8 HPSRRLD9 HPSRRRI0 HPSRRRI9 HPSRSTMT
    H1IM210J
    

Publications Referenced
SC18922204    

Fix information

  • Fixed component name

    IMS HIGH PERF L

  • Fixed component ID

    5655E0700

Applicable component levels

  • R210 PSY UK73194

       UP11/10/26 P F110

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.

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89F","label":"IMS HP Load"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 November 2011