DDCS/2 v2.2 FixPak APAR information                         30/07/96
===================================


Defects fixed for FixPak 7093 (Jul, 1996)
-----------------------------------------

JR08356  20197  DDCS/2 sends wrong version and release to host

JR08866  41023  DDCS returns +100 for 2nd fetch when 1st fetch return neg code.

JR08953  42930  Export host data HANG with DDCS/2


Defects fixed for FixPak 7046 (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 7036 (January, 1995)
---------------------------------------------

JR08083: DDCS Logon using lower case

    Users logging on through DDCS/2 were not able to use lower case letters.
    This fix allows users to use both upper and lower case letters in the
    userid and password fields during a host logon via DDCS/2 v2.2.

***********************************************************************
**                                                                   **
**  (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1996.  **
**                    ALL RIGHTS RESERVED.                           **
**                                                                   **
***********************************************************************