IBM Support

OA44757: AOF618I NO VALID ACF MEMBER FOUND FOR XX - ACF TOKEN MISMATCH

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer performs the following steps:
    1. created new ACF (via build) without doing a Refresh
    2. recycled SA/Netview  (or IPL, Manager start hot)
    3. Message AOF618I NO VALID ACF MEMBER FOUND FOR xx - ACF TOKEN
    MISMATCH
       occurs.
    4. F PAM,refresh,* or INGAMS REFRESH CFG=*  resolves that issue
    5. adding a new APL into the Policy and run Build and refresh.
    Refresh complains about the new member with message
      AOF784I AUTOMATION CONTROL FILE MEMBER Z9RJAAPL IS EMPTY OR
    DOES NOT EXIST.
    yet the member is ok.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All SA z/OS V3R3 and V3R4 customers.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: When msgAOF618I has been issued to      *
    *                      indicate an ACF load failure, it is     *
    *                      possible that while wtor msgAOF602D is  *
    *                      waiting for a reply an attempt to       *
    *                      refresh the ACF will leave the ACF      *
    *                      allocated as a DSIPARM OPER-DS dataset. *
    *                      When this occurs then any new members   *
    *                      added to the ACF cannot be identified   *
    *                      and is normally followed by msgAOF784I  *
    *                      indicating which member.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The ACF should not be left in the DSIPARM concatenation as an
    OPER-DS dataset following a load failure.
    

Problem conclusion

  • Rexx routine AOFRANT3 has been changed to ensure the ACF is
    removed as an OPER-DS dataset from the DSIPARM concatenation
    following a load failure.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA44757

  • Reported component name

    SYSTEM AUTO Z/O

  • Reported component ID

    5698SA300

  • Reported release

    340

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-03-13

  • Closed date

    2014-03-25

  • Last modified date

    2014-04-02

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

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

    UA72945 UA72946

Modules/Macros

  • AOFRANT3
    

Fix information

  • Fixed component name

    SYSTEM AUTO Z/O

  • Fixed component ID

    5698SA300

Applicable component levels

  • R330 PSY UA72945

       UP14/03/27 P F403

  • R340 PSY UA72946

       UP14/03/27 P F403

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSWRCJ","label":"IBM Tivoli System Automation for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"340","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 April 2014