APAR S25102
                                                                     -----------

Date:         March 15, 1999


Memorandum
To:           All Comm-Pro ITI NCP/NEO Users at the SHIP25 Distribution Level.


Subject:      APAR S25102 (with our apologies)


Problem
Description:  This APAR addresses two separate conditions:

              Item 1 - FMD RU size (device to host) previously restricted 
              to 1024 bytes per chained element. This limitation was the 
              result of a restriction in the DSP support that uses common
              logic with ITI NCP/NEO sessions.

              Solution is to bypass logic that restricts the RU size to
              1024 if the session is ITI. We will now use any legitimate
              size as defined in the BIND from the application. Note that
              the majority of applications for ITI NCP/NEO (PU Type 1, LU 
              Type 0 or 1) BIND the session with an RU size of 256 bytes.

                This problem was observed at a site with custom logic to
                force OIC (only in chain) RU's. The remote transaction
                generator was intermittently batching transaction groups
                in excess of 1024 byte lengths which caused the RU size
                exception. Note that our standard RU chaining logic
                would not have encountered this problem. This is because
                RU chain elements normally contain the X.25 packet level 
                window size (+1 packet) of packet data per RU chain 
                element for large m-bit packet sequences.
                
              Item 2 - This condition can only affect sessions bound with
              FM Usage - Common LU Protocols, normal-flow send/receive 
              mode selection of half-duplex contention (HDX/CTN). 
 
              Register usage error can cause the SLU (Secondary LU) to 
              appear as the contention winner if Bracket Termination 
              Rule 2 is in effect. Note that this is primarily a cosmetic
              change because of the standard values normally set in the 
              BIND for Common LU Protocols. 

              Solution is to test LUBBCCWM (flag X'10') in BIND byte 7 
              (LO7) instead of byte 6 (HI7).  


Solution:     Perform the following macro update(s) then rerun your Comm-Pro
              SYSGEN.  Additional APAR installation instructions can be found
              in the SHIP25 documentation manual in APPENDIX F (Maintenance).

              All occurrences of 37mm below should be replaced with your FEP
              model (3745, 3725 or 3720).


....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8

*/*
*/* XFM37XX - XFLULU and XFFLIH MACRO UPDATE(s) FOLLOW:
*/*

./       CHANGE NAME=XFLULU,LIST=ALL
./ NUMBER SEQ1=15230000,NEW1=15231025,INCR=1000,INSERT=YES       S25102 15230000
         AGO   .BIND45        SKIP OLD DSP SEGMENT CHECK LOGIC.  S25102
./ NUMBER SEQ1=15320000,NEW1=15321025,INCR=1000,INSERT=YES       S25012 15320000
.BIND45  SPACE 1                                                 S25102
         TRM   LO7,LUBBCCWM   SEE IF SLU IS CONTENTION WINNER. X_S25102 21280000
./       CHANGE NAME=XFFLIH,LIST=ALL
         DC    CL24'S25102 (MANUAL) XFLULU..'                    S25102 01010225
//

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8

*END-OF-FILE*  (THIS FILE BEST VIEWED WITH A FIXED FONT SUCH AS COURIER)