APAR status
Closed as canceled.
Error description
This Info. APAR documents changes to the DB2 Messages and Codes SC26489200 which did not make the Version 3 GA pubs. This APAR is continued in II07908 & II08169. 5740xyr00 R310 ================================================================ Book Title: Messages and Codes Page Number: 2-21 Change description: Replace SQL code -309 with the following: -309 A PREDICATE IS INVALID BECAUSE A REFERENCED HOST VARIABLE HAS THE NULL VALUE Explanation: The statement could not be processed because a host variable appearing in a predicate such as column-name = host-variable had the NULL value. Such a predicate is not permitted when the host variable contains the NULL value even though the object column might contain nulls. System Action: The statement cannot be executed. Programmer Response: Rebind the plan or package containing the statement. The condition described is not an error in DB2 Version 2 Release 3 and later. SQLSTATE: 22512 ================================================================ Version 3 Book Title: Messages and Codes Pages: 2-25 Change Description: In SQLCODE -501, replace the 3rd sentence of the PROGRAMMER RESPONSE with the following: SQLCODES -404, -652, -679, -901, -904, -909, -910, -911, and -913 might force the cursor to close. ================================================================ Version 3 Book Title: Messages and Codes Pages: 2-30 Change Description: In SQLCODE -539, add SQLSTATE 55008. ================================================================ Book Title: Messages and Codes Page Number: 2-32 Change description: For SQL code -601, add the following paragraph after the existing paragraph under "Explanation:" If 'obj-type' is TABLE/VIEW, the alias-name specified in the CREATE ALIAS statement is identical to the table-name/view-name specified. The TABLE/VIEW might not exist in the DB2 subsystem. ================================================================ Book Title: Messages and Codes Page Number: 2-49 Change description: For SQL code -870, replace the first sentence under "Problem Determination" with the following: If the SQL statement is bound locally, descriptors are built by the DB2 precompiler. ================================================================ Book Title: Messages and Codes Page Number: 3-21 DSNCxxx and DSN2xxx chapters Change Description: There are now two versions of the CICS attachment facility: o The version shipped with DB2 requires CICS Version 3 Release 3 or an earlier release. This attachment facility issues DSNCxxx messages. o The version shipped with CICS requires a CICS release later than Version 3 Release 3. This attachment facility issues DSN2xxx messages. The new and old CICS attachment facility messages are generally the same. If you get a DSN2xxxx message, find the DSNCxxxx message with the same number. Some DSN2 messages (DNS2040, DSN2052, and DSN2052) differ slightly from their equivalent DSNC messages. These changes are documented along with the new DSN2 messages and the new and changed DSNC messages. *******************DSNC MESSAGES**************************** Replace message DSNC052I with the following: DSNC052I INSUFFICIENT STORAGE AVAILABLE TO START ATTACHMENT FACILITY EXPLANATION: During startup the CICS attachment facility was unable to allocate the required amount of storage. This message might be issued if an error occurs while the attachment facility is loading the data only load module, DSNCRCTx. This message is issued by the following CSECT(s): DSNCMSG0 DSNCSTRT SYSTEM ACTION: The CICS attachment facility is not initialized. SYSTEM PROGRAMMER RESPONSE: Allow a larger amount of dynamic storage on your CICS system. Alternatively, you can delete unused entries or lower THRDA and THRDM values in your RCT, which reduces the size of the storage that the attachment facility requires. For a load error, check the MVS console log for any preceding messages to determine why the load failed. If there is not enough free REGION space to load the RCT, see the appropriate CICS documentation for information on tuning your CICS system. ========================================================== These are new DSNC messages: DSNC057I csect-name CICS RELEASE release IS TOO HIGH FOR THIS ATTACHMENT FACILITY EXPLANATION: The attachment facility that you are using requires CICS Version 3 Release 3 or an earlier release. You are using a CICS release later than CICS Version 3 Release 3. For this release of CICS, you must use the attachment facility shipped with CICS. SYSTEM ACTION: The attachment facility does not initialize. USER RESPONSE: Ensure that the CSD definition of the DSNC transaction specifies program DSN2COM1. If you are initializing the attachment facility using CICS program list table (PLT) processing, ensure that your CICS PLTPI table uses program DSN2COM0 to initialize the attach. DSNC059I csect-name CICS ATTACHMENT FACILITY MISMATCH WITH RESOURCE CONTROL TABLE rct-name EXPLANATION: The wrong macro library was used to assemble DSNCRCT, the resource control table. There are two versions of the CICS attachment facility. The version shipped with DB2 requires CICS Version 3 Release 3 or an earlier release; the one shipped with CICS requires a CICS release later than Version 3 Release 3. This message indicates that CICS is using the attachment facility shipped with DB2, but the RCT was assembled using the CICS macro libraries. SYSTEM ACTION: The CICS attachment facility initialization terminates. USER RESPONSE: Reassemble DSNCRCT using the DSNCRCT macro shipped in the DB2 macro libraries. ******************DSN2 MESSAGES**************************** See the note about the DSN2 messages above. ----------------------------------------------------------- In message DSN2040I, replace the System Programmer Response in message DSNC040I with the following: Check the CICS JOBLIB/STEPLIB libraries and ensure that the CICS SDFHAUTH and the DB2 SDSNLOAD libraries are defined there. ----------------------------------------------------------- In message DSN2052I, replace the last sentence of the Explanation in message DSNC052I with the following: This message might be issued if an error occurs while the attachment facility is loading the data only module, DSN2CTxx. ----------------------------------------------------------- In message DSN2053I, replace the first sentence of the System Programmer Response in message DSNC053I with the following: Ensure that CSD group DFHDB2 was installed in the CSD. ========================================================== These are new DSN2 messages: DSN2002I csect-name DSN2CTxx MODULE NOT FOUND EXPLANATION: The resource control table DSN2CT with suffix xx could not be loaded. SYSTEM ACTION: The CICS attachment facility initialization terminates. USER RESPONSE: Reenter the start command with the correct suffix. Ensure that the resource control table DSN2CT is in the correct application program library, which is concatenated in the JOBLIB or STEPLIB statement of your CICS startup JCL. If DSN2CT is not in your application program library, ensure that you are using the correct version of the DSNCRCT macro to assemble DSN2CT. For CICS versions later than Version 3 Release 3, the correct DSNCRCT macro is in the CICS macro library rather than in the DB2 macro library. DSN2056I csect-name CICS RELEASE release IS DOWN LEVEL FOR THIS ATTACHMENT FACILITY EXPLANATION: The attachment facility that you are using requires a CICS release later than Version 3 Release 3. You are using CICS Version 3 Release 3 or an earlier release. For this release of CICS, you must use the attachment facility shipped with DB2. SYSTEM ACTION: The attachment facility does not initialize. USER RESPONSE: Ensure that the CSD definition of the DSNC transaction specifies program DSNCCOM1. If you are initializing the attachment facility using CICS program list table (PLT) processing, ensure that your CICS PLTPI table uses program DSNCCOM0 to initialize the attach. DSN2059I csect-name CICS ATTACHMENT FACILITY MISMATCH WITH RESOURCE CONTROL TABLE rct-name EXPLANATION: The wrong macro library was used to assemble DSN2CT, the resource control table. There are two versions of the CICS attachment facility. The version shipped with DB2 requires CICS Version 3 Release 3 or an earlier release; the one shipped with CICS requires a CICS release later than Version 3 Release 3. This error message indicates CICS is using the attachment facility shipped with CICS, but the RCT was assembled using the DB2 macro libraries. SYSTEM ACTION:The CICS attachment facility initialization terminates. USER RESPONSE: Reassemble DSN2CT using the DSNCRCT macro shipped in the CICS macro libraries. DSN2060I csect-name INITPARM IS IGNORED BECAUSE FORMAT IS INVALID. EXPLANATION: The DSN2STRT INITPARM specified on the CICS initialization job is incorrect. The format of the INITPARM should be: INITPARM=(DSN2STRT='xx,yyyy') where xx is the suffix of the RCT and yyyy is the DB2 subsystem id. The RCT suffix cannot be greater than 2 characters, and the subsystem ID cannot be greater than 4 characters. To specify an RCT suffix only, use the format: INITPARM=(DSN2STRT='xx') To specify a subsystem ID override only, use the format: INITPARM=(DSN2STRT=',yyyy') SYSTEM ACTION: The attachment facility attempts to initialize with the subsystem ID specified in the DSNC STRT command. If no subsystem ID is provided there, it attempts to initialize with the subsystem ID specified in the resource control table. USER RESPONSE: If you want to override the subsystem ID, restart the attachment facility using the DSNC STRT command with the correct SSID. Alternatively, you can correct the DSN2STRT INITPARM Additional messages are continued in APAR II07908. ================================================================ This Info. APAR is continued in II07908 & II08169.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
close for INTERNET viewing
APAR Information
APAR number
II07607
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1994-02-10
Closed date
1997-11-01
Last modified date
1997-11-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
14 December 2020