home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
CM2AP111.PKG
< prev
next >
Wrap
Text File
|
1996-05-10
|
20KB
|
486 lines
*******************************************************************
*
* Date: 03/12/96 (Repackaged on 3/28/96 into 3 zip files.)
*
* This package contains APAR fixtests to release level code. This
* package is distributable to any customer who has a CM/2 license.
*
*******************************************************************
*
* Applicable CM/2 version(s): 1.11 (WR06150)
*
*******************************************************************
*
* List of APARs included, Description of new function APARs
* included in the package, and Installation instructions follow:
*
*******************************************************************
*
* LIST OF APARs INCLUDED:
*
* The following SNA-APPC-APPN-SNAGATEWAY APAR fixtests are included in this package:
*
* All APARs closed prior to July 1, 1994 and
* the APARs listed below:
*
*
* JR08524 JR08587 JR08345 JR08617 JR08852 JR08616
* JR08280 JR08611 JR08288 JR08610 JR08838 JR08806
* JR08205 JR08608 JR08346 JR08564 JR08812 JR08611
* JR08359 JR08580 JR08454 JR08568 JR08803 JR08647
* JR08473 JR08565 JR08373 JR08517 JR08768 JR08438
* JR08314 JR08535 JR08370 JR08528 JR08738 JR08558
* JR08381 JR08524 JR08395 JR08457 JR08722 JR08854
* JR08365 JR08509 JR08251 JR08500 JR08751 JR08601
* JR08255 JR08492 JR08497 JR08490 JR08737 JR08560
* JR08435 JR08484 JR08324 JR08453 JR08762 JR08624
* JR08339 JR08452 JR08402 JR08431 JR08693
* JR08403 JR08386 JR08262 JR08287 JR08695
* JR08299 JR08278 JR08260 JR08244 JR08714
* JR08176 JR08217 JR08236 JR08286 JR08646
* JR08229 JR08165 JR08124 JR08084 JR08652
* JR07971 JR08193 JR08189 JR08245 JR08651
* JR08196 JR08182 JR08160 JR07455 JR08665
* JR08250 JR08101 JR08121 JR08131 JR08591
* JR08106 JR08065 JR08130 JR08121 JR08606
* JR08058 JR08052 JR08527 JR08459 JR08615
*
*DESCRIPTION OF NEW FUNCTION APARS INCLUDED IN THE PACKAGE:
*
*
* APAR= JR08665 FIXED PACING FOR INTERMEDIATE NODES. - NEW FUNCTION
*
*
* Interactive traffic waits behind large file transfers.
*
* The problem is that too much data is queued to the DLC
* queue. If interactive data comes afterwards, it has to
* wait much longer. Now, if the fixed pacing is used,
* the data may get collected at intermediate node in SNA
* queue but the DLC queue will never have
* more than "2n-1" frames for that particular session where
* n is the fixed pacing window.
*
* The benefit of fixed pacing is:
*
* Fixed pacing when used at end workstation or intermediate node,
* it limits to amount of frames that can be queued to the DLC to
* 2n-1 for a given session. (n is fixed pacing value). This allows
* other sessions to also queue data to the DLC queue before all
* the data from an earlier file transfer is queued to the DLC."
* This new function was added to Communications Manager/2 1.11.
* See APAR JR08131 for defining fixed pacing and related
* APAR JR08492.
*
*
*
* APAR= JR08431
* NEW FUNCTION FOR SDLC DIAL-OUT TO ALLOW A BACKUP HOST TO
* DIAL-IN.
*
* The new function required is ... to have a primary host that is
* dialed out and an incoming backup host (different fully
* qualified name and node ID) that is received for SDLC.
*
* Communications Manager/2 was updated to match an incoming
* request to a defined link if the defined link has no adjacent
* CP name or adjacent node ID and the incoming request has
* INIT_SELF supported (from a PU 2.0 host) on the received
* XID3 for SDLC connections.
*
*
* APAR= JR08452
* NEW FUNCTION TO OPTIONALLY NOT REACTIVATE THE DLC.
*
* Communications Manager/2 1.11 ( WR06150 )
*
* Communications Manager/2 was updated to look at the
* APPCPC.DAT file to determine if the DLC is to be reactivated
* or not.
*
* The default for Communications Manager/2 is reactivate the DLC.
*
* To define Communications Manager/2 such that it will not
* reactivate the DLC:
* 1. Edit the APPCPC.DAT file in cmlib
* 2. A "D" begins each line of the DLC records in the APPCPC.DAT
* file. Look for the "*", which is in column 37.
* 3. For the DLC that you do not want to reactive, place a
* "1" after the "*" , column 38. The DLC name is in columns
* 26-33.
* 4. Enter CMSETUP and change a value in the configuration of
* the DLC that is not to be reactivated. Any parameter can
* be changed. Exit the panel, then reenter the panel to
* change the parameter back to the original value. This will
* cause Communications Manager/2 to read the APPCPC.DAT and
* update the Communications Manager/2 configuration to not
* reactivate the chosen DLCs.
*
*
* APAR= JR08453
* AUTOMATICALLY RESTORE CP-CP SESSION WHEN A LINK IS DROPPED.
*
* When CP - CP Sessions fail between Communications Manager/2
* and its partner CP, the link had to be broken and brought
* back up again to restore the CP - CP Sessions.
* This in effect meant that all application sessions would have to
* come down as well.
*
* This APAR provides the ability for Communications Manager/2 to
* recover CP-CP sessions (reactivate) without having to deactivate
* the link from CM/2 to NCP (3745).
*
*
* APAR= JR08492
* TWO WAY FIXED PACING
*
* 3270 sessions appear to hang or stop during transmission of
* large amounts of data by APPC or LU6.2 programs.
*
* The problem is that the 3270 traffic is interspersed with the
* APPC traffic as it is queued on the Data Link Control. For
* example a large APPC data transaction would be queued,
* next a 3270 enter key. The 3270 transaction would
* wait until all previously queued data was transmitted, and
* it would be sent.
*
* If the host is sending data then setting FIXED PACING
* (see JR08131) may resolve the problem if the host is
* also properly configured. This APAR introduces TWO_WAY_FIXED
* pacing as another alternative, if you have Communications
* Manager/2 connected to an NCP and you do not want to change
* the NCP definition.
*
* Communications Manager/2 via this APAR, implements a new
* function called TWO_WAY_FIXED pacing. This new function
* will work over sessions flowing between and NCP and
* Communications Manager/2, but not between two
* Communications Manager/2 workstations.
*
* When Communications Manager/2 to Communications Manager/2
* is attempted with TWO_WAY_FIXED pacing, Sense 08350008
* is returned in the UNBIND.
*
* With TWO_WAY_FIXED pacing, Communications Manager/2
* will set both the primary receive and secondary send pacing
* window size in the bind response from the mode
* RECEIVE_PACING_WINDOW.
*
* You will need to chose the window sizes that work
* best in your environment.
*
* To configure two way fixed pacing, edit the *.ndf file, under
* DEFINE_MODE, add or change the PACING_TYPE to
* PACING_TYPE(TWO_WAY_FIXED).
*
* Example: DEFINE_MODE mode_name(mode1)
* max_ru_size_upper_bound(4096)
* cos_name(#connect)
* default_ru_size(yes)
* max_negotiable_session_limit(1)
* min_conwinners_source(1)
* plu_mode_session_limit(1)
* receive_pacing_window(7)
* compression_need(requested)
* PACING_TYPE(TWO_WAY_FIXED).
* plu_slu_compression(rle)
* slu_plu_compression(lz9)
* description(single session mode);
*
* After adding the keyword, run CMVERIFY on the
* configuration file to verify the changes. Communications
* Manager/2 can then be started.
*
*
* APAR= JR08500
* HOST BACK UP LINK FOR A GIVEN PU - NEW FUNCTION.
*
* Communications Manager/2 1.11 does not support
* Host backup link when the primary link to host
* fails. APAR JR08500 adds host backup link support for
* dependent LU's. It is not supported for independent LU 6.2
* sessions.
*
* New Function: Adds support for backup host link for dependent
* sessions. To setup the host backup link, you need to define
* two links with the same (local) PU Name on DEFINE_LOGICAL_LINK
* verb in .NDF file. Then, indicate the backup link with the
* new backup link parameter. Same PU and LU definitions should
* be used at Host.
*
* Dependent LU definitions can be only on the host link for a PU
* that is defined as the primary host link. However, both primary
* and backup host links for a PU will use all LUs defined for that
* PU. The backup host link will be automatically activated if
* activation of the primary host link activation fails.
*
* NOTES:
* 1. The backup link is a backup only for dependent LU
* (gateway, LUA, or 6.2 dependent LUs) traffic.
* 2. The backup must be inactive except when automatically
* activated for use as the backup host link.
* 3. There is no automatic switch back to the primary link.
*
* To define a back-up link for Communications Manager/2 1.11:
* 1. Stop Communications Manager 1.11.
* 2. Create another link through panel interface or adding
* DEFINE_LOGICAL_LINK for the new link in .NDF file. No
* Partner LU's should be defined to the backup link.
* 3. Add "HOST_BACKUP_LINK(YES)" parameter in the
* DEFINE_LOGICAL_LINK for the backup link.
* 4. Set "ACTIVATE_AT_STARTUP(NO)" parameter in
* DEFINE_LOGICAL_LINK for the backup link.
* 5. Keep "PU_NAME" parameter in DEFINE_LOGICAL_LINK same as the
* primary link.
* 6. Verify the configuration file by "CMVERIFY cfgname" where
* cfgname is the name of your configuration file. Use /I
* option for SNA Phone Connect.
* 7. Start Communications Manager. If you also create a new DLC,
* you must reboot the workstation.
*
*
* JR08130: X.25 Dial Remote DTE and CP Names.
*
* Previous to this APAR, Communications Manager did not
* allow dial-out and dial-in environments where the
* host has multiple X.25 links unless either the CPNAME or
* the adjacent node_id match between the link definition
* and the XID exchanged during activation.
*
* Since the selected link can change, the remote DTE address
* is not guaranteed to be the same for each dial in connection.
* This change tests for an asterisk (*) X.25 remote DTE address
* and uses that definition even if the adjacent node id and
*
* Communications Manager also required that the
* remote DTE address match if it is specified. This change
* allows the remote DTE address to mismatch as long as the
* Partner CPNAME matched in the XID exchange.
*
* Communications Manager was updated to
* test for an asterisk (*) X.25 remote DTE address, then
* uses that definition even if the adjacent node id and adjacent
* CPNAME do not match.
*
* Now when remote DTE address changes, Communications Manager
* will check the FULLY QUALIFIED PARTNER CPNAME for the link.
* Further, the remote DTE address can mismatch as long as the
* Partner CPNAME matched in the XID exchange.
*
*
* JR08131: Fixed pacing in Communications Manager 1.11 (WR06150)
*
* To configure fixed pacing for a particular mode, there are
* two approaches:
*
* 1. UPDATING THE .NDF FILE:
* A new keyword, PACING_TYPE, was added to the DEFINE_MODE
* verb in the .NDF file. The valid values are
* ADAPTIVE and FIXED. The default is ADAPTIVE.
*
* Example: DEFINE_MODE mode_name(mode1)
* max_ru_size_upper_bound(4096)
* cos_name(#connect)
* default_ru_size(yes)
* max_negotiable_session_limit(1)
* min_conwinners_source(1)
* plu_mode_session_limit(1)
* receive_pacing_window(7)
* compression_need(requested)
* PACING_TYPE(FIXED)
* plu_slu_compression(rle)
* slu_plu_compression(lz9)
* description(single session mode);
*
* After adding the keyword, run CMVERIFY on the
* configuration file to verify the changes. Communications
* Manager can then be started.
*
* 2. UPDATING VIA A RESPONSE FILE:
* A new keyword, PACING_TYPE, was added to the MODE record
* for CID response files. This keyword has values of:
*
* 0 = Adaptive Pacing, 1 = Fixed Pacing
*
* The default is 0. The following example can be used
* in a CID response file to change an existing mode to
* use fixed pacing:
*
* Example: MODE = (
* NAME = mode1
* PACING_TYPE = 1
* )
*
*
*
* JR08314: LU62 Sessions remain active even when not needed.
*
* Previous to this APAR, Communications Manager/2 did not free LU6.2
* sessions even after they were no longer needed.This APAR fix allows one to
* modify the Communications Mgr/2 configuration file with a new
* parameter known as FREE_UNUSED_SESSIONS. You may invoke
* this new function as follows:
*
* Determine the name of your Communications Manager/2 configuration
* file. If you do not know the name, execute the command CMQUERY
* at an OS/2 command prompt while Communications Manager/2 is running.
* CMQUERY will return the name of the active configuration.
* For this example, assume the name is CMBASE.
*
* From an OS/2 window edit the file CMBASE.NDF, found in the
* CMLIB directory (where CMBASE is the name of YOUR Communications
* Manager/2 configuration file).
*
* The CMBASE.NDF file is an ASCII file that is readable. The first
* section in this file shows the DEFINE_LOCAL_CP verb and the
* associated parameters. See example below:
*
* DEFINE_LOCAL_CP FQ_CP_NAME(USIBMNR.MYCPNAME )
* DESCRIPTION(Created on 01-15-93 at 02:31p)
* CP_ALIAS(MYCPNAME )
* NAU_ADDRESS(INDEPENDENT_LU)
* NODE_TYPE(EN)
* NODE_ID(X'05D512A0')
* NW_FP_SUPPORT(NONE)
* HOST_FP_SUPPORT(YES)
* HOST_FP_LINK_NAME(HOST0001)
* add------------>FREE_UNUSED_SESSIONS(YES)
* MAX_COMP_LEVEL(NONE)
* MAX_COMP_TOKENS(0)
*
* Notice the 'add--------------->' indicator. This shows the new line
* that must be added to invoke this new function. Only enter the
* FREE_UNUSED_SESSIONS(YES) parameter (add---------------> is just to
* show you where the parameter is inserted).
*
* After adding the new line parameter, SAVE the change and then
* perform a C:\CMVERIFY CMBASE /e
* This will verify the configuration file change. Upon successful
* verification, STOP and RESTART Communications Manager/2 to invoke
* the new function.
*
*
*
* JR08473: SNA Gateway feature reactivation of HOST link
*
* When a downstream workstation connects to the Communications Manager/2
* SNA GATEWAY, and the link to the Host fails to activate,
* and the maximum activate links is exceeded, Communications Manager/2
* will retry the host link once every 30 minutes, rather than
* retry as each downstream workstation connects in to the SNA
* GATEWAY.
*
*******************************************************************
*
* Installation instructions:
*
* 1) Make a temporary directory, for example C:\cmtemp,
* the instructions will use c:\cmtemp as the example.
*
* 2) Download the files(s) in binary to your computer to C:\cmtemp
*
* 3) Execute the following command from c:\cmtemp:
* PKUNZIP2 cm2ap111.zip
* Three files will be unzipped into the C:\cmtemp directory,
* CM2ABASE.ZIP, CM2BBASE.ZIP and ANYNET.ZIP.
*
* The reason for the three zip files is that CM2AP111.ZIP will
* not fit on a single diskette. If you need to apply the
* APAR fixtest to another workstation via diskettes, you can
* copy CM2ABASE.ZIP, CM2BBASE.ZIP and ANYNET.ZIP onto diskettes.
* Next take the diskettes and copy the zip files
* into C:\cmtemp on the other workstation. Then continue
* with the installation instructions on the other workstation.
*
* 4) Stop Communications Manager, Communications Manager's
* Subsystem Management, all transaction programs (programs using the Communications
* Manager application programming interfaces).
* Stop and Close the Communications Manager trace facility.
* and exit all FFST/2 displays.
*
* 5) At an OS/2 prompt enter: CMKFMSMI 0 (This stops the Communications Manager
* Frame manager that is started in config.sys)
*
* 6) Back up the following files in the following directories:
*
* cmlib\acsapldr.exe
* cmlib\cmmh.msg
* cmlib\cmm.msg
* cmlib\lulist.exe
* cmlib\lutpm.exe
* cmlib\pluverb.h
* cmlib\lutpm.hlp
* cmlib\cmstart.exe
* cmlib\remmain.exe
* cmlib\cmverify.txt
* cmlib\cml2a.srv
* cmlib\cmpd.cmd
* cmlib\cmpd.pak
* cmlib\appnv.ctl
* cmlib\cmkfmsmi.exe
* cmlib\cmkfmde.sys
* cmlib\appnp.hlp
* cmlib\appnp.pml
* cmlib\appnp.pdl
* cmlib\dll\appc.dll
* cmlib\dll\cmkfmapi.dll
* cmlib\dll\appnutl.dll
* cmlib\dll\acsgwscp.dll
* cmlib\dll\appncfg4.dll
* cmlib\dll\acsrui.dll
* cmlib\dll\acssli.dll
* cmlib\dll\appncfg.dll
* cmlib\dll\ccdmain.dll
* cmlib\dll\acs3elue.dll
* cmlib\dll\acs3evs.dll
* cmlib\dll\acsipx.dll
* cmlib\dll\cpic.dll
* cmlib\dll\acsmptn.dll
* cmlib\dll\acssvc.dll
* cmlib\dll\lutab.dll
* cmlib\dll\acsrastd.dll
* cmlib\dll\cmfreedl.dll
* cmlib\dll\remapi.dll
*
* It is possible that some of these files will not be present on
* your system, depending on your configuration.
*
*
* 7) Execute the following command from the cmtemp subdirectory:
*
* PKUNZIP2 -d -o cm2abase.zip C:\
*
* where C: is the drive where Communications Manager/2 is installed. You
* should change this if Communications Manager/2 is installed on a
* different drive. The zip file is created such that the files will be
* placed into cmlib and cmlib\dll in the specified drive.
*
* 8) Execute the following command from the cmtemp subdirectory:
*
* PKUNZIP2 -d -o cm2bbase.zip C:\
*
* where C: is the drive where Communications Manager/2 is installed. You
* should change this if Communications Manager/2 is installed on a
* different drive. The zip file is created such that the files will be
* placed into cmlib and cmlib\dll in the specified drive.
*
* 9) If you are using ANYNET with Communications Manager/2 then
* execute the following command from the cmtemp subdirectory:
*
* PKUNZIP2 -d -o anynet.zip C:\
*
* where C: is the drive where Communications Manager/2 is installed. You
* should change this if Communications Manager/2 is installed on a
* different drive. The zip file is created such that the files will be
* placed into cmlib and cmlib\dll in the specified drive.
*
* 10) Reboot the workstation.
*
* 11) Communications Manager/2, and the other stopped functions can now be
* restarted.
*
*******************************************************************
*b010/p072
*******************************************************************
CM2AP111 ZIPBIN *