OA42162: COMPATIBILITY ISSUES WITH TIVOLI NETVIEW FOR Z/OS V6R1

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• This APAR will address compatibility issues with Tivoli NetView
  for z/OS V6R1.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of Tivoli NetView for z/OS V6R1    *
  *                 who need to also run an instance of a        *
  *                 product with COMPID 5698LSA01 (IACz or       *
  *                 Tivoli NetView for z/OS V6R2) in the same    *
  *                 LPAR.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: If Netview V6R1 is run in the same LPAR *
  *                      as a product with COMPID 5698LSA01      *
  *                      (IACz or NetView V6R2), multiple errors *
  *                      occur, such as ABENDs and other error   *
  *                      messages.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Changes were made to common control blocks in the development of
  the IBM Automation Control for z/OS (IACz) product (which is
  also the base portion of NetView V6R2) that causes
  incompatibilities with NetView V6R1. As a result, both V6R1 and
  V6R2 or IACz cannot run in the same LPAR without changes to
  code in V6R1.
  

Problem conclusion

Temporary fix

Comments

• NetView V6R1 is being changed to resolve incompatibilities with
  future releases of NetView-based products, include V6R2.
  Also, the Tivoli NetView for z/OS V6R1 Messages and Codes Volume
  1 (AAU-DSI) (GC27-2856-02) should be changed in the following
  ways:
   - The message text and description of message CNM598W should be
     changed to read as follows:
       CNM598W Subsystem is not active for ssi_name
  
       Explanation: The named subsystem cannot process system
       messages or designated commands. This can be the result of
       a SETSSI DEACTIVATE command, a missing INITRTN parameter,
       or an inactive CNMPSSI (SSI procedure).
  
       Message Variables:
  
       ssi_name The 4-character subsystem name that is used in
               IEFSSNxx definitions or with SETSSI commands.
  
       Operator response: Notify the system programmer.
  
       System programmer response: Check the IEFSSNxx member of
       SYS1.PARMLIB for the ssi_name reported. Add an INITRTN
       statement specifying DSI4LSIT. If you are migrating from an
       earlier version of the NetView program, consult the
       Installation: Migration Guide. If a SETSSI system command
       deactivated the named subsystem, you can reactivate it by
       starting or restarting the NetView SSI procedure. If a
       CNM543 message is displayed, consult the help for that
       message.
   - New message CNM749A should be added, which should read as
     follows:
       CNM749A Incompatible NetView program or subsystem is
            defined for subsystem subsystem.
  
       Explanation: The code for the specified subsystem is at a
       different support level from that of the NetView program
       issuing the message.
  
       Message Variables:
  
       subsystem The subsystem name of the incompatible NetView
               component.
  
       Operator response: Notify the system programmer.
  
       System programmer response: Shut down and deactivate the
       specified subsystem and all associated instances of the
       NetView program. Apply the appropriate maintenance, and
       then follow the instructions included in that maintenance
       for restarting all instances of the NetView program.
  The online help for msgCNM598W and msgCMN749A is being changed
  to reflect the above.
  *** IMPORTANT: After applying the fix for this APAR, in order to
  restart the NetView address space without an IPL, the following
  steps MUST be executed, in order:
  1. Use the NetView command REVISE CMD OFF to disable command
     revision. You will need to know what parameters were used to
     enable MPF. To learn what parameters were used, review
     instances of message IEE252I in Canzlog (or SYSLOG).
  
  2. To determine the name of the active NetView subsystem, issue
     the following command:
  
       D SSI,ALL,STATUS=ACTIVE
  
     Review the output of the command to identify those names
     associated with the NetView product.  You should find exactly
     one such associated name. You will need that name in a
     subsequent step. (The name will be the first four characters
     of the jobname of the your "Principal" NetView instance.)
  
     If you find names associated with a NetView product at
     version V5.4 or earlier, you can ignore them for purposes of
     this installation.
  
  3. You found exactly one subsystem name for a NetView instance
     in the step above. Stop that subsystem using the following
     command:
  
       SETSSI DEACTIVATE,SUBNAME=ssiname
  
     where ssiname is the name of the active subsystem noted in
     step 2 above.
  
     Note: You may ignore message IEFJ037I.
  
  4. Stop all address spaces associated with the NetView product.
     This includes "SSI proc" jobs.
  
  5. Dynamically add the required NetView modules to the link pack
     area (LPA):
  
       DSIRVCEX
       DSI4LSIT
       CNMCSSPI
  
     Use the SETPROG LPA ADD command to add each module:
  
       SETPROG LPA,ADD,MODNAME=module,DSNAME=library
  
     where module is the module name and library is the data set
     name of the library where the module was installed.
  
  6. Enable command revision (CRT), by issuing a SET MPF command,
     using the same parameters as for your previous MPF
     initialization, as discovered in step 1 above.
  
  7. If you want to define a new subsystem name for any NetView
     procedure running version 6.1 or above, you can do so at this
     time.  Use the SETSSI ADD command(s) like the following:
  
     SETSSI ADD,SUBNAME=newName,INITRTN=DSI4LSIT
  
     Where "newName" is the four character subsystem name to be
     added and which will also be the first four characters of the
     jobname(s) for the procedure(s).
  
     Do not include a INITPARM argument on this (these) commands.
  
     Message CNM617I is displayed when the SETSSI ADD command
     completes.
  
  8. Recall the active subsystem name discovered in step 2 and
     start the Subsystem procedure (e.g. CNMPSSI) for that same
     subsystem name. Then:
     - If message CNM541I (indicating success) is issued, continue
       with step 11.
     - If message CNM749A (indicating a conflict) is issued or if
       CNM598W is issued (indicating downlevel DSI4LSIT), continue
       with step 9.
     - If another failure message is issued, consult the help for
       that message.
  
  9. Choose a new subsystem name to act as a placeholder for
     dynamic subsystem initialization.  This can be any four
     character name, acceptable to the MVS system as a subsystem
     name (and not already in use). It will not be associated with
     any jobname or procedure name.
  
  10. Dynamically add the subsystem for the new subsystem name by
     issuing the SETSSI command:
  
       SETSSI ADD,SUBNAME=subsystem,INITRTN=DSI4LSIT
  
     Message CNM617I is displayed when the SETSSI ADD command
     completes.
  
  11. If the Subsystem procedure did not start successfully in
     step 8, repeat that step now. After the CNM541I message is
     issued, start the subsystem procedure for each of the NetView
     instances to be used. The CNM541I message is displayed after
     each subsystem is successfully started.
  
  12. Start the main procedures for each instance of the NetView
     program desired.
  ž**** PE14/02/27 FIX IN ERROR. SEE APAR OA44196  FOR DESCRIPTION
  ž**** PE14/12/03 FIX IN ERROR. SEE APAR OA44273  FOR DESCRIPTION
  

