Utility products for DB2 abend codes

The Utility products for DB2 can issue the following abend codes.
Number Description
800

Explanation: REORG PLUS can abend or terminate with user abend code 800 if certain internal errors or conditions occur that REORG PLUS does not expect. You can find the reason code in register 15 of the job log that contains the abend summary.

User response: Contact BMC Customer Support and provide the reason code.

3100

Explanation: The Utility products for DB2 can abend or terminate with user abend code 3100 if certain errors or conditions occur in the DB2 Utilities Common Code (D2U). You can find the reason code in register 15 of the job log that contains the abend summary.

User response: Contact BMC Customer Support and provide the reason code.

3200

Explanation: REORG PLUS can abend or terminate with user abend code 3200 if certain errors or conditions occur that REORG PLUS does not expect. These are usually associated with VSAM data set processing. You can find the reason code in register 15 of the job log that contains the abend summary. The following table lists examples of these unexpected errors or conditions:

Reason code

Description

1 (X'01')

The REORG PLUS SYNC subtask encountered an unrecoverable error. For more information, see accompanying messages.

3 (X'03')

REORG PLUS reached an end-of-file indication before the last segment of a spanned record. You might have used an incorrect file to restart REORG PLUS. If this is not the case, contact BMC Customer Support.

4 (X'04')

No sequential I/O buffers are available. Ensure that the REORG PLUS installation options specify the appropriate number of buffers for your data sets. If you specified the appropriate amount, contact BMC Customer Support.

5 (X'05')

REORG PLUS encountered an unexpected error condition. For more information, see the accompanying message. This reason code usually indicates an error or mismatch in table structure, data, and EDITPROC. Verify table structure and data.

7 (X'07')

The number of sort work data sets available is fewer than the minimum required for this job. To avoid this abend, specify a value for the SORTNUM option that is greater than 1.

8 (X'08')

REORG PLUS encountered an unexpected error condition while trying to set or reset a DB2 pending status, such as copy pending (COPY), check pending (CHKP), or recover pending (RECP). Message BMC50498U usually accompanies this abend. Check the system log and DB2MSTR address space for additional error messages that might help determine the cause of the problem. Restart REORG PLUS and allow it to complete.

9 (X'09')

REORG PLUS could not locate the index-key build fragments that it requires. Review the dump produced with this abend code.

12 (X'0C')

REORG PLUS encountered a nontype 2 index.

13 (X'0D')

An internal error occurred in the log apply index update process.

16 (X'10')

There is probably an error in BMCSORT. Check UTPRINT for additional messages.

100 (X'64')

REORG PLUS detected that utility termination was requested. (The user canceled the job.)

3940 (X'F64')

While reorganizing a LOB table space, REORG PLUS attempted to establish the recovery exit but the attempt failed.

3949 (X'F6D')

While reorganizing a LOB table space, REORG PLUS attempted to read a page in a VSAM data set. Either the data set does not exist, or the data set number is higher than the number that REORG PLUS allows.

3965 (X'F7D')

While reorganizing a LOB table space, REORG PLUS encountered an index page that is marked as a leaf page. However, a non-leaf page points to that page and has a level higher than 2.

3968 (X'F80')

While reorganizing a LOB table space, REORG PLUS encountered a page that it expected to be the root page.

3969 (X'F81')

While reorganizing a LOB table space, REORG PLUS encountered a page header that contains an unexpected IPLEVEL value.

3980 (X'F83')

While reorganizing a LOB table space, REORG PLUS encountered a page header that does not indicate that the page is a leaf page. However, a level-2 page points to that page.

3983 (X'F86')

While reorganizing a LOB table space, REORG PLUS encountered one of the following conditions on the auxiliary index:

  • The index is versioned.

  • It is defined as NOT PADDED.

  • The length of its key is not 19 bytes.

  • The RID size is not 5 bytes.

3987 (X'F8A')

While reorganizing a LOB table space, REORG PLUS encountered a LOB map entry with one of the following problems:

  • The map entry is marked as not chunked but describes at least one chunk of pages.

  • The map entry is marked as chunked but maps a number of pages that is not divisible by the chunk size.

