OA46497: AUTOMATION GUIDE SHOULD BE UPDATED FOR TWO DIFFERENT REASONS

APAR status

• Closed as documentation error.

Error description

• The NetView Automation Guide should be updated in 2 ways:
  1. Should replace SUP(ALL) with SUP(YES) for the following
     sections in the NetView Automation Guide:
     - 5.1.1.1.2
     - 7.10.1.1 - may just need a pointer to the Init&Tuning ref
     - 7.10.1.2 - same as 7.10.1.1
     - APPENDIX1.4.1.2 - change "messages" to "Unsolicited
       Messages"
     - APPENDIX1.6.2.4
     - APPENDIX1.6.2.18
  2. The documentation for the DISABLE option of the HOLD
     automation table action item should be restored.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of Tivoli NetView for z/OS.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: The MVS Initialization and Tuning       *
  *                      Reference states that specifying        *
  *                      SUP(YES) for a solicited message does   *
  *                      not result in the message being         *
  *                      suppressed from display. However,       *
  *                      several places in the NetView           *
  *                      Automation Guide imply that SUP(YES)    *
  *                      suppresses any type of message.         *
  *                      Also, starting in V5R4, the DISABLE     *
  *                      option of the HOLD automation table     *
  *                      action is not documented.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Several places in the Tivoli NetView for z/OS Automation Guide
  state that SUP(YES) in an MPFLSTxx member causes a message to be
  suppressed. As the z/OS MVS Initialization and Tuning Reference
  states, SUP(YES) causes the message to be suppressed only for
  unsolicited messages. In order to have solicited messages
  suppressed via MPF, SUP(ALL) should be used. The Automation
  Guide should be updated to reflect this.
  Also, the documentation for the HOLD(DISABLE) action in the
  Automation Table chapter was removed in the V5R4 version of the
  Automation Guide. However, this option is still viable and
  supported, so it should be reinstated.
  

Problem conclusion

• The Tivoli NetView for z/OS V6R1, V6R2 and V6R2M1 Automation
  Guides (SC27-2846-01, SC27-2846-02 and SC27-2846-03,
  respectively), should be updated according to the following:
  - Since solicited messages are not suppressed when SUP(YES) is
    used for the message in an MPFLSTxx system PARMLIB member, but
    are suppressed when SUP(ALL) is used, all occurrences of
    "SUP(YES)" should be changed to SUP(ALL) in the following
    sections:
    - The section titled "Ensuring That z/OS Forwards System
      Messages to NetView" (numbered 5.1.1.1.2 in V6R1) in the
      chapter titled "Automation Setup Tasks" (Chapter 18 in V6R1)
      under the major heading "Single-System Automation"
    - Section 4, "Solicited System Messages" (identified as
      APPENDIX1.6.2.4 in V6R1) in the section titled "Flow
      Descriptions" in the Appendix titled "Detailed NetView
      Message and Command Flows" (Appendix F in V6R1)
    - Section 18, "Solicited and Unsolicited System MVS Extended
      Console Messages for an OST, NNT, or Autotask" (identified
      as APPENDIX1.6.2.18 in V6R1) in the section titled "Flow
      Descriptions" in the Appendix titled "Detailed NetView
      Message and Command Flows" (Appendix F in V6R1)
  - The following note should be added to the sections titled
    "Messages That Originate on the Global Processor" (numbered
    7.10.1.1 in V6R1) and "Messages That Originate on the Local
    Processor" (numbered 7.10.1.2 in V6R1), each immediately
    following the bulleted list of actions taken by MPF, in the
    chapter titled "Job Entry Subsystem 3 (JES3) Automation"
    (Chapter 36 in V6R1) under the major heading "Additional
    NetView Automation Topics":
      Note: There are exceptions to the way messages are handled
      that might be different than what you might expect,
      especially related to SUP(YES) and solicited messages. Refer
      to the documentation describing the MPFLSTxx member in the
      z/OS MVS Initialization and Tuning Reference for more
      information.
  - In the section titled "Subsystems in Message Processing"
    (identified as APPENDIX1.4.1.2 in V6R1) in the appendix titled
    "MVS Message and Command Processing" (Appendix D in V6R1), the
    paragraph which begins with "To direct a message" and the
    subsequent paragraph which begins with "EMCS consoles that are
    acquired" should be changed to read as follows:
      To direct a message for NetView automation, set the AUTO
      keyword for that message to AUTO(YES) or AUTO(token) in the
      MPF table. If you also want to suppress the message so it is
      not displayed at MVS operator consoles (including those
      owned by NetView operators), you can set the SUP keyword in
      the message processing facility (MPF) table to SUP(ALL) for
      any message or SUP(YES) for messages that are not command
      responses. However, if you do not direct a message for
      NetView automation and you also suppress the message, the
      message is stopped at the MPF table and is effectively lost.
      Therefore, do not opt to prevent both automation (using
      AUTO(NO)) and display (using SUP(YES) or SUP(ALL)) for the
      same message, unless you want to completely stop the message
      from passing through MPF.
  
      EMCS consoles that are acquired by NetView cannot solicit
      messages by route code if the messages are marked with
      SUP(YES) or SUP(ALL) in the MPF table.
  - The description of the HOLD automation table action in the
    section titled "Actions" (numbered 4.6.7 in V6R1) in the
    chapter titled "Automation Table" (Chapter 15 in V6R1) under
    the major heading "NetView Program Automation Facilities"
    should be changed as follows:
    - The syntax diagram should be changed to read as follows:
        HOLD(YES|NO|LOCAL|DISABLE)
    - The description of the DISABLE option should be added to
      read as follows:
          HOLD(DISABLE)
            Causes the following to occur:
            - The message is not held on the NetView screen
            - The message is no longer considered an action
              message
            - The message is not rerouted upon logoff
  
            Notes:
            - If the message is later routed to a different
              domain, and is automated such that it is held on a
              NetView operator there, the NetView program does not
              ensure that it is deleted when and if a DOM is
              issued in the originating domain.
            - If a program erroneously issues an action message
              but never issues a corresponding DOM, you can use
              HOLD(DISABLE) to prevent the message from being held
              unnecessarily.
  

Temporary fix

Comments

APAR Information

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

  OA46326

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

Fix information

Applicable component levels