IBM Support

PM07578: CREATE GDG BASE FOR DFSURWF1.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Create GDG base if DFSURWF1 is defined as a generation data set
    and the base does not exist.
    

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: HP Load creates GDG base for DSFURWF1   *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    This APAR enables HP Load to create a GDG base if DFSURWF1 is
    defined as a generation data set and the base does not exist.
    To use the new function, you need the following JCL changes:
     - Specify GDGBASE=YES and WF1DSN=GDG_base_name.&GDG in the
       FRRIN DD (GDG_base_name is used as a GDG base entry name)
     - Omit the DFSURWF1 DD specification
     - If necessary, specify GDGLIMIT, WF1SPACE, WF1UNIT and WF1VOL
       in the FRRIN DD
    

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           Operating instructions
    2.2.2         JCL requirements
       :
    DFSURWF1 DD
    :
    This DD statement is necessary if at least one of the following
    conditions are met:
    - The database is HDAM, HIDAM, or HISAM and it has logical
      relationship.
    - The database has a secondary index and INDEXBLD=NO is
      specified for the IPR Driver, but the HPSRSIDX DD
      statement is not coded.
    In these cases, if WF1REC=NO is specified, you can omit the DD
    statement. In other cases, the DD statement is not necessary.
    
    |  Notes:
    |  1. If WF1REC=NO is specified, you can omit this DD statement.
    |     If the preceding condition is not met, this DD statement
    |     is not required.
    |  2. If you omit the DFSURWF1 DD statement and specify the
    |     WF1DSN statement, IMS HP Load allocates the DFSURWF1 data
    |     set dynamically. You can specify the attributes of the
    |     data set by using WF1SPACE, WF1UNIT, and WF1VOLUME
    |     statements.
    
    | 2.2.3.xx GDGBASE control statement
    |  Specifies whether to create a generation data group (GDG)
    |  base entry when a GDG base entry does not exist.
    |  This control statement is optional. If you do not explicitly
    |  specify this control statement, GDGBASE=NO is used.
        ___________________________________________________________
    | |                                                            |
    | |                 _NO___                                     |
    | | >>__GDGBASE=__|_YES__|__________________________________>< |
    | |____________________________________________________________|
    
    |  YES
    |      If there is no GDG base entry for the generation data set
    |      that is to be created and if the generation data set is
    |      to be allocated dynamically, a GDG base entry is created.
    |  NO
    |      GDG base entry is not created.
    |  Note:
    |    The default value of the GDGBASE control statement can be
    |    changed. For details, see "Setting installation default
    |    option" in topic 6.1.
    
    | 2.2.3.xx GDGLIMIT control statement
    |  Specifies the maximum number of generation data sets (GDS)
    |  that can be associated with the generation data group (GDG)
    |  that is to be created.
    |  This specification is valid only when GDGBASE=YES is
    |  specified.
    |  This control statement is optional. If you do not explicitly
    |  specify this control statement, GDGLIMIT=10 is used.
        ___________________________________________________________
    |  |                                                           |
    |  |                 _10__                                     |
    |  | >>__GDGLIMIT=__|_nnn_|_________________________________>< |
    |  |___________________________________________________________|
    
    |  nnn
    |      Specifies a left-justified decimal number from 1 to 255.
    |  Note:
    |    The default value of the GDGLIMIT control statement can be
    |    changed. For details, see "Setting installation default
    |    option" in topic 6.1.
    
    | 2.2.3.xx WF1DSN control statement
    |  Specifies the data set name for the DFSURWF1 data set that is
    |  to be dynamically allocated. This control statement is
    |  optional and does not have a default.
    |   ___________________________________________________________
    |  |                                                           |
    |  | >>__WF1DSN=_ _data_set_name______ _____________________>< |
    |  |             |_GDG_base_name.&GDG_|                        |
    |  |___________________________________________________________|
    
    |  data_set_name
    |      Specifies the data set name for the DFSURWF1 data set.
    |      The name is a 1-44 alphanumeric or national characters
    |      ($,#,@).
    |  GDG_base_name.&GDG
    |      Specifies to create a DFSURWF1 data set as a generation
    |      data set. &GDG must be specified in the last position in
    |      the pattern.
    |      GDG_base_name is used as a GDG base entry name. If the
    |      base entry does not exist and you specify GDGBASE=YES,
    |      a new GDG base entry is created.
    |      The data set name generated must be a 1-44 alphanumeric
    |      or national characters ($,#,@).
    |  Note:
    |    If you specify the DFSURWF1 DD statement, this control
    |    statement is ignored.
    
    | 2.2.3.xx WF1SPACE control statement
    |  Specifies the space parameter for the DFSURWF1 data set that
    |  is to be dynamically allocated.
    |  This specification is valid only when WF1DSN is specified.
    |  If you do not explicitly specify this control statement, IMS
    |  HP Load calculates the size on the basis of the allocation
    |  size of database data set.
    |  This control statement is optional and does not have a
    |  default.
    |  ____________________________________________________________
    | |                                                            |
    | | >>__WF1SPACE=_ _CYL_ _,primary_alloc,secondary_alloc____>< |
    | |               |_TRK_|                                      |
    | |____________________________________________________________|
    
    |  CYL
    |      Specifies that space is to be allocated in cylinders.
    |  TRK
    |      Specifies that space is to be allocated in tracks.
    |  primary_alloc
    |      Specifies the primary space quantity. It must be a
    |      left-justified decimal number from 1 to 9999.
    |  secondary_alloc
    |      Specifies the secondary space quantity. It must be a
    |      left-justified decimal number from 1 to 9999.
    |  Note:
    |    If you specify the DFSURWF1 DD statement, this control
    |    statement is ignored.
    
    | 2.2.3.xx WF1UNIT control statement
    |  Specifies the device for the DFSURWF1 data set that is to be
    |  dynamically allocated.
    |  This specification is valid only when WF1DSN control
    |  statement is specified.
    |  This control statement is optional. If you do not explicitly
    |  specify this control statement, WF1UNIT=SYSALLDA is used.
    |  ____________________________________________________________
    | |                                                            |
    | |                _SYSALLDA__                                 |
    | | >>__WF1UNIT=__|_unitname__|_____________________________>< |
    | |____________________________________________________________|
    
    |  unitname
    |      Specifies the device type or the device group name for
    |      the DFSURWF1 data set.
    |  Note:
    |    If you specify the DFSURWF1 DD statement, this control
    |    statement is ignored.
    
    | 2.2.3.xx WF1VOL control statement
    |  Specifies one or more volume names for DFSURWF1 data set that
    |  is to be dynamically allocated.
    |  This specification is valid only when WF1DSN control
    |  statement is specified.
    |  This control statement is optional and does not have a
    |  default.
    |  ____________________________________________________________
    | |                                                            |
    | |                   <_,_____________                         |
    | | >>__WF1VOL=_ _(___ _volume_name_ _|__)_ ________________>< |
    | |             |     |_*___________|      |                   |
    | |             |_ _volume_name_ __________|                   |
    | |               |_*___________|                              |
    | |____________________________________________________________|
    
    |  volume_name
    |      Specifies the volume names. You can make a nonspecific
    |      volume request by specifying an asterisk (*).
    |      Two or more volume names must be separated by commas and
    |      enclosed in parentheses. For example,
    |      WF1VOL=(VOLSR1,VOLSR2).
    |      You can specify up to 5 volume names.
    |  Note:
    |    If you specify the DFSURWF1 DD statement, this control
    |    statement is ignored.
    
    6.1    Setting installation default option
    6.1.4  How to code HPSROPT macro statements
       :
       ____________________________________________________________
      |                                                            |
      | RELOAD:                                                    |
      |           <_,___________________________________________   |
      | |_RELOAD__ ____________________________________________ |_||
      |           |_ ________________________________________ _|   |
      |           | |             _(__YES,WARN__)__________  | |   |
      |           | |            |             _WARN__     | | |   |
      |           | |_CHKTRAIL=__|_(__YES__,__|_ERROR_|__)_|_| |   |
      |           |              |_NO______________________|   |   |
      |           |            _NO______________________       |   |
      |           |           |             _ABEND_     |      |   |
      |           |_CHKUPDT=__|_(__YES__,__|_WARN__|__)_|______|   |
    | |           |_ ____________________ _____________________|   |
    | |           | |            _NO___  |                     |   |
    | |           | |_GDGBASE=__|_YES__|_|                     |   |
    | |           |_ __________________________________________|   |
    | |           | |             _10__  |                     |   |
    | |           | |_GDGLIMIT=__|_nnn_|_|                     |   |
      |           |_ ________________ _________________________|   |
      |           | |_HPIO=__ _NO__ _|                         |   |
      |           |          |_YES_|                           |   |
        :
      |____________________________________________________________|
       :
      The option keywords supported for the RELOAD parameter are as
      follows:
    |   - CHKTRAIL, CHKUPDT, GDGBASE, GDGLIMIT, HPIO, ILDSBLD,
          ITKBLOAD, ITKBSRVR, OADSPR, PARTINIT, and WF1REC.
    
    7.2.3         Messages
    7.2.3.1       IMS HP Load messages
    
    |  HPSR0039I GDG BASE ENTRY WAS CREATED
    
    |  Explanation: GDGBASE=YES was specified, and GDG base entry
    |  was created by the IDCAMS command.
    |  System Action: Processing continues.
    |  User Response: None.
    |  Problem Determination: None.
    
    |  HPSR0041I GDG BASE ENTRY WAS NOT CREATED BECAUSE GDG BASE
    |  ENTRY ALREADY EXISTS
    
    |  Explanation: GDGBASE=YES was specified. However, GDG base
    |  entry was not created because a GDG base entry with the name
    |  that was specified in WF1DSN= already exists.
    |  System Action: Processing continues.
    |  User Response: None.
    |  Problem Determination: None.
    
    |  HPSR0043I WF1DSN IS IGNORED BECAUSE MULTIPLE DATABASES WERE
    |  PROCESSED
    
    |  Explanation: The specification of the WF1DSN statement was
    |  ignored because multiple PCBs are specified in the PSB and a
    |  logical relationship or a secondary index is defined in those
    |  PCBs. In this case, Load API cannot allocate a DFSURWF1 data
    |  set dynamically.
    |  System Action: Processing continues.
    |  User Response: None.
    |  Problem Determination: None.
    
    |  HPSR0044W WF1DSN SPECIFICATION IS IGNORED BECAUSE DFSURWF1 DD
    |  IS SPECIFIED
    
    |  Explanation: The specification of the WF1DSN statement was
    |  ignored because DFSURWF1 DD statement is specified in the JCL
    |  stream.
    |  System Action: Processing continues. IMS HP Load uses the
    |  data set that is specified in the DFSURWF1 DD statement.
    |  User Response: If you want to use the data set that is
    |  specified in the WF1DSN statement, remove the DFSURWF1 DD
    |  statement and rerun the job.
    |  Problem Determination: None.
    
    |  HPSR3765E IDCAMS COULD NOT DEFINE A GDG
    
    |  Explanation: IDCAMS failed in defining a GDG. The error
    |  messages that were issued by IDCAMS are shown in the GDG Base
    |  Information report.
    |  System Action: IMS HP Load issues a user 3765 abend.
    |  User Response: Check the IDCAMS messages, correct any errors,
    |  and rerun the job.
    |  Problem Determination: None.
    
    |  HPSR3766E GDG BASE ENTRY FOR DFSURWF1 WAS NOT FOUND
    |  (R15=register15, R0=register0)
    
    |  Explanation: IMS HP Load tried to create a generation data
    |  set. However, the GDG base entry was not found by the LOCATE
    |  macro. register15 and register0 show the returned information
    |  from the LOCATE macro.
    |  System Action: IMS HP Load issues a user 3766 abend.
    |  User Response: Confirm the specification of WF1DSN and
    |  GDGBASE. If you specify a symbolic parameter &GDG in the
    |  WF1DSN statement and want to create a DFSURWF1 data set
    |  together with a new generation data set group, specify
    |  GDGBASE=YES. Otherwise, contact IBM Software Support.
    |  Problem Determination: None.
    

APAR Information

  • APAR number

    PM07578

  • Reported component name

    IMS HIGH PERF L

  • Reported component ID

    5655E0700

  • Reported release

    210

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-12

  • Closed date

    2010-03-31

  • Last modified date

    2010-04-03

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

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

    UK55727

Modules/Macros

  • FABFLINK HPSCIOSA HPSCOPTD HPSRAP0A HPSRAP0B
    HPSRAP00 HPSRAP07 HPSRAP08 HPSRAP09 HPSRAS00 HPSRDSCT HPSRDYF1
    HPSRFCA0 HPSRGDGB HPSRHDLA HPSRHDLB HPSRHDLD HPSRHDL7 HPSRHDL8
    HPSRHDL9 HPSRHSLA HPSRHSLB HPSRHSLD HPSRHSL7 HPSRHSL8 HPSRHSL9
    HPSRHTBL HPSRIDA  HPSRIDAD HPSRIDA0 HPSRIOSA HPSRLGSA HPSRLGSB
    HPSRLGSC HPSRLGS7 HPSRLGS8 HPSRLGS9 HPSRMSGT HPSROPT  HPSROPTA
    HPSROPTS HPSRRRIN 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 UK55727

       UP10/04/01 P F003

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:
03 April 2010