DB2 Server for VSE Messages and Codes (Version 7 Release 5)

SQLSTATEs

-129 on page 254 for too many table

-605 on page 295

names or columns

55002

The explanation table is not defined

54005

The sort key is too long, or it has too

properly.

many columns.

-619 on page 297

-124 on page 253

55008

This SQLSTATE has been changed to

54006

The result of concatenation is too long.

42888.

-137 on page 256

55013

This SQLSTATE has been changed to

42889.

54008

The key is too long, or it has too many

columns.

55021

Change of data type or length of host

variable is invalid, because blocking is in

-614 on page 296

effect.

-617 on page 297.

-521 on page 288

54011

Too many columns were specified for a

55023

An error occurred calling a procedure.

table or view.

-471 on page 283

-602 on page 294

-928 on page

54012

The FIELDPROC literal list is too long.

55044

The PROCEDURE must have a status of

-684 on page 303

STOP-REJ, or the PSERVER must be

54013

The statement has too many host

stopped with IMPL=N, before it can be

variables.

altered or dropped.

-129 on page 254 for too many variables

-15000 on page 328

or too many characters in variable names

56001

This SQLSTATE has been changed to

54014

Too many cursors are open.

42901.

-522 on page 289

56002

This SQLSTATE has been changed to

42902.

54015

Section was not created as a result of

executing the null form of an extended

56003

This SQLSTATE has been changed to

dynamic PREPARE or preprocessing a

42903.

PREPARE statement.

56004

The statement failed, because the Invalid

-523 on page 289

Entities table is full.

54016

Too many tables were detected in a

-698 on page 304

DBSPACE.

56005

This SQLSTATE has been changed to

-607 on page 295

42905.

54017

The maximum number of active packages

56006

This SQLSTATE has been changed to

for a unit of work has been exceeded.

42906.

-807 on page 312

56007

This SQLSTATE has been changed to

42907.

54018

The row is too long.

56008

This SQLSTATE has been changed to

-809 on page 313

42908.

54019

The maximum number of late

56009

This SQLSTATE has been changed to

descriptions has been exceeded, probably

42909.

because too many different CCSIDs were

used.

56011

This SQLSTATE has been changed to

42911.

-129 on page 254

56012

This SQLSTATE has been changed to

54020

Too many indexes were detected for a

42912.

table.

Chapter 19. SQLSTATEs

351

SQLSTATEs

56013

This SQLSTATE has been changed to

-832 on page 316.

42913.

56043

This SQLSTATE has been changed to

56014

This SQLSTATE has been changed to

42943.

42914.

56044

An attempt was made to execute a section

56015

This SQLSTATE has been changed to

that has been marked as invalid in a

42915.

modifiable package that is undergoing

modification.

56017

This SQLSTATE has been changed to

42917.

-760 on page 310

56026

This SQLSTATE has been changed to

56046

CREATE PACKAGE with the REPLACE

25000.

option cannot be issued against a

modifiable package.

56031

The clause or scalar function is invalid,

because mixed and graphic data are not

-829 on page 316

supported on this system.

56047

PREPARE Adding Empty Section was not

-640 on page 299

preceded by a CREATE PACKAGE with

the NOMODIFY option.

56032

This SQLSTATE has been changed to

42932.

-834 on page 317

56033

The insert or update value of a long

56048

Three part package name is not

string column must be a host variable or

supported.

NULL.

-136 on page 256

-135 on page 256

56049

An unexpected error occurred when

56034

ALLUSERS can only be used in GRANT

attempting to rebind a view with a new

CONNECT without a password.

version of the database manager. The

view must be dropped and recreated.

-562 on page 293

-835 on page 317

56035

Referential constraints cannot cross

DBSPACEs resident in different types of

56058

This SQLSTATE has been changed to

storage pools.

2D528 and 2D529.

-714 on page 307

56061

This SQLSTATE has been changed to

42961.

56037

This SQLSTATE has been changed to

42937.

56069

This SQLSTATE has been changed to

42969.

56038

Requested feature is not supported in this

environment.

56079

Neither protocol option AUTO nor DRDA

can be specified because the DRDA

-947 on page 327

facility has not been installed for the

56039

This SQLSTATE has been changed to

application requester.

42939.

-861 on page

56042

Only one package can be created or

57008

The date or time local format exit has not

modified in a unit of work, and, while

been installed.

that package is being created or modified,

all statements in that unit of work must

-185 on page 265

be issued against that package. If the

57010

A field procedure could not be loaded.

package is non-modifiable, only Extended

PREPARE statements can be issued.

-682 on page 302

-565 on page 294

57011

Virtual storage or database resource is not

available.

-756 on page 309

-674 on page 302

-757 on page 309

-701 on page 305

-758 on page 309

352

Messages and Codes

SQLSTATEs

-702 on page 305

57027

Connection to the application server has

been severed by the operator.

-703 on page 305

-916 on page 321

-704 on page 306

-933 on page for operator action

-711 on page 307

57028

Unit of work has been rolled back due to

-712 on page 307

an excessive number of system-wide lock

-930 on page 322

requests.

-932 on page 322 when obtaining dynamic

-912 on page 320

storage

57029

Unit of work has been rolled back due to

-940 on page 324 when server-name

an excessive number of lock requests by

resource is not available.

the unit of work.

-942 on page 325.

-915 on page 321

57012

A non-database resource is not available.

57030

Connection to the application server

This will not affect successful execution of

would exceed the installation-defined

subsequent statements.

limit.

-30040 on page 330

-933 on page 322 when maximum number

of connections exceeded

57013

A non-database resource is not available.

This will affect the successful execution of

57033

Deadlock or timeout occurred without

subsequent statements.

automatic rollback.

-30041 on page

-913 on page 320

57014

Processing was canceled as requested.

57037

The ACQUIRE DBSPACE command

failed, because all storage pools for

-914 on page 320.

available dbspaces are full.

57016

Table cannot be accessed, because it is

-699 on page 304

inactive.

57038

No space is available in the storage pool.

-668 on page 301

-700 on page 304

57017

Character conversion is not defined.

57039

Online support is ending.

-332 on page 278

-937 on page 324

57022

Table could not be created, because the

authorization ID of the statement does not

57040

DBNAME Directory error.

own any suitable dbspaces.

-841 on page 318

-620 on page 297

57044

Resource adapter cannot find file.

57024

No appropriate message repository can be

-993 on page 328

accessed.

57045

The Resource Adapter cannot find an

-720 on page 308

entry for the character set in the file.

-721 on page 308.

-994 on page 328

57025

There is not enough room in the dbspaces

58002

An exit has returned an error or invalid

allocated to hold packages.

data.

-945 on page 326

-685 on page 303

-946 on page 326.

-688 on page 304

57026

The system dbspace SYS002 does not

-816 on page 314

exist. This dbspace is used to store

packages.

58003

An invalid section number was detected.

-944 on page 325

-144 on page 256

Chapter 19. SQLSTATEs

353

SQLSTATEs

58004

A system error (that does not necessarily

58019

This SQLSTATE has been changed to

preclude the successful execution of

08001.

subsequent SQL statements) occurred.

58021

A system error occurred while loading a

-753 on page 309

program or control block.

-824 on page 314

-934 on page 322

-901 on page 319

58022

This SQLSTATE has been changed to

40003.

-931 on page 322

58023

System error has caused the current

-932 on page 322 when freeing dynamic

program to be canceled.

storage

-906 on page 320

-941 on page 325.

58024

An error occurred in the underlying

58005

A system error (that prevents the

operating system.

successful execution of subsequent SQL

statements) occurred.

-949 on page 328

-902 on page 319

58025

A column in a catalog table has the

wrong data type.

-754 on page 309

-921 on page 321

58009

Execution failed due to a distribution

protocol error that caused deallocation of

58027

The package was not created and the unit

the conversation.

of work was rolled back due to an earlier

system error.

-30020 on page 329

-917 on page 321

58010

Execution failed due to a distribution

protocol error that will affect the

58029

An internal error has occurred while

successful execution of subsequent DDM

attempting to log user data.

commands or SQL statements.

-754

on page

309

-30021 on page 329

58011

The DDM command is invalid while the

bind process in progress.

-30050 on page 330

58012

The bind process with the specified

package name and consistency token is

not active.

-30051 on page 331

58014

The DDM command is not supported.

-30070 on page 332

58015

The DDM object is not supported.

-30071 on page 332

58016

The DDM parameter is not supported.

-30072 on page

58017

The DDM parameter value is not

supported.

-30073 on page 332

58018

DDM reply message is not supported.

-30074 on page 332

354

Messages and Codes

Chapter 20. DB2 Server for VSE Reason Codes

The DB2 Server for VSE reason codes are printed

Code

VSE/Advanced Functions

in message ARI0042I. The DB2 Server for VSE

Value

Abnormal Termination Code

reason codes are the VSE return codes that were

Dec (Hex)

Meaning

returned to the database manager. Message

(12)

Insufficient buffer space for channel

ARI0042I is usually accompanied by other

program translation

database messages; for example: ARI0026E,

(13)

CCW with count greater than 32K

ARI0027E, ARI0039E, ARI0040E, ARI0041E, etc.

(14)

Page pool too small

The return codes fall into three categories:

(15)

Page fault in disabled program (not a

supervisor routine)

1. VSE/Advanced Functions System Services

(16)

Page fault in MICR stacker select or page

(such as CDLOAD or GETVIS).

fault appendage routine

2. VSE/Advanced Functions Abnormal

(17)

Main task issued a CANCEL macro with

Termination Codes.

subtask still attached

3. VSE/Advanced Functions Cross-Partition

(18)

Main task issued a DUMP macro with

Communication (XPCC) return codes.

subtask still attached

(19)

Operator replied CANCEL as the result

of an I/O error message

VSE/Advanced Functions System

(1A)

An I/O error has occurred

Services Return Codes

(1B)

Channel failure

(1C)

CANCEL ALL macro issued in another

The VSE/Advanced Functions System Services

task

return codes are found in the IBM VSE/ESA

(1D)

Main task terminated with subtask still

System Macros Reference manual.

attached

(1E)

I/O error on external lock file

(1F)

Processing unit failure

VSE/Advanced Functions

(20)

A program check occurred

Abnormal Termination Codes

(21)

An invalid SVC was issued by the

problem program or macro

The return codes from VSE/Advanced Functions

(22)

Phase not found in the library phase

Abnormal Termination are found in IBM VSE/ESA

member

System Macros Reference under the discussion of

(23)

CANCEL macro issued

STXIT macro instructions with the AB parameter.

(24)

Canceled due to an operator request

The following is a list of the VSE/Advanced

(25)

Invalid virtual storage address given

Functions Abnormal Termination Codes. (The

(outside partition)

code values also appear as the reason code in

(26)

SYSxxx not assigned (unassigned LUB

message ARI0042I.)

code)

(27)

Undefined logical unit. Guest sharing is

Code

VSE/Advanced Functions

not supported in a Dynamic partition.

Value

Abnormal Termination Code

(28)

Reserved

Dec (Hex)

Meaning

(29)

Reserved

00 (00)

Default value for all cases other than

(2A)

I/O error on page data set

those listed below

(2B)

I/O error during fetch from private

(0A)

Access control processing error

library phase member

(0B)

Access violation

(2C)

Page fault appendage routine passed

(0C)

Operator/ICCF system request

illegal parameter to supervisor

(0D)

Program check in subsystem or

(2D)

Program cannot be executed or restarted

appendage

because of a failing storage block

(0E)

Page fault in subsystem or appendage

(2E)

Invalid resource request (possible

(0F)

Invalid FBA DASD address for SYSFIL

deadlock)

(10)

Normal EOJ

(2F)

More than 255 PFIX requests on one page

(11)

No channel program translation for

(30)

Read past a /& statement

unsupported device

355

DB2 Server for VSE Reason Codes

Code

VSE/Advanced Functions

Reason

Return

Value

Abnormal Termination Code

Code

Dec (Hex)

Meaning

Value

Reason Code

(31)

I/O error queue overflow during system

Dec (Hex)

Meaning

error recovery procedure

(05)

(04)

DB2 Server for VSE partition

(32)

Invalid DASD address

terminated while the resource

(33)

No long seek on a DASD

adapter had a connect request

pending

(35)

Job control open failure

(06)

(04)

DB2 Server for VSE partition

(36)

Page fault in I/O appendage routine

disconnected normally

(38)

Wrong privately translated CCW

(07)

(04)

DB2 Server for VSE partition

(39)

Error in SYSLOG channel program

disconnected abnormally

(40)

ACF/VTAM^® error, invalid condition

(08)

(04)

A duplicate application name

(41)

ACF/VTAM error, invalid condition

(identify) exists in the system

(42)

Invalid extent information violates DASD

(08)

(04)

When accompanied by message

file protection

ARI2908, indicates that an

255

(FF)

Unrecognized cancel code

APPC/VM function was

rejected at initialization

(09)

(04)

