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

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

System Programmer Response: Enter the option

ARI2064E DBSPACE dbspace-number is unacquired.

desired.

Explanation: The dbspace-number used for release

empty pages processing (STARTUP=P) is found in the

ARI2068E Previously LOGMODE was L, inactive

catalog table SYSTEM.SYSDBSPACES but has not been

log was not archived, and now

acquired.

LOGMODE is A. To start with

System Action: Release empty pages processing ends.

LOGMODE = A, restart with

LOGMODE = L, perform SQLEND with

Operator Response: Correct the DBSPACE number (be

LARCHIVE, and then restart with

sure that the DBSPACE number has been acquired) and

LOGMODE = A.

reenter the command.

Explanation: The database manager was started with

LOGMODE = A, but the previous LOGMODE was L

ARI2065D Do you want to do a database archive

and the inactive log is not archived.

(ARCHIVE), user archive (UARCHIVE),

or no archive (NOARCHIVE) at the end

System Action: The application server is ended.

of the run? (Warning: Database may not

Operator Response: If LOGMODE = L is desired,

be restorable if you choose

restart the database manager with LOGMODE=L. If

NOARCHIVE.) Enter one of the values

LOGMODE = A is desired, restart the database

or enter a null response to use the

manager with LOGMODE = L, perform SQLEND

default (ARCHIVE).

LARCHIVE to archive the inactive and active log and

Explanation: If an archive is not taken after release

then start the database manager with LOGMODE = A.

empty pages processing (STARTUP=P) is run, a

subsequent database restore will not have the empty

ARI2069D You are in the restore process. The

pages released. This can lead to storage pool full

inactive log has not been archived but

conditions when log archives are applied to the system.

LOGMODE = {A|Y|N}. You must either

Choosing NOARCHIVE is not recommended.

end the restore, issue SQLEND

System Action: The system waits for you to enter a

LARCHIVE, and restart the restore with

LOGMODE={A|Y|N} or you can use

LOGMODE=L during the restore.

System Programmer Response: Enter the option

desired.

Enter 0 to end the restore, or

to restore with LOGMODE= L

ARI2066E Invalid response: &1.

Explanation: The database manager was started with

Explanation: You did not provide an acceptable

LOGMODE=A, Y, or N but the previous LOGMODE

response to a question.

was L and the inactive log is not archived.

System Action: The system waits for you to enter an

System Action: If you reply 0, the application server

acceptable response.

is ended. If you reply 1, the database manager will

switch the LOGMODE to L and apply all applicable log

System Programmer Response: Review the question,

archives as if you had started the application server

and provide an acceptable response.

with LOGMODE=L.

Operator Response: If restore with LOGMODE=A, Y,

ARI2067D The inactive log has not been archived.

or N is desired, reply 0 to end the restore, restart the

If log reformatting is required, enter

database manager with LOGMODE=L. Perform

ARCHIVE to archive the inactive log. If

SQLEND LARCHIVE to archive the inactive and active

log reconfiguration is required, enter

log and start the database restore with LOGMODE=A,

END, archive the database, and then run

Y, or N. Reply 1 if you wish to restore with

the COLDLOG again.

LOGMODE=L.

Explanation: The inactive log was not archived before

the coldlog operation. If the coldlog was issued to

reformat the logs, issuing ARCHIVE will archive the

inactive log before the logs are reformatted. If the

coldlog was issued to reconfigure the logs, a database

archive must be taken before the coldlog is run.

System Action: The system waits for you to enter a

reply.

Messages and Codes

Chapter 4. ARI2900-ARI2942 Common Messages

v The phase corresponding to American English

ARI2900E Language &1. cannot be accessed.

(LANGID: AMENG, LANKEY: S001) repository

Reason Code = nn.

could not be CICS LOADed.

Explanation: Either the national language name has

been misspelled, or the language specified on the SET

The failure was due to one of the following reasons:

LANGUAGE command cannot be accessed because of

v Message phase not found

one of the following reasons:

v Language not installed

Message file not found.

This message is always issued in English.

Storage problem.

System Action: Subcomponent initialization is

Language cannot be installed because:

cancelled.

v Language ID is not in table

User Response: Notify your system programmer.

SYSLANGUAGE.

v Language ID is in SYSLANGUAGE but was

System Programmer Response: Ensure that the phase

inserted into SYSLANGUAGE during a DB2

corresponding to the LANGID parameter is available,

Server for VSE session.

or the phase corresponding to the default language is

available, or the phase corresponding to AMENG is

&1. is the language identifier.

available (Phase name: ARIMS001). Refer to the DB2

Server for VSE Program Directory and DB2 Server for VSE

System Action: An attempt to set language &1. failed,

System Administration manual for more information on

because the language specified could not be found.

installing a language on your system.

User Response: Make sure that the language identifier

is correct and the requested language is supported on

ARI2903E Error loading Resource Adapter.

your system.

SQLCODE = &1A

An INSERT may have been made into table

Explanation: Resource adapter could not be loaded.

SYSLANGUAGE during a DB2 Server for VSE session.

This message is always issued in English.

You must bring the DB2 Server for VSE machine down

and bring it up again in order for the inserted language

System Action: Subcomponent initialization is

IDs in SYSLANGUAGE to be recognized.

cancelled.

User Response: Notify your System Programmer.

ARI2901I

Warning: The database manager cannot

Programmer response: Correct the problem indicated

access the default language &1.. English

by the SQLCODE value. For more information, see

will be used instead. Reason Code = nn.

Chapter 18, “SQLCODEs,” on page 237.

Explanation: The message file for the language

currently set in VM could not be loaded and the

ARI2904I

Warning: DBCS language &1. is not

attempt to set the DB2 Server for VSE default language

supported on the VSE operator console.

also failed. The English message repository is used

The database manager uses English or

instead. Reason codes have the following meaning:

the previous language.

Message file not found

Explanation: The operator console cannot use a

Storage problem

double-byte character set (DBCS). &1. is the language

identifier.

Language not installed.

User Response: Check that the correct language is

specified and that the requested language is supported

ARI2902E There is no message file that the

on your system. For more information on "National

database manager can access.

Languages" see either the DB2 Server for VSE System

Explanation: This message appears when all of the

Administration manual or the DB2 Server for VSE & VM

following conditions have been met:

Operation manual.

v The repository phase corresponding to the LANGID

parameter could not be CICS LOADed.

ARI2905E The command command is not supported

v The repository phase corresponding to the default

when using the DRDA protocol.

language defined as the first entry in the link-edited

LANGBLK table, could not be CICS LOADed.

Common Messages - ARI2900-ARI2942

Explanation: You are accessing a remote application

ARI2909I

Warning: An error in the conversation

server and have attempted to use the specified

has been detected. Please wait for the

command against this application server. The command

data capture completion message to

is available only against a local application server.

appear before taking further action.

System Action: Command processing failed.

DUMPID = &1.

User Response: Enter another command.

Explanation: An error has been detected in either the

communication partner’s datastream or internally in

DB2 Server for VSE distributed flow processing.

ARI2906I

The only valid isolation level is CS

when the DRDA protocol is used.

System Action: System information is dumped to

Isolation level of CS is now in effect.

SYSLST. The dump identifier may be used to correlate

this message to the SYSLST dump file.

Explanation: If the DRDA protocol is used, the

isolation level defaults to cursor stability (CS). The SET

User Response: Wait until completion message

ISOLATION command cannot be used to change the

ARI2910I is displayed, and then notify your system

isolation level.

programmer.

System Action: The SET ISOLATION command is

CAUTION:

ignored.

User Response: You may continue with another

Do not erase any SYSLST files that may exist.

command.

System Programmer Response: This message

indicates that an error has occurred during distributed

ARI2908I

XPCCB, IJBXRUSR = aabbccccddeeeeee

flow processing, and diagnostic error information has

been dumped to SYSLST. Save the SYSLST file

Explanation: For VSE Guest-Sharing users, this

containing the dump identified by the dump identifier

message displays secondary return codes captured in

in the message and contact the designated support

the IJBXRUSR field within the XPCCB control block.

group for your installation.

These return codes can be used to diagnose XPCC

communication problems while communicating with

APPC/VM in a Guest-Sharing environment. Refer to

ARI2910I

Data capture process completed

the VM/ESA: Connectivity Planning, Administration, and

successfully. Please notify your system

Operation manual for an explanation of the APPC/VM

programmer.

return codes.

[Job Name = jobname

aabbccccddeeeeee is a 16-byte hexadecimal string with the

Job Number = jobnumber]

following formats:

Explanation: The data capture process referred to in

Format 1

When SQLERRD2 = 38, only the first

message ARI2909I is completed.

4 bytes are significant, where:

aa = APPC/VM Function Code

bb = APPC/VM Return Code.

ARI2911E An internal error has occurred in the

data capture process. Notify your system

Format 2

For all other cases:

programmer. [DUMPID =dumpid.]

aa = APPC/VM Function Code

[IPWSEGM =code.]

The next 14 bytes are APPC/VM

error data, external interrupt

Explanation: An error has occurred during the data

information:

capture process. This indicates a serious system

bb = ’IPTYPE’

problem.

cccc = ’IPCODE’

System Action: Process of data capture is interrupted.

dd = ’IPWHATRC’

A SYSLST file containing partial data may or may not

eeeeee = ’IPAUDIT’

exist.

System Programmer Response: Ensure that the VSE

User Response: Notify your system programmer. Do

Guest system is properly installed for Guest-Sharing.

NOT erase any SYSLST files that may exist.

Refer to IBM VSE/ESA Installation, or for a brief

description, refer to the DB2 Server for VSE Program

System Programmer Response: This message

Directory.

indicated that a DB2 Server for VSE internal error has

occurred during data capture. There may or may not be

a SYSLST file containing a partial dump identified by

the dump identifier in the message. Save this file if it

exists. Contact the designated support group for your

installation.

Messages and Codes

Common Messages - ARI2900-ARI2942

SYSCHARSETS table, add the row to the table and then

ARI2912E Error reading NETID from SNA NETID

recreate the ARISSCRD phase. Refer to the DB2 Server

file.

for VSE Program Directory.

Explanation: You have specified PROTOCOL=AUTO

If this message is issued other than by ISQL, DBSU, or

which requires a NETID value. An error occurred when

the Preprocessors, and the row is missing from the

the SQLSTART EXEC tried to retrieve the NETID value

system catalog table, insert a row with the correct

from the SNA NETID file on the production disk.

values into the table. If the catalog table that needs

System Action: Database startup is terminated

updating is SYSTEM.SYSCHARSETS, refer to the DB2

because the NETID is a required parameter for DRDA

Server for VSE System Administration manual for

protocol.

information on updating this catalog table.

User Response: Check the existence of the SNA

NETID file on the production disk. If it is not found or

ARI2914E An error occurred with the MACRO

corrupted, then recreate the file with the correct NETID

name while accessing the file file. Return

value and rerun the EXEC.

code = rc.

Explanation: An error occurred with the MACRO

ARI2913I

Character translation table for

while accessing the file file that is required for character

CHARNAME = charname cannot be

translation support or for CCSID support. file may have

found. The character translation table

one of the following values: ARISCCSD PHASE,

for INTERNATIONAL will be used.

ARISSTRD PHASE or ARISSCRD PHASE. The return

code value is the MACRO return code.

Explanation: If this message is displayed by ISQL,

DBSU, or the Preprocessors: the row with the

System Action: Processing terminates.

CHARNAME value cannot be found in the ARISSCRD

User Response: Contact your system programmer.

phase, or the phase cannot be accessed, or the phase

does not exist or is empty. If the CHARNAME value is

System Programmer Response: Refer to the VSE/ESA

’unknown’, an error has occurred while retrieving the

System Macros Reference for an explanation of the return

GLOBAL variable CHARNAME from the SQLGLOB

code and correct the problem. If the problem cannot be

file.

corrected, contact the designated support group for

your installation.

If this message is not displayed by ISQL, DBSU, or the

Preprocessors: if the CHARNAME value is ’unknown’,

the row where SQLOPTION=CHARNAME cannot be

ARI2920E Application Identifier resolution error.

found in the SYSTEM.SYSOPTIONS catalog table.

Detection point = &1.. Return Code =

Otherwise, the row where NAME=charname cannot be

&2A..

found in the SYSTEM.SYSCHARSETS catalog table.

Explanation: An error was detected when trying to

System Action: Processing continues. The character

resolve the Application Identifier of the application

translation table for INTERNATIONAL will be used.

server. The error is related to a specific operation or

entity of the DBNAME Directory service.

User Response: If the CHARNAME value is

’unknown’, and this message is issued by ISQL, DBSU,

&1. is the function or entity in which the error was

or the Preprocessors, use the DSQU transaction to

found.

create a new user record with the desired SQLGLOB

&2A. is the error code returned from the DBNAME

values. If the SQLGLOB file is not found, or cannot be

Directory Service or set by the service caller.

accessed, notify your system programmer.

This message is displayed by the caller of the

Contact your system programmer if the specified

DBNAME Directory Service. For more information, see

CHARNAME cannot be found in the ARISSCRD phase,

the DB2 Server for VSE Messages and Codes manual.

or the phase does not exist, or the phase cannot be

accessed, or if this message is not issued by ISQL,

Detection

Return

DBSU, or the Preprocessors.

Point

Code

System Programmer Response: If the SQLGLOB file is

(&1.)

(&2A.)

Explanation

not found, or cannot be accessed, recreate the

LOAD

CDLOAD CDLOAD of DBNAME Directory

SQLGLOB file using the IBM-supplied ARISGDEF job

Service failed. Refer to VSE

control program.

CDLOAD return codes for

corrective actions.

Check that the row corresponding to the CHARNAME

SEARCH 4

The search with DBNAME or

value exists in the ARISSCRD phase, or in the system

TPN does not have a match.

catalog table SYSTEM.SYSCHARSETS. If the row is in

SYSTEM.SYSCHARSETS but does not exist in the

phase, or the phase does not exist or is empty, recreate

the ARISSCRD phase. If the row does not exist in the

Chapter 4. ARI2900-ARI2942 Common Messages

Common Messages - ARI2900-ARI2942

Detection

Return

ARI2922I

Using the following parameter values:

Point

Code

parameter(value)

(&1.)

(&2A.)

Explanation

Explanation: This message appears in the listing file

The parameter list was incorrectly

of the SQLDBDEF utility. It shows the value of each

set up. Report this error to the

parameter, including parameters that were not specified

designated support group for

when the utility was invoked.

your installation.

The DBNAME Directory is

System Action: Processing continues.

invalid. The DBNAME Directory

could have been corrupted.

ARI2923I

FORMAT 1

v Make sure that ARISDIRD.A is

Running ARIDBDEF to generate:

correctly set up and catalog ed.

FORMAT 2

v Regenerate the DBNAME

- GRANT statements for user authorities

Directory using the ARISBDID

FORMAT 3

JCL supplied. If the error

- CREATE statements for stored

persists, report the error to the

procedures

designated support group for

FORMAT 4

your installation.

- CREATE statements for stored

APPLID

The APPLID in the DBNAME

procedures and stored procedure servers

Directory is invalid for a DB2

FORMAT 5

Server for VSE server. The

- SQL statements to re-create all objects

database manager startup failed.

FORMAT 6

v Valid APPLIDs for DB2 Server

- SQL statements to re-create all objtypes

for VSE servers are: SYSARI0x

FORMAT 7

where x = 0..9 and A..Z.

- SQL statements to re-create all objects

v Make sure that ARISDIRD.A is

in dbspace dbspace

correctly set up and cataloged.

FORMAT 8

v Regenerate the DBNAME

- SQL statements to re-create all tables

Directory using the ARISBDID

and table and column privileges

JCL supplied. If the error

persists, report it to the

Explanation: This message appears in the output

designated support group for

listing created by the SQLDBDEF utility. It indicates

your installation.

what type of statements were generated by that

invocation of the utility.

System Action:

If this message is issued from the

System Action: Processing continues.

database manager, the initialization of the database

manager ends. Otherwise, the issuer of this message

ARI2924I

Processing object-type.

terminates itself.

Explanation: This message is displayed by the

Operator Response: Record the error detection point,

SQLDBDEF utility, as an indication of the progress of

the return code, and the issuing partition for problem

the utility.

determination.

System Action: Processing continues.

System Programmer Response: Refer to the specific

error explanation above for corrective actions.

ARI2925I

There are no objects defined.

ARI2921I

The SQLDBDEF utility was invoked as

Explanation: The SQLDBDEF utility is attempting to

follows: Command and parameters used to

extract SQL definitions for all objects of a specified

invoke SQLDBDEF utility

type. The type is specified as objects, but there are no

objects of that type defined in the database.

Explanation: This message appears in the listing file

of the SQLDBDEF utility. It shows the command and

System Action: Processing ends.

parameters that were used to invoke the utility.

System Action: Processing continues.

ARI2926E Unable to connect to database dbname.

Explanation: The SQLDBDEF utility is attempting to

extract SQL object definitions from database dbname,

but is unable to connect to the database. This message

is followed by messages containing the SQLCODE and

other diagnostic information.

Messages and Codes

Common Messages - ARI2900-ARI2942