3991 (X'F8E')

While reorganizing a LOB table space, REORG PLUS encountered a LOB map that is not an initial map, but it follows a LOB map marked as last.

3992 (X'F8F')

While reorganizing a LOB table space, REORG PLUS encountered one of the following problems:

  • The auxiliary index points to a page that is not a LOB map.

  • A page that is not marked as a LOB map follows a LOB map that is not marked as last.

3994 (X'F91')

While reorganizing a LOB table space, REORG PLUS encountered a ROWID in the auxiliary index that does not match the ROWID on the LOB map page.

3996 (X'F93')

While reorganizing a LOB table space, REORG PLUS encountered an auxiliary index that points to a LOB map that is not marked as first.

User response: Use the information in the preceding table to determine whether you can correct the problem. For assistance, or if the reason code is not listed in the preceding table, contact BMC Customer Support and provide the reason code.

3400

Explanation: LOADPLUS can abend or terminate with user abend code 3400 if certain errors or conditions occur that LOADPLUS does not expect. You can find the reason code in register 15 of the job log that contains the abend summary. The following table lists examples of these unexpected errors or conditions:

Reason code

Description

1 (X'01')

See accompanying messages. LOADPLUS displays this reason code when you encounter one of the following errors:

  • The LOADPLUS SYNC subtask encountered an unrecoverable error.

  • When running an SQLAPPLY load job, LOADPLUS encountered an out-of-space error on SYSERR, resulting in a D37 abend.

  • LOADPLUS encountered an out-of-space error on an inline copy data set, resulting in a D37 abend.

Note

If you receive this user abend secondary to a D37 abend, you can correct the out-of-space condition and restart or resubmit the job.

3 (X'03')

LOADPLUS reached an end-of-file indication before the last segment of a spanned record. You might have used an incorrect file to restart LOADPLUS. If this is not the case, contact BMC Customer Support.

4 (X'04')

No sequential I/O buffers are available. Ensure that the LOADPLUS installation options specify the appropriate amount of buffer space for your data sets. If you specified the appropriate amount, contact BMC Customer Support.

5 (X'05')

LOADPLUS encountered an unexpected error condition. This reason code usually indicates an error or mismatch in the table structure, data, or EDITPROC. Message BMC50498U or BMC50499U usually accompanies this abend. Verify your table structure and data.

7 (X'07')

The number of sort work data sets available is fewer than the minimum required for this job. To avoid this abend, specify a value for the SORTNUM option that is greater than 1.

8 (X'08')

LOADPLUS encountered an unexpected error condition while trying to set or reset a DB2 pending status, such as COPY pending (COPY), CHECK pending (CHKP), or RECOVER pending (RECP). Message BMC50498U usually accompanies this abend. Check the system log and DB2MSTR address space for additional error messages that might help determine the cause of the problem. Restart LOADPLUS and allow it to complete.

16 (X'10')

There is probably an error in BMCSORT. Check UTPRINT for additional messages.

100 (X'64')

LOADPLUS detected that utility termination was requested. (The user canceled the job.)

User response: Use the information in the preceding table to determine whether you can correct the problem. For assistance, or if the reason code is not listed in the preceding table, contact BMC Customer Support and provide the reason code.

3600

Explanation: UNLOAD PLUS can abend with user abend code 3600 if certain errors or conditions occur that UNLOAD PLUS does not expect. You can find the reason code in register 15 of the job log that contains the abend summary. The following table lists examples of these unexpected errors or conditions:

Reason code

Description

1 (X'01')

The UNLOAD PLUS SYNC subtask encountered an unrecoverable error. See accompanying messages.

3 (X'03')

UNLOAD PLUS reached an end-of-file indication before the last segment of a spanned record. You might have used an incorrect file to restart UNLOAD PLUS. If this is not the case, contact BMC Customer Support.

4 (X'04')

