Why am I getting S8 and TG or TF LMP errors?

Products

• Vision:Two

Issue/Introduction

Description:

Users are mystified when CAS9xxx errors issue where these are apparently not in use.

Solution:

S8 is the LMP code for VISION:Two
S9 is the LMP code for VISION:Two GDBI interface
TF is the LMP code for VISION:Two IMS interface
TG is the LMP code for VISION:Two DB2 interface

The following errors are issued sites that have not installed CA VISION:Two or may occur when a database feature is not in use:

    CAS9012A 00004 KEY WARNING UPDATE CPU 
    CAS9180E  CPU REQUIRES AN LMPKEY (S8) 
    CAS9180E  CPU REQUIRES AN LMPKEY (TG) 
 
    CAS9180E  CPU REQUIRES AN LMPKEY (TF) 
 
    or 
 
    CAS9013A PRODUCT ABOUT TO EXPIRE 
    PRODUCT COMPONENT CODES:  (TG) & (S8) 
 
    PRODUCT COMPONENT CODES:  (TF)

This occurs at sites installing INVISION 27 packaged by Siemens Medical Solutions (SMS) which imbeds CA VISION:Two and its database interface. Hence CA VISION:Two is installed, but that is transparent to the user.
A new release of the SMS INVISION 27 package imbeds VISION:Two r14.0 which invokes the standard CA90 licensing mechanism which is generating the messages. This did not occur in prior SMS INVISION package delivery because it used VISION:Two 11.0 which used an internal Sterling licensing mechanism.

Further, there was a bug in VISION:Two such that the wrong interface LMP code was checked. The SMS INVISION 27 package uses the GDBI interface which is LMP code S9, so the inserts to the CAS9 messages should be S8 and S9 instead of S8 and TG.

SMS customers can get both the LMP keys and updated INVISION package from Siemens to invoke the correct key code. Refer to SMS items SSKB EV04906749 and model EVTS ticket 4907845 when contacting Siemens.
In the short term please contact the CA licensing department to request temporary LMP keys for S8 and TG.

The error with the TF insert occurs at CA customer sites running VISION:Two DB2 jobs.
The bug mentioned above causes the wrong insert in the CAS9 message.
RO09486 is available for download from Support Online to correct the problem.

Environment

Release:
Component: V:TWO