The database to which the SQLDBDEF utility is

ARI2931W Column colname uses field procedure

attempting to connect is the one specified for the DB

fpname in the source table.

parameter on the invocation of the utility. If the DB

parameter was not specified, the utility attempts to use

Explanation: This message is produced by the

the default database, which is the one listed as the

SQLDBDEF utility when generating a CREATE TABLE

default in the DBname directory.

statement. It appears if a field procedure is defined on

a column in the source table, when the target database

System Action: Processing ends.

on which the DBSU job will be run does not support

field procedures.

ARI2927E User userid does not have DBA

System Action: Processing continues.

authority.

Explanation: The SQLDBDEF utility must be run from

ARI2932I

Column colname uses CCSID CCSID and

an ID that has DBA authority in the database from

subtype subtype in the source table.

which the SQL definitions will be extracted.

Explanation: This message is written to the

System Action: Processing ends.

SQLDBDEF utility listing, when the utility is generating

User Response: Run the utility again, specifying a

a CREATE TABLE statement.

user ID that has DBA authority.

System Action: Processing continues.

ARI2928I

All ARIDBDEF processing completed

ARI2933I

SYSOPTIONS option option has value

successfully.

value in the source table.

Explanation: This message appears in the output

Explanation: This message is written to the

listing created by the SQLDBDEF utility.

SQLDBDEF utility listing.

System Action: Control returns to the SQLDBDEF

System Action: Processing continues.

EXEC.

ARI2934W Primary key keyname is defined with

ARI2929I

Errors occurred during ARIDBDEF

PCTFREE= pctfree in the source table.

processing.

Explanation: This message is written to the

Explanation: This message appears in the output

SQLDBDEF utility listing, if a primary key defined in

listing created by the SQLDBDEF utility. It is

the source table uses a value other than the default for

accompanied by messages that provide information

PCTFREE.

about the error that occurred.

System Action: Processing continues.

System Action: Control returns to the SQLDBDEF

EXEC.

ARI2935W Column colname is in descending order

in primary key keyname in the source

ARI2930W SQL that was used on the source

table.

database is not valid on the target

database.

Explanation: This message is written to the

SQLDBDEF utility listing, if a column in a primary key

Explanation: This message is generated by the

is specified to be in descending order.

SQLDBDEF utility. It indicates that when the object

being processed was created on the source DB2 Server

System Action: Processing continues.

for VM & VSE database, options were specified that are

not applicable on the platform on which the generated

ARI2936W The DBSU job does not contain SQL to

DBSU job is to run.

create key keyname because it is inactive

System Action: Processing continues.

in the source table.

User Response: The listing and/or the DBSU job

Explanation: This message is written to the

contain further information about the object and the

SQLDBDEF utility listing, if a key in the source

option that is not valid on the target database. Review

database has been deactivated.

these files to determine whether further action is

System Action: Processing continues. If you want the

necessary.

generated DBSU job to recreate the key keyname, use

the ALTER TABLE command to reactivate the key in

the source table, and run the SQLDBDEF utility again.

Chapter 4. ARI2900-ARI2942 Common Messages

Common Messages - ARI2900-ARI2942

ARI2937W Acquire dbspace has no equivalent on

ARI2941I

Index indexname is the clustering index

OS/400. However a schema must exist

in the source database.

before objects can be created in that

Explanation: In the DBSU job generated by the

schema. For example, schema A must

SQLDBDEF utility, CREATE INDEX statements will not

exist before table A.tabname can be

necessarily appear in the order in which they were

created. Review the generated DBSU job

issued on the source database. This message is

and ensure that you have created any

generated so that the DBSU job can be modified to

necessary schemas on the target

maintain the clustering index if necessary.

database prior to running the DBSU job.

System Action: Processing continues.

Explanation: This message is generated by the

SQLDBDEF utility, to indicate action that must be taken

User Response: If you want indexname to be a

before tables can be recreated on a target DB2 database

clustering index in the target database, ensure that the

on OS/400.

generated DBSU job creates index indexname before it

creates any other indexes on the same table.

System Action: Processing continues.

User Response: Before running the generated DBSU

ARI2942W Warnings occurred during ARIDBDEF

job against the target database, create any schemas that

processing.

will be required for the CREATE TABLE statements in

the DBSU.

Explanation: This message appears in the output

listing created by the SQLDBDEF utility.

ARI2938I

Grants of user authorities are not

System Action: Control returns to the SQLDBDEF

performed on OS/400.

EXEC.

Explanation: This message is generated by the

User Response: Review the warning messages in the

SQLDBDEF utility. It indicates that the generated DBSU

output listing, and take appropriate action.

job does not contain GRANT statements for user

authorities, since these are not relevant on the target

database.

System Action: Processing continues.

ARI2939I

User userid has auth authority in the

source database.

Explanation: This message is generated by the

SQLDBDEF utility, if userid has a level of authority that

is not supported on the target database.

System Action: Processing continues.

User Response: Determine whether userid needs to be

authorized to the target database, and if so, issue the

appropriate GRANT command or take the appropriate

system action.

ARI2940I

User userid has SCHEDULE authority in

the source database, and is granted

CONNECT authority by the DBSU job.

Explanation: SCHEDULE authority is relevant only on

a VSE or VM database. The SQLDBDEF utility grants

CONNECT authority to any users who have

SCHEDULE authority in the source database.

System Action: Processing continues.

User Response: If userid does not need CONNECT

authority on the target database, remove the GRANT

statement from the generated DBSU job.

Messages and Codes

Chapter 5. ARI0400-ARI0498 Resource Adapter Messages

Resource Adapter was already initialized and active or

ARI0400E Invalid input parameter entered.

is being initialized within the partition. Only one

Parameter = parm

Resource Adapter may be active within a CICS/VSE

Explanation: The DB2 Server for VSE Resource

partition.

Adapter Begin transaction (CIRB) or the Termination

Operator Response: In general, do nothing. If CIRB

transaction (CIRT) or the Resource Adapter Add

was entered to modify the initialization parameter (for

Connections Transaction (CIRA) or the Resource

example, increase the number of paths to the database

Adapter Remove Connections Transaction (CIRR) or the

manager), first enter the DB2 Server for VSE Resource

Resource Adapter Display Transaction (CIRD) or the

Adapter Termination transaction (CIRT) to terminate

Resource Adapter Change Default Server Transaction

the active resource adapter. After CIRT disables the

(CIRC) detected an incorrect input parameter.

resource adapter (message ARI0413I is displayed),

parm is the parameter which was not valid. For CIRB,

reenter CIRB with the new input parameters.

parm may be PASSWORD, NOLINKS, DEFUID, RMID,

If CIRB was entered to add connections to another

LANGID, or DBNAME. For CIRT, parm may be

application server, use the CIRA transaction to do this.

PASSWORD, MODE, or INTERVAL. For CIRA, parm

may be PASSWORD, NOLINKS, DEFUID, OR

DBNAME. For CIRR, parm may be PASSWORD,

ARI0402E CICS/VSE load of &1. failed.

MODE, INTERVAL, OR DBNAME. For CIRC, parm

Explanation: The DB2 Server for VSE Resource

may be DBNAME.

Adapter Begin transaction (CIRB) attempted to load

PASSWORD and DEFUID must be character strings

one of the phase/load modules ARI0OLRM or

from 1 to 8 characters with no imbedded blanks. The

ARICMOD. In this message &1. will be either

character string for PASSWORD which is input to CIRT

ARI0OLRM or ARICMOD. CICS/VSE was not able to

or CIRR must match the password of at least one

locate either ARI0OLRM or ARICMOD.

server enabled by CIRB or CIRA. PASSWORD must be

System Action: The CIRB transaction ends.

preceded by one or more blanks.

Operator Response: Refer this message to your

NOLINKS must be a decimal value between 0 and 64.

system programmer.

RMID must be a decimal value between 0 and 63.

System Programmer Response: Verify that the

MODE must be either the character string NORMAL or

program named ARI0OLRM or ARICMOD is correctly

the character string QUICK.

defined to CICS/VSE and is in an accessible library

phase member. See the DB2 Server for VSE Program

INTERVAL must be a decimal value between 0 and

Directory.

3 600.

LANGID must be one of AMENG, UCENG, FRANC,

ARI0403E Error attempting to use CICS/VSE

GER, KANJI, or HANZI.

service. CICS/VSE service = service.

DBNAME must be 1 to 18 characters.

EIBRCODE = return-code. [TS queue

name = queue-name.] [Target database =

The delimiter between parameters is a comma or one

db-name.]

or more blanks.

Explanation: The DB2 Server for VSE Resource

System Action: The transaction ends.

Adapter Begin transaction (CIRB) or the Resource

Operator Response: Reissue the transaction with the

Adapter Terminate transaction (CIRT) or the Resource

correct input parameters. Refer to the DB2 Server for

Adapter Add Connections transaction (CIRA) or the

VSE & VM Operation manual for more information

Resource Adapter Remove Connections transaction

about the input parameters.

(CIRR) or the Resource Adapter Display transaction

(CIRD) or the Resource Adapter Change Default Server

transaction (CIRC) or the DB2 Server for VSE Bind

ARI0401I

DB2 Server for VSE Online Resource

transaction (CBND) or the DSQx transaction (DSQG,

Adapter is already present in this

DSQU, DSQQ, DSQD) encountered the error while

partition.

using the EXEC CICS interface.

Explanation: The DB2 Server for VSE Resource

service defines the service/command which was

Adapter Begin transaction (CIRB) was entered to

executed. Use the CICS/VSE manuals listed in the

initialize the DB2 Server for VSE Online Resource

System Programmer Response to map the value for

Adapter. The CIRB transaction detected that the

Resource Adapter Messages - ARI0400-ARI0498

service to the CICS/VSE EIBFN code. The EIBFN code

ARI0405E RMID input parameter is not unique.

may be used as an aid in interpreting the value for

return-code.

Explanation: The DB2 Server for VSE Resource

Adapter Begin transaction (CIRB) attempted to log on

return-code is the CICS/VSE return code (EIBRCODE).

to the system communication facility with the name

queue-name is the CICS/VSE temporary storage queue

ARIxOLRM, where x was the RMID input parameter.

that the CICS/VSE service was trying to work with for

The communications facility returned a code indicating

the CBND, DSQQ, DSQG, DSQU, and DSQD

that ARIxOLRM was not unique in the system. This

transactions.

condition will occur for an installation which executes

multiple CICS/VSE partitions, each with access to the

db-name is the name of the target database server for

database manager, and does not specify a unique RMID

the CBND process.

input parameter to CIRB.

System Action: The transaction continues if the

System Action: The CIRB transaction ends.

CICS/VSE service is DELAY, RELEASE or DISABLE.

Otherwise, the transaction ends.

Operator Response: Reenter the CIRB transaction with

a unique RMID.

User Response: If the CICS/VSE service is

’READQTS’, the EIBRCODE is X’020000000000’ and the

TS queue name is ’NLSLKEY’, run CIRB before

ARI0406E Error in using system communications

reissuing the failing transaction.

facility. Request = request. Return Code

= return-code. Reason Code =

Operator Response: Refer this message to your

reason-code..

system programmer.

Explanation: The DB2 Server for VSE Resource

System Programmer Response: Correct the CICS/VSE

Adapter Begin Transaction (CIRB) or the Resource

problem and reissue the failing transaction. See the

Adapter Terminate Transaction (CIRT) or the Resource

CICS/VSE Application Programming Reference manual for

Adapter Add Connections Transaction (CIRA) or the

a description of the EIBRCODE. If the CICS/VSE

Resource Adapter Remove Connections Transaction

service was EXTRACT, ENABLE, or DISABLE, refer to

(CIRR) encountered an error condition while using the

the CICS/VSE System Programming Reference manual.

system communication facility. Additionally, the online

support may encounter this error.

ARI0404E Unable to allocate storage in the

request identifies the VSE XPCC request code.

CICS/VSE partition. Requested size =

size.

return-code identifies the DB2 Server for VSE return

code.

Explanation: The DB2 Server for VSE Resource

Adapter Begin transaction (CIRB) or the Resource

reason-code identifies the reason code from the system

Adapter Add Connections Transaction (CIRA) or the

communication facilities of the operating system.

Resource Adapter Remove Connections Transaction

See Chapter 20, “DB2 Server for VSE Reason Codes,”

(CIRR) or the Resource Adapter Termination

on page 355 for a description of the codes provided

Transaction (CIRT) was not able to obtain the storage

with this message.

required for execution.

System Action: The CIRB or CIRA transaction ends.

size defines the number of bytes which were required.

The CIRT or CIRR transaction attempts to continue the

System Action: The transaction ends.

shutdown process and then ends. If the DB2 Server for

VSE online support encountered the communications

Operator Response: Either reissue the CIRB or CIRA

error, it internally activates CIRR for termination in

transaction after providing CICS/VSE with a larger

QUICK mode. CIRR generates the error message.

partition or reissue the CIRB or CIRA transaction with

a smaller value for the NOLINKS input parameter or

Operator Response: Refer this message to your

fewer server names. For CIRR or CIRT, reissue the

system programmer.

transaction when fewer transactions are running.

System Programmer Response: Correct the

communication error.

Note: For details on the storage requirements, refer to

the DB2 Server for VSE System Administration

Note: If the communication error was because of a

manual.

problem in the database manager partition and a

dump was written to SYSLST or SYSLOG, the

dump contains information necessary for

correcting the problem.

Messages and Codes

Resource Adapter Messages - ARI0400-ARI0498

ARI0407E Error in attempting to execute SQL.

ARI0411I

Resource Adapter is not enabled.

SQLCODE = sqlcode. SQLERRD1 =

Explanation: The DB2 Server for VSE Resource

errd1. SQLERRD2 = errd2.

Adapter Termination transaction (CIRT) or the Resource

Explanation: The DB2 Server for VSE Resource

Adapter Display Transaction (CIRD) or the Resource

Adapter Begin Transaction (CIRB) or the Resource

Adapter Add Connections Transaction (CIRA) or the

Adapter Add Connections Transaction (CIRA)

Resource Adapter Remove Connections Transaction

encountered an error attempting to execute SQL.

(CIRR) was entered. It was determined that the

Resource Adapter was not initialized. Either the

sqlcode, errd1, and errd2 is the return code information.

Resource Adapter was not initialized or a previous

Refer to Chapter 18, “SQLCODEs,” on page 237 for an

execution of CIRT or CIRR terminated the Resource

explanation of the error.

Adapter.

System Action: The CIRB or CIRA transaction

System Action: The CIRT or CIRD or CIRA or CIRR

bypasses the server that had the error and continues

transaction ends.

processing the next server in the server name list.

Operator Response: Refer this message to your

ARI0412I

Resource Adapter ARI0OLRM is

system programmer.

disabling.

System Programmer Response: Correct the SQL error

Explanation: The DB2 Server for VSE Resource

and reissue the CIRB or CIRA transaction.

Adapter Remove Connections Transaction (CIRR)

determined that the termination process was already

Note: If the SQLCODE is -560 or -561, the CICS/VSE

active because of a previous invocation of CIRT or

APPLID, which defaults to DBDCCICS, does not

CIRR.

have the proper authorization. See the DB2

Server for VSE Program Directory.

System Action: The CIRR transaction ends. The

termination process continues to execute under the

original invocation of CIRT or CIRR.

ARI0408E Insufficient number of links specified.

NOLINKS = links SERVER = server-name.

ARI0413I

Resource Adapter ARI0OLRM is

Explanation: The DB2 Server for VSE Resource

disabled.

Adapter Begin transaction (CIRB) or the Resource

Adapter Add Connections Transaction (CIRA) was

Explanation: The DB2 Server for VSE Resource

executed with a NOLINKS input parameter that was

Adapter Termination transaction (CIRT) or the Resource

too small.

Adapter Remove Connections Transaction (CIRR)

successfully completed the termination process.

links specifies the minimum number of links required

for recovery.

System Action: The CIRT or CIRR transaction ends.

server-name specifies the server that was being accessed.

Operator Response: Do nothing unless it is necessary

to initialize online access to the database manager. In

System Action: The CIRB transaction or CIRA

that case, enter the CIRB transaction.

transaction bypasses the server that had the error and

continues processing the next server in the server name

list.

ARI0414A Retry the disable transaction tran.

Application transactions are accessing

Operator Response: Reexecute the CIRB or CIRA

the Resource Adapter. [SERVER =

transaction with NOLINKS greater than or equal to

server-name.]

links.

Explanation: The DB2 Server for VSE Resource

Adapter Termination transaction (CIRT) or the DB2

ARI0410I

Resource Adapter ARI0OLRM is

Server for VSE Resource Adapter Remove Connections

enabled.

transaction (CIRR) was not able to continue because

Explanation: The DB2 Server for VSE Resource

applications were accessing the database manager or

Adapter Begin transaction (CIRB) successfully

because the applications which previously accessed the

completed the initialization process. Online access is

database manager were still active. This causes the

now allowed to the database manager.

resource adapter to delay for a time interval

(INTERVAL input parameter to CIRT or CIRR) as had

System Action: The CIRB transaction ends.

been indicated by either message ARI0425I, ARI0465I,

