| UNIX | OS/2 |
In an XA Distributed Transaction Processing environment, such as CICS, applications will always run with connect type 2 as the connection setting. In the last release, connect type 1 was used.
It will not be possible to modify the authorization ID on a database connection when the connection already exists.
Modification of the authorization ID on a database connection will have to be performed when the connection does not exist.
| UNIX | OS/2 |
In an XA Distributed Transaction Processing environment such as CICS, information returned in SQLERRD after a CONNECT has changed. In Version 1, SQLERRD(6) was used to indicate one of the following:
Beginning in Version 2, SQLERRD(6) is no longer used, but SQLERRD(3) and SQLERRD(4) are used as follows:
The sixth SQLERRD element will no longer contain the information wanted by the application.
Change the application to look at the third and fourth SQLERRD fields.
| OS/2 |
DDCS for OS/2 used to have a SQLJSETP environment variable. This item had two uses. Each is listed with the DDCS Version 2.3 and DB2 Connect replacement. (In DB2 Version 5, DDCS changed to DB2 Connect.)
/s=c meant to prep/bind and perform syntax checking only without actually creating a package. This has been replaced by the SQLERROR CHECK bind/prep option.
/s=n meant no errors were allowed during prep/bind. A package would only be created if there were no errors. This has been replaced by the SQLERROR NOPACKAGE prep/bind option.
The SQLJSETP environment variable and options are ignored, causing prep/bind to work according to their defaults.
Use the SQLERROR NOPACKAGE and/or SQLERROR CONTINUE options as needed.
| UNIX |
The DDCSSETP utility has been removed. There is no longer a need for this because all messages are now revealed to the precompiler (and hence its message file) regardless of using SQLERROR CONTINUE or not. Refer to the prep/bind options discussed in "DDCS - SQLJSETP" for information.
| OS/2 |
DDCS for OS/2 had a utility called sqljtrc.cmd. It has been replaced by the ddcstrc.exe executable. The invocation syntax has changed.
Attempting to trace DB2 Connect will fail if the old utility and parameters are used.
Execute the command ddcstrc.exe with valid parameters. See the DB2 Connect User's Guide for the new syntax.
| OS/2 |
The DDCS for OS/2 utility called sqljbind.cmd has been removed.
Attempts to use this utility with DB2 Connect will fail.
This utility has been replaced by a three step set of instructions which are described in "Chapter 4, Binding Applications and Utilities" in the DB2 Connect User's Guide.
| OS/2 |
When using APPC, DB2 for OS/2 Version 1 supported the following commands for cataloging entries in the node directory:
Beginning in Version 2, support for the following has been removed:
The CATALOG APPC NODE command has been changed to represent the APPC communication parameters required for the Communications Manager for OS/2 CPI Communications (CPIC) Side Information Profile.
The symbolic destination name parameter, in the CATALOG APPC NODE, contains the CPIC Side Information profile name in Communications Manager for OS/2. Refer to the Command Reference for details on this command.
All of the current connections using APPC will continue to work correctly and DB2 will accept the current catalog information after migration. This is true whether you migrate your server, clients or both.
The current catalogs cannot be modified. If you need to modify the information, you will have to UNCATALOG the node entry, and then recatalog using the new CATALOG APPC command.
If you have existing applications that call the CATALOG NODE API to catalog APPC and APPN node directory entries, these applications will still work. The CATALOG NODE API still supports the Version 1 APPC and APPN API structures.
When you try execute the CATALOG APPC node you will need to:
Refer to the DB2 Connect Personal Edition Quick Beginnings for details on setting these nodes.