IBM Support

PM66108: DEBUGGER START COMMAND FOR MAS METHOD FAILS WITH MESSAGE MODB IS INACTIVE FOR THIS MAJOR OBJECT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Attempting to START an internal method via a MAS using DBG0 now
    fails with the following message:
    CMD=> START NQGR
    MODB is inactive for this major object.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V4R1M0 and V4R2M0 Users      *
    ****************************************************************
    * PROBLEM DESCRIPTION:    At the direction of CPSM Support,    *
    *                      you log on to one of your MASes and     *
    *                      enter the COD0 debugging transaction.   *
    *                      You then execute the START command      *
    *                      for a method in the MAS major object    *
    *                      (for example, NQGR).  You receive the   *
    *                      following message:                      *
    *                                                              *
    *                           MODB is inactive for this major    *
    *                              object.                         *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all MASes must be recycled to pick     *
    *                 up the new code.  Note that regions do not   *
    *                 need to be brought down and restarted at     *
    *                 the same time.                               *
    ****************************************************************
       To facilitate the START and ATTACH debugger commands, a
    dummy method, COD2, is inserted in the public method table
    for each CPSM major object.  The public method table for the
    MAS major object does not have any unused entries, so the
    COD2 method could not be defined in the MAS major object.
    As a result, message
    
         MODB is inactive for this major object.
    
    is issued when a START (in a MAS) or ATTACH (in a CMAS) command
    is entered for a method in the MAS major object.
    

Problem conclusion

  •    Module EYU9DBG1 (DBG1 - Debugging Transaction Main Program)
    was modified to attempt to add method COD2 to the private method
    table for a major object if no unused entries are found in the
    public table.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM66108

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    60M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-04

  • Closed date

    2012-06-05

  • Last modified date

    2012-07-02

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

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

    UK79344 UK79345

Modules/Macros

  •    EYU0DATC EYU0DLOD EYU9DBG1
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R60M PSY UK79344

       UP12/06/18 P F206

  • R70M PSY UK79345

       UP12/06/18 P F206

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":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"4.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 July 2012