The following messages can appear during the processing of a Smalltalk application image under OS/390, CICS/ESA, or IMS/ESA.
ABTB1100E | Unable to Load Smalltalk VM Module (Single Image -- Load From File): VM= virtual_machine |
Explanation: While attempting to run an OS/390 Native application load module in a load from file scenario, the system could not locate the specified virtual machine needed to run the application.
Issuing module: ABTBMN
System Action: The system fails the application.
User Response: The JCL used to run the application load module is missing the ABT.V4R5M0.SABTLOAD data set from the STEPLIB statement. For an example of the correct JCL used to run OS/390 Native application load modules, see member ABTBEXEC in data set ABT.V4R5M0.SABTJLIB.
ABTB1101E | Smalltalk VM exception occurred, RC= return_code |
Explanation: While attempting to run an OS/390 Native application load module in a load from file scenario, the system encountered a primitive error in the specified virtual machine.
Issuing module: ABTBMN
System Action: The system fails the application.
User Response: See the primitive error code table in the IBM Smalltalk Programmer's Reference for a description of the return_code.
ABTB1102E | Failure: Abend Code= abend_code, Reason Code= reason_code |
Explanation: While attempting to run an OS/390 Native application load module in a load from file scenario, the application abnormally ended.
Issuing module: ABTBMN
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code.
ABTB1103E | Unable to Load Smalltalk VM Module (Single Image -- Static Link): VM= virtual_machine |
Explanation: While attempting to run an OS/390 Native application load module in a single image, static link scenario, the system could not locate the specified virtual machine needed to run the application.
Issuing module: ABTBMN1
System Action: The system fails the application.
User Response: The JCL used to run the application load module is missing the ABT.V4R5M0.SABTLOAD data set from the STEPLIB statement. For an example of the correct JCL used to run OS/390 Native application load modules, see member ABTBEXEC in data set ABT.V4R5M0.SABTJLIB.
ABTB1104E | Smalltalk VM exception occurred, RC= return_code |
Explanation: While attempting to run an OS/390 Native application load module in a single image, static link scenario, the system encountered a primitive error in the specified virtual machine.
Issuing module: ABTBMN1
System Action: The system fails the application.
User Response: See the primitive error code table in the IBM Smalltalk Programmer's Reference for a description of the return_code.
ABTB1105E | Failure: Abend Code= abend_code, Reason Code= reason_code |
Explanation: While attempting to run an OS/390 Native application load module in a single image, static link scenario, the application abnormally ended.
Issuing module: ABTBMN1
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code.
ABTB1106E | Unable to Load Smalltalk VM Module (Dual Image): VM= virtual_machine |
Explanation: While attempting to run an OS/390 Native application load module in a dual image scenario, the system could not locate the specified virtual machine needed to run the application.
Issuing module: ABTBMN2
System Action: The system fails the application.
User Response: The JCL used to run the application load module is missing the ABT.V4R5M0.SABTLOAD data set from the STEPLIB statement. For an example of the correct JCL used to run OS/390 Native application load modules, see member ABTBEXEC in data set ABT.V4R5M0.SABTJLIB.
ABTB1107E | Smalltalk VM exception occurred, RC= return_code |
Explanation: While attempting to run an OS/390 Native application load module in a dual image scenario, the system encountered a primitive exception error in the specified virtual machine.
Issuing module: ABTBMN2
System Action: The system fails the application.
User Response: See the primitive error code table in the IBM Smalltalk Programmer's Reference for a description of the return_code.
ABTB1108E | Failure: Abend Code= abend_code, Reason Code= reason_code |
Explanation: While attempting to run an OS/390 Native application load module in a dual image scenario, the application abnormally ended.
Issuing module: ABTBMN2
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code.
ABTB1109E | Failure: Abend Code= abend_code, Reason Code= reason_code |
Explanation: While attempting to access the OS/390 Native virtual machine, an abend occurred.
Issuing module: ABTBVM1
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code.
ABTB1110E | Failure: Abend Code= abend_code, Reason Code= reason_code |
Explanation: While attempting to access the OS/390 Native virtual machine, an abend occurred.
Issuing module: ABTBVM2
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code.
ABTB1111E | -i (image) option was not specified |
Explanation: While performing the initialization step for an OS/390 Native application load module, the system found that the required image option was not specified.
Issuing module: ABTBNIT2
System Action: The system fails the initialization step.
User Response: Specify a valid image name and resubmit the job.
ABTB1112E | Unable to read image file from specified dataset, DSN= dataset_name |
Explanation: While performing the initialization step for an OS/390 Native application load module, the system was unable to read the specified image file.
Issuing module: ABTBNIT2
System Action: The system fails the initialization step.
User Response: Ensure that your JCL refers to the correct image name. If it does, it is possible that the image is not valid. Re-packaged the image on the workstation and make sure you upload it to OS/390 as binary.
ABTB1113E | -b (base VM) option was not specified |
Explanation: While performing the initialization step for an OS/390 Native application load module in a dual scenario, the system found that the required base module option was not specified.
Issuing module: ABTBNIT2
System Action: The system fails the initialization step.
User Response: Specify a valid base image name and resubmit the job.
ABTB1114E | Unable to Load Smalltalk VM Module (Dual Image): VM= virtual_machine |
Explanation: While performing the initialization step for an OS/390 Native application load module in a dual image scenario, the system could not locate the specified virtual machine needed to run the application.
Issuing module: ABTBNIT2
System Action: The system fails the initialization step.
User Response: The JCL used to run the application load module is missing the ABT.V4R5M0.SABTLOAD data set from the STEPLIB statement. For an example of the correct JCL used to run OS/390 Native application load modules, see member ABTBEXEC in data set ABT.V4R5M0.SABTJLIB.
ABTB1115E | Smalltalk Dependent Image Initialization, RC= return_code |
Explanation: The initialization step for a dependent OS/390 Native application load module has completed. If return_code is zero, the initialization completed successfully.
Issuing module: ABTBNIT2
System Action: The system continues processing.
User Response: If the return code is zero, no action is required. For a non-zero return code, see the primitive error code table in the IBM Smalltalk Programmer's Reference for a description of the return_code.
ABTB1116E | Argument Required: Smalltalk-Module-Name |
Explanation: While attempting to query an OS/390 Native application load module, the system found that the Smalltalk module name was not specified.
Issuing module: ABTBQMOD
System Action: The system fails the module query.
User Response: Specify a valid image name and resubmit the query request.
ABTB1117E | Module module_name Load Request Failed, RESP= response_code |
Explanation: While attempting to query an OS/390 Native application load module, the system could not load the specified module.
Issuing module: ABTBQMOD
System Action: The system fails the query request.
User Response: Ensure that the image you are attempting to query is a valid Smalltalk image. See OS/390 system codes for a description of the response_code.
ABTB1118E | module_name is not a Smalltalk Module |
Explanation: While attempting to query an OS/390 Native application load module, the system determined that the specified module is not a Smalltalk module.
Issuing module: ABTBQMOD
System Action: The system fails the query request.
User Response: Specify a valid image name and resubmit the request.
ABTB1119E | Unable to Load Virtual Machine, VM= virtual_machine, RESP= response_code |
Explanation: While attempting to query an OS/390 Native application load module, the system could not load the virtual machine to complete the query.
Issuing module: ABTBQMOD
System Action: The system fails the query request.
User Response: Ensure that the image you are attempting to query was properly built as a load module. See OS/390 system codes for more information about the response_code.
ABTB1120E | virtual_machine is not a valid Smalltalk Virtual Machine |
Explanation: While attempting to query an OS/390 Native application load module, the system determined that the referenced virtual machine module is not a valid Smalltalk virtual machine.
Issuing module: ABTBQMOD
System Action: The system fails the query request.
User Response: Either the JCL with which you are querying the image does not point to the correct Smalltalk virtual machine, or the image was not properly built as a load module. Ensure that the JCL you are using to query the image is correct, then resubmit the job. If the error persists, rebuild the image as a load module and attempt to query it again.
ABTB1121I | Smalltalk Module Summary text |
Explanation: Displays the result of an OS/390 Native application load module query command. text is as follows:
Image Name : imagename VM Module : modulename Image Type : {Single Image | Dependent Image | Not Recognized} [Base Image : basename] Execution Mode : {Static Link | Load from File | Not Recognized} Created (Date) : date Version : version [Perf Instrumentation : On] [Cmd Line Arguments : args] * Virtual Machine * VM Module : modulename VM Type : {Single Image VM | Dual Image VM | Not Recognized} Created (Date) : date Version : version
The Perf Instrumentation line appears only when performance instrumentation has been turned on. The Cmd Line Arguments line appears only when command line arguments have been specified. The Base Image line appears only when the module being queried is a dependent image and requires the named base image to run.
Issuing module: ABTBQMOD
System Action: The system continues processing.
User Response: No action is required.
ABTB1122E | Module module_name Load Request Failed, RESP= response_code |
Explanation: While attempting to query the OS/390 Native image control table, the system could not load the specified module.
Issuing module: ABTBQMOD
System Action: The system fails the query request.
User Response: Ensure that the image control table you are attempting to query has been properly set up. See OS/390 system codes for a description of the response_code.
ABTB1123I | Smalltalk Image Control Table Summary version text |
Explanation: Displays the result of an OS/390 Native image control table query command. text is as follows:
imagemodule Timestamp: date @ time number. DSN= dataset
Issuing module: ABTBQMOD
System Action: The system continues processing.
User Response: No action is required.
ABTC1200E | Failure: Abend Code= abend_code Reason Code= reason_code |
Explanation: While attempting to access a CICS Smalltalk base module, the system abnormally ended.
Issuing module: ABTCBAS1
System Action: The system fails the request.
User Response: See OS/390 system codes for the abend_code and reason_code.
ABTC1201E | Smalltalk failure, Abend Code= abend_code |
Explanation: While attempting to access a CICS Smalltalk base module, the system encountered a Smalltalk failure and abnormally ended.
Issuing module: ABTCBAS1
System Action: The system fails the request.
User Response: See OS/390 system codes for the abend_code.
ABTC1202E | Unable to Load Smalltalk VM Module (Single Image -- Load From File): VM= virtual_machine |
Explanation: While attempting to run a CICS application load module in a load from file scenario, the system could not locate the specified virtual machine needed to run the application.
Issuing module: ABTCMN
System Action: The system fails the application.
User Response: The CICS DFHRPL concatenation is missing the ABT.V4R5M0.SABTLOAD data set. Add this data set to the concatenation.
ABTC1203E | Smalltalk failure, Abend Code= abend_code |
Explanation: While attempting to run a CICS application load module in a load from file scenario, the system abnormally ended.
Issuing module: ABTCMN
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code.
ABTC1204E | Smalltalk VM exception occurred, RC= return_code |
Explanation: While attempting to run a CICS application load module in a load from file scenario, the system encountered a protection exception error in the specified virtual machine.
Issuing module: ABTCMN
System Action: The system fails the application.
User Response: See the primitive error code table in the IBM Smalltalk Programmer's Reference for a description of the return_code.
ABTC1205E | Unable to Load Smalltalk VM Module (Single Image -- Static Link): VM= virtual_machine |
Explanation: While attempting to run a CICS application load module in a single image, static link scenario, the system could not locate the specified virtual machine needed to run the application.
Issuing module: ABTCMN1
System Action: The system fails the application.
User Response: The CICS DFHRPL concatenation is missing the ABT.V4R5M0.SABTLOAD data set. Add this data set to the concatenation.
ABTC1206E | Smalltalk failure, Abend Code= abend_code |
Explanation: While attempting to run a CICS application load module in a single image, static link scenario, the system encountered a Smalltalk failure and abnormally ended the application.
Issuing module: ABTCMN1
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code.
ABTC1207E | Smalltalk VM exception occurred, RC= return_code |
Explanation: While attempting to run a CICS application load module in a single image, static link scenario, the system encountered a protection exception error in the specified virtual machine.
Issuing module: ABTCMN1
System Action: The system fails the application.
User Response: See the primitive error code table in the IBM Smalltalk Programmer's Reference for a description of the return_code.
ABTC1208E | Unable to Load Smalltalk VM Module (Dual Image): VM= virtual_machine |
Explanation: While attempting to run a CICS application load module in a dual image scenario, the system could not locate the specified virtual machine needed to run the application.
Issuing module: ABTCMN2
System Action: The system fails the application.
User Response: The CICS DFHRPL concatenation is missing the ABT.V4R5M0.SABTLOAD data set. Add this data set to the concatenation.
ABTC1209E | Smalltalk failure, Abend Code= abend_code |
Explanation: While attempting to run a CICS application load module in a dual image scenario, the application abnormally ended.
Issuing module: ABTCMN2
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code.
ABTC1210E | Smalltalk VM exception occurred, RC= return_code |
Explanation: While attempting to run a CICS application load module in a dual image scenario, the system encountered a protection exception error in the specified virtual machine.
Issuing module: ABTCMN2
System Action: The system fails the application.
User Response: See the primitive error code table in the IBM Smalltalk Programmer's Reference for a description of the return_code.
ABTC1211E | -i (image) option was not specified |
Explanation: While performing the initialization step for a CICS application load module, the system found that the required image option was not specified.
Issuing module: ABTCNIT2
System Action: The system fails the initialization step.
User Response: Specify a valid image name and resubmit the job.
ABTC1212E | Unable to read image file from specified dataset, DSN= dataset_name |
Explanation: While performing the initialization step for a CICS application load module, the system was unable to read the specified image file.
Issuing module: ABTCNIT2
System Action: The system fails the initialization step.
User Response: Ensure that your JCL refers to the correct image name. If it does, it is possible that the image is not valid. Re-packaged the image on the workstation and make sure you upload it as binary.
ABTC1213E | -b (base VM) option was not specified |
Explanation: While performing the initialization step for a CICS application load module in a dual scenario, the system found that the required base module option was not specified.
Issuing module: ABTCNIT2
System Action: The system fails the initialization step.
User Response: Specify a valid base image name and resubmit the job.
ABTC1214E | Unable to Load Smalltalk VM Module (Dual Image): VM= virtual_machine |
Explanation: While performing the initialization step for a CICS application load module in a dual image scenario, the system could not locate the specified virtual machine needed to run the application.
Issuing module: ABTCNIT2
System Action: The system fails the initialization step.
User Response: The CICS DFHRPL concatenation is missing the ABT.V4R5M0.SABTLOAD data set. Add this data set to the concatenation.
ABTC1215E | Smalltalk Dependent Image Initialization, RC= return_code |
Explanation: The initialization step for a dependent CICS application load module has completed. If return_code is zero, the initialization completed successfully.
Issuing module: ABTCNIT2
System Action: The system continues processing.
User Response: If the return code is zero, no action is required. For a non-zero return code, see the primitive error code table in the IBM Smalltalk Programmer's Reference for a description of the return_code.
ABTC1216E | Argument Required: Smalltalk-Module-Name |
Explanation: While attempting to query a CICS application load module, the system found that the Smalltalk module name was not specified.
Issuing module: ABTCQMOD
System Action: The system fails the module query.
User Response: Specify a valid image name and resubmit the query request.
ABTC1217E | Module module_name Load Request Failed, RESP= response_code |
Explanation: While attempting to query a CICS application load module, the system could not load the specified module.
Issuing module: ABTCQMOD
System Action: The system fails the query request.
User Response: Ensure that the image you are attempting to query is a valid Smalltalk image. See OS/390 system codes for a description of the response_code.
ABTC1218E | module_name is not a Smalltalk Module |
Explanation: While attempting to query a CICS application load module, the system determined that the specified module is not a Smalltalk module.
Issuing module: ABTCQMOD
System Action: The system fails the query request.
User Response: Specify a valid image name and resubmit the request.
ABTC1219E | Unable to Load Virtual Machine, VM= virtual_machine, RESP= response_code |
Explanation: While attempting to query a CICS application load module, the system could not load the virtual machine to complete the query.
Issuing module: ABTCQMOD
System Action: The system fails the query request.
User Response: Ensure that the image you are attempting to query was properly built as a load module. See OS/390 system codes for the response_code.
ABTC1220E | virtual_machine is not a valid Smalltalk Virtual Machine |
Explanation: While attempting to query a CICS application load module, the system determined that the referenced virtual machine module is not a valid Smalltalk virtual machine.
Issuing module: ABTCQMOD
System Action: The system fails the query request.
User Response: Either the JCL with which you are querying the image does not point to the correct Smalltalk virtual machine, or the image was not properly built as a load module. Ensure that the JCL you are using to query the image is correct, then resubmit the job. If the error persists, rebuild the image as a load module and attempt to query it again.
ABTC1221I | Smalltalk Module Summary text |
Explanation: Displays the result of a CICS application load module query command. text is as follows:
Image Name : imagename VM Module : modulename Image Type : {Single Image | Dependent Image | Not Recognized} [Base Image : basename] Execution Mode : {Static Link | Load from File | Not Recognized} Created (Date) : date Version : version [Perf Instrumentation : On] [Cmd Line Arguments : args] * Virtual Machine * VM Module : modulename VM Type : {Single Image VM | Dual Image VM | Not Recognized} Created (Date) : date Version : version
The Perf Instrumentation line appears only when performance instrumentation has been turned on. The Cmd Line Arguments line appears only when command line arguments have been specified. The Base Image line appears only when the module being queried is a dependent image and requires the named base image to run.
Issuing module: ABTCQMOD
System Action: The system continues processing.
User Response: No action is required.
ABTC1240E | Module module_name Load Request Failed, RESP= response_code |
Explanation: While attempting to query the CICS image control table, the system could not load the specified module.
Issuing module: ABTCQMOD
System Action: The system fails the query request.
User Response: Ensure that the image control table you are attempting to query has been properly set up. See the appropriate documentation for a description of the response_code.
ABTC1241I | Smalltalk Image Control Table Summary version text text |
Explanation: Displays the result of a CICS image control table query command. text is as follows:
imagemodule Timestamp: date @ time number. DSN= dataset
Issuing module: ABTCQMOD
System Action: The system continues processing.
User Response: No action is required.
ABTC1244E | Smalltalk load from file failed, Abend Code= abend_code, Return code= return_code text |
Explanation: A failure occurred while Smalltalk attempted to load the image from file.text is as follows:
Transaction: transid Dataset: dataset Member: member
Issuing module: ABTCBAS1
System Action: The system fails the transaction.
User Response: See the reason code under CICS abend code S615.
ABTI1300E | Failure: Abend Code= abend_code Reason Code= reason_code |
Explanation: While attempting to run an IMS application load module, the system abnormally ended.
Issuing module: ABTICC
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code and reason_code.
ABTI1301E | Failure: Abend Code= abend_code Reason Code= reason_code |
Explanation: While attempting to run an IMS application load module, the system abnormally ended.
Issuing module: ABTIFM
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code and reason_code.
ABTI1302E | Failure: Abend Code= abend_code Reason Code= reason_code |
Explanation: While attempting to run an IMS application load module, the system abnormally ended.
Issuing module: ABTIFM1
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code and reason_code.
ABTI1303E | Failure: Abend Code= abend_code Reason Code= reason_code |
Explanation: While attempting to run an IMS application load module, the system abnormally ended.
Issuing module: ABTIFM1
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code and reason_code.
ABTI1304E | Failure: Abend Code= abend_code Reason Code= reason_code |
Explanation: While attempting to run an IMS application load module, the system abnormally ended.
Issuing module: ABTIMN
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code and reason_code.
ABTI1305E | Failure: Abend Code= abend_code Reason Code= reason_code |
Explanation: While attempting to run an IMS application load module, the system abnormally ended.
Issuing module: ABTIMN1
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code and reason_code.
ABTI1306E | Failure: Abend Code= abend_code Reason Code= reason_code |
Explanation: While attempting to run an IMS application load module, the system abnormally ended.
Issuing module: ABTIMN2
System Action: The system fails the application.
User Response: See OS/390 system codes for the abend_code and reason_code.
ABTI1307E | -i (image) option was not specified |
Explanation: While performing the initialization step for an IMS application load module, the system found that the required image option was not specified.
Issuing module: ABTINIT2
System Action: The system fails the initialization step.
User Response: Specify a valid image name and resubmit the job.
ABTI1308E | Unable to read image file from specified dataset, DSN= dataset_name |
Explanation: While performing the initialization step for an IMS application load module, the system was unable to read the specified image file.
Issuing module: ABTINIT2
System Action: The system fails the initialization step.
User Response: Ensure that your JCL refers to the correct image name. If it does, it is possible that the image is not valid. Re-packaged the image on the workstation and make sure you upload it as binary.
ABTI1309E | -b (base VM) option was not specified |
Explanation: While performing the initialization step for an IMS application load module in a dual scenario, the system found that the required base module option was not specified.
Issuing module: ABTINIT2
System Action: The system fails the initialization step.
User Response: Specify a valid base image name and resubmit the job.
ABTI1310E | Unable to Load Smalltalk VM Module (Dual Image): VM= virtual_machine |
Explanation: While performing the initialization step for an IMS application load module in a dual image scenario, the system could not locate the specified virtual machine needed to run the application.
Issuing module: ABTINIT2
System Action: The system fails the initialization step.
User Response: The JCL used to run the application load module is missing the ABT.V4R5M0.SABTLOAD data set from the STEPLIB statement.
ABTI1311E | Smalltalk Dependent Image Initialization, RC= return_code |
Explanation: The initialization step for a dependent IMS application load module has completed. If return_code is zero, the initialization completed successfully.
Issuing module: ABTINIT2
System Action: The system continues processing.
User Response: If the return code is zero, no action is required. For a non-zero return code, see the primitive error code table in the IBM Smalltalk Programmer's Reference for a description of the return_code.
ABTI1316E | Argument Required: Smalltalk-Module-Name |
Explanation: While attempting to query an IMS application load module, the system found that the Smalltalk module name was not specified.
Issuing module: ABTIQMOD
System Action: The system fails the module query.
User Response: Specify a valid image name and resubmit the query request.
ABTI1317E | Module module_name Load Request Failed, RESP= response_code |
Explanation: While attempting to query an IMS application load module, the system could not load the specified module.
Issuing module: ABTIQMOD
System Action: The system fails the query request.
User Response: Ensure that the image you are attempting to query is a valid Smalltalk image. See OS/390 system codes for the response_code.
ABTI1318E | module_name is not a Smalltalk Module |
Explanation: While attempting to query an IMS application load module, the system determined that the specified module is not a Smalltalk module.
Issuing module: ABTIQMOD
System Action: The system fails the query request.
User Response: Specify a valid image name and resubmit the request.
ABTI1319E | Unable to Load Virtual Machine, VM= virtual_machine, RESP= response_code |
Explanation: While attempting to query an IMS application load module, the system could not load the virtual machine to complete the query.
Issuing module: ABTIQMOD
System Action: The system fails the query request.
User Response: Ensure that the image you are attempting to query was properly built as a load module. See OS/390 system codes for the response_code.
ABTI1320E | virtual_machine is not a valid Smalltalk Virtual Machine |
Explanation: While attempting to query an IMS application load module, the system determined that the referenced virtual machine module is not a valid Smalltalk virtual machine.
Issuing module: ABTIQMOD
System Action: The system fails the query request.
User Response: Either the JCL with which you are querying the image does not point to the correct Smalltalk virtual machine, or the image was not properly built as a load module. Ensure that the JCL you are using to query the image is correct, then resubmit the job. If the error persists, rebuild the image as a load module and attempt to query it again.
ABTI1321I | Smalltalk Module Summary text |
Explanation: Displays the result of an IMS application load module query command. text is as follows:
Image Name : imagename VM Module : modulename Image Type : {Single Image | Dependent Image | Not Recognized} [Base Image : basename] Execution Mode : {Static Link | Load from File | Not Recognized} Created (Date) : date Version : version [Perf Instrumentation : On] [Cmd Line Arguments : args] * Virtual Machine * VM Module : modulename VM Type : {Single Image VM | Dual Image VM | Not Recognized} Created (Date) : date Version : versionThe Perf Instrumentation line appears only when performance instrumentation has been turned on. The Cmd Line Arguments line appears only when command line arguments have been specified. The Base Image line appears only when the module being queried is a dependent image and requires the named base image to run.
Issuing module: ABTIQMOD
System Action: The system continues processing.
User Response: No action is required.
ABTI1322E | Module module_name Load Request Failed, RESP= response_code |
Explanation: While attempting to query the IMS image control table, the system could not load the specified module.
Issuing module: ABTIQMOD
System Action: The system fails the query request.
User Response: Ensure that the image control table you are attempting to query has been properly set up. See OS/390 system codes for the response_code.
ABTI1323I | Smalltalk Image Control Table Summary version text |
Explanation: Displays the result of an IMS image control table query command. text is as follows:
imagemodule Timestamp: date @ time number. DSN= dataset
Issuing module: ABTIQMOD
System Action: The system continues processing.
User Response: No action is required.
ABTX1000I | Smalltalk Single Image Initialization, RC=return_code |
Explanation: Displays the result of the initialization of a single image. If the return_code is zero, the initialization completed successfully. If the return_code is non-zero, the initialization failed.
Issuing module: ABTXNIT1
System Action: If return_code is zero, the system continues processing. If return_code is non-zero, the system fails the job step.
User Response: For a return code of zero, ignore the message. For a non-zero return code, see the primitive error code table in the IBM Smalltalk Programmer's Reference for a description of the return_code.
ABTX1001E | Failure: Abend Code=abend_code, Reason Code=reason_code |
Explanation: The system failed during initialization of an application image.
Issuing module: ABTXNIT1
System Action: The system fails the job step with the specified abend code and reason code.
User Response: See OS/390 system codes for the abend_code and reason_code.
ABTX1002E | Could not open input file: filename |
Explanation: While attempting to build a load module from an application image, the system could not open the specified input file.
Issuing module: ABTXSET
System Action: The system fails the job step.
User Response: Ensure that the input filename specified in the build JCL is correct and that the file exists.
ABTX1003E | Could not open output file: filename |
Explanation: While attempting to build a load module from an application image, the system could not open the specified output file.
Issuing module: ABTXSET
System Action: The system fails the job step.
User Response: Ensure that the output filename specified in the build JCL is correct and that the file exists.
ABTX1004E | Could not locate XHDR signature: signature |
Explanation: The ABTXSET JCL shipped with the product has been modified; the system cannot find the correct signature information.
Issuing module: ABTXSET
System Action: The system fails the job step.
User Response: Ensure that the ABTXSET jobstep statements conform to the build JCL procedures shipped with the product.
ABTX1005E | Expecting 4 arguments: ImageName, BaseImage, ExecType, ExecMode |
Explanation: While attempting to build a load module from an application image, the system determined that not enough required arguments were specified.
Issuing module: ABTXSET
System Action: The system fails the job step.
User Response: Update the JCL to include the required arguments.
ABTX1006E | Arg 1 -- Image Name -- Invalid Length |
Explanation: While attempting to build a load module from an application image, the system found that the image name specified in the JCL was of an incorrect length.
Issuing module: ABTXSET
System Action: The system fails the job step.
User Response: Update the image name specification in the build load module JCL. The name must adhere to OS/390 naming conventions.
ABTX1007E | Arg 2 -- VM Name -- Invalid Length |
Explanation: While attempting to build a load module from an application image, the system found that the virtual machine name specified in the JCL was of an incorrect length.
Issuing module: ABTXSET
System Action: The system fails the job step.
User Response: Update the VM name specification in the build load module JCL. The name must adhere to OS/390 naming conventions.
ABTX1008E | Arg 3 -- EXEC Type -- 1 or 2 |
Explanation: While attempting to build a load module from an application image, the system found that the execution type parameter specified in the IBM--supplied procedure was altered incorrectly.
Issuing module: ABTXSET
System Action: The system fails the job step.
User Response: Update the execution type parameter in the IBM-supplied procedure to indicate the type of module being built. For a single image, the execution type should be specified as a 1. For a dual image, the execution type should be specified as a 2.
ABTX1009E | Arg 4 -- EXEC Mode -- S, D or B |
Explanation: While attempting to build a load module from an application image, the system found that the execution mode parameter specified in the IBM--supplied procedure was altered incorrectly.
Issuing module: ABTXSET
System Action: The system fails the job step.
User Response: Update the execution mode parameter in the IBM-supplied procedure to indicate the mode of the module being built. For a single image, the execution mode should be specified as S. For a dependent image, the execution mode should be specified as D. For a base image, the execution mode should be specified as B.
ABTX1010I | Smalltalk Image Build Summary text |
Explanation: Displays the build summary of an image module to load module conversion. text is as follows:
Image Name : imagename VM Module : modulename Image Type : {Single Image VM | Dual Image VM | Not Recognized} Execution Mode : {Static Link | Load from File | Not Recognized} Created (Date) : date Version : version [Perf Instrumentation : On] [Cmd Line Arguments : args]
The Perf Instrumentation line appears only when performance instrumentation has been turned on. The Cmd Line Arguments line appears only when command line arguments have been specified.
Issuing module: ABTXSET
System Action: The system continues processing.
User Response: If Not Recognized appears in the message, the module's image type or execution mode is not valid. Correct the problem and query the module again. Otherwise, no action is required.
ABTX1022I | Smalltalk Image Conversion, RC=image_conversion_code |
Explanation: Displays the result of the conversion step of an image. If the image_conversion_code is zero, the conversion completed successfully. If the image_conversion_code is non-zero, the conversion failed.
Issuing module: ABTXCONV
System Action: If image_conversion_code is zero, the system continues processing. If image_conversion_code is non-zero, the system fails the job step.
User Response: For a return code of zero, ignore the message. For a non-zero return code, see Image conversion errors for the image_conversion_code.
ABTX1023I | Number of Days = days |
Explanation: Indicates the aging specification for the records of a stack dump data set. Any records older than this specification are removed from the stack dump data set.
Issuing module: ABTXSDFN
System Action: The system continues processing.
User Response: No action is required.
ABTX1024E | Usage is: PARM='x' where x is number of days to keep |
Explanation: Indicates the aging specification needed to delete records from the stack dump data set.
Issuing module: ABTXSDFN
System Action: The system continues processing.
User Response: Specify a value for the aging specification. The aging parameter indicates the number of days records should be kept in the stack dump data set. Records older than the aging specification are removed from the stack dump data set.
ABTX1025I | Input Dataset is empty - nothing to archive |
Explanation: The aging specification indicated that records should be deleted from the stack dump data set, but the stack dump data set is empty.
Issuing module: ABTXSDFN
System Action: The system continues processing.
User Response: No action is required.
ABTX1026E | Could not open input file - DD:STAKDUMP |
Explanation: The system attempted to perform an aging operation on the stack dump data set but was unable to open the data set.
Issuing module: ABTXSDFN
System Action: The system fails the aging operation.
User Response: Ensure that the stack dump data set is a valid VSAM data set. If it is, check that the data set has been properly set up. See the appropriate program directory documentation for more information.
ABTX1027E | Could not open output file - DD:OUTFILE |
Explanation: The system attempted to perform an aging opertation on the stack dump data set but was unable to open the data set into which the altered stack dump records were to be written.
Issuing module: ABTXSDFN
System Action: The system fails the aging operation.
User Response: Ensure that the output data set, specified with a DD name of OUTFILE, is a valid VSAM data set. If it is, check that the data set has been properly set up. See the appropriate program directory documentation for more information.
ABTX1028I | No records moved |
Explanation: The aging operation found no records old enough to be removed from the stack dump data set.
Issuing module: ABTXSDFN
System Action: The system continues processing.
User Response: No action is required.
ABTX1029E | Read error |
Explanation: During the aging operation, the process of reading the records from the stack dump data set encountered an error.
Issuing module: ABTXSDFN
System Action: The system fails the aging operation.
User Response: Ensure that the stack dump data set is a valid VSAM data set. If this error persists, contact the IBM Support Center.
ABTX1030E | Write error, Writelen= length |
Explanation: During the aging operation, the process of writing the valid records to a new stack dump data set encountered an error.
Issuing module: ABTXSDFN
System Action: The system fails the aging operation.
User Response: Ensure that the output data set, specified with a DD name of OUTFILE, is a valid VSAM data set. If the error persists, contact the IBM Support Center.
ABTX1031E | VSAM Return Code= return_code, Feedback Code= feedback_code |
Explanation: The aging operation failed because the stack dump data set or the output data set is not a valid VSAM data set.
Issuing module: ABTXSDFN
System Action: The system fails the aging operation.
User Response: Determine the failure by referring to the proper VSAM documentation describing the return_code and feedback_code.
ABTX1032E | VSAM Error, R15 Value= error_code, Feedback Code= feedback_code, RBA= rba, Last_op= operation, Myerrno= error_number |
Explanation: The aging operation failed because the stack dump data set or the output data set is not a valid VSAM data set.
Issuing module: ABTXSDFN
System Action: The system fails the aging operation.
User Response: Determine the failure by referring to the proper VSAM documentation describing the error.
ABTX1033E | VGET failed -- exiting, RC = return_code |
Explanation: An ISPF error occurred while attempting to access the stack dump panel.
Issuing module: ABTXSDFL
System Action: The system fails to display the stack dump panel.
User Response: Determine the failure by referring to the ISPF documentation describing the return_code.
ABTX1034E | Display of ABTPANEL failed, RC= return_code |
Explanation: An ISPF error occurred while attempting to open the stack dump panel.
Issuing module: ABTXSDFL
System Action: The system fails to display the stack dump panel.
User Response: Determine the failure by referring to the ISPF documentation describing the return_code.
ABTX1035E | TBCREATE failed, RC= return_code |
Explanation: An ISPF error occurred while attempting to create the table displaying valid stack dumps on the stack dump panel.
Issuing module: ABTXSDFL
System Action: No stack dumps are displayed.
User Response: Determine the failure by referring to the ISPF documentation describing the return_code.
ABTX1036E | FLOCATE failed, RC= return_code |
Explanation: An ISPF error occurred while attempting to locate the stack dump you are an attempting to access.
Issuing module: ABTXSDFL
System Action: The system continues processing but does not export the specified data set.
User Response: Determine the failure by referring to the ISPF documentation describing the return_code.
ABTX1037E | Read error -- ferror() |
Explanation: The system could not read the data from the specified stack dump data set.
Issuing module: ABTXSDFL
System Action: The system does not export the specified stack dump.
User Response: Ensure that the specified stack dump data set has been properly set up.
ABTX1038E | EOF encountered -- feof() |
Explanation: The specified stack dump could not be located in the stack dump data set before reaching the end of the data set.
Issuing module: ABTXSDFL
System Action: The system does not export the stack dump.
User Response: Ensure that the stack dump data set contains the stack dump you are attempting to access. The stack dump might have been aged off of the stack dump data set.
ABTX1039E | TBADD failed, RC= return_code |
Explanation: An ISPF error occurred while attempting to add a stack dump entry to the table on the stack dump panel.
Issuing module: ABTXSDFL
System Action: The system does not add the stack dump entry to the stack dump table.
User Response: Determine the failure by referring to the ISPF documentation describing the return_code.
ABTX1040E | TBSORT failed, RC= return_code |
Explanation: An ISPF error occurred while attempting to sort the stack dump entries on the table on the stack dump panel.
Issuing module: ABTXSDFL
System Action: The system does not sort the stack dump entries on the stack dump table.
User Response: Determine the failure by referring to the ISPF documentation describing the return_code.
ABTX1041E | TBDISPL failed, RC= return_code |
Explanation: An ISPF error occurred while display the table on the stack dump panel.
Issuing module: ABTXSDFL
System Action: The system does not display the stack dump table.
User Response: Determine the failure by referring to the ISPF documentation describing the return_code.
ABTX1042E | TBSORT--USER failed, RC= return_code |
Explanation: An ISPF error occurred while attempting to sort the entries in the USER column of the table on the stack dump panel.
Issuing module: ABTXSDFL
System Action: The system does not sort the USER column on the stack dump table.
User Response: Determine the failure by referring to the ISPF documentation describing the return_code.
ABTX1043E | TBSORT--PROGRAM failed, RC= return_code |
Explanation: An ISPF error occurred while attempting to sort the entries in the PROGRAM column of the table on the stack dump panel.
Issuing module: ABTXSDFL
System Action: The system does not sort the PROGRAM column of the stack dump table.
User Response: Determine the failure by referring to the ISPF documentation describing the return_code.
ABTX1044E | TBSORT--TRANID failed, RC= return_code |
Explanation: An ISPF error occurred while attempting to sort the entries in the TRANID column of the stack dump panel.
Issuing module: ABTXSDFL
System Action: The system does not sort the TRANID column of the stack dump table.
User Response: Determine the failure by referring to the ISPF documentation describing the return_code.
ABTX1045E | TBSORT--DATETIME failed, RC= return_code |
Explanation: An ISPF error occurred while attempting to sort the entries in the DATETIME column of the table on the stack dump panel.
Issuing module: ABTXSDFL
System Action: The system does not sort the DATETIME column of the stack dump table.
User Response: Determine the failure by referring to the ISPF documentation describing the return_code.
ABTX1046E | Panel not found: ABTXSDFM, RC= return_code |
Explanation: An error occurred when ISPF could not find the ABTXSDFM panel it tried to display.
Issuing module: ABTXSDFL
System Action: The system does not display the specified panel.
User Response: Contact the IBM Support Center.
ABTX1047E | Key not found on EXPORT, KEY= key, RC= return_code |
Explanation: While attempting to export the selected stack dump to an export stack dump data set, an error occurred when the system could not locate the key needed to perform the export operation.
Issuing module: ABTXSDFL
System Action: The system does not export the stack dump.
User Response: Contact the IBM Support Center.
ABTX1048E | Write failed: WRITELEN= length |
Explanation: While attempting to export the selected stack dump to the export stack dump data set, an error occurred when the system was unable to write into the export data set.
Issuing module: ABTXSDFL
System Action: The system does not export the stack dump.
User Response: Ensure that the export stack dump data set has been properly set up with the correct DCB values.
ABTX1049E | Retype input file name and press enter to continue |
Explanation: While attempting to export the selected stack dump to the export stack dump data set, the system was unable to locate the input file name you specified.
Issuing module: ABTXSDFL
System Action: The system does not export the stack dump.
User Response: Specify a new input file name and press enter.
ABTX1050I | Copy operation completed without errors |
Explanation: Indicates that the export operation completed successfully.
Issuing module: ABTXSDFL
System Action: The system exports the stack dump.
User Response: No action is required.
ABTX1052E | Input file must be entered -- STACK VSAM file |
Explanation: While attempting to export the selected stack dump to the export stack dump data set, the system found that the required input file specification was not provided.
Issuing module: ABTXSDFL
System Action: The system does not export the stack dump.
User Response: Provide an input file name and resubmit the request.
ABTX1053E | Output file must be preallocated (PO or Sequential) with -- LRECL=24000,RECFM=F |
Explanation: While attempting to export the selected stack dump to the export stack dump data set, the system found that the data set into which the stack dump is to be exported is not a valid output data set.
Issuing module: ABTXSDFL
System Action: The system does not export the stack dump.
User Response: Ensure that the export stack dump data set has been properly set up with the correct DCB values.
ABTX1054E | No data found in Data Set -- input another Data Set Name with MAXLRECL=24080, and KEYLEN = 32 bytes |
Explanation: The system determined that the input data set from which you wish to view stack dumps is empty.
Issuing module: ABTXSDFL
System Action: The system continues processing.
User Response: Provide an input data set which contains the stack dump you wish to view.
ABTX1055E | Required field -- or use Data Set Name field |
Explanation: While attempting to export the selected stack dump to the export stack dump data set, the system could not export the data set because an output data set name was not specified.
Issuing module: ABTXSDFL
System Action: The system does not export the stack dump.
User Response: Specify a valid output data set for the exported stack dump.
ABTX1056E | Check input file -- should be VSAM with -- MACLRECL=24080, and KEYLEN = 32 bytes |
Explanation: The input from which you wish to view stack dumps is not valid.
Issuing module: ABTXSDFL
System Action: The system continues processing.
User Response: Provide a valid input data set from which stack dumps can be viewed.
ABTX1061E | Cannot run a image_type image under environment |
Explanation: An attempt was made to run an OS/390 Native image under a CICS environment or a CICS image under an OS/390 Native environment. VisualAge Smalltalk Server checks to ensure the correct type of image is being run for the appropriate environment.
Issuing module: ABTCMN, ABTCMN1, ABTCMN2, ABTBNM, ABTBMn1, or ABTBMN2
System Action: The system abends the application image.
User Response: Ensure that you are using the correct JCL build procedure to produce an
executable image for the desired environment.
Explanation: The INI parser was unable to open the temporary data set ABTASM.
Issuing module: ABTXIPRS
User Response: Check the JCL to ensure the data set is defined properly and that there is
enough space available. Explanation: The INI parser was unable to open the ini file specified.
Issuing module: ABTXIPRS
User Response: Check the JCL to ensure that the ABTINI parameter is pointing to the ini
file. Explanation: The load module specified could not be found or it is not an INI load
module.
Issuing module: ABTXIPRT
User Response: Ensure that the correct load module name was specified for the MODNAME
variable in the JCL ABTXIPRT and the load module is contained in one of the
data sets defined to the STEPLIB DD statement.ABTX1064E Unable to open file ABTASM
ABTX1065E Unable to open file INIFILE
ABTX1066E Unable to load module: xxxxxxxx
ABTX9999E | NLS Failure, RC=return_code (MSG# message_number) |
Explanation: The MVS Smalltalk NLS interface is not correctly installed. return_code can be one of the following:
Issuing module: Any message module
System Action: Processing of the utility or image continues. However, informational and error messages will not be properly produced.
User Response: Verify that the product was installed correctly. For CICS environments, ensure that the CICS DFHRPL concatenation contains the correct product release library (that is, ABT.V4R5M0.SABTLOAD) and that the CICS CSD GROUP(ABT) contains the latest product program definitions. For IMS or OS/390 Native environments, ensure that the image execution STEPLIB concatenation contains the correct product release library (that is, ABT.V4R5M0.SABTLOAD). If the problem persists, contact the IBM Support Center.