ARI0426I, or ARI0469I. The delay interval has

Operator Response: Do nothing unless it is necessary

completed and the conditions indicated by ARI0425I,

to terminate online access to the database manager.

ARI0465I, ARI0426I, or ARI0469I still exist.

When termination is necessary, enter the CIRT

transaction.

tran is the transaction identifier CIRT or CIRR.

Chapter 5. ARI0400-ARI0498 Resource Adapter Messages

Resource Adapter Messages - ARI0400-ARI0498

server-name is the server that is still being accessed or

Note: If this message occurs frequently, it indicates a

transactions which accessed it before are still active.

high degree of contention for the cross-partition

links established for the partition. This

System Action: The CIRT or CIRR transaction

contention could be reduced by increasing the

terminates thus freeing the terminal for system

number of available links when the database

programmer action. Other servers in the list which did

manager is restarted.

not display this message are disabled.

Operator Response: After all transactions which are

ARI0418A Application server server-name is not

or were accessing the database manager have

ready. Retry the enable transaction tran

terminated, the CIRT or CIRR transaction should be

after the application server starts.

reentered. You may do one of the following:

Explanation: The DB2 Server for VSE Resource

v Wait for the active transactions to terminate

Adapter Begin transaction (CIRB) or the Resource

normally.

Adapter Add Connections Transaction (CIRA) is not

v Use CSMT to terminate the active transactions.

able to access the server server-name. Either the

v If the retry of CIRT or CIRR was requested because

database manager has not been started or it has not yet

one or more logical units of work are still active (as

completed its initialization process.

was indicated by message ARI0425I), immediately

tran is the transaction identifier CIRB or CIRA.

reissue CIRT or CIRR with the input parameter

QUICK.

System Action: The CIRB or CIRA transaction

v If the retry of CIRT or CIRR was requested because

bypasses the server that had the error and continues

one or more APPC conversations are still active (as

processing the next server in the server name list.

was indicated by message ARI0469I), terminate the

Operator Response: Reenter the CIRB transaction or

APPC conversation before reissuing CIRT or CIRR.

CIRA for the servers that were not started after the

database manager has completed its initialization. If the

ARI0415D Database server &1. is not ready. Enter

CIRB transaction was used and it established

&2. or CANCEL.

connections to at least one server then the CIRA

transaction must be used to establish the connections to

Explanation: The database manager was not started in

the servers that failed.

multiple user mode before the application issued an

SQL request. &2. is either WAIT or RETRY.

ARI0419A The database manager does not have

Operator Response: If a DB2 Server for VSE partition

enough cross-partition links. The enable

is to be accessed, reply with either WAIT or CANCEL.

transaction tran requires num-links more

A reply of WAIT implies that you will be starting a

links to server server-name.

DB2 Server for VSE partition and that the resource

adapter should wait until the database manager is

Explanation: The NOLINKS input parameter to the

ready. Reply with CANCEL if a DB2 Server for VSE

DB2 Server for VSE Resource Adapter Begin transaction

partition cannot be started.

(CIRB) or the Resource Adapter Add Connections

transaction (CIRA) is too large. The database manager,

For Guest Sharing, reply with RETRY after the database

server-name, either was not started with enough links or

server has been started. If RETRY is entered and the

the links are now allocated to other applications or

server is not ready, this message is displayed again.

subsystems.

Reply with CANCEL if the database server cannot be

started.

tran is the transaction identifier CIRB or CIRA.

num-links indicates additional number of links required.

ARI0416E Invalid input. Enter WAIT or CANCEL.

server-name indicates the server that had the insufficient

Explanation: You replied to message ARI0415D with

number of links.

other than WAIT or CANCEL. A maximum of five

System Action: The CIRB or CIRA transaction

attempts to reply WAIT or CANCEL will be allowed.

bypasses the server that had the error and continues

After five attempts the system will cancel the request.

processing the next server in the server name list.

Operator Response: Reply with either WAIT or

Operator Response: Either reenter CIRB or CIRA

CANCEL.

when more links become available, or reenter CIRB or

CIRA with a smaller NOLINKS input parameter for the

ARI0417I

Application is waiting for cross-partition

server that had the error.

link.

Explanation: The DB2 Server for VSE Batch Resource

Adapter tried to connect to a cross-partition

communications link but a link was not available.

Messages and Codes

Resource Adapter Messages - ARI0400-ARI0498

support remains active and only the server with the

ARI0420E Operating System storage management

error is disabled.

failure. Operating System Return Code

= return-code

Operator Response: Correct the storage error.

Re-establish connections to the server with the CIRB

Explanation: The DB2 Server for VSE Resource

transaction if the online support was disabled or with

Adapter Begin transaction (CIRB) or the Resource

the CIRA transaction if the online support is still active.

Adapter Add Connections transaction (CIRA) or the

Resource Adapter Remove Connections transaction

(CIRR) or the Resource Adapter Termination

ARI0423A Use the SHOW and FORCE commands

transaction (CIRT) encountered a storage error.

to COMMIT or ROLLBACK the

following units of work:

return-code is the return code from the operating

system.

ARI0424I

User ID = userid Agent Identifier = agent

System Action: If the storage request was to GET

Server = server-name.

storage, the transaction ends. If the storage request was

to FREE storage, the transaction continues.

Explanation: This message can be displayed in the

CICS partition or in the database manager partition.

Operator Response: Correct the storage management

error and reissue the transaction. The VSE/ESA System

CICS Partition

Services return codes are in the IBM VSE/ESA System

After a system or subsystem failure, the Resource

Macros Reference manual under the discussion of the

Adapter Begin transaction (CIRB) or the Resource

GETVIS/FREEVIS macro instructions.

Adapter Add Connections transaction (CIRA) detected

that the indicated logical units of work must be

ARI0421I

DISABLE escalated from NORMAL to

committed or rolled back.

QUICK for server server-name.

Database Manager Partition

Explanation: The DB2 Server for VSE Resource

After a system or subsystem failure, the database

Adapter Termination transaction (CIRT) or the Resource

manager detected logical units of work that must be

Adapter Remove Connections transaction (CIRR) was

committed or rolled back. These units of work cannot

entered with the input parameter QUICK. A previous

be resolved automatically by the Resource Adapter

activation of CIRT or CIRR was with the NORMAL

Begin transaction (CIRB) or the Resource Adapter Add

option.

Connections transaction (CIRA).

System Action: The termination process continues in

userid is the established DB2 Server for VSE user ID for

QUICK mode.

the logical unit of work.

agent is the agent identifier which should be used with

ARI0422E DB2 Server for VSE online support had

the FORCE command.

a storage failure. Return Code =

return-code. Storage Length = length.

server-name is the server that the agent belongs to.

Storage Location = X'location.'

System Action:

Explanation: While terminating a logical unit of work,

CICS Partition

the DB2 Server for VSE online support encountered a

storage error attempting to free storage used for the

The CIRB or CIRA transaction bypasses the server that

application’s messages to the database manager. (In this

had the error and continues processing the next server

case, the message exceeded 1028 bytes in length and

in the server name list.

could not fit into the normal message buffer which was

allocated, thus causing the temporary need for a larger

Database Manager Partition

storage requirement.) The Return Code value

The Database manager comes up and an in-doubt agent

return-code is the return code from the VSE FREEVIS

has been created.

macro. length is the length of storage represented as a

decimal value. location is the storage location

Operator Response: Use the SHOW CONNECT

represented as a hexadecimal value.

command to obtain more information about the logical

units of work. Then use the FORCE command to

System Action: The DB2 Server for VSE online

commit or rollback the logical units of work.

support internally activates the Resource Adapter

Remove Connections transaction (CIRR). CIRR writes

In general, the logical units of work should be

the above message. If the server that had the error in

committed because the application had attempted a

the only one that has connections, then the online

COMMIT which was interrupted by the system or

support is disabled when the server is disabled. If there

subsystem failure. However, if the application was

are connections to other servers, then the online

updating multiple resources (for example, DB2 Server

for VSE resources, DL/I resources, and CICS resources),

Chapter 5. ARI0400-ARI0498 Resource Adapter Messages

Resource Adapter Messages - ARI0400-ARI0498

the installation database administrator should be

ARI0427A DB2 Server for VSE online support

consulted to determine the action. (See message

detected an error during

ARI0232E for more information.)

synchronization. SQLCODE = sqlcode

After all logical units of work are resolved with a

SQLERRD1 = errd1 SQLERRD2 = errd2

COMMIT or a ROLLBACK, reenter the CIRB or CIRA

SERVER = server-name

transaction, if this message was issued in the CICS

Explanation: After encountering the conditions

partition.

indicated by sqlcode, errd1, and errd2, the DB2 Server for

VSE online support internally activated the Resource

ARI0425I

Online LUWs are still active for server

Adapter Remove Connections transaction (CIRR) for

server-name.

the named server in QUICK mode. CIRR wrote the

above message.

Explanation: The Resource Adapter Termination

transaction (CIRT) or the Resource Adapter Remove

sqlcode, errd1, and errd2 is the SQL return information.

Connections transaction (CIRR) was executed with the

Refer to Chapter 18, “SQLCODEs,” on page 237 for an

input parameter NORMAL. Since some online

explanation of the error. server-name is the application

applications are still accessing the database manager,

server that reported the problem.

the termination process must be delayed.

Operator Response: Use the SHOW CONNECT and

server-name is the server that is still being accessed.

FORCE commands to COMMIT or ROLLBACK any

units which are prepared for COMMIT or ROLLBACK.

System Action: The CIRT or CIRR transaction will

Then, enter the CIRB or CIRA transaction to reactivate

delay for a time interval, as specified by the INTERVAL

the connections to the server.

input parameter. After the delay, the process will again

attempt to terminate. If it finds that transactions are

still accessing the database manager or transactions

ARI0430I

No transaction timing displayed because

which previously accessed the database manager are

of the state of TOD clock.

still active, CIRT or CIRR will issue a retry message

Explanation: The Resource Adapter display

(see ARI0414A), and terminate in order to free the

information transaction (CIRD) encountered an error

terminal.

during a STORE CLOCK operation. The clock is not

Operator Response: Do nothing until the retry

set.

message ARI0414A is displayed.

System Action: The internal timer in the CIRD

transaction is set to 0. CIRD display output will not

ARI0426I

The disable transaction tran must delay

display the time value until the Online Resource

for a interval-second time interval before

Adapter is restarted with the Time-Of-Day clock

it retries the EXEC CICS DISABLE

working properly.

interface.

Explanation: The Resource Adapter Termination

ARI0431E Unable to allocate storage in the

transaction (CIRT) or Resource Adapter Remove

CICS/VSE partition. Transaction =

Connections transaction (CIRR) has terminated all

CIRD. Return Code = nn. The CIRD

communications to the database manager and had

transaction is terminated.

attempted to disable the online support. However, the

Explanation: The Resource Adapter display

EXEC CICS DISABLE interface has returned a code

information transaction (CIRD) encountered an error

indicating that transactions which had previously

while requesting virtual storage. The meanings of the

accessed the database manager are still active.

Return Code values (nn) are:

tran is the transaction identifier CIRT or CIRR.

No more virtual storage available

interval is the delay time interval in seconds

Hardware storage error

(INTERVAL input parameter).

Any other

System Action: The CIRT or CIRR transaction uses the

Internal error

EXEC CICS DELAY interface with the keyword

INTERVAL equal to the value specified as an input

System Action: The CIRD transaction ends.

parameter. After the delay, it will again attempt to use

User Response: Notify your system programmer.

the EXEC CICS DISABLE interface to disable the

resource adapter. If the disable attempt fails, the

System Programmer Response: Take action according

transaction will issue a retry message (see ARI0414A),

to the Return Code value:

and terminate in order to free the terminal.

A larger partition is required for the DB2

Operator Response: Do nothing until the retry

Server for VSE Online Resource Adapter; in

message ARI0414A is displayed.

Messages and Codes

Resource Adapter Messages - ARI0400-ARI0498

particular, the GETVIS area of the CICS/VSE

wrong and notify your system programmer.

partition must be increased.

System Programmer Response: Ensure that any newly

Report this hardware storage error to your

installed application programs are not overlaying

hardware service representative.

CICS/VSE or DB2 Server for VSE storage. If the

problem persists, make a record of what went wrong

Any other

and contact the designated support group for your

Make a record of what went wrong and

installation.

contact the designated support group for your

installation.

ARI0435I

tran transaction WRITEQ of queue-name

failed. WRITEQ return code =

ARI0432E Unable to free the storage in the

return-code.

CICS/VSE partition. Transaction =

CIRD. Return Code = nn.

Explanation: The Resource Adapter Begin transaction

(CIRB) unsuccessfully wrote the DBNAME or NLSKEY

Explanation: The Resource Adapter display

to the temporary storage queue ARIDBNAM or

information transaction (CIRD) encountered an error

NLSLKEY and ended with a WRITEQ error, or the

while trying to free virtual storage. Any Return Code

Resource Add Connections transaction (CIRA) or

value (nn) indicates an internal error and is the return

Resource Adapter Remove Connections transaction

code from the VSE FREEVIS macro.

(CIRR) failed to write the DBNAME to the temporary

System Action: The CIRD transaction ends.

storage queue ARIDBNAM and ended with a WRITEQ

error. queue-name is the queue id and return-code is the

User Response: Notify your system programmer.

WRITEQ error code. tran is the transaction identifier

System Programmer Response: Make a record of

CIRB or CIRA.

what went wrong and contact the designated support

System Action: If the WRITEQ is for NLSLKEY, CIRB

group for your installation.

terminates. If it is for DBNAME, CIRB or CIRA or

CIRR continues to enable the Online Resource Adapter.

ARI0433E CICS/VSE end-of-task exit is not

The ARIDBNAM queue is used by ISQL to identify the

supported. The CIRD transaction is

default target application server on the ISQL sign-on

terminated.

screen.

Explanation: The Resource Adapter display

Operator Response: Report this message to the system

information transaction (CIRD) needs the CICS/VSE

programmer for further investigation.

End of Task Exit support, which is not now supported

System Programmer Response: Investigate the

in your installation.

WRITEQ error by analyzing the WRITEQ return code,

System Action: The CIRD transaction ends.

and perform corrective action.

Operator Response: Notify your system programmer.

ARI0436E Automatic restart resynchronization

System Programmer Response: If CIRD display

failed. The CICS log does not contain

information is desired, you must install the CICS/VSE

information for an in-doubt logical unit

restart resynchronization transactions. Refer to the DB2

of work. Connections to server

Server for VSE Program Directory for details.

server-name are not established.

Explanation: During automatic restart

ARI0434E Local task storage (RMLO) identified by

resynchronization processing, CICS/VSE encountered a

CICS/VSE was not found on chain for

logical unit of work that the database manager

server server-name.

indicated needed to be resolved. However, the

information needed to resolve the logical unit of work

Explanation: During the process of unchaining a task

was not on the CICS/VSE log. This generally results

local control block (RMLO), the RMLO passed by

from a CICS/VSE coldstart following a system failure.

CICS/VSE to be deleted from the active task chain was

If a CICS/VSE coldstart did not occur after the last

not found in the chain. This condition can result when

system failure, the CICS/VSE log or the DB2 Server for

an application program overlays CICS/VSE storage or

VSE log data has been damaged. This could be the

DB2 Server for VSE storage.

result of an application that inadvertently overlaid the

System Action: The CIRR transaction is invoked

DB2 Server for VSE resource adapter in CICS/VSE

internally to remove the connections to server-name. If

storage.

connections to other servers exist, they remain active.

This message is followed by messages ARI0423A and

Operator Response: Use the appropriate transaction,

ARI0424I, which identify the logical units of work

CIRB or CIRA, to re-establish connections to the server.

(agents) that need to be resolved. These agents must be

If the problem persists, make a record of what went

resolved (with the FORCE command) before the CIRB

Chapter 5. ARI0400-ARI0498 Resource Adapter Messages

Resource Adapter Messages - ARI0400-ARI0498

or CIRA transaction can be run successfully.

ARI0442E A non-DB2 Server for VSE message has

System Action: The CIRB or CIRA transaction

been received. The Resource Adapter

bypasses the server that had the error and continues

has severed the communication path.

processing the next server in the server name list.

Explanation: The resource adapter received a non-DB2

Operator Response: Refer to the OPERATOR ACTION

Server for VSE message.

for messages ARI0423A and ARI0424I.

System Action: The resource adapter terminated the

communication path.

ARI0438E Automatic restart resynchronization

Operator Response: If you are unable to determine

failed. A logical unit of work that DB2

the cause of the problem, retry the application

Server for VSE indicated needed to be

program. If the problem repeats, collect pertinent

resolved was not identified by the

information and notify the system programmer.

CICS/VSE log as needing resolution.

Programmer response: Make a record of the error and

Explanation: During automatic restart

contact the designated support group for your

resynchronization processing, CICS/VSE encountered a

installation.

logical unit of work that the database manager

indicated needed to be resolved. However, information

in the CICS/VSE log indicated that the logical unit of

ARI0444E &1 transaction DELETEQ of &2. failed.

work did not need to be resolved. CICS/VSE cannot

DELETEQ return code = &3A.

