Call attachment facility trace messages
An application programmer that uses the call attachment facility (CAF) to write an application that attaches to Db2 can choose whether the messages are displayed or not. They display if the DSNTRACE ddname is allocated during CAF execution.
Message number
- Name of the CSECT that caused the message to be written.
- TCB address of the task currently running.
- A series of tokens and token-explanations unique to each message.
| Message number | Message text | Explanation |
|---|---|---|
| DSNA800I | DSNACA00 TCB=address ENTERED DSNACA00 ACTION=action R1=address CABPTR=address CABFLAG1=flag1 CABFLAG2=flag2 |
The call attachment facility received a call attachment facility request to perform the 'action' function. The parameter list begins at location 'address'. CABPTR specifies the location of the call attachment facility control block (the CAB). CABFLAG1 and CABFLAG2 are the current flag bytes. This message is issued by the following module: DSNACA00 |
| DSNA801I | DSNACA00 TCB=address LEAVE DSNACA00 CABFLAG1=flag1 CABFLAG2=flag2 CABPTR=address |
The call attachment facility issues this message following completion of a call attachment facility request. CABFLAG1 and CABFLAG2 are the flag bytes and CABPTR specifies the location of the call attachment facility control block. This message is issued by the following module: DSNACA00 |
| DSNA805I | DSNACA00 TCB=address CONNECT REQUEST SSID=ssid SECBP=ecb address TECBP=ecb address RIBW=address |
The call attachment facility received a CONNECT request with the specified parameter values. SSID is the subsystem identifier, SECBP is the Db2 start-up ECB address, TECBP is the Db2 termination ECB address, and RIBW is the address of the fullword that will be set to contain the address of the release information block (RIB) after the CONNECT completes. This message is issued by the following module: DSNACA00 |
| DSNA806I | DSNACA00 TCB=address DISCONNECT REQUEST |
The call attachment facility received a DISCONNECT request for the specified TCB. This message is issued by the following module: DSNACA00 |
| DSNA807I | DSNACA00 TCB=address OPEN REQUEST SSID=ssid PLAN=plan name |
The call attachment facility received an OPEN request with the specified SSID and PLAN values. This message is issued by the following module: DSNACA00 |
| DSNA808I | DSNACA00 TCB=address CLOSE REQUEST TRMOP=terminate option |
The call attachment facility received a CLOSE request with the specified termination option. This message is issued by the following module: DSNACA00 |
| DSNA810I | DSNACA00 TCB=address BEFORE function ==================== |
The call attachment facility issues this message before a 'function' request to Db2. This is the last call attachment facility action performed before passing control to Db2 for processing. If this is the last call attachment facility message before an abend, then the abend very probably occurred in the Db2 code proper, rather than in the call attachment facility code. This message is issued by the following module: DSNACA00, DSNACA70 |
| DSNA811I | DSNACA00 TCB=address AFTER function ==================== |
The call attachment facility issues this message when Db2 returns control after a 'function' request. This message is issued by the following modules: DSNACA00, DSNACA70 |
| DSNA813I | csectname TCB=address FRBP=address RAL=data RALE=data FVLE=data PARM=data PCNT=data |
This message, along with message DSNA814I, displays the contents of the FRB control block before or after a call to Db2. This message is issued by the following modules: DSNACA00, DSNACA70 |
| DSNA814I | csectname TCB=address RC1=retcode RC2=reascode FBACK=feedback RHPC=data QUAL=data RSV1=data |
This message, along with message DSNA813I, displays the contents of the FRB control block before or after a call to Db2. This message is issued by the following modules: DSNACA00, DSNACA70 |
| DSNA815I | DSNACA70 TCB=address FDBKEIB=EIB-address SSID=ssid GATT=group-attach-name GRPN=group-name MBRN=member-name SGATT=subgroup-name |
This message displays the address and contents of the environment information control block (EIB). Db2 generates this message when the EIB address is not 0. |
| DSNA821I | DSNACA00 TCB=address IMPLICIT CONNECTION REQUEST |
The call attachment facility received an SQL request before establishing the Db2 connection. This results in an implicit connection to Db2 using defaults for the application plan name and, if no CONNECT was issued, the Db2 subsystem identifier. This message is issued by the following module: DSNACA00 |
| DSNA822I | DSNACA00 TCB=address TRANSLATE REQUEST SQLCA=address CABFRC1=retcode CABFRC2=reascode FRBRHPC=frbrhpc |
The call attachment facility received a TRANSLATE request. This message identifies the location of the SQLCA whose SQLCODE field will be set and the return codes that will be translated. The translate will not be performed if FRBRHPC is zero. |
| DSNA824I | DSNACA00 TCB=address CAF READY FOR NEW CONNECTION SERVICE REQUESTS |
This message indicates that the previous Db2 connection has been terminated, certain clean-up processing has occurred, and that the call attachment facility is now ready to process additional connection requests. This message is issued by the following module: DSNACA70. It is accompanied by return code 4 in register 15 and code reason code 00C10824 in register 0. |
| DSNA825I | DSNACA70 TCB=address CABSSID=ssid CABREL=release CABDECPP=address EIBPARM=EIB-address |
This message lists the current values in DSNHDECP, which is link edited with the call attachment facility main load module, DSNACAF. These values are used as defaults on implicit connection requests. |
| DSNA826I | DSNACA00 TCB=address BEFORE VALIDITY CHECKING THE type ECB AT ADDRESS location |
This trace message indicates that a check of the 'type' ECB (either start-up or shutdown), is about to be done to determine if the address identified by 'location' is addressable. If an 0C4 abend occurs immediately following this message, then an invalid ECB address was passed on a CONNECT request. |
| DSNA827I | DSNACA00 TCB=address AFTER VALIDITY CHECKING THE ECB WHICH CONTAINS 'data' |
This trace message indicates that the identified ECB is addressable and contains the specified data value. Appearance of this message is not a guarantee that the ECB address that was passed is valid; it has only passed preliminary tests. Deleting this ECB without Db2 knowing makes the ECB invalid. This message is issued by the following module: DSNACA00 |
| DSNA828I | DSNACA00 TCB=address RIB ADDRESS=ribaddr RIBPTR ADDR=ribptr |
This trace message lists the address of the Db2 release information block (ribaddr) and the address of the fullword that points to the RIB (ribptr) after connection attempts that were made to a Db2 subsystem identifier that existed. This message is issued by the following module: DSNACA70 |
| DSNA829I | DSNACA00 TCB=address R1(FRB)=frbaddr SQLDSECT(FRBPARM)=dsectaddr RDI=rdiaddr SQLCA=sqlcaaddr CABFLAG2=flag2 |
This trace message lists the addresses of the FRB, the SQLDSECT, the RDI and the SQLCA. The CABFLAG2 flag byte is useful for learning the AMODE of DSNACA00's caller, the Language Interface (DSNALI). This message is issued by the following module: DSNACA00 |
| DSNA830I | DSNACA00 TCB=address SQLCODE=sqlcode CABFLAG1=flag1 CABFLAG2=flag2 |
This trace message lists the SQLCODE and the two call attachment flag bytes. This message is issued by the following module: DSNACA00 |
| DSNA831I | DSNACA70 RELEASE LEVELS NOT COMPATIBLE. CAF=release_level, DB2=release_level |
The call attachment facility (CAF) has detected a release level incompatibility between Db2 and itself. The current release levels of CAF code and the Db2 subsystem load modules are indicated as a string of three numeric characters, one for each of the following items:
The connection to the Db2 subsystem is not successful. A return code of 8, and a reason code of 00C10831 are returned to the caller's application program. If you used JCL or a TSO logon procedure to invoke CAF, check that the correct Db2 libraries are defined in your JOBLIB and STEPLIB allocations. See your system programmer if you invoke CAF by using procedures that are supplied by your system programmer. If you are unable to determine the problem, you can trace CAF execution by defining a DSNTRACE DD data set. Ensure that coexistence is supported on both release levels (CAF and Db2). If coexistence is supported, ensure that the lower-level release has the correct SPE level code support that is required to coexist with the current higher level release. |