No sequential I/O buffers are available. Ensure that the UNLOAD PLUS installation options specify the appropriate number of buffers for your data sets. If you specified the appropriate number of buffers already, contact BMC Customer Support.

5 (X'05')

UNLOAD PLUS encountered an unexpected error condition. This reason code usually indicates an error mismatch in one or more of the table structure, data, or EDITPROC. Message BMC50498U or BMC50499U usually accompanies this abend. Verify your table structure and data.

7 (X'07')

The number of SORTWK data sets available is fewer than the minimum required for this job. To avoid this abend, specify a value for the SORTNUM option that is greater than 1.

8 (X'08')

UNLOAD PLUS encountered an unexpected error condition while trying to set or reset a DB2 pending status, such as COPY pending (COPY), CHECK pending (CHKP), or RECOVER pending (RECP). Message BMC50498U normally accompanies this abend. Check the system log and DB2MSTR address space for additional error messages that might help determine the cause of the problem. Restart UNLOAD PLUS and allow it to complete.

16 (X'10')

There is probably an error in BMCSORT. Check UTPRINT for additional messages.

100 (X'64')

UNLOAD PLUS detected that utility termination was requested. (The user canceled the job.)

User response: Use the information in the preceding table to determine whether you can correct the problem. For assistance, or if the reason code is not listed in the preceding table, contact BMC Customer Support and provide the reason code.

3800

Explanation: CHECK PLUS can abend or terminate with user abend code 3800 if certain errors or conditions occur that CHECK PLUS does not expect. You can find the reason code in register 15 of the job log that contains the abend summary. The following table lists examples of these unexpected errors or conditions:

Reason code

Description

1 (X'01')

The CHECK PLUS SYNC subtask encountered an unrecoverable error. See accompanying messages.

3 (X'03')

CHECK PLUS reached an end-of-file indication before the last segment of a spanned record. You might have used an incorrect file to restart CHECK PLUS. If this is not the case, contact BMC Customer Support.

4 (X'04')

No sequential I/O buffers are available. Ensure that the CHECK PLUS installation options specify the appropriate number of buffers for your data sets. If you specified the appropriate number of buffers, contact BMC Customer Support.

5 (X'05')

CHECK PLUS encountered an unexpected error condition. This reason code usually indicates an error or mismatch in the table structure, data, or EDITPROC. Message BMC50498U or BMC50499U usually accompanies this abend. Verify your table structure and data.

7 (X'07')

The number of SORTWK data sets available is fewer than the minimum required for this job. To avoid this abend, specify a value for the SORTNUM option that is greater than 1.

8 (X'08')

CHECK PLUS encountered an unexpected error condition while trying to set or reset a DB2 pending status, such as copy pending (COPY), check pending (CHKP), or recover pending (RECP). Message BMC50498U normally accompanies this abend. Check the system log and DB2MSTR address space for additional error messages that might help determine the cause of the problem. Restart CHECK PLUS and allow it to complete.

16 (X'10')

There is probably an error in BMCSORT. Check UTPRINT for additional messages.

100 (X'64')

CHECK PLUS detected that utility termination was requested. (The user canceled the job.)

User response: Use the information in the preceding table to determine whether you can correct the problem. For assistance, or if the reason code is not listed in the preceding table, contact BMC Customer Support and provide the reason code.

3900

Explanation: The Utility products for DB2 can abend or terminate with user abend code 3900 if certain errors or conditions occur in the I/O subsystem that the utility does not expect. You can find the reason code in register 15 of the job log that contains the abend summary. If you receive one of the following reason codes, the abend might be secondary to an x37 abend, indicating an out-of-space condition:

  • 352 (X'160')

  • 464 (X'1D0')

  • 532 (X'214')

  • 536 (X'218')

User response: Check any additional messages that the utility issues to determine the cause of the problem. If you receive a reason code that indicates that the abend is secondary to an x37 abend, correct the out-of-space condition and restart or resubmit the job. If you are unable to resolve the problem, contact BMC Customer Support and provide the abend reason code.

Was this page helpful? Yes No Submitting... Thank you

Comments