> # DB2 Application Support Package Messages

> This section contains z/OS log messages generated by DB2ASP modules. DB2ASP handles the server DB2 access.

> VAID000I | Successful connection to DB2(ssss).
> | Severity: | Information
> | Explanation: | SequeLink for z/OS is connected to DB2 address space "ssss" (DB2 subsystem ID) and ready to accept DB2 session requests.
> | System action: | None.
> | User response: | None.
> VAID001I | DB2(ssid) initialization completed, yyyyy attachment.
> | Severity: | Information
> | Explanation: | Initialization to DB2 subsystem completed using either CAF or RRSAF attachment.
> | System action: | None.
> | User response: | None.
> VAID003I | DB2 (ifid) is now active.
> | Severity: | Information
> | Explanation: | DB2ASP has detected that the previously inactive DB2 system ifid (DB2 interface ID) has now become active.
> | System action: | The SequeLink for z/OS DB2 environment is initialized.
> | User response: | DB2 session requests will now be permitted.
> VAID004I | DB2 (ifid) is terminating.
> | Severity: | Information
> | Explanation: | DB2ASP has detected that DB2 ifid is about to terminate.
> | System action: | All current DB2 sessions will be aborted and DB2ASP will proceed according to the SYSINI DB2STOPOPT specification.
> | User response: | None.
> VAID005E | Connection to DB2(ssss) failed. R15=X'rc'. R0=X'reason'.
> | Severity: | Error
> | Explanation: | Connection to DB2 address space "ssss" failed. "rc" and "reason" are the return/reason codes for the failure.
> | System action: | If the error is "DB2 inactive", DB2ASP will enter a dormant state and wait for DB2 to come back up. Any other error causes DB2ASP to terminate with RC=08. Note that this message will always be issued when DB2ASP has detected that DB2 has gone inactive, and the user wants to maintain the connection to the DB2 address space (DB2STOPOPT is "LEAVE").
> | User response: | Situation-dependent.
> VAID006I | Waiting for DB2(ssss) to become active.
> | Severity: | Information
> | Explanation: | DB2ASP is waiting for DB2 "ssss" to become active. Issued after message VAID005E when the error was "DB2 inactive".
> | System action: | DB2ASP enters a dormant state and waits for DB2 "ssss" to become active.
> | User response: | Start-up DB2 address space "ssss".
> VAID007E | Disconnection to DB2(ssss) failed. R15=X'rc'.R0=X'reason'.
> | Severity: | Error
> | Explanation: | Disconnection from DB2 address space "ssss" failed. "rc" and "reason" are the return/reason codes for the failure.
> | System action: | DB2ASP continues, but this may be a serious error.
> | User response: | Contact DataDirect Technologies technical support.
> VAID008E | Datamodel - aaaaaaaaaaaaaaaa syntax error.
> | Severity: | Error
> | Explanation: | Required Datamodel attribute for this DB2 root task is missing or has a syntax error - aaaaaaaaaa describes the attribute.
> | System action: | No attachment is set up to the corresponding DB2 subsystem.
> | User response: | Correct or supply missing attribute in the DataModel and restart the server.
> VAID010E | Abnormal termination detected in DB2 (ifid) thread manager- DB2ASP terminating.
> | Severity: | Error
> | Explanation: | The DB2ASP thread manager (VAICDB2T) of DB2 interface ifid abnormally terminated.
> | System action: | DB2ASP terminates with RC=08.
> | User response: | Contact DataDirect Technologies technical support.
> VAID011E | Setup ContextCleanup Problem - ttttttttttttttt.
> | Severity: | Error
> | Explanation: | Setup for automatic cleanup of RRS context(s) failed for reason ttttttttttttttt, where ttttttttttttttt is either 'invalid EntryPoint VAICRRSM' or 'SET_TIM routine failed'.
> | System action: | Initialization continues; no ContextCleanup will be done.
> | User response: | Contact DataDirect Technologies technical support.
> VAID012E | Syntax error/invalid value in DB2ASP command.
> | Severity: | Error
> | Explanation: | DB2ASP operator request contained a syntax error or the parameter value was rejected.
> | System action: | Self-explanatory.
> | User response: | Correct the command and re-enter.
> VAID014E | Ttttttttt - Error detected in VAICDB2I - <error description>
> | Severity: | Error
> | Explanation: | This message is an internal error. <error description> shows one of the errors: `"No valid TACBUID2"` `"No DB2Plan passed"` `"No DBWA for Service"` `"Wrong DB2attachment"` `"DB2 not active"`
> | System action: | None.
> | User response: | If `DB2 not active`, start DB2. For all other cases, this is an internal error. Contact DataDirect Technologies technical support.
> VAID015E | Loadmodule VAICRRSM could not be loaded.
> | Severity: | Error
> | Explanation: | The Loadmodule fetch failed.
> | System action: | Initialization continues; no ContextCleanup will be done.
> | User response: | Check that loadmodule VAICRRSM is installed in steplib.
> VAID016W | Subsystem name xxxx found in DSNHDECP module, expected to find Subsystem yyyy.
> | Severity: | Warning
> | Explanation: | SequeLink detected a DB2 SubsystemName mismatch in DSNHDECP module.
> | System action: | SequeLink Server continues startup.
> | User response: | Make sure the correct SDSNEXIT library for yyyy DB2 subsystem is concatenated to DB2 Interface DD statement. Change MVSDB2ExitLibrary attribute in Configuration file and regenerate SequeLink Server JCL.
> VAID020T | Tttttttt - DB2SQL - ssssssssssssssssssssss to be executed
> | Severity: | Trace
> | Explanation: | This messages shows which DB2 StatementType is about to be passed to DB2.
> | System action: | None.
> | User response: | None.
> VAID021E | Tttttttt - Abend in DB2 while an ssssssssssssssssssss StatementType is executing.
> | Severity: | Error
> | Explanation: | SequeLink Server trapped an abend in DB2. This error shows the DB2 StatementType active in DB2 when this event happened onThrdid Tttttttt.
> | System action: | None.
> | User response: | See the Reason and AbendCode in the VAID046E message for more information.
> VAID024I, VAID025I | UserID Thread# Service Plan Net Stat SQLcalls
> | Severity: | Information
> | Explanation: | The following information is displayed when a DB2 STATUS command is issued: UserID-client userid Thread# -thread number Service-service requested by client Plan-DB2 plan being used Net-network platform (TCP or APPC) Stat-thread status OPEN-thread is open. DISC-thread is disconnected. CLOS-thread is closed. RLSE-thread is eligible for release (reuse). WAIT-thread is waiting for an available thread. SQLcalls-number of SQL calls is issued by the session. NOTE: This field will always be OPEN if thread management is inactive.
> VAID027I | Connection to DB2(ssss) is ccccc, DB2 STOPOPT is ooooo.
> | Severity: | Information
> | Explanation: | This message is displayed when a DB2 STATUS command is issued. ssss - is the subsystem ID of the DB2 address space. ccccc - is either ACTIV or INACT. ooooo - is the DB2 stop option specified in the SYSINI.
> | System action: | None.
> | User response: | None.
> VAID028I | Already connected to DB2-request ignored.
> | Severity: | Information
> | Explanation: | An operator issued a DB2 CONNECT command, but SequeLink for z/OS was already connected to the DB2 address space.
> | System action: | Command ignored.
> | User response: | None.
> VAID029I | Already disconnected from DB2-request ignored.
> | Severity: | Information
> | Explanation: | An operator issued a DB2 DISCONNECT command, but SequeLink for z/OS was already disconnected from the DB2 address space.
> | System action: | Command ignored.
> | User response: | None.
> VAID030I | Issuing DB2 cccccccc per operator request.
> | Severity: | Information
> | Explanation: | DB2ASP is executing DB2 request "cccccccc" (CONNECT or DISCONN) in response to an operator request.
> | System action: | DB2 request "cccccccc" is issued.
> | User response: | None.
> VAID031I | ID (ifid) is an unknown DB2 interface.
> | Severity: | Information
> | Explanation: | DB2 interface ID "ifid" is not known.
> | System action: | The DB2 command is ignored.
> | User response: | Correct "ifid" and reissue the command.
> VAID032I | Db2 interface (ifid) is currently busy.
> | Severity: | Information
> | Explanation: | DB2 interface "ifid" is temporarily unable to process the requested DB2ASP command.
> | System action: | The DB2ASP command is ignored.
> | User response: | Reissue the command.
> VAID033E | Syntax error/invalid value in DB2ASP command.
> | Severity: | Error
> | Explanation: | DB2ASP command contains invalid data.
> | System action: | Command is ignored.
> | User response: | Use correct syntax for DB2ASP command.
> VAID034I | There are no configured DB2 interfaces.
> | Severity: | Information
> | Explanation: | A DB2 SHOW command detected no DB2 interfaces.
> | System action: | None.
> | User response: | None.
> VAID035I | DB2 interface (ifid) associated with (ssid).
> | Severity: | Information
> | Explanation: | Normal output of a DB2 SHOW command.
> | System action: | None.
> | User response: | None.
> VAID036F | Db2 module mmmmmm not loaded for Interface dddd.
> | Severity: | Fatal
> | Explanation: | DB2ASP command contains invalid data.
> | System action: | Abend Server abend code User 801.
> | User response: | Check that the correct DB2 Load Libraries are Concatenated to DD statement DB2ifid and are for the correct DB2 version.
> VAID037I | Server ASID(asid/asidx) DB2 version (xxxx), Attachment(aaaaa).
> | Severity: | Information
> | Explanation: | This message is issued when DB2 STATUS command is entered, and is preceded by VAID027I message.
> | System action: | None.
> | User response: | None.
> VAID038W | ATTACHMENT=RRSAF incompatible with DB2 (xxxx), CAF substituted.
> | Severity: | Warning
> | Explanation: | RRSAF attachment requested, see GlobalDB2attachment attribute in DataModel, but RRSAF is incompatible with the current DB2 version.
> | System action: | Use CAF attachment to DB2.
> | User response: | Change GlobalDB2attachment to CAF.
> VAID039I | xxxx waiting for RRS/MVS to become active.
> | Severity: | Information
> | Explanation: | RRSAF attachment requires RRS to be active.
> | System action: | Server continues initialization, but DB2 services will not be available.
> | User response: | Either use CAF attachment, or activate RRS.
> VAID040T | Tracing Information - not documented.
> | Severity: | Trace
> | Explanation: | Internal use.
> | System action: | None.
> | User response: | None.
> VAID041T | Tracing Information - not documented.
> | Severity: | Trace
> | Explanation: | Internal use.
> | System action: | None.
> | User response: | None.
> VAID042E | ccccccc Command ignored - tttttttttttttttttttttttttttttttttt
> | Severity: | Error
> | Explanation: | RRS RELEASE or LIST command has been ignored for reason tttttttttttttttttttttttttttttttttt.
> | System action: | The command is ignored.
> | User response: | Correct the command.
> VAID043T | Ttttttttt - CorrId(cccccc) Prim.Auth(authid) User(uuuuuuu) ACEE(aaaaaaaa) ActTk(tttttt).
> | Severity: | Trace
> | Explanation: | Auth_Signon RRSAF call parameters for connection Ttttttttt.
> | System action: | None.
> | User response: | None.
> VAID044T | Tracing Information - not documented.
> | Severity: | Trace
> | Explanation: | Internal use.
> | System action: | None.
> | User response: | None.
> VAID045T | Tracing Information - not documented.
> | Severity: | Trace
> | Explanation: | Internal use.
> | System action: | None.
> | User response: | None.
> VAID046T | Ttttttttt - DB2 abend(------) ReasonCode(rrrrrrrr) trapped in DB2SQL transformed as SQLCODE(-999) to application.
> | Severity: | Trace
> | Explanation: | DB2 abended with S04E/S04F abend, with reasoncode(rrrrrrrr). The Unit of Work (UOW) for connection tttttttt will be rolled back.
> | System action: | The UOW will be rolled back. The connection will end.
> | User response: | Refer to the reason code in your DB2 documentation for the recommended user response.
> VAID047T | Tracing Information - not documented.
> | Severity: | Trace
> | Explanation: | Internal use.
> | System action: | None.
> | User response: | None.
> VAID048T | Tracing Information - not documented.
> | Severity: | Trace
> | Explanation: | Internal use.
> | System action: | None.
> | User response: | None.
> VAID050E | Ttttttttt - RRS(callname) ReturnCode(rrrrrrrr).
> | Severity: | Error
> | Explanation: | The given RRS-call failed for reason rrrrrrrr.
> | System action: | User logon or thread association will fail.
> | User response: | Refer to the Resource Recovery information in your MVS programming documentation for the explanation and action.
> VAID051E | Ttttttttt - RRSAF(callname) ReturnCode(rrrrrrrr) ReasonCode(rrrrrrrr).
> | Severity: | Error
> | Explanation: | The given RRSAF-call failed.
> | System action: | User logon or Thread association failed.
> | User response: | Refer to the reason code in your DB2 documentation for the recommended user response.
> VAID052E | Ttttttttt - CAF(callname) ReturnCode(rrrrrrrr) ReasonCode(rrrrrrrr).
> | Severity: | Error
> | Explanation: | The given CAF-call failed.
> | System action: | User logon will fail.
> | User response: | Refer to the reason code in your DB2 documentation for the recommended user response.
> VAID053T | Ttttttttt - CTXBEGC Contxt(context) RmToken(rmtoken).
> | Severity: | Trace
> | Explanation: | Arguments passed to the RRS Begin_Context service.
> | System action: | None.
> | User response: | None.
> VAID054T | Ttttttttt - CTXSWCH Contxt(context) DisAssocContxt(context).
> | Severity: | Trace
> | Explanation: | Arguments passed to the Switch_Context RRS service.
> | System action: | None.
> | User response: | None.
> VAID055T | Ttttttttt - CTXEND Contxt(context) ComplType(type).
> | Severity: | Trace
> | Explanation: | Arguments passed to the End_Context RRS service.
> | System action: | None.
> | User response: | None.
> VAID056T | Ttttttttt - Dispatched on WorkerThread(TWORKnnn)
> | Severity: | Trace
> | Explanation: | Connection Ttttttttt was dispatched on worker thread nnn of the threadpool.
> | System action: | None.
> | User response: | None.
> VAID057T | Ttttttttt - Leaving WorkerThread(TWORKnnn).
> | Severity: | Trace
> | Explanation: | Connection Ttttttttt is leaving worker thread nnn of the threadpool.
> | System action: | None.
> | User response: | None.
> VAID060I | ThreadId RRSAF State Age.
> | Severity: | Information
> | Explanation: | This is the Header message resulting from the 'RRS LIST' operator command.
> | System action: | None.
> | User response: | None.
> VAID061I | ThreadId RRSAF State Age.
> | Severity: | Information
> | Explanation: | This is the Detail message resulting from the 'RRS LIST ' operator command where: ThreadId: Identifies the thread. RRSAF State: The RRSAF State of the DB2 thread is one of the following: REUSABLE: DB2 thread can be reused or released. FLAGFORREUSE: DB2 thread is flagged for reuse. INUSE: DB2 thread is in use. Age: Indicates how many seconds this DB2 thread is in REUSABLE state.
> | System action: | None.
> | User response: | None.
> VAID062I | Total nnn DB2Thread(s), peak mmm DB2Threads used.
> | Severity: | Information
> | Explanation: | This is the response to the RRS LIST command.
> | System action: | None.
> | User response: | None.
> VAID063I | nnn DB2Thread(s) released.
> | Severity: | Information
> | Explanation: | This is the response from the RRS RELEASE operator command.
> | System action: | nnn number of DB2 thread(s) were released.
> | User response: | None.
> VAID064I | ThreadId - Logon request from aaa.aaa.aaa.aaa for userid uuuuuuuu data source dddddddd.
> | Severity: | Information
> | Explanation: | This message is the result of a logon command where: ThreadId: Identifies the thread. aaa.aaa.aaa.aaa: Identifies the client IP address uuuuuuuu: Identifies the userid validated by the SAF z/OS security system. dddddddd: Identifies the server data source used by the user.
> | System action: | uuuuuuu will be used as Primary Authid for DB2.
> | User response: | None.
> VAID065I | ThreadId - Logon from aaa.aaa.aaa.aaa userid uuuuuuuu mapped to mmmmmmmm uidmap pppppppp data source dddddddd.
> | Severity: | Information
> | Explanation: | This message results from a logon command with a mapped user where: ThreadId: Identifies the thread. aaa.aaa.aaa.aaa: Identifies the client IP address. uuuuuuuu: Identifies the userid validated by the SAF z/OS security system. mmmmmmmm: Identifies the name of mapped user. pppppppp: Identifies the the name of the UID map specified in MVSDataSourceUIDMap. dddddddd: Identifies the server data source used by the user.
> | System action: | mmmmmmmm will be used as Primary Authid for DB2.
> | User response: | None.
> VAID066I | Ttttttttt - Anonymous logon request from aaa.aaa.aaa.aaa userid Unknown mapped to mmmmmmmm uidmap pppppppp datasource dddddddd.
> | Severity: | Information
> | Explanation: | This message results from a logon command for anonymous access where: aaa.aaa.aaa.aaa is a client IP address. mmmmmmmm: Identifies the name of mapped user. pppppppp: Identifies the name of the UID map specified in MVSDataSourceUIDMap. dddddddd: Identifies the server data source used by the user.
> | System action: | mmmmmmmm will be used as the Primary Authid for DB2.
> | User response: | None.
> VAID067I | Ttttttttt - Logged off.
> | Severity: | Information
> | Explanation: | The connection is logged off from DB2.
> | System action: | DB2 resources are committed.
> | User response: | None.
> VAID068W | Ttttttttt - Logged off abnormally.
> | Severity: | Warning
> | Explanation: | The connection is logged off abnormally from DB2.
> | System action: | DB2 resources are Rolled back.
> | User response: | None.
> VAID069W | ServiceDB2MaxThreads(nnn) lower then ServiceMaxThreads(mmm).
> | Severity: | Warning
> | Explanation: | Configuration conflict.
> | System action: | The value of ServiceMaxThreads will be used to limit the maximum number of DB2 threads allowed.
> | User response: | Increase the value of the dynamic ServiceDB2MaxThreads parameter. Verify that the new value is lower than the MAX BATCH CONNECT parameter in the Thread management panel (DSNTIPE) of the DB2 installation, and greater than ServiceMaxThreads in SequeLink Configuration file.
> VAID070W | Ttttttttt - Maximum of allowed DB2Threads(nnnn) reached.
> | Severity: | Warning
> | Explanation: | The connection will not obtain a DB2 thread.
> | System action: | Either the Logon fails or the client connection is unable to use DB2 (sqlcode =-981).
> | User response: | Increase the value of the dynamic ServiceDB2MaxThreads parameter, and verify that this value is lower than the MAX BATCH CONNECT parameter in the Thread management panel (DSNTIPE) of the DB2 installation.
> VAID072T | VAICDB2R - IFI command cccccccccccccccccc IFCARC1( rc1) IFCARC2(rc2).
> | Severity: | Trace
> | Explanation: | When canceling a DB2Thread, IFI command ccccccccccccc issued with corresponding returncodes is displayed.
> | System action: | None.
> | User response: | None.
> VAID073I | VAICDB2R - ThrdId(tttttttt) found in output DISPLAY THREAD command, token(nnnn) extracted.
> | Severity: | Information
> | Explanation: | The DB2 token nnnn, which is extracted with the DISPLAY THREAD command for the Connection tttttttt active on DB2Thread that will be canceled, is displayed.
> | System action: | None.
> | User response: | None.
> VAID074E | VAICDB2R - ThrdId(tttttttt) not found in output DISPLAY THREAD command.
> | Severity: | Error
> | Explanation: | ThrdId tttttttt was not found in the output DISPLAY THREAD command.
> | System action: | None.
> | User response: | None.
> VAID075E | VAICDB2R - ThrdId(tttttttt) found in output DISPLAY THREAD command, But ThrdId is not active.
> | Severity: | Error
> | Explanation: | ThrdId tttttttt found in output DISPLAY THREAD command, but is not active in DB2.
> | System action: | None.
> | User response: | None.
> VAID076I | VAICDB2R - Canceling DB2Thread with Token(nnnn) for ThreadId(tttttttt).
> | Severity: | Information
> | Explanation: | The DB2Thread with token nnnn on which ThreadId tttttttt is active in DB2, is canceled when requested by a KILL command or during Shutdown with Type=immed.
> | System action: | Either the Logon fails or the client connection is unable to use DB2 (sqlcode =-981).
> | User response: | SequeLink, when requested by a KILL command or during shutdown, terminates the connection and cancels the DB2Thread only if the connection is still active in DB2.
> VAID077E | VAICDB2R - Cancel THRDID - invalid format specified.
> | Severity: | Error
> | Explanation: | Internal error when trying to Cancel a DB2Thread.
> | System action: | None.
> | User response: | Contact DataDirect Technologies technical support.
> VAID100E | VAICRRSM abend aaaa.
> | Severity: | Error
> | Explanation: | Program VAICRRSM is returned with abend aaaa.
> | System action: | Either the RRS command or the automatic ContextCleanup failed.
> | User response: | Contact DataDirect Technologies technical support.
> VAID101I | ThreadId UR identifier UR state.
> | Severity: | Information
> | Explanation: | This message is always generated as the title for the RRS LIST command report output.
> | System action: | Processing continues normally.
> | User response: | None.
> VAID102E | ThreadId UR identifier UR state.
> | Severity: | Error
> | Explanation: | A stored procedure abended.
> | System action: | The stored procedure is not executed and the service returns the SQL code.
> | User response: | Correct the stored procedure.
> VAID103W | ThreadId UR identifier UR state.
> | Severity: | Warning
> | Explanation: | The explanation depends on the exact nature of the problem.
> | System action: | The system action depends on the exact nature of the problem.
> | User response: | The user response depends on the exact nature of the problem.
> VAID104I | ThreadId UR identifier UR state.
> | Severity: | Information
> | Explanation: | The explanation depends on the exact nature of the problem.
> | System action: | The system action depends on the exact nature of the problem.
> | User response: | The user response depends on the exact nature of the problem.
> VAID105T | ThreadId UR identifier UR state.
> | Severity: | Trace
> | Explanation: | The explanation depends on the exact nature of the problem.
> | System action: | The system action depends on the exact nature of the problem.
> | User response: | The user response depends on the exact nature of the problem.