IBM Support

OA47182: MONITOR ROUTINE NONE AND INTERVAL NONE IS NOT WORKING AS EXPECTED.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Defining a Monitor Routine other than NONE and Monitor Interval
    NONE works fine to switch off the monitoring of an APL, but
    Monitor Routine NONE and Interval NONE is not working as
    expected.
    Client had a TYPE NONMVS APL connected to class defined with,
    Job Type . . . . . . . . . NONMVS
    Monitor Routine  . . . . . TESTMON
    Monitor Interval . . . . . 00:10
    then connects an APL TYPE NONMVS to this class, but this APL
    does not require a Monitor Routine.
    Monitor Routine  . . . . . NONE
    Monitor Interval . . . . . NONE
    A build and refresh is done and DISPINFO still show that the
    Monitor interval is still in place.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All SA z/OS V3R4 and V3R5 customers using    *
    *                 the Customization Dialogs.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When specifying NONE for fields         *
    *                      'Monitor Routine' and 'Monitor          *
    *                      Interval' on Application Information    *
    *                      panel AOFGDYNA, the value NONE for      *
    *                      'Monitor Interval' may be ignored.      *
    *                      This occurs when the application is     *
    *                      linked to a class where an Interval     *
    *                      with a time value was specified.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A value of NONE in field 'Monitor Interval' can be ignored.
    This will then result in NetView timer settings trying
    to initiate the monitor cycles.
    
    Note: When you have this problem for an application you must
    perform a dummy change for this application, perform a build,
    followed by a refresh of the configuration file.
    

Problem conclusion

  • Skeleton AOFSAPL has been modified to default the 'Monitor
    Interval' to NONE when 'Monitor Routine' NONE is specified.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA47182

  • Reported component name

    SYSTEM AUTO Z/O

  • Reported component ID

    5698SA300

  • Reported release

    350

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-02-24

  • Closed date

    2015-02-27

  • Last modified date

    2015-04-02

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

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

    UA76452 UA76453

Modules/Macros

  • AOFSAPL
    

Fix information

  • Fixed component name

    SYSTEM AUTO Z/O

  • Fixed component ID

    5698SA300

Applicable component levels

  • R340 PSY UA76452

       UP15/03/03 P F503

  • R350 PSY UA76453

       UP15/03/03 P F503

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":"350","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 April 2015