A duplicate application name

VSE/Advanced Functions

(identify) exists in the partition

(09)

(04)

When accompanied by message

Cross-Partition Communication

ARI2908, indicates that an

Codes

APPC/VM function completed

unsuccessfully

The VSE/Advanced Functions cross-partition

(0A)

(04)

The DB2 Server for VSE system

communication (XPCC) codes are usually

has not done an identify

displayed as returned to the DB2 Server for VSE

(0A)

(04)

When accompanied by message

system. In some cases they are translated by the

ARI2908, indicates that the

database manager. These codes are printed by the

other side issued an unexpected

database manager and the resource adapter

APPC/VM function

partitions.

(0B)

(04)

When accompanied by message

ARI2908, indicates that an

unexpected interrupt occurred

The message ARI0406E is issued by the Resource

on an APPC/VM connection

Adapter and displays the request code, return

(0C)

(04)

The DB2 Server for VSE system

code, and reason code. Message ARI4006E, like

has not issued a CONNECT

ARI0406E, also displays the request code, return

command

code, and reason code. If the reason code = 06 or

(17)

(08)

The DB2 Server for VSE system

07 with a return code of 04, accompanying

issued a TERMQSCE command

messages will be issued by the DB2 Server for

(06)

(0C)

Control block format error

VSE partition. The accompanying messages must

(07)

(0C)

Wrong identity token

be considered to determine the condition that

(08)

(0C)

Wrong path id

existed and the action to be taken. The following

(09)

(0C)

Requesting task does not own

is a list of the reason codes, return codes, and

the control block

their meanings as contained in message ARI0406E

(0A)

(0C)

Invalid buffer list

and ARI4006E.

(0B)

(0C)

Buffer length greater than 16

megabytes

If ARI0406E or ARI4006E contains a reason code

(0C)

Receive buffer too small

that is not found in the following table, make a

(0D)

(0C)

More than 64 connect requests

record of what went wrong and contact the

issued by resource adapter

designated support group for your installation.

partition

The XPCC return codes are documented in the

(0E)

(0C)

No storage available for

IBM VSE/ESA System Macros Reference.

VSE/Advanced Functions

control blocks

(0F)

(0C)

Connect request must be made

to a subsystem by user

partition (resource adapter)

356

Messages and Codes

DB2 Server for VSE Reason Codes

Reason

Return

Reason Code

Code

Value

Reason Code

Dec (Hex)

Reason Code Meaning

Dec (Hex)

Meaning

08 (08)

SUBSID not accepted, invalid

(10)

(0C)

No request pending for other

name length

partition

(0C)

SUBSID not accepted,

(12)

(0C)

Request already pending for

VSE/Advanced Functions

same partition

internal list is full

(13)

(0C)

Invalid request sequence

(10)

Name not found

(14)

(0C)

Invalid terminate request while

(14)

SUBSID function not available

requests are still pending

(15)

(0C)

Invalid disconnect request

while request still by

The following are the request codes for messages

disconnecting side

ARI0406E and ARI4006E and their meanings:

(16)

(0C)

Invalid disconnect request

while request still pending from

Request Code

other partition

Value

(18)

(0C)

Invalid request; no connect was

Dec (Hex)

Request Code Meaning

ever done by other partition

01 (01)

Logon (XPCC IDENT)

(1C)

(0C)

Invalid XPCCB (control block)

02 (02)

Connect (XPCC CONNECT)

address

04 (04)

Send with reply (XPCC SENDR)

(26)

(0C)

VSE Guest Sharing, APPC/VM

05 (05)

Receive (XPCC RECEIVE)

request failed. See System

06 (06)

Reply (XPCC REPLY)

Console message ARI2908I

07 (07)

Reset Send (XPCC CLEAR)

(27)

(0C)

Not enough real storage was

08 (08)

Reset Receive/Reply (XPCC

allocated to PFIX buffers

PURGE)

needed for XPCC

09 (09)

Disconnect (XPCC DISCONN)

communication

(0A)

Disconnect Unconditional

255

(FF)

(0C)

Invalid DB2 Server for VSE

(XPCC DISCPRG)

request

(0B)

Disconnect All (XPCC

DISCALL)

(0C)

Logoff (XPCC TERMIN)

(0D)

Logoff Unconditional (XPCC

If message ARI0027E, A COMMUNICATION

TERMPRG)

LINK ERROR HAS OCCURRED is issued:

(0E)

Shutdown (XPCC TERMQSCE)

v Message ARI0040E provides an indication of

(0F)

Wait (VSE/Advanced Functions

the communication link request associated with

WAIT)

the error. (See Chapter 24, “System Errors,” on

page 371 for the definitions.)

v Message ARI0042I contains the reason code.

Other DB2 Server for VSE

Reason code values and meanings are the same

Abnormal Termination Codes

as listed for message ARI0406E where the

return code is 12 (X’0C’).

Reason Code

v Message ARI0043I contains a value of 516.

Dec (Hex)

Reason Code Meaning

254

(FE)

The database manager has

If message ARI0040E DB2 Server for VSE

been terminated due to a lack

SYSTEM ERROR OCCURRED - ARICIP2 01 is

of virtual storage. A dump has

been issued. (Register 15

issued, the reason code in message ARI0042I is

contains the ‘254’ return code.)

the return code from the VSE SUBSID macro

instruction. The reason code meanings are:

code from the failing VSE

GETVIS macro.

Reason Code

Value

Dec (Hex)

Reason Code Meaning

04 (04)

The DB2 Server for VSE system

already exists in another

partition

Chapter 20. DB2 Server for VSE Reason Codes

357

ARISBDID JCL Return Codes

v xxx4 - Erase data from a VSAM file

ARISBDID JCL Return Codes

150 - End of file

During DBNAME Directory generation, some

175 - I/O error

errors might be reported by the DBNAME

–

200 - Get storage failed

Directory Generator, ARICBDID. The following

–

225 - Free storage failed

lists the return codes with their explanations.

–

250 - Invalid call

1xx - SYSIPT or SYSPCH open error

v xxx5 - Write data to a VSAM file

112 - I/O error

150 - End of file

–

124 - Virtual storage request failed or

–

175 - I/O error

CDLOAD anchor table full

–

200 - Get storage failed

–

225 - Free storage failed

2xx - Read error

–

250 - Invalid call

212 - I/O error

–

248 - Error retrieving file for SYSIPT READ

v xxx6 - Close a VSAM file

MEMBER statement

150 - End of file

–

175 - I/O error

3xx - Write error

–

200 - Get storage failed

312 - I/O error

–

225 - Free storage failed

–

352 - End of extents encountered while

–

250 - Invalid call

attempting to write to disk

4xx - Close error

Report all undocumented return codes to the

412 - I/O error

designated support group for your installation.

5xx - Content error

500 - Invalid APPLID specified in

ARISCNVD JCL Return Codes

ARISDIRD.A

501 - Invalid DBNAME specified in

During the refresh of the CCSID-related phases,

ARISDIRD.A

some errors might be reported by the refresh job,

6xx - Definition error

ARISCNVD. The following lists the return codes

600 - More than one system default

with their explanations.

specified.

1xx - Error opening work file

12 - I/O error

Report all undocumented return codes to the

16 - Invalid device type

designated support group for your installation.

–

20 - Invalid call

24 - Virtual storage request failure or

CDLOAD anchor table full

ARISBGUD JCL Return Codes

32 - Internal error

When updating the SQLGLOB file using the

36 - Tape dynamic assign or unassign error

SQLGLOB File Batch Update/Query Program

3xx - Error writing to work file

(ARIRBGUD), some error might be reported by

12 - I/O error

the update program. The following lists the return

–

20 - Invalid call

codes with their explanations.

–

32 - Internal error

v xxx1 - Check the VSAM SQLBLOG file label

–

52 - End of extents encountered while

100 - Label not found

attempting to write to disk

–

125 - Unexpected error

4xx - Error closing work file

v xxx2 - Generate ACB and RPL for SQLGLOB

12 - I/O error

file

–

20 - Invalid call

175 - I/O error

–

32 - Internal error

–

200 - Get storage failed

–

32 - Tape dynamic assign or unassign error

–

225 - Free storage failed

1xxx - SQL warning occurred

v xxx3 - Open a VSAM file

- xxx - SQLCODE (positive value)

150 - End of file

2xxx - SQL error occurred

–

175 - I/O error

- xxx - SQLCODE (negative value)

–

200 - Get storage failed

–

225 - Free storage failed

Report all undocumented return codes to the

250 - Invalid call

designated support group for your installation.

358

Messages and Codes

ARISGDEF JCL Return Codes

xxx1 - Check the BIND file label

ARISGDEF JCL Return Codes

100

- Label not found

During the setting of the SQLGLOB file default,

125

- Unexpected error

some errors might be reported by the default

xxx2 - Generate ACB and RPL for BIND file

creation, ARISGDEF. The following lists the return

175

- I/O error

codes with their explanations.

–

200

- Get storage failed

xxx1 - Check the VSAM SQLBLOG file label

–

225

- Free storage failed

100

- Label not found

xxx3 - Open a BIND file

–

125

- Unexpected error

150

- End of file

xxx2 - Generate ACB and RPL for SQLGLOB

–

175

- I/O error

file

–

200

- Get storage failed

175

- I/O error

–

225

- Free storage failed

–

200

- Get storage failed

–

250

- Invalid call

–

225

- Free storage failed

xxx4 - Erase a BIND record

xxx3 - Open a VSAM file

150

- End of file

150

- End of file

–

175

- I/O error

–

175

- I/O error

–

200

- Get storage failed

–

200

- Get storage failed

–

225

- Free storage failed

–

225

- Free storage failed

–

250

- Invalid call

–

250

- Invalid call

xxx5 - Write data to a BIND file

xxx4 - Erase data from a VSAM file

150

- End of file

150

- End of file

–

175

- I/O error

–

175

- I/O error

–

200

- Get storage failed

–

200

- Get storage failed

–

225

- Free storage failed

–

225

- Free storage failed

–

250

- Invalid call

–

250

- Invalid call

xxx6 - Close a BIND file

xxx5 - Write data to a VSAM file

150

- End of file

150

- End of file

–

175

- I/O error

–

175

- I/O error

–

200

- Get storage failed

–

200

- Get storage failed

–

225

- Free storage failed

–

225

- Free storage failed

–

250

- Invalid call

–

250

- Invalid call

xxx7 - Open a PACKAGE file

xxx6 - Close a VSAM file

175

- I/O error

150

- End of file

–

200

- Get storage failed

–

175

- I/O error

–

250

- Invalid call

–

200

- Get storage failed

–

300

- Wrong record length

–

225

- Free storage failed

–

325

- Internal error

–

250

- Invalid call

–

360

- Error retrieving file for SYSIPT read

370

- End of extents encountered while

Report all undocumented return codes to the

attempting to write to disk

designated support group for your installation.

xxx8 - Read data from a PACKAGE file

175 - I/O error

200 - Get storage failed

ARISIQBD/Other bindfile load

–

250 - Invalid call

JCL Return Codes

–

300 - Wrong record length

–

325 - Internal error

During the conversion of the bind file, some

–

360 - Error retrieving file for SYSIPT read

errors might be reported by the bind file

–

370 - End of extents encountered while

generation (loading of bindfile A-members to the

attempting to write to disk

VSAM bindfile), ARISIQBD/ARIDSQLB/

ARIXUxxB, ARISIQBD. The following lists the

xxx9 - Close a PACKAGE file

return codes with their explanations.

175 - I/O error

200 - Get storage failed

v xxx0 - Get the storage for bind file record

250 - Invalid call

–

200 - Get storage failed

300 - Wrong record length

Chapter 20. DB2 Server for VSE Reason Codes

359

Chapter 21. Sequential File Errors

This section describes the causes and suggests

second. For any pair of codes not listed, see the

corrective actions for error messages due to errors

“Other” item at the end of the list.

encountered by the DB2 Server for VSE system

An uncorrectable I/O error occurred

while processing sequential input or output files

while reading (GET macro) or writing

in a VSE system. The error messages are

(PUT macro) a SAM file.

displayed on the system operator console or in a

SYSLST print file.

Corrective Action: Get the I/O error

message (0Pnn PIOCS message) from the

Problem Determination Notes for VSAM Access of

system operator. Take the corrective action

Sequential Files (Log Archive Files):

recommended or suggested by the I/O

error message. You may need help from

v The primary error code value is the return code

your VSE or system programmer to

value from entry point ARISYSEA and

resolve the problem. Depending on the

ARISYSEF in module ARISYSED.

type of I/O error, you may be able to

End of file

recover by using a different hardware I/O

device or by using a different tape or

I/O error

DASD volume.

Invalid call

The database file could not be opened

Get virtual storage failed

because the partition did not have enough

virtual storage.

Internal error (such as free storage

failed)

Corrective Action: Either change the

v The secondary error code value is the operation

program’s parameters so that it requires

which failed:

less virtual storage, or run the program in

a larger partition. If you are running the

GENCB for ACB or RPL failed

program with the database manager in

Open file for input or output failed

single user mode, you may be able to run

the program in a smaller partition by

Get log control information descriptor

running the database manager in multiple

page failed

user mode (if the failing program can be

4/7

Closed file failed

run in multiple user mode). You may

need help from your VSE or system

5/6

Get or Put operation failed

programmer.

Problem Determination Notes for SAM Access:

The database file could not be opened

because the partition CDLOAD anchor

v The primary error code value is the return code

table is full. (This table is used by the

value from entry point ARISYSD5 in module

VSE/Advanced Functions CDLOAD

ARISYSDD.

macro instruction.)

v The secondary error code value is the field

EREASON in parameter structure ARIFDESC

Corrective Action: Save the error message

used in ARISYSD5 calls.

and any other error messages. Request

help from your system programmer.

v For primary error code 36, the secondary error

code is the return code (in decimal) from the

System Programmer Response: If the

VSE/Advanced Functions ASSIGN macro

program is being run with the database

instruction.

manager in single user mode, you may be

able to eliminate this problem by running

Primary-Secondary Error Code Pairs

it with the database manager in multiple

user mode.

In the following list, the Primary Error Code is

VSE/VSAM consumes a lot of CDLOAD

listed first, and the Secondary Error Code is listed

anchor table space. If the failure is in the

361

Sequential File Errors

DB2 Server for VSE database partition,

such a partition, request that your VSE

consider moving SVA-eligible VSAM

system programmer generate a new VSE

phases to the VSE/Advanced Functions

supervisor with a partition containing

Shared Virtual Area (SVA). If the problem

more programmer logical units. (The

persists, make a record of what went

number of programmer logical units is

wrong and contact the designated support

controlled by the BGPGR or FnPGR

group for your installation.

parameter of the VSE/Advanced

Functions IOTAB supervisor generation

The database file could not be opened

macro instruction.)

because the VSE/Advanced Functions

GETVIS macro instruction detected a

In opening a DB2 Server for VSE

main storage hardware error.

accounting output tape file, archive tape

file, or trace output tape file, the tape unit

Corrective Action: Report this problem to

could not be dynamically assigned

the hardware service person at your

(VSE/Advanced Functions ASSIGN macro

installation.

instruction). The assignment was not done

VSE/Advanced Functions data

because the specified tape unit address

management detected a wrong-length

(cuu) was not found in the VSE

record while reading the file (using a GET

supervisor PUB table; that is, the cuu is

macro instruction).

not known to the VSE system.

Corrective Action: Ensure that the

If this occurs for any other file (or not on

program is reading the file it expects.

open), it is a DB2 Server for VSE or VSE

Ensure that (where applicable) the correct

system error.

blocksize, record format, and logical

Corrective Action: Ensure that the system

record length were specified for the file. If

operator entered a valid tape unit cuu

the program requires a specific blocksize,

address. If a valid tape unit cuu was

logical record length, maximum logical

entered by the system operator (in a reply

record length, or record format, ensure

to message ARI073A, ARI295A, ARI299A,

that the input file meets these

or ARI092A, or by the TRACE ON

specifications. Check the program that

command), refer the problem to your VSE

created the file to ensure that it used the

system programmer. The system

correct blocksize, (maximum) logical

programmer should ensure that the tape

record length, and record format. If you

unit is defined to the VSE system by

find no inconsistencies, ask the system

using the initial program load (IPL) ADD

programmer to determine the service

command.

level of the database manager and report

this problem to the designated support

In opening a DB2 Server for VSE

group for your installation.

accounting output tape file, archive tape

file, or trace output tape file, the tape unit

In opening a DB2 Server for VSE

could not be dynamically assigned

accounting output tape file, archive tape

(VSE/Advanced Functions ASSIGN macro

file, or trace output tape file, the tape unit

instruction). The assignment was not done

could not be dynamically assigned

because the specified tape unit address

(VSE/Advanced Functions ASSIGN macro

(cuu) was defined in the VSE supervisor

instruction). The assignment was not done

PUB table as a device other than a tape

because the VSE supervisor had no free

unit.

Logical Unit Block (LUB) entry to allocate

to the file.

If this occurs for any other file (or not on

open), it is a DB2 Server for VSE or VSE

If this occurs for any other file (or not on

system error.

open), it is a DB2 Server for VSE or VSE

system error.

Corrective Action: Ensure that the system

operator entered a valid tape unit cuu

Corrective Action: Either reconfigure the

address. If a valid tape unit cuu was

job control for the failing program or run

entered by the system operator (in a reply

it in a partition with more programmer

to message ARI0073A, ARI0295A,

logical units available. If you do not have

ARI0299A, or ARI0092A, or by the

362

Messages and Codes

Sequential File Errors

TRACE ON command), refer the problem

made because the specified tape unit

to your VSE system programmer. The

(cuu) has not been previously assigned.

system programmer should ensure that

This is a DB2 Server for VSE or VSE

the tape unit is defined to the VSE system

system error if the specified tape unit

by using the initial program load (IPL)

remained assigned.

ADD command.

Corrective Action: Ensure that the

In opening a DB2 Server for VSE

specified tape unit is no longer assigned.

accounting output tape file, archive tape

Otherwise, contact the designated support

file, or trace output tape file, the tape unit

group for your installation.

could not be dynamically assigned

(VSE/Advanced Functions ASSIGN macro

In opening a DB2 Server for VSE

instruction). The assignment was not done

accounting output tape file, archive tape

because the specified tape unit address

file, or trace output file, the tape unit

(cuu) is down (due to the VSE/Advanced

could not be dynamically assigned

Functions DVCDN job control command).

(VSE/Advanced Functions ASSIGN macro

instruction). The assignment was not

If this occurs for any other file (or not on

made because the specific tape unit (cuu)

open), it is a DB2 Server for VSE or VSE

is currently owned by another partition.

system error.

If this occurs for any other file (or not on

Corrective Action: If the tape unit is no

OPEN), it is a DB2 Server for VSE or VSE

longer inoperative or off-line for service,

system error.

enter the VSE/Advanced Functions

DVCUP job control command to make the

Corrective Action: The system operator

tape unit available for program use.

must select a tape unit which is not

Otherwise the system operator must

currently assigned to any partition when

select a different tape unit for the tape

entering the cuu for the accounting tape

file.

file, the archive tape file, or the trace tape

file.

In opening or closing a DB2 Server for

VSE accounting output tape file, archive

In opening a DB2 Server for VSE

tape file, or trace output tape file, the tape

accounting output tape file, archive tape

unit could not be dynamically assigned or

file, or trace output file, the tape unit

unassigned (VSE/Advanced Functions

could not be dynamically assigned

ASSIGN macro instruction). The action

(VSE/Advanced Functions ASSIGN macro

was not taken because the partition did

instruction). The assignment was not

not have enough virtual storage.

made because the specified tape unit

(cuu) is currently assigned to a system

Corrective Action: Either change the

logical unit (for example, SYSLST).

program’s parameters so that the it

requires less virtual storage, or run the

If this occurs for any other file (or not on

program in a larger partition. If you are

OPEN), it is a DB2 Server for VSE or VSE

running a program with the database

system error.

manager in single user mode, you may be

An error occurred while processing an

able to run the program in a smaller

READ MEMBER statement in a SYSIPT

partition by running the database

file. Message ARI0068E describing the

manager in multiple user mode (if the

error condition has been displayed on the

failing program can be run in multiple

system operator console and on SYSLST.

user mode). You may need help from

Refer to that message for further

your VSE or system programmer.

explanation.

In closing a DB2 Server for VSE

Corrective Action: Refer to the corrective

accounting output tape file, archive tape

action for message ARI0068E.

file, or trace output file, the tape unit

could not be dynamically unassigned

The disk output file has filled all space