resolve the logical unit of work; it treats this condition

Explanation: The transaction &1 tried to delete the

as an error condition.

ARIDBNAM temporary storage queue and ended with

This condition can occur when an application program

a DELETEQ error. &2. is the queue ID and &3A. is the

overlays a CICS/VSE log buffer, or when a DB2 Server

DELETEQ error code.

for VSE log buffer is destroyed. Or, the CICS/VSE log

System Action: The transaction &1 continues to

or the DB2 Server for VSE log may have been

disable the Online Resource Adapter regardless of the

damaged.

DELETEQ error.

This condition also occurs when the automatic restart

Operator Response: Report this message to the system

synchronization is invoked more than once. If CIRB or

programmer for further investigation.

CIRA is used to start connections to a server that had

in-doubt units of work, those in-doubt units of work

System Programmer Response: Investigate the

are resolved and CICS destroys the log buffer. If CIRA

DELETEQ error by analyzing the DELETEQ return

is invoked again for another server that has in-doubt

code. If the ARIDBNAM queue still exists, try deleting

units of work, there is no more record of them in the

the queue again by using the CICS-supplied

CICS/VSE log buffer and this message is displayed.

transaction.

This message follows messages ARI0423A and ARI0424I

which identify the logical units of work (agents) that

ARI0445E Storage failure occurred while

need to be resolved. These agents must be resolved

attempting to free storage acquired to

before the CIRB or CIRA transaction can be run

support a blocked request.

successfully.

Identifier = &1

System Action: The CIRB or CIRA transaction

FREEVIS Return Code = &2

bypasses the server that had the error without

Storage Length = &3

establishing connections to it and continues processing

Storage Location = &4

the next server in the server name list.

Explanation: The database manager encountered an

Operator Response: Refer to the OPERATOR ACTION

error when attempting to free storage used in support

for messages ARI0423A and ARI0424I.

of a BLOCK request.

System Programmer Response: Ensure that any newly

v &1. identifies the location within the database

installed application programs are not overlaying

manager where the storage error occurred.

CICS/VSE or DB2 Server for VSE storage. If the

v &2. is the return code from the VSE FREEVIS macro.

problem persists, make a record of what went wrong

and contact the designated support group for your

v &3. is the length of the storage represented as a

installation.

decimal value.

v &4. is the storage location represented as a

hexadecimal value.

System Action: The Resource Adapter Remove

Connections transaction (CIRR) is internally activated

which terminates connections to the current server.

Messages and Codes

Resource Adapter Messages - ARI0400-ARI0498

CIRR writes the above message. The current server is

ARI0452I

EXTNAME = external name.

identified by messages issued from the Resource

RDBMS = dbname server version

Adapter Display transaction (CIRD) which is internally

STATUS = status

activated by CIRR.

TIME = time

Operator Response: Correct the storage error and then

LU = luname

reinitialize connections to the server with the CIRA

TPN = tpn

transaction. If online support was terminated as a result

Explanation: This is the normal DB2 Server for VSE

of the storage error, use the CIRB transaction to

response to SQLQRY.

reinitialize connections to the server.

ARI0453I

The transaction name transaction cannot

ARI0446E Error in attempting to execute function.

be started at this time. Please try later.

Modname = modname. Return code =

retcode.

Explanation: A CICS resource used by the Online

Resource Adapter is currently held by either the Begin

Explanation: A Resource Adapter Begin transaction

transaction (CIRB), the Termination transaction (CIRT),

(CIRB) or a Resource Adapter Add Connections

the Add Connections transaction (CIRA), the Remove

transaction (CIRA) was entered to allow access to a

Connections transaction (CIRR) or the Display

remote server. An attempt was made to load the phase

Information transaction (CIRD).

modname, but the load failed.

System Action: The invoked transaction is cancelled.

function is the action that failed.

The transaction holding the resource continues to

modname

execute.

is the name of the phase on which the action

User Response: Try the transaction again at a later

function is performed.

time. Usually the resource is held for a few moments.

retcode is the return code of the function.

Operator Response: Try the transaction again at a

System Action: The Resource Adapter Begin

later time. Usually the resource is held for a few

transaction (CIRB) or the Resource Adapter Add

moments. During the initialization process, if you

Connections transaction (CIRA) bypasses all remote

suspect a problem and the CIRT transaction failed to

application servers. Online access to remote application

terminate the process, then the CIRB transaction can be

servers is not enabled.

purged by using a CICS command. After purging the

CIRB transaction, the CIRT transaction must be issued

User Response: Refer this message to your DB2 Server

to perform the Online Resource Adapter final cleanup.

for VSE Database Administrator.

Database Administrator Action: Determine whether

ARI0454I

Connections to server-name established.

or not you require your application requester to initiate

RMCV at address.

DRDA conversation. If so, recreate the phase modname.

Refer to the DB2 Server for VSE System Administration

Explanation: The Resource Adapter Begin transaction

manual.

(CIRB) was entered to initialize the DB2 Server for VSE

Online Resource Adapter or the Resource Add

Connections transaction (CIRA) was entered. The CIRB

ARI0450I

DB2 Server for VSE online support has

or CIRA transaction completed successfully and online

an entry point of entry-point. RMGL at

access is now allowed to the application server.

pointer. [DRDA online support entry

point at entry-point2.]

System Action: The CIRB or CIRA transaction

continues processing the next server in the server name

Explanation: The Resource Adapter Begin transaction

list.

(CIRB) has completed and online access to the database

manager is activated. This message is displayed as a

Operator Response: Do nothing unless it is necessary

debug aid.

to terminate online access to the application server.

When termination is necessary, enter the CIRT

entry-point is the entry point of the DB2 Server for VSE

transaction.

Online Support.

If CIRB was entered to modify the initialization

pointer is the pointer to the global control block RMGL.

parameter (for example, increase the number of paths

entry-point2 is the entry point of the DB2 Server for

to the DB2 Server for VSE system), first enter the DB2

VSE Online DRDA Router.

Server for VSE Resource Adapter Termination

transaction (CIRT) to terminate the active resource

System Action: The CIRB transaction ends.

adapter. After CIRT disables the resource adapter

(message ARI0413I is displayed), reenter CIRB with the

new input parameters.

Chapter 5. ARI0400-ARI0498 Resource Adapter Messages

Resource Adapter Messages - ARI0400-ARI0498

ARI0455I

{Connections | Online access} to server-name

ARI0457W Connections to server-name already exist.

{are | is} disabled.

Explanation: The Resource Adapter Begin transaction

Explanation: The Resource Adapter Termination

(CIRB) or the Resource Add Connections transaction

transaction (CIRT) was entered to disable the DB2

(CIRA) was entered to establish connections to an

Server for VSE Online Resource Adapter or the

application server. Connections to that server already

Resource Adapter Remove Connections transaction

existed because of a previous invocation of CIRB or

(CIRR) was entered to disable the connections to a local

CIRA or because the server-name was listed more than

application server or to disable online access to a

once in the server-name list of the CIRB or CIRA

remote application server.

transaction.

System Action: The CIRT or CIRR transaction

System Action: The existing connections remain. The

continues processing the next server in the server name

CIRB or CIRA transaction bypasses the server that had

list.

the error and continues processing the next server in

the server name list.

Operator Response: Do nothing unless it is necessary

to re-establish online access to the application server.

Operator Response: No action is required. If the

Use the CIRB transaction to re-establish online access if

connections to that server need to be changed they

the online resource adapter has been terminated. If the

must first be removed using CIRR or CIRT and then

online resource adapter is still active, use the CIRA

re-established using CIRA or CIRB.

transaction to re-establish online access to the

application server.

ARI0458I

The default server is server-name.

Explanation: The Resource Adapter Begin transaction

ARI0456I

Connections to server-name do not exist.

(CIRB) was entered to initialize the DB2 Server for VSE

Explanation: Three scenarios are possible.

Online Resource Adapter. This message identifies the

name of the default application server.

1. The Resource Adapter Change transaction (CIRC)

was entered to change the default application server

System Action: The CIRB transaction continues

to server-name. The default server could not be

processing the next server in the server name list.

changed because connections to the requested

server do not exist.

ARI0459I

The new default server is server-name.

2. The Resource Adapter Remove Connections

The previous default server was

transaction (CIRR) was entered to disable the

server-name.

connections to an application server but the

connections to the specified server do not exist. If

Explanation: The Resource Adapter Change

no server was specified then the default server is

transaction (CIRC) was entered to change the default

used.

application server to server-name. The default server

3. The Resource Adapter Display transaction (CIRD)

was successfully changed to the new value. The

was entered to display active transactions for

previous value is displayed for information only.

server-name. Nothing could be displayed because

System Action: The CIRC transaction ends. The

connections to the specified server do not exist.

default server is changed.

System Action: If the CIRC transaction was entered it

ends and the default server is not changed. If the CIRR

ARI0460W

{Connections | Online access} to the

transaction was entered it bypasses the server that had

default server server-name {have | has}

the error and continues processing the next server in

been disabled.

the server name list. If the CIRD transaction was

entered it ends.

Explanation: The Resource Adapter Termination

transaction (CIRT) was entered or the Resource Adapter

Operator Response: If the CIRC transaction was

Remove Connections transaction (CIRR) was entered to

entered, the CIRA transaction can be used to establish

terminate the connections to the default local server or

connections to the desired server. When the connections

to terminate the online access to the default remote

have been successfully established the CIRC transaction

server.

can be run to change the default server.

System Action: The CIRR or CIRT transaction

If the CIRR transaction was entered, determine the

continues processing the next server in the server name

correct server name and retry the CIRR transaction.

list. The default server is inaccessible.

If the CIRD transaction was entered, determine the

Operator Response: The CIRB transaction can be used

correct server name and retry the CIRD transaction.

to re-establish the connections if the online resource

adapter is not active or the CIRA transaction can be

used to re-establish the connections if the online

resource adapter is still active or the CIRC transaction

Messages and Codes

Resource Adapter Messages - ARI0400-ARI0498

can be used to specify a new default server if the

tran is the transaction identifier CIRT or CIRR.

online resource adapter is still active.

interval is the delay interval in seconds (INTERVAL

If the lost connections were the last ones, then the

input parameter).

online resource adapter has been disabled. In this case

System Action: The CIRT or CIRR transaction will

the CIRB transaction must be used to start the online

delay for the time interval specified. After the delay, the

resource adapter.

process will again attempt to terminate. If it finds that

transactions are still accessing at least one of the servers

ARI0461E Connections to server-name are already

to be disabled, or that transactions which previously

being disabled.

accessed at least one of the servers to be disabled are

still active, CIRT or CIRR will issue a retry message

Explanation: The Resource Adapter Termination

(see ARI0414A) and terminate in order to free the

transaction (CIRT) or the Resource Adapter Remove

terminal.

Connections transaction (CIRR) was entered to

terminate the connections to server-name but a previous

Operator Response: Do nothing until the retry

invocation of CIRT or CIRR was already entered for

message ARI0414A is displayed.

server-name.

System Action: The CIRT or CIRR transaction

ARI0464E Connections to server-name could not be

continues to process any remaining servers before

disabled because the password is

ending.

invalid.

Explanation: The Resource Adapter Remove

ARI0462E Connections to server server-name could

Connections transaction (CIRR) or the Resource

not be established.

Adapter Termination transaction (CIRT) attempted to

disable the connections to server-name but could not

Explanation: The Resource Add Connections

because the password supplied was not the same as the

transaction (CIRA) or the Resource Adapter Begin

password that was used to initially enable the

transaction (CIRB) was entered to establish connections

connections to server-name.

to server server-name but was unsuccessful.

System Action: The CIRR or CIRT transaction

System Action: If a server name list was specified, the

continues processing the next server in the server-name

CIRB or CIRA transaction continues processing the

list.

other servers in the list until it is finished if the error

was not severe. If the error was severe so that

Operator Response: Reissue the CIRR or CIRT

processing cannot continue, the remaining servers in

transaction with the correct password.

the server name list will not be processed and the CIRB

or CIRA transaction ends.

ARI0465I

Transactions are still active for server

This message is also issued for the remaining servers in

server-name.

the list which were not processed because a previous

Explanation: The Resource Adapter Termination

server encountered a severe error.

transaction (CIRT) or the Resource Adapter Remove

If no server name list was specified or the failing server

Connections transaction (CIRR) has terminated all

was the last one in the list then the CIRB or CIRA

communications to the server server-name. However,

transaction ends.

transactions which had previously accessed the server

are still active.

Operator Response: Previous messages issued should

indicate what error occurred that prevented the

server-name is the server that is still being accessed.

connections from being established. Refer these

System Action: The CIRT or CIRR transaction will

messages to your system programmer.

delay for a time interval as specified by the INTERVAL

System Programmer Response: Correct the error and

input parameter. After the delay, it will again attempt

reissue the CIRB or CIRA command.

to terminate. If transactions are still active, CIRT or

CIRR will issue a retry message (see ARI0414A), and

terminate in order to free the terminal.

ARI0463I

The DISABLE transaction tran must

delay for a interval-second interval

Operator Response: Do nothing until the retry

before attempting the disable.

message ARI0414A is displayed.

Explanation: The Resource Adapter Termination

transaction (CIRT) or the Resource Adapter Remove

ARI0466E CICS restart resynchronization is not

Connections transaction (CIRR) was entered to disable

available. The tran transaction is ended.

connections but was unsuccessful. Check previously

Explanation: The Resource Add Connections

displayed messages ARI0425I, ARI0465I, or ARI0469I to

transaction (CIRA) or Resource Adapter Begin

determine which servers could not be disabled.

Chapter 5. ARI0400-ARI0498 Resource Adapter Messages

Resource Adapter Messages - ARI0400-ARI0498

transaction (CIRB) detected that the CICS restart

terminate in order to free the terminal.

resynchronization transaction CRSY is not enabled.

Operator Response: Do nothing until the retry

tran is the CIRA or CIRB transaction.

message ARI0414A is displayed.

System Action: The CIRA or CIRB transaction ends.

ARI0470E Trace file OPEN failed. Reason Code =

Operator Response: Enable the CICS restart

nn. Return Code = nn.

resynchronization transaction CRSY. Then reissue the

CIRA or CIRB transaction.

Explanation: The Resource Adapter trace is being

initialized before application execution. An error

System Programmer Response: Ensure that CICS

occurred when the database manager attempted to

restart resynchronization support has been installed

open the trace output file on tape unit or CMS

properly. See the DB2 Server for VSE Program Directory

minidisk. The Reason Code value is the Primary Error

for more details.

Code. The Return Code value is the Secondary Error

Code. For further explanation, look up the displayed

ARI0467I

RMCV for remote server server_name

error codes under either Chapter 21, “Sequential File

established. RMCV at XXXXXXXX.

Errors,” on page 361, or "SEQ FILE ERRORS" in the

HELP text.

Explanation: The Resource Adapter Begin transaction

(CIRB) was entered to initialize the DB2 Server for VSE

System Action: The trace facility remains inactive and

Online Resource Adapter or the Resource Adapter Add

the application continues to execute.

Connections transaction (CIRA) was entered. The CIRB

Operator Response: For corrective action, look up the

or CIRA transaction completed successfully and online

displayed error codes under either Chapter 21,

access is now allowed to the remote application server.

“Sequential File Errors,” on page 361, or "SEQ FILE

System Action: The CIRB or CIRA transaction

ERRORS" in the HELP text.

continues processing the next server in the server name

System Programmer Response: See the Operator

list.

Response.

Operator Response: Do nothing unless it is necessary

to terminate online access to the remote application

ARI0471I

Trace is ON.

server. When termination is necessary, enter the CIRT

transaction.

Explanation: The Resource Adapter trace parameters

have been successfully processed. The trace is now

active with trace output going to a tape unit or a CMS

ARI0468I

DISABLE changed from QUICK to

minidisk.

NORMAL for remote server server-name.

System Action:

Explanation: A Resource Adapter Terminate

v Trace is active. Resource Adapter trace is active as

transaction (CIRT) or a Resource Adapter Remove

specified by the TRACERM, TRACECONV,

Connections transaction (CIRR) was entered using

initialization parameters to the SQLINIT EXEC.

QUICK mode, but QUICK mode is not supported for a

remote server. The transaction has converted the

v Trace output is directed to tape unit or CMS

QUICK mode to NORMAL, and will process the

minidisk.

shutdown in a NORMAL mode.

System Action: Shutdown continues. NORMAL

ARI0472E Trace file CLOSE failed. Reason Code =

shutdown will complete only when all the

nn. Return Code = nn.

conversations to the remote server are deallocated.

Explanation: The Resource Adapter Trace is being

turned off during application termination. When the

ARI0469I

APPC conversations are still active for

system attempted to close the trace output file on a

server server_name.

tape unit or a CMS minidisk, a termination error

occurred. The Reason Code value is the Primary Error

Explanation: A Resource Adapter Terminate

Code. The Return Code value is the Secondary Error

transaction (CIRT) or a Resource Adapter Remove

Code. For further explanation, look up the displayed

Connections transaction (CIRR) was entered to

error codes under either Chapter 21, “Sequential File

terminate online access to a remote server, but there are

Errors,” on page 361, or "SEQ FILE ERRORS" in the

