home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
network
/
ptf357.zip
/
PTF357.DOC
< prev
next >
Wrap
Text File
|
1993-02-16
|
16KB
|
357 lines
README for PTF357.ZIP
February 10, 1993
STOP!!!
Do not simply copy these files!
You MUST follow the installation instructions below exactly!!
SUMMARY
PTF 357 is the current maintenance PTF for NetWare for SAA Version 1.2.
It solves the following problems:
GENERAL
Fixes required relative to "NetWare SNA Links"
Workstation unable to connect with more than 29 Comm Servers on Net
Unable to connect to NWSAA through TCP/IP connection
"Alloc short term memory allocator request exceeded the configuration"
GPPE errors including "Running Process: Streams Q Runner
CONNECTED TOKEN RING
Connection does not establish with "Link Disconnected" message
Lose Connection to the Host
RUNNING PC SUPPORT
Blank screen
PCS6545 0A 0001 000000A1 00
Error on start 32
Unable to correct password after executing STRNRTR
High server utilization rate
Problems using JD Edwards applications
Unable to connect three (3) AS/400s
COMM ERROR 001 00000018
Workstation Hang
"9999 Unexpected Code Error" with failure to transfer large files
USING LU 6.2
Unable to establish conversation
Server fails with "GPPE error in SNAP"
Workstation hangs during XCOM 6.2 file transfer
CONNECTED SDLC
GPPE error when server is loaded and unloaded
"Data larger than MAX SDLC frame size, caused by checksum error"
"No ECB available
RTS stays high
Workstations hang and SDLC board no longer communicates
Link does not establish
Slow performance
Sense Codes
Aborted file transfers from the Host
Unable to establish connection to the Host
Problems when running full duplex
Reports of Transmit Errors
NEW FEATURE - Auto Disconnect support
WARNINGS
1. Follow the installation instructions exactly!
2. CSINSTAL must be used to install this PTF.
3. Version 1.2 of NetWare for SAA must be installed before this PTF is
installed.
4. In addition to the installation instructions, the PROBLEM/SOLUTION
DETAIL section includes instructions which must be followed for some fixes
and new features to be implemented.
INSTALLATION INSTRUCTIONS
1. If the Communications Executive is active do a CSDOWN from the CS>
prompt.
2. Unload the Communications Executive by typing "UNLOAD COMMEXEC" from
the
server (:) prompt.
3. Put the files in this PTF onto a floppy disk.
4. Put the disk into drive A: of the comm server.
5. At the comm server (:) prompt type "LOAD A:CSINSTAL A".
6. Chose the option to "Update Netware Communication Service".
7. Confirm that Netware for SAA should be updated.
Be patient, it may take more than 10 minutes for update to complete.
8. Exit CSINSTAL and reload the COMMEXEC and Host profiles.
9. If you are using PC Support with a SDLC connection:
A. Bring up the SNA SDLC Configuration Panel and change the PU2.1 link
station role to SECONDARY.
B. On the AS400
- In the Controller Description, change the Data Link role to
SECONDARY.
- In the Line Description change the Data Link role to PRIMARY.
Failure to do this will result in the link not being established.
10. ONLY IF three AS400s are connected.
Configure CONFIG.PCS as in the EXAMPLE below. Note that the TRLI
parameters contain the three system names, followed by their local adapter
addresses contained within the line configuration of the associated AS/400.
CSNA SAA
SFLR 1,D,,PHASE4
UPDT D:\QIWSFLR,C:PCS,S,,,PC SUPPORT/400
RTYP ITRN
RTLN APPN.FRED
TRLI PHASE4,400000032348,04
TRLI WARP2,4000000A1062,04
TRLI MACH1,400000063232,04
11. ONLY for Token Ring Connection.
Put the following statement in AUTOEXEC.NCF prior to loading the SNA
Service Profile.
LOAD ITRNPS /RT=n
"n" is a number from 1 to 5, with each increment equaling 5 seconds.
As ITRNPS tries 6 times before dropping the connection "LOAD ITRNPS /RT=5"
would set the Response Timer to the maximum wait of 30 seconds.
PROBLEMS and SOLUTIONS DETAIL
1. When Netware for NFS and NetWare for SAA were installed on the same
server, a UNIX client was not able to connect to NetWare for SAA through a
TCP/IP connection.
The problem was caused by Netware for SAA and NetWare for NFS print
services both trying to use port 515 for TCP/IP connection. CMTCP.NLM has
been changed so Netware for SAA will now use TCP/IP port 1366.
2. A 3270 LAN workstation will now be able to connect without problems if
more than 29 Comm servers are on the Network.
3. The error message, "Alloc short term memory allocator request exceeded
the configuration" was sometimes received at the SAA server and the SAA
server subsequently failed.
There are two possible causes for the error message:
- Too little RAM in the server.
Solution: a minimum of 6M RAM
- Corrupted Memory Pointers
Solution: apply this PTF
4. 3270 LAN Workstation for DOS sent a packet with an invalid source
identification field to Netware for SAA during session startup. When the
SAA server received such a packet it would abend with the error message,
"General Protection Processor Exception Running Process: Streams Q Runner
Process". IMERC.EXEs dated 5/18/92, or later, include a modification so
the workstation will no longer send a packet that contains a corrupted
source ID field.
THEREFORE this problem will not be solved unless your 3270 LAN Workstations
for DOS are at version 2.02 (or higher) AND with an IMEREC.EXE dated
5/18/92 or later.
Such an IMEREC.EXE for Workstation V2.02 can be found in PTF349.ZIP.
3270 LAN Workstation for DOS V2.00 can be upgraded to V2.02 by downloading
WSDUP.ZIP.
5. WITH TOKEN RING CONNECTION
5A. The connection would not establish and the server displayed the
error message; "Link Disconnected" because, SAA responded with "XID
negotiation error byte 9 bit offset 4" to an "00 Exchange State Not
Supported" in XID from the host.
5B. SAA sets a response timer for each frame that it sends to an IBM
Host and disconnects the link to the Host (displaying a message at the CS
Console) if a response is not received before this timer expires. The
response can be slow in large WAN environments, resulting in a loss of
connection.
After installing the new ITRNPS.NLM by following Installation Instruction
#11 you will have the ability to adjust the response timer so that SAA
will wait longer for a Host response before disconnecting the link.
To do so, put the following statement in AUTOEXEC.NCF prior to loading
the SNA Service Profile.
LOAD ITRNPS /RT=n
"n" is a number from 1 to 5, with each increment equaling 5 seconds.
As ITRNPS tries 6 times before dropping the connection "LOAD ITRNPS
/RT=5" would set the Response Timer to the maximum wait of 30 seconds.
6. Accessing an AS/400 via PC Support
6A. With NetWare for SAA on a NetFrame server; after the router
(STRNRTR) starts and the Workstation Function (WSF) loads, the emulation
screen is blank except for the Operator Information Area (OIA).
6B. The length of the PIU was incorrect causing one byte of the file to
be overwritten. This caused large file transfers to fail with the
message, 9999 Unexpected Code Error.
6C. Support for the connection of three AS/400s on a Token Ring network
did not work because the third Mac address overlaid the second Mac
address. The ITRNPS.NLM included with this PTF adds support for the
connection of three (3) AS\400s. See installation step #9 above.
6D. If "A" was pressed to ADD A STUDENT when using Schools
Administrative Student Information (SASI), from Macro Educational
Systems, the workstation locked with COMM ERROR 001 00000018.
6E. High server utilization rates were observed at some installations.
6F. An incorrectly entered password could not be corrected during
STRNRTR.
6G. Problems were experienced running JD Edwards applications.
6H. Recognition of the System Name has been modified so that if the
AS/400 system name is less than 8 characters, the workstation will no
longer hang when Rochester Software Connection's ShowCase Vista software
is invoked when the system is selected.
6I. RTRMAP from IBM, maps requests from "Extended DOS PC Support"
functions into requests recognized by the NetWare Router for AS/400 PC
Support. When RVMRTR is used to remove the Router it frees the memory
that RTRMAP was using but did not display a message. (corrected with
additional APPC verb support)
NOTE: RTRMAP is in a patch available from IBM
- V2 Release 1 requires IBM PTF SF09653
- V2 Release 1.1 requires IBM PTF SF09654
- V2 Release 2 contains the corrected code
6J. Additional APPC verb support has been added so that:
- When running Remote SQL (RMTSQL) from IBM with PC Support Extended, it
will no longer fail with "error on start 32"
- After starting Workstation Function (WSF) from PC Support Extended, and
signing on at the Sign On Screen, the monitor will no longer go blank
with the exception of two lines at the bottom:
PCS6545 0A 0001 000000A1 00 (first line)
The WSF status line (second line)
- When the Remove PC Support (RMVPCS) command is used to release the
memory of selected PC Support Functions, it will now remove the NetWare
Router for AS/400 PC Support.
7. USING LU6.2
7A. Userids and passwords supplied by LU6.2 applications were not passed
to the host. They will now be passed to the host, allowing conversations
to be established.
7B. "GPPE error in SNAP" should no longer be received when using two site
information records with CPIC API.
7C. When using XCOM 6.2 file transfer a 12FF and 12E1 were sent in the
data stream and hung the workstation.
7D. A number of problems have been corrected which occurred in both PU2.0
or PU2.1 configurations.
8. With SDLC Connection
8A. R3SDLC has been modified so that:
1) The server will no longer abend with a GPPE error if the server is
unloaded and reloaded while a leased line link is up.
2) The message "Data larger than MAX SDLC frame size, caused by
checksum error" will no longer display on the console.
Instead, the "receive packet too big count" in MONITOR will be
incremented.
NOTE: The error can be caused by a Network Interface Card with shared
RAM interfering with the SDLC adapter. We suggest trying another
brand of LAN card.
3) The profile configuration will now determine if RTS is held high or
toggles.
4) Workstations will no longer hang if the SAA adapter board receives
an invalid interrupt.
5) Frames will no longer be resent unnecessarily. The retrys degraded
performance.
6) 'Ghost', "Receive Packet Miscellaneous Errors" will no logged be
logged in the Monitor Utility, when in fact, not occurring.
7) Abort Frames will now be properly handled.
Abort Frames from the Host were detected but not handled correctly. A
RESEND was requested, but the bad frame not flushed. Instead, it was
added to the resent Frame and passed on to the workstation. This
caused the display screen to show the bad frame data. In structured
field mode the length of field came out wrong, and a sense code was
returned to the Host.
In the case of file transfer (RECEIVE.EXE) the transfer aborted.
8) Full duplex communication will now be properly supported.
When running Full Duplex the number of SDLC frames transmitted from
the Host did not match the number received.
NOTE: To implement a Full Duplex line use a statement like the
following Line
Macro example:
N11L001 LINE ADDRESS=(001,FULL)
ISTATUS=ACTIVE
8B. SDLCPS was modified:
1) To improve ECB management. This will sharply reduce the number
of sites receiving the console message "No ECB Available".
2) So that NetWare for SAA will now respond with a UA (Unnumbered
Acknowledge) when FEP sends a DISCONNECT (53). Failure to send a UA
caused the Link to not establish.
3) The Comm Server will respond with only one UA when the Host sends
two SNRM's in a row.
The Comm Server was responding with two UAs which caused the Host to
send a disconnect to the Comm Server.
This resulted in the connection to the Host never being established.
NEW SDLC FEATURE
R3SDLC.LAN now supports Auto Disconnect. The firmware disables the
receiver when it turns off DTR.
SDLC CHANGE
R3SDLC.LAN will no longer send a message to the console "No DSR from modem,
please dial to host. Need to use Novell cable". When the R3 SDLC cable is
disconnected and the R3 driver attempts to connect to host.
Instead, the DSR Inactivity Count under Custom Statistics for the R3SDLC
driver will increment the counter by one every time the driver attempts to
make a host connection without the cable attached.
FILES IN PTF 357
AS400PCS.NLM 17362 7-12-92 *336
CM.NLM 36813 10-15-92 *396
CMAT.NLM 43921 10-2-92 *396
CMTCP.NLM 36483 10-19-92 *405, 396
CNSMX.NLM 57795 10-05-92 *396, 303
CS$ERR.DAT 9451 2-26-90 *425
CS$HELP.DAT 3722 9-1-89 *425
CS$MSG.DAT 24812 12-14-89 *425
CSCON.EXE 370462 8-28-92 *425
CSCONFRM.FRM 27767 6-20-92 *425
CSCONFRM.HLP 65167 7-22-92 *425
CSSECUR.NLM 95019 11-19-92 *426
ITRNPS.NLM 35083 5-04-92 *301
NOVELLRT.MRI 6415 3-28-92 *285
NOVELLRT.OVL 5750 7-12-92 *336
NWSAA.NLM 294343 1-27-93 *445, 424, 423, 358
PB_NWSAA.NLM 29263 8-28-92 *424
PBTRACE.NLM 2646 8-28-92 *424
R3SDLC.LAN 22125 11-23-92 *428
RMVNRTR.EXE 10203 7-12-92 *336
SDLCPS.NLM 32859 11-10-92 *421
STRNRTR.EXE 30629 7-12-92 *336
CSINSTAL.NLM 149897 3-02-92
NWSAA.RMV 1390 2-20-92
DISK1.INS
PTF357.DOC
* Novell Internal Control Number
HISTORY
PTF 357 supersedes all Prior NetWare for SAA v1.2 PTFs including PTF 324
and PTF 325. The immediately preceding NetWare for SAA 1.2 PTF was PTF 357
in SAA1_2.ZIP.
DISCLAIMER
Novell, Inc. makes no representations or warranties with respect to any
NetWare software, and specifically disclaims any express or implied
warranties of merchantability, title, or fitness for a particular purpose.
Distribution of any NetWare software is forbidden without the express
written consent of Novell, Inc. Further, Novell reserves the right to
discontinue distribution of any NetWare software.
Novell is not responsible for lost profits or revenue, loss of use of the
software, loss of data, costs of re-creating lost data, the cost of any
substitute equipment or program, or claims by any party other than you.
Novell strongly recommends a backup be made before any software is
installed. Technical support for this software may be provided at
the discretion of Novell.