PW-OSF PWOSF_ECO250F PATHWORKS for OSF V5.0F ECO Summary
Copyright (c) Digital Equipment Corporation 1995.
All rights reserved.
PRODUCT: PATHWORKS for OSF V5.0F
OP/SYS: OSF/1 V3.0
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: PWOSF_ECO250F
ECO Kits Superseded by This ECO Kit: PWOSF_E01050F
ECO Kit Approximate Size: PWOSF_ECO250F.TAR 22947840 Bytes
ECO KIT SUMMARY:
An ECO kit exists for PATHWORKS for OSF V5.0F on OSF/1 V3.0 or later.
The Pathworks for OSF ECO release notes contains a complete explanation of
each ECO that will be applied. Below is a brief description of each ECO:
ECO # Description/Symptoms
===== ====================
ECO#1 - At times, files opened by a WfW client will not be closed.
This problem was occurring because the server incorrectly
accepted an open request with opportunistic locking.
ECO#2 - UAS replication was sometimes failing because the server
was using a bad (long) mailslot name. This mailslot
problem could also intermittently affect other file
replication, any communication between servers in a domain,
and some net commands.
ECO#3 - The netBEUI code would panic during shutdown when
embryonic session control blocks were waiting for
datalink LCBs. This problem occurred when the
DL_DATALINKS value (in dlpi_data.c) was less than the
NB_DATALINKS value (in nbdata.c)
ECO#4 - Could not rename long file names for the Windows NT and
Win95 clients. The same problem prevented the creation
of a new folder for a Win95 client.
ECO#5 - The flush SMB had performance problems. These problems
became serious when an application frequently generated
flush SMBs.
ECO#6 - Memory leaks in the license registrar (pwlic.reg) caused
logon performance problems over time.
ECO#7 - When the /etc/group file had a lot of users in a group,
the long line could get truncated when a lanman group was
deleted from the file.
ECO#8 - The lmx.nbd process would not start on systems where
DECnet was running on a tu0 controller. This problem is
timing-related and could happen intermittently on systems
that used other controllers.
ECO#9 - The PATHWORKS DECnet daemon (lmx.nbd) would not start on a
server with a low Phase IV DECnet address.
ECO#10 - When copying large files from share to share over TCP/IP,
the client would intermittently hang.
ECO#11 - When the remote adapter is defined on a DECnet client (via
ncp) the client could not get a license.
ECO#12 - When a write error occurred on AdvFS, either because of
quotas exceeded or a full file system, the error was not
reported to the client.
ECO#13 - If user has NFS share exported with root access and
ignoreunix is set to yes and a directory in the share has
permissions 755, a user could not create a file in that
directory even if the PATHWORKS permissions allow it.
ECO#14 - The NET FILES command would not completely list the open
files, but would abort with SYSTEM ERROR 8 - OUT OF
MEMORY.
ECO#15 - For a particular application (ATTACHE), the client sends
SMBlseek for a 0 byte file with an offset of -1 and the
server responded with an error. According to the SMB
definition, the server should just set the file pointer to
the beginning of the file.
ECO#16 - NetBEUI control blocks would get into a "waiting" state and
wouldn't be recovered until system reboot. The server
would gradually run out of NetBEUI sessions.
ECO#17 - When mail notification is sent on TCP/IP, the client
program expects an ASCII name in the source name field of
the NetBIOS header. But, the name that was used was the
permanent unique name, which is binary.
ECO#18 - A panic could occur when the knb timer queues are
corrupted.
ECO#19 - Panic inside flushq() when an invalid queue is passed.
INSTALLATION NOTES:
Customers must de-install PATHWORKS FOR OSF Base system subset using
setld:
- If any of the subsets are not installed, setld displays a
message to the user stating that. It also prompts the user to
make sure they really want to deinstall the subsets specified.
and re-install with new kit:
> /etc/setld -l /kitdir
- /kitdir is the location of the kit. If the kit is on tape, the
most common tape drive specification is /dev/rmt0h. If the kit is
already on the system, /kitdir is the path to the kit's location.
See directions below for details on installing the kit.
Installing The PATHWORKS for OSF 5.0F ECO2 Kit:
----------------------------------------------------
Use the tar utility to unpack the kit, example:
> tar xvf PWOSF_ECO250F.tar
- the following files are in the tar file.
PWKBASE510 PWKNWTRAN3510
PWKCONFIG510 PWKRNOTE510
PWKDNA3510 PWKRPL510
PWKLIC510 PWKTCP3510
PWKNBU3510 PWKNW3SVOL510
PWKNWBASE510 instctrl
Change to the kit directory and use the setld utility to install the kit:
> cd
> setld -l /kitdir
- The above setld command will display a list of valid subsets that
are in the current directory in menu format and prompts the user.
Below is an example:
The subsets listed below are optional:
There may be more optional subsets than can be presented on a single
screen. If this is the case, you can choose subsets screen by screen
or all at once on the last screen. All of the choices you make will
be collected for your confirmation before any subsets are installed.
- PATHWORKS for DEC OSF/1 AXP (Common):
1) PATHWORKS for DEC OSF/1 AXP - License Server
2) PATHWORKS for DEC OSF/1 AXP - PATHWORKS Configuration
3) PATHWORKS for DEC OSF/1 AXP - Release Notes
- PATHWORKS for DEC OSF/1 AXP (LAN Manager):
4) PATHWORKS for DEC OSF/1 AXP - DECnet Driver
5) PATHWORKS for DEC OSF/1 AXP - LAN Manager Services
6) PATHWORKS for DEC OSF/1 AXP - NetBEUI Driver
--- MORE TO FOLLOW ---
Enter your choices or press RETURN to display the next screen.
Choices (for example, 1 2 4-6):
Choices (for example, 1 2 4-6):
7) PATHWORKS for DEC OSF/1 AXP - Remote Boot Service
8) PATHWORKS for DEC OSF/1 AXP - TCP/IP Driver
- PATHWORKS for DEC OSF/1 AXP (NetWare):
9) PATHWORKS for DEC OSF/1 AXP - NetWare Services
10) PATHWORKS for DEC OSF/1 AXP - NetWare System Volume
11) PATHWORKS for DEC OSF/1 AXP - NetWare Transports
Or you may choose one of the following options:
12) ALL of the above
13) CANCEL selections and redisplay menus
14) EXIT without installing any subsets
Enter your choices or press RETURN to redisplay menus.
Choices (for example, 1 2 4-6):
- the installation proceeds from here.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
pwosf_e01050f.README
pwosf_eco250f.CHKSUM
pwosf_eco250f.CVRLET_TXT
pwosf_eco250f.tar
|
