DDCS/2 v2.0 FixPak APAR information 30/07/96 =================================== Defects fixed for FixPak 7091 (May, 1995) ----------------------------------------- JR08866 41023 - DDCS returns +100 for 2nd fetch when 1st fetch return neg. code. Defects fixed for FixPak 7041 (May, 1995) ----------------------------------------- JR08316 - Allow Clients to connect to multiple instances on DB2/6000 In the past, DB2/2 clients could only connect to one instance of DB2/6000 running with SNA/6000 Server. This functional enhancement allows DB2/2 clients to connect to multiple DB2/6000 instances on the same box. To take advantage of the new feature, different remote TP names (transaction program names) must be specified for each instance: Normally, a DB2/2 client uses the remote service TP name x'07'6DB for database connections, and the remote service TP name x'07'6SN for interrupts. The environment variable DB2PARTNERLULIST can be used to customize the remote TP names that the DB2/2 client uses. To define the DB2PARTNERLULIST variable, add the following statement in the CONFIG.SYS: SET DB2PARTNERLULIST=[plu,dbtp,intrtp] where each partner lu list triplet consists of: plu is the partner lu alias specified in the APPC node directory entry, or the fully qualified partner lu name specified in the APPN node directory entry. A partner lu alias can be mixed case. A fully qualified partner lu name must be all upper case. dbtp is the remote TP name to be used for database connections. This cannot be a service TP. intrtp is the remote TP name to be used for interrupts. This cannot be a service TP. Basically, when the partner lu specified by a DBPARTNERLULIST triplet matches the corresponding partner lu specified in the APPC/APPN node directory entry, the customized TP names specified by DB2PARTNERLULIST are used, instead of the default service TP names x'06'6DB and x'07'6SN. For example, SET DB2PARTNERLULIST=[lu1,TEST,TESTINT][CAIBMOML.LU2,DBTP,INTTP][.LU3,tp3,itp3] The first partner lu list triplet is used for an APPC node directory entry where the partner lu alias is lu1. The second partner lu list triplet is used for an APPN node directory entry where the remote network id is CAIBMOML and the partner lu name is LU2. The third partner lu list triplet is used for an APPN node directory entry where the remote network id is not specified, and the partner lu name is LU3. JR08351 - Stack overflow error for APPC (F015 from CM/2 or SYS3175) Previously, applications accessing a database via APPC could receive stack overflow errors. Errors could be in the form of F015 in Communication Manager/2 (CM/2) or system trap SYS3175. This has been fixed. Defects fixed for FixPak 7031 (January, 1995) --------------------------------------------- JR08061 - SYS3171 if network id for APPN workstation set to null In the past if a user cataloged an APPN workstation and specified NULL for the Network ID, a trap message similar to the following one was received when the user tried to connect: SYS3171 in ACSSVC.DLL 0005:13fe4148 This has been fixed to enable the user to connect successfully from an APPN workstation without encountering a system trap. Defects fixed for FixPak 7024 (May, 1994) ----------------------------------------- JR07377 - DDCS/2 SQLCODE mapping When DDCS/2 performed SQLCODE mapping on errors with long message tokens, the first character of the SQLERRP field was corrupted. This has been corrected to return the correct code. JR07710 - Disabling NetBIOS This fix allows DB2/2 to disable the NetBIOS protocol initialization. This will conserve system resources and NetBIOS subsystem resources for those DB2 users that are not using the DB2 NetBIOS protocol. To specify this option, the user should set the SQLNADPT environment variable (either from the command line or in config.sys) to "NONE" before issuing a STARTDBM. i.e. SET SQLNADPT=NONE The Select Pak should be installed on all work stations on which it is desirable to disable the NetBIOS protocol. With this fix, a NetBIOS client which attempts to connect to a "NetBIOS disabled" server will receive an SQLCODE -30080 '0014' (Server is not ready). A "NetBIOS disabled" client which tries to access a sever via NetBIOS will receive an SQLCODE 30080 'FFFF' (Local DB2/2 NetBIOS protocol has not been initialized correctly). JR07759 - DOS\Windows client connecting to AS/400 When a DOS\Windows client accessing an AS/400 system through DDCS tried to insert null data into a fixed char column, an SQLCODE 30020N, reason code 220A was returned. The insert will now be performed correctly. FixPak 7016 (January, 1994) --------------------------- Defects fixed for FixPak 7011 (July, 1994) ------------------------------------------ JR07104 - LANGLEVEL Option The sqlprep LANGLEVEL Option (/L) was incorrectly supported in DDCS/2 2.0. With this fix, DDCS/2 will always operate as though /L=0 (SAA support) has been specified. *********************************************************************** ** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1994. ** ** ALL RIGHTS RESERVED. ** ** ** ***********************************************************************