======================================================================== Support Note: 11 Product: The Operations Pack (TOP) Version: All versions Title: Description of MIP EMS Events Created: 18 March 2004 Updated: - Copyright 2004 Gresham Software Labs Pty Ltd -------------- MIP EMS Events -------------- Events generated from MIP contain only the standard EMS header tokens and the ZEMS_TKN_TEXT token. The ZEMS_TKN_TEXT contains the displayed text. The owner is always GSL. Events generated from MIP directly use subsystem number 1 and are never critical. Events that are generated indirectly from the client use the subsystem number, criticality and text which the end-user has supplied. The event numbers for GSL.1 are: 1 - "NOTE: Your license has expired !" Cause: your MIP license has expired Effect: TOP cannot be used Recovery: obtain a new license - "NOTE: Your license is in the future !" Cause: the license date has not been reached Effect: TOP cannot be used Recovery: obtain a new license 2 - "WARNING: Your license will expire at midnight on " is the day on which the current MIP license will expire Cause: the date at which your license expires is approaching Effect: Information only. Recovery: organize to obtain a new license 3 - "NOTE: Your license is not valid, code " is an internal error code Cause: the MIP license is not valid for this system Effect: TOP cannot be used Recovery: check you are using the correct license. If so, call your distributor with this event text. - "NOTE: Your license is not valid" Cause: the MIP license file is not valid Effect: TOP cannot be used Recovery: use previous events to determine the underlying cause 4 - "NOTE: You are not licensed to run " is a TOP subsystem Cause: you are not licensed to use the given subsystem Effect: the subsystem cannot be used Recovery: obtain a new license including the subsystem 5 - "NOTE: io error reading license file" is a file system error number Cause: the MIP license file cannot be read Effect: TOP cannot be used Recovery: check you are using the correct license file. - "NOTE: io error opening profile database" is a file system error number Cause: the TOP profile file cannot be opened Effect: TOP cannot be used Recovery: use the error to correct problem. To return to the default MIP behaviour you can delete or rename the PROFILES file - "NOTE: io error creating profile database" is a file system error number Cause: the TOP profile file cannot be created Effect: TOP user-defined profiles cannot be used Recovery: use the error to correct problem 6 - "NOTE: bad format license file" Cause: the MIP license file is not in the correct format Effect: TOP cannot be used Recovery: check you are using the correct license file. 7 - Error exit: is description of major error Cause: see Effect: MIP is stopped and TOP cannot be used. Recovery: use the description to correct problem and restart MIP. 8 - "MIP abending, trap=, file=", is an internal trap number is the internal location of the trap Cause: an internal error has occurred Effect: current clients using this MIP will get errors. MIP will restart in its backup. A saveabend file should be produced. Recovery: notify your distributor of the EMS event and be prepared to send the saveabend file 9 - "MIP socket error (function ), TCP/IP function temporarily" " disabled, retry in 30 seconds" is a file system error number is a tcpip function Cause: listening to the MIP port number failed Effect: Direct TCP/IP access from client is not allowed, only from MIP on another node Recovery: Use the error number to correct the problem. There is no need to restart MIP as the attempt will be made repeatedly. 10 - "MIP can't allocate timer, TCP/IP function permanently disabled" Cause: no Guardian timers are available Effect: Direct TCP/IP access from client is not allowed, only from MIP on another node Recovery: Use the error number to correct the problem and restart MIP 11 - "MIP socket error (function ) on application socket" is a file system error number is a tcpip function Cause: an unexpected error occurred on a socket Effect: the client will get a tcpip failure Recovery: use the error number to correct the problem then retry from the client 12 - "Management Interface Process, version , TCP/IP process " "port . Copyright , Gresham Software Labs Pty Ltd." " License " is the MIP version id is the TCP/IP process name is the TCP/IP port number is the copyright date is the license file name. Cause: MIP startup or a new license file Effect: Information only Recovery: None required. - "Management Interface Process, version , no TCP/IP function " "Copyright , Gresham Software Labs Pty Ltd." " License " is the MIP version id is the copyright date is the license file name. Cause: MIP startup or a new license file Effect: Direct TCP/IP access from client is not allowed, only from MIP on another node Recovery: None required if effect is desirable, otherwise start MIP with a port number - "Management Interface Process, version , running as logon server." "Copyright , Gresham Software Labs Pty Ltd." is the MIP version id is the copyright date Cause: end-user logon required Effect: Information only Recovery: None required. 13 - "Customer is ''" is the customer name from the license file Cause: MIP startup or a new license file Effect: Information only Recovery: None required. 14 - "MIP SPI error on to " is an SPI error number is an SPI function is a TCP/IP process name Cause: an unexpected error has been received using SPI Effect: the ip-address of the host cannot be determined Recovery: use the error number to correct the problem - "MIP file error on to " is a file system error number is a file system function is a TCP/IP process name Cause: an unexpected file system error has been received Effect: the ip-address of the host cannot be determined Recovery: use the error number to correct the problem - "MIP failed to open TCP/IP process , error " is a TCP/IP process name is a file system error number Cause: an unexpected file system error has been received Effect: the ip-address of the host cannot be determined Recovery: use the error number to correct the problem 15 - "Error writing to audit collector " is a file system error number is the process name of the collector Cause: file system error writing to the collector Effect: audit records are not written Recovery: use the error numbers to correct the problem 16 - "MIP error / spawning /bin/sh to copy topsh" , , are fields in the process_extension_results_def structure Cause: cannot start the OSS shell to install the topsh OSS program Effect: access to OSS files is not available Recovery: use the error numbers to correct the problem 20 - "AUDIT: => " is the type of audit operation, one of Command, Response, Run is the name of the executing program is the name of the user causing the operation is the audited information Cause: an auditted operation has occurred Effect: Information only Recovery: None required END OF SUPPORT NOTE ====================================================