IBM Support

PI86492: ALLOW USER TO SPECIFY JOB CC IF DBRC RETURNS DSP00251 MESSAGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Allow User to specify Job CC if DBRC returns DSP00251 Message.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IMS High Performance Change *
    *                 Accumulation Utility Extended Batch mode.    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Final Job CC=20 when DBRC returns       *
    *                      DSP0025I causes some customers          *
    *                      problems.                               *
    *                                                              *
    *                      CA2PITCA DSN= does not support CA on    *
    *                      tape.                                   *
    *                                                              *
    *                      HPCA report headings show "Version 1"   *
    ****************************************************************
    * RECOMMENDATION: APPLY corrective maintenance for PI86492.    *
    ****************************************************************
    HPCA completes with CC=20 when a CA or PITCA is created with a
    Timestamp of an existing PITCA. This can happen when a CA or
    PITCA job is ran against a CA group with no unaccumulated
    changes since an existing PITCA. This results in DBRC returning
    a DSP0025I message during NOTIFY.CA processing. Since the
    NOTIFY.CA processing is after the CA/PITCA is created the data
    set created is retained although not registered in DBRC due to
    the DSP0025I, Duplicate Key issue. The user wants flexibility in
    specifying the final job CC and the CA/PITCA data set deleted if
    the DSP0025I condition is raised.
    
    When a PITCA job is ran with CA2PITCA DSN= to create a PITCA
    from an existing CA when there are no unaccumulated changes for
    a CA Group the job fails if the input CA is on a magnetic tape
    device.
    
    The HPCA report header shows "Version 1 Release 1".
    

Problem conclusion

Temporary fix

Comments

  • A new HPCSYSIN parameter is created, "DSP0025I RC = nnnn" where
    'nnnn' is any value between 0 and 4095.  New message HPC4043E is
    issued if the 'nnnn' value is not numeric or is outside the
    bounds of 0-4095:
    "HPC4043E DSP0025I RC : value must be numeric between 0 and
    4095."
    As an additional extended batch environment enhancement when the
    DSP0025I condition is detected HPCAPRO2 makes SVC 99 calls to
    determine and delete the CA/PITCA data set created but not
    registered with DBRC. New message HPC4042I is issued following
    the SVC 99 calls.
    "HPC4042I DBRC returned duplicate key message.
              CA DSN=TEMP.IRP.F1O1GRUP.D17237.T154115.CA DELETED."
    The "CA DSN=" will be "PITCA DSN=" for a PITCA job. The
    "DELETED" will be "RETAINED" if the SVC 99 is unable to delete
    the data set.
    In the event the data set name cannot be determined an
    additional message, HPC9998E is issued prior to the HPC4042I:
    HPC9998E Internal HPCA error.  Contact IBM Support.
    HPC4042I DBRC returned duplicate key message DSP0025I.
             CA DSN= *** CA OUTPUT MASTER DATA SET *** UNDETERMINED.
    The corresponding Sort Address Space (SAS) can then be searched
    for the string "CA OUTPUT MASTER" to determine the data set
    name.
    If the new parameter "DSP0025I RC = nnnn" is not specified the
    user will see no difference in what they have been seeing for
    the DSP0025I condition. The job will finish with CC=20 and the
    data set will be retained. Neither of the new messages will be
    issued.
    
    A new HPCSYSIN parameter "CA2PITCA UNIT=" is added to allow the
    user to specify the unit of the PITCA output when
    "CA2PITCA DSN=" is specified to create a PITCA from an existing
    CA when there are no unaccumulated changes for a CA group.  When
    the PITCA is created from an existing CA the output PITCA must
    be on the same device type as the input CA.  New message
    HPC4024W is issued if the input CA is not on DASD and CA2PITCA
    UNIT= is not specified or does not specify a unit of the same
    device type:
    HPC4024W PITCA processing failed for CAGROUP
    CA dataset is not on DASD and a valid CA2PITCA UNIT was not
    specified.
             Input CA dataset CADATASETNAME
    
    HPCAREPT is corrected to output "Version 2 Release 1".
    

APAR Information

  • APAR number

    PI86492

  • Reported component name

    IMS RCVR SOLUTN

  • Reported component ID

    5655V8600

  • Reported release

    210

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2017-08-28

  • Closed date

    2017-12-15

  • Last modified date

    2018-01-03

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

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

    UI52719

Modules/Macros

  • HPCACMM0 HPCACUM0 HPCADRIV HPCADRI1 HPCALST0
    HPCAMAIN HPCAPRO2 HPCARCAP HPCAREPT
    

Fix information

  • Fixed component name

    IMS RCVR SOLUTN

  • Fixed component ID

    5655V8600

Applicable component levels

  • R210 PSY UI52719

       UP17/12/19 P F712

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 January 2018