IBM Support

OA38197: TEMS CRASHES DURING STARTUP.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • TEMS fails during initialization when automatically starting a
    situat
    with malformed SQL.  The failue reported initially reported
    occurred
    the Windows platform but this failure can occur on all
    platforms.
    
    The failing thread call stack looks a follows:
    
      kdsmain!VPM11CAT+0x14b4
      kdsmain!VPM11CVP+0x78a
      kdsmain!VVW1CSV+0x3aa
      kdsmain!VRQ11CR+0xbf2
      kdsmain!VPA11_CreateRequest+0x322
      KDSBASE!sql1creq+0xb05
      kdsmain!RUL11CRQ+0x5e4
      kdsmain!RUL11DEC+0x41f
      kdsmain!RUL11CRN+0x255
      kdsmain!RUL11CRT+0xa0e
      kdsmain!SIT11CS+0x24a
      kdsmain!VST12SRT+0x1ce
      kdsmain!VPM11OUT+0xeeb
      kdsmain!VPM11CT+0x48c
      kdsmain!VVW1CSV+0x6ba
      kdsmain!VRQ11CR+0xbf2
      kdsmain!VPA11_CreateRequest+0x322
      KDSBASE!sql1creq+0xb05
      KSM!WsSqlDSRequest::WsSqlDSRequest+0x3c3
      KSM!WsSqlDSDB::CreateRequest+0x296
    
    RECREATE INSTRUCTIONS:
    The following SQL can be issued to cause the exception reported
    here:
    
      SELECT SITDB.RULENAME,
             SITDB.PREDICATE
      FROM   O4SRV.SITDB, O4SRV.LOCALTIME;
    

Local fix

  • Modify the offending situation to not be automatically started.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All TEMS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: THE MONITORING SERVER CRASHES DURING    *
    *                      STARTUP PROCESSING SITUATION            *
    *                      AUTOSTARTS.                             *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    ****************************************************************
    The monitoring server fails during startup when a malformed
    situation is defined and "autostart = yes" is specified.
    

Problem conclusion

  • Detect when a malformed SQL that specifies a tablename on
    the FROM clause without any columnnames corresponding to the
    table.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA38197

  • Reported component name

    MGMT SERVER DS

  • Reported component ID

    5608A2800

  • Reported release

    622

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-11-30

  • Closed date

    2011-12-05

  • Last modified date

    2012-01-01

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

    IV04070

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

Modules/Macros

  • KDSMAIN
    

Fix information

  • Fixed component name

    MGMT SERVER DS

  • Fixed component ID

    5608A2800

Applicable component levels

  • R622 PSY UA63440

       UP11/12/17 P F112

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSRJ5K","label":"Tivoli Management Server for Distributed Systems on z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"622","Edition":"","Line of Business":{"code":"LOB17","label":"Mainframe TPS"}}]

Document Information

Modified date:
01 January 2012