(VSE/Advanced Functions ASSIGN macro

allocated to it (including any secondary

instruction). The unassignment was not

allocations if the VSE/VSAM Space

Management for SAM feature is being

Chapter 21. Sequential File Errors

363

Chapter 22. Include File Access Errors

This section describes the causes and suggests

An uncorrectable I/O error

corrective actions for error messages due to errors

occurred while reading (by a GET

encountered by the DB2 Server for VSE system

macro) the source member.

while locating and reading VSE source members.

Corrective Action: Check for

The error messages are displayed on the system

further error messages (including

operator console or in a SYSLST print file.

0Pnn PIOCS messages to the

system operator) indicating the

Problem Determination Notes:

cause of the I/O error. You may

be able to recover by mounting

v The database manager uses the VSE DTFSL

the DASD volume on a different

macro (with FIND and GET calls) and access

(or repaired) disk drive. If the

method to find and sequentially retrieve source

error is due to a DASD volume

members.

media error (such as a defective

v The primary error code value is the return code

track), you may have to rebuild

value from entry point ARISYSD8 in module

the library source member on a

ARISYSDD.

new volume or DASD extent. You

v The secondary error code value is the field

may need help from your VSE

REASON in the parameter structure used in

system programmer.

ARISYSD8 calls.

The source member could not be

v FIND calls determine if the library source

opened (FIND call) for access

member exists (or can be accessed) and

because the partition did not have

perform OPEN-like functions for accessing the

enough virtual storage.

member. GET (or READ) calls sequentially

retrieve the records from the member.

Corrective Action: Either change

the program’s parameters so that

Primary-Secondary Error Code Pairs

it requires less virtual storage, or

run the program in a larger

In the following list, the Primary Error Code is

partition. If you are running the

listed first, and the Secondary Error Code is listed

program with the database

second. For any pair of codes not listed, see the

manager in single user mode, you

“Other” item at the end of the list.

may be able to run the program

in a smaller partition by running

The requested source member is

the database manager in multiple

not in any currently accessed

user mode (if the failing program

library. This error occurs on FIND

can be run in multiple user

calls.

mode). You may need help from

Corrective Action: Verify that you

your VSE or system programmer.

specified the correct membername

The source member could not be

(and, if applicable, the correct

opened (FIND call) for access

source member type). Check the

because the partition CDLOAD

job control for the failing job.

anchor table is full. (This table is

Verify that the library containing

used by the VSE/Advanced

the member is in the library

Functions CDLOAD macro

concatenation chain. If necessary,

instruction.)

add the library using the

appropriate JCL. If you have

Corrective Action: Save the error

failed to put the member in the

message and any other error

library, run the appropriate

messages. Request help from your

librarian job to place the member

system programmer.

in the desired library.

365

Problem Determination Notes:

System Programmer Response: If

database manager and report this

the program is being run with the

problem to the designated

database manager in single user

support group for your

mode, you may be able to

installation.

eliminate this problem by running

Other

DB2 Server for VSE or VSE

it with the database manager in

system error.

multiple user mode.

Corrective Action: Save the error

VSE/VSAM consumes a lot of

message and any other error

CDLOAD anchor table space. If

messages displayed and give the

the failure is in the DB2 Server for

material to your system

VSE database partition, consider

programmer.

moving SVA-eligible VSAM

phases to the VSE/Advanced

System Programmer Response:

Functions Shared Virtual Area

Determine the service level of the

(SVA). If you cannot eliminate the

database manager and report this

problem, report it to the DB2

problem to the designated

Server for VSE designated

support group for your

installation.

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.

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

366

Messages and Codes

Chapter 23. Limit Errors

When limit errors are detected, message ARI0039E

ARICEXP nn

is issued. The text of the message is:

(See note 1.)

Insufficient storage

ARI0039E Application server limit error occurred -

Insufficient storage

ARIxxxx nn

ARICIP1 nn

Explanation: The following are the conditions that

(See note 1.)

cause the message to be issued where ARIxxxx nn is:

Failure occurred while loading phase

ARICCRA nn

ARIXRDS (not enough storage or phase

(See note 1.)

not found)

Get working storage error (DSCAREA)

Failure occurred while loading phase

Get working storage error (YTABLE1)

ARIXSXR (not enough storage or phase

not found)

Get working storage error (SCANS)

ARICIPB nn

Get working storage error (MODCB)

(See note 1.)

Working storage initialization error

(DSCAREA)

(DSCAREAP)

Get working storage error

Get working storage error (WAITM Table)

(Communication Link control blocks)

Get working storage error (DCES)

Get working storage error

(Communication Manager Parameter List)

Get working storage error

(Communication Link ID BLOCKS)

Get working storage error (OMB

Parameter List)

Get working storage error (CPC Connect

Blocks)

Get working storage error (RDAREA)

Get working storage error (TRACE

Get working storage error (SQLCA)

FDESC)

Get working storage error (TBASE)

Get below working storage error (HSDS,

CID)

Get working storage error (RI area)

Get working storage error (Global Tables)

Get working storage error (default input

buffer)

Get working storage error (Accounting

I/O File Descriptor Block)

Get working storage error (default output

mailbox buffer)

Get working storage error (Online

Accounting Storage Queue Header)

Get working storage error (Parser)

Get working storage error (accounting

Get working storage error (Generator)

records)

Get working storage error (Conversion)

Get working storage error (Transproc

Get working storage error (DRRMSTR)

control)

Get working storage error (DCAREA)

ARICIP1 nn

(See note 1.)

Get working storage error (ASPAREA)

Failure occurred while loading phase

Get working storage error (TRANS)

ARIXRDS (not enough storage or phase

Get working storage error (PCAREA)

not found)

ARICDSP nn

Failure occurred while loading phase

ARIXSXR (not enough storage or phase

All agents waiting for buffers, and SQL is

not found)

out of page buffers

367

Limit Errors

ARICJAC nn

ARISIIO nn

(See note 1.)

Insufficient storage

Not enough virtual storage for directory

file buffer during database generation

ARICSPM nn

(See note 1.)

Not enough virtual storage for directory

file blocks during database generation

Failure occurred while loading phase

xxxxxxxx (not enough virtual storage or

Same as 03

phase not found; message ARI0026E

Same as 03

identifies the phase name)

Same as 03

ARICSHO nn

(See note 1.)

Same as 03

Insufficient storage

Same as 03

Insufficient storage

Same as 03

ARICSPM nn

Same as 03

(See note 1.)

ARISRMG nn

Single user mode, and either the program

(See note 1.)

was not found, or there was insufficient

Insufficient storage

storage

Insufficient storage

ARICSTK nn

(See note 1.)

ARISUXP nn

Not enough virtual storage to allocate

DASD storage assigned to the storage

DB2 Server for VSE stack storage for

pool is full (See message ARI0201E)

agents

ARIXERO nn

ARISDBR nn

(See note 1.)

No working storage

Not enough virtual storage for database

Same as 13

generation value table

Same as 13

Not enough virtual storage for database

generation input file control block

Same as 13

ARISDSK nn

ARIYC11 nn

(See note 1.)

Insufficient storage

Not enough virtual storage for log buffer

Insufficient storage

Same as 09

ARISFDB nn

Not enough virtual storage for log

(See note 1.)

information

Not enough virtual storage for loading

Same as 17

directory block during database

generation

Same as 09

ARISFMG nn

Same as 17

(See note 1.)

Not enough virtual storage for log record

Insufficient storage

Same as 17

Insufficient storage

Not enough virtual storage for log

ARISFM1 nn

ARIYD48 nn

(See note 1.)

DASD storage assigned to the storage

Not enough virtual storage for

pool is full (See message ARI0201E)

input/output buffer to format database

files

DASD storage assigned to the storage

pool is full (See message ARI0201E)

368

Messages and Codes

Limit Errors

ARIYD69 nn

ARIYI63 nn

(See note 1.)

Invalid entities table is in new format. The

Request for working storage for building

directory must be reset, but there are

new row during row update recovery

either transient or invalid indexes.

(UNDO/BACKUP or REDO) failed

ARIYK12 nn

Same as 01

(See note 1.)

Same as 01

Not enough storage for deadlock cycle

tables

ARIYD81 nn

(See note 1.)

Same as 03

Request for working storage to assemble

Same as 03

data manipulation call parameter values

ARIYK41 nn

for DBSS entry or exit level 2 trace output

failed

No more LRBs available

Same as 06

ARIYK53 nn

(See note 1.)

Same as 06

Not enough virtual storage space for

Same as 06

SHOW LOCK WANTLOCK command

Same as 06

processing.

ARIYI14

Insufficient storage for stack storage.

Directory buffer pool is exhausted

ARIYK54 nn

(NDIRBUF parameter) (See message

(See note 1.)

ARI0203E)

Not enough virtual storage for SHOW

ARIYI19

LOCK USER command processing

Page buffer pool is exhausted (NPAGBUF

ARIYK55 nn

parameter) (See message ARI0203E)

(See note 1.)

ARIYI22

Not enough virtual storage for SHOW

(See note 1.)

LOCK DBSPACE command processing

Not enough storage to allocate VSAM

ARIYK56 nn

ACBs for database files

(See note 1.)

Not enough storage to allocate VSAM

Not enough virtual storage for SHOW

EXLISTs for database files

LOCK ACTIVE command processing

Not enough storage to allocate VSAM

Same as 01

ACB pointer array for database files

ARIYK57 nn

Same as 01

(See note 1.)

Not enough storage to allocate VSAM

Not enough virtual storage for SHOW

RPLs for database files

LOCK GRAPH command processing

Same as 07

Same as 01

Same as 07

ARIYL00 nn

(See note 1.)

ARIYI29

Number of log pages exceeds limit. (Note

DASD storage assigned to the storage

1 does not apply to this limit error.)

pool is full (See message ARI0201E)

Insufficient storage for checkpoint record

DASD storage assigned to the storage

pool is full (See message ARI0201E)

Insufficient storage for checkpoint record

ARIYI36

Insufficient storage for log page

(See note 1.)

Insufficient storage for checkpoint record

Not enough storage to allocate bit map

Insufficient storage for log page

table for DBSPACE directory file

allocation blocks

ARIYL01 nn

Chapter 23. Limit Errors

369

Limit Errors

Database manager log file is full (See

Get working storage error (Counter Pool

message ARI0276E)

Structure)

ARIYL08 nn

ARIYT29

(See note 1.)

Not enough agents specified (NCUSERS

Not enough virtual storage for checkpoint

parameter) (See message ARI0231E)

record

ARIYX02

ARIYL09 nn

DASD storage assigned to the storage

(See note 1.)

pool is full (see message ARI0201E) or

Insufficient storage for checkpoint record

internal DBSPACE is full

Insufficient storage for checkpoint record

ARIYX04

ARIYL14 nn

Create index - not enough virtual storage

(See note 1.)

for sort base

Insufficient storage for checkpoint record

ARIYX09

ARIYL17 nn

Get working storage error (See note 1.)

(See note 1.)

The index was at the maximum of eight

Get working storage error (File Descriptor

levels, and the insert would have caused

Block)

the index to expand to a ninth level.

Same as 01

ARIYX29

ARIYL18 nn

The index was at the maximum of eight

(See note 1.)

levels, and the INSERT would have

caused the index to expand to a ninth

Get working storage error (File Descriptor

level.

Block)

ARIYX36

Same as 01

An attempt was made to mark an entity

ARIYL19 nn

invalid but there are already 16 invalid

(See note 1.)

entities.

Get working storage error

More entries in the YINVALID table than

Get working storage error

the maximum number allowed.

ARIYL21 nn

ARIYZ00

(See note 1.)

Not enough virtual storage for restore

Insufficient storage

buffer

Insufficient storage

Not enough virtual storage for file

Insufficient storage

descriptor block

Insufficient storage (TABSTAT)

ARIYL23 nn

(See note 1.)

Note 1: These limit errors are caused by insufficient

Not enough virtual storage for archive

virtual storage. See message ARI0059E for

buffer

corrective action.

Not enough virtual storage for archive file

descriptor block

ARIYS08 nn

(See note 1.)

Sort REDO/UNDO - not enough virtual

storage for log record

ARIYT00 nn

Get working storage error (Counter

Internal Structure)

370

Messages and Codes

Chapter 24. System Errors

When a system error is detected, message

ARICMUDC

ARI0040E is issued. The text of the message is:

The following new SYSTERR codes may be set:

Error freeing prereceive buffer

ARI0040E A database manager system error

Error freeing input mailbox buffer

occurred - ARIxxxx nn

ARICOMB nn

Explanation: Communication Link error conditions

may have caused the message to be issued.

Communication Link error - REPLY

Communication Link errors are VSE XPCC errors. The

Same as 01

reason code (message ARI0042I) contains the system

return code. When any of these situations occurs,

ARICSHT nn

contact the designated support group for your

Communication Link error - TERMQSCE

installation.

(READY/RECOVERY)

Some of the error messages are shown below. ARIxxxx

Communication Link error - TERMQSCE

nn in the message is equal to:

(General)

ARICCLA nn

Communication Link error - TERMQSCE

Communication Link error -

(INDOUBT)

DISCONNECT

ARISIIO nn

ARICDSP nn

The database directory has not been

Communication Link error -

properly restored.

READY/RECOVERY AGENT (Reason

ARIYC25 nn

code of less than 5 is not valid.)

The DB2 Server for VSE system was

ARICENA nn

rolling back the drop index operation.

Communication Link error - CONNECT

Message ARI00421 contains the DBSS

Return Code. Refer to Chapter 17, “DBSS

ARICIP2 nn

Return Codes,” on page 231 for these

Communication Link error - SUBSID

codes.

Communication Link error - IDENTIFY

ARIYD77 nn

(General Purpose)

During recovery, an entry was found in

Communication Link error - IDENTIFY

the log for a delete, shorten, or update of

(INDOUBT)

a tuple, and the tuple does not exist in the

database. You will need to use filtered log

Communication Link error - IDENTIFY

recovery to BYPASS or ROLLBACK this

(READY/RECOVERY)

LUW.

ARICJACC

ARIYI01 NN

The following new SYSTERR codes may be set:

During an archive, a DB2 Server for VSE

Get working error or no storage for

system disk (directory, log or data disk)

accounting queue entry or on-line

was defined in VSAM with

accounting records

SHAREOPTIONS(1). The

Cannot find the accounting queue entry

SHAREOPTIONS will need to be set to 2,

for the on-line user

and the archive must be redone.

Cannot find the accounting queue entry

ARIYL00 nn

for the on-line user being at End Of

During warmstart, ARIYL00 tries to read

Transaction

the checkpoint record from the log and

ARICMUD nn

does not find a checkpoint at the address

pointed to by the directory.

Communication Link error - RECEIVE

Performing a restore, the log disk is

Communication Link error - PURGE

checked to find the last checkpoint that

371

System Errors

occurred before the restore (to determine

whether the current log needs to be

archived). This error occurs when the

record pointed to (by the LOGCID)is not a

checkpoint.

ARIYL26 nn

During a startup of the application server,

ARIYL26 scans the logs for the HSDS

(history area) of the logs and there are no

HSDS records in the logs. You may have

done a VSAM delete and define of the log

extents. Perform a coldlog and take a new

database archive immediately after

performing the coldlog. The coldlog will

write the HSDS record to the log.

ARIYX29 nn

Not enough index pages in the dbspace to

accomplish the INSERT

Not enough index pages in the dbspace to

accomplish the INSERT

NOTE 1

Other situations can occur where message

ARI0040E is issued. When any of these

situations occurs, make a record of what went

wrong and contact the designated support group

for your installation.

372

Messages and Codes

Chapter 26. DPROPR Messages

when Capture issued an EXEC SQL statement.

Introduction

User Response: Take action based on the SQLCODE

The following is a list of messages issued by the

and SQLERRMC descriptive text. For additional

IBM DPROPR Capture component of the IBM

information on the specific problem, refer to the

Relational Data Replication Tools for the VSE

appropriate SQLCODE in the section Chapter 18,

platform. A brief explanation of the status is

“SQLCODEs,” on page 237,or use the SQLCODE

provided.

numbers as the topic for the ISQL HELP command.

These messages are intended to aid the user, as

ASN0002E The Capture program could not connect

well as IBM Development and Support Center

to DB2. The routine name is routine; the

personnel.

SQLCODE is sqlcode.

Explanation: An error occurred when Capture issued

Unless otherwise stated, error messages are issued

a CONNECT function to the data base.

with a return code of 8.

User Response: Take action based on the SQLCODE.

For additional information on the specific problem,

ASN0000E-ASN0203I DPROPR

refer to the appropriate SQLCODE in the section

Chapter 18, “SQLCODEs,” on page 237, or use the

Capture Messages

SQLCODE numbers as the topic for the ISQL HELP

command.

ASN0000E INTERNAL ERROR OCCURRED FOR

MESSAGE NUMBER = message_number.

ASN0005E The Capture program encountered an

ITS SUBSTITUTION FIELDS ARE

error while reading the DB2 log. The

routine name is routine; the log sequence

sub1 sub2 sub3 sub4 sub5 sub6 sub7

number is log_sequence_number; the

ACCESS RC= return_code.

return code is return_code; the reason

code is reason_code.

Explanation: Capture was unable to read the file

containing messages. Note that message ASN0000E is

Explanation: An error occurred when Capture read

issued in English.

the DB2 log. There might be an SQL error.

User Response: See the messages and codes

A dump has been generated for this message. The

publication for your platform for information about

return code is for VSE/VSAM GET macro.

return codes to determine why Capture could not read

the messages file.

User Response: See Chapter 20, “DB2 Server for VSE

Reason Codes,” on page 355 for the appropriate reason

v Capture had a problem attempting to read the file.

code. For more information on VSE/VSAM errors, see

The file is specified in the MSGS DLBL job control

the VSE/VSAM Return and Error Codes manual.

statement.

Errors include:

4 - error on flocate()

ASN0006E The Capture program encountered an

8 - error on fread()

unexpected log error of unknown log

12- error on fopen()

variation. The routine name is routine.

Explanation: An unexpected log error occurred while

Examine the message description for message_number to

Capture was processing the DB2 log records. Capture

determine the underlying error.

could not determine the type of SQL update associated

with the log record.

ASN0001E The Capture program encountered an

User Response: Contact your IBM Service

SQL error. The routine name is routine;

Representative.

the SQL request is request; the table

name is table_name; the SQLCODE is

sqlcode; the SQLERRML is sqlerrml; the

ASN0007E The Capture program encountered an

SQLERRMC is sqlerrmc

unexpected log error of an

unimplemented data type. The routine

Explanation: A nonzero SQLCODE was returned

name is routine.

375

IBM DPROPR Capture - ASN0000E-ASN0203I

Explanation: The SQL type in the log record data was

ASN0014E The processing of the Capture program

invalid. A table might have been registered without the

has fallen below a minimum level. The

Replication Center and contains unsupported SQL

log record lags current time by number

types (e.g. LONG or large object types).

seconds. The routine name is routine.

User Response: Cancel the registration and use the

Explanation: Capture terminated because a high DB2

Replication Center to register tables, to ensure only

transaction rate caused the Capture program to run

valid types are registered. Or, when manually

slower than the defined minimum level.

registering a table, ensure that the table has supported

SQL types. See the DB2 for VSE & VM Replication

User Response: Refer to the DB2 for VSE & VM

Supplement for information about unsupported data

Replication Supplement manual for more information on

types.

the lag limit. Perform a cold start.

ASN0008I The Capture program was stopped.

ASN0015E The Capture program encountered a

storage allocation error. The routine

Explanation: This informational message is issued

name is routine; the storage required is

when the STOP command is entered.

amount.

User Response: None required.

Explanation: A storage allocation error was detected;

sufficient storage is not available.

ASN0009E The table was created without the

User Response:

DATA CAPTURE CHANGES attribute.

The routine name is routine; the table

All available GETVIS storage has been exhausted. You

name is table_name.

may need to restart the Capture program after

allocating a larger partition.

Explanation: The source table was defined without the

DCC attribute and the Capture program tried to

capture changes for the replication source.

ASN0016E The Capture program could not begin

capturing changes because there was not

User Response:

an eligible replication source.

1. Stop the Capture program.

Explanation: The replication source information has

2. Delete the replication source.

not been defined.

3. Define the replication source again, if you do not

Capture started but could not find source tables that

have the Data capture is full-refresh only check

were:

box selected, the Replication Center will alter the

v Enabled with the DATA CAPTURE CHANGES

source table with the DCC attribute.

option of the CREATE or ALTER TABLE statement.

4. Start the Capture program.

v Defined as replication sources with the Data capture

is full-refresh only check box cleared on the Define

ASN0010E The Capture program can not obtain

as Source window.

enough storage. The routine name is

User Response: Ensure that the register table is

routine; the storage required is amount.

defined properly. For more information about the

Explanation: The Capture program cannot continue

processing because not enough free storage is available.

Supplement Verify that replication sources have been

defined.

User Response:

All available GETVIS storage has been exhausted. You

ASN0017E The Capture program encountered a

may need to restart the Capture program after

severe internal error and could not issue

allocating a larger partition.

the correct error message. The routine

name is routine; the return code is

ASN0013E The Capture program required a column

return_code.

that was not defined in the change data

Explanation: An unexpected error occurred while

table. The routine name is routine; the

Capture was executing.

table name is table_name.

User Response: Contact your IBM Service

Explanation: The user did not define an IBMQREP

Representative.

required column in the change data table.

User Response: Ensure that the change data table

definition is correct. Refer to the DB2 for VSE & VM

Replication Supplement for more information.

376

Messages and Codes

IBM DPROPR Capture - ASN0000E-ASN0203I

ASN0018W The Capture program did not process

ASN0026W The Capture program could not allocate

updates made to the register table rows.

the trace buffer. The routine name is

The routine name is routine; the table

routine; the storage required is amount.

name is table_name.

Explanation: A storage allocation error was detected;

Explanation: The user changed a replication source

not enough storage is allocated for the trace buffer. The

while the Capture program was running and then

trace buffer is an information-only feature of Capture

issued a REINIT command. The register table, which

and the allocated storage is not required for Capture to

contains a row for each registration, might not match

run.

the other replication source control tables.

User Response:

All available GETVIS storage has been exhausted. You

1. Stop Capture.

may need to restart the Capture program after

2. Delete the replication source.

allocating a larger partition.

3. Redefine the replication source.

4. Start Capture.

ASN0028I The Capture program is suspended by

operator command

ASN0022E DB2 release release is not supported. The

routine name is routine.

Explanation: An operator command has suspended

the Capture program, and the program has entered a

Explanation: The Capture program does not support

wait state.

this release of DB2.

User Response: This message is for your information

User Response: Run the Capture program with the

only, and no action is required.

appropriate release of DB2.

ASN0029I The Capture program is resumed by

ASN0023I The Capture program successfully

operator command.

reinitialized the register table. The table

name is table_name.

Explanation: An operator command has resumed the

Capture program from a suspended state, and the

Explanation: A REINIT command was issued and the

Capture program has continued running.

updates were successfully made to the Capture internal

control information.

User Response: This message is for your information

only, and no action is required.

User Response: None required. This is an

informational message.

ASN0030I The Capture program command or

parameter entered by the operator was

ASN0024I The Capture program did not need to

unrecognized.

reinitialize the register table. The table

table_name did not change.

Explanation: This message is issued when a command

is not recognized by the Capture program. The only

Explanation: The REINIT command was issued. No

valid commands are:

updates were made to the register table since

STOP

initialization or the last REINIT.

REINIT

User Response: None required. This is an

REINITQ

informational message.

PRUNE

CHGPARMS

QRYPARMS

ASN0025I The Capture program reinitialized the

STATUS

SUSPEND

number potentially bad row(s).

RESUME

Explanation: This message accompanies ASN0018W.

User Response: Use only valid Capture program

Reinitialization was performed as requested despite

commands.

potential problems reported in ASN0018W.

User Response: See ASN0018W. This is an

ASN0031E The Capture program tuning parameter

informational message.

table can have only one row. The

routine name is routine; the table name

is table_name.

Explanation: The tuning parameter table was not

Chapter 26. DPROPR Messages

377

IBM DPROPR Capture - ASN0000E-ASN0203I

defined correctly or has been updated with invalid

ASN0060E pgmname : program_qualifier : The Capture

rows.

program encountered an internal error

User Response: Refer to the DB2 for VSE & VM

error_code.

Replication Supplement to determine the correct format

Explanation: An unexpected error occurred in the

of this table. Remove any invalid rows.

Capture program. The Capture program terminates.

User Response: Contact IBM Software Support for

ASN0033E The Capture program could not

assistance.

reinitialize the register table. The table

name is table_name.

ASN0061E pgmname : program_qualifier : A

Explanation: The Capture program tried to reinitialize,

registration that is not valid has been

but there was an error in the register table. A user

found. Source table source_owner.

might have tried to update a replication source while

source_table does not exist in the system

the Capture program was running or suspended, and

catalog tables.

the register table might not match the other control

tables.

Explanation: The Capture program tried to initialize a

registration and found that the source table specified in

User Response: This is a secondary message. See any

the registration was not in the source system catalog.

preceding messages for more information about the

This message is issued during Capture warm start or

error. See the DB2 for VSE & VM Replication Supplement

when the Apply program issues the first CAPSTART

for more information about reinitializing Capture and

signal for a subscription set that contains a registration

about the register table.

that is not valid. This error does not cause the Capture

program to terminate. The values for the columns

ASN0034E An incorrect value was supplied for

source_owner and source_table in the Capture control

column column of the Capture program

table IBMQREP_SUBS might have been incorrectly

tuning parameter table. The routine

specified, or the source table was dropped and no

name is routine; the table name is

longer exists.

table_name.

User Response: If the source table no longer exists,

Explanation: The tuning parameters table does not

then the registration is no longer valid and can be

have the correct values. Values might be out of range.

removed.

User Response: Refer to the DB2 for VSE & VM

Replication Supplement for more information. Check the

ASN0065E pgmname : program_qualifier : A

lag limit, retention period and commit frequency.

registration that is not valid has been

found. The source table

source_owner.source_table is not a local

ASN0035W Some rows were found in the register

physical table.

table with an unsupported architectural

level. The routine name is routine; the

Explanation: The Capture program tried to initialize a

table name is table_name.

registration and found that the source table for the

registration is a not a local physical table, but is instead

Explanation: The register table version does not match

on a non-DB2 relational server that is used as a source

the current version of the Capture program. The

and called by a nickname. When a non-DB2 relational

current version of the Replication Center is not

server is used as a source, data from each server is

compatible with the version of Capture that you are

captured through a trigger program. Each source table

running.

must be in its own register table built on the non-DB2

User Response: Refer to the DB2 for VSE & VM

relational server. This message is issued during a

Replication Supplement to check the required value for

Capture warm start or when the first CAPSTART signal

the ARCH_LEVEL column in the register table. Verify

against this registration is received for a subscription.

that the value in the register table at the source server

This error does not cause the Capture program to

is correct. If not, use compatible versions of the

terminate. The registration has been created incorrectly

Replication Center and the Capture program.

in an IBMQREP_SUBS table in a DB2 database.

User Response: This registration must be rebuilt and

ASN0036E DB2 was terminated abnormally. The

made valid at the correct non-DB2 relational server.

routine name is routine.

Explanation: DB2 was terminated while the Capture

program was still active.

User Response: Start DB2 and start the Capture

program.

378

Messages and Codes

IBM DPROPR Capture - ASN0000E-ASN0203I

which Capture captures changes.

ASN0100I The Capture program initialization is

successful.

User Response: None required. This is an

informational message.

Explanation: The Capture program initialization was

successfully performed. If Capture was started with the

NOTERM option and and DB2 terminates, this message

ASN0105I Data that has been copied was pruned

is also issued by Capture after DB2 comes back up.

from the change data table table_name

and the unit-of-work table.

User Response: None required. This is an

informational message.

Explanation: This is an informational message to

indicate the pruning operation was performed.

ASN0101W The Capture program warm start failed

User Response: None required.

because existing data is too old; a cold

start will be attempted.

ASN0106I The Capture program is waiting for DB2

Explanation: The data in the change data tables is

to come up.

older than the value current_timestamp-lag_limit. A cold

Explanation:

start will be performed.

If the NOTERM option is specified on the ASNCCP

User Response: None required. This is an

command, Capture will wait for DB2 to come back up

informational message. See the DB2 for VSE & VM

when DB2 fails. The operator can stop Capture with

Replication Supplement for more information about

the STOP command while it is waiting.

warm and cold starts to determine why the Capture

program could not warm start.

User Response: None required. This is an

informational message.

ASN0102W pgmname : program_qualifier : The

program will attempt to switch to cold

ASN0111I pgmname : program_qualifier : The pruning

start because the warm start information

cycle started at timestamp.

is insufficient.

Explanation: This message is issued at the beginning

Explanation: A problem occurred during the retrieval

of each pruning cycle.

of the restart information. A cold start will be

User Response: This message is for your information

attempted.

only, and no action is required.

v STARTMODE = WARMSI and the RESTART queue is

empty. This means that replication has never been

attempted before. You must cold start the first time.

ASN0112I pgmname : program_qualifier : The pruning

cycle ended at timestamp.

v STARTMODE = WARMSA and warm start failed.

Option WARMSA allows a switch to cold start if any

Explanation: This message is issued at the termination

problems are encountered with the warm start.

of each pruning cycle.

User Response: This is an informational message. See

User Response: This message is for your information

the DB2 Replication Guide and Reference for more

only, and no action is required.

information about warm and cold starts to determine

why the Capture program could not warm start.

ASN0117I Warm start control information was not

saved. The routine name is routine; the

ASN0103I The Capture program started. The

table name is table_name.

Enq_name is enq_name; the start_type is

start_type; the term_type is term_type; the

Explanation: An error occurred that prevented warm

prune_type is prune_type.

start information from being saved in the

IBMQREP_WARM_START table. Warm start can be

Explanation: This is an informational message that

attempted and can take longer because backup sources

displays the Capture start up options.

will be used.

User Response: None required.

User Response: None required. This is an

informational message.

ASN0104I Change capture started for owner owner;

the table name is table_name at log

ASN0120I DataPropagator Relational Log Read

sequence number log_sequence_number.

Feature Trace Buffer contents:

Explanation: Capture was started for the table owner

Explanation: This header appears prior to the trace

and table name at the specified log sequence number

buffer, which is printed in case of severe error.

(LSN). This message is issued for each base table for

379

Chapter 26. DPROPR Messages

IBM DPROPR Capture - ASN0000E-ASN0203I

User Response: None required. This is an

informational message.

informational message only.

ASN0121E The Capture program warm start failed

ASN0200E An incorrect parameter parameter was

because existing data is too old; the

passed to the Capture program.

Capture program will terminate.

Explanation:

Explanation: The time of the warm start information

For VSE,

exceeded LAG_LIMIT.

v An incorrect parameter was specified on the

User Response: No response required; the Capture

ASNCCP start up command.

program will terminate because WARMNS was

specified.

User Response: Verify the values supplied.

ASN0122E pgmname : program_qualifier : An error

ASN0201E The Capture program encountered a

occurred while reading the warm start

platform error. The routine name is

information or DB2 log. The Capture

routine; the function name is function; the

program will terminate.

return code is return_code.

Explanation: A problem occurred while retrieving the

Explanation: For platform VSE,

restart information. The restart table data was not valid.

v For functionname GENCB, MODCB, OPEN, GET,

When the error is resolved, you can restart using the

CLOSE, or ENDREQ errors see the IBM VSE/ESA

warm start option.

Messages & Codes under 42xxx and 4Axxx (for IBM

VSE/VSAM macros). Capture received an error

User Response: Determine why the restart

while trying to set-up or read the database log or

information could not be retrieved by Capture from

directory.

IBMQREP_RESTART. Look at previous messages for

clues as to what may have gone wrong. Correct the

v For functionname GETVIS, FREEVIS, or XPCC errors

problem, if possible and restart Capture warm. If the

see the IBM VSE/ESA System Macros Reference

problem cannot be corrected, restart Capture cold.

Capture received an error while trying to perform

one of these functions.

ASN0123I The highest log sequence number of a

User Response: Correct the error as described in the

successfully captured log record is

VSE documentation.

log_sequence_number

Explanation: The Capture program saved the highest

ASN0202E The USERID parameter was not

log sequence number (LSN) in the warm start table.

specified.

This is the point at which the Capture program

Explanation: The USERID parameter is required in the

finished successfully processing the log data.

PARM= field on the EXEC job control statement is

User Response: No response required; this message

passed to the Capture program.

accompanies termination.

User Response: Add the USERID= parameter,

specifying the userid and password, in the PARM=

ASN0124I The prune command was accepted; the

field and resubmit the job.

pruning action is queued.

Explanation: This informational message is issued

ASN0204E pgmname : program_qualifier : An error

when the PRUNE command is entered. The Capture

occurred when running the dataspace

program has queued the request. Capture will prune

function dataspace_function for dataspace

the change data (CD) table and the unit-of-work

dataspace_name; the return code is

(UOW) table.

return_code, the reason code is

reason_code.

User Response: No response required.

Explanation: An error occurred when CREATING,

ADDING AN ACCESS LIST ENTRY FOR, REMOVING

ASN0125I The current log sequence number of

AN ACCESS LIST ENTRY, DESTROYING, READING

successfully captured log records is

FROM OR WRITING TO a dataspace.

log_sequence_number. The log timestamp

is timestamp.

If the dataspace function is:

v CREATING - the DSPSERV CREATE macro was

Explanation: The Capture program is processing the

issued

DB2 log at the log sequence number provided.

v ADDING AN ACCESS LIST ENTRY FOR - the

ALESERV ADD macro was issued

380

Messages and Codes

IBM DPROPR Capture - ASN0000E-ASN0203I

v REMOVING AN ACCESS LIST ENTRY FOR - the

ASN0503E pgmname : program_qualifier : The integer

ALESERV REMOVE macro was issued

value input_value, supplied for parameter

v DESTROYING - ADRSPACE DESTROY - the

parameter_name, is outside the supported

DSPSERV DELETE macro was issued

range for this parameter.

User Response: Check the return code/reason code in

Explanation: The program or a command program

the VSE/ESA Systems Macro Reference manual for the

was invoked with an input value specified which is

macro corresponding to the dataspace_function.

outside the supported range. The message indicates the

name of the program that is reporting the error, which

input value is incorrect, and for which parameter this

ASN0500E pgmname : program_qualifier : The

input value was specified.

parameter input input_value supplied for

parameter name parameter_name is not

User Response: Correct the invocation to include the

valid.

correct range value for the parameter input and

resubmit it.

Explanation: The program or a command program

has been invoked with a specified input parameter that

is not valid. The message indicates the name of the

ASN0504E The program did not recognize the

program that is reporting the error, along with the

invocation parameter incorrect_input.

parameter name and the parameter value.

Explanation: The program or a command program

User Response: Check the documentation on valid

has been invoked with a specified parameter or

invocation parameters, correct the input, and resubmit

command that is not valid. The message indicates

the task or command.

which program issued this message, and the invocation

input that is unrecognized.

ASN0501E pgmname : program_qualifier : The value

User Response: Check the documentation on valid

input_value supplied for the parameter

input parameters, correct the input and resubmit the

parameter_name is not the correct data

task or command.

type.

Explanation: The program or a command program

ASN0509E pgmname : program_qualifier : The

was invoked with an input value with an associated

program could not process a received

data type that is not valid. The message indicates the

message because of an incorrect message

name of the program that is reporting the error, the

version.

incorrect input value, and the name of the parameter

Explanation: The program or a command program

for which this input value was specified.

encountered an internal error while trying to process a

User Response: Correct the invocation to include the

user command. The program did not terminate for this

correct data type for the parameter input and resubmit

failure, but the command did not get executed.

it.

User Response: Retry the failing command. Contact

IBM Software Support if the problem persists.

ASN0502E pgmname : program_qualifier : The value

input_value of length invalid_string_length,

ASN0511E pgmname : program_qualifier : The

supplied for parameter parameter_name,

program was unable to process the

is greater than the maximum allowed

received message because of an

string length of allowed_string_length.

unknown message function.

Explanation: The program or a command program

Explanation: The program encountered an internal

has been invoked using an input value with a string

error while trying to process a user command. The

length that is not valid. The message indicates the

program did not terminate for this failure, but the

name of the program that is reporting the error, what

command did not get executed.

input value is incorrect, and for which parameter this

input value was specified.

User Response: Retry the failing command. Contact

IBM Software Support if the problem persists.

User Response: Correct the invocation to include the

correct string length for the parameter input and

resubmit it.

ASN0513E pgmname : program_qualifier : The

program could not open the message

file named msg_file.

Explanation: This message file used by the program

has been installed incorrectly, or the language

environment variables are not set correctly.

Chapter 26. DPROPR Messages

381

IBM DPROPR Capture - ASN0000E-ASN0203I

User Response: Refer to the documentation for

ASN0519E The parameter input parameter_value

information about installation and configuration.

supplied for CHGPARMS parameter

parameter_name is not valid.

ASN0514E pgmname : program_qualifier : The

Explanation: The CHGPARMS command was invoked

program could not open the log file

with incorrect parameter input.

log_file.

User Response: Correct the command input and

Explanation: The program encountered an internal

resubmit the command.

error while trying to open a file for its own program

message log, and terminates abnormally because of this

failure. This problem might have occurred because the

ASN0520I pgmname : program_qualifier : The

file was inadvertently deleted, or because the userid

STATUS command response: thread_type

associated with this process does not have the sufficient

thread is in the status_condition state.

authority to open the file.

Explanation: In response to the status command, one

User Response: Verify that sufficient authority is

of these messages will be issued for each of the threads

provided to the processing userid. If the file was

associated with the program that received the

inadvertently deleted, restart the program to create a

command, in each case providing the current state of

new log file.

that thread.

User Response: This message is for your information

ASN0515E pgmname : program_qualifier : The

only, and no action is required.

program could not close the log file.

Explanation: The program encountered an internal

ASN0521I pgmname : program_qualifier : The

error while trying to close the file used for its own

QRYPARMS command response:

program message log. The file might have been deleted

parameter_name was set to parameter_value

inadvertently before the program tried to terminate.

by the following method: method.

Final termination messages might not be issued.

Explanation: In response to the QRYPARMS

User Response: If the file was inadvertently deleted,

command, a message will be issued for each of the

restart the program to create a new log file.

program parameters. For each parameter, the message

provides the name of the parameter, the current setting

of the parameter, and the method (by default, by

ASN0516E pgmname : program_qualifier : The

changing the IBMQREP_CAPPARMS table, by the

program could not close the message

startup option, or by the use of the CHGPARMS

catalog.

command) that was employed by the user to set the

Explanation: The program encountered an internal

value of the parameter.

error while trying to close the message catalog file. The

User Response: This message is for your information

file might have been deleted inadvertently before the

only, and no action is required.

program tried to terminate. Final termination messages

might not be issued.

ASN0522I pgmname : program_qualifier : The

User Response: If the message file has been deleted, it

program received the command_type

needs to be reinstalled.

command.

Explanation: The program received a command to be

ASN0518E pgmname : program_qualifier : The

processed.

program does not accept multiple

commands.

User Response: This message is for your information

only, and no action is required.

Explanation: The command program was invoked

with multiple commands specified. Each command

invocation must be performed with a single input

ASN0523I pgmname : program_qualifier : The

command, along with any other required command

CHGPARMS command response:

input. Note: The CHGPARMS command allows

parameter_name has been set to

multiple parameters to be changed with one invocation

parameter_value.

of the CHGPARMS command.

Explanation: In response to the CHGPARMS

User Response: Correct the command input, and

command, one of these messages will be issued for

resubmit the command.

each of the program parameters that was changed. For

each parameter, the message provides the new value

for the parameter.

User Response: This message is for your information

382

Messages and Codes

IBM DPROPR Capture - ASN0000E-ASN0203I

only, and no action is required.

parameters table, or by the startup option.

User Response: This message is for your information

ASN0524E pgmname : program_qualifier : The

only, and no action is required.

program required parameter

parameter_name was not specified.

ASN0530E pgmname : program_qualifier : The

Explanation: The program or a command program

program could not connect to database

was invoked without one of the required parameters

database_name with USERID user_id . The

specified.

SQLCODE is sql_code.

User Response: Correct the invocation to include the

Explanation: An error occurred when the program

appropriate parameter and its corresponding input

issued one of the following functions:

value.

v a CONNECT function to DB2 for VSE and VM

User Response: See the DB2 codes in the messages

ASN0526E The program was invoked without any

and codes publication of the DB2 database manager on

command input.

your operating system for the appropriate reason code.

Explanation: The command program was invoked

without a command to process. No command

ASN0533E pgmname : program_qualifier : DB2 was

processing is performed.

terminated abnormally.

User Response: Resubmit the command with all the

Explanation: DB2 was terminated while the program

required input.

was still active and the user did not specify the

NOTERM invocation parameter.

ASN0527E The program was invoked without any

User Response: Start DB2 and start the program.

CHGPARMS command input.

Explanation: The commands program was invoked

ASN0537E pgmname : program_qualifier : The

with the CHGPARMS command but without any

program could not connect to database

command input to process. No command processing is

database_name, the return code is

performed.

return_code, and the reason code is

reason_code.

User Response: Resubmit the command with all the

required input.

Explanation: An error occurred when the program

issued one of the following functions:

ASN0528E pgmname : program_qualifier : The

v a CONNECT function to DB2 for VSE and VM

program will terminate because the

v a CONNECT function to DB2 Call Attachment

required control table

Facility (CAF)

tableowner.tablename does not exist.

v an implicit connect to DB2 UDB

Explanation: The Capture or the Apply program tried

User Response: See the DB2 codes in the messages

to execute an SQL operation against a required Capture

and codes publication of the DB2 database manager on

control table. The program received a not found return

your operating system for the appropriate reason code.

code from DB2. The return code occurs either if the

migration has not been completed or if a required

Capture control table has been accidentally dropped

ASN0541E An incorrect value column_value was

from the environment.

supplied for column column_name of the

program parameter table parms_table.

User Response: See the message text for the name of

the missing control table. Create the table and restart

Explanation: This message is issued during

the Capture program.

initialization of the Capture program if the validation

of the IBMQREP_CAPPARMS table found that one of

the parameter value settings is not valid. The Capture

ASN0529I pgmname : program_qualifier : The value of

program terminates with this error.

parameter_name was set to parameter_value

at startup by the following method:

User Response: Check the documentation for

method.

permitted parameter values allowed in this table.

Correct the values and restart the Capture program.

Explanation: The program started, and the program

parameters were initialized based on the combination

of startup options that are specified and the existing

contents of the parameters table. The parameters were

set by one of the methods: by default, by changing the

Chapter 26. DPROPR Messages

383

IBM DPROPR Capture - ASN0000E-ASN0203I

needs to be investigated, such as an out of space

ASN0542E The maximum number of lock time-out

condition, or DB2 is unavailable for use by

or deadlock retries has been reached,

applications. This message is sometimes followed by a

SQLSTATE sqlstate was returned.

second message that provides information about what

Explanation: The Capture program has internally

replication was doing when this SQLCODE was

retried a time-out or deadlock condition multiple times.

encountered.

If the program task that receives the persistent lock

User Response: See the messages and codes

condition is critical the whole Capture program

documentation of the DB2 database manager on your

terminates. If the program task is not critical, such as

operating system for an explanation of this SQLCODE

pruning, then the task will be retried at a later time,

and for information about corrective actions that might

and the Capture program remains active.

need to be taken in DB2. If replication issued another

User Response: Check for corresponding database

message immediately following this one, see the

messages that might provide additional detail about the

explanation and user response for that message.

source of the locking contention. Correct the situation if

the error is a user error, such as a user held lock. If the

ASN0553E pgmname : program_qualifier : Internal

condition persists, contact IBM Software Support for

error error_number occurred for message

assistance.

number msg_number containing

num_tokens substitution fields:

ASN0543E The program cannot obtain bytes_number

sub_tokens.

bytes of storage for a object.

Explanation: The error number is a decimal internal

Explanation: The program is unable to obtain memory

error number which is defined as:

for a necessary in-memory storage structure. The

Instance is not valid

program terminates.

Access denied

User Response: Consider allowing a larger memory

allowance to the program, then restart the program.

No files

No message

ASN0544E pgmname : program_qualifier : The

Locale is not valid

program is already active.

System error

Explanation: You tried to start more than one Capture

program per DB2 subsystem or database.

Not enough memory

User Response: Ensure that the schema or qualifier is

specified correctly.

The msg_number is the message that the program was

trying to issue. The num_tokens is the number of

v Run only one Capture program per database using a

substitution tokens given for the message (not

given schema.

including the pgmname and program_qualifier tokens).

The sub_tokens is the substitution tokens for the

ASN0548I pgmname : program_qualifier : The

message in error separated by commas.

program received an operator stop

User Response: Take any corrective action possible

command.

based on the error code given. For example, if the

Explanation: This informational message indicates that

message file was not found or could not be accessed,

a stop command was issued to the program.

you should also see message ASN0513 which gives you

the file name. Verify that the message file exists with

User Response: This message is for your information

the correct permissions. If you get error code 4, you

only, and no action is required.

might have an old message file.

ASN0552E pgmname : program_qualifier : The

ASN0554E pgmname : program_qualifier : The

program encountered an SQL error. The

program encountered a DB2 log full

server name is server_name. The SQL

condition on server server_name.

request is sql_request. The table name is

table_name. The SQLCODE is sqlcode. The

Explanation: The program tried to process an insert or

SQLSTATE is sqlstate. The SQLERRMC

update which was denied by DB2 because the DB2

is sql_tokens. The SQLERRP is

transaction log is full. The program will stop

error_module.

processing.

Explanation: A nonzero SQLCODE returned when the

User Response: Check the amount of space remaining

Capture program issued an EXEC SQL statement. This

on the filesystem containing your database files.

SQLCODE might be caused by a DB2 problem that

Increase the size of the log data set, or commit more

384

Messages and Codes

IBM DPROPR Capture - ASN0000E-ASN0203I

often in long running applications.

ASN0563W pgmname : program_qualifier : The

parameter parameter-1 is not compatible

ASN0557E pgmname : program_qualifier : The value

with parameter parameter-2. The

column_value for column column_name of

parameter parameter-1 will be ignored.

owner.table with source table

Explanation: The program was started with both

source_owner.source_table, is not valid.

parameters specified in the command or in the

Explanation: The Capture program tried to initialize a

parameters table. These parameters are not compatible.

registration and found a value that is not valid for a

One parameter was ignored when the program started

column in the register (IBMQREP_SUBS) table.

and continued to run.

User Response: Correct the value for the column in

User Response: The next time you start the program,

error. Refer to the description of the register table for

specify only the parameter that you want the program

valid values for the column in error.

to use.

ASN0558E pgmname : program_qualifier : The

ASN0566E program_name : program_identifier :

parameter table parameter_table can have

Pruning of table table_name failed with

only one row corresponding to program

SQL return code sqlcode.

qualifier program_qualifier.

Explanation: Pruning failed with an unexpected SQL

Explanation: The program parameters table was not

error code. This error does not cause the program to

defined correctly or was updated with rows that are

terminate. The program will try to prune the table

not valid.

again at the next pruning interval or when the program

is restarted.

User Response: Ensure that there is only one row in

the parameter table corresponding to the

User Response: If this SQL return code indicates a

program_qualifier. Ensure that the parameters table has a

temporary error, then no action is required. Otherwise,

unique index on the program qualifier. Refer to the

take action as indicated for the SQL error in the DB2

description of the parameter tables for additional

Messages and Codes manual.

information.

ASN0567I program_name : program_identifier : number

ASN0560E pgm_name : program_qualifier : The

rows were pruned from table table_name.

program is unable to create db_object

Explanation: See message text.

object_name in database db_name

User Response: This message is for your information

Explanation: The program is unable to create the

only. No action is required.

database object in the database.The database object is

being created in the same object table space as the

server control tables.

ASN0569E program_name : program_identifier : The

program encountered an internal error

User Response: Review the SQL error code that is

error_code.

related to this error message and take the appropriate

action.

Explanation: An unexpected error occurred in the

program. The program will terminate.

ASN0561W pgmname : program_qualifier : The

User Response: Contact IBM Software Support for

program’s application code page

assistance.

application_code_page is not the same as

code page database_code_page of database

ASN0570I program_name : program_identifier : The

database.

program failed to obtain the code page

Explanation: For OS/400 only. The Capture program’s

information of the application client

application code page is not compatible with the code

program MQCAP: error description. The

page of the database for which it is capturing data.

default code page INTERNATIONAL is

This can result in corrupted data or unexpected errors

used.

when the Capture program inserts data into CD tables.

Explanation: The program failed to obtain the code

User Response: If the code pages are compatible, no

page information of the capture problem on VM, or

action is required. If the code pages are incompatible,

failed to access the SQLGLOB file on VSE. The default

stop the Capture program, change the Capture

code page INTERNATIONAL is used as the target code

program’s application code page to be that of the

page for ccsid conversion when handling the ADMINQ

database, and restart the Capture program.

messages.

User Response: For SQLGLOB file open error, make

Chapter 26. DPROPR Messages

385

IBM DPROPR Capture - ASN0000E-ASN0203I

sure there is a DLBL for the SQLGLOB file. Contact

Apply program is stored in the IBMQREP_TARGETS

IBM Software Support for assistance.

table.

User Response: See the reason code documentation in

ASN0571E program_name : program_identifier : The

the WebSphere MQ Application Programming

program cannot start because the

Reference for an explanation of this WebSphere MQ

parameter table table_name is empty or it

reason code and for information about actions that you

contains more than one row.

might need to take.

Explanation: The program parameter table must have

exactly one row.

ASN0576E program_name : program_identifier : The

program cannot access the WebSphere

User Response: Before you start the program, use the

MQ queue queue_name.

replication administration tools to redefine the content

of the parameter table so that it contains exactly one

Explanation: Either the queue does not exist or it is

row.

specified incorrectly in the control tables. The program

terminated as a result of this error.

ASN0572I program_name : program_identifier : The

User Response: Ensure that the queue name is

program initialized successfully.

specified correctly in the control tables and that it is

accessible to application programs. Create the queue if

Explanation: See message text.

it does not exist.

User Response: This message is for your information

only. No action is required.

ASN0580E program_name : program_identifier : The

license for product product_name was not

ASN0573I program_name : program_identifier : The

found.

program was stopped.

Explanation: The program terminated because it

Explanation: See message text.

cannot run without a license.

User Response: This message is for your information

User Response: Install the program license or contact

only. No action is required.

your IBM representative.

ASN0574E program_name : program_identifier : The

ASN0777I pgmname : program_qualifier : Additional

WebSphere MQ queue manager

information message_text, reason code(s):

queue_manager_name is not available or it

rc1, rc2, rc3.

was not started. The program will

Explanation: The Additional information shown in this

terminate.

message refers to an informational text message. The

Explanation: The program cannot connect to the

reason codes provide supplemental return code

WebSphere MQ queue manager. This error causes the

information related to this message text. If an

program to terminate.

informational code field is not applicable, it contains ″*″

(an asterisk).

User Response: Ensure that the WebSphere MQ queue

manager started successfully before running the

User Response: This message is for your information

program.

only, and no action is required.

ASN0575E program_name : program_identifier : The

ASN0999E pgmname : program_qualifier : Error

program encountered a WebSphere MQ

condition message_text, error code(s): rc1,

error reason_code while issuing the

rc2, rc3.

WebSphere MQ command command on

Explanation: The Error condition shown in this

queue queue_name.

message is the description of an error that occurred in

Explanation: A nonzero WebSphere MQ reason code

the specified program with the specified qualifier (if

was returned when the program issued an WebSphere

displayed). The error codes provide supplemental

MQ command. The reason code indicates that there is a

information related to this message text. If an error

WebSphere MQ problem (for example, storage is not

code field is not applicable, it contains ″*″ (an asterisk).

available for WebSphere MQ objects) or that WebSphere

User Response: Use the information from the Error

MQ is not available.

condition and from the specified error codes to

The ERROR_ACTION value determines how the

determine the cause of the error. Contact IBM Software

program behaves due to this error. The value for the Q

Support if you cannot resolve the error.

Capture program is stored in the

IBMQREP_SENDQUEUES table. The value for the Q

386

Messages and Codes

IBM DPROPR Capture - ASN0000E-ASN0203I

to accommodate one row in a transaction for this Q

ASN7000I pgmname : program_qualifier : number

subscription.

subscriptions are active. number

subscriptions are inactive. number

User Response: Increase the MAX_MESSAGE_SIZE

subscriptions that were new were

value in the IBMQREP_SENDQUEUES table for this

successfully activated. number

send queue. If necessary, increase the MAXMSGL

subscriptions that were new could not

attribute:

be activated and are now inactive.

v For remote send queues, increase the MAXMSGL

Explanation: This message describes the number of Q

attribute of the transmission queue.

subscriptions that are in various states.

v For local send queues, increase the MAXMSGL

attribute.

User Response: This message is for your information

only. No action is required.

The MAX_MESSAGE_SIZE column value also must not

exceed the MAXMSGL attribute of the WebSphere MQ

queue manager.

ASN7001I pgmname : program_qualifier : The

command_name command was received.

Restart the Q subscription.

Explanation: The command that was received might

be processed asynchronously. The program will issue a

ASN7006E pgmname : program_qualifier : Q

message when the command is processed and store

subscription name was deactivated.

that message in the trace table

(IBMQREP_CAPTRACE).

Explanation: The specified Q subscription was

deactivated due to an error that was specified in a

User Response: This message is for your information

previous message.

only. No action is required.

User Response: Look in the Q Capture diagnostic log

or in the IBMQREP_CAPTRACE table to find the error

ASN7004E pgmname : program_qualifier : The source

message that precedes this one. Take the appropriate

column source_column subscribed in Q

action to correct the problem (follow the instructions in

subscription name does not exist in the

the user response of the previous message). Activate

source table table_name.

the Q subscription.

Explanation: The column shown in the

IBMQREP_SRC_COLS table does not exist in the source

ASN7008I program_name : program_identifier : The

table. This error occurred due to one of the following

program was successfully reinitialized.

problems:

number subscriptions are active. number

v The column name was specified incorrectly in the Q

subscriptions are inactive. number

subscription.

subscriptions that were new were

v The source table changed since the Q subscription

successfully activated. number

was created.

subscriptions that were new could not

v Extra columns were specified in the Q subscription.

be activated and are now inactive.

Therefore, the Q subscription cannot be activated.

Explanation: The REINIT command was processed

successfully. As a result, the Q Capture program

User Response: Ensure that the column name is

recognizes any changed attributes for Q subscriptions

specified correctly in the Q subscription.

and queue maps. Any new Q subsriptions were

automatically activated. Refer to the message text for

If the Q subscription is not correct (for example,

the number of Q subscriptions that are in various

because it contains more columns than are available at

states.

the source table), use the replication administration

tools to perform the following steps:

User Response: This message is for your information

1. Drop the Q subscription and recreate it.

only. No action is required.

2. Activate the Q subscription.

ASN7009I pgmname : program_qualifier : Send queue

queue_name of replication queue map

ASN7005E program_name : program_identifier : The Q

queue_map_name was successfully

subscription name was deactivated

reinitialized.

because the specified

MAX_MESSAGE_SIZE is too small for

Explanation: The Q Capture program successfully

the send queue queue_name, replication

reinitialized a send queue and it will process

queue map queue_map_name. number

transactions according to the new queue attributes.

bytes are required.

Explanation: The maximum message size is too small

Chapter 26. DPROPR Messages

387

IBM DPROPR Capture - ASN0000E-ASN0203I

User Response: This message is for your information

ASN7015E pgmname : program_qualifier : The

only. No action is required.

program detected an unrecoverable

WebSphere MQ error for send queue

ASN7010I pgmname : program_qualifier : The

send_queue_name of replication queue

program successfully activated Q

map queue_map_name. The error action

subscription name (send queue

specified for the queue map is

queue_name, replication queue map

error_action.

queue_map_name) for source table

Explanation: An unrecoverable WebSphere MQ error

table_name.

occurred on this send queue. The Q subscriptions that

Explanation: The Q Capture program is replicating

use the queue are deactivated or the Q Capture

changes for the active Q subscription.

program stops. The ERROR_ACTION value determines

how the program behaves due to this error. The value

When the Q Capture program starts, it activates any

for the Q Capture program is stored in the

new Q subscriptions. While the Q Capture program

IBMQREP_SENDQUEUES table.

runs, it performs the following actions:

User Response: Look in the IBMQREP_CAPTRACE

v It activates any new Q subscriptions when it

table to find the error message that precedes this one.

reinitializes.

Take the appropriate action to correct the problem

v It activates any new or inactive Q subscriptions

(follow the instructions in the user response of the

when it receives a capstart signal.

previous message). Activate the Q subscription.

User Response: This message is for your information

If the Q Capture program terminated because of this

only. No action is required.

error, warm start the Q Capture program.

ASN7011E pgmname : program_qualifier : Source table

ASN7016E pgmname : program_qualifier :

table_name of Q subscription name (send

program_name : program_identifier : The

queue queue_name, replication queue

LOADDONE signal failed because the

map queue_map_name) was not found.

Q subscription name has no load phase.

Explanation: The source table specified in the Q

Explanation: The Q subscription does not have a load

subscription does not exist. Most likely the wrong table

phase (HAS_LOADPHASE=N). This error could be due

name was specified when attempting to activate the Q

to an incorrect Q subscription name specified in the

subscription. Otherwise, the source table might have

LOADDONE signal or in the load done received

been dropped intentionally since the Q subscription

message.

was created.

User Response: If the Q subscription has a load phase

User Response: Take one of the following actions:

and you inserted the LOADDONE signal: Make sure

v Ensure that the source table is specified correctly in

that the Q subscription name in the signal is correct

the control tables and that it exists in the database.

and re-insert the LOADDONE signal.

Activate the Q subscription again.

If the Q subscription has a load phase and you sent the

v If you dropped the source table intentionally, delete

load done received message: Make sure that the Q

the Q subscription.

subscription name in the message is correct and resend

the load done received message.

ASN7012I pgmname : program_qualifier : The Q

subscription name was successfully

ASN7017I pgmname : program_qualifier : The target

reinitialized.

table table_name is ready to be loaded

Explanation: The Q Capture program was successfully

from source table table_name for Q

reinitialized and will process transactions according to

subscription name.

the new attributes.

Explanation: See message text.

User Response: This message is for your information

only. No action is required.

ASN7013I pgmname : program_qualifier : The Q

ASN7018E pgmname : program_qualifier : The source

subscription name was deactivated.

table table_name for Q subscription name

Explanation: The Q subscription was deactivated

does not have the DATA CAPTURE

because the CAPSTOP signal was received.

CHANGES attribute set.

User Response: This message is for your information

Explanation: The source table is incorrectly defined.

only. No action is required.

No data will be captured for this Q subscription.

388

Messages and Codes

IBM DPROPR Capture - ASN0000E-ASN0203I

User Response: Alter the source table so that the

IBMQREP_CAPPARMS table.

DATA CAPTURE CHANGES attribute is set and restart

If the restart queue was improperly altered, clear the

the Q subscription. For example:

queue and cold start the Q Capture program.

alter srce_owner.srce_table data capture changes

ASN7025E program_name : program_identifier : The

ASN7019I program_name : program_identifier :

program cannot access the restart queue

signal_name signal was received and will

restart_queue.

be processed.

Explanation: See message text.

User Response: Make sure the restart queue is

User Response: This message is for your information

correctly specified and accessible to application

only. No action is required.

programs (GET enabled).

ASN7020I pgmname : program_qualifier : The

ASN7026E pgmname : program_qualifier : Invalid

program reached the end of the active

signal type signal_type and subtype

log and terminated because the

subtype.

AUTOSTOP option is specified.

Explanation: The signal type or signal subtype is not

Explanation: See message text.

supported.

User Response: This message is for your information

User Response: Check the SIGNAL_TYPE and

only. No action is required.

SIGNAL_SUBTYPE of the row inserted in the

IBMQREP_SIGNAL control table. Ensure that the signal

type or signal subtype is correct and try inserting the

ASN7022W pgmname : program_qualifier : Q

signal again.

subscription name does not exist in the

IBMQREP_SUBS control table. The

signal signal was ignored.

ASN7027E pgmname : program_qualifier : The restart

queue restart_queue is empty.

Explanation: The program cannot find this Q

subscription in the IBMQREP_SUBS control table.

Explanation: The Q Capture program could not warm

start. See message text.

User Response: Ensure that the Q subscription name

is accurate for the signal.

User Response: Cold start the Q Capture program.

ASN7023W pgmname : program_qualifier : Source table

ASN7028E pgmname : program_qualifier : The

table_name does not have a primary key,

MAX_MESSAGE_SIZE specified for

unique constraint, or unique index.

send queue queue_name for replication

queue map queue_map_name in the

Explanation: The source table must have a primary

IBMQREP_SENDQUEUES table is

key, unique constraint, or at least a unique index.

larger than the MAXMSGL queue

Otherwise source data might not be replicated or

attribute value of number bytes defined

published correctly. The related Q subscriptions are still

in WebSphere MQ.

activated.

Explanation: The MAX_MESSAGE_SIZE column value

User Response: Create a primary key, a unique

of this send queue is not valid because it exceeds the

constraint, or a unique index on the source table and

MAXMSGL attribute of the WebSphere MQ queue

reinitialize all related Q subscriptions.

manager. The send queue is invalidated.

User Response: Decrease the MAX_MESSAGE_SIZE

ASN7024E program_name : program_identifier : The

column value for this send queue. If necessary, increase

program cannot process the restart

the MAXMSGL attribute:

message from the restart queue

restart_queue.

v For remote send queues, increase the MAXMSGL

attribute of the transmission queue.

Explanation: The program detected an internal

v For local send queues, increase the MAXMSGL

inconsistency.

attribute.

User Response: Check that the correct version of the

Restart any Q subscription on that send queue.

Q Capture program is running and that the restart

queue was not improperly altered.

To determine the correct version of the Q Capture

program, see the ARCH_LEVEL column in the

Chapter 26. DPROPR Messages

389

IBM DPROPR Capture - ASN0000E-ASN0203I

Explanation: See message text.

ASN7029E pgmname : program_qualifier : The restart

message exceeded the maximum

User Response: Make sure that the format and the

message size of the restart queue

attributes of the control message are correct and put the

restart_queue.

message on the administration queue again.

Explanation: See message text.

ASN7035W pgmname : program_qualifier : The

User Response: Increase the maximum message size

program received a WebSphere MQ

of the restart queue and warm start the Q Capture

exception report message on the

program.

administration queue queue_name that

contains an unsupported message.

ASN7030E pgmname : program_qualifier : The restart

Message type: message_type. Message

queue queue_name is full. The Q Capture

content: message_content.

program will terminate.

Explanation: See message text.

Explanation: The number of messages reached the

User Response: Make sure that your WebSphere MQ

number that is set for the MAXDEPTH attribute on the

configuration is correct.

restart queue.

User Response: If necessary, increase the value for the

ASN7036E pgmname : program_qualifier : The

MAXDEPTH attribute of the restart queue. After you

program cannot process a message from

increase the value, cold start the Q Capture program.

the administration queue queue_name.

Message type: message_type. Message

ASN7033E pgmname : program_qualifier : An invalid

content: message_content.

search condition was detected for Q

Explanation: The program detected an internal

subscription name. Column name:

inconsistency.

column_name. Reason code: reason_code.

User Response: Contact IBM Software Support.

Explanation: The following values are valid for the

Provide the exact message that you received, which

reason code:

identifies the Q Capture schema. Provide the diagnostic

An ordinary identifier for a column name

log file. Also, provide a trace dump (ASNTRC DMP)

must start with a letter followed by letters,

file, if available.

numbers, or underscores.

The column name is not followed by a double

ASN7043W program_name : program_identifier : A

quotation mark.

message_type message was received in the

administration queue for the

Only spaces are allowed between a column

nonexistent or inactive Q subscription

name and a closing square bracket (’]’) .

