DB2 Server for VM: Messages and Codes

Problem Determination Notes:

• The primary error code value is the return code value from entry point ARISYSD8 in module ARISYSFC.
• The secondary error code value is the field REASON in the parameter structure used in ARISYSD8 calls.
• FIND calls determine if the file exists (or can be accessed) and if the format is valid; FIND calls perform "OPEN-like" functions for the file. GET (or READ) calls sequentially retrieve the records in the file.

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 28

The requested CMS file could not be found on the disk specified by the file mode letter (or on any accessed CMS disk, if a file mode of * was specified). This error occurs only on a FIND call.

Corrective Action: Verify that you correctly specified the CMS file name (and file type and file mode, if applicable). You can use the CMS LISTFILE command to tell you if a particular CMS file exists on an accessed disk. You can use the CMS QUERY DISK command to display the VOLID (LABEL field) and access letters (M field) of all the disks accessed by your virtual machine. If necessary, access the missing CMS disk or create the missing CMS file before rerunning the database manager program.

12 3

An I/O error occurred while reading a CMS file with a GET call. A CMS error message (prefix is DMS) may be displayed on your virtual machine console to give you additional information.

Corrective Action: If you received a CMS message about the I/O error, take the corrective action suggested by that message. If your virtual machine is reading a CMS file while another virtual machine is updating that file, your virtual machine may get an I/O error. If your virtual machine is reading from a shared disk, make sure that this situation has not occurred. Otherwise:

• If you do not know the file mode letter for the file, use the CMS LISTFILE command to obtain it.
• Use the CMS QUERY DISK access-letter command to obtain the minidisk volume serial number (LABEL field) and virtual cuu.
• Use the CP QUERY DASD command to obtain the real device type and real volume serial number of the virtual cuu.
• Use the CP MSG OP command to query the CP operator for an I/O error message with your virtual machine ID and the real volume serial number and the virtual cuu. Take the corrective action suggested by the CMS or CP error message. You may need help from your VM system programmer.

24 1 or 25

The virtual machine does not have enough virtual storage to process the file. Secondary Error Code 1 occurs for a FIND call. Secondary Error Code 25 occurs for a GET call.

Corrective Action: Either run the failing program in a larger virtual machine or change the program parameters so that it requires less virtual storage. If you are running a program with the database manager in single virtual machine mode, you may be able to run it in a smaller virtual machine while the database manager is running in multiple virtual machine mode. Consult with your system programmer to help you. (You can use the CP QUERY STORAGE command to display the virtual storage size of your virtual machine. You can set the size of your virtual machine by using the CP DEFINE STORAGE command before you use the CP IPL CMS command.)

24 2, 3, 4, or 9

A DB2 Server for VM or VM system error occurred in a virtual storage request during the FIND call for the file.

Corrective Action: Save the error message and any other error messages displayed. For secondary error code 9, give the material to your VM system programmer. For other secondary error codes, give the material to your database manager programmer.

System Programmer Response: The secondary error code is the CMS free storage macro instruction return code. If a user program is running with the DB2 Server for VM program, try to verify that it is not damaging CMS storage pointers (secondary error codes 2 and 3).

For secondary error code 9, determine the service level of VM and report the problem to the designated VM support group for your installation.

For other secondary error codes, determine the service level of the database manager and report the problem to the designated DB2 Server for VM support group for your installation.

28 0

The requested CMS file either contains variable-length records or fixed-length records that are not 80 bytes long. For this function, only fixed-length 80-byte records can be used. This error occurs only on a FIND call.

Corrective Action: Verify that you have specified the correct CMS file. If you have not, correct the file specification. Otherwise, re-create the CMS file with fixed-length 80-byte records. (You can use the CMS LISTFILE command with the LABEL option to display the record format and logical record length of the specified file.)

36 4

The specified CMS file name contains an asterisk as its first character. You are not permitted to use the '*' default for the CMS file name; file names must contain only letters and numbers (up to 8 characters). Alphabetic characters must be upper case; if they are supplied from your terminal, VM folds them to upper case. This error occurs only on a FIND call.

Corrective Action: Correct the file name specification and rerun the DB2 Server for VM program.

36 8

The specified CMS file type contains an asterisk as its first character. You are not permitted to use the '*' default for the CMS file type; file types must contain only letters and numbers (up to 8 characters). Alphabetic characters must be upper case; if they are supplied from your terminal, VM folds them to upper case. This error occurs only on a FIND call.

Corrective Action: Correct the file type specification and rerun the DB2 Server for VM program.

If the DB2 Server for VM program supplies the CMS file type (or optionally does so if you omit it, and you did omit it), this is a DB2 Server for VM system error. Gather all program error messages and report this problem to your system programmer.

System Programmer Response: If a DB2 Server for VM system error has occurred, determine the service level of the database manager and report the problem to the designated support group for your installation.

36 20

The specified CMS file name or file type contains a character that is not valid. File names and file types must contain only letters and numbers (up to 8 characters). Alphabetic characters must be upper case; if they are supplied from your terminal, VM folds them to upper case. This error occurs only on a FIND call.

Corrective Action: Correct the file name or file type specification and rerun the DB2 Server for VM program.

If your specification is valid and the DB2 Server for VM program supplies the file type (or both), this is a DB2 Server for VM system error. Gather all program error messages and report this problem to your system programmer.

System Programmer Response: If a DB2 Server for VM system error has occurred, determine the service level of the database manager and report the problem to the designated support group for your installation.

36 24

The specified CMS file mode is not valid. It must be one of these:

• '*', or
• An uppercase alphabetic letter (A-Z), or
• An uppercase alphabetic letter (A-Z) and a digit (no blank between) from 0 to 5.

Alphabetic characters must be upper case; if they are supplied from your terminal, VM folds them to upper case. This error occurs only on a FIND call.

Corrective Action: Correct the file mode specification and rerun the DB2 Server for VM program.

If the DB2 Server for VM program supplies the CMS file mode (or optionally does so if you omit it, and you did omit it), this is a DB2 Server for VM system error. Gather all program error messages and report this problem to your system programmer.

System Programmer Response: If a DB2 Server for VM system error has occurred, determine the service level of the database manager and report the problem to the designated support group for your installation.

40 36

The CMS minidisk identified by the file mode letter is not accessed by your virtual machine. This error occurs only on a FIND call.

Corrective Action: If you have specified the wrong file mode to the DB2 Server for VM program, rerun the DB2 Server for VM program with the correct file mode specification. Otherwise, ensure that the required CMS minidisk is defined to your virtual machine (using the CP LINK or DEFINE command), and ensure that it is defined to CMS with the desired access (file mode) letter (using the CMS ACCESS command) before rerunning the DB2 Server for VM program.

Other

DB2 Server for VM or VM 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.