The messages in this document may be produced by Software AG mainframe license processing or when using the license utility, LICUTIL.
MLC1001 | MLC1002 | MLC1003 | MLC1004 | MLC1005 | MLC2001 | MLC2002 | MLC2003 | MLC2004 | MLC2005 | MLC2006 | MLC2007 | MLC2008 | MLC2009 | MLC2010 | MLC2011 | MLC2012 | MLC2013 | MLC3001 | MLC3002 | MLC3003 | MLC3004 | MLC3005 | MLC3006 | MLC3007 | MLC3008 | MLC3009 | MLC3010 | MLC3011 | MLC3012 | MLC3013 | MLC3014 | MLC9001 | MLC9002 | MLC9003 | MLC9004 | MLC9005 | MLC9006 | MLC9007 | MLC9009 | MLC9010| MLC1001 | CPU-ID cpuid is not defined in your product license |
| Explanation |
The CPU ID listed in the message (cpuid) is not defined in your product license. Either your license file is invalid or you have attempted to run the Software AG mainframe product on a machine for which it is not licensed. |
| Action |
Install and run the Software AG product on the machine for which it is licensed. If the problem persists, contact your Software AG sales representative for assistance. |
| MLC1002 | LPAR name lparname is not defined in your product license |
| Explanation |
The LPAR name listed in the message (lparname) is not defined in your product license. Either your license file is invalid or you have attempted to run the Software AG mainframe product on a machine for which it is not licensed. |
| Action |
Install and run the Software AG product on the machine for which it is licensed. If the problem persists, contact your Software AG sales representative for assistance. |
| MLC1003 | Machine capacity value higher than MSUs in your product license |
| Explanation |
The machine or the partition capacity (value) of the CEC or LPAR respectively on which you have attempted to install and run the Software AG mainframe product exceeds the capacity allowed in your product license. Either your license file is invalid or you have attempted to run the Software AG mainframe product on a machine for which it is not licensed. |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC1004 | The product license will expire on date |
| Explanation |
This warning message provides the date (YYYY/MM/DD) when the license will expire for this Software AG mainframe product. The product cannot be started with the current product license after this date. For example, an expiration date of 2018/09/05 indicates that you can still work on 2018/09/05 until 23:59 (local time) but need a new license from the next day (2018/09/06). |
| Action |
No action is required for this warning message. However, you should contact your Software AG sales representative to obtain an updated license soon. |
| MLC1005 | We assume CPU-ID cpuid as your DR or DR testing environment |
| Explanation |
The CPU ID listed in the message (cpuid) is not defined in your product license. Therefore, we assume that you are running in a disaster recovery environment. |
| Action |
If you are running in a disaster recovery environment, no action is required for this warning message. If you are not running in a disaster recovery environment, contact your Software AG sales representative to obtain an updated license. |
| MLC2001 | The product license is invalid |
| Explanation |
Your product license is invalid. |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC2002 | The product license key is invalid |
| Explanation |
The license file for the Software AG mainframe product is invalid. |
| Action |
Verify that the license file was transferred correctly to the mainframe host and that it is still in ASCII format. If the problem persists, contact your Software AG sales representative for assistance. |
| MLC2003 | The product license is not for value |
| Explanation |
The license file for the Software AG mainframe product is not for the operating system (OS), product code, or product version listed in the message (value). |
| Action |
Use the correct license file. If the problem persists, contact your Software AG sales representative for assistance. |
| MLC2004 | The product license has expired on date |
| Explanation |
The product license has expired. The date (YYYY/MM/DD) it expired is given in the message (date). |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC2005 | Tag missing in product license: tagname |
| Explanation |
The tag with the name listed in the message (tagname) is missing in your product license. |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC2006 | Invalid tag value in product license: tagname |
| Explanation |
The value of the tag with the name listed in the message (tagname) is invalid in your product license. |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC2007 | Current CPU-ID not found for product license check |
| Explanation |
The CPU ID of the CPU on which the product license check was run is not found in the license file. |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC2008 | The number of MSU values in the product license is incorrect |
| Explanation |
The machine capacity covered by the product license is incorrect. |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC2009 | ExtendedRights setting value not allowed under this system |
| Explanation |
The ExtendedRights setting listed in the message (value) is not supported by your system. |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC2010 | Soft capping is not allowed with ExtendedRights value |
| Explanation |
Your product license does not allow soft capping with the ExtendedRights setting listed in the message (value). |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC2011 | Defined hardware class in the license exceeded value |
| Explanation |
The hardware class (PriceQuantity) in your product license is too small for the current machine (value). |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC2012 | The number of zIIPs (value) exceeds the license definition |
| Explanation |
The number of zIIP processors in the current machine exceeds the number of zIIPs (PriceQuantity) in your product license. |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC2013 | The number of zIIP values in the product license is incorrect |
| Explanation |
The number of zIIP values (zIIPs) in your product license does not match with the number of LPAR values (LPARs). |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC3001 | Invalid LCPCB length |
| Explanation |
The license check routine has been incorrectly called. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3002 | Work area too small |
| Explanation |
The size of the work area for the license check routine is too small. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3003 | Invalid function code |
| Explanation |
The license check routine has been incorrectly called. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3004 | Invalid operating system |
| Explanation |
The ID of the operating system passed through the license check routine is invalid. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3005 | Invalid product code |
| Explanation |
The product code passed through the license check routine is invalid. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3006 | Invalid product version |
| Explanation |
The product version passed through the license check routine is not numeric. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3007 | Invalid current date |
| Explanation |
The current date passed through the license check routine is invalid. The date must be in the format yyyy-mm-dd. The dash (-) delimiters are not checked but the numbers must be a valid year, month and day, respectively. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3008 | Tag not found |
| Explanation |
The license check routine cannot find the requested XML tag. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3009 | Component Id tag not found |
| Explanation |
The license check routine cannot find the XML tag |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3010 | Invalid search tag |
| Explanation |
The XML search tag requested by the license check routine is invalid. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3011 | Insufficient I/O area size |
| Explanation |
The size of the I/O area for the license check routine is too small. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3012 | Output record length too small |
| Explanation |
The length of the output record for the license check routine is too small. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3013 | Error message text not found |
| Explanation |
The license check routine cannot find the text that belongs to the requested error message. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC3014 | Too many errors occurred |
| Explanation |
The license check routine detected too many errors. Some messages are lost. |
| Action |
Contact your Software AG support representative for assistance. |
| MLC9001 | License exceeds maximum size of 8000 |
| Explanation |
Your license file is too large. |
| Action |
Contact your Software AG sales representative for assistance. |
| MLC9002 | Error opening license file input |
| Explanation |
An error occurred during an attempt to open the license file input. |
| Action |
Investigate the cause of the error, paying special attention to the corresponding error messages produced by the operating system. Contact your Software AG sales or support representative for assistance. |
| MLC9003 | Error reading license file input |
| Explanation |
An error occurred during an attempt to read the license file input. |
| Action |
Investigate the cause of the error, paying special attention to the corresponding error messages produced by the operating system. Contact your Software AG sales or support representative for assistance. |
| MLC9004 | Error opening license file assembler output |
| Explanation |
An error occurred during an attempt to open the license file assembler output. |
| Action |
Investigate the cause of the error, paying special attention to the corresponding error messages produced by the operating system. Contact your Software AG sales or support representative for assistance. |
| MLC9005 | Error writing license file assembler output |
| Explanation |
An error occurred during an attempt to write the license file assembler output. |
| Action |
Investigate the cause of the error, paying special attention to the corresponding error messages produced by the operating system. Contact your Software AG sales or support representative for assistance. |
| MLC9006 | License converted to assembler output records written to output file |
| Explanation |
The license file was successfully converted to an assembler source module. Output records were written to the output file. |
| Action |
No action is required for this informational message. |
| MLC9007 | Error loading license module modulename errorcode |
| Explanation |
The LOADLIC function (z/OS only) tried to load a license module from the load library and received an error (errorcode) from the operating system. |
| Action |
Correct the LICUTIL input, removing duplicate LICUTIL function calls. Check that the license module (modulename) is in the load library, that the correct library is referenced in the JCL, and that the module name is specified correctly in the LOADLIC statement (case sensitive, a blank between LOADLIC and modulename). |
| MLC9009 | DMS Error |
| Explanation |
A DMS error occurred (only in BS2000 environments). |
| Action |
Investigate the cause of the BS2000 DMS error. If you need assistance, contact your Software AG support representative. |
| MLC9010 | LOADLIC can only be issued once, before any DISPLAY, CHECK, MAKE or READ |
| Explanation |
The LOADLIC function (z/OS only) can only be performed once per LICUTIL session. LOADLIC must not be preceded by the DISPLAY, CHECK or READ function. These functions can only locate the license module after the LOADLIC. |
| Action |
Correct the LICUTIL input, removing duplicate LICUTIL function calls. Change the call order so that the LOADLIC precedes any DISPLAY, CHECK or READ. |