II11247: INFO APAR TO DOCUMENT TME10 NETVIEW FOR OS/390 V1R2 NON-DEFECT PROBLEMS.

APAR status

• Closed as canceled.

Error description

• ---------------------------------------------------
  This is an informational apar to list Tivoli
  NetView for OS/390 V1R2 common non-defect problems
  ---------------------------------------------------
   Problem: Where is Step 9 in the Install and Admin guide which
   required the user to add BNJMTERM to IEAVTRML in IGC0001C?
  Answer:
  NetView uses MVS RESMGR macro to dynamically define BNJMTERM
  memory-termination module rather than adding it to IEAVTRML.
  The MVS RESMGR macro was introduced in MVS 4.1, and the MVS
  documentation states that the RESMGR macro should be used
  to define resource managers such as NetView's BNJMTERM, the
  NetView Address Space termination routine. In pre-TME10
  NetView, BNJMTERM was defined by zapping BNJMTERM's name in
  csect IEAVTRML in load module IGC0001C. This has been updated
  so NetView uses the RESMGR macro to define BNJMTERM, as the MVS
  doc recommends. Therefore the ZAP to IEAVTRML is no longer
  needed.
  This provides a more usable interface so customers will NOT
  need a zap in IEAVTRML for NetView's BNJMTERM whenever they
  go to a new release of MVS.
  Note that no versioning code is needed around the RESMGR macro.
  It was introduced in MVS 4.1, and the oldest MVS that NetView
  V3R3 supports is MVS 4.3, thus no versioning is required.
  ***************************************************************
  RACF definitions necessary for NetView/OS390 Unix Services and
  PIPE UNIX:
  1.  DEFINE THE USERID ASSOCIATED WITH NETVIEW'S ADDRESS SPACE
      TO HAVE UID 0 AND TO HAVE AN OMVS SEGMENT.
  2.  MAKE SURE THE USERID IN #1 HAS READ ACCESS TO BPX.DAEMON AND
       THAT THE SAF FACILITY CLASS IS DEFINED AND ACTIVE BY:
       RDEFINE FACILITY BPX.DAEMON UACC(NONE)
       SETROPTS CLASSACT(FACILITY)
       SETROPTS RACLIST(FACILITY)
       PERMIT BPX.DAEMON CLASS(FACILITY) ID(ID IN #1) ACCESS(READ)
       SETROPTS PROGRAM(WHEN)
       SETROPTS RACLIST(FACILITY) REFRESH
   3.  MAKE SURE YOU HAVE ISSUED THE FOLLOWING RDEFINE COMMANDS TO
       GIVE THE LIBRARIES PROGRAM CONTROL:
   RDEFINE PROGRAM * ADDMEM ('SYS1.LINKLIB'/??????/NOPADCHK)
     UACC(READ)
  RDEFINE PROGRAM * ADDMEM ('hlq.SCEERUN'/??????/NOPADCHK)
    UACC(READ)
  RDEFINE PROGRAM * ADDMEM ('hlq.SEAGALT'/??????/NOPADCHK)
    UACC(READ)
   RDEFINE PROGRAM * ADDMEM ('hlq.SEKGLNK1'/??????/NOPADCHK)
     UACC(READ)
  RDEFINE PROGRAM * ADDMEM ('hlq.xxxxxxx'/??????/NOPADCHK)
    UACC(READ) , where xxxxxxx is the dataset containing
     IRXANCHR if you have a USERMOD coded there.
  * WHERE ?????? IS THE VOLUME ON WHICH THOSE DATASETS RESIDE.
  * THE ABOVE RACF COMMANDS NEED TO BE RUN TO GIVE PROGRAM
    CONTROL TO SYS1.LINKLIB, YOUR LE RUNTIME LIBRARY AND YOUR
    REXX ALTERNATE LIBRARY
  4.  AFTER YOU HAVE ISSUED THE ABOVE COMMANDS, YOU WILL NEED TO
      MAKE SURE YOU ISSUE A SETROPTS WHEN(PROGRAM) REFRESH
  5.  ALSO, MAKE SURE THAT THE NETVIEW OPERATOR THAT IS ISSUING
      THE PIPE UNIX COMMAND HAS BEEN DEFINED AS A UNIX USER WITH
      THE OMVS SEGMENT
  ------------------------------------------------------------
  If RACF is active on your system, then you will need to
  activate the RACF SURROGAT class if you are using PIPE TSO:
      SETROPTS CLASSACT(SURROGAT)
  ***********************************************************
  problem: abend0c8 bnjavhsf +2b0 / +2b8  -or-
           abend0c4 bnjavhsf +2c2
  answer:
  NPDA / Hardware Monitor uses a format to record information
  to VSAM. Because the VSAM record format has been redesigned,
  Hardware Monitor data from NetView releases prior to TME 10
  NetView for OS/390 V1R1 cannot be used with this NetView
  release. NetView migrating users must delete and redefine
  the BNJLGPR and BNJLGSE databases before the databases can
  can be used with this NetView release if their previous
  release was prior to TME10 NetView V1R1.
  If TME10 V12 NetView is brought up the first time (with the
  npda databases deleted and redefined), then backed out to a
  pre-TME10 NetView release, and then TME10 V12 NetView brought
  back up again, it is NECESSARY to once again delete and
  reallocate the databases or one or the other above abend will
  occur.
  *******************************************************
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• Info apar.  Always cancel.
  

APAR Information

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

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

Fix information

Applicable component levels