home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IBM Presents OS/2 Software Hits 1995
/
OS-2_SW_HITS_2ND_EDITION_1995.ISO
/
i17
/
gwy195.doc
< prev
next >
Wrap
Text File
|
1995-02-17
|
9KB
|
228 lines
NFS Gateway 1.2 Update for NW 3.x (GWY195.EXE)
---------------------------------------------------------------
This package is made up of the following files:
GWY195 DOC15HB5 - This document
GWY195 EXE15HB5 - Binary self-extracting file.
---------------------------------------------------------------
NOVELL PRODUCT and VERSION: NetWare NFS Gateway 1.2
ABSTRACT:
Accumulated bug fixes for NetWare NFS Gateway. Read the
installation instructions INSTALL.TXT when installing. Read
the supplement FEATURES.TXT to understand new features and
parameters.
---------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY
THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS
DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO
EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
---------------------------------------------------------------
SYMPTOM
1) Server abend with GPPE when using Wordperfect 5.1 in
Windows 3.11. Windows and Wordperfect are installed on a
NetWare volume.
Steps to reproduce:
a. Start Wordperfect.
b. Open a file which resides on a gateway volume.
c. Click on Open again to open two submenus.
d. From one of the submenus double click on ".." to go up one
directory.
e. The server abends with a GPPE error.
Also, the GPPE can occur by using the DOS command "cd ..".
2) Documentum, or other applications which create files on the
NFS server through some other means than the Gateway itself,
is intermittently unable to access newly created files. User
gets "file not found". In the case of Documentum, the
workstation sends TCP messages directly to an AIX box running
Oracle. Oracle and UNIX function calls (fcreate, fopen, fread,
fwrite) create a temporary directory called /DATA/COMMON which
lasts for duration of Documentum session. The NFS Gateway may
not always see these files even if /ETC/NWPARAMS contains
"DIR_COMP_TIME = 0".
This problem can be recreated without Documentum as follows:
a. UNIX: mkdir tst/d1
b. UNIX: cp /etc/hosts tst/d1/f1
c. DOS: DIR TST/D1 /S
d. DOS: TYPE TST/D1/F1
e. UNIX: rm -rf tst/d1
f. UNIX: mkdir tst/e1 ( e1 should have the same i-node as d1 )
g. UNIX: cp /etc/hosts tst/e1/f1 ( f1 should have the same i-
node as previous f1 )
h. DOS: TYPE TST/E1/F1 ====> THIS SHOULD FAIL
i. UNIX: rm-rf tst/e1
j. UNIX: mkdir tst/g1 (g1 should have the same i-node as d1
and e1 )
k. DOS: CD G1 ====> THIS SHOULD FAIL
3) Cannot mount NFS server running on OS/2 because UNICON
prevents user from typing "\". Changed to allow "\" character.
It is no longer necessary to manually edit the SYS:ETC/NWPARAMS
file.
4) Installation of NFS Gateway 1.2 increases allowed
connections, which is shown in SYSCON and other NetWare
administration utilities. For example, a 100-user license of
NetWare would appear as 250-user after installing NFS Gateway
1.2. May cause problems with some applications which examine
the maximum connection allowed, such as ARCSERV.
5) Can't read/copy files from SJF-NFSGW to local drives even
though files have read/write permissions.
6) Abend: nfsgw (gwch read_data_ release func-release()).
Intermittent problem which occurs when gateway is under a load
greater than 40 workstations. There was small window of time
for error in the synchronization of a write and read request
after a lock request.
7) Workstation connection can become hung. Hung connection
cannot be removed through MONITOR.NLM or any means other than
rebooting the server. Fixed for known circumstances.
8) Abend: DeleteFromHash was called with directory entry
number.
9) Cannot copy files from the Gateway volume to local drive
even though files have read and write permissions.
10) Certain applications, including MHS router, CC:Mail and MS
Mail, and MS Access applications cannot read files on the SYS:
volume. They appear to be locked whenever NFSGW is loaded.
CC:MAIL programs (such as ADMIN.EXE) get message "Cannot Unlock
Database File."
11) After heavy use of the Gateway, some files in a directory
are marked as hidden even if the file names do not start with a
leading period (.).
Steps to reproduce:
a. UNIX: touch .xyz
b. DOS: NDIR ¬XYZ (The Gateway uses carat (¬) to indicate
hidden files.)
c. UNIX: mv .xyz abc
d. DOS: NDIR ABC
e. note that ABC it is marked as hidden.
12) Windows File Manager cannot copy a sub-directory from
local disk to a drive letter mapped to Gateway volume using
drag and drop. Error is "cannot create file/directory".
Steps to reproduce:
From DOS:
a. touch xyz
b. flag xyz ro
c. flag xyz ro
d. del xyz
From File Manager:
e. Drag the c:\dos directory to drive mapped to a Gateway
volume. This should give an error.
NOTE: During the above test, the Gateway should not be used by
anyone else.
13) Cannot access a remote directory if it was created with
the same inode number as a directory recently deleted from
UNIX.
14) A filename is changed on gateway volume where NFS server
is running on IBM OS/2 version 2.1. If correct filename
contains non-numeric characters, the character "0" is appended
to filename. If it consists of all numeric characters, the
file name is "incremented" by one. The correct name is
restored when volume is re-mounted. NFS Gateway is attempting
to avoid a duplicate name collision when this is not necessary.
Problem occurs because some OS/2 systems support only upper
case, at least as seen through the NFS daemon of OS/2. If NFS
Gateway user creates file "STUB" the Gateway will create the
file "stub" on the NFS server (assuming that most users will be
UNIX users). OS/2 saves the file as upper case STUB". Now
when the Gateway user does a DIR, the Gateway detects that it
already has "STUB" in its cache or shadow file, so to avoid
duplicates it displays "STUB0".
With this fix, when the volume is first mounted it will attempt
to create a lower case scratch file, then read it back to test
whether the file has been on upper or lower case on the NFS
server. If upper, then the NFS server only supports upper case
filenames.
NOTE: The exported directory of the remote NFS volume must be
writable by the UID used for mounting, or the scratch file test
will fail.
NOTE: A related tunable parameter UPPER_CASE has been added to
the SYS:ETC/NWPARAMS file. It forces the NFS Gateway to create
only upper case file and directory names. See the FEATURES.TXT
for details.
15) Gateway time stamps incorrect for a while after DOS COPY.
To reproduce, copy some files from C: drive onto Gateway drive.
Use DIR to see time stamp. Time stamp reflects the server
system time for an unpredictably long time.
16) Need DBCS Character support. NFS Gateway 1.2J running on
NW 3.12J does not support DBCS on NW volumes.
17) Source code error found during code review.
18) On Gateway volume with directories with up to 15 levels of
subdirectories, the deletion of directories via DELDIR or
FILER is fast when there are 5 levels or less. More than 5
levels incurs a delay of up to 10 seconds for each level.
19) File is truncated to some fixed length when copying files
in non-packet burst mode from a Gateway volume. The file is
large and the NFS transfer size (NFS_XFER_SIZE) is set less
than 8k.
SOLUTION
Apply GWY195.EXE
Self-Extracting File Name: GWY195.EXE Revision: A
Files Included Size Date Time
\
GWY195.TXT (This File)
NFSGW.NL_ 227007 12-02-94 5:26p
SPACE.DAT 10 02-01-93 3:58p
PFILES.DAT 388 01-23-95 3:19p
GWADMIN.NL_ 19607 12-02-94 5:28p
INSTALL.TXT 3116 01-27-95 3:34p
PCONFIG.DAT 64 12-02-94 2:55p
PCONFIG.HLP 2183 07-29-92 1:27p
PCONFIG.NLM 15934 09-17-93 6:03p
FEATURES.TXT 4163 01-27-95 3:36p
PINSTALL.HLP 6798 06-21-93 2:53p
PINSTALL.NLM 130422 11-08-93 6:39p
P_UNINST.HLP 892 07-27-92 12:02p
P_UNINST.NLM 72042 11-08-93 6:40p
Installation Instructions:
See INSTALL.TXT.
Solution Specifics:
GWY195.EXE corrects all of the listed symptoms.
---------------------------------------------------------------
Any trademarks referenced in this document are the property of
their respective owners. Consult your product manuals for
complete trademark information.
---------------------------------------------------------------