Server Guide

Abend codes

The following abend codes can appear during the processing of a Smalltalk application image under OS/390, CICS/ESA, or IMS/ESA.

04

Explanation: During DB2 call attach facility (CAF) processing, a CAF warning occurred. There is a release level mismatch between DB2 and the CAF code.

Module: DB2 CAF

User Response: Ensure that the target DB2 subsystem and the ABTBEXEC JCL are referencing the same DB2 release. The JCL substitution parameter DB2PRFX must match the DB2 subsystem release.

08 or 12

Explanation: During DB2 CAF processing, a DB2 connection error encountered. The DB2 subsystem is not available.

Module: DB2 CAF

User Response: Ensure that the target DB2 subsystem is started and is not in a DB2 STOP MODE=QUIESCE or FORCE status.

150

Explanation: The QMOD utility has attempted to load a module for processing and was unable to locate the module in the //STEPLIB concatenation list.

Module: ABTXLOAD

User Response: Ensure that the //STEPLIB concatenation contains the load module requested via the QMOD utility.

200

Explanation: During DB2 CAF processing, a CAF user error occurred, resulting from CAF protocol errors.

Module: DB2 CAF

User Response: See the DSNTRACE data for more information. Contact the IBM Support Center. CAF interface errors result in an OS/390 user abend, for which there is an associated DB2 reason code. See DB2 Diagnosis Guide and Reference for an explanation of the DB2 reason codes.

204

Explanation: During DB2 CAF processing, a CAF system error occurred.

Module: DB2 CAF

User Response: See the DSNTRACE data for more information. Contact the IBM Support Center. CAF interface errors result in an OS/390 user abend, for which there is an associated DB2 reason code. See DB2 Diagnosis Guide and Reference for an explanation of the DB2 reason codes.

S604

Explanation: During CICS processing, a dependent application image has incorrectly linked to a Smalltalk virtual machine intended for single images.

Module: CICS

User Response: Correct the JCL so that you build the dependent application image to link to a base image.

S606

Explanation: During CICS processing, a single application image has incorrectly linked to a Smalltalk virtual machine intended as a base image for dependent application images.

Module: CICS

User Response: Correct the JCL so that you build the single application image to link to a Smalltalk VM intended for single images.

S614

Explanation: During CICS processing, an attempt to load the image control table (ICT) failed.

Module: CICS

User Response: Ensure that the ABTXICT module has been successfully linkedited to a data set found in the CICS DFHRPL concatenation and that the program definition for ABTXICT is in an existing CICS RDO group. See ABT.V4R5M0.SABTJLIB(ABTCCSD) for an example of the CICS program definition for ABTXICT.

S615

Explanation: During CICS processing, an error occurred while attempting to load from file. A return code is provided with the abend:

Return Code
  Explanation

503
The organization for the accessed data set is incorrect. The organization must be specified as PO.

Action: Ensure that the data set organization is specified as PO.

506
The record format for the accessed data set is incorrect. The record format must be specified as F or FB.

Action: Ensure that the data set record format is specified as FB.

507
The image library list defined by the image control table (ICT) was searched and no corresponding packaged image name was found that matched the Smalltalk application name.

Action: Ensure that the packaged image associated with your Smalltalk application is available in a library specified by the ICT.

If you receive a return code other than those listed above, it is dynamic allocation error reason code from OS/390.

Module: CICS

S618

Explanation: During CICS processing, an error occurred while attempting to write the stack dump file.

Module: CICS

User Response: Probable causes of this abend code are as follows:

S630

Explanation: During CICS processing, your program encountered an error. A walkback has occurred.

Module: CICS

User Response: Use the stack dump created with the error to debug the problem.

S631

Explanation: During CICS processing, the system was unable to load the Smalltalk virtual machine.

Module: CICS

User Response: See the CICS log for the return code and contact the IBM Support Center.

S632

Explanation: During CICS processing, a Smalltalk virtual machine exception occurred.

Module: CICS

User Response: Occurs when a Smalltalk application coding error has occurred. CEEOUT contains the message:

ABTCVMx: Smalltalk VM execution has 
         occurred RC=62

The user primitive code 62 indicates a Smalltalk coding error and that a stack dump has been taken.

S634

Explanation: During dependent module initialization in CICS processing, your program encountered an error. A stack dump has been written.

Module: CICS

User Response: For a reason code of 0, the CICS virtual machine is indicating to you that a stack dump successfully occurred. For a reason code of 2, ensure that the STAKDUMP definition has been setup properly. All other reason codes are internal; contact the IBM Support Center.

Sxxx

Explanation: Internal Smalltalk error.

Module: CICS

User Response: Contact the IBM Support Center.

1650

Explanation: During IMS, OS/390 Native, or build initialization processing, your program encountered an error and could not continue. A stack dump has been written.

Module: IMS, OS/390 Native, or during build initialization

User Response: For a reason code of 0, a stack dump successfully occurred. For a reason code of 2, ensure that the STAKDUMP definition has been setup properly. All other reason codes are internal; contact the IBM Support Center.

1651

Explanation: During IMS, OS/390 Native, or build initialization processing, a Smalltalk virtual machine error was detected.

Module: IMS, OS/390 Native, or during build initialization

User Response: One of the following:

1652

Explanation: During IMS, OS/390 Native, or build initialization processing, a Smalltalk virtual machine runtime error occurred.

Module: IMS, OS/390 Native, or during build initialization

User Response: See the primitive error code table in the IBM Smalltalk Programmer's Reference for a description of the error.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]