name. The control message was ignored.

There is a missing closing square bracket (’]’)

Explanation: The request that was received on the

after the column name.

administration queue could not be performed because

The search condition is missing the keyword

the Q subscription does not exist or is inactive.

’WHERE’.

User Response: Ensure that the name of the Q

The search condition contains a column that is

subscription is correct and that it is in the active state.

not in the source table

Put the control message on the administration queue

again.

The search condition does not contain any

source table column names.

ASN7045E pgmname : program_qualifier : The send

User Response: Ensure that the search condition is in

queue queue_name of replication queue

the proper format and restart the Q subscription. Refer

map queue_map_name is not active. The

to the Q replication and transaction publishing product

REINITQ command was ignored.

documentation for the correct way to specify a search

condition.

Explanation: The REINITQ command must be issued

for an active send queue.

ASN7034W pgmname : program_qualifier : The

User Response: Check that the queue name is correct

program cannot process a message from

and reissue the REINITQ command or reinitialize the

the administration queue queue_name.

queue from the Replication Center.

Message type: message_type. Message

content: message_content.

390

Messages and Codes

IBM DPROPR Capture - ASN0000E-ASN0203I

User Response: This message is for your information

ASN7046I pgmname : program_qualifier : Send queue

only. No action is required.

queue_name of replication queue map