still active conversations for the server.

HELP text.

System Action: The CIRT or CIRR transaction will

System Action: Trace shutdown is completed. DB2

delay for a time interval as specified by the INTERVAL

Server for VSE Resource Adapter trace is in the OFF

input parameter. After the delay, it will again attempt

state. Assume that the trace tape or minidisk file was

to terminate. If conversations are still active, CIRT or

not closed and is not fully processable (see below).

CIRR will issue a retry message (see ARI0414A), and

Messages and Codes

Resource Adapter Messages - ARI0400-ARI0498

Operator Response: Report the problem (message) to

System Action: The user or global SQLGLOB

your system programmer. Include any CMS minidisk

parameters are replaced with the new values. The new

or tape unit error messages displayed by CMS.

values will remain in effect until:

You can run the DB2 Server for VSE Trace Formatter

explicitly changed through:

Utility Program (ARIMTRA). It will format and output

1. the SQLGLOB File Batch Update/Query Program

all trace data up to the point of failure. At that point, it

(ARIRBGUD), or

may end because of a lack of tape/minidisk CLOSE

2. a subsequent DSQU or DSQG transaction or

recording or an unreadable record on the

tape/minidisk.

explicitly deleted through:

System Programmer Response: For corrective action,

1. the SQLGLOB File Batch Update/Query Program

look up the displayed error codes under either

(ARIRBGUD), or

Chapter 21, “Sequential File Errors,” on page 361, or

2. a subsequent DSQD transaction.

"SEQ FILE ERRORS" in the HELP text.

Any subsequent DRDA connections will use the new

ARI0473I

Trace is OFF.

values.

Explanation: The Resource Adapter Trace is inactive

and the trace output file is closed on a tape unit or a

ARI0482I

The following {user | global} SQLGLOB

CMS minidisk.

parameters have been saved [for user

userid]:

System Action: The trace output file is closed.

Operator Response: None required.

CHARNAME

= charname.

QRYBLKSIZE = qryblksize.

DBCS

= dbcs.

ARI0480I

The user has not signed on.

SYNCPOINT

= syncpoint.

Explanation: An Update User SQLGLOB Parameters

CCSIDSBCS

= ccsidsbcs.

transaction (DSQU) or a Delete SQLGLOB Parameters

CCSIDMIXED = ccsidmixed.

transaction (DSQD) was entered, but the signed-on

CCSIDDBCS

= ccsiddbcs.

userid is not available, or the update was not

TRACERA

= tracera.

successful. If message ARI0486E is displayed, the

TRACEDRRM

= tracedrrm.

update failed.

TRACECONV

= traceconv.

COMMPROTO = commproto.

System Action: Processing ends. The SQLGLOB

parameters are not updated.

Explanation: An Update User SQLGLOB Parameters

transaction (DSQU) or an Update Global SQLGLOB

User Response: Retry the transaction from a valid

Parameters transaction (DSQG) was entered, and the

userid.

update completed successfully. The displayed

SQLGLOB parameter values have been saved in the

ARI0481I

The following {user | global} SQLGLOB

SQLGLOB file.

parameters have been replaced [for user

System Action: The user or global SQLGLOB

userid]:

parameters are replaced with the new values. The new

values will remain in effect until:

CHARNAME

= charname.

QRYBLKSIZE = qryblksize.

explicitly changed through:

DBCS

= dbcs.

1. the SQLGLOB File Batch Update/Query Program

SYNCPOINT

= syncpoint.

(ARIRBGUD), or

CCSIDSBCS

= ccsidsbcs.

2. a subsequent DSQU or DSQG transaction or

CCSIDMIXED = ccsidmixed.

CCSIDDBCS

= ccsiddbcs.

explicitly deleted through:

TRACERA

= tracera.

TRACEDRRM

= tracedrrm.

1. the SQLGLOB File Batch Update/Query Program

TRACECONV

= traceconv.

(ARIRBGUD), or

COMMPROTO = commproto.

2. a subsequent DSQD transaction.

Explanation: An Update User SQLGLOB Parameters

Any subsequent DRDA connections will use the new

transaction (DSQU) or an Update Global SQLGLOB

values.

Parameters transaction (DSQG) was entered, and the

update completed successfully. The displayed

SQLGLOB parameter values have been replaced with

the new values.

Chapter 5. ARI0400-ARI0498 Resource Adapter Messages

Resource Adapter Messages - ARI0400-ARI0498

entered without all parameters specified, or a Delete

ARI0483I

The {user | global} SQLGLOB parameters

User SQLGLOB Parameters transaction (DSQD) was

[for user userid] are:

entered, and the global SQLGLOB record does not

exist.

CHARNAME

= charname.

QRYBLKSIZE = qryblksize.

System Action: Processing ends.

DBCS

= dbcs.

User Response: Retry the transaction without the

SYNCPOINT

= syncpoint.

userid parameter to display the global SQLGLOB

CCSIDSBCS

= ccsidsbcs.

parameters. If user SQLGLOB parameters are desired,

CCSIDMIXED = ccsidmixed.

use the DSQU transaction to create them.

CCSIDDBCS

= ccsiddbcs.

TRACERA

= tracera.

TRACEDRRM

= tracedrrm.

ARI0486E

{DSQG | DSQU | DSQD | DSQQ}

TRACECONV

= traceconv.

cannot be completed successfully.

COMMPROTO = commproto.

Explanation: An Update Global SQLGLOB Parameters

Explanation: A Query SQLGLOB Parameters

transaction (DSQG) or an Update User SQLGLOB

transaction (DSQQ) was entered. If the userid parameter

Parameters transaction (DSQU) or a Delete User

was specified, and user SQLGLOB parameters exist for

SQLGLOB Parameters transaction (DSQD) or a Query

the specified userid, then the user SQLGLOB

SQLGLOB Parameters transaction (DSQQ) was entered,

parameters are displayed. Otherwise, the global

but could not complete successfully.

SQLGLOB parameters are displayed.

System Action: Processing ends.

System Action: The SQLGLOB parameters are

User Response: Refer to previous error messages for

displayed.

the cause of the error. If the problem persists, notify

your System Programmer.

ARI0484I

The user SQLGLOB parameters for user

System Programmer Response: Refer to the

userid were deleted. The following

previously displayed error messages for the cause of

global SQLGLOB parameters are now in

the error.

effect for user userid:

CHARNAME

= charname.

ARI0487E The SQLGLOB file does not exist.

QRYBLKSIZE = qryblksize.

Explanation: An Update Global SQLGLOB Parameters

DBCS

= dbcs.

transaction (DSQG) or an Update User SQLGLOB

SYNCPOINT

= syncpoint.

Parameters transaction (DSQU) or a Delete User

CCSIDSBCS

= ccsidsbcs.

SQLGLOB Parameters transaction (DSQD) or a Query

CCSIDMIXED = ccsidmixed.

SQLGLOB Parameters transaction (DSQQ) was entered,

CCSIDDBCS

= ccsiddbcs.

but failed because the SQLGLOB file could not be

TRACERA

= tracera.

found.

TRACEDRRM

= tracedrrm.

TRACECONV

= traceconv.

System Action: Processing ends.

COMMPROTO = commproto.

User Response: Notify your System Programmer.

Explanation: A Delete User SQLGLOB Parameters

System Programmer Response: Recreate the

transaction (DSQD) was entered, and completed

SQLGLOB file using the IBM-supplied job control

successfully.

program ARISGDEF.

System Action: The user SQLGLOB parameters for

the signed-on userid are deleted. Any subsequent

ARI0488D The global SQLGLOB parameters will

DRDA connections done on behalf of this signed-on

be used when the user SQLGLOB

userid will use the global SQLGLOB parameters.

parameters are deleted.

ARI0485I

The {global | user} SQLGLOB parameters

Are you sure you want to delete the user

[for user userid] do not exist.

SQLGLOB parameters for user userid?

Enter 0(No) or 1(Yes).

Explanation: A Query SQLGLOB Parameters

transaction (DSQQ) was entered for a specified userid,

Explanation: A Delete User SQLGLOB Parameters

but the user SQLGLOB parameters for the specified

transaction (DSQD) was entered. Confirmation of the

userid do not exist. Either a previous DSQU transaction

delete is required.

was not executed to create the user SQLGLOB

parameters, or a previous DSQD transaction deleted the

System Action: Processing is halted until a response is

user SQLGLOB parameters. Alternatively, an Update

entered. If a 1 is entered, the delete continues. If a 0 is

User SQLGLOB Parameters transaction (DSQU) was

entered, processing ends.

Messages and Codes

Resource Adapter Messages - ARI0400-ARI0498

User Response: Reply with 1 (Yes) to confirm the

ARI0492I

An unauthorized change has been made

delete, or 0 (No) to cancel the operation.

to the SQLGLOB file, which may have

altered the {user | global} SQLGLOB

ARI0489E The {CCSIDS | CCSIDM | CCSIDG} of

parameters [for user userid]. These

CHARNAME = charname in the

parameters will be replaced.

ARISCCSD phase is not in the expected

Explanation: An Update User SQLGLOB Parameters

format.

transaction (DSQU) or an Update Global SQLGLOB

Explanation: A record was found in the ARISCCSD

Parameters transaction (DSQG) was entered with all

phase for the charname value, but the record does not

parameters specified. The transaction found that the

contain valid data.

SQLGLOB VSAM file had been changed, but not

through DSQU, DSQG or the SQLGLOB File Batch

System Action: Processing ends.

Update/Query Program (ARIRBGUD). The SQLGLOB

User Response: Notify your system programmer.

values may have been altered. This message is

displayed for information purposes only, since all the

System Programmer Response: Recreate the

SQLGLOB values will be replaced by the transaction.

ARISCCSD phase using the IBM-supplied job control

program ARISCNVD. Refer to the DB2 Server for VSE

System Action: Processing continues.

Program Directory.

User Response: No action required.

ARI0490E An unauthorized change has been made

ARI0493I

DSQD operation has been cancelled.

to the SQLGLOB file, which may have

altered the {user | global} SQLGLOB

Explanation: You entered 0 (NO) when DSQD

parameters [for user userid].

prompted you to confirm the delete request.

Explanation: An Update User SQLGLOB Parameters

System Action: No action is taken.

transaction (DSQU) or an Update Global SQLGLOB

Parameters transaction (DSQG) or a Query SQLGLOB

ARI0494E Invalid input parameter entered.

Parameters transaction (DSQQ) or a Delete User

Parameter = parm.

SQLGLOB Parameters transaction (DSQD) was entered

or the SQLGLOB File Batch Update/Query Program

Explanation: An Update User SQLGLOB Parameters

(ARIRBGUD) was executed. The transaction found that

transaction (DSQU) or an Update Global SQLGLOB

the SQLGLOB VSAM file had been changed, but not

Parameters transaction (DSQG) or a Query SQLGLOB

through DSQU or DSQG or the batch update/query

Parameters transaction (DSQQ) was entered with an

program. The SQLGLOB values may have been altered,

incorrect parameter, or a Delete User SQLGLOB

and should not be used.

Parameters transaction (DSQD) was entered with a

parameter.This message can also be received from the

System Action: Processing ends.

SQLGLOB File Batch Update program (ARICBGUD).

User Response: Use the DSQU transaction (for user

System Action: Processing ends.

SQLGLOB parameters) or the DSQG transaction (for

global SQLGLOB parameters) or execute the job

User Response: Correct or remove the parameter and

ARIRBGUD (for batch update for both global and user

retry the transaction.

SQLGLOB parameters) specifying all parameters to

replace all of the entries in the SQLGLOB file.

ARI0495E Write error trace file. Reason

Code = response code.

ARI0491E You have not entered any parameters for

Explanation: When the DB2 for VSE Online Resource

the {DSQG | DSQU} transaction. Please

Adapter attempted to write trace data to the trace

try again.

output file, an access error occurred. The Reason Code

Explanation: The Update Global SQLGLOB

value is the CICS/VSE response code (EIBRCODE)

Parameters transaction (DSQG) or the Update User

returned after the Online Resource Adapter attempted

SQLGLOB Parameters transaction (DSQU) was entered

to write trace data to a transient data queue.

with no parameters specified. You must specify at least

System Action: Any further Online Resource Adapter

one parameter.

trace output is disabled.

System Action: Processing ends.

User Response: Save this message and give it to your

User Response: Reenter the desired transaction with

system programmer.

the proper parameters.

System Programmer Response: Refer to the CICS/VSE

Application Programming Reference manual for a

description of the EIBRCODE.

Chapter 5. ARI0400-ARI0498 Resource Adapter Messages

Resource Adapter Messages - ARI0400-ARI0498

phase. Refer to the DB2

Server for VSE System

ARI0496I

An unauthorized change has been made

Administration manual.

to the SQLGLOB file, which may have

altered the user SQLGLOB parameters

for user userid.

Explanation: A Delete User SQLGLOB Parameters

transaction (DSQD) was entered. The transaction found

that the SQLGLOB VSAM file had been changed, but

not through DSQU, DSQG or the SQLGLOB File Batch

Update/Query Program (ARIRBGUD). The SQLGLOB

values may have been altered. This message is

displayed for information purposes only, since all the

user SQLGLOB values will be deleted by the

transaction.

System Action: Processing continues.

User Response: No action required.

ARI0497E The DRDA facility has not been

installed. Processing of server

server_name is bypassed.

Explanation: A Resource Adapter Begin transaction

(CIRB) or a Resource Adapter Add Connections

transaction (CIRA) was entered to allow online access

to a remote server, but the DRDA AR support has not

been enabled.

System Action: The Resource Adapter Begin

transaction (CIRB) or the Resource Adapter Add

Connections transaction (CIRA) bypasses all remote

application servers. Online access to remote application

servers are not enabled.

User Response: Contact your database administrator

to enable the DRDA AR support.

Database Administrator Action: Determine whether or

not you require your application requester to initiate

DRDA conversation. If so, enable the DRDA facility by

running the job ARIS715D. Refer to the DB2 Server for

VSE System Administration manual for complete details.

If this message was preceded by message ARI0446E or

ARI0498E, recreate the phase mentioned in these

messages. Refer to the DB2 Server for VSE System

Administration manual for complete details.

ARI0498E The phase phase is empty.

Explanation: A Resource Adapter Begin transaction

(CIRB) or a Resource Adapter Add Connections

transaction (CIRA) was entered to allow online access

to a remote server. An attempt was made to access the

phase phase, but the phase contains no records.

System Action: Processing ends. The Resource

Adapter Begin transaction (CIRB) or the Resource

Adapter Add Connections transaction (CIRA) bypasses

all remote application servers. Online access to remote

application servers are not enabled.

User Response: Notify your system programmer.

System Programmer Response: Recreate the phase

Messages and Codes

Chapter 6. ARI4000-ARI4599 DB2 Server for VSE Control

Messages

Operator Response: Stop and restart CICS.

ARI4000E Invalid input parameter entered.

Parameter = parm.

ARI4002E CICS/VSE load of module-name failed

Explanation: The DAXP or the DAXT transaction

[for DRDA TRUE TRUE-name]. Resp =

detected an incorrect input parameter.

resp1. Resp2 = resp2.

parm is the parameter which was not valid. For DAXP,

Explanation: CICS/VSE was not able to load

parm may be PASSWORD, LANGID, or

module-name in one of the following situations:

SERVER_NAME. For DAXT, parm may be PASSWORD,

MODE, INTERVAL, or SERVER_NAME.

v The DAXP transaction attempted to load the

phase/load module ARICDR2 or the message

PASSWORD must be a character string of 1 to 8

repository.

characters with no imbedded blanks. The character

v The DAXT transaction attempted to load the phase

string for PASSWORD, which is input to DAXT, must

ARICDR2.

be the same string that the AXE transaction used to

autostart the DRDA TRUE which the DAXT transaction

v While autostarting DRDA TRUE support TRUE-name,

is disabling. PASSWORD must be preceded by one or

the AXE transaction attempted to load one of the

more blanks.

phase/load modules ARICDRAD, ARICDR2 or the

message repository.

LANGID must be a character string of 1 to 5 characters

with no imbedded blanks. It must be one of AMENG,

module-name will be either ARICDRAD, ARICDR2, or

UCENG, FRANC, GER, KANJI, or HANZI.

the name of a DB2 Server for VSE message repository.

SERVER_NAME must be a character string of 1 to 18

characters with no imbedded blanks. The server

TRUE-name is the name of the DRDA TRUE support

APPLID corresponding to SERVER_NAME (found in

the AXE transaction is autostarting.

the DBNAME directory) must be within the range

'SYSARI00' to 'SYSARI09' or 'SYSARI0A' to 'SYSARI0Z'.

resp is the CICS/VSE EIBRESP number.

MODE must be either the character string NORMAL or

resp2 is the CICS/VSE EIBRESP2 number.

the character string QUICK.

System Action: The DAXP or DAXT transaction ends.

INTERVAL must be a decimal value between 0 and

The AXE transaction ends the enabling of the DRDA

3600.

TRUE.

The delimiter between parameters is a comma or one

Operator Response: Refer this message to your

or more blanks. Commas must be used for null parms.

system programmer.

