AWS Mainframe Modernization Service (Managed Runtime Environment experience) is no longer open to new customers. For capabilities similar to AWS Mainframe Modernization Service (Managed Runtime Environment experience) explore AWS Mainframe Modernization Service (Self-Managed Experience). Existing customers can continue to use the service as normal. For more information, see AWS Mainframe Modernization availability change.
AWS Blu Age Runtime Error Codes related to Utility Programs
Utility pgm error codes, prefixed with BA-U.
| Key | Severity | Text | Additional details |
|---|---|---|---|
BA-U1001 |
Warn | Input lilian seconds scale exceeds maximum scale. Maximum scale will be used instead. | |
BA-U2001 |
Error | Failed to process TrailerItem subclass encountered. Ensure the trailer item is supported. | |
BA-U2002 |
Error | Failed to parse TrailerItem argument. Ensure the trailer item arguments is supported. | |
BA-U2003 |
Error | Failed to process the DFSORT date format argument. Ensure the date format argument is supported. | |
BA-U2004 |
Error | Invalid input while extracting the Header1 from SortGrammar. Ensure Header1 string is well-formed and follows the expected structure. | |
BA-U2005 |
Error | Unexpected error while processing SortGrammar. Review exception details and verify input integrity and grammar parsing logic. | |
BA-U2006 |
Error | Feedback code CEE2F3: Failed to retrieve current system date and time. Check system clock configuration and timezone settings. | |
BA-U2007 |
Error | Feedback code CEE2EC: Failed to parse the date value passed to CEEDAYS or CEESECS. Ensure the date format is supported. | |
BA-U2008 |
Error | Feedback code CEE2EH: Input date/time in a CEEISEC, CEEDAYS, or CEESECS call was not within the valid range. Ensure the input date is within the supported range. | |
BA-U2009 |
Error | Feedback code CEE2EM: Failed to parse an input picture string in a call to a date/time service. Ensure the picture format is supported. | |
BA-U2010 |
Error | Feedback code CEE2EG: Input lilian date value was not within the valid range. Ensure the input lilian date is within the supported range. | |
BA-U2011 |
Fatal | Number of arguments received does not match expected number of arguments. Ensure the correct number of arguments is passed to the called program. | |
BA-U2012 |
Error | Failed to process DFSORT TIME argument. Ensure the format of the argument is correct. | |
BA-U2013 |
Error | Failed to process DFSORT TIMENS argument. Ensure the format of the argument is correct. | |
BA-U3001 |
Error | An error occurred while parsing SYSIN for INZUTILB programs. Verify SYSIN syntax and contact support if it should be supported. | |
BA-U3002 |
Error | Unable to detect database type. Defaulting to PostgreSQL. Verify database connection, driver configuration and ensure that the correct JDBC driver is loaded. | |
BA-U3003 |
Error | INZUTILB Unload operation failed. Review SYSIN commands syntax for INZUTILB utility, verify database connectivity. | |
BA-U3004 |
Error | SYSIN input is empty or contains no valid commands. Add at least one valid command (UNLOAD, SELECT, etc.) to SYSIN. | |
BA-U3005 |
Error | Required parameter OUTDDN is missing. Specify output dataset using OUTDDN(ddname) command in SYSIN. | |
BA-U3006 |
Error | Database type is not supported. Use one of the supported databases: PostgreSQL, Oracle, or DB2. | |
BA-U3007 |
Error | No formatter found for the database type when running INZUTILB program. Analyze whether the type should be considered and contact support for analyze. | |
BA-U3008 |
Error | Formatting not handled for the selected output format, DSNTIAUL format used instead. Check the output format in the control card or contact support if an implementation is needed. | |
BA-U3009 |
Error | Invalid mask parameter on PIC option. Verify your control card and use a valid mask. | |
BA-U3010 |
Error | Invalid sign parameter on PIC option. Accepted values are '-', '+', 'P' and 'V'. Verify your control card and use a valid parameter. | |
BA-U3012 |
Error | Unable to parse SYSIN for INZUTILB program. Check the above exception(s) and contact support for analysis. | |
BA-U3013 |
Error | INFUTILB Unload operation failed. Review SYSIN commands syntax for INFUTILB utility, verify database connectivity. | |
BA-U3014 |
Error | Invalid output file type for SYSPUNCH when running INFUTILB program. Consider using one of the following types: GDGSupportConfiguration, FileSystemFileConfiguration or DummyFileConfiguration. | |
BA-U3015 |
Error | No formatter found for the database type when running INFUTILB program. Analyze whether the type should be considered and contact support for analyze. | |
BA-U3016 |
Error | Missing record size for SYSPUNCH when running INFUTILB program. Set the record size in the file configuration or add it in the catalog. | |
BA-U3017 |
Error | Invalid output file type for SYSREC. Consider using one of the following types: GDGSupportConfiguration or FileSystemFileConfiguration. | |
BA-U3018 |
Error | Unsupported SQL query. Check the SQL query. | |
BA-U3019 |
Error | Unsupported column name. Check the table definition. | |
BA-U3020 |
Error | DFSIGDCB option: Unable to update LRECL of the SYSREC file. Consider using type FileSystemFileConfiguration, or remove DFSIGDCB option. | |
BA-U3021 |
Error | Splitting unload into chunks is not supported with the current database type. Use one of the supported databases: PostgreSQL or Oracle. | |
BA-U4001 |
Error | IDCAMS parsing error. The SYSIN content contains invalid syntax or unsupported commands. Review the SYSIN content for syntax errors or typos. Check the error message for details about what failed to parse. | |
BA-U5001 |
Error | Invalid POSITION option when calling DSNUTILB LOAD utility. Use a valid POSITION option. |