IBM Support

OA41986: WHEN RUNNING THE RESOURCE COMMAND, AUTO2 MAY HANG SHOWING A COMMAND OF PIPE1. 13/04/15 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer was seeing AUTO2 hanging and TASKUTIL showed a command
    of PIPE1.  A LIST AUTO2 showed the task was running MEMSTORE.
    MEMSTORE is set up to run on a timer basis and it issues the
    RESOURCE command from a PIPE named PIPE1. The resource command
    was running into a problem when subtracting the parked time from
    the total CPU time and coming up with a negative value. This
    may happen when a CPU is varied offline, the parked time is not
    reinitialized when the CPU is varied offline.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli NetView for z/OS users of the     *
    *                 RESOURCE command with PTF UA68294 installed. *
    ****************************************************************
    * PROBLEM DESCRIPTION: When running the RESOURCE command, the  *
    *                      task on which it is running may appear  *
    *                      to hang. Issuing the TASKUTIL command   *
    *                      will show that over time the 'hung'     *
    *                      task is using CPU time.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The RESOURCE command collects CPU timing data from system
    control blocks on initial entry, waits for about one second and
    then makes a second collection of CPU timing data. If between
    the first and second collections there is a change in the number
    or status of the CPUs from the first collection, the RESOURCE
    will cycle to make another set of collections. The RESOURCE
    command is not resetting one of its data accumulators which
    causes the RESOURCE command to cycle to make another set of CPU
    timing data collections. This cycling will occur once every
    second until the RESOURCE command is canceled or the task is
    terminated.
    

Problem conclusion

  • The RESOURCE command is being changed to reset the data
    collection variable which is causing the data collection
    cycling to occur.
    

Temporary fix

Comments

  • ž**** PE13/08/15 FIX IN ERROR. SEE APAR OA43111  FOR DESCRIPTION
    ž**** PE13/10/28 PTF IN ERROR. SEE APAR OA43545  FOR DESCRIPTION
    

APAR Information

  • APAR number

    OA41986

  • Reported component name

    NETVIEW FOR Z/O

  • Reported component ID

    5697ENV00

  • Reported release

    54B

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-15

  • Closed date

    2013-05-14

  • Last modified date

    2013-10-31

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

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

    UA69114

Modules/Macros

  •    DSIMONIT DSIRESRC DSITASKU
    

Fix information

  • Fixed component name

    NETVIEW FOR Z/O

  • Fixed component ID

    5697ENV00

Applicable component levels

  • R54B PSY UA69114

       UP13/05/21 P F305

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":"SSZJDU","label":"IBM Z NetView"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"54B","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
31 October 2013