(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: Vector Graphics & GDDM V2R2
DOCUMENT ID#: FYI.S.SAA04
DATE: 06AUG92
PRODUCT: NetWare Vector Graphics with NetWare for SAA
PRODUCT VERSION: NA
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Does NetWare Vector Graphics work with GDDM v2r2?
SOLUTION
NetWare Vector Graphics has been successfully tested with GDDM v2r2.
FYI: Data Corruption Occurring between AS/400 and NetWare SAA Client
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: Data Corruption Occurring between AS/400 and NetWare SAA Client
DOCUMENT ID#: FYI.S.SAA
DATE: 05AUG92
PRODUCT: NetWare for SAA with Wall Data Rumba for AS400
PRODUCT VERSION: V1.0 Update 03
SUPERSEDES: NA
SYMPTOM:
ISSUE/PROBLEM
Using Wall Data's Rumba for AS/400 on a MS Windows v3.1, IBM PS/2 35-043 client using IPXODI drivers; when getting the initial AS/400 Sign On screen it was not displayed properly (data lines were not in the correct location on the screen).
SOLUTION
A Compaq Systempro was serving as the SAA server. Either:
1. Change the clocking of the Compaq Systempro;
- from HIGH - constant high speed
- to AUTO - switch to lowest clock speed when accessing slower devices e.g., floppy disk).
OR
2. Use the following command with Compaq's utility disk:
MODE MEMCACHE OFF
Disables the cache memory controller.
FYI: Increasing Send/Receive Packet Size
FYI
(Note: 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 claims to the validity of this information.)
TITLE: Increasing Send/Receive Packet Size
DOCUMENT ID#: FYI.S.WIN02
DATE: 31JUL92
PRODUCT: 3270 LAN for Windows
PRODUCT VERSION: 1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
3270 LAN Workstation for Windows 1.0 has a default packet size of 4K for file transfers.
SOLUTION
To increase the packet size on the workstation add two parameters to the global configuration file WSCFG.INI or to the individual configuration file (*.WSC) if you do not want all defined sessions to be affected by the change.
The parameters must be added to the end of the session type definition in the configuration file being changed.
Example: If you choose to modify the WSCFG.INI file and your users are all type 2/model 2, you would add the two parameters to the end of the model 2 session definition information in that file. If they are using any other model types (3,4,5), those definitions would also have to be modified.
The parameters are the following:
Add to WSCFG.INI or to *.WSC files:
SNDRCV_MAX_PACKET_SIZE=X
TRAN_SPX_GLOBAL_MEMORY=Y
X = Packet size chosen up to 32000 max (4000 default) must be in thousands
Y = SPX memory allocated to the selected packet size in X (1.5 x X = Y)
Example:
SNDRCV_MAX_PACKET_SIZE=16000 (increases packet size from 4K to 16K)
TRAN_SPX_GLOBAL_MEMORY=24000 (increases spx memory buffer to handle
increased packet size. 16K x 1.5=24K)
Note that increasing the packet size can have adverse effects on the number of sessions that a user can open.
The problem is that by increasing the SPX memory to handle the larger packet size, you are decreasing the amount of available SPX memory buffers that are available to open sessions with.
Figure D-2 on page D-3 in the manual shows a sample session definition in the WSCFG.INI file.
FYI: X() Problems
FYI
(Note: 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 claims to the validity of this information.)
TITLE: X() Problems
DOCUMENT ID#: FYI.S.WIN01
DATE: 31JUL92
PRODUCT: NetWare for SAA 1.1 and 3270 LAN Workstation for Windows 1.0
PRODUCT VERSION: See Above
SUPERSEDES: NA
SYMPTOM: X()
ISSUE/PROBLEM
Configuration:
SAA was Token-Ring attached to a 3174.
The 3174 was configured to transmit a 2042 frame size to SAA.
SAA was configured to send a 2042 frame size to the 3174.
The users would log in to the host through a "super session" product called TPX. The problems occurred whenever a user tried to perform functions like get mail, send mail, or scheduling. The workstation would x() and the session had to be terminated.
The 3174 logged many I-frame transmit errors (about 10000 per every 20000). A normal situation would show this counter to be 0.
SOLUTION
Increasing the Maximum Physical Receive Packet Size to 4202 solved the problem.
FYI: Correct WNIM for Each Product
FYI
(Note: 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 claims to the validity of this information.)
TITLE: Correct WNIM Choice for Each Product
DOCUMENT ID#: FYI.S.WNM05
DATE: 27JUL92
PRODUCT: WNIM
PRODUCT VERSION:
SUPERSEDES: P.3045, P1807
SYMPTOM: Various
ISSUE/PROBLEM
Some Novell Products work with only certain versions of the WNIM Board.
SOLUTION
1. Access Server requires a WNIM+ or a WNIM Z-80. It will not work with the ribbon connector WNIM board (no longer sold).
2. NACS 2x is expected to work with any WNIM board.
3. NACS 3x has only been tested with the WNIM+ and WNIM Z-80 boards, the old ribbon cable WNIM boards are not supported.
4. ACS (precursor to NACS no longer sold) works only with the original (ribbon connector) WNIM.
5. The Asynch Router is expected to work with any WNIM board but the WNIM+ and WNIM Z-80 are the safest choices.
FYI: Data Corruption Occurring between AS/400 and NetWare SAA Client
FYI
(Note: 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 claims to the validity of this information.)
TITLE: Data Corruption Occurring between AS/400 and NetWare SAA Client
DOCUMENT ID#: FYI.S.SAA02
DATE: 23JUL92
PRODUCT: NetWare for SAA
PRODUCT VERSION: V1.2
SUPERSEDES: NA
SYMPTOM: Data Lines in Sign on Screen not displayed in proper location
ISSUE/PROBLEM
Configuration:
■ Rumba V1.0 Update 03
■ Windows v3.1
■ Client using IPXODI drivers
■ Compaq Systempro as the SAA server.
The problem only occurs while using Wall Data's Rumba for AS/400.
The initial AS/400 Sign On screen was not displayed properly (data lines were not in the correct location on the screen).
SOLUTION
Either change the speed clocking of the Compaq Systempro down
from HIGH - constant high speed
to AUTO - switch to lowest clock speed when accessing slower devices (such as floppy disk).
or Obtain from Compaq the Compaq DOS set parameter to turn cache off and still run the Compaq at HIGH - constant.
FYI: Async Router and Telebit Trailblazer Plus Modems
FYI
(Note: 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 claims to the validity of this information.)
TITLE: Async Router and Telebit Trailblazer Plus Modems
DOCUMENT ID#: FYI.S.ARO1
DATE: 21JUL92
PRODUCT: NetWare Asynch Router (NARR)
PRODUCT VERSION:
SYMPTOM: Unable to Maintain a Link
ISSUE/PROBLEM
The link would drop.
SOLUTION
This modem initialization string created a solid connection at 19.2K, with no MNP, no error correction, and no fallback speeds.
AT~&7FS0=1S51=5S58=2S68=2S97=1S98=3S106=0
FYI: Mixing Versions of LINK/64 and LINK/T1
FYI
(Note: 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 claims to the validity of this information.)
TITLE: Mixing Versions of LINK/64 and LINK/T1
DOCUMENT ID#: FYI.S.LNK1
DATE: 16JUL92
PRODUCT: LINK/64 and LINK/T1
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: Various
ISSUE/PROBLEM
Version 1.0 and 1.1 are significantly different. In keeping with the general rule that the use of dissimilar drivers tends to cause aberrations, mixing the two versions is definitely not recommended.
The problem stems from the performance options added to v1.1 (such as Large Frame option) that do not work with v1.0. Also, the Data Compression Module is a new option which required code modification.
SOLUTION
Upgrade all LINK/64 and LINK/T1 products on the WAN to the same version.
FYI: Sys Request Key
FYI
(Note: 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 claims to the validity of this information.)
TITLE: Sys Request Key
DOCUMENT ID#: FYI.S.WIN04
DATE: 26JUN92
PRODUCT: 3270 LAN Workstation For Windows
PRODUCT VERSION: 1.0
SUPERSEDES: NA
SYMPTOM: Sys Request not working
ISSUE/PROBLEM
The Windows template indicates that Alt+Shift to be used in conjunction with the Sys Request (Print Screen) key. In fact, although this works in DOS mode, it does not in Windows mode.
The function of this key in the mainframe environment is to clear the LU-LU session you are in, and to then establish an SSCP to LU session. In doing so, the screen goes blank. You can toggle back to your LU-LU session from where you left off.
The Print Screen key is reserved in the 3270 Windows software.
SOLUTION
Use the ALT+Shift, Scroll Lock keys instead.
Beware, other keys are also reserved, and the only way to find out that they are reserved is to try and COPY or PASTE them.
FYI: Extra Form Feeds and Slow Printing
FYI
(Note: 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 claims to the validity of this information.)
TITLE: Extra Form Feeds and Slow Printing
DOCUMENT ID#: FYI.S.SAA01
DATE: 19JUN92
PRODUCT: 3270 LAN Workstation
PRODUCT VERSION: 2.0 with NW4SAA 1.1
SUPERSEDES: NA
SYMPTOM: Extra Form Feeds and Slow Printing
ISSUE/PROBLEM
When Host print jobs were sent to a server attached host printer, a form feed was inserted in between the report pages and printing was very slow.
Example: If the printed file is made up of 10 printed pages, every printed page would be followed by a blank page plus an additional time delay occurs during printing of the report.
SOLUTION
Configuring WSLAN with NO DOS Session fixed the problem.
FYI: 3270 Workstation for Windows, Host Printing Problem
FYI
(Note: 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 claims to the validity of this information.)
TITLE: 3270 Workstation for Windows, Host Printing Problem
DOCUMENT ID#: FYI.S.WIN06
DATE: 02JUN92
PRODUCT: 3270 LAN Workstation for Windows
PRODUCT VERSION: 1.0
SUPERSEDES: NA
SYMPTOM: Only one character would print
ISSUE/PROBLEM
When using Type 3 printing to a Postscript printer, only one character would print.
SOLUTION
Change from the "Postscript" to the "Generic Text" Windows driver.
FYI: WTSPX Error 671
FYI
(Note: 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 claims to the validity of this information.)
TITLE: WTSPX Error 671
DOCUMENT ID#: FYI.S.WIN03
DATE: 02JUN92
PRODUCT: 3270 LAN Workstation for Windows
PRODUCT VERSION: 1.0 and 1.1
SUPERSEDES: NA
SYMPTOM: "WTSPX had fatal error 671- SPX event code ee and fe"
ISSUE/PROBLEM
The error message is telling us that there are not enough Event Control Blocks (ECBs).
SOLUTION
Use the parameter below to increase the amount of available SPX buffers which may help eliminate the error message.
"TRAN_SPX_GLOBAL_MEMORY=12000" (default is 6000) v1.1 Beta default is 10000. The maximum setting is 64000, but it is not recommended. You need to set the number based on the environment. (Two times the default is the rule of thumb.)
The parameter has to be put in the WSCFG.INI or *.WSC files and must be put at the end of each model type that the users are configured for .3270.
FYI: PA2 Key with TPX
FYI
(Note: 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 claims to the validity of this information.)
TITLE: PA2 Key with TPX
DOCUMENT ID#: FYI.S.WIN05
DATE: 15APR92
PRODUCT: NetWare for SAA
PRODUCT VERSION: With both DOS and Windows Workstation
SUPERSEDES: NA
SYMPTOM: PA2 key not working
ISSUE/PROBLEM
While using a third party application called "TPX" and a 3178C or 3179 terminal, pressing the PA2 key switches between mainframe session (such as TSO and CICS).
With both 3270 LAN Workstation for DOS and for Windows workstation, the use of the PA2 key with "TPX" does not result in a switch between mainframe sessions.
SOLUTION
Use the ATTN key (ESC).
FYI: "INSUFFICIENT HEAP" error on the NetWare 3270 Gateway.
FYI
(Note: The origin of this information may be internal or external to Novell.Novell makes every effort within it's means to verify this information.However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: "INSUFFICIENT HEAP" error on the NetWare 3270 Gateway.
DOCUMENT ID#: FYI.S.4
DATE: 01APR92
PRODUCT: NetWare 3270 Gateway
PRODUCT VERSION: NA
SUPERSEDES: NA
SYMPTOM: Out of Heap
ISSUE/PROBLEM
Out of Heap
SOLUTION:
See page 5-1 forward in the Gateway manual.
You can be expect to correct the problem by increasing HEAP.
To increase HEAP:
> GWCONFIG GWSERVER /D
> then pagedown until the internal customization pannel appears.
> Then increase HEAP by 20K increments until the problem goes away or you have increased by 80K.
FYI: CDIS CDROM Driver and Access Server (NAS)
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: CDIS CDROM Driver and Access Server (NAS)
DOCUMENT ID#: FYI.S.27
DATE: 19MAR92
PRODUCT: Access Server (NAS)
PRODUCT VERSION: 1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The use of CDROM players with Access Server (NAS).
SOLUTION
The CBIS "CD Solution v2.20C" (100-user), production date 2/10/92 is reported to work with Access Server (NAS) V1.2.
The configuration requirements are:
1. A CONFIG.SYS file for the REMOTE workstation as shown below. Note in particular the LASTDRIVE statement. A LASTDRIVE statement must be inserted on the Access Service as well and the drive specification must be identical to that of the REMOTE workstation. Failure to do this will allow access to the CD drives from the first session ONLY. A session will terminate normally but upon reconnecting to the NAS, attempt to access the CD drives results in an error message and the NAS must be rebooted.
FILES=30
BUFFERS=25
DEVICE=C:\CDSYS.SYS /D:MSCD001 /N:3
LASTDRIVE=H
2. A CONFIG.SYS for the Access Server (NAS) is show below. Actual INCLUDE & EXCLUDE statements will vary from environment to environment and are not relevant to the CD Solution requirements. Note that the CDSYS.SYS driver is ahead of the NASDISK.SYS drives. This is required for proper drive pointer allocation.
The following batch file is for the workstations locally on the network. They will allow normal use of the CD ROM drives by individuals local to the LAN. Note that you do not have to use a CDUSE command as the line MSCDEX /D:MSCD001 /L:E does this.
The /L:nn is the start letter for the sequence of redirected CD drives. In this case our first CD drive is E:. The /D:MSCD001 is the CD device name from CBIS CD SERVER. This batch file accommodate IPX connections to the NAS.
C:
CD\CBIS
MSCDEX /D:MSCD001 /L:E
CDFICHE
3. A batch file on the NAS's C: drive as shown below. Unfortunately, you must allow users rights to access the NAS's local drives. This is accomplished by inserting a /LD parameter on the %1:SIGNON line in the NASSTART.BAT file. This potentially presents a security issue. Here we are using the CDREDIR and CDUSE commands as MSCDEX will attempt to redirect to drive A:. CDUSE F: J: will redirect the CD drive J: from the CD server to a local drive F:. The /O parameter is critical as it allows an override to previous redirection. Not including the /O parameter will cause the batch file to run properly the first time, but subsequent attempts will result in an error message of duplicate redirection. This batch file can be executed out of the LOGIN SCRIPT as EXIT 'CD.BAT'. It applies to users connecting to the NAS via the WNIM+ board. A conditional IF..THEN statement is recommended.
@ECHO OFF
CDREDIR
CDUSE F: J: /O
CDUSE G: K: /O
CDUSE H: L: /O
CD\CBIS
CDFICHE
CD\
4. A modification of the DVINTF.CFG file in the \ACCESS directory as shown below. DVINTF.CFG may or may not be created during NASGEN. It is a text file and may be created using an ASCII text editor.
DEVICE=C:\CDSYS.SYS /D:MSCD001 /N:<number of active CD drives>
LASTDRIVE=L
MAX DV TASKS=<maximum number of active sessions allowed>
MAX BUFFER LENGTH=<packet buffer size, max=1536, default=512>
NOTE: This is not a certification. Further testing is still needed.
FYI: LINK/64 LINK/T1 Internal Router with NetWare 2.15
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: LINK/64 LINK/T1 Internal Router with NetWare 2.15
DOCUMENT ID#: FYI.S.25
DATE: 07FEB92
PRODUCT: LINK/64 LINK/T1
PRODUCT VERSION: 1.1
SUPERSEDES: NA
SYMPTOM: Various
ISSUE/PROBLEM
The NetWare 2.15 drivers are in a subdirectory (NW215.INT) of the LAN_DRV_192/93 diskette. The instructions in the Manual do not make this clear and a NetWare 2.2 Internal Router may be installed in error when a NetWare 2.15 Internal Router is required.
SOLUTION
Manually copy:
1. The *.OBJ files from the NW215.INT subdirectory of the LAN_DRV_192 [or 193] diskette to the LAN_DRV_.192/193 subdirectory of your generation directory.
2. The proper BIN file to the SYSTEM subdirectory of the generation directory.
3. NWLT1.LAN/NWL64.LAN to the AUXGEN subdirectory of the generation directory.
4. Run NETGEN
FYI: WNIM Z-80 and Dead Ports
FYI
(Note: 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 claims to the validity of this information.)
TITLE: WNIM Z-80 and Dead Ports
DOCUMENT ID#: FYI.S.WNM04
DATE: 05FEB92
PRODUCT: WNIM
PRODUCT VERSION: Z-80
SUPERSEDES: NA
SYMPTOM: Port 3 and Port 4 Dead
ISSUE/PROBLEM
Some WNIM Z-80 cards shipped with bad cables. This results in ports 3 and 4 being DEAD.
The bad cables differ from the goods one by the following:
■ Not having the port number stamped on the RS-232 enclosure
■ Not having the Gateway name stamped on them
■ The port numbers marked by tie-on straps attached near the RS-232 end
The WNIM Z-80 cables with the metal 50 micro-pin enclosures are not bad. Only those cables made in white plastic are suspect.
SOLUTION
Exchange for another WNIM Z-80 board.
FYI: Files transfer empty when the KBD= parameter is used
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: Files transfer empty when the KBD= parameter is used
DOCUMENT ID#: FYI.S.24
DATE: 03FEB92
PRODUCT: 5250 File Transfer
PRODUCT VERSION: 1.38
SUPERSEDES: NA
SYMPTOM: Files transfer empty when the KBD= parameter is used
ISSUE/PROBLEM
During File Transfer a procedure called DBDLA is created. When NVLFTI is executed specifying the PUT Function, the data activation string DLBDA SECURITY is sent to the host.
KBD= specifies the language the of the string.
KBD=F for French speaking countries
KBD=G for German speaking countries
However, Version 1.38 of 5250 File Transfer does not process the parameter KBD= (Version 1.37 does), therefore, the string is not sent to the host correctly. The display shows the word SECURITY translated with or without the parameter.
The PUT function appears to work, the transfer operates normally and the file appears to be transferred. However, the file created is empty.
The GET function works properly.
SOLUTION
Page 7-3 of the NetWare 5250 File Transfer Guide shows the session parameter SSN with only one option when in fact there are three options: It should say SSN[s,kbd,tt] instead of SSN[s]
kbd specifies the keyboard select option to modify the Netware 5250 File Transfer Scan Code Table.
tt=0 (default) specifies that the built-in ASCII to EBCDIC Translation Table will be used -and normally doesn't need to be changed-, or, tt=1 specifies that the ASCII to EBCDIC Translation Table to be used will be the one in the 5250 Emulation Software.
These options can also be set through the environment variable DLSSN, by means of the SET command, in which case no parameters need to be added to the command line when executing NVLFTI.
In either case, it is very important to remember that commas have to be used in place of the parameters that will remain unchanged.
NVLFTI SSN[,G,1] will result in a first session with keyboard select option for Germany and the Translation Table of the 5250 emulation software. The same result is obtained running NVLFTI.EXE, without options after setting the environment variable: SET DLSSN=,G,1
(see Note 3-96 for further information)
FYI: Sobar Ticket Printer
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: Sobar Ticket Printer
DOCUMENT ID#: FYI.S.23
DATE: 31JAN92
PRODUCT: 3270 LAN Workstation
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: Printer error status "45"
ISSUE/PROBLEM
The SOBAR ticket printer is a serial printer that uses DSR to reflect when the buffers are full, paper out, etc. WSLAN on the other hand uses DSR to determine if power is on/off, and CTS for buffers full, paper out etc.
SOLUTION
To resolve this conflict the interface cable should be wired as shown below:
PC (9PIN) SOBAR (25PIN)
DCD 1 -------------------------- 1 CARRIER DETECT
TD 2 -------------------------- 3 RECEIVE DATA
RD 3 -------------------------- 2 TRANSMIT DATA
DTR __ 4 N/C 20 DATA TERMINAL
| READY
|
SG | 5 -------------------------- 5 SIGNAL GROUND
|
DSR |__ 6 /----------- 6 DATA SET READY
/
RTS 7-------------/------------- 4 REQUEST TO
/ SEND
CTS 8-----------/
FYI: French and International Code Page
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: French and International Code Page
DOCUMENT ID#: FYI.S.MAC01
DATE: 30JAN92
PRODUCT: 3270 Lan Workstation for Macintosh
PRODUCT VERSION: 1.0
SUPERSEDES: NA
SYMPTOM: "3270 emulator error: could not locate resource BCEB 1609"
ISSUE/PROBLEM
"3270 emulator error: could not locate resource BCEB 1609"
> When the French Code Page is chosen the following error is received:
"3270 emulator error: could not locate resource BCEB 1609".
> When the International Code Page is chosen, it is reflected as the French Code Page.
SOLUTION
The problem occurs because the EBCIDIC code resources are improperly mapped between the International and French Code Page.
To correct the problem use RESEDIT, before starting review the RESEDIT section of the manual.
1. With RESEDIT, open the 3270 Lan Workstation for Macintosh application.
2. Select the BCEB type and double click on the module. Another pop-up window will appear with ID's ranging from 1600 to 1611.
3. ID 1609 is skipped. Select ID 1610 and do a GET INFO on the resource. (or, after selecting ID 1610, hold down the Apple-I key sequence)
4. In the ID field, change 1610 to 1609. Close the get info box on this ID by double clicking on the small upper left hand box.
5. Select ID 1611 and do a get info on this resource.
6. In the ID field change 1611 to 1610. Close the get info box on this ID by double clicking on the small upper left hand box.
7. Close the BCEB resource box by double clicking on the small upper left hand box.
8. Close the 3270 LAN Workstation for Macintosh window by double clicking on the small upper left hand box and answer YES to save the changes to the application.
NOTE: This a temporary work around. A future version will correct the problem.
FYI: Two 3270 LAN Workstation for MAC Problems
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: 3270 LAN Workstation for MAC, 3270 Printing
DOCUMENT ID#: FYI.S.MAC02
DATE: 20JAN92
PRODUCT: 3270 LAN Workstation for MAC, 3270 Printing
PRODUCT VERSION: 1.0
SUPERSEDES: NA
SYMPTOM: 1. A Bomb
2. Failure to print
ISSUE/PROBLEM
1. Using a MAC+ only, when launching the 3270 application it may BOMB with an id=12 (a picture of a BOMB with a fuse) this indicates that debug stop points were inadvertently left in the code.
2. When trying to print 3270 host screens via the SETTINGS pull down menu, the PRINTER FONT defaults to NOVELL 3270.
This is ONLY while trying to perform host screen prints FROM the MACINTOSH.
SOLUTION
DO NOT use the Novell "3270 Font" choose another font instead.
The MAC 3270 Workstation does NOT currently directly support 3287 printing but you may direct host print jobs to a DOS WSLAN 3287 printer session.
The problem will be corrected in a later release.
FYI: Novell No Longer Sells WNIM
FYI
(Note: 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 claims to the validity of this information.)
TITLE: Novell No Longer Sells WNIM
DOCUMENT ID#: FYI.S.WNM03
DATE: 02JAN92
PRODUCT: WNIM
PRODUCT VERSION: All (WNIM, WNIM+, WNIM-Z80)
SUPERSEDES: NA
SYMPTOM:
ISSUE/PROBLEM
Novell no longer sells WNIM.
SOLUTION
Microdyne now sells WNIM+ and Z80. For information, contact Microdyne at 800-326-6363.
FYI: DOS ERRORLEVEL and Printing ZAP
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: DOS ERRORLEVEL and Printing ZAP
DOCUMENT ID#: FYI.S.22
DATE: 31DEC91
PRODUCT: Netware 3270 Workstation for DOS
PRODUCT VERSION: 2.0
SUPERSEDES: NA
SYMPTOM: - Slow Printing
- DOS ERRORLEVEL Function Not Supported
ISSUE/PROBLEM
1. The speed of DOS redirectable print jobs was slowed down in version 2.0 of WSLAN.
2. Although Version 1.2 of the Workstation supported DOS ERRORLEVEL Version 2.0 does not.
SOLUTION
Contact Novell Tech Support for a patch and directions for use.
On NetWire contact:
Bill Olsen 76702,1447
Bob LoFaso 76701,146
OR Call 800-NETWARE
FYI: WNIMs and the Newport X.25 Adapter
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: WNIMs and the Newport X.25 Adapter
DOCUMENT ID#: FYI.S.17
DATE: 06DEC91
PRODUCT: Access Server (NAS)
PRODUCT VERSION: 1.2 with Newport X.25 Adapter
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The Newport Systems XCI X.25 adapter will work in Version 1.2 Access Server (NAS) which also contains one or more WNIM+ boards.
SOLUTION
Some tips:
1. The default hardware address for the XCI adapter is C80000, but if your NAS has more than 12 megabytes of memory, you CANNOT use this address. You must select some other address range such as D00000. THe WNIM+ and XCI drivers are written to a Novell specification which lets both use the same hardware address. Thus a single hardware memory addresse may be specified for both adapter types. Disregard any warnings or other discrepancies. It works!
2. When you run NASGEN to install the hardware adapters, install the WNIM(S) first, then your XCI adapter. That way the first X number of ports are based on the number of async ports. The remaining ports are simply allocated to the X.25 adapter, until the maximum of 16 ports has been reached.
3. Configure the X.25 ports (logical ports) to modem = none.
4. If your remote site is using an X.25 PAD, configure the pad to CCITT profile 89. If 89 is not available, choose profile 91 and modify the profile to suit your needs.
FYI: SAA Guide Correction
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: SAA Guide Correction
DOCUMENT ID#: FYI.S.21
DATE: 02DEC91
PRODUCT: NetWare for SAA
PRODUCT VERSION: 1.1
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Errors in the NetWare for SAA version 1.1 Administration Guide and Addendum.
SOLUTION
Please make pen and ink changes to correct the following errors on Pages 5-15, 5-16, and 5-17 of the Guide:
1. All load token node statements should specify 8 digits (node=7093xxxx) instead of 9 digits (70093xxxx).
2. Both Maximum and Minimum Packet Receive Buffers must be set:
> SET MAXIMUM PACKET RECEIVE BUFFERS=2000 must be included in AUTOEXEC.NCF (not STARTUP.NCF).
> SET MINIMUM PACKET RECEIVE BUFFERS=500 must be included in AUTOEXEC.NCF
FYI: SAA & Nearest Server
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: SAA & Nearest Server
DOCUMENT ID#: FYI.S.19
DATE: 08NOV91
PRODUCT: NetWare for SAA
PRODUCT VERSION: NA
SUPERSEDES: NA
SYMPTOM: WSLAN unable to find SAA Server
ISSUE/PROBLEM
WSLAN uses "Get Nearest SAA File Server" to reach the nearest SAA Server. That means that it must be able to reach a file server or router that has a router table which will tell it where the nearest SAA Server is. If all SAA Servers AND File Servers in the segment have Get Nearest turned OFF, WSLAN will not know where to find an SAA Server unless a router on the segment has the capability to provide SAA server information.
The above is true only for the standard version of NetWare for SAA. With the run time version, nearest server = OFF will not stop WSLAN from finding the SAA server.
SOLUTION
Testing on how does the set reply to get nearest server = ON/OFF affect the WSLAN to locate the SAA server. Original we had different conclusion, but after we took a good look of each version, BOTH are valid. Here is the catch...
1. On the NW 3.11 Run time version.
If the SET reply to get , it has no effect on the WSLAN's server request. Wslan will get response.
2. ON the standard NW 3.11 version.
If the SET reply to get nearest server = OFF, BOTH the WSLAN and NETx's request will be ignored.
FYI: SAA & Token Ring Cards
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: SAA & Token Ring Cards
DOCUMENT ID#: FYI.S.18
DATE: 07NOV91
PRODUCT: NetWare for SAA
PRODUCT VERSION: NA
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The following may be interpreted as contradictory.
1. An SAA Server may have only two Token Ring cards.
2. A separate Token Ring card is recommended for the LAN and the Host.
3. The documentation specifies a separate card for each host.
SOLUTION
There are a number of choices:
- You can use one card for the LAN and use the other to go to the two hosts:
> If you have two 3174s because each would be running a different SAP.
OR
> If you have two 9370s on the same ring because the 9370 can support multiple SAP IDs on the TIC.
- If you have only one 3X74 or 37XX FEP you can use one card for onehost and one card for the other host and LAN traffic. This is differnt from the recommendation but will work.
FYI: Redirectable Screen Print Performance
FYI
(Note: 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 claims to the validity of this information.)
TITLE: Redirectable Screen Print Performance
DOCUMENT ID#: FYI.S.WSD01
DATE: 01OCT91
PRODUCT: 3270 LAN Workstation for DOS
PRODUCT VERSION: 2.0
SUPERSEDES: NA
SYMPTOM: slow printing
ISSUE/PROBLEM
Screen printing with the redirectable option was slowed somewhat in the design of v2.0 (relative to prior versions) in order to gain performance in other areas of the program.
SOLUTION
Upgrade to v2.02. Version 2.02 contains an option which allows greater or less priority to be devoted to redirectable printing.
FYI: NEWPORT SYSTEMS SOLUTIONS' X.25 COMMUNICATIONS INTERFACE
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: Access Server (NAS) and NEWPORT SYSTEMS X.25 Board
DOCUMENT ID#: FYI.S.16
DATE: 05SEP91
PRODUCT: Access Server (NAS)
PRODUCT VERSION: 1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The X.25 Communications Interface (XCI) from Newport Systems Solutions, Newport Beach, CA, provides X.25 connectivity for the NetWare Access Server (NAS) V1.2 allowing remote users to take full advantage of X.25 Public Switching Networks (PSN):
Reduces Host Site Requirements
The XCI can multiplex 16 users on a single physical link to an X.25 network. In a fully configured Access Server (NAS), one synchronous modem and line to the X.25 network replaces 16 separate asynchronous modems and associated lines that would otherwise be required to accommodate 16 users. The XCI requires only one slot in the Access Server (NAS), compared to the asynchronous WNIM+ configuration that requires four slots.
Multiple Connection Options
Multiple connections options allow both remote PC users and remote LAN users to access the Access Server (NAS).
- A remote PC or asynchronous terminal can dial into X.25 PADs (Packet Assembler/Disassemblers), i.e., a remote PC running OnLAN/PC can communicate via an asynchronous communications line and modem to an X.25 asynchronous PAD, which in turn is connected to an X.25 PSN.
- A LAN workstation can run OnLAN/PC communicating via an synchronous communications server, which utilizes an asynchronous line and modem communicating to an X.25 asynchronous PAD.
- A LAN workstation can dial directly into an X.25 network for a communications path to the Access Server (NAS). This is done by running OnLAN/PC communicating via a LAN X.25 gateway, which is connected to an X.25 PSN via a synchronous communications line and modem.
Local Charges for End Users
Remote end users are charged for local access into the X.25 network instead of for a long distance call to the central host site. Charges are for connect time and amount of data sent, not for distance, which could be extremely important for international companies. Both public and private X.25 networks are supported in most foreign countries.
Support for Multiple Ports per WNIC
The WNIC supports two synchronous ports at speeds up to 64 Kbps per port. Each port could support up to 16 users, although most users would employ only one port for communications, saving the second port to connect to a second X.25 network. If both ports are connected to the same X.25 network, the number of users can be split over each port to provide more bandwidth per user than is possible with only one port connected to the X.25 network. The XCI ports support RS-232, RS-422, V.35 and X.21 line interfaces.
X.25 Configurator Included
All X.25 parameters are factory set to default values. An X.25 Configurator is included to allow customizing of X.25 parameters, if necessary.
Additional X.25 Features
Some additional X.25 features supported by XCI are:
- Support for both Switched (SVCs) and Permanent Virtual Circuits (PVCs).
- Automatic configuration of remote terminal profile to condition the remote PAD for proper operation with the XCI.
- Configurable to accept or reject collect calls.
- Configurable for DCE (Data Circuit Equipment) operation to allow direct connection without an intervening X.25 PSN.
- CCITT X.25 1988 compliant.
X.25 Statistic Utility
From the Access Server (NAS) console, the user may display XCI operational statistics and status by using a menu-driven program. X.25 link and packet statistics are displayed side by side for a selected link. Port statistics and status provide information about the current or last X.25 call to the port. Links may also be enabled or disabled from this utility.
Automatic Installation
Utility automatically installs the XCI software. The NetWare Access Server (NAS) Generator (NASGEN) must be run after XCI installation.
Reliable Hardware Adapter
XCI software runs on the WNIC (Wide-Area Network Interface Coprocessor), a 16 bit coprocessor that uses one slot in a PC/AT. The WNIC has 512 Kbytes of dual-ported RAM. The main on-board processor is a 10 Mhz, 16 bit NEC V50 microprocessor with four channel DMA (Direct Memory Access) support.
Compatibility
The XCI can coexist in the Access Server (NAS) with NetWare's WNIM+ or Newport Systems Solutions' ACI (Asynchronous Communications Interface) product.
Novell Tested and Approved
XCI is Novell tested and approved. Newport worked very closely with Novell during all phases of XCI development and verification to ensure complete compatibility.
FYI: Microcom Token Ring Bridges
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: Microcom Token Ring Bridges
DOCUMENT ID#: FYI.S.13
DATE: 23JUL91
PRODUCT: NetWare 3X
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: File servers can intermittently not be seen
ISSUE/PROBLEM
The Microcom bridges see SAPs from NetWare 3x servers as tokens they, the bridges, put on the ring.
Since the bridges think the token was one they put on the ring they purge the token from ring. This means the SAPs can not get to other servers.
Since the SAPs are not received by other servers these servers delete the SAPing server from their router tables. The SAPs are not consistently purged so some SAPs get through and some do not.
NetWare 3x SAPS are different then 286 SAPs. 3x SAPs do a directed broadcast with the destination address of FFFFFFFF {all F's}. Netware 286 servers SAP with a destination address of C04FFFFF and the Microcom bridges do not have a problem with such broadcast addresses.
SOLUTION
Microcom has prepared a patch and it can be secured from them.
FYI: NACS/NASI Compatibility
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: NACS/NASI Compatibility
DOCUMENT ID: FYI.S.1
DATE: 15JUL91
PRODUCT: NACS
PRODUCT VERSION: All
SUPERSEDES: Earlier dates of FYI1
SYMPTOM: NA
ISSUE/PROBLEM
See below
SOLUTION
As shown below many communications programs are compatible with NACS for calling out purposes. However, only two products are known to be able to call into a NACS and take over a workstation on the LAN:
1. PCAnywhere (Including AnywhereIV LAN) from DMA, 516-462-0440 is NACS/NASI compatible for calling BOTH in AND out.
2. A version of CoSession, 516-462-0440.
- OnLAN Version 1.2 is NACS/NASI compatible.
- The most recent version of LEXUS is compatible with the most recent version of NACS/NASI.
- West Law is compatible.
- ASCOM IV Version 1.41 is compatible (sold by DMA,516-462-0440).
The following are claimed by their manufacturers to be NACS/NASI compatible:
Product Version** Telephone #
Crosstalk Mark 4 V1.1 and later 800-348-3221
Crosstalk for Windows* v1.2 " " "
Crosstalk 16 Network V3.71 " " "
DynaComm Asynch* V3.0Z 713-496-9400
EM220 V4.0 and later 303-447-9251
EM320 All " " "
EM4010 All " " "
EM4105 All " " "
Mirror III LAN All "LAN" 800-634-8670
PCTerm All 206-487-3656
PolyCom All 314-432-4142
PolyStar All " " "
PolyNet*** All " " "
Procom+ Network V1.0 314-474-8461
Reflection All but Mac V 206-324-0407
Relay Gold LAN V3.0 & later 800-822-8224
Smartcom Exe V2.1 404-441-1617
Smartcom III V2.0 " " "
SmartTerm 240 V3.0 & later 800-368-5283
SmartTerm 320 All " " "
SmartTerm 340 All " " "
SmartTerm 470 All " " "
SoftermPC 2.0 & later 719-593-9550
Softerm Modular All " " "
VsCom Novell V6.0 & 312-443-1222
VsCom LAN All " " "
- A compatible version of TAPCIS is being developed.
* Windows application
** Later versions may also be compatible
*** ODI
FYI: WNIM Z-80 Boards and US Robotics Rack Mounted V.32 Modems
FYI
(Note: 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 claims to the validity of this information.)
TITLE: WNIM Z-80 Boards and US Robotics Rack Mounted V.32 Modems
DOCUMENT ID#: FYI.S.WNM02
DATE: 01JUL91
PRODUCT: WNIM
PRODUCT VERSION: Z-80
SUPERSEDES: NA
SYMPTOM:
ISSUE/PROBLEM
The WNIM Z-80 board, on boot of the computer, brings pin 25 high (Pin 25 is usually unassigned or busy). The USR rack mount (but not stand alone external) modems use this pin to signify that the modem is busy. Therefore, all the attached modems go off hook.
SOLUTION
Cut pin 25 on the WNIM interfaces or cut pin 17c on the USR modem interface module. Pin 17c controls pin 25 on port 0 for the USR high speed modems. Their 2400 baud modems use two ports. Call US Robotics for the appropriate pin to cut if you run into a problem.
FYI: H.P. Vectra Classic with 3270 Multi Workstation
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: H.P. Vectra Classic with 3270 Multi Workstation
DOCUMENT ID: FYI.S.11
DATE: 24JUN91
PRODUCT: NetWare 3270 Multi Workstation
PRODUCT VERSION: 1.1
SUPERSEDES: NA
SYMPTOM: Workstation hangs upon loading Multi Workstation
ISSUE/PROBLEM
When loading WSMULTI on a H.P.Vectra Classic the PC hangs.
Note: A cold boot was required to remedy this problem.
SOLUTION
There is a conflict with Multi's API interrupt which defaults to H "6F" and the Vectra Classic extended BIOS. Changing the Multi Workstation API interrupt address to H "5F" resolved this problem.
FYI: WNIM Switch Settings
FYI
(Note: 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 claims to the validity of this information.)
TITLE: WNIM Switch Settings
DOCUMENT ID#: FYI.S.WNM01
DATE: 12JUN91
PRODUCT: WNIM
PRODUCT VERSION: Z80
SUPERSEDES: NA
SYMPTOM: Card not initializing.
ISSUE/PROBLEM
There have been reports a few WNIM Z-80 boards being manufactured with the dip switches upside down.
SOLUTION
Set the switches that would ordinarily be in the up position to the down position and vice versa.
FYI: Modem Pooling in a NetWire Environment
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: Modem Pooling in a NetWire Environment
DOCUMENT ID#: FYI.S.7
DATE: 01MAY91
PRODUCT: Access Server (NAS), NACS
PRODUCT VERSION: NA
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
SOLUTION:
It is feasible to provide modem access to and from a NetWare LAN through a single point. Many organizations find this cost effective because it avoids providing a modem and phone line at every workstation which might have a reason to use a modem. A number of companies manufacture products which provide this ability. Novell produces, sells, and provides technical support for two; Access Server (NAS) and NACS.
For Calling into A NetWare LAN
NetWare Access Server (NAS)
NetWare Access Server (NAS) software enables up to 16 remote users to dial in to a NetWare LAN and access all the services and files available on the network including applications, electronic mail and access to mainframes and minicomputers. The software turns a DEDICATED 80386 (or 486) Industry Standard Architecture (ISA) bus machine into a remote communications server by dividing the 386 (or 486) CPU into as many 640KB machines as installed RAM allows (up to 16). Each remote user calling in receives one or more of the virtual sessions in which to their work.
Remote users can dial into an Access Server (NAS) through asynchronous modems or multiplexers using any PC or Macintosh, or most ASCII terminals. "ONLAN/PC" and "ONLAN/Mac" are provided with the Access Server (NAS) and provide a particularly smooth interface with Access Server (NAS). However, many terminal emulation programs may be used a substitute for ONLAN/ONLANMAC with some limitations. "ONFILE" is also included with the Access Server (NAS) software and is the only supported method of file transfer. Each owner of an Access Server (NAS) is authorized to provide unlimited copies of ONLAN/PC and ONLANMAC to any site which may call the Access Server (NAS).
Because all processing is handled by Access Server (NAS), only screen updates and keystrokes travel over the asynchronous lines and file access occurs at LAN speeds.
Besides normal NetWare security there are number of specific Access Server (NAS) security features which optionally may be used including:
- Dial Back" which does not allow a caller to have a session until they have been called back at a telephone number specified by the network supervisor.
Access Server (NAS) allows the use of expanded memory above the 640 base for each individual session.
For more information about Access Server (NAS) see the "Rules of Thumb" for Access Server (NAS) and it is important that you read it before making any decisions regarding hardware (including modems) and software to use with Access Server (NAS).
For Calling Into or Out of a NetWare LAN
NACS
The NetWare Asychronous Communications Server (NACS) turns a DEDICATED IBM PC/IBM PC AT or compatible into an asychronous communications server that allows up to 16 network stations to simultaneously call out of a LAN or to be accessed by a call into the LAN.
Unlike Access Server (NAS), applications are not processed within the NACS but calls simply go through the WNIM+ ports on the NACS instead of the PCs COMM port. Users only have to specify a port by name in order to connect to a particular modem or line. In addition, NACS is capable of "rotating" if a port is busy.
The recommended hardware for a NACS is:
- An IBM AT or close compatible (but an XT or compatible will work) with:
- A CGA OR MONOCHROME Video Adapter (Has no effect on caller's displays)
- Not more 512K RAM (will run but not configure with 256K)
- 10 MHz or more
- In addition the following is REQUIRED:
- One WNIM or WNIM+ card for each 4 simultaneous connections.
- "NASI Compatible" communications software. (A list is provided in NACCOM.TXT in NOVA Library 9.
- One asynchronous modem for each port to be used. (A NACS can also be connected directly to the asychronous ports on a Mini or Mainframe computer.)
- The NACS machine may not have a microchannel bus.
The Decision
NOTE: There is no practical special limit on the number of Access Server (NAS)s and NACS that can coexist on the same LAN.
1. For the best support for incoming calls Access Server (NAS) is recommended.
2. For the best support for outgoing calls NACS is recommended.
3. For a LAN with a large amount of outgoing calls and a small amount of incoming calls NACS is recommended. However, each incoming call will a require a separate workstation in "call waiting status". With appropriate "NASI Compatible" software.
4. For a LAN with a large amount of outgoing calls AND a large amount of incoming we recommend that both an Access Server (NAS) and a NACS be secured.
5. If there will only be 1 or 2 simultaneous incoming or outgoing calls at one time and you do not require the special feature of Access Server (NAS) or NACS you may wish to explore third party products.
Limitations
1. The large amount of data required to be transmitted across the phone lines for intensive graphics makes asynchronous remote use less than completely practical for such applications.
2. Mice and similar tracking devices do not lend themselves to use across asychronous lines.
FYI: Mapping the F keys for Access Server (NAS)
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: Mapping the F keys for Access Server (NAS)
DOCUMENT ID#: FYI.S.3
DATE: 19APR91
PRODUCT: Access Server (NAS)
PRODUCT VERSION: 1.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Maping the F keys for Access Server (NAS)
SOLUTION:
To map the F keys for Access Server (NAS) with a particular terminal
1. You have either a FASTART.TMP or HASTART.TMP file.
Temporarily modify it by inserting PAUSE right after ANYWNAS
2. Then bring up the Access Server (NAS).
"Hit Any Key" will appear on the screen.
Hit CONTROL-BREAK
Answer YES to the question "BREAK BATCH?"
Type "MODTERM" (enter)
Choose the terminal type
Choose KEYBOARD SEQUENCE
Choose FUNCTION KEYS
Use "K" to kill for each Function key to be programed
Hit SPACE to change
At each function key spot hit the proper "F key".
F10 to save
3. Change FASTART/HASTART back to original (no pause).
4. Reboot
FYI: NetWare SNA Glossary
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: NetWare SNA Glossary
DOCUMENT ID#: FYI.S.9
DATE: 01APR91
PRODUCT: SNA
PRODUCT VERSION: NA
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
ACCESS CODE
In Novell LAN-based 3270 and 5250 communications products, a name with up to 15 characters used to select a host session or group of host sessions through a specified gateway server. On the server, a host session, a group of up to 5 host sessions, or a pool or such sessions or session groups is defined under the access code.
ACF/NCP
Advanced Communications Function/Network Control Program. Software resident in an IBM 37x5 communications controller that manages communication between the host system attached to the controller and other devices on the network (usually, but not necessarily an SNA network).
ACF/TCAM
Advanced Communications Function for the Host/Telecommunications Access Method
ACF/VTAM
Advanced Communications Function for the Virtual Telecommunications Access Method. System program which runs on an IBM host computers and controls communication between host application or service programs and terminals. The prefix ACF distinguishes contemporary VTAM releases from earlier ones which provided much less comprehensive support.
ADAPTER
See LAN adapter.
ADDRESS
An identifier for a physical or logical device on a network. In SNA networks, each physical unit, logical unit and system service control point has an address. In local area networks, each node on the network has an address.
ADVANCED PROGRAM-TO-PROGRAM COMMUNICATION
See APPC
API
Application Programming Interface.
The module of network software that communicates with a user's application. In networks built on the ISO OSI model, APIs usually work on the seventh layer.
APPC
Advanced Program-to-Program Communications. An IBM protocol for developing peer-to-peer communications that allows programs to communicate with equal control. APPC is implemented through LU 6.2.
APPLICATION LAYER
The seventh layer of the ISO OSI model. This layer passes requests and responses between the network and applications.
ASCII (American standard Code for Information Interchange)
A code for representing characters to a processor; each character is represented by 7 bits with an optional eighth bit for parity checking. ASCII is used on microcomputers; EBCDIC is used on IBM host computers.
AS/400
IBM mainframe computer that can act as a host for a Token-Ring gateway connection.
BROADCAST
To send a message to all users on a network.
CLUSTER CONTROLLER
Also known as a control unit (IBM model numbers 3174, 3172, 3274). A machine that supervises terminals and other peripherals. When personal computers are connected to a host computer through a gateway, the gateway server functions as a cluster controller.
COAXIAL CABLE
Frequently called coax cable, a cable consisting of one conductor within another conductor, covered by an outer insulating shield. Coaxial cable is sometimes used to connect the gateway server to the host.
COMMUNICATIONS CONTROLLER
Also known as a front-end processor (IBM model numbers 3725, 3745, 3705, 3720). In remote environments, a machine directly attached to a host computer, that processes communication requests.
CONNECTIONLESS SYSTEM
A network type that treats each packet as an individual system communication (IPX, for example). Each packet contains a destination address, allowing it to be delivered independent of any other packet.
CONNECTION ORIENTED SYSTEM
A network in which two nodes establish a session before they communicate. During the session, the two nodes communicate only with each other. When the transmission is complete, the session is ended.
CONTROL UNIT
See cluster controller.
CUT
Control-Unit Terminal. An IBM 3270 terminal attached to a cluster controller that processes its keystrokes and managers its buffers. A control-unit terminal can support one host communications session at a tine.
DATA FLOW CONTROL LAYER
The fifth layer of the SNA model. The data flow control layer manages sessions and provides error recovery.
DATA LINK CONTROL LAYER
The second layer of the SNA model. The data link control layer constructs frames from a bit stream.
DATA LINK LAYER
The second layer of the ISO OSI model. The data link layer handles the translation between the electrical signals transmitted by the physical layer and the bit patterns required by the higher layers.
DATA LINK TRACE
In the SNA Gateway, a diagnostic test in which the gateway simulates the host to check for proper LAN functioning.
DATA STREAM
Data that is flowing between points on a network. A data stream is usually a succession of messages.
DFT
Distributed Function Terminal. A coaxially-connected device that does not require cluster-controller interaction to respond to keystrokes.
DISTRIBUTED PROCESSING
A data processing type in which more than one processor shares the execution of an application. In SNA networks, distributed processing is implemented through APPC.
DOS (Disk Operating System)
The initial operating system used for System/360 mainframes; also, a loose term for a personal computer operating system, short for PC-DOS or MS-DOS.
EBCDIC is for mainframes what ASCII is for microcomputers to represent different characters.
EGA (Enhanced Graphics Adapter)
A display adapter for personal computers that provides monochrome or color monitors with 350-line resolution and graphics capabilities.
END USER LAYER
The seventh layer of the SNA model. The end user layer is the interface between the SNA network and user applications.
FRAME
A message sent over a network. A frame usually contains data plus address, control, and error-check information. On a LAN, this structure is frequently called a packet.
FREE TOKEN
A unique sequence of bits transmitted on a token ring network. Each node must wait for the token before it transmits.
FRONT-END PROCESSOR (FEP)
See communications controller.
GATEWAY
A network node that operates as an interface between different network types. Also a gateway server.
GATEWAY SERVER
A personal computer that runs NetWare SNA Gateway or NetWare SNA Gateway ELS software, and has a LAN adapter, and a host interface adapter that enables data transmission between gateway workstations and a host computer.
GATEWAY WORKSTATION
A personal computer in a LAN that is connected to the gateway server and runs NetWare 3270 LAN Workstation software.
HALF-DUPLEX
A two-way data transmission mode where data between two points is sent one direction at a time.
HOST
The controlling computer on a network, similar to a file server on a LAN. In SNA Gateway environments, the host is usually a mainframe or minicomputer.
HOST INTERFACE ADAPTER
An add-in board for personal computers that can provide direct or remote connections to a host computer.
HOST SESSION
A temporary logical connection established between two network addressable units; for example, a gateway workstation and a host computer.
IBM 3174
A 3270 series cluster controller, introduced in 1987, that can support Category A coaxially-connected devices (in CUT mode or DFT mode, single and multiplexed) and/or Token-Ring devices.
IBM 3270
IBM terminals that include models 3278, 3279, 3178 and the 3287 host-addressable printer.
IBM 3274
A 3270 series cluster controller, that can support Category A coaxially-connected devices (in CUT mode or DFT mode, single and multiplexed).
IBM 37XX FRONT END PROCESSOR
A 3270 series IBM front-end processor that includes the 3705, 3720, 3725 and 3745 models. With its associated software, ACF/NCP, the 37XX controls the operation of a number of attached communication lines, which may be operating in a variety of modes and under a variety of protocols. The 3705 is no longer manufactured, but is often used as a non-specific reference for compatible communications.
IBM TOKEN RING LAN
A local area network access mechanism and topology in which a supervisory frame or token is passed from station to station in sequential order. To gain access to the network, stations must wait for the token to arrive before transmitting data. In a token ring, the next logical station receiving the token is the next physical station on the ring.
INTERNETWORK
An interconnected group of networks.
IPL (Initial Program Load)
A command used to restart a host computer or a host virtual machine. Similar to reboot on a personal computer.
IPX/SPX (The Internetwork Packet Exchange/Sequenced Packet Exchange protocol)
The Novell communications protocol for transmitting data packets on a LAN installed with NetWare.
ISO (International Standards Organization)
The group that developed the OSI Reference Model.
KBPS (Kilobits per second)
A unit of measure for high-speed data transmission.
LAN
See local area network.
LAYER
Part of a network architecture that performs services and passes data to another part. Many network architectures are designed with seven layers, with each layer providing isolated functions.
LEASED LINE
A dedicated or private line leased for exclusive use.
LOCAL AREA NETWORK (LAN)
Personal computers and peripherals within a small area (such as a building or part of a building) that are linked so that they share data and resources.
LOGICAL LINK
The top sublayer of the data link layer. This sublayer control passes data to higher layers; the protocol differs (LLC) according to the network.
LOGICAL UNIT
A software component of an SNA network that allows a person or application to access the network; also called an LU. To the network, each user (whether a person or an application) is an LU.
LU
See logical unit.
LU6.2 (Logical unit type 6.2)
In SNA networks, the logical unit that implements distributed processing and peer-to-peer communications.
MULTICAST
To send a message to more than one user on a network simultaneously.
MULTIPLEXER
A device that accepts many data lines and combines them into a single, high-speed, composite data stream.
NAU (Network Addressable Unit)
A location in an SNA network that supports one or more ports for communication through the network.
NAU SERVICES LAYER
The sixth layer of the SNA model. The NAU services layer provides presentation services and session services to user processes.
NCP
See network control program.
NetBIOS (Network Basic Input/Output System)
A network protocol used on many LANs. The Novell IPX/SPX protocol is a similar protocol.
NETWORK ADDRESSABLE UNIT
In an SNA network, a logical unit, physical unit or system service control point.
NETWORK CONTROL PROGRAM (NCP)
Firmware in a communications controller that processes control interrupts for the host.
NETWORK LAYER
The third layer of the ISO OSI model. The network layer performs switching and routing, especially important in large internetworks.
NODE
In a network, a physical point where components connect to each other. Loosely, a component of the network. For example, a workstation is a node on a LAN. Cluster controllers or host computers are nodes in SNA networks. Nodes on a LAN are similar to logical units and physical units in SNA networks.
OFF-LINE TEST
In the NetWare SNA Gateway, a diagnostic test used to check for problems in the connection between the gateway and the host.
OSI MODEL
Open Systems Interconnection Reference Model. The architecture developed by the ISO to standardize networking and data communications. The OSI model has seven layers: the physical, data link, network, transport, session, presentation, and application layers. The OSI model is frequently used for microcomputer networks, and the SNA model, for IBM host computer networks.
PACKET
A unit of information sent over a network. A packet contains data and control and address information. Packet is commonly used with microcomputer networks, and frame, with mainframe networks; the terms are synonymous.
PATH CONTROL LAYER
The third layer of the SNA model. The path control layer handles routing and traffic control. For example, it might group unrelated packets to send to the same address.
PATH CONTROL NETWORK
The part of an SNA network that links the network units and handles physical transmission. The path control network is similar to the physical and data link layers of the ISO OSI model.
PEER PROCESS
In a network model, processes operating on the same levels of different computers; for example, on layer 7 of computer A and layer 7 of computer B.
PEER-TO-PEER NETWORK
A network whose nodes can each act with equal authority, without having a master-slave relationship.
PHYSICAL COMMUNICATION
The actual transmission of data from one computer to another; this occurs on the physical layer of the OSI or SNA model.
PHYSICAL LAYER
The hardware connection (for example, cabling) between two computers used for transmitting data.
PHYSICAL UNIT (PU)
An SNA software component that manages a physical device and represents it to the network. Each PU supports one or more logical units (LUs). The closest microcomputer term is node, although it does not distinguish between physical and logical types.
POOLING
A method of assigning codes that control host session allocation on LAN workstations. Host sessions can be pooled in one of the three following ways:
1) All workstations use the same access code.
2) All workstations use a unique access code.
3) Some workstations use the same access code.
PRESENTATION LAYER
The sixth layer of the ISO OSI model. It performs layer frequently used routines, such as translating data between EBCDIC and ASCII.
PRESENTATION TRACE
A diagnostic trace used in the gateway to check the data flow between the gateway and the workstation.
PRIMARY STATION
In an SNA network, the station that controls the link and determines when other stations may transmit. Compare secondary station.
PROTOCOL
A set of rules, including data format and error handling, which governs communication between computers.
PU
See physical unit.
REBOOT
To restart a microcomputer. In host systems, this is frequently called an IPL or an IML.
RS-232-C
An Electronics Industries Association (EIA) standard for a common connection used to attach microcomputers to peripherals.
SESSION LAYER
The fifth layer of the ISO OSI Model, providing administrative jobs for the network, such as security.
SDLC (Synchronous Data Link Control)
A protocol used to transfer data in SNA environments.
SECONDARY STATION
In an SDLC configuration, a station that is governed by a primary station. When using the SNA Gateway, the workstations are secondary stations.
SESSION
A logical connection between two nodes in a network that allows them to exchange messages.
SNA
See Systems Network Architecture.
SNA model
The seven-layer model for network operations that is part of the Systems Network Architecture. Compare OSI model.
SPX (Sequenced Packet Exchange)
A protocol that allows two workstations or applications to communicate across the network. SPX uses the Internetwork Packet Exchange (IPX) protocol to deliver the messages.
STATUS WORK
One of the frame types sent from the gateway server to the host in response to a poll command, indicating the status of the gateway server.
SWITCHED LINE
Within a network, a line that is switched to establish a continuous pathway between the sender and the receiver.
SYNCHRONOUS
A data transmission mode that synchronizes entire blocks of data.
SYSTEMS NETWORK ARCHITECTURE
A set of protocols, message formats, and other specifications developed by IBM that unites several generations of computers, operating systems, peripheral devices, and telecommunications systems. SNA specifies how computer equipment connects and communicates.
SYSTEM SERVICE CONTROL POINT
An SNA software component that manages the network or a portion of it.
TERMINAL
A device with a keyboard and a monitor that sends and receives information on a network. A terminal usually cannot function as an independent system.
TIC
See token ring interface coupler.
TOKEN FRAME
A structure that contains data on a token ring network. When a node has data to transmit, it replaces a free token with a token frame.
TOKEN RING INTERFACE COUPLER (TIC)
Device on IBM 3725 or 3745, allowing the use of Token Ring topology for communication with local terminal emulation devices. The IBM 3174 cluster controller provides the same capability by way of its optional token-ring adapter. In many cases, the IBM 3174 will communicate with both the host and the terminal emulation devices via the Token Ring.
TRANSMISSION CONTROL LAYER
The fourth layer of the SNA network. This layer creates, manages and ends sessions.
TRANSPORT LAYER
The fourth layer of the ISO OSI model. This layer handles layer the sequencing and guaranteed delivery of packets.
VIRTUAL COMMUNICATION
Communication between corresponding layers of two computers in a network. For example, between layer 7 of one computer and layer 7 of another. Data is not transmitted directly between the corresponding layers.
VIRTUAL TELECOMMUNICATION ACCESS METHOD (VTAM)
See ACF/VTAM.
WORKSTATION
A network device that contains a central processing unit, a keyboard and a monitor. The closest mainframe equivalent is a terminal; however, terminals do not contain CPUs.
SOLUTION: NA
FYI: MicroFocus Cobol
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: MicroFocus Cobol
DOCUMENT ID#: FYI.S.6
DATE: 14MAR91
PRODUCT: Access Server (NAS)
PRODUCT VERSION: 1 & 1.01
SUPERSEDES: NA
SYMPTOM: Failure to Run MicroFocus Cobol Applications
ISSUE/PROBLEM
MicroFocus Cobol apllications can run on an Access Server (NAS) but only with slight modifications to MicroFocus Cobol to take in to account the fact that Access Server (NAS) Applications run in protected mode.
SOLUTION:
For a Runtime System The default is a bound executable which checks to see if it is running in protected mode and if it is assumes that it should be OS2. As Access Server (NAS) DOS sessions are protected mode but not OS2 you must run the MicroFocus runtime system unbound.
In order to do this:
- Change the name of RUN.EXE to something else and save.
- Change the name of RUN.DLE to RUN.EXE
If using BUILD Use the /r parameter to create a real mode executable.
If you need further information Call MicroFocus technical support at 415-856-4161.
FYI: MAP Root and Access Server (NAS)
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: MAP Root and Access Server (NAS)
DOCUMENT ID#: FYI.S.5
DATE: 27FEB91
PRODUCT: ACCESS SERVER (NAS)
PRODUCT VERSION: 1 & 1.01
SUPERSEDES: NA
SYMPTOM: failure to MAP
ISSUE/PROBLEM
If your Access Server (NAS) users do not get the mapping you expect them to you are probably trying to use MAPROOT.
Access Server (NAS) does not currently (2/27/91) support MAPROOT.
SOLUTION:
Support is expected in a later version.
FYI: Access Server (NAS) on a Backbone
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: Access Server (NAS) on a Backbone
DOCUMENT ID#: FYI.S.2
DATE: 01DEC90
PRODUCT: Access Server (NAS)
PRODUCT VERSION: 1.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM:
Attaching Users to a Particular File Server
SOLUTION:
WORK AROUND #1
Modify FASTART or HASTART by changing (will be TMP or BAT files)
%1:signon /P
To
%1:signon AFILESERVERNAME/a fictitious name
That is for example
%1:signon NETWIRE/BRUTH
Then have the system Login Script read
IF LOGIN_NAME=BRUTH
EXIT"LOGIN"
END
The user will then be required to give their NetWare password and will be attached to their usual file server.
WORK AROUND #2
Modify FASTART or HASTART by changing
%1:signon /P
To
%1:signon AFILESERVERNAME/AFICTIOUSNAME
That is for example
%1:signon NETWIRE/BRUTH (for example)
Then have "BRUTH's" Login Script read
EXIT"LOGIN"
The user will then be connected to the desired file server and required to login and give their password just as though they had not come in through Access Server (NAS).
In each case the fictitious name must be actually a listed (fictitious) user on the file server.
These are temporary "inelegant" temporary work arounds.
FYI: VTAM Patches from IBM
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: VTAM Patches from IBM
DOCUMENT ID#: FYI.S.15
DATE: 01SEP90
PRODUCT: NetWare SNA Token Ring Gateway
PRODUCT VERSION: 1.2
SUPERSEDES: NA
SYMPTOM: PU does not become active, in CONCT status
ISSUE/PROBLEM
A patch may be required for VTAM 2.1.
In the known instance the Gateway was channel attached from a 3174 controller to an IBM 3090.
SOLUTION
Contact IBM for the latest patches. In the fall of 1990 they were:
UY39726 and UY40647
FYI: Token Ring Gateway attached to a 3745
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within it's means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit claims to the validity of this information.)
TITLE: Token Ring Gateway attached to a 3745
DOCUMENT ID#: FYI.S.20
DATE: 27DEC89
PRODUCT: SNA Gateway
PRODUCT VERSION: NA
SUPERSEDES: NA
SYMPTOM: PU will not come out of CONCT status
ISSUE/PROBLEM
Token Ring Gateway attached to a 3745 at NCP 5.21 PU status is CONCT (Connectable).
SOLUTION
OPTION statement in NCP must contain NEWDEFN=(YES,ECHO) as first parm.
After generation, gen output must be renamed to source input for VTAM. This is because NCP 5.21 gen replaces options in the source file needed for NTRI resources.
Reference: NCP, SSP, EP RESOURCE DEFINITION GUIDE.