System Action: The DAXP or DAXT transaction ends.

System Programmer Response: Verify that the

Operator Response: Reissue the DAXP or DAXT

program named ARICDRAD or ARICDR2 or the DB2

transaction with the correct input parameters. Refer to

Server for VSE message repository is correctly defined

the DB2 Server for VSE System Administration manual

to CICS/VSE and that its phase is in an accessible

for more information about the input parameters.

library. See the DB2 Server for VSE System

Administration manual.

ARI4001E DRDA TRUE TRUE-name is already

present in this partition.

ARI4003E Error in attempting to use CICS/VSE

service [for DRDA TRUE TRUE-name].

Explanation: The AXE transaction was autostarting

CICS/VSE service = service. EIBRCODE

DRDA TRUE support TRUE-name, but detected that the

= return-code.

DRDA TRUE is already enabled and active within the

partition. Only one DRDA TRUE with the name

Explanation: The DAXP transaction, the DAXT

TRUE-name may be active within a CICS/VSE partition.

transaction, or the AXE transaction while autostarting

DRDA TRUE support TRUE-name, encountered an error

TRUE-name is the name of the DRDA TRUE support

while using the EXEC CICS interface.

the AXE transaction is autostarting.

TRUE-name is the name of the DRDA TRUE support

System Action: The AXE transaction ends the

the AXE transaction is autostarting.

enabling of the DRDA TRUE.

DB2 Server for VSE Control Messages -ARI4000-ARI4599

service defines the CICS/VSE service/command which

It may be necessary to stop and restart CICS.

was executed. Use the CICS/VSE manuals listed in the

System Programmer Response below for this message

ARI4006E Error in using system communications

to map the value for service to the CICS/VSE EIBFN

facility for DRDA TRUE TRUE-name.

code. The EIBFN code may be used as an aid in

Request=request. Return Code =

interpreting the value for return-code.

return-code. Reason Code = reason-code.

return-code is the CICS/VSE return (EIBRCODE).

Explanation: One of the following situations has

System Action: The DAXP or DAXT transaction ends.

occurred:

The AXE transaction ends the enabling of the DRDA

v While autostarting DRDA TRUE support TRUE-name,

TRUE.

the AXE transaction encountered an error condition

using the system communication facility.

Operator Response: Refer this message to your

system programmer.

v While the DRDA TRUE TRUE-name was executing, it

encountered an error condition using the system

System Programmer Response: Correct the CICS/VSE

communication facility.

problem and reissue the DAXP or DAXT transaction.

See the CICS/VSE Application Programming Reference ,

TRUE-name is the name of the DRDA TRUE support.

SC33-0713, for a description of the EIBRCODE. If the

CICS/VSE service was EXTRACT, ENABLE, START, or

request identifies the VSE XPCC request code.

DISABLE refer to "System commands" in the CICS/VSE

System Programming Reference , SC33-0711.

return-code identifies the DB2 Server for VSE return

code.

ARI4004E Unable to allocate storage in the

CICS/VSE partition [for DRDA TRUE

reason-code identifies the reason code from the system

TRUE-name]. Requested size = size.

communication facilities of the operating system.

Explanation: The DAXP transaction, the DAXT

transaction, or the AXE transaction while autostarting

See Chapter 20, “DB2 Server for VSE Reason Codes,”

DRDA TRUE support TRUE-name, was not able to

on page 355 for a description of the codes provided

obtain the storage required for execution.

with this message.

TRUE-name is the name of the DRDA TRUE support

System Action: If the AXE transaction encountered

the AXE transaction is autostarting.

the communications error, it ends the enabling of the

DRDA TRUE. If the DRDA TRUE support encountered

size defines the number of bytes which were required.

the communications error, it internally activates DAXT

System Action: The DAXP or DAXT transaction ends.

for termination. DAXT generates the error message.

The AXE transaction ends the enabling of the DRDA

Operator Response: Refer this message to your

TRUE.

system programmer.

Operator Response: Provide CICS/VSE with a larger

System Programmer Response: Correct the

partition.

communication error.

Note: If the communication error was because of a

ARI4005E The attempt to log on to the system

problem in the DB2 Server for VSE partition and a

communication facility failed. The name

dump was written to SYSLST or SYSLOG, the dump

name is not unique in the system.

contains information necessary for correcting the

problem.

Explanation: While autostarting the DRDA TRUE

support, the AXE transaction attempted to log on to the

system communication facility with the name name. The

ARI4007E Error attempting to execute SQL by

system communication facility returned a code

DRDA TRUE TRUE-name. SQL = sql

indicating that the name name was not unique in the

request. SQLCODE = sqlcode. SQLERRD1

system.

= errd1. SQLERRD2 = errd2.

name is the name of the application identified to the

Explanation: While autostarting DRDA TRUE support

system communication facility.

TRUE-name, the AXE transaction encountered an error

attempting to execute SQL.

System Action: The AXE transaction ends the

enabling of the DRDA TRUE.

TRUE-name is the name of the DRDA TRUE support

the AXE transaction is autostarting.

Operator Response: Determine why name is not

unique in the system communications facility and

sql request is the SQL request being executed.

correct it.

sqlcode, errd1, and errd2 are the return code information.

Messages and Codes

DB2 Server for VSE Control Messages -ARI4000-ARI4599

Refer to Chapter 18, “SQLCODEs,” on page 237 for an

default settings for the DRDA TRUE of application

explanation of the error.

server server-name.

System Action: The AXE transaction ends the

langid is the DAXP LANGID parameter.

enabling of the DRDA TRUE.

server-name is the DAXP SERVER_NAME parameter.

Operator Response: Refer this message to your DB2

server-applid is the server APPLID of the DAXP

Server for VSE system programmer.

SERVER_NAME parameter.

System Programmer Response: Correct the SQL error.

System Action: The default settings will be used by

the AXE transaction the next time it autostarts the

ARI4008E Server server-name is not ready.

DRDA TRUE support for this server.

Explanation: While autostarting DRDA TRUE support,

the AXE transaction could not connect to the

ARI4011I

The tran transaction cannot be started at

application server for which the DRDA TRUE support

this time. The resource res is not

was being autostarted. Either the application server has

available. Please try later.

not been started or it has not yet completed its

Explanation: A CICS resource used by DB2 Server for

initialization process.

VSE for the DRDA TRUE is currently held by either the

server-name is the name of the application server for

AXE transaction while autostarting DRDA TRUE

which the DRDA TRUE support was being autostarted.

support or the DAXT transaction.

System Action: The AXE transaction ends the

tran is the transaction identifier of the invoked

enabling of the DRDA TRUE.

transaction.

Operator Response: Refer this message to your DB2

res is the name of the resource to be enqueued.

Server for VSE database administrator.

System Action: The invoked transaction is cancelled.

Database Administrator Action: Start the application

The transaction holding the resource continues to

server with SYNCPNT = "Y".

execute.

Operator Response: Try the transaction again at a

ARI4009E VSE EXTRACT macro failed for DRDA

later time. Usually the resource is held for a few

TRUE TRUE-name. Operating system

moments.

return code = return-code.

Explanation: While autostarting DRDA TRUE support,

ARI4012I

The disable transaction tran must delay

the AXE transaction issued a VSE EXTRACT request to

for a interval- second interval before it

obtain the partition start and end addresses. The

retries EXEC CICS DISABLE for DRDA

EXTRACT request failed.

TRUE TRUE-name.

TRUE-name is the name of the DRDA TRUE support

Explanation: The DAXT transaction was disabling a

the AXE transaction is autostarting.

DRDA TRUE. However, EXEC CICS DISABLE has

returned a code indicating that AXE transactions are

return-code is the return code from the operating

still active.

system.

tran is the transaction identifier DAXT.

System Action: The AXE transaction ends the

enabling of the DRDA TRUE.

interval is the delay time interval in seconds

(INTERVAL input parameter).

Operator Response: Refer this message to your

system programmer.

TRUE-name is the name of the DRDA TRUE to be

disabled.

System Programmer Response: Save this message and

report this problem to the designated support group for

System Action: The DAXT transaction issues EXEC

your installation.

CICS DELAY with the keyword INTERVAL equal to the

value specified as an input parameter. After the delay,

it will again attempt to issue EXEC CICS DISABLE. If

ARI4010I

The following DRDA TRUE support

the disable attempt fails, DAXT will issue a retry

enabling parameters have been saved:

message (see message ARI4013A) and terminate in

LANGID = langid. SERVER_NAME =

order to free the terminal. If the disable attempts

server-name. SERVER_APPLID =

succeeds, DAXT will issue a disable done message (see

server-applid. These parameters will be

message ARI0191I) and terminate.

used by the AXE transaction when it

autostarts DRDA TRUE support.

Operator Response: Do nothing until the retry

message ARI4013A is displayed, or the disable done

Explanation: The DAXP transaction has saved the

message ARI0191I is displayed.

Chapter 6. ARI4000-ARI4599 DB2 Server for VSE Control Messages

DB2 Server for VSE Control Messages -ARI4000-ARI4599

dapplid is the APPLID of the application server as

ARI4013A Retry the disable transaction tran.

determined by the DAXP transaction.

Application transactions are accessing

the DRDA TRUE for server-name.

aapplid is the APPLID of the application server as

determined by the AXE transaction.

Explanation: The DAXT transaction was not able to

continue because the EXEC CICS DISABLE interface

System Action: The AXE transaction ends the

indicated that AXE transactions which previously

enabling of the DRDA TRUE.

accessed DB2 Server for VSE were still active. This

Operator Response: Reissue the DAXP transaction.

causes the DAXT transaction to delay for a time

interval (INTERVAL input parameter to DAXT) as had

been indicated by message ARI4012I. The delay interval

ARI4016I

The following DRDA TRUE support

has completed but the condition still exists.

enabling parameters have been replaced:

LANGID = langid. SERVER_NAME =

tran is the transaction identifier DAXT.

server-name. SERVER_APPLID =

server-name is the name of the application server for

server-applid.

which we are disabling the DRDA TRUE support.

Explanation: The DAXP transaction was issued for an

System Action: The DAXT transaction ends.

application server for which a previous DAXP

transaction had been issued. The new DAXP

Operator Response: After all AXE transactions which

parameters override the previous DAXP parameters.

are or were accessing DB2 Server for VSE have

This message is followed by message ARI4010I.

terminated, the DAXT transaction should be reentered.

langid is the previous DAXP LANGID parameter.

ARI4014E System error occurred in the DRDA

server-name is the previous DAXP SERVER_NAME

TRUE TRUE-name. Internal shutdown of

parameter.

the DRDA TRUE is starting. Errnum =

server-applid is the server APPLID of the previous

enum.

DAXP SERVER_NAME parameter.

Explanation: An internal system error occurred within

System Action: The new DAXP parameters will be

the DRDA TRUE TRUE-name.

used by the AXE transaction the next time it autostarts

TRUE-name is the name of the DRDA TRUE which

the DRDA TRUE support for the application server.

encountered an internal system error.

enum is the error number used to identify what error

ARI4017E Guest sharing is not allowed in a

had occurred in the DRDA TRUE support.

DRDA 2 environment. Server APPLID =

server-applid.

System Action: The DRDA TRUE began to terminate

itself by internally activating the DAXT transaction.

Explanation: The DAXP transaction was issued for an

DAXT wrote the message.

application server whose APPLID is not within the

range 'SYSARI00' to 'SYSARI09' or 'SYSARI0A' to

Operator Response: Refer this message to your DB2

'SYSARI0Z'. A DRDA2 application requester can only

Server for VSE system programmer.

request access to a DB2 Server for VSE application

server. Requests for connection to a VM application

ARI4015E A DAXP entry was found for server

server (via Guest Sharing) will be rejected.

name server-name but its APPLID does

server-applid is the server APPLID of the DAXP

not match the AXE transaction APPLID.

SERVER_NAME parameter.

DAXP server APPLID = dapplid. AXE

server APPLID = aapplid.

System Action: The DAXP transaction ends.

Explanation: While enabling the DRDA TRUE support

for application server server-name, the AXE transaction

ARI4018A Use the database manager SHOW and

detected an error when it was using the DRDA TRUE

FORCE commands to commit or

defaults set by the DAXP transaction for this

rollback the following units of work:

application server. The server APPLID determined by

the DAXP transaction is different from the server

ARI4019I

SERVER_NAME = server-name. USER ID

APPLID determined by the AXE transaction. This

= user id. AGENT IDENTIFIER = N.

situation will happen when the DB2 Server for VSE

DBNAME Directory and the DAXP parameters are out

Explanation: This message can be displayed in the

of sync.

CICS partition or in the database manager partition.

server-name is the name of the application server for

CICS Partition

whom the AXE transaction is autostarting the DRDA

While autostarting DRDA TRUE support and

TRUE support.

Messages and Codes

DB2 Server for VSE Control Messages -ARI4000-ARI4599

performing TRUE resynchronization, the AXE

application requester’s sync point manager.

transaction was informed by CICS/VSE that a logical

Operator Response: Refer this message to your DB2

unit of work it is trying to resynchronize is lost due to

Server for VSE database administrator.

CICS cold start or that a logical unit of work should

not be resynchronized because it should not be

Database Administrator Action: Manual intervention is

in-doubt.

necessary to ensure that the LUW is in a consistent

state at all sites where the LUW has been distributed.

Database Manager Partition

This may require intervention at this database manager,

After a system or subsystem failure, the database

or possibly at other database managers.

manager detected logical units of work that must be

committed or rolled back. These units of work are

ARI4024I

DRDA TRUE is disabling for server

DRDA2 in-doubt units of work and cannot be resolved

server-name.

automatically by the DRDA TRUE resynchronization

support.

Explanation: The DAXT transaction started to disable

the DRDA TRUE support for an application server.

server-name is the name of the application server that

owns the logical unit of work.

server-name is the name of the application server for

which Distributed Unit of Work support is to be

user id is the established DB2 Server for VSE user ID

disabled.

for the logical unit of work.

System Action: The DAXT transaction continues with

N is the agent identifier which should be used with the

the process of disabling the DRDA TRUE support.

FORCE command.

Database Administrator Action: Watch to make sure

System Action: The LUW remains unsynchronized

that no error messages appear after ARI4024I.

with the sync point manager. The LUW still appears

when SHOW INDOUBT command is issued.

ARI4025E DAXP table overflow encountered. The

Operator Response: Refer this message to your DB2

new DRDA TRUE support enabling

Server for VSE database administrator.

parameters have not been saved.

Database Administrator Action: Use the database

Explanation: The DAXT transaction was trying to save

manager SHOW CONNECT command to obtain more

the new DRDA TRUE enabling parameters in a table,

information about the logical units of work. Then use

but detected an overflow condition.

the database manager FORCE command to commit or

rollback the logical units of work.

System Action: The DAXP transaction terminates and

the new DRDA TRUE enabling parameters are not

In order to clear each LUW from SHOW INDOUBT

saved.

display, it is necessary to use the RESET INDOUBT

command.

Operator Response: Refer this message to your DB2

Server for VSE system programmer.

Manual intervention is necessary, before RESET

INDOUBT is issued, to ensure that the LUW is in a

consistent state at all sites where the LUW has been

ARI4026E Product key validation failed. Return

distributed. This may require intervention at this

code = rc.

database manager, or possibly at other database

Explanation: A valid product license key is not found

managers.

or is invalid. A valid key is required to run DB2 Server

for VSE. The possible values for the return code are:

ARI4020E The DRDA TRUE TRUE-name detected

The key is not found or the key that was

an error during synchronization.

found is invalid.

SQLCODE = sqlcode. SQLERRD1 = errd1.

SQLERRD2 = errd2.

The key validation routine is not loaded.

Explanation: The DRDA TRUE support detected an

System Action: The system is not started.

error while processing a rollback request or phase 2 of

User Response: Report this error to your system

a 2-phase commit request.

programmer.

TRUE-name is the name of the DRDA TRUE that

System Programmer Response: Obtain and install a

detected the synchronization error.

valid key for the product. A valid key can be obtained

sqlcode, errd1, and errd2 is the SQL return information.

by contacting your IBM representative. Instructions for

Refer to Chapter 18, “SQLCODEs,” on page 237 for an

installing the key are found in the DB2 Server for VSE

explanation of the error.

Program Directory.

System Action: The DRDA TRUE is not terminated.

CICS/VSE communicates the error back to the DRDA2

Chapter 6. ARI4000-ARI4599 DB2 Server for VSE Control Messages

DB2 Server for VSE Control Messages -ARI4000-ARI4599

System Action: The application server listens for

ARI4027W There are n day(s) left in the evaluation

TCP/IP connect requests on the port identified in

period for the product DB2/VSE.

port-number. The application server is able to handle

Explanation: A valid license key has not been installed

both SNA connections and TCP/IP connections.

for this product. The evaluation period will expire after

the specified number of days. The product is enabled

ARI4102I

Unable to initialize TCP/IP service.

for a limited period of time. When the evaluation

period has expired, it will not execute until a license

Explanation: The application was unable to initialize

key for the product is installed.

TCP/IP services because access to TCP/IP for VSE was

not available.

System Action: Processing continues.

System Action: The application system continues, but

User Response: Report this error to your system