APAR Information

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

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

  UA70457 UA70458 UA70459

Modules/Macros

• CNMCMSG  CNMCMSGR CNMCROCK CNMCRSST CNMCSSIF
  CNMCSSIN CNMCSSIR CNMCSSIS CNMCSSIW CNMCSSPI CNMCSSVT CNMINIT
  CNMMSJPN CNM59    CNM74    DSIDEFAU DSIGTCON DSIISVLM DSILOGMT
  DSIMIGIT DSIMSSI  DSIOVERR DSIPICRW DSIPICZD DSIRLCON DSIRVCEY
  DSISVKNL DSI4CLSB DSI4LAPM DSI4LAPN DSI4LA2Z DSI4LCDS DSI4LCMD
  DSI4LCME DSI4LCM1 DSI4LCON DSI4LCYS DSI4LGBL DSI4LIMG DSI4LSIT
  DSI4LWLM DSI4LWQD DSI4LZF  DSI4LZLO DSI4LZM  HNV610BJ
  

Fix information

• Fixed component name

  NETVIEW FOR Z/O

• Fixed component ID

  5697NV600

Applicable component levels

• R10B PSY UA70457

     UP13/10/23 P F310

• R10E PSY UA70458

     UP13/10/23 P F310

• R10J PSY UA70459

     UP13/10/23 P F310

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.