queue_map_name was successfully

reinitialized. The following attributes

ASN7062E program_name : program_identifier : Q

were refreshed: ERROR_ACTION is

subscription name was not activated

error_action, HEARTBEAT_INTERVAL is

because Q subscription name is in an

heartbeat_interval, MAX_MESSAGE_SIZE

invalid state state.

is max_message_size.

Explanation: To activate a Q subscription for

Explanation: See message text.

peer-to-peer replication, all the other Q subscriptions in

the same Q subscription group must be in the active or

User Response: This message is for your information

inactive state in the IBMQREP_SUBS table. This error

only. No action is required.

might occur if any Q subscriptions in the same Q

subscription group are in the process of being

ASN7048E pgmname : program_qualifier : The

initialized or deactivated.

program encountered an error during

User Response: Redefine the Q subscription using one

ccsid conversion from source ccsid to

of the replication administration tools, and then

target ccsid. The return code is return

activate the Q subscription.

code.

Explanation: The ccsid conversion from the source

ASN7067E pgmname : program_qualifier : Unable to

ccsid to the target ccsid failed with the following return

process signal signal_name because of

codes:

invalid SIGNAL_INPUT_IN

-1

ccsid conversion is not supported

signal_input_in, expected format:

signal_input_format.

-100

failed while getting the index for the