it can only accept SNA connections.

programmer.

Operator Response: Report this error to your system

System Programmer Response: Obtain and install a

programmer.

valid key for the product. A valid key can be obtained

by contacting your IBM representative. Instructions for

System Programmer Response: If TCP/IP services are

installing the key are found in the DB2 Server for VSE

required, make sure that TCP/IP for VSE is available

Program Directory.

and running, and the two-digit ID number specified for

the SYSPARM= parameter in the OPTION statement of

the application server startup job control is correct.

ARI4028I

DB2 Server for VSE Version N1 Release

Once the error condition is resolved, issue the START

N2 Modification N3

TCPIP operator command to restart TCP/IP support. If

Explanation: This message reports the current version,

TCP/IP services are not required, ignore this message

release and modification level of the database manager.

or start the application server with the TCPPORT=0

parameter to bypass the TCP/IP initialization.

System Action: Processing continues.

ARI4103I

TCP/IP service service-name failed.

ARI4029I

Alternate logging is not enabled because

Return code = n.

LOGMODE is not L.

Explanation: A TCP/IP function was performed but

Explanation: The database manager detected an

an error occurred during the execution of the function.

inactive log is defined in the system. However, the

service-name identifies the function and n is the return

inactive log can only be used when LOGMODE=L.

code that was received.

System Action: Processing continues.

System Action: The system continues.

Operator Response: Refer this message to your

Operator Response: Report this error to your system

system programmer.

programmer.

System Programmer Response: If alternate logging is

System Programmer Response: Take corrective action,

to be enabled, ensure the operator is requested to start

if necessary, based on the function and return code

the application server with LOGMODE=L.

received.

The description of the function and the explanation of

ARI4100I

TCP/IP service initialized from

the return code reported by this message can be found

{DBNAME DIRECTORY/TCPPORT/WELL

in the VSE/ESA Version 2 Release 3 Enhancement manual.

KNOWN PORT}. TCP/IP Port is

port-number.

ARI4109E While trying to process an external

Explanation: The TCP/IP service was successfully

security manager request through the

initialized by the application server.

RACROUTE macro, an error occurred.

TCP/IP service can be initialized from the Dbname

Directory, TCPPORT, or the Well Known Port, 446. If it

Function = function

is Dbname Directory, then the port number was

SAF Return Code = X’return code’

determined by a lookup in the Dbname Directory. If it

ESM Return Code = X’return code’

is TCPPORT, then the port number was taken from the

ESM Reason Code = X’reason code’

TCPPORT parameter specified during database startup

Explanation: The application server issued the

or in the START TCPIP operator command. If it is

RACROUTE macro to authenticate a userid. The

WELL KNOWN PORT, it means TCPPORT is not

RACROUTE macro responded with the information

specified either during startup or in the Dbname

described in the message.

Directory. The predefined well known port number,

446, is used.

System Action: Authentication of the userid failed.

Messages and Codes

DB2 Server for VSE Control Messages -ARI4000-ARI4599

For REQUEST=VERIFY, SECTYPE remains at ESM and

ARI4113I

TCP/IP support for the database

processing continues. For REQUEST=STAT, SECTYPE is

manager was never enabled. Start

changed to DB2.

request is ignored.

System Programmer Response: Correct the problem

Explanation: The START TCPIP operator command

with the external security manager. For more

was issued while the TCP/IP support initialization

information about the return codes and reason codes,

process was never invoked during application server

see Workbook for External Security Managers/Resource

startup. The restart process is relying on the TCP/IP

Managers.

agent structure previously created during application

server initialization. Without the agent structure, restart

ARI4110E ESM function ESM function failed.

process cannot be performed. This is the case where

Return code = return code

either TCPPORT = 0 was specified or RMTUSERS = 0

was specified.

Explanation: The application server was performing

function ESM function and encountered an error. return

System Action: The system continues, the application

code indicates the error that occurred.

server ignores the restart TCP/IP request. The

application server will only be able to accept SNA

System Action: Processing continues.

connections.

System Programmer Response: Report this error to

Operator Response: Report this error to your system

the designated support group for your installation.

programmer.

System Programmer Response: Restart the application

ARI4111I

Unable to find host-name in IPINITnn

server by specifying a valid TCPPORT parameter if

file.

TCP/IP support is desired.

Explanation: The application server attempted to

search the IPINITnn file for the value identified by

ARI4114I

TCP/IP support for the database

host-name.

manager is still active. Start request is

System Action: The system continues, the application

ignored.

server will discontinue TCP/IP Only initialization. The

Explanation: The START TCPIP operator command

application server will only be able to accept SNA

was issued, but the TCP/IP support for the application

connections.

server is still active.

Programmer response: Report this message to your

System Action: The system continues, the application

system programmer.

server ignores the restart TCP/IP request.

System Programmer Response: Determine if an entry

Operator Response: Issue the START TCPIP command

for host-name should be defined to the IPINITnn file.

only after TCP/IP support for the application server

Add the entry if it is required.

went down abnormally.

ARI4112I

TCPPORT nnnnn is invalid. It must be

ARI4115I

TCP/IP support for the database server

in the range from n1 to n2.

is disabled.

Explanation: An invalid port number was specified in

Explanation: TCP/IP support for the application

the START TCPIP TCPPORT operator command, nnnnn

server is disabled. This could be the result of a severe

is the port number specified.

error detected during the execution of a TCP/IP

n1 is the lower limit (or minimum) for the correct

function. The listener socket of the application server is

parameter value.

closed and no new TCP/IP connect request can be

n2 is the upper limit (or maximum) for the correct

accepted. The application server will only be able to

parameter value.

accept SNA connections.

System Action: The system continues, the application

For the error situation encountered, there should be a

server ignores the restart TCP/IP request. The

preceding message that describes the error. Refer to the

application server will only be able to accept SNA

corresponding message and take action accordingly.

connections.

System Action: The system continues, but no TCP/IP

Operator Response: Retry the command by specifying

support is available.

a valid port number.

Operator Response: Report this error to your system

programmer.

System Programmer Response: Take correction action,

if necessary, based on the function and return code

received in the preceding error message. Once the error

Chapter 6. ARI4000-ARI4599 DB2 Server for VSE Control Messages

DB2 Server for VSE Control Messages -ARI4000-ARI4599

condition is resolved, issue the START TCPIP operator

manager will attempt to restart it automatically.

command to restart TCP/IP support if TCP/IP

Operator Response: Automatic restart can be disabled

communication for the application server is desired.

by issuing the operator command SET TCPRETRY N.

ARI4116I

TCP/IP automatic restart begins.

ARI4120I

Maximum number of automatic TCP/IP

Attempt = number.

restart attempts has been reached.

Explanation: The database manager has detected that

Explanation: The maximum number of automatic

TCP/IP support has been disabled and is attempting to

TCP/IP restart attempts, as defined by the TCPMAXRT

re-enable TCP/IP support. Number indicates how many

initialization parameter, has been reached.

times the database manager has attempted to re-enable

TCP/IP support. Refer to DB2 Server for VSE System

System Action: The database manager disables

Administration for information on the strategy used by

automatic TCP/IP restart and sets the value of

the database manager to re-enable TCP/IP support.

TCPRETRY to N.

System Action: The system attempts to re-enable

Operator Response: Automatic restart can be enabled

TCP/IP support. All other processing continues.

again by issuing the operator command SET

TCPRETRY Y. If the maximum number of attempts is

Operator Response: Automatic restart can be disabled

too small, it can be changed by issuing the operator

by issuing the operator command SET TCPRETRY N.

command SET TCPMAXRT n.

ARI4117E TCP/IP automatic restart attempt number

ARI4121E

TCP/IP restart is in progress. The SET

failed. Attempts attempts remaining.

option command is not allowed at this

Explanation: The database manager has attempted to

time.

re-enable TCP/IP support. The attempt was

Explanation: TCP/IP restart is in progress and an

unsuccessful. Number indicates how many times the

attempt was made to change the value of TCPRETRY

database manager has attempted to re-enable TCP/IP

or TCPMAXRT. These values cannot be changed when

support. Attempts indicates how many more times the

TCP/IP restart is in progress.

database manager will attempt to re-enable TCP/IP

support. It is calculated as TCPMAXRT minus number.

System Action: The SET command is ignored. The

database manager continues with the TCP/IP restart

System Action: The system will continue to attempt to

that is already in progress.

re-enable TCP/IP support until support has been

re-enabled, or the maximum number of attempts has

Operator Response: The SET command can be

been reached, or the operator disables the automatic

entered again when the TCP/IP restart attempt ends.

restart support by issuing the command SET

TCPRETRY N. All other processing continues.

ARI4122I

TCP/IP automatic restart disabled and

Operator Response: Automatic restart can be disabled

cannot be enabled.

by issuing the operator command SET TCPRETRY N.

Explanation: The database manager disabled TCP/IP

The maximum number of attempts can be increased by

automatic restart because of a system error. The SET

issuing the operator command SET TCPMAXRT n.

TCPRETRY Y command cannot be used to enable

TCP/IP automatic restart.

ARI4118I

The TCP/IP automatic restart is

System Action: The system continues.

disabled.

Operator Response: TCP/IP can be re-enabled

Explanation: The database manager or the operator

manually with the START TCPIP operator command.

has disabled automatic restart of TCP/IP support.

Automatic TCP/IP restart can be enabled by stopping

System Action: The system processing continues. If

the database manager with the SQLEND command and

TCP/IP support becomes disabled, it must be restarted

starting it again.

manually.

Operator Response: Automatic restart can be enabled

ARI4123E TCP/IP support has used all available

by issuing the operator command SET TCPRETRY Y.

sockets and cannot be started.

Explanation: TCP/IP support has been disabled

ARI4119I

The TCP/IP automatic restart is enabled.

because the VSE limit of 8000 sockets was reached. The

START TCPIP command and automatic TCP/IP restart

Explanation: The database manager or the operator

cannot be used to re-enable TCP/IP support.

has enabled automatic restart of TCP/IP support.

System Action: The system continues without TCP/IP

System Action: The system processing continues. If

support available.

TCP/IP support becomes disabled, the database

100

Messages and Codes

DB2 Server for VSE Control Messages -ARI4000-ARI4599

Operator Response: Stop the database manager with

Explanation: The stored procedure referenced has

the SQLEND command and restart it to enable TCP/IP

been started successfully.

support.

System Action: Processing of the operator command

has completed.

ARI4124I

TCP/IP service input parameters

ARI4152E FORMAT 1

<input parameter 1> = value_1

START PROC failed for proc-name.

<input parameter 2> = value_2

Reason Code reason-code.

FORMAT 2

<input parameter n> = value_n

START PROC failed for proc-name for

Explanation: This message is an extension of ARI4103I

AUTHID authid.

and lists the input parameters for a TCP/IP service.

Reason Code reason-code.

The number and value of the input parameters varies

Explanation: Processing of the command failed.

depending on which TCP/IP service caused the error.

Possible reason codes are:

An example of the message’s appearance (using the

SOCKET TCP/IP service) would be:

The procedure is not found.

ARI4124I TCP/IP service input parameters

A wildcard is used improperly in the

TCP/IP blocking = x

procedure name.

The TCP/IP service causing the error is indicated by

A wildcard is found in the authid.

message ARI4103I which is displayed immediately

The procedure name specified is a keyword.

before this message.

The authid specified is a keyword.

System Action: The system continues.

System Action: The operator command is not

Operator Response: Report this error to your system

processed.

programmer.

Operator Response: Correct the error and issue the

System Programmer Response: Take corrective action,

command again.

if necessary, based on the function input.

ARI4153I

FORMAT 1

ARI4150E Stored Procedure proc-name failed.

Stored procedure proc-name is

Stored procedure server

already started.

serv-name returned the following

FORMAT 2

information:

Stored procedure proc-name for

Stored Procedure SQLCODE = sql-code

AUTHID authid is already

Module and failure point = failure-point

started.

CEEPIPI return code = ce-rc

LE enclave return code = le-rc

Explanation: The stored procedure referenced was

LE enclave reason code = le-reason-code

started by a previous START PROC command.

Explanation: An error occurred while executing a

System Action: Processing of the operator command

CALL request. The stored procedure server server-name

has ended.

terminated abnormally. Only error information returned

by the stored procedure server is displayed. User will

ARI4154I

FORMAT 1

receive SQLCODE -471 as a result of the same failure.

Stored procedure proc-name is not

System Action: Processing of the SQL statement has

found.

ended.

FORMAT 2

Stored procedure proc-name for

System Programmer Response: Use error information

AUTHID authid is not

displayed, and SQLCODE -471 reason code received by

found.

user to determine the cause of the problem.

FORMAT 3

Wildcard is used improperly in stored

ARI4151I

FORMAT 1

procedure name proc-name.

START PROC successful for

FORMAT 4

proc-name.

Wildcard is used improperly in

FORMAT 2

AUTHID authid for stored procedure

START PROC successful for

proc-name.

proc-name for AUTHID authid.

FORMAT 5

Stored procedure

Chapter 6. ARI4000-ARI4599 DB2 Server for VSE Control Messages

101

DB2 Server for VSE Control Messages -ARI4000-ARI4599

name proc-name is

ARI4157E FORMAT 1

a keyword.

STOP PROC failed for proc-name.

FORMAT 6

Reason code reason-code.

AUTHID authid for

FORMAT 2

stored procedure

STOP PROC failed for proc-name

name proc-name is a keyword.

for AUTHID authid.

FORMAT 7

Reason code reason-code.

ACTION action specified is invalid.

Only QUEUE and REJECT are valid.

Explanation: Processing of the command failed.

Possible reason codes are:

Explanation: This message provides information about

an error that occurred when an operator command was

The procedure is not found.

issued. It indicates that either

A wildcard is used improperly in the

1. The procedure specified was not found in the

procedure name.

cached information from SYSTEM.SYSROUTINES

2. Invalid information was entered.

A wildcard is found in authid.

System Action: Processing of the operator command

The procedure name specified is a keyword.

has ended.

The authid specified is a keyword.

Operator Response: Correct the source of the error

Action specified is invalid. Only QUEUE and

and issue the command again.

REJECT are valid.

System Action: Processing of the operator command

ARI4155I

FORMAT 1

has ended.

STOP PROC successful for

proc-name.

Operator Response: Correct the error and issue the

FORMAT 2

command again.

STOP PROC successful for proc-name

for AUTHID authid.

ARI4158E Error in operator command oper-cmd.

Explanation: The stored procedure referenced has

Reason code reason-code.

been stopped successfully.

Explanation: Processing of the command failed.

System Action: Processing of the operator command

Possible reason codes are:

has completed.

The stored procedure is not found.

ARI4156I

FORMAT 1

A wildcard is used improperly in the

procedure name.

New calls to stored procedure

proc-name will

A wildcard is found in authid.

be action-code.

FORMAT 2

The procedure name specified is a keyword.

New calls to stored procedure

The authid specified is a keyword.

proc-name with AUTHID authid

will be action-code.

Stored procedure server is not defined.

Explanation: This message is displayed when a stored

Stored procedure server group is not defined.

procedure is stopped. It indicates how subsequent

A wildcard is used improperly in the stored

CALLs to that procedure will be handled.

procedure server name.

proc-name

A wildcard is used improperly in the stored

The name of the stored procedure

procedure server group name.

authid The authorization ID associated with the

The stored procedure server name specified is

stored procedure

a keyword.

action-code

The stored procedure server group name

Either QUEUED or REJECTED

specified is a keyword.

System Action: The STOP PROC command has

completed successfully for the procedure indicated.

oper-cmd The operator command issued.

System Action: Processing of the operator command

has ended.

102

Messages and Codes

DB2 Server for VSE Control Messages -ARI4000-ARI4599

Operator Response: Correct the error and issue the

FORMAT 4

command again.

Wildcard is used improperly in stored

procedure server group name

serv-group-name.

ARI4159I

FORMAT 1

FORMAT 5

Stored procedure proc-name is

Stored procedure server name

already stopped.

serv-name is a keyword.

FORMAT 2

FORMAT 6

Stored procedure proc-name for

Stored procedure server group name

AUTHID authid

serv-group-name is a keyword.

is already stopped.

Explanation: This message provides information about

Explanation: The stored procedure referenced was

an error that occurred when an operator command was

stopped by a previous STOP PROC command.

issued. It indicates that either

System Action: Processing of the operator command

1. The stored procedure server specified was not

continues.

found in the cached information from

SYSTEM.SYSPSERVERS

2. Invalid information was entered.

ARI4160E Operator command oper-cmd has

insufficient number of input parameters.

System Action: Processing of the operator command

terminates.

Explanation: The command entered did not use the

correct syntax.

Operator Response: Correct the error and issue the

command again.

oper-cmd The operator command issued.

Operator Response: Refer to the DB2 Server for VSE &

ARI4164I

Stored procedure server serv-name is

VM Operation manual for the syntax diagram for the

already started.

command.

Explanation: The stored procedure server serv-name

was started by a previous START PSERVER command.

ARI4161E Operator command oper-cmd has too

many input parameters.

System Action: Processing of the operator command

has ended.

Explanation: The command entered did not use the

correct syntax.

ARI4165I

