DB2 Server for VSE: Messages and Codes


Problem Determination Notes:

Primary-Secondary Error Code Pairs

In the following list, the Primary Error Code is listed first, and the Secondary Error Code is listed second. For any pair of codes not listed, see the "Other" item at the end of the list.

8 0
The requested source member is not in any currently accessed library. This error occurs on FIND calls.

Corrective Action: Verify that you specified the correct membername (and, if applicable, the correct source member type). Check the job control for the failing job. Verify that the library containing the member is in the library concatenation chain. If necessary, add the library using the appropriate JCL. If you have failed to put the member in the library, run the appropriate librarian job to place the member in the desired library.

12 0
An uncorrectable I/O error occurred while reading (by a GET macro) the source member.

Corrective Action: Check for further error messages (including 0Pnn PIOCS messages to the system operator) indicating the cause of the I/O error. You may be able to recover by mounting the DASD volume on a different (or repaired) disk drive. If the error is due to a DASD volume media error (such as a defective track), you may have to rebuild the library source member on a new volume or DASD extent. You may need help from your VSE system programmer.

24 12
The source member could not be opened (FIND call) for access because the partition did not have enough virtual storage.

Corrective Action: Either change the program's parameters so that it requires less virtual storage, or run the program in a larger partition. If you are running the program with the database manager in single user mode, you may be able to run the program in a smaller partition by running the database manager in multiple user mode (if the failing program can be run in multiple user mode). You may need help from your VSE or system programmer.

24 16
The source member could not be opened (FIND call) for access because the partition CDLOAD anchor table is full. (This table is used by the VSE/Advanced Functions CDLOAD macro instruction.)

Corrective Action: Save the error message and any other error messages. Request help from your system programmer.

System Programmer Response: If the program is being run with the database manager in single user mode, you may be able to eliminate this problem by running it with the database manager in multiple user mode.

VSE/VSAM consumes a lot of CDLOAD anchor table space. If the failure is in the DB2 Server for VSE database partition, consider moving SVA-eligible VSAM phases to the VSE/Advanced Functions Shared Virtual Area (SVA). If you cannot eliminate the problem, report it to the DB2 Server for VSE designated support group for your installation.

24 32
The source member could not be opened (FIND call) for access because the VSE/Advanced Functions GETVIS macro instruction detected a main storage hardware error.

Corrective Action: Report this problem to the hardware service person at your installation.

44 0
The source member could not be opened (FIND call) for access because the specified source member type is an invalid character. The source member type character must be an uppercase alphabetic character (including the extended alphabetic characters $, #, and @) or a digit. If the source member type character was user-specified, this is a user error. Otherwise, this is a DB2 Server for VSE system error.

Corrective Action: If the source member type character was user-specified, correct the source member type character specification. Otherwise, save the error message and any other error messages displayed and give the material to your system programmer.

System Programmer Response: Determine the service level of the database manager and report this problem to the designated support group for your installation.

Other
DB2 Server for VSE or VSE system error.

Corrective Action: Save the error message and any other error messages displayed and give the material to your system programmer.

System Programmer Response: Determine the service level of the database manager and report this problem to the designated support group for your installation.




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