======================================================================== Support Note: 3 Product: The Operations Pack (TOP) Version: TOP Base Release 2.0 (and later) Title: Description of error codes displayed by the Management Interface Process (MIP) after detecting an invalid license Date: 12 October 2000 Copyright 2000 Gresham Software Labs Pty Ltd ======================================================================== Contents ======================================================================== Summary Details When the MIP detects an invalid license EMS events EMS events produced after the MIP detects a valid license EMS events produced after the MIP detects an invalid license Description of error codes after the MIP detects an invalid license When TOP detects an invalid license ======================================================================== Summary ======================================================================== When a customer starts the Management Interface Process (MIP) and the MIP detects an invalid license, it produces an EMS event that reports the license is invalid. The EMS event contains an error code that indicates why the license is invalid. This support note displays and describes possible error codes. Even if the MIP was started with a valid license, it is possible for the license to be invalid when The Operations Pack (TOP) is started, and for TOP to detect and report an invalid license. This support notes explains when this can occur and what to do if this occurs. ======================================================================== Details ======================================================================== ------------------------------------------------------------------------ When the MIP detects an invalid license ------------------------------------------------------------------------ The MIP is required by The Operations Pack. The MIP is usually started by a RUN command from a TACL prompt. When a customer runs the MIP executable object file, the MIP looks for a file called LICENSE in the same subvolume as the MIP executable object file. If the RUN command is valid, MIP starts whether or not it finds LICENSE. If the MIP finds LICENSE, it checks whether the license information in the file is valid. It produces EMS events to report the success or failure of the license check. If the MIP detects an invalid license, it produces an EMS event to indicate the cause of the failure. This EMS event includes an error code that indicates why the license is invalid. Note: A customer can view EMS events using applications such as The Operations Pack, NonStop NET/MASTER, and ViewPoint. ------------------------------------------------------------------------ EMS events ------------------------------------------------------------------------ An EMS event usually includes initial information such as date, time, process name, subsystem ID (subsystem owner, number, and version), and then the event number followed by the event text. The initial information that is included in an EMS event depends on the application that produces the event. The event number and event text indicate why an EMS event was produced. ------------------------------------------------------------------------ EMS events produced after the MIP detects a valid license ------------------------------------------------------------------------ After the MIP detects a valid license, the MIP produces EMS events with information about the customer and the MIP. These indicate that the license is valid. For example: 13 Customer is 'XYZ Development Corporation' 12 Management Interface Process, version 3.2, TCP/IP process \SYSDEV.$ZTC0, port 2345. Copyright 2000, Gresham Software Labs Pty Ltd. License \SYSDEV.$DATA.MYMIP.LICENSE ------------------------------------------------------------------------ EMS events produced after the MIP detects an invalid license ------------------------------------------------------------------------ After the MIP detects an invalid license, the MIP produces an EMS event with an error code that indicates why the license is invalid, and also an EMS event with information about the MIP. For example: 3 NOTE: Your license is not valid, code 10,0,0,0 12 Management Interface Process, version 3.2, TCP/IP process \SYSDEV.$ZTC0, port 2345. Copyright 2000, Gresham Software Labs Pty Ltd. License \SYSDEV.$DATA.MYMIP.LICENSE ------------------------------------------------------------------------ Description of error codes after the MIP detects an invalid license ------------------------------------------------------------------------ The error code in EMS event 3 indicates why a license is invalid. An error code has several parts. The first part is a number that identifies the error. Other parts provide more information about the error. For example, if the error code is 10,0,0,0, the first part of the error code is 10. Other parts are 0,0,0. The following table displays and describes possible error codes: Error Code Description ---------- ------------------------------------------------------------ 1 The license key is not 11 characters More information: the key length Example error code: 1,12,0,0 (if the key length is 12 characters) ------------------------------------------------------------ 2 The expiry date is not 8 characters or an asterisk (*) Example error code: 2,0,0,0 ------------------------------------------------------------ 3 The expiry date is not all digits or an asterisk (*) Example error code: 3,0,0,0 ------------------------------------------------------------ 4 The expiry month is not legal More information: dd,mm,yyyy Example error code: 4,01,13,2000 (if the month is 13) ------------------------------------------------------------ 5 The expiry day is not legal More information: dd,mm,yyyy Example error code: 5,30,02,2000 (if the day is 30 for February) ------------------------------------------------------------ 6 Too many CPUs More information: CPU count Example error code: 6,5,0,0 (if you are licensed for four CPUs) ------------------------------------------------------------ 7 Unknown CPU type (could not find name in internal table) Example error code: 7,0,0,0 ------------------------------------------------------------ 8 A CPU is too powerful More information: CPU number,CPU type,CPU model Example error code: 8,1,9,10 (if you have a license for an S7000 system but try to run the MIP on an S74000 system) ------------------------------------------------------------ 9 Cannot find CPU type More information: CPU number,CPU type,CPU model Example error code: 9,1,9,10 ------------------------------------------------------------ 10 License key does not match other information in LICENSE Example error code: 10,0,0,0 Note: This error will occur if you alter any information in LICENSE. If you want to open LICENSE to view the information, we recommend you open LICENSE in READONLY mode to ensure you do not accidentally alter any information. ------------------------------------------------------------ 11 Wrong system number/name with a standard license More information: System number, System name (numeric representation of first four ASCII characters, including the \), System name (numeric representation of second four ASCII characters) Example error code: 11,45,1547845956,1312902469 (if the number is 45 and the name is \BADNAME) ------------------------------------------------------------ 12 Start date of the license is not all digits Example error code: 12,0,0,0 ------------------------------------------------------------ 13 Start date month of the license is not legal More information: dd,mm,yyyy Example error code: 13,01,13,2000 (if the month is 13) ------------------------------------------------------------ 14 Start date day of the license is not legal More information: dd,mm,yyyy Example error code: 14,30,02,2000 (if the day is 30 for February) OR Wrong system number/name with a special site license More information: System number, System name (numeric representation of first four ASCII characters, including the \), System name (numeric representation of second four ASCII characters) Example error code: 11,45,1547845956,1312902469 (if the number is 45 and the name is \BADNAME) ------------------------------------------------------------------------ When TOP detects an invalid license ------------------------------------------------------------------------ Even if the MIP was started with a valid license, it is possible for the license to be invalid when The Operations Pack is started. This occurs if a customer tries to start The Operations Pack in a way that is inconsistent with their license. In other words, the license check succeeded when the MIP was started, but a customer is now trying to use The Operations Pack in a way for which they are not licensed. This occurs in situations such as the following: o A customer is licensed to use a specific version of The Operations Pack, but tries to use a different version. In this case, the license is valid only for a specific version of The Operations Pack. o A customer is licensed to use The Operations Pack until a certain date, but tries to use The Operations Pack after that date. In this case, the license is valid but has expired. o A customer is licensed to use The Operations Pack with specific Manager clients, but tries to use The Operations Pack with other Manager clients. In this case, the license is valid only for specific Manager clients. In situations such as these, the customer must either use The Operations Pack in a way that is consistent with their license or obtain a replacement license. END OF SUPPORT NOTE ====================================================