START PSERVER cannot be processed

oper-cmd The operator command issued.

for server-name because it has a status of

System Action: Processing of the operator command

status.

has terminated.

Explanation: Only a stored procedure server that is

Operator Response: Refer to the DB2 Server for VSE &

currently stopped can be started. Possible values for

VM Operation manual for the syntax diagram for the

status are:

command.

v STARTING

v STOPPING

ARI4162I

Stored procedure server serv-name has

System Action: Processing of the operator command

been started.

terminates.

Explanation: The stored procedure server serv-name is

Operator Response:

able to accept SQL CALL statements to run stored

v If the current status is STARTING, no action is

procedures associated with this server.

necessary.

System Action: Operator command complete

v If the current status is STOPPING, the stored

successfully. Processing continues.

procedure server is waiting for a stored procedure to

complete. When the stored procedure finishes, the

stored procedure server will be terminate, and then

ARI4163I

FORMAT 1

the START PSERVER command can be issued for

Stored procedure server

that stored procedure server.

serv-name is not defined.

If you need to stop and start the stored procedure

FORMAT 2

immediately, you can use the STOP PSERVER

Stored procedure server group

command with the QUICK option, and then issue

serv-group-name is not defined.

the START PSERVER command.

FORMAT 3

Wildcard is used improperly in stored

procedure server name serv-name.

Chapter 6. ARI4000-ARI4599 DB2 Server for VSE Control Messages

103

DB2 Server for VSE Control Messages -ARI4000-ARI4599

Wildcard is used improperly in stored

ARI4166I

FORMAT 1

procedure server name serv-name.

Unable to acquire storage for a

pseudoagent for server server-name.

Wildcard is used improperly in stored

FORMAT 2

procedure server group name serv-group-name.

Unable to acquire storage for an

Stored procedure server name serv-name

XPCC control

specified is a keyword.

block for server

server-name.

Stored procedure server group name

serv-group-name specified is a keyword.

Explanation: In VM, when START PSERVER is issued,

the database manager allocates the pseudoagent

System Action: Processing of the operator command

structure to be used for the connection between the

has ended.

database manager and the stored procedure server. In

Operator Response: This message is preceded by an

VSE, when START PSERVER is issued, the database

informational message that indicates the reason for the

manager allocates an XPCC control block to be used for

error. Follow the instructions given in the Operator

the connection between the database manager and the

Response for the informational message.

stored procedure server. In either case, if storage for the

structure is not available, the START PSERVER

command cannot complete.

ARI4168I

START PSERVER operator command

timed out.

System Action: Processing of the operator command

terminates.

Explanation: The START PSERVER command did not

complete in the amount of time specified by the

Operator Response: Try the command again later.

initialization parameter PTIMEOUT. Either:

Since storage utilization on the database manager

v the PTIMEOUT value is too short

varies depending on the number of active agents and

v the database manager was not able to connect to the

their activities, storage may become available, enabling

stored procedure server

the command to complete.

System Action: Processing of the operator command

Database Administrator Action:

terminates.

Consider whether the amount of storage available to

System Programmer Response: If the connection

the database manager needs to be increased.

failed, use the diagnostic information displayed to

determine the source of the problem and correct the

ARI4167E FORMAT 1

error.

START PSERVER for serv-name

Database Administrator Action:

failed.

Reason code reason-code.

If no error occurred during the attempt to connect to

FORMAT 2

the stored procedure server, consider whether the

START PSERVER GROUP for

PTIMEOUT value should be increased.

serv-group-name failed.

Reason code reason-code.

ARI4169E FORMAT 1

Explanation: Processing of the command failed.

Stored Procedure proc-name has

Possible reason codes are:

exceeded the maximum number of

abends allowed. It has been stopped

Stored procedure server serv-name is not

successfully. New calls will be

defined.

rejected.

Stored procedure server group serv-group-name

FORMAT 2

is not defined.

Stored Procedure proc-name for

AUTHID authid has exceeded the

The database manager is not able to acquire a

maximum number of abends allowed.

pseudoagent for the stored procedure server.

It has been stopped successfully.

The database manager is not able to allocate

New calls will be rejected.

an XPCC control block for the stored

Explanation: A stored procedure has exceeded the

procedure server.

number of allowed abnormal terminations as defined

START PSERVER cannot be issued for a stored

by PROCMXAB init parameter.

procedure server that has a status of

System Action: Processing of the SQL statement has

STARTING.

ended.

START PSERVER cannot be issued for a stored

Operator Response: Issue START PROC command to

procedure server that has a status of

restart the procedure.

STOPPING.

104

Messages and Codes

DB2 Server for VSE Control Messages -ARI4000-ARI4599

Programmer response: Determine the reason for

proc-name with AUTHID

stored procedure abend.

authid to finish.

Explanation: The STOP PSERVER command was

ARI4170E FORMAT 1

issued for a stored procedure server that is currently

Cannot action stored procedure

running a stored procedure.

proc-name The cache structure

System Action: When the stored procedure finishes,

is currently being updated by another

the database manager will stop the stored procedure

agent.

server.

FORMAT 2

Cannot action stored procedure

Operator Response: If you must stop the stored

proc-name for AUTHID authid

procedure server immediately, issue the STOP

The cache structure is currently

PSERVER command again, specifying the QUICK

being updated by

option.

another agent.

FORMAT 3

ARI4174E FORMAT 1

Cannot action stored procedure server

STOP PSERVER for serv-name failed.

serv-name

Reason code reason-code.

The cache structure is currently

FORMAT 2

being updated by another agent.

STOP PSERVER GROUP for

Explanation: The cache structure is currently being

serv-group-name failed.

updated by another agent.

Reason code reason-code.

System Action: Processing of the operator command

Explanation: Processing of the command failed.

has ended.

Possible reason codes are:

Operator Response: Issue the command again at a

The definition of the stored procedure server

later time

serv-name is not found.

The definition of the stored procedure server

ARI4171I

FORMAT 1

group serv-group-name is not found.

Stored procedure server serv-name

A wildcard is used improperly in stored

has been stopped.

procedure server name serv-name.

It can be implicitly started.

FORMAT 2

A wildcard is used improperly in stored

Stored procedure server serv-name

procedure server group name serv-group-name.

has been stopped. It cannot be

The stored procedure server name serv-name

implicitly started.

specified is a keyword.

Explanation: Stored procedure server serv-name has

The stored procedure server group name

been deactivated as requested by a STOP PSERVER or

serv-group-name specified is a keyword.

SQLEND command.

System Action: Processing of the operator command

has ended.

is complete.

Operator Response: Correct the error and issue the

command again.

ARI4172I

Stored procedure server serv-name is

already stopped.

ARI4175I

The cach-name cache is loaded at

Explanation: The stored procedure server serv-name

load-address.

was stopped by a previous STOP PSERVER command.

Explanation: cach-name is the name of the cache

System Action: Processing of the operator command

loaded by the database manager.

terminates.

load-address is the storage address (expressed in

hexadecimal) where the cache was loaded.

ARI4173I

FORMAT 1

Stored procedure server serv-name is

System Action: Processing continues.

waiting for stored procedure

proc-name to finish.

System Programmer Response: You may want to note

FORMAT 2

the address for use in any potential problem

Stored procedure server serv-name is

determination.

waiting for stored procedure

Chapter 6. ARI4000-ARI4599 DB2 Server for VSE Control Messages

105

Chapter 7. ARI0500-ARI0511 SQL Messages

The SQL messages are associated with the

ARI0502I

Following SQL warning conditions

SQLCODEs. These messages provide general

encountered: {truncation |

information; they do not give detailed

NULLIGNORED | mismatch |

descriptions of the cause of the error. The

NULLWHERE | performance | implicit

SQLCODE appears in message ARI0505I. The text

rollback | adjustment | ineligible | no

following messages ARI0501 and ARI0503 is the

storage | can’t fit 2}.

SQLCODE descriptive text. To find the

Explanation: Each of the SQL processing warning

explanation and related action, refer to

condition keywords is directly associated with an

Chapter 18, “SQLCODEs,” on page 237 of this

SQLCA SQLWARN indicator. The applicable

manual.

SQLWARN indicator is identified in the explanation of

each keyword.

ARI0500I

SQL processing was successful.

TRUNCATION (SQLWARN1) - one or more of the

requested data items was truncated due to insufficient

Explanation: The processing of the SQL statement was

space in the declared program variable. By examining

successful. This message occurs only when SQLCODE

the null indicator variables of the data items returned,

= 0 and no SQL warning conditions occurred during

you can find which data items were truncated. A

SQL statement processing. This message is followed by

positive value in the null indicator denotes actual

message ARI0505I, which indicates the SQLCODE and

length before truncation.

ROWCOUNT information.

Set to W, if the value of a string column was truncated

System Action: Normal completion.

when it was assigned to a host variable.

Set to Z, if mixed character data was truncated and the

ARI0501I

An SQL warning has occurred.

resulting data does not follow the proper rules

SQLCODE descriptive text

regarding mixed data.

Explanation: This message occurs when either:

Set to Z, if both W and Z truncations occur.

v The SQLCODE is greater than zero, or

NULLIGNORED (SQLWARN2) - set to W, if null

v The SQLCODE is zero and SQL warning conditions

values were ignored in the computation of a column

occurred during SQL statement processing, or

function such as AVG, SUM, MAX, MIN, or COUNT.

v The SQLCODE is negative, but the preprocessor is

treating it as a warning at preprocessing time.

MISMATCH (SQLWARN3) - set to W, if the number of

target variables in the INTO clause is less than the

number of items in the SELECT list.

This message is followed by message ARI0505I, which

provides the SQLCODE and ROWCOUNT information,

If the number of target variables in the INTO clause is

and in the first two conditions, the ARI0502I message

greater than the number of items in the SELECT list,

that indicates the specific warning conditions.

then the warning flag will not be set.

NULLWHERE (SQLWARN4) - set to W, if an UPDATE

The SQLCODE descriptive text describes the SQLCODE

or DELETE command has been used without a WHERE

error condition.

clause. The user should verify that the update or

System Action: SQL statement processing completed

deletion was intended unconditionally on the entire

successfully.

table.

User Response: For an SQLCODE greater than zero,

PERFORMANCE (SQLWARN5) - set to W, if a

take action based upon the SQLCODE descriptive text.

WHERE clause, represented internally by one or more

For the SQLCODE of zero, take action defined for

search arguments, associated with a SELECT statement

message ARI0502I. For an SQL code of less than zero,

has exceeded a DB2 Server for VSE internal limitation.

correct the problem described in the SQLCODE

This means that a performance degradation will result

descriptive text before the application program is

because the database manager will not internally

executed.

convert eligible predicates to search arguments. The

database manager may still choose to use indexes for

eligible predicates, but if not, degradation may further

be increased since a DBSPACE scan would be used to

retrieve query data. Decreasing the number of

predicates, such as by removing unnecessary conditions

107

SQL Messages - ARI0500-ARI0511

which may exist in the WHERE clause of the SELECT

ARI0504I

SQLERRP: pppppppp SQLERRD1: nnn

statement, may alleviate this condition.

SQLERRD2: nnn.

IMPLICIT ROLLBACK (SQLWARN6) - the logical unit

Explanation:

of work is no longer active. It has been rolled back due

to a system failure.

SQLERRP

RDS module name, preprocessor

module name, Resource Adapter

Set to W, when the database manager is forced to

module name, or RUN-TIME that set

terminate a logical unit of work.

either the warning flag or the

Set to S, when the database manager issues a severe

SQLCODE.

RUN-TIME means that an error

ADJUSTMENT (SQLWARN7) - set to W, when an

occurred while a DB2 Server for VSE

adjustment has been made to a derived date or

data manipulation statement was

timestamp value for the last day of the month.

being executed.

Set to Z, when the divisor or dividend of a DECIMAL

If an error occurs while the statement

divide operation requires readjustment in order to

is being preprocessed, the RDS

complete the divide operation. This may affect the

module name is displayed. If the

accuracy of the quotient (result).

error occurs in the run-time access

generator (when the statement is

INELIGIBLE (SQLWARN8) - set to W, if the statement

being executed), the message text

is disqualified for blocking for reasons other than

may contain either the RDS module

storage, such as use of long fields.

name or the literal string RUN-TIME.

Set to Z, if a character that could not be converted was

The RUN-TIME message is issued

replaced with a substitute character.

when the error is one that cannot be

trapped by the access generator

NO STORAGE (SQLWARN9) - set to W, if there was

run-time modules and is handled by

insufficient storage for blocking and therefore blocking

the DB2 Server for VSE abend

is cancelled for the subject cursor.

handler. For example, division by

zero or an arithmetic overflow.

CAN’T FIT 2 (SQLWARNA) - set to W, if blocking

factor of at least two rows cannot be maintained and

SQLERRD1

Secondary return code value set by

therefore blocking is cancelled for the subject cursor.

module pppppppp. This value, along

with the module name, can be used

System Action: Normal completion; SQL statement

by persons responsible for locating

processed successfully.

problems within the database

User Response: Take appropriate action based upon

manager itself. This information is not

warning condition.

usually of interest to others. However,

if the SQLCODE is -314, the

SQLERRD1 value denotes the reason

ARI0503E An SQL error has occurred. SQLCODE

why a host variable was incorrectly

descriptive text

declared. Refer to SQLCODE -314 for

Explanation: Processing of the SQL statement was not

more information.

successful. This message is followed by message

SQLERRD2

Return code value set by DBSS or the

ARI0505I, which provides the SQLCODE and

Resource Adapter. The definition of

ROWCOUNT information, and message ARI0504I,

the Resource Adapter return codes

which indicates the condition that caused the error

can be found under Chapter 20, “DB2

message.

Server for VSE Reason Codes,” on

SQLCODE descriptive text is derived from SQLCODE

page 355. See Chapter 17, “DBSS

descriptive text modules. Multiple lines of SQLCODE

Return Codes,” on page 231 for

descriptive text may appear.

definitions of the DBSS return codes.

System Action: SQL statement was not processed.

This message follows messages ARI0503E (or

User Response: Take action based on the SQLCODE

ARI0533E) and ARI0505I.

descriptive text. For additional information on the

System Action: See System Action for the associated

specific problem, refer to the appropriate SQLCODE in

ARI0503E (or ARI0533E) message.

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

use the SQLCODE number as the topic for the ISQL

User Response: See User Response for the associated

HELP command (for example: enter HELP -105).

ARI0503E (or ARI0533E) message.

108

Messages and Codes

SQL Messages - ARI0500-ARI0511

System Action: Processing of the command continues.

ARI0505I

SQLCODE = nnn [SQLSTATE = nnnnn]

ROWCOUNT = nnn

ARI0511E SQL message formatter error. Reason

Explanation: This message follows messages ARI0500I,

Code = nn.

ARI0501I, and ARI0503E (or ARI0533E). In the case of

DELETE statements, it only appears when the number

Explanation: The SQL Message Formatter Routine has

of dependent rows affected is greater than zero.

encountered incorrect parameter values being passed to

it by some system internal calling routine.

SQLCODE= nnn:

REASON CODE = nn:

nnn < 0

SQL statement processing has not

been completed because an error

nn = 10

occurred.

The MSGID SQLTEXT flag is set ON but the

SQLMSGNO field does not contain either of

nnn = 0

SQL statement processing completed.

the valid values, 501 or 503.

Warning may or may not indicate an

error.

nn = 20

The MSGID SQLTEXT flag is set OFF with one

nnn > 0

This indicates a warning. SQL

or more of the MSGID fields nonzero and

statement processing completed but

either the MSGNO field is not equal to the

one or more unusual conditions

SQLMSGNO field, or the SEQNO field is not

occurred.

greater than 1.

The text following message ARI0501I or ARI0503E is

System Action: Processing of the current SQL

the SQLCODE descriptive text. To find the explanation

statement has ended. A return code value of 20 is

and related action, either refer to the section

returned to the calling routine in register 15.

Chapter 18, “SQLCODEs,” on page 237 in this manual

User Response: Notify your system programmer.

or enter a HELP command for the SQLCODE indicated.

System Programmer Response: Make a record of

SQLSTATE=nnnnn, where nnnnn is a 5-digit number

what went wrong and contact the designated support

associated with an SQLCODE. See Chapter 19,

group for your installation.

“SQLSTATEs,” on page 335 for a list of SQLSTATE

values.

Note: The application server does not issue an

SQLSTATE value if the error occurs during DB2

Server for VSE preprocessing.

ROWCOUNT = nnn, where nnn is a value that

indicates:

UPDATE

the number of rows updated.

INSERT

the number of rows inserted.

DELETE

the number of rows deleted.

For any other SQL statement or catalog migration, the

value of ROWCOUNT is not applicable.

System Action: See System Action for the associated

SQLCODE.

User Response: See User Response for the associated

SQLCODE.

ARI0506I

Dependent rows affected = n.

Explanation: This message appears only for DELETE

statements when the number of dependent rows

affected is greater than zero. The command caused

changes to dependent tables because of referential

constraints with a rule of SET NULL or CASCADE. The

number (n) of dependent rows affected is reported.

Chapter 7. ARI0500-ARI0511 SQL Messages

109

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