PM82353: KO2O0801E MAXIMUM DB2S (32) BEING MONITORED. SESSION FAILED (INITSCVT) AND KD2SLOG NONE DB2 SUBSYSTEM NOT DEFINED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• User receives KO2O0801E when attempting to logon to Omegamon DB2
  using an unknown DB2 subsystem name.
  KO2O0801E MAXIMUM DB2S (32) BEING MONITORED.  SESSION FAILED
  (INITSCVT).
  
  OMPE default configuration will set the default DB2 to logon to
  as NONE in RKD2PAR(RVTMNONE). If less than 32
  subsystems are being monitored and no DB2 subsystem is
  named NONE,  the user will be taken to the RLOG screen
  where the user can select a listed subsystem to monitor by
  pressing PF11.  If there is a DB2 subsystem with the name
  NONE the user will be logged on to subsystem NONE.
  NONE is a valid construct for a DB2 subsystem name.
  
  OMEGAMON DB2 (OMPE) is limited to monitoring a
  maximum of 32 subsystems on a single LPAR
  regardless of the number of OMPE collector tasks running
  at a particular release level. If 32 subsystems are being
  monitored and a user attempts to logon with a subsystem
  name that is not in this list, message KO2O0801E is issued
  and the customer is forced to logoff.
  
  If 32 subsystems are being monitored, any value provided
  as the DB2 subsystem name at logon time that is not a valid
  DB2 subsystem name will cause this issue.
  
  This situation manifests itself a in the CUA logon by displaying
  a pop up that shows
  KD2SLOG
  cccc DB2 subsystem not defined
  where cccc is the value that was used as the DB2 subsystem
  name to monitor.
  The RKLVLOG will display message KD200045I and display
  the RLOG screen showing the available DB2 to monitor.
  

Local fix

• For logon to classic VTAM specify a valid DB2 id at logon time.
  This can be done by setting the default DB2 in the
  RKD2PAR(RVTMxxxx) member or by passing a valid DB2 id
  in the logon command.
  LOGON APPLID(aaaaaaaa) DATA(DB2=cccc)
  where aaaaaaaa is the OMPE classic applid which can be found
  in message OMV002I and CCCC is a valid DB2 subsystem
  .
  For KD2SLOG message the workaround is:
  In the CUA logon 'Sign on panel' screen press PF11 after
  entering userid and this will take you to new screen called
  'Logon Options' and put the correct DB2 ssid name in the DB2
  Subsystem field
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   Classic Interface                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: KO2O0801E MAXIMUM DB2S (32) BEING       *
  *                      MONITORED.                              *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  *                                                              *
  ****************************************************************
  PROBLEM SUMMARY:
  DB2 SSIDs specified during logon are inserted in a table
  before validation.
  
  PROBLEM CONCLUSION:
  DB2 SSIDs are validated prior to table insertion.
  

Problem conclusion

• DB2 SSIDs are validated prior to table insertion.
  
  KEYWORDS : DB2 SSID KO2O0801E
  

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:

  UK93440 UK93441

Modules/Macros

•    KO2OINTB
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R510 PSY UK93440

     UP13/04/18 P F304

• R511 PSY UK93441

     UP13/04/18 P F304

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.