home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
wr07060a.zip
/
US7060B1.DSK
/
WR07060.INF
(
.txt
)
< prev
Wrap
OS/2 Help File
|
1995-05-03
|
71KB
|
1,948 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
IBM NTS/2 LAN Adapter and Protocol Support ServicePak WR07060
IBM PTF WR07060
This ServicePak will service LAPS V2.11 or higher. For levels below V2.11,
apply NTS/2 ServicePak WRx7020 or WRx7045 before applying this ServicePak. The
following versions of LAPS can be serviced with this ServicePak:
Version Product in which LAPS was included
LAPS V2.11 LAN Server 3.0
NTS/2 V1.0
LAPS V2.20 NTS/2 ServicePak WRx7020
LAN Distance V1.0
CM/2 V1.1
LAPS V2.20.1 LAN Server 3.0.1
LAN Distance V1.1
LAN Distance V1.1 ServicePak IPx7050
LAPS V2.20.2 NTS/2 ServicePak WRx7045
Communication Manager/2 V1.1 ServicePak
LAN Distance V1.1 (CD-ROM)
This package includes the separately installable NTS/2 BonusPak containing MAC
drivers for OEM adapter cards, new applets, an updated SRVIFS, and an upgraded
CID installation utility. See the BONUSPAK.INF on the BonusPak diskette for
additional information about the BonusPak content and installation.
Warning: - This ServicePak has a new method of installation using Corrective
Service Facility (CSF) version 2-B. Please review the entire Installation
section before proceeding. Service to Servers which use "Advanced Features" can
be complex.
Good Insurance!
Have appropriate Bootable Standalone Service Diskettes.
ΓòÉΓòÉΓòÉ 1.1. Affected SYSLEVEL Files ΓòÉΓòÉΓòÉ
After installation of this ServicePak, the Current CSD level of the following
SYSLEVEL file will indicate WRx7060 (where x is the country code):
SYSLEVEL.TRP IBM OS/2 LAN Adapter and Protocol Support
ΓòÉΓòÉΓòÉ 1.2. Trademarks ΓòÉΓòÉΓòÉ
The following are trademarks of IBM Corporation:
o Communication Manager/2
o IBM
o LAN Support Program
o OS/2
o Operating System/2
o PC LAN Program
o Presentation Manager
o Win-OS/2
The following are trademarks of other Corporations:
o ComPaq (ComPaq Computer Corporation)
o Extra! (Attachmate Corporation)
o Lotus 1-2-3 (Lotus Development Corporation)
o Lotus Notes (Lotus Development Corporation)
o Microsoft (Microsoft Corporation)
o Pentium (Intel Corporation)
o Rumba/400 (Wall Data Corporation)
o Rumba/3270 (Wall Data Corporation)
o SmartStart (ComPaq Computer Corporation)
o Ungermann-Bass (Ungermann-Bass, Inc.)
o Windows (Microsoft Corporation)
ΓòÉΓòÉΓòÉ 2. Installation ΓòÉΓòÉΓòÉ
This ServicePak uses Corrective Service Facility (CSF) version 2-B (provided on
the tool diskette of this ServicePak) for installation.
Complete instructions for the use of the updated SERVICE and FSERVICE commands
are provided with the CSF Version 2-B, README.INF file on the ServicePak Tool
Diskette. Please read the CSF instructions for information on the use of CSF
Version 2-B backup and restore capabilities.
Note: - Archiving is not enabled for this ServicePak.
Installing the ServicePak is essentially a three phase process:
Phase 1 - Quiesce the Target System
Stop all running applications.
Phase 2 - Install the ServicePak
Use one of the following methods to replace system files with those
provided on this ServicePak.
Selective Install
Redirected (CID) Install
Phase 3 - Return the Serviced System to Normal Operation
Perform a normal system boot. Also, Post Installation Procedures
may be necessary when servicing an NTS/2 level below Version 2.11.
Note: - If asked for permission to replace any files, respond Yes for hidden
or system files, or any private fixes that are indicated as newer than the
ServicePak files.
ΓòÉΓòÉΓòÉ 2.1. Selective Install ΓòÉΓòÉΓòÉ
This method will apply fixes to selected subsystems, partitions, and
directories: The Corrective Service Facility will handle Locked Files
automatically so boot diskettes are not required before applying service.
1. Insert the ServicePak tool diskette in the A drive.
2. At an OS/2 command prompt type "A:SERVICE" and press Enter.
3. Insert ServicePak diskette 1 when prompted.
4. Follow the prompts to the CSF SERVICEABLE PRODUCTS panel. Review the
serviceable products selected on the panel and deselect any products that
you do not want to service at this time. Then choose the SERVICE push
button.
5. Enter (optional) backup path then choose the OK push button.
6. If the APPLICATION IN USE locked files panel is presented, choose CONTINUE.
7. Follow prompts to complete the process.
8. Remove the diskette from drive A:, then perform the system Shutdown
procedure.
9. Reboot the system normally.
When problems such as insufficient disk space are encountered when performing
the Selective Install, use the Special Situation Install method to perform
service.
ΓòÉΓòÉΓòÉ 2.2. Redirected Installation (CID) Method ΓòÉΓòÉΓòÉ
This method is useful for those who are using the CID (Configuration,
Installation, and Distribution) Services as provided by IBM NTS/2. The
Selective Install method is recommended for Servers exploiting 386 HPFS
function, Fault Tolerance and/or Local Security.
While setting up a CID server is beyond the scope of this document, we have
provided a sample LAN CID Utility REXX Command file segment (WR_7060.CID) that
may prove useful in setting up a CID server for this ServicePak.
The sample WR_7060.CID assumes the following:
o The ServicePak Tool diskette files are placed on the code server using "XCOPY
A:\*.* /S" (or equivalent) in 'z:\img\csd\nts2\wr_7060' where 'z:' is the
drive seen by the client.
o The ServicePak files are placed on the code server using "XCOPY A:\*.* /S"
(or equivalent) at 'z:\img\csd\nts2\wr_7060' where 'z:' is the drive seen by
the client.
o The sample RESPONSE.FIL (or equivalent) is placed on the code server in
z:\rsp\csd\nts2\wr_7060.
o The following CID server directory structure contains the contents of the
ServicePak and the tool diskette:
img\csd\nts2\wr_7060 * Root directory of ServicePak diskette 1
img\csd\nts2\wr_7060 * ServicePak Tool diskette files
img\csd\nts2\wr_7060\FIX * No files
img\csd\nts2\wr_7060\FIX\TRP.1 * NTS/2 Fixes
rsp\csd\nts2\wr_7060 * RESPONSE.FIL (from sample on ServicePak
tool diskette)
o A log directory exists at 'z:\log\csd\nts2\wr_7060' for the log files.
ΓòÉΓòÉΓòÉ 2.3. Bootable Standalone Service Diskettes ΓòÉΓòÉΓòÉ
Sometimes it becomes necessary to boot from diskette in order to perform
certain operations on fixed-disk, like installing this ServicePak or running
CHKDSK /f.
All necessary files must be contained on diskette. Files from the fixed-disk
should not be referenced in A:\CONFIG.SYS or A:STARTUP.CMD. Otherwise Locked
Files can still exist on the fixed-disk.
Should the need arise to boot from diskette for any reason, you may:
o Use the Install diskette and Diskette #1 of OS/2 2.x or OS/2 3.x. Escape to
A:
o Create custom Bootable Standalone Service Diskettes from your licensed
materials. The makeup of these is dependent on the system to be serviced.
Instruction is available for:
Requesters and Entry Version Servers.
Advanced Version Servers.
CAUTION:
LAN Servers that utilize the Advanced features, Access Control Lists or Fault
Tolerance must use custom Bootable Standalone Service Diskettes. Regular HPFS
boot diskettes, such as the OS/2 Installation diskettes, CANNOT mirror changes
to Fault Tolerance partitions or access files/directories which are controlled
by local security.
ΓòÉΓòÉΓòÉ 2.3.1. Making OS/2 2.x Bootable Diskettes ΓòÉΓòÉΓòÉ
1. Make a copy of the OS/2 2.x or OS/2 3.x Installation Diskette and Diskette
#1. Call them SA#1 and SA#2 respectively.
2. Delete SYSINST2.EXE from Diskette SA#2.
3. Delete BUNDLE from Diskette SA#2 (this will be on OS/2 versions 2.1 or
greater).
4. Modify CONFIG.SYS on SA#2 as follows:
buffers=50
memman=noswap
protshell=a:\cmd.exe
protectonly=yes
libpath=a:\;
ifs=hpfs.ifs /c:64
set path=a:\;
set dpath=a:\;
5. Copy UHPFS.DLL from OS/2 Diskette #2 or C:\OS2\DLL to SA#2.
ΓòÉΓòÉΓòÉ 2.3.2. Making Advanced Server Bootable Diskettes ΓòÉΓòÉΓòÉ
MAKEDISK is an Advanced Server utility designed to make the necessary Bootable
Standalone Service Diskettes used in periodic maintenance of 386 HPFS systems.
1. Make a copy of the OS/2 2.x or 3.x Installation Diskette and Diskette #1.
Call them SA#1 and SA#2 respectively.
2. Delete SYSINST2.EXE from Diskette SA#2.
3. Delete BUNDLE from Diskette SA#2 (this will be on OS/2 versions 2.1 or
greater).
4. With Boot Diskette SA#2 in drive a: or b: run MAKEDISK from an OS/2 prompt.
Note: Syntax is MAKEDISK /BOOTDRIVE:d where d is the OS/2 boot drive.
For additional Information see the Network Administrators Reference:
Creating a 386 HPFS Boot Diskette, or LAN Server Utilities.
5. If using Fault Tolerance, add the Fault Tolerance files to the Bootable
Diskette SA#2.
6. Verify that the 386 HPFS Bootable Standalone Service Diskettes work
properly.
o Shutdown the system.
o Insert the Bootable Standalone Service Diskette SA#1 in the A drive.
o Reboot the system (Ctrl+Alt+Del, or other method).
o Determine if Local Security is working.
o Determine if Fault Tolerance is working.
ΓòÉΓòÉΓòÉ 2.3.3. Adding Fault Tolerance to 386 HPFS Bootable Standalone Service Diskettes ΓòÉΓòÉΓòÉ
386 HPFS Bootable Standalone Service diskettes require additional customizing
in order to properly update files on partitions which are mirrored.
The following steps may have to be done for each LAN Server with Fault
Tolerance since the configuration information transferred in step 3 can be
unique for each such system.
1. Copy the following four Fault Tolerance files from the first diskette of
the NTS/2 ServicePak to your Bootable Standalone Service Diskette SA#2.
1) DISKFT.SYS 2) FTD.MSG 3) FTATTRIB.EXE 4) FTCOPY.CMD
2. Add the following line to the CONFIG.SYS on the Bootable Standalone Service
Diskette SA#2.
DEVICE=DISKFT.SYS
3. At an OS/2 command prompt, make the current drive A:, and have the 386 HPFS
Bootable Standalone Service Diskette SA#2 in drive A. Type "FTCOPY" to copy
the customized Fault Tolerance configuration information to the 386 HPFS
Bootable Standalone Service Diskette SA#2.
Warning: Test your 386 HPFS Bootable Standalone Service Diskette before you
make any alterations to your system. This Diskette is the Master Key should
your system ever fail to boot from its hard drive.
ΓòÉΓòÉΓòÉ 2.4. Special Situation Install ΓòÉΓòÉΓòÉ
This method will apply all fixes to all partitions and directories:
FSERVICE is used for CID installation of this ServicePak, for multiboot systems
with IBM386FS on a drive other than the 'C' drive, or when problems, such as
insufficient memory for the locked file device driver or corrupted disk drives,
are encountered using the Selective Install method. It does require booting
from diskette to insure that there are no Locked Files during the install
phase.
Warning: - Ensure that all drives to be updated are clean by performing a
CHKDSK /F on each drive before FSERVICE is invoked. There will be no
opportunity to clean up the drives after FSERVICE is invoked.
1. Boot from the Bootable Standalone Service Diskettes.
2. Establish A: as the Current Directory.
3. Replace the Boot Diskette with the ServicePak Tool Diskette.
4. At the A: prompt, type "FSERVICE" and press Enter. Click here for
additional steps needed for multi-boot systems.
5. At the panel titled "Installing this ServicePak" press Enter (Option 1).
6. Follow the prompts provided by the Corrective Service Facility.
7. Reboot the system normally.
ΓòÉΓòÉΓòÉ 2.4.1. Updating IBM386FS Directory on a Multiboot System ΓòÉΓòÉΓòÉ
A new parameter has been added to the FSERVICE command to enable servicing the
IBM386FS directory when it resides on a bootdrive other than C:. Specify the
bootdrive containing the IBM386FS directory to be serviced as the /b parameter
on the FSERVICE command:
FSERVICE /b:d
(where d is the drive letter assigned to bootdrive)
Note: There is NO colon after the bootdrive 'd'.
Two methods are available for servicing the IBM386FS directories on multiple
bootable drives:
1. Run FSERVICE iteratively. That is, run FSERVICE /b: for each bootable drive
containing an IBM386FS directory.
2. Edit the RESPONSE.FIL (on the Tool diskette of this ServicePak) to add the
following parameter set after the :SYSLEVEL label:
:DIRLIST
d1:\IBM386FS where d1 = a bootable drive requiring IBM386FS service,
d2:\IBM386FS and d2 = another bootable drive requiring IBM386FS service.
:ENDDIRLIST
ΓòÉΓòÉΓòÉ 3. Post Install Procedure for IBM LAN Server 2.0 Users ΓòÉΓòÉΓòÉ
NTS/2 has two versions of NETBIOS.OS2. Using the wrong version of NETBIOS.OS2
can result in unstable LAN operation. Perform the following steps after
installing this ServicePak.
1. Select the LAPS Icon or run LAPS.EXE from the \IBMCOM subdirectory.
2. Select Configure from the LAPS logo window
3. With the Configure LAN transports radio button highlighted, Select
Continue....
Note: The Configure Workstation panel appears. You may elect to alter
your configuration at this time; LAPS automatically determines the
LAN version and selects the appropriate NETBIOS.OS2.
4. Select OK.
5. At the LAPS logo window, select Exit
6. Select the drive on which CONFIG.SYS is located.
7. Select Continue... from the CONFIG.SYS Updates window.
8. Continue through the remaining panels and reboot the system.
ΓòÉΓòÉΓòÉ <hidden> Locked Files ΓòÉΓòÉΓòÉ
Sometimes it is essential that programs own (become the master of) system
resources such as Memory Blocks, Communication Ports, and Files. When a program
stakes claim to a file, that file is said to be Locked; no other program is
allowed to alter (replace or write to) it until the owning program explicitly
removes the lock.
.DLL Files can become Locked by residing in a directory that is included in
the LIBPATH string of CONFIG.SYS.
For example, ACSLAN.DLL can be locked when \IBMLAN\DLL exists in the LIBPATH of
CONFIG.SYS.
ΓòÉΓòÉΓòÉ <hidden> Escape to A: from OS/2 Install Diskettes ΓòÉΓòÉΓòÉ
To obtain the A: prompt when using the OS/2 2.x Product installation diskettes
as Bootable Standalone Service Diskettes:
o Boot the system with Install Diskette in drive A.
o At the IBM Logo Screen - Insert Diskette #1, press Enter.
o At the Welcome Screen - Press Esc to Exit. (F3 for OS/2 3.x)
The A: prompt should appear. OS/2 Programs, including FSERVICE.EXE, can be run
from here.
ΓòÉΓòÉΓòÉ <hidden> Creating a 386 HPFS Boot Diskette Refer to ΓòÉΓòÉΓòÉ
Appendix H in:
Operating System/2 Local Area Network Server
Network Administrator Reference Volume1: Planning and
Installation
Version 3.0
ΓòÉΓòÉΓòÉ <hidden> LAN Server Utilities ΓòÉΓòÉΓòÉ
Refer to Appendix C, Miscellaneous Utilities MAKEDISK in:
Operating System/2 Local Area Network Server
Network Administrator Reference Volume3: Network Administrator
Tasks
Version 3.0
ΓòÉΓòÉΓòÉ 4. 802.2 Virtual Device Driver - Emulator Considerations ΓòÉΓòÉΓòÉ
To make your emulator easier to use, we recommend creating an icon on your OS/2
desktop for your emulator. In the discussions below relating to emulator
settings, d:\EmulPath refers to the drive and path of where your emulator
program is installed. CFGFILE refers to the name of your emulator
configuration file. The path and configuration File Name of your particular
emulator will be different from the examples below.
Warning: The following problems may occur:
o If a Windows emulator will not successfully start while another Windows
emulator is running, it may be necessary to start the emulators in reverse
order.
o If a Windows emulator will not successfully start while another Windows
emulator is running, it may be necessary to toggle (Ctrl-Esc) back and forth
to the OS/2 desktop or minimize the running emulator session before starting
the second emulator.
o It is not possible to run two WIN-OS/2 sessions while using XGA video mode.
Refer to the OS/2 README for additional information on restrictions using
WIN-OS/2 and XGA.
ΓòÉΓòÉΓòÉ 4.1. PC/3270 for DOS emulator ΓòÉΓòÉΓòÉ
On the Program panel, set the following parameters:
Path/Filename = d:\EmulPath\CFGFILE.BAT
Parameters = blank
Working Directory = d:\EmulPath
o On the Session panel, select DOS Full Screen.
o Before attempting to run PC3270 for DOS, edit your CFGFILE.BAT file adding
COMMAND.COM as the last line in the file. This must be done every time you
change your emulator configuration. Failure to add COMMAND.COM to your .BAT
file will cause PC3270 to exit when it attempts to return control to DOS.
ΓòÉΓòÉΓòÉ 4.2. PC3270 for Windows emulator ΓòÉΓòÉΓòÉ
PC3270 for Windows can run either as a regular Windows program (inside a
WIN-OS/2 session), or it can run 'seamlessly.' Seamless means the PC3270
windows appear on top of the OS/2 desktop directly, instead of appearing inside
a WIN-OS/2 command prompt.
To run PC3270 as a WIN-OS/2 application:
o Create a file called CFGFILE.BAT. This file should look like this:
@ECHO OFF
COPY d:\EmulPath\CFGFILE.CNF d:\EmulPath\$$TEMP$$.BAT > NUL
CALL d:\EmulPath\$$TEMP$$.BAT
ERASE d:\EmulPath\$$TEMP$$.BAT
CALL d:\EmulPath\SOMEFILE %1 %2 %3 %4 %5 %6 %7 %8 %9
o Create another file called SOMEFILE.BAT (this file is referenced in
CFGFILE.BAT:
@ECHO OFF
C:\OS2\MDOS\WINOS2\WINOS2
d:\EmulPath\PCSPDOS.EXE -END
o On the Program panel, set the following parameters:
Path/Filename = d:\EmulPath\CFGFILE.BAT
Parameters = blank
Working Directory = d:\EmulPath
o On the Session panel, select DOS Full Screen.
To run PC3270 Seamlessly:
o Create a file called CFGFILE.BAT. This file should look like this:
@ECHO OFF
COPY d:\EmulPath\CFGFILE.CNF d:\EmulPath\$$TEMP$$.BAT > NUL
CALL d:\EmulPath\$$TEMP$$.BAT
WINOS2.COM PCS3270.EXE
o On the Program panel, set the following parameters:
Path/Filename = d:\EmulPath\PC3270W.EXE
Parameters = blank
Working Directory = d:\EmulPath
o On the Session panel, select WIN-OS/2 window, click on Separate Session, then
click on WIN-OS/2 Settings.
o On the WIN-OS/2 Settings panel, add the following to the end of the DOS_SHELL
statement:
/C d:\EmulPath\CFGFILE.BAT
Note: If you start PC3270 for Windows, and get a message saying there is
invalid TSR information, then edit the CFGFILE.CNF file and change the line
'REM TSR=N' to 'REM TSR=Y'.
ΓòÉΓòÉΓòÉ 4.3. Attachmate's Extra! Extended for DOS ΓòÉΓòÉΓòÉ
o On the Program panel, set the following parameters:
Path/Filename = d:\EmulPath\CFGFILE.BAT
Parameters = blank
Working Directory = d:\EmulPath
o On the Session panel, select DOS Full Screen.
o Before attempting to run Extra! for DOS, you must edit your CFGFILE.BAT file,
and add COMMAND.COM as the last line in the file. This must be done every
time you change your emulator configuration. Failure to add COMMAND.COM to
your .BAT file will cause Extra! to exit when it attempts to return control
to DOS.
Note: It may be necessary to run the VDM configuration utility, LTSVCFG, with
the P=x parameter where x is a nonzero value indicating the number of half
seconds the deadman timer will wait before expiring. This will be necessary if
the emulator looks like it is hung. Typically this value should be set to 2 if
needed.
ΓòÉΓòÉΓòÉ 4.4. Attachmate's Extra! Extended for Windows ΓòÉΓòÉΓòÉ
o Create a file called EXTRA.BAT. This file should look like this:
@ECHO OFF
C:\OS2\MDOS\WINOS2\WINOS2
o On the Program panel, set the following parameters:
Path/Filename = d:\EmulPath\EXTRA.BAT
Parameters = blank
Working Directory = d:\EmulPath
o On the Session panel, select DOS Full Screen.
Note: The Extra! for Windows installation program normally modifies the
AUTOEXEC.BAT file to add its directory to the PATH statement, and to add a
DLCINTFC statement if Lan support is used. This information is also needed
when running under OS/2. We suggest you keep this information in your
AUTOEXEC.BAT file, exactly as Extra! for Windows placed it. Alternatively, you
can add the DLCINTFC statement to your EXTRA.BAT file instead of adding it to
AUTOEXEC.BAT.
ΓòÉΓòÉΓòÉ 4.5. PC Support/400 ΓòÉΓòÉΓòÉ
PC Support will not run correctly in DOS Emulation mode. To run PC Support,
you must start a version of DOS (such as DOS 5.0, etc.) that will run PC
Support. Please refer to the Master Help Index of OS/2 for information on how
to start a specific version of DOS. Search for 'Starting DOS.'
When you create a diskette or diskimage for a specific version of DOS, you
must insure the CONFIG.SYS file for that DOS version loads the following device
drivers:
DEVICE=C:\IBMCOM\PROTOCOL\LANVMEM.SYS
DEVICE=d:\EmulPath\EIMPCS.SYS
DEVICE=d:\EmulPath\ECYDDX.SYS
In addition, you may want to create an AUTOEXEC.BAT file for your specific DOS
version that automatically starts PC Support. To do this, invoke STARTPCS.BAT
from your AUTOEXEC.BAT file.
o On the Program panel, set the following parameters:
Path/Filename = *
Parameters = blank
Working Directory = d:\EmulPath
o On the Session panel, select DOS Full Screen, then click on DOS Settings.
o On the DOS Settings panel, set the following parameters:
DOS_STARTUP_DRIVE = A:\
KBD_CONTROL_BYPASS = ALT_ESC
In this example, DOS_STARTUP_DRIVE is set to A:\ with the assumption you are
loading the specific DOS version from diskette. If you load the specific DOS
version from a diskette image file on your hard drive, update the
DOS_STARTUP_DRIVE accordingly.
Warning: Some known problems:
The PC Support installation program may update the CONFIG.SYS file and add two
device drivers 'EIMPCS.SYS' and 'ECYDDX.SYS.' If these statements are in your
CONFIG.SYS, remove them. Under OS/2, these statements will instead be loaded
from your bootable DOS diskette.
Each Virtual DOS Machine (VDM) will need a separate APPC controller on the
AS/400. The controllers can be exactly the same except for the LAN destination
service access point (LAN DSAP: 08). A line in the CONFIG.PCS needs to contain
a matching TRSS entry (TRSS 08).
It is necessary to run the VDM configuration utility, LTSVCFG, with the P=x
parameter where x is a nonzero value indicating the number of half seconds the
deadman timer will wait before expiring. Typically this value should be set to
1 for using a single VDM and increased to 4 if additional VM Boot sessions are
active. When additional VM Boot sessions are active it is recommended to
decrease the MAXWAIT parameter in CONFIG.SYS to 1 second.
When running more than 2 sessions in a stress environment it may be necessary
to obtain OS/2 2.0 Service Pak (XRx6055).
For valuable information required for operating PC Support/400 in a VDM, please
reference IBM publication GG24-3856 entitled "Using DOS PC Support/400 in OS/2
V2 Virtual DOS Machines".
ΓòÉΓòÉΓòÉ 4.6. Wall Data's Rumba/400 emulator ΓòÉΓòÉΓòÉ
o Create a file called RUMBA.BAT. This file should look like this:
@ECHO OFF
D:\PCS\STARTRTR D:\PCS\CONFIG.PCS
C:\OS2\MDOS\WINOS2\WINOS2
In this example, D:\PCS is the directory where PC Support is installed.
Rumba/400 requires PC Support in order to run.
o On the Program panel, set the following parameters:
Path/Filename = d:\EmulPath\RUMBA.BAT
Parameters = blank
Working Directory = d:\EmulPath
o On the Session panel, select DOS Full Screen
ΓòÉΓòÉΓòÉ 4.7. Wall Data's Rumba/3270 emulator ΓòÉΓòÉΓòÉ
o Create a file called RUMBA.BAT. This file should look like this:
@ECHO OFF
d:\EmulPath\WDTOKTSR.EXE /R=16 /T=8
C:\OS2\MDOS\WINOS2\WINOS2
WDTOKTSR.EXE is required by Rumba/3270 in order to use Lan support. Refer to
the Rumba program documentation for more information about command line
parameters. The above parameters work in most cases.
o On the Program panel, set the following parameters:
Path/Filename = d:\EmulPath\RUMBA.BAT
Parameters = blank
Working Directory = d:\EmulPath
o On the Session panel, select DOS Full Screen.
ΓòÉΓòÉΓòÉ 5. TCP/IP for DOS - Considerations ΓòÉΓòÉΓòÉ
Before you can use TCP/IP under OS/2 2.0, you must set up certain DOS settings.
To create an icon and initialize the DOS settings, follow these steps:
o On the Program panel, set the following parameters:
Path/Filename = *
Parameters = Blank
Working Directory = C:\TCPDOS
(Assuming TCP/IP was installed on C:\TCPDOS)
o On the DOS Settings panel, click on 'Session' and set the following
parameters:
DOS_DEVICE = C:\TCPDOS\BIN\NETDEV.SYS
(Assuming TCP/IP was installed on C:\TCPDOS)
LTSVCFG.COM must be run with parameter D=1 before TCP/IP can run in a VDD. This
is necessary because TCP/IP uses the direct station link of the 802.2 protocol.
A slash is used to signify the adapter number.
Adapter Number Command to Run
Adapter 0 LTSVCFG D=1
Adapter 1 LTSVCFG / D=1
Adapter 2 LTSVCFG / / D=1
LTSVCFG can be included in the AUTOEXEC.BAT file to execute automatically. or
run manually from a DOS command prompt.
When running TCP/IP's file transfer application FTPD and FTP it is necessary to
clear the APPEND environment variable on both the server and client machines.
This can be done by commenting out the LOADHIGH APPEND C:\OS2;C:\OS2\SYSTEM
statement in the AUTOEXEC.BAT file, or by entering APPEND=* at the DOS command
prompt. This is necessary because if the files being transferred appear in the
APPEND path of the destination machine, the APPEND path will override the
specified destination path.
ΓòÉΓòÉΓòÉ 6. Things that Changed ΓòÉΓòÉΓòÉ
The following sections describe changes that have been made to the product's
executables, publications, and messages/helps.
ΓòÉΓòÉΓòÉ 6.1. NTS/2 Enhancements ΓòÉΓòÉΓòÉ
The following sections explain enhanced NTS/2 features. Those features that
have not appeared in previous ServicePaks are highlighted when this document is
displayed.
ΓòÉΓòÉΓòÉ 6.1.1. SRVIFS - Supports a maximum of 15 alphanumeric characters for NetBIOS names ΓòÉΓòÉΓòÉ
SRVIFS has been enhanced to support server and client NetBIOS names up to a
maximum of 15 alphanumeric characters (a maximum of 8 alphanumeric characters
was supported). NTS/2's SRVIFS utility THINIFS has also been enhanced to
support a maximum of 15 alphanumeric characters for NetBIOS names. This
includes values for the /req parameter and the /srv parameter. If using the
code server alias format "\\servername\alias" for the /srv parameter, the
server name can support up to 15 alphanumeric characters, however, the alias
name still has the restriction of a maximum of 8 characters.
SRVIFS files can be found in the SRVIFS zip file on the WRx7060 BonusPak
diskette. See the BonusPak.INF file on that diskette for additional
information.
ΓòÉΓòÉΓòÉ 6.1.2. THINLAPS - Supports non-NTS/2 Supplied MAC Drivers ΓòÉΓòÉΓòÉ
THINLAPS supports the installation and configuration of MAC drivers that do not
ship with NTS/2. This could include MAC drivers that are shipped by IBM after
the release of NTS/2 or MAC drivers that are supplied by other manufacturers.
New MAC drivers shipped by IBM are available on the NTS/2 BonusPak available on
many bulletin boards and included in this package.
To use a MAC driver that did not ship with NTS/2, do the following on the CID
code server:
1. Copy the MAC driver and its associated files (except for the .MSG files)
into the <path>\IBMCOM\MACS directory.
2. Copy the .MSG files into the <path>\IBMCOM directory.
where <path> is the target directory that was indicated when the LAPSDISK
utility was run to copy the NTS/2 disk to the code server.
After the MAC driver files have been copied to the code server, use THINLAPS to
configure LAPS on the boot diskettes for use with the adapter that the new MAC
driver supports. To do this, run THINLAPS specifying the NIF file associated
with the new MAC driver.
Following is an example of a PROTOCOL.INI file created with THINLAPS:
[protman]
driverName = protman$
[netbeui_nif]
driverName = netbeui$
bindings = mac
; If running on an ethernet network, remove the semicolon from
; the "ETHERAND_TYPE =" statement to change the protocol
; convention from IEEE 802.3 to DIX 2.0.
; ETHERAND_TYPE = "D"
[mac]
drivername = ibmtok$
; EARLYRELEASE
ADAPTER = "PRIMARY"
; NETADDRESS = ""
MAXTRANSMITS = 6
RECVBUFS = 2
RECVBUFSIZE = 256
XMITBUFS = 1
; XMITBUFSIZE =
; INTERRUPT =
PCMCIA
; RAM = 0x
RINGSPEED = 4
; RAMSIZE =
; MMIO = 0x
The following list describes the keyword types in the PROTOCOL.INI example:
1. ADAPTER, MAXTRANSMITS, RECVBUFS, RECVBUFSIZE, XMITBUFS, RINGSPEED
o These are keywords with decimal values that have default values associated
with them.
2. XMITBUFSIZE, INTERRUPT, RAMSIZE
o These are keywords with decimal values that do not have default values
associated with them. To activate one of these keywords, remove the
semicolon in column one and place a valid value after the equal sign. For
example, XMITBUFSIZE = 256.
3. PCMICA
o This is a keyword without a value that is defaulted to ON in the .NIF
file.
4. EARLYRELEASE
o This is a keyword without a value that is defaulted to OFF in the .NIF
file. To activate this keyword, remove the semicolon in column one.
5. NETADDRESS
o This is a keyword with a string value that does not have a default value
associated with it. To activate this keyword, remove the semicolon in
column one, and place the desired value within the double quotes. For
example, NETADDRESS = "400000274715".
6. RAM, MMIO
o These are keywords with hexadecimal values that do not have default values
associated with them. To activate one of these keywords, remove the
semicolon in column one and place a valid hexadecimal value after the 0x.
For example, RAM = 0xA00.
Note: Keywords requiring values that do not have default values associated
with them and keywords not requiring values that are defaulted to OFF are
remarked out with a semicolon in column one in the PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.1.2.1. User Modification of PROTOCOL.INI: ΓòÉΓòÉΓòÉ
The PROTOCOL.INI file created by THINLAPS is sufficient for most network
environments. However, since the PROTOCOL.INI file may not be appropriate for
the network environment, some parameter values in the PROTOCOL.INI file that
THINLAPS created may need to be adjusted. Use an ASCII editor to view and
change the PROTOCOL.INI file created on the target drive after running
THINLAPS.
Because THINLAPS supports the configuration of non-IBM supplied MAC device
drivers, all keywords with the MAC NIF files are defined in the resulting
PROTOCOL.INI file. Following are guidelines for modifying the MAC section in
the PROTOCOL.INI file:
o To modify the value of a keyword without a semicolon in column one, edit the
value in the same format that it appears in the file (decimal, hexadecimal,
string, and so on).
o To modify the value of a keyword with a semicolon in column one, remove the
semicolon from column one, if there is:
o NO "=" this task is complete.
o Nothing following the "=" Supply a decimal value. For example, 129.
o A 0x following the "=" Supply a hexadecimal value after the 0x. For
example, 0xA00.
o Quotes following the "=" Supply an ASCII string inside the quotes. For
example, "400000274715"
ΓòÉΓòÉΓòÉ 6.1.2.2. NOTES: ΓòÉΓòÉΓòÉ
o All keywords from the NIF file occur in the PROTOCOL.INI file.
o Keywords that have defaults are activated and have the default value
provided.
o Keywords requiring values that do not have default values associated with
them are remarked out with a semicolon in column one.
o Keywords that do not have values that are defaulted to ON are activated.
o Keywords not requring values that are defaulted to OFF in the .NIF file are
remarked out with a semicolon in column one.
o If there are any questions concerning the keywords or valid values for each
of the keywords, use an ASCII editor to view the MAC NIF file, which
describes each of the keywords and its valid values.
ΓòÉΓòÉΓòÉ 6.1.2.3. RESTRICTIONS: ΓòÉΓòÉΓòÉ
o THINLAPS supports only the configuration of one network adapter.
o THINLAPS provides only NetBIOS support.
o THINLAPS installs only in the root of the target drive.
o THINLAPS works only with valid MAC NIF files. NTS/2 provides an applet
called SNIFFLE that validates .NIF files. VIEW the BonusPak.INF file on the
NTS/2 WR07060 BonusPak diskette for more information on the SNIFFLE applet.
ΓòÉΓòÉΓòÉ 6.1.3. IBMTOK.OS2 MAC device driver upgraded to version 2.6 ΓòÉΓòÉΓòÉ
The IBMTOK.OS2 MAC device driver has been upgraded to Version 2.6. This new
version of the IBMTOK.OS2 MAC driver has added support for both the IBM Auto
16/4 Token-Ring MC Adapter Card and the IBM Auto 16/4 Token-Ring ISA Adapter
Card.
ΓòÉΓòÉΓòÉ 6.1.4. MAC Drivers - New supported MAC drivers for NTS/2 ΓòÉΓòÉΓòÉ
The following is a list of the new supported MAC drivers for NTS/2. These MAC
drivers can be found in the appropriate zip files on the BonusPak provided with
this ServicePak.
o \3com\elnk3.os2
o \olicom\olitok16.os2
o \racore\rtr16nds.os2
o \ti\tr2kndis.os2
o \cabletrn\e11nd.os2
o \cabletrn\e21nd.os2
o \cabletrn\e31nd.os2
o \cabletrn\t20nd.os2
o \cabletrn\t30nd.os2
o \cray\pc04.os2
o \ibm\ibmeni.os2
o \ibm\ibmenii.os2
o \ibm\ibmmpc.os2
o \ibm\ibmtokmp.os2
o \intel\exp16.os2
o \intel\intel16.os2
o \intel\intel32.os2
ΓòÉΓòÉΓòÉ 6.1.5. TRACENAMES - New Parameter for NETBIOS Traces ΓòÉΓòÉΓòÉ
The TRACENAMES parameter is used to limit tracing activity to the interaction
between specified machines. Prior to the offering of this parameter, tracing at
the transport level picked up all frame activity on the line, causing the trace
buffer to quickly fill with irrelevant frame records. This parameter is ideal
for isolating a problem between a server and requester on a large network.
Tracing is limited by selecting NETBIOS names on remote machines using the
TRACENAMES parameter. Names can be specified as either a 16-byte ASCII or
32-byte Hex value. Up to four names can be selected in either format. The
asterisk wildcard character (*) can be used in the ASCII format for ease of
use, or to increase the number of remote names traced if machines have similar
names. All names must reside on the same line as the TRACENAMES parameter.
Incorrect length or invalid hex numbers cause an error and NETBEUI will not
load.
TRACENAMES works in conjunction with the OS2TRACEMASK parameter and the
TRACEOFF parameter already available for NETBEUI in NTS/2 version 1.0 and LAN
Server 3.0. The OS2TRACEMASK must be set to the necessary nonzero values to
activate any NETBIOS traces. The recommended setting is 0x07FF. NDIS activity
will not be filtered if the NDIS bits are activated in OS2TRACEMASK.
The TRACENAMES parameter must be inserted into the PROTOCOL.INI file using an
editor and is not yet a part of the LAPS config and install tool. TRACENAMES
must be placed only in the NETBEUI_nif section. The following example shows the
general location and format of the parameter:
PROTOCOL.INI
[NETBEUI_nif]
DriverName = netbeui$
Bindings = IBMTOK_nif
...
...
DLCRETRIES = 5
OS2TRACEMASK = 0x07FF
TRACENAMES = "req1 " "req2 " "req3 "
Other valid TRACENAMES formats are:
TRACENAMES = "72617131202020202020202020202000" "req2 *"
TRACENAMES = "req*************" "72617131202020202020202020202020"
Activity relevant to the remote NETBIOS is traced. This includes NCBs issued
with that remote name, as well as all session activity related to that remote
name. All statuses from the lower layers are reported whether related to the
remote station or not. Frame activity between the remote and local machines is
traced by Local Session Number(LSN) after the session is established with the
remote machine. A maximum of 12 active sessions is traced.
Some NCBs are not associated with a remote name or LSN and are not traced:
o Add Name
o Add Group Name
o Delete Name
o Cancel
o LAN Status
o Session Status
o Receive Broadcast Datagram
o Send Broadcast Datagram
NCB.Reset is traced even though it is not related to sessions or specific
names. Datagrams and other UI frames are traced if they contain a remote name
specified in TRACENAMES. RECEIVE.ANY type commands are traced on completion if
they report a session event related to a specified remote machine.
ΓòÉΓòÉΓòÉ 6.1.6. ODI2NDI Obtains Universal Address Automatically ΓòÉΓòÉΓòÉ
For ODI2NDI.OS2(V1.0), configuration of the NETADDRESS parameter was required,
even if the user wanted to use the Network adapter universally administered
address. This requirement is necessary because ODI2NDI must provide the
NETADDRESS to the ODI protocol (IPX) before ODI2NDI can obtain the adapter
netaddress through the NDIS interface.
ODI2NDI.OS2(V1.1) is modified so that it obtains the Network adapter universal
address automatically when the NETADDRESS parameter is not configured for
ODI2NDI.OS2. To take advantage of this enhancement, the following manual
modifications of CONFIG.SYS are required.
1. Configure ODI2NDI for a Network adapter MAC using the LAPS configuration.
2. Manually perform the following updates to CONFIG.SYS:
a) Locate the Network adapter MAC device driver statement in CONFIG.SYS.
For example, for IBM Token Ring Network Adapters, the MAC device driver
statement is:
DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2
b) Position the MAC device driver statement after the PROTMAN.OS2 device
driver statement, but before the ODI2NDI.OS2 device driver statement in
the CONFIG.SYS file. An example CONFIG.SYS fragment is:
:
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
:
:
DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2
:
:
REM --- NetWare Requester statements BEGIN ---
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE
device = C:\ibmcom\protocol\odi2ndi.os2
:
:
c) Save the modified CONFIG.SYS. The computer must be restarted for the
change to take effect.
The manual updates to the CONFIG.SYS file need to be done only the first
time the ODI2NDI protocol is configured for a Network Adapter MAC.
Modifying ODI2NDI or MAC parameters does not require additional updates to
CONFIG.SYS.
Note: This enhancement does NOT work with ALL Network adapters. If the
enhancement does not work with the Network adapter on the updated
computer, message LT80227 is displayed when the computer is started.
This message is also logged in the LANTRAN.LOG file located in the
IBMCOM subdirectory. If message LT80227 occurs, use the LAPS
configuration utility to configure the NETADDRESS for ODI2NDI.OS2.
ΓòÉΓòÉΓòÉ 6.1.7. LAPS Icon on the Desktop ΓòÉΓòÉΓòÉ
After NTS/2 LAN Adapter and Protocol Support (LAPS) has been installed and
configured on an OS/2 2.x system, a LAPS icon is placed in the System Setup
folder. Double clicking on the icon brings up the LAPS
installation/configuration utility.
ΓòÉΓòÉΓòÉ 6.2. NTS/2 Fixes ΓòÉΓòÉΓòÉ
The following sections describe APAR and Non-APAR defects corrected in this
ServicePak. Descriptions are in numerical order by ServicePak. Corrections new
for WRx7060 (not fixed in a previous ServicePak) are highlighted on the
display.
ΓòÉΓòÉΓòÉ 6.2.1. NETBIOS Protocol Stack Defects ΓòÉΓòÉΓòÉ
Files that changed:
\IBMCOM\PROTOCOL\NETBEUI.OS2
\IBMCOM\PROTOCOL\NETBEUI.NIF
\IBMCOM\PROTOCOL\NETBIOS.OS2
\IBMCOM\LT0.MSG
\IBMCOM\LT0H.MSG
ΓòÉΓòÉΓòÉ 6.2.1.1. APAR fixes ΓòÉΓòÉΓòÉ
o APAR IC06827 - NETBIOS RETURNS 0x4E FOR RING BEACONING
In the event of a beaconing ring for more than 60 seconds, NetBIOS will
return a 0x4E return code, clean queues, clean up any shared names, and force
a hard reset. Similar events will occur with a cable pull with the exception
being a return code of 0x4F instead of 0x4E.
o APAR IC07036 - FRAME LENGTH INCORRECT IN A SIDEBAND/ETHERNET ENVIRONMENT
Frame length field was incorrect when a small frame was transmitted in an
Ethernet environment and netbeui sideband enabled.
o APAR IC07038 - NCB.STATUS RETURNED INCORRECT LAN TYPE
NCB.STATUS returned LAN type Token Ring even if the LAN connectivity was
Ethernet.
o APAR IC07151 - NETBEUI ENHANCEMENT FOR SMP ARCHITECTURED SYSTEMS
Netbeui module was enhanced to run on SMP architectured systems.
o APAR IC07192 - NETBIOS RECEIVE.ANY RETURNS CORRUPTED DATA
RECEIVE.ANY NetBIOS command that was aborted because of a hangup, returned an
incorrect name ID in the NCB_NUM field. This caused the RECEIVE.ANY to
return with an incorrect return code of 0x13.
o APAR IC07262 - NETBEUI TRAP ON LAN SERVER ULTIMEDIA SERVER
LAN Server Ultimedia using FDDI connectivity removes priority sends from the
send queue based on the number of priority sends. With the fcpriority set to
5 on both the server and client workstations, netbeui failed to test for an
empty queue condition and a trap D occurred. The fix also checks if the
connectivity is FDDI and if so, the bandwidth ack code is disabled but
netbeui still sends frames at priority.
o APAR IC07768 - NCB.STATUS INDICATES NEGATIVE VALUE FOR NCB COUNTER
NCB.STATUS indicated an incorrect value for the current number of free NCBs.
o APAR IC07858 - NEW NETBEUI MESSAGE LT00108 CAUSES TRAP IN IBMTOK.OS2 DRIVER
New NETBEUI message LT00108 caused a trap to occur in the IBMTOK.OS2 driver.
This problem only occurred in LAPS syslevel 2.20.3.
o APAR IC07914 - NETBIOS TRAPS ATTEMPTING SHORT TERM MEMORY LOCK
NetBIOS passed a bad parameter to the DevHlp short term memory lock if a
DevHlp long term memory lock failed. The bad parameter caused the trap to
occur.
o IC08092 - NEW NetBIOS ERROR MESSAGES
Created new NetBIOS error messages. These new messages indicate when a
system has run out of UI buffers or datagram buffers (LT00108), a request to
use a free NETBEUI GDT selector has failed (LT00105).
o IC08278 - DEFAULT NETBEUI CONFIGURATION PARAMETERS CHANGED
The following NETBEUI default configuration parameters were changed for
performance enhancements:
1. SELECTORS - from 5 to 15
2. T1 - from 500 to 1000
3. NETBIOSRETRIES - from 8 to 2
4. DATAGRAMPACKETS - from 2 to 10
5. LOOPPACKETS - from 1 to 8
6. DLCRETRIES - from 5 to 10
o IC08503 - NETWORK RESOURCE RESERVATION AUTOFAIL FUNCTION IS INCORRECT
LAN Server Ultimedia, Network Resource Reservation (NRR) and autofail
function did not work correctly.
o IC08654 - FILE TRANSFER CAUSES FILE DATA CORRUPTION
Transfering of files on a fast processor occassionly caused data corruption
in the resulting file.
o IC08773 - NAME DEREGISTERED CONDITION AFTER CANCEL ISSUED TO NCB.CALL
After a NCB.CALL command was cancelled after the NAMEQUERY was broadcasted.
An incorrect NAME_DEGREGISTERED (0x0f) return code was returned as the
NCB.CALL was completed.
o IC09159 - DATA FROM TIME-OUT SEND STAYS ON SEND QUEUE
NCB.SEND times out, but a pointer to the user's data was still remaining on
the send queue to be flushed later. This caused the possibility of the user
to overwrite that data buffer, and bad data was sent.
o IC06115 - Duplicate LAA Causes Errorous Server Name-In-Conflict
Two LAN requesters with the same LAA causes a name-in-conflict frame to be
sent indicating that the Server's name is in conflict. The name-in-conflict
frame caused the Server to remove it's NETBIOS name, shutting down the
Server.
o IC06224 - NETBEUI Stack Corruption Causes Various Session Control Problems
Corrupted NETBEUI stacked caused session abends and Trap E.
o IC06398 - Pulled PC-NET Cable Fails To Provide Proper NETBIOS Return Code
When executing NETBIOS applications and the PC-NET cable is pulled, all
NETBIOS commands appeared to be executing (no return code to indicated a
NETBIOS reset was needed). A pull PC-NET cable causes a network status of NO
CARRIER and the adapter is NOT closed. NETBIOS now waits 60 seconds before
returning a return code to indicate that a NETBIOS reset is needed.
o IC06414 - NETBIOS Reset Returns Incorrect Resource Information
When a NETBIOS reset is issued to an adapter that is not being used by LAN
Server, the reset returns incorrect resource information and completes with a
return code 0x09. This problem was introduced in NTS/2 CSD WR07020.
o JR07633 - NETBIOS Fails To Detect Bad PC-NET Card During Initial Adapter Open
During IPL, NETBIOS failed to execute a check on the hardware status bits
during the initial open adapter. If the PC-NET card was open but the
hardware status bits indicated a problem, NETBIOS never detected it.
o IC04951 - UNC Name failures with IBM Ethernet
References to a resource by UNC names failed with error code SYS0240 on the
server that was working on the NETBEUI stack with IBM Ethernet.
o IC05402 - SOURCE ROUTING FIXES IN NETBEUI
Fixes were required for receiving frames on a link that crosses
source-routing bridges - the route of the incoming frame should not be
assumed to be the same as the route used for outgoing frames. For TEST
frames received with 2 bytes of Routing Information, the TEST response was
built incorrectly.
o IC05486 - TRAP IN NETBEUI ON A VALUEPOINT MACHINE
Residual code from an OS/2 EE 1.3 environment remained in NETBEUI. Residual
code caused the Trap D.
o IC05526 - HPFS386 SIDEBAND TRAP D ON ETHERNET
When running HPFS386 on Ethernet and attempting to copy a file from a
redirected drive, a Trap D occurred at CS:C08 EIP:8A5.
o IC05551 - TRAP D IN NETBEUI - INITDS CORRUPTED
Trap D was caused by an invalid selector for low memory data segment.
o IC05673 - Four Separate Symptoms
o IC05673 - 1) SESSION NOT ESTABLISHED IF SABMES ARRIVE AT WRONG TIME
If sessions were being brought up simultaneously on two machines, SABMEs and
UAs can conflict causing session establishment to fail. The data area is
then corrupted because the link state is wrong.
o IC05673 - 2) RECEIVE BROADCAST LOOPING
When two or more applications have a receive_broadcast NCB outstanding, issue
the next receive_broadcast on appendage. NETBEUI goes into a loop processing
the appendage NCB as an additional receive on the receive_broadcast queue.
o IC05673 - 3) SESSION_ALIVE SENT WITH INCORRECT LSN NUMBER CAUSES CORRUPTION
Session_Alive sent with incorrect LSN number causes corruption of the NTE
Listen queue. Links can drop afterward. Fix was to correct sending of
Session_Alive frame to have correct LSN number only from links in Normal
state.
o IC05673 - 4) ADJUST ORDER OF SABME/UA RESPONSES
Reordered processing of link establishment and closing prevents case of extra
receive ready, or FRMR.
o IC05780 - STARTING LS 3.0 WHILE 3270 COMING UP CAUSES COM505 ERROR -
If starting LAN Server and Communications Manager 3270 feature at the same
time, Communications Manager 3270 will hang with COM505 Error.
o IC05794 - NETBIOS RESET RETURNS RC=23
Applications on Token Ring Network can issue "Reset" before NETBIND has
completed. When this occurs, NETBIOS returns RC=38 (Requested Resource Not
Available) and then RC=23 (Invalid LAN Adapter Number). Serialization of the
NETBIND execution process can solve the problem. This fix increases the
number of "Reset Retries" which should mask any such race condition.
o IC05869 - TRAP E IN NETBEUI
Trap E occurs during Remote IPL of OS/2 2.0 or OS/2 2.1.
o IC05902 - XMIT_TEST_CMD RESPONSE LOST BY NETBEUI
Under certain circumstances Transmit_Test_Cmd is rejected by Netbeui and
passed to the next protocol stack.
o JR06350 - Redirector failing to Reset
NETBEUI was clearing a flag bit whether it actually issued the hard reset or
not. Clearing this flag bit when a different flag bit was set prevented
NETWKSTA.SYS from issuing the reset.
o JR06550 - CLIENT REMOTE BUSY STATE CAUSED SERVER HANG
Requester workstations were in a ReMoteBusy state causing the Server to fill
up the I-Frame buffer with SessionAlive frames. Eventually this caused the
Server to hang if the requester workstations remained in a ReMoteBusy state.
ΓòÉΓòÉΓòÉ 6.2.1.2. Other fixes ΓòÉΓòÉΓòÉ
o RING 3 APPLICATION DOESN'T GET IMMEDIATE BAD RETURN CODE
Ring 3 applications was not given back an immediate bad returned code.
o Access Denied Copying a 583120 Byte File To Server
When attempting to copy a 583120 byte file from a requester to a HPFS386
server, an access denied was caused by NETBEUI.
o NETBIOS NCB.STATUS Failed To Return Correct Datagram Size
The datagram length was calculated incorrectly causing data to be lost.
o NAME-IN-CONFLICT Message
When a NAME-IN-CONFLICT occurs, a NAME-IN-CONFLICT message LT00102 will be
logged to the LANTRAN.LOG file indicated the NETBIOS name-in-conflict and the
node address of the workstation sending the NAME-IN-CONFLICT frame. When a
NAME-IN-CONFLICT occurs with a LS Server name, the message will also pop-up
to the screen.
o Prevent NETBIOS Timers From Wrapping
NETBIOS timers are now set to maximum value if wrapping occurs.
o NETBIOS returns FF Return Code As Final NETBIOS Return Code
A NCB.SEND command completed on interrupt before the NCB.SEND was put on a
queue with a FF pending code. The final return code was overwritten with FF.
Some NETBIOS applications received a NETBIOS return code 13 due to this
problem.
o Configuration Of Different Netbios Transports Causes Trap D
A trap D occurred in NETBIOS.OS2 when two different NETBIOS transports were
configured with one of them having insufficient resources configured in
protocol.ini for what was requested in ibmlan.ini file. The trap occurred on
the first NETBIOS command issued other than a reset.
o NETBEUI INITIALIZATION FAILS
Some configurations caused NETBEUI to fail to initialize.
o INCORRECT PACKET SIZE BROUGHT DOWN LAN SERVER 3.0
An Ethernet-only requester reaching a token-ring Busmaster server through an
8209 bridge eventually caused the server to have multiple sessions and then
the server could not communicate with the Ethernet requester or the
token-ring requesters. The packet size was being altered by the 8209 bridge.
o NETBEUI WAS NOT LOOKING FOR 2 IN MINOR NDIS VERSION IN THE COMMON
CHARACTERISTICS TABLE
To determine if a MAC driver supports an extension to the MAC
Service-Specific Characteristics, NETBEUI should be looking for a 2 in the
Minor NDIS Version in the Common Characteristics table.
o ILLEGAL FRAME SIZE CAUSED TRAP D
When an illegal frame size was checked, it caused a Trap D in NETBEUI.
o TRAP D WHILE RUNNING NETSERV.EXE
A Trap D occurred in CS:OC78 EIP:EC9
o NETBIOS FAILED TO INITIALIZE ON ANY OS/2 VERSION GREATER THAN 2.0.
Install NTS/2 on OS/2 2.1 and configure for NETBIOS. During IPL, NETBIOS
failed to initialize. This indicated the wrong version of the operating
system.
o AFTER RUNNING A LONG PERIOD OF TIME, NETBIOS RETURN ERROR 22
Too many outstanding NCBS (un_freed) cause NETBIOS to return "to Many
Commands Pending" (RC=22). This occurs over a varying period of time
depending on LAN activity.
ΓòÉΓòÉΓòÉ 6.2.2. IBM Token Ring MAC Driver Defects ΓòÉΓòÉΓòÉ
Files that changed:
\IBMCOM\MACS\IBMTOK.OS2.
ΓòÉΓòÉΓòÉ 6.2.2.1. APAR fixes ΓòÉΓòÉΓòÉ
o IC07131 - XMIT_STATUS Field Incorrect In a SCION TransmitConfirm.
The xmit_status field in a SCION TransmitConfirm subsequent to a bridge frame
forward indicates the status of the transmitted frame. Incorrect values were
being stored in this field.
ΓòÉΓòÉΓòÉ 6.2.2.2. Other fixes ΓòÉΓòÉΓòÉ
There are no non-APAR fixes for IBM Token Ring MAC Driver.
ΓòÉΓòÉΓòÉ 6.2.3. IBM Token Ring Busmaster MAC Driver Defects ΓòÉΓòÉΓòÉ
Files that changed:
\IBMCOM\MACS\IBMTRBM.OS2.
ΓòÉΓòÉΓòÉ 6.2.3.1. APAR fixes ΓòÉΓòÉΓòÉ
o JR05729 - BUSMASTER DOES NOT RECOVER FROM LOBE FAULT.
LAN Server/Requestor 2.0 could not be restarted on machines equipped with
Busmaster cards after the cable was unplugged and replugged.
o JR06486 - BUSMASTER TRAP D UNDER HEAVILY STRESSED NETWORK
The Busmaster driver was performing a call that was not legal at the time.
This caused a Ring 0 Trap D.
ΓòÉΓòÉΓòÉ 6.2.3.2. Other fixes ΓòÉΓòÉΓòÉ
o BUSMASTER UNABLE TO RE-ENTER RING AFTER DUPLICATE ADDRESS
One machine booted and got a particular token ring address. Another machine
(with Busmaster) booted requesting the same address, and got a duplicate
address indication, closing the adapter. The first machine left the ring,
freeing the address. Any attempt to reopen the previously failed busmaster
adapter using Communication Manager failed, still indicating a duplicate
address.
o WRONG FILTER VALUE USED
Prior to deleting an address, the first byte of the address was checked
against 80h, which is the equivalent of universal group. It should be checked
against C0h, which is local group. This caused what was accepted in the add
to be rejected in the delete. Making this change created consistency with
the add address.
ΓòÉΓòÉΓòÉ 6.2.4. IBM Token Ring 16/4 Adapter II (IBM16TR.OS2) ΓòÉΓòÉΓòÉ
Files that changed:
\IBM16TR\IBM16TR.OS2
\IBM16TR\IBM16OS2.NIF
ΓòÉΓòÉΓòÉ 6.2.4.1. APAR fixes ΓòÉΓòÉΓòÉ
There are no fixed APARs for IBM Token Ring 16/4 Adapter II
ΓòÉΓòÉΓòÉ 6.2.4.2. Other fixes ΓòÉΓòÉΓòÉ
o IBM Token Ring 16/4 Adapter II MAC Driver Upgraded to Version 3.0
The IBM Token Ring 16/4 Adapter II MAC Driver found on the NTS/2 Additional
Driver Diskette has been upgraded from Version 1.0 to Version 3.0.
ΓòÉΓòÉΓòÉ 6.2.5. Configuration Defects (LAPS) ΓòÉΓòÉΓòÉ
Files that changed:
\IBMCOM\DLL\LAPSPM.DLL
\IBMCOM\DLL\ LAPSCID.DLL
\IBMCOM\DLL\IBMLXCFG.DLL
\IBMCOM\IBMLXCFG.HLP
\IBMCOM\LAPS.EXE
\IBMCOM\XI1.MSG
\IBMCOM\LAPSICON.EXE
\IBMCOM\LAPSRSP.EXE
\IBMCOM\THINLAPS.EXE
\IBMCOM\LAPSDISK.EXE
ΓòÉΓòÉΓòÉ 6.2.5.1. APAR fixes ΓòÉΓòÉΓòÉ
o APAR IC06825 - KEYPAD DOES NOT FUNCTION CORRECTLY WHEN CONFIGURING LAPS
With NUMLOCK ON, the numeric keypad did not function correctly. The 2,3,8
and 9 keys behaved as cursor down, page down, cursor up and page up.
o IC05711 - THINLAPS FAILS TO REMOVE PREVIOUS INVOCATION
If THINLAPS was executed more than once to a diskette, then multiple LAPS
device and run lines were left in CONFIG.SYS file.
o IC05794 - RUN STATEMENT CHANGED TO A CALL STATEMENT FOR NETBIND.EXE
During IPL the netbind executable in the config.sys binds the configured
protocols with the configured adapter cards. On fast processor systems,
NetBIOS applications were attempting to issue NetBIOS reset command prior to
netbind binding the NetBIOS to the configured adapter cards. This caused
NetBIOS to return a return code 0x23 indicating an invalid LAN adapter
number.
o APAR IC07113 - SYS3175 IN HELP MANAGER WHEN CONFIGURING LAPS
A SYS3175 occurred in LAPS after choosing Options-Contents menu item.
o IC07132 - Invalid Driver IBMTOK02$ When Configuring for 2 Token-Ring Adapters
This problem was introduce in LAPS version 2.20.1. When configuring for two
NDIS or NDIS_MULT type drivers, the numeric digit 02 was appended to the
driver name in the protocol.ini. During IPL, the second MAC driver failed to
bind because the driver name was incorrect. The numeric digit 2 is now
appended to the driver name.
o IC06187 - Proper Version Of NETBIOS Is Not Copied For CID /E:PREP Install
When CID installing LAPS using the /E:PREP option, NETBIOS.LS? was not copied
to NETBIOS.OS2 based on the version of LAN Services installed. This problem
was introduced with NTS/2 CSD WR07020.
o IC06413 - CID Install Of Long File Name Fails
CID install using HPFS long file name caused a LAPS return code XI00041.
o IC04997 - USING ADAPTER NUMBERS TO GUARANTEE UNIQUENESS FOR LANVMAC
LANVMAC requires that its upper boundary be strictly defined; the Media
Access Control (MAC) for adapter 0 can only be defined for adapter 0.
o IC04999 - LAPS CONFIGURATION NEEDS TO TREAT LANVMAC NETADDRESS LIKE LANDD
Function was added that treats the LANVMAC netaddress field the same as the
LANDD netaddress field.
o IC05159 - MAINTENANCE INSTALL OF LAPS DURING CID FAILS ON OS/2 2.1
When running maintenance LAPS installation using CID on OS/2 2.1, LAPS failed
while attempting to update the IBMLVL.INI file.
o IC05553 - LAPS INSTALL DID NOT PUT LANVDD AND LANPDD IN THE CONFIG.SYS FILE
(LAPSPM.DLL)
On OS/2 2.1, the LAPS install did not place statements for LANVDD.OS2 and
LANPDD.OS2 in the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.2.5.2. Other fixes ΓòÉΓòÉΓòÉ
o LOG FILE NOT PROVIDED FOR CID INSTALL IF TARGET DRIVE DOES NOT EXIST
A LAPSHIST.LOG file was not created to indicate that a LAPS install on a
non-existent drive partition failed.
o DEFAULT HANDLING OF UPGRADE_LEVEL GIVE WRONG CID RETURN CODE LAPS response
file upgrade_level parameter was omitted, thus it defaults to old, meaning
that reinstallation of LAPS will only occur on systems with the same version
of LAPS. On systems with a different version of LAPS, LAPS returned an
incorrect return code which indicated a successful LAPS installation even
through LAPS was not installed.
o LAPS ERROR LOG FILE TRUNCATED WITH EOF MARKERS.
The LAPSHIST.LOG file was corrupted occasionally with extra EOF '0A' markers.
o UPDATE MESSAGE WHEN INSTALLING LAPS OVER LATER VERSION OF MPTS
The message when reinstalling LAPS over a more recent version of MPTS (LS
4.0) was changed to strongly warn the user that if the current install
continues, it will disable some of the MPTS functions.
o PRESERVE LOCATION OF NETBIOS.OS2 IN CONFIG.SYS FILE
NetBIOS device driver statement is now preserved at its current location in
the config.sys when reconfiguring LAPS.
o LAPS REMOVES DIGIT FROM DRIVERNAME IN PROTOCOL.INI FILE
The last digit in a MAC drivername was inadvertently removed, creating an
incorrect MAC drivername in the protocol.ini file.
o TAB Function Fails With LAPS Configuraton Utility
Pressing the TAB key selected the OK pushbutton instead of moving to next
configurable parameter within the LAPS configuration utility.
o CONFIG.SYS Drive Is Not Correct When Copying NETBIOS.OS2
The wrong CONFIG.SYS drive was used to copy NETBIOS.LS2 or NETBIOS.LS3. This
caused NETBIOS.LS3 to always be copied when installed on the non-boot drive.
This problem was introduced with NTS/2 CSD WR07020.
o LAPS Able To Configure 64 Logical Adapters
LAPS configuration utility increased the number of configurable logical
adpaters from 16 to 64.
o NLS LAPS CID Install Causes Trap D
LAPS CID install on various NLS verions caused a Trap D when XI1.MSG message
file was used.
o ERROR IN NIF VALIDATION WHEN CHECKING DEFAULT AGAINST RANGE (LAPSCID.DLL
LAPSPM.DLL IBMLXCFG.DLL)
The NIF validation code was incorrectly handling the case in which a default
value of type HexString was being checked against the arguments of the Range
keyword. The check failed if the default value was enclosed with double
quote characters or specified with a "0x" prefix. The problem only occurred
in the situation where the parameter was of type HexString, had a default
value, had a specified range, and the default value had quotes and/or a
prefix.
o VDD/PDD CONFIG.SYS PROBLEM
Eliminates LANVDD and LANPDD device statements from the CONFIG.SYS file if
802 or NETBIOS are not configured.
o FIX REDIRECTOR STATEMENT
Fixed redirector statement position in the CONFIG.SYS file.
o LAPS CONFIGURATION GENERATES DIFFERENT RESULTS
Upon configuring the LANVMACs, LAPS configuration set the drivername on
entries 2-n to LANVMA2 and the module names for entries 2-n end in "_nif2".
o CREATING RESPONSE FILE FROM LAPSRSP.EXE - IMPROPER TARGET KEYWORD
Specifying a target using LAPSRSP.EXE generates a response file containing
"target_drive" instead of "target".
ΓòÉΓòÉΓòÉ 6.2.6. 802.2 Protocol Stack Defects ΓòÉΓòÉΓòÉ
Files that changed:
\IBMCOM\PROTOCOL\LANDD.OS2
\IBMCOM\PROTOCOL\LANDLLDD.OS2
\IBMCOM\DLL\ACSLAN.DLL
\IBMCOM\\LANMSGDD.OS2
\IBMCOM\\LT0.MSG
\IBMCOM\\LT0H.MSG
ΓòÉΓòÉΓòÉ 6.2.6.1. APAR fixes ΓòÉΓòÉΓòÉ
o IC06318 - RIPL SERVICE FAILS TO START
When attempting to start the RIPL service in LAN Server, the service was
never completed. The problem occurred intermittently and LAN Server net
error NET3182 was posted.
o IC07486 RING_UTILIZATION FIELD INDICATES 0% UTILIZATION
The ring_utilization field in the extended_status_addr section of a
DIR.STATUS command indicated ring utilization at 0%.
o FFST/2 INSTALLED MESSAGE LT00073 MODIFIED
LT00073 message was modified to avoid confusion on whether FFST/2 was
properly installed. The message was modified to indicate that FFST/2 was
installed, but not started instead of not properly installed.
o IC08097 DESTINATION MAC ADDRESS CAUSES LAN DISTANCE MACHINE TO TRAP
When using a destination MAC address starting with 4000FFFF, caused a trap
when using LAN Distance 1.1.
o IC08626 DLC.RESET WITH STATION_ID '0000' FAILS
Submitting a CCB DLC.RESET with Station_ID '0000' returned an invalid return
code 0x43.
o IC07133 - LANDD Loops while MAC Adapters Initialize DMA
LANDD was looping while various MAC Adapters were initializing their DMA.
This cause the system to appear to be hung for approximately 30 seconds.
LANDD thread is now blocked during initializing time.
o IC06177 - SNA Gateway Loses Its LU Connections
The problem Workstations intermittedly lost their 3270 LU connections to the
Gateway machine. The Gateway eventually recovered on its own and the
Workstation's LU connections were re-established. The problem occurred
because extended registers were not used and caused a memory index problem.
o JR07531 - Trap D In LANDD When LAN Station Manager Is Installed
A Trap D occurred when LAN Station Manager device driver (LSMMIB2) was
loaded. LAN Station Manager declared itself as an NDIS Extension application
but did not provide the data structure corresponding to an NDIS Extension.
LANDD will now check the length of the data structure to see if it has a NDIS
Extension length.
o IC04923 - MULTICAST ADDRESS SUPPORT FIX
The multicast address support functions in 802.2 fixes to loopback path,
error codes, and command codes.
o IC05000 - TRAP D IN LANDD CODE RUNNING 75+ WORKSTATION GATEWAY (LANDD.OS2)
Each time the links were deactivated, the downstream emulators reactivated
the link and the LU-LU sessions were automatically reestablished. A Trap D
occurred.
o IC05001 - COMMUNICATIONS MANAGER (CM) UNABLE TO STOP NORMALLY OR ABNORMALLY
CM was unable to exit because it cannot close the token-ring link to the
AS400. The hang was due to the Close.Station being issued on the completion
appendage for a Transmit.I.Frame, resulting in a DISC sent to the MAC, the T1
timer started and the Link state set to disconnecting. When the completion
appendage returns to NETBEUI, it continues processing the I-frame completion
which stops T1.
o IC05003 - UNABLE TO REOPEN BUSMASTER ADAPTER AFTER LOBE FAILURE
(LANDLLDD.OS2)
o IC05360 - TRAP D IN LANDLL; CS=0C38;
Attempting to bring up LAN Net Manager (LANDLLDD.OS2) results in TRAP=000D
with the CS register at x'0C38'
o IC05753 - LANDD INCORRECT FRAME CAUSED TRAP D (LANDD.OS2)
The Trap D occurred when remotely configuring a LAN-attached printer. A
pop-up said the action was successful, then there was an OK button. If the
button was not clicked, after about 20 seconds, a Trap D occurred.
ΓòÉΓòÉΓòÉ 6.2.6.2. Other fixes ΓòÉΓòÉΓòÉ
o NDIS 2.0.1 EndReset Supported In LANDD.OS2
LANDD.OS2 was not supporting NDIS 2.0.1 EndReset and was fixed to support the
NDIS 2.0.1 EndReset function.
o RECEIVE COMMAND WITH RETURN CODE = 20 SHOULD ZERO OUT THE BUFFER POINTER
(LANDLLDD.OS2)
When the receive command completed with return code = 20 (lost data, no
buffers), the buffer pointer should be 0 since there were no partial buffers.
o SERVER ACCESS POINT POOL SIZE OF 1000H NOT HANDLED (LANDD.OS2)
When the maximum size, 0x1000 was used for pool_length in a DIR.OPEN.DIRECT,
a return code of 0x16 was returned. The value should work appropriately.
ΓòÉΓòÉΓòÉ 6.2.7. 802.2 and NETBIOS Virtual Device Driver Defects. ΓòÉΓòÉΓòÉ
Files that changed:
\IBMCOM\LTSVCFG.COM
\IBMCOM\PROTOCOL\LANVDD.OS2
ΓòÉΓòÉΓòÉ 6.2.7.1. APAR fixes ΓòÉΓòÉΓòÉ
o IC06017 - Attachmate Extra For Windows 3270 Causes LANVDD Trap D
Stopping a 3270 Attachmate session and starting a new session caused a trap D
in the LANVDD.OS2 module. The fix zeroes out various structures on exit.
o IC06434 - Attempting To Load PCSUPPORT Router In a VDM Causes Trap D
Attempting to load PC-Support (connection for AS/400) in a VDM caused a trap
D in the LANVDD.OS2 module. The fix was to restore an index register after
returning from a procedure call.
o JR06756 - DIR.INTERUPT RETURNS 0 IF ADAPTER NOT OPEN (LANVDD.OS2)
Attempting to run an Ethernet packet driver for TCP/IP. It failed when it
attempted to initialize, because the executable ran a dir.interrupt command
to see if the adapter was open. VDD returned a return code = 0 if the
adapter was not open. It should have returned a bad return code.
ΓòÉΓòÉΓòÉ 6.2.7.2. Other fixes ΓòÉΓòÉΓòÉ
o THE DOS 8209 BRIDGE UTILITY CAN NOT FIND ADAPTER WITH VDD
The DOS version of the 8209 Bridge Utility could not find the adapter when
running under the VDD.
o LTSVCFG ALWAYS RETURNS NONZERO
When LTSVCFG was run, an error code environment variable was always set to
nonzero. Even though LTSVCFG executed successfully, a nonzero return code
was always returned.
o NETBIOS and 802.2 SUPPORTS ONLY 8 DOS SESSIONS
DOS Virtual Device Support for Netbios and 802.2 should support 16 sessions,
not just eight.
ΓòÉΓòÉΓòÉ 6.2.8. Protocol Manager Defects ΓòÉΓòÉΓòÉ
Files that changed:
\IBMCOM\PROTMAN.OS2
ΓòÉΓòÉΓòÉ 6.2.8.1. APAR fixes ΓòÉΓòÉΓòÉ
o IC07134 - LANMSGDD.OS2 TRAPS WITH INVALID PROTOCOL.INI FILE
A trap in lanmsgdd.os2 device driver occurred during ipl if there was not a
square bracket as the first character of the protocol.ini file.
ΓòÉΓòÉΓòÉ 6.2.8.2. Other fixes ΓòÉΓòÉΓòÉ
o PROTMAN.OS2 VECTOR SIZE INCREASED
Protman.os2's vector size was increased to fix 64 adapter support.
o PERFORMANCE AND NDIS SUPPORT IN PROTMAN
PROTMAN supports the GET_PPATINFO IOCTL for the NDIS requirements and the
GET_MODULE_CHAR_ TABLE IOCTL for the Monitor product.
ΓòÉΓòÉΓòÉ 6.2.9. IBM Netware Requester Support Defects ΓòÉΓòÉΓòÉ
Files that changed:
IBMCOM\PROTOCOL\ODI2NDI.OS2
IBMCOM\NWFIXUP.EXE
IBMCOM\LT8.MSG
IBMCOM\LT8H.MSG
ΓòÉΓòÉΓòÉ 6.2.9.1. APAR fixes ΓòÉΓòÉΓòÉ
o IC06987 - ODI2NDI COEXISTENCE WITH CM/2 CAUSES 3270 ERRORS
When CM/2 coexisted with ODI2NDI.OS2, 3270 sessions were unable to connect to
the host and received COM695 errors. The Netware requester, however,
functioned properly. If ODINSUP was used, both Netware and the 3270 sessions
worked normally. This problem seems to occur mostly on 3COM Ethernet adapters
and PCMCIA adapters.
o IC07347 - TRAP IN ODI2NDI.OS2 MODULE
A trap occurred in ODI2NDI device driver during IPL.
o IC07912 - ODI2NDI DEVICE DRIVER DOES NOT RECONNECT AFTER CABLE PULL
After pulling the token ring cable on a machine running NetWare requester
and ODI2NDI, the sessions did not reconnect. A reboot was required to
reconnect.
o IC05577 - NWFIXUP Utility Failed To Order Device Driver Statements Properly
System configured with ODINSUP. NTS/2 was installed with ODI2NDI device
driver and the NWFIXUP utility was executed. During IPL, a LT80221 error
occurred. NWFIXUP failed to properly move PROTMAN.OS2 and LANMSGDD.OS2
within the config.sys.
o IC06212 - Trap D in ODI2NDI.OS2 Device Driver
A Trap D occurred in ODI2NDI.OS2 device driver. This problem was introduced
in NTS/2 CSD WR07020.
o IC05437 - LOTUS NOTES RUNNING ODI2NDI OVER ETHERNET LOST SESSION
While running Lotus Notes over ODI2NDI Ethernet, the session between the
server and client was eventually lost.
ΓòÉΓòÉΓòÉ 6.2.9.2. Other fixes ΓòÉΓòÉΓòÉ
o ODI2NDI DEVICE DRIVER WRITES UNIVERSAL ADDRESS TO LANTRAN.LOG FILE
ODI2NDI writes the universal address of the adapter(s) that it is using to
the LANTRAN.LOG file.
o IBMCOM PATH ADDED TO ODI2NDI MESSAGE FILE NAME
The IBMCOM path has been added to the ODI2NDI message file name to make
ODI2NDI easier to use in a RIPL environment.
o ODI2NDI FAILS WHEN TCP/IP USES DIRECT STATION OF IEEE 802.2
A NetWare Requester for OS/2 over ODI2NDI stops working when an application
using the direct station interface of IEEE 802.2 is started.
ΓòÉΓòÉΓòÉ 7. Appendix ΓòÉΓòÉΓòÉ
Appendix of other interesting topics.
ΓòÉΓòÉΓòÉ 7.1. Printing Information from this On-line Document ΓòÉΓòÉΓòÉ
The OS/2 view function provides a print capability to the printer defined as
the "default" printer for your system. From the "Services" popup, selecting
print provides several options; Print All, Marked, or This Section(s),
Contents, or Index.
All but the Print Marked Sections are fairly self explanatory. To Print
"Marked" sections one must first know how to "Mark". It is best to do this with
the contents window fully expanded, ie. every section shows up in the content
panel. Then simply press the space bar when the section you chose is
highlighted or point and click the left mouse button while also holding the
ctrl key to "mark" a section for print.
The highlighting for "marked sections" is slightly larger than normal
highlighting. To notice the difference, select an item in the contents and
repeatedly press the space bar.
ΓòÉΓòÉΓòÉ 7.2. Restarting ServicePak Installation ΓòÉΓòÉΓòÉ
If the installation procedure stops after selecting the "Continue" button on
the Start Service Panel and before service is complete, the system may be in an
indeterminate state. To complete the service process:
o Insert the Bootable Standalone Service Diskette
o Restart the system - Ctrl+Alt+Del or Power On.
o From the A: Prompt type "FSERVICE" and Enter.
ΓòÉΓòÉΓòÉ <hidden> Initiating Service ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé--Γöé Initiating Service Γöé
Γö£ΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé
Γöé Continuing at this point will cause all selected Γöé
Γöé directories to be updated. If you want to change the Γöé
Γöé selected directories, click on Cancel and then click Γöé
Γöé on Select Directories. Γöé
Γöé Γöé
Γöé The application of service cannot be interrupted. Γöé
Γöé After this point you will not be able to exit the Γöé
Γöé service process. Γöé
Γöé Γöé
Γöé Do not start those applications being serviced Γöé
Γöé Γöé
Γöé Do you want to continue? Γöé
Γöé Γöé
Γöé ΓòöΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòù ΓòöΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòù ΓòöΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòù Γöé
Γöé Γòæ Continue Γòæ Γòæ Cancel Γòæ Γòæ Help Γòæ Γöé
Γöé ΓòÜΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¥ ΓòÜΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¥ ΓòÜΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¥ Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of IBM Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Microsoft Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Wall Data Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Attachmate Corporation