OA38276: PPI RECEIVERS NOT INITIALIZING UNDER NETVIEW 6.1

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Two PPI address spaces were initialized. After the first
  PPI address space became active, the first few receivers
  initialized to it. Then after the second PPI address space
  became active, the remaining PPI receivers initialized to
  the second PPI address space as their tasks became active.
  The second PPI address space is then the only one recognized
  leaving the first PPI address space dormant along with its
  receivers.
  *****
  Additional Symptoms reported in PMR 51918,082,000:
  PPI transfer failed with RC: +0000000026
  PPI to TEC failed with RC: +0000000026
  PPI TECROUTE IHSATEC fails with Return Code 26  RC 26
  The NetView for z/OS Application Programmer's Guide defines
  Return Code: 26 - The receiver program is not defined.
  Additional symptoms added by RJC 12/14/2011
  *****
  

Local fix

• A bypass for this is to make sure that only one SSI/PPI
  procedure has the PPIOPT parameter set to PPI and the others
  set to NOPPI.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli NetView for z/OS V6R1 users       *
  *                 starting multiple SSI/PPI subsystems on the  *
  *                 same MVS image with option PPIOPT set to PPI *
  *                 on more than one of the started procedures.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: In V6R1 when multiple SSI/PPI           *
  *                      subsystems are started on the same MVS  *
  *                      image with the PPIOPT paramter set to   *
  *                      PPI, PPI receivers that are initialized *
  *                      after the first PPI subsystems are      *
  *                      started will seem to disappear by the   *
  *                      time the last PPI subsystem is started. *
  *                      Only those PPI receivers initialized    *
  *                      after the last PPI subsystem is started *
  *                      will appear to be active and will       *
  *                      receive data. The earlier PPI receivers *
  *                      will receive no data. A DISPPI command  *
  *                      issued from a NetView operator will     *
  *                      also only show the PPI receivers that   *
  *                      were initialized after the last PPI     *
  *                      subsystem was started. A DISPPI command *
  *                      issued using the MVS modify (F) command *
  *                      to any of the subsystems initialized    *
  *                      with the PPIOPT parameter set to PPI    *
  *                      will only show the PPI receivers        *
  *                      defined for the subsystem to which the  *
  *                      modify command was directed.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Multiple PPI subsystems are allowed to be started when only one
  is supposed to be allowed. This is because the code is not
  properly checking for the existence of an active PPI address
  space.
  

Problem conclusion

• The PPI subsystem code is being changed to again prevent
  multiple PPI subsystems from being started even if PPIOPT=PPI
  is specified on the SSI/PPI started procedure.
  Also a 600 user abend is being added to the code to help detect
  this and similar errors in the future.
  Also code is being changed in the MVS modify DISPPI command
  processor to display the defined PPI receivers in SSI/PPI
  address space to which the modify command is directed if it has
  an active PPI in that address space. Otherwise message CNM217I
  is issued indicating there is no PPI active in that address
  space.
  

Temporary fix

Comments

APAR Information

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

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

  UA63720

Modules/Macros

• CNMCPC   CNMCRSST CNMCSTMD
  

Fix information

• Fixed component name

  NETVIEW FOR Z/O

• Fixed component ID

  5697NV600

Applicable component levels

• R10B PSY UA63720

     UP12/02/01 P F201

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.