We have the following configuration.
Db2 : Version 12 FL506 (test) , FL506 (prod).
Db2 connect gateway and IBM Data Server client version : V11.1 Fix Pack 3
ZPARM APPLCOMPAT : V12R1M506 (test) , V12R1M501(prod)
Application uses Websphere to make connection to Db2 z/OS via connect gateway.
Before we migrate to FL506 in production, I wanted to run IFCID 376 to see any incompatibility. We turned on trace for IFCID 376 and produced CA SYSVIEW batch report BTRINCMT (SQL Incompatibility Trace).
We see some incompatibilities reported for the IBM Data Server Driver package NULLID.SYSLH200.
We did not REBIND/BIND this package after the upgrade. The idea is to use separate collection id for each APPLCOMPAT if there is a need (application wanting to use a v12 feature etc.,)
No one complained about a failed transaction/process so far.
Following is a portion of IFCID 376 report. There are additional messages for long CLIENT_APPLNAME, CLIENT_USERID & CLIENT_WRKSTNNAME. The workstation in this case is the Websphere Application Server IP address.
EVENT: 04/22/20 12:37:13.3265 INCOMPATIBILITY REASON: Long
CLIENT_ACCTNG SR REASON CODE: 1104
AUTH ID : XXXXXXX CONNECTION ID: SERVER
PLAN NAME : DISTSERV CORRELATION ID: db2jcc_appli
LOCATION : DB2T
WORKSTATION : XX.XXX.XX.XXX
TRANSACTION : db2jcc_application
ENDUSER : XXXXXXX
COLLECTION ID : NULLID
PROGRAM NAME : SYSLH200
CONTOKEN (HEX): 5359534C564C3031
STMT ID (HEX) : 000000000000055B STMT NUMBER: 1 SECTION: 1 STMT TYPE: Dynamic
My understanding is that NULLID packages does NOT need any change unless application wants to use a new feature.
1) Why do i see this in the report? Is this because the package NULLID.SYSLH200 was last bound in V10 (APPLCOMPAT and FUNCTION_LVL for this package is blank) and we see V10R1 behavior?
The following link says these special register values will be truncated to V10 maximum length padded with blanks.
2) Should I just ignore these as warnings and assume they will go away when we start using different set of IBM Data Server Driver packages with latest APPLCOMPAT ?
I have attached the full incompatibility report for reference.
Thanks very much in advance.