IBM Support

OA49173: ANTPC2 RC28 RSN189C18A4 RSN18A4 ANTUPET_NO_MPET_DATA_PTR ANTM6999E RC6307

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • Hundreds of ANTPC2 RC28 RSN189C18A4 events are recorded in
    LOGREC due to a PET table initialization failure ( RC6307 ).
    Every subsequent attempt to access data areas in the PET table
    are going to fail because the mpetp_in_head_ptr is zero,
    until another restart of ANTMAIN is done.
    
    Add. keywords:
    ANTPC2 RC28 RSN189C18A4 rsn18A4 antupet_no_mpet_data_ptr
    
    DUMP TITLE:
      COMPON=SDM DIAGNOSTIC DUMP,COMPID=DF117,ISSUER=ANTPC2,
      JOBNAME=jjjjjjjj,RC=00000028,RSN=189C18A4
    
    SYMPTOM RECORD ==> PRIMARY SYMPTOM STRING:
    
      SYMPTOM            SYMPTOM DATA
      ---------------    -------------
      PIDS/5695DF117     5695DF117
      RIDS/ANTPC2        ANTPC2     ==> RC 00000028 RSN 189C18A4
    
    ANTM6999E PET TABLE INITIALIZATION FAILED, RC=6307 RC6307
    

Local fix

  • Restart of ANTMAIN
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Concurrent Copy.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: If message ANTM6999E with RC=6307 is    *
    *                      observed, Concurrent Copy will fail     *
    *                      with SDM DIAGNOSTIC DUMP containing     *
    *                      RC=00000028,RSN=189C18A4                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A documentation change will been made.
    
    The following updates will be reflected in a future revision
    of z/OS MVS System Messages, Volume 1(ABA-AOM)(SA38-0668):
    
    In the ADR Messages section under ADR735W, reason code 10,
    the following information will be amended:
    
    If DSS message ADR735W is issued with reason code 10,
    indicating that the system data mover is not available, and
    there is a previous SDM message ANTM6999E with RC=6307, then
    any storage shortages that may exist must be resolved and the
    ANTMAIN address space must be refreshed (Cancel of the ANTMAIN
    address space).
    If the ANTM6999E/RC=6307 continues to be observed, ensure there
    are no existing storage shortages and then refresh ANTMAIN
    again.
    
    
    In the ANT Messages section under message ANTM6999E, the
    following will be added to the end of the System Programmer
    Response section:
    
    System programmer response: If return_code is 6307,
    there might be insufficient ECSA available to allocate the
    table. Either increase the system ECSA, or reduce the size of
    the table. See z/OS DFSMS Advanced Copy Services for
    instructions on modifying PET table size. After all system ECSA
    issues have been resolved, the ANTMAIN address space must be
    refreshed (by executing a CANCEL command to ANTMAIN).  If the
    return_code 6307 continues to be observed and all storage
    issues have been resolved report the problem to the IBM Support
    Center. For other errors, search problem reporting databases
    for a fix for the problem. If no fix exists, report the problem
    to the IBM Support Center.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA49173

  • Reported component name

    SYSTEM DATA MOV

  • Reported component ID

    5695DF117

  • Reported release

    210

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-10-23

  • Closed date

    2016-05-31

  • Last modified date

    2016-05-31

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

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

Publications Referenced
SA380668XX    

Fix information

Applicable component levels

[{"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":"210","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
31 May 2016