translation table

Explanation: The program requires a parameter of the

signal to be specified in SIGNAL_INPUT_IN. This error

-150

failed while fetching the ASNWRAP module

will be issued if some of the parameters are missing or

-200

failed while getting the pointer to the

in an unexpected format.

translation table

User Response: Ensure that the SIGNAL_INPUT_IN is

-300

invalid data in source string

specified correctly and re-insert the signal.

User Response: For return code -150, make sure the

ASNWRAP module is on the same disk as the

ASN7073E pgmname : program_qualifier : The

ASNQCAP module. Contact IBM Software Support for

REINIT_SUB command failed because

assistance.

the Q subscription name is not active.

Explanation: The REINIT_SUB command requires that

ASN7051E pgmname : program_qualifier : The Q

an Q subscription is active.

subscription name was deactivated

User Response: Check that the Q subscription was

because no key column is specified in

specified correctly in the command parameters and

the IBMQREP_SRC_COLS table.

reissue the command.

Explanation: At least one column in the source and

target tables must be specified as a key column for the

ASN7074E pgmname : program_qualifier : The

Q subscription. The name of this column is specified in

REINIT_SUB signal is not valid for Q

the IBMQREP_SRC_COLS table.

subscription name. The Q subscription

User Response: Ensure that at least one column in the

was not reinitialized.

source and target tables is specified as a key column for

Explanation: The REINIT_SUB command or the

the Q subscription, then activate the Q subscription.

REINIT_SUB signal applies only to Q subscriptions of

subscription type ’U’ (unidirectional).

ASN7057I pgmname : program_qualifier : The SUB_ID

User Response: For a Q subscription, ensure that you

of Q subscription name in the control

have the correct name and that the SUBTYPE in the

table IBMQREP_SUBS is not unique. A

IBMQREP_SUBS table is ’U’ (unidirectional). Reissue

new SUB_ID is generated.

the command or reinsert the signal.

Explanation: A duplicate SUB_ID was found in the

control table IBMQREP_SUBS for Q subscription name.

The value in this column must be unique.

Chapter 26. DPROPR Messages

391

DB2 Server for VSE Messages and Codes (Version 7 Release 5) - page 10