This appendix lists all the error messages that can appear on the emulation status line, followed by suggested corrective actions. Some error messages appear as numbers on the status line. Other error messages appear as text and are not numbered.
Messages and corrective actions are listed in the following order:
All the corrective actions are listed with a letter that identifies them, A through E, as explained below. All the numbered messages appear in numeric order. Each message explanation includes a probable cause, the IBM SNA sense data associated with the situation, and a letter that identifies the corrective action. The un-numbered text error messages appear in courier type . Explanations and suggested corrective actions appear immediately after each message, in normal text.
When a message appears at the PC during emulation, write it down or print the PC screen. Look it up in this section and follow the instructions indicated for that message.
Corrective Actions for Numbered Messages
Following are the corrective actions referred to in the numbered messages:
A — Data stream errors. Contact your applications programming personnel.
B — Configuration problem. Contact your VTAM/NCP systems programming personnel.
C — System software is inconsistent. Contact your systems operation personnel.
D — Device is in inactive or suspended state. Contact your systems operation personnel.
E — 3270/SNA service is inconsistent. If stopping and restarting the service does not correct the problem, report the symptoms to Banyan.
The error messages below appear on the status line in this format:
Prog errornum sensecode
The errornum can be any number from 1 to 130. These are listed in order below. The IBM sense code is four hexadecimal digits. Sense codes are documented in the IBM SNA Reference Summary.
1 Negative response received from HOST. Sense data is displayed. Use corrective action A.
2 Received an unsupported DFC (data flow control) request. The unsupported request code is displayed. Use corrective action B.
3 Your device has not been activated. Possibly, your device has been placed in an inactive state due to some communications error. Use corrective action D.
4 Your device has not been activated. Possibly, your device has been placed in an inactive statue due to some communications error. Use corrective action D.
5 Data Flow Control receive check. The request code on a response does not match the original response. SNA receive check sense data 4012 (hex) is displayed. This should never happen and indicates that either mainframe or VINES software is in an inconsistent state. Use corrective action C.
6 Data Flow Control receive check. Both BC and EC must be included on a normal flow response. SNA receive check sense data 400B (hex) is displayed. Use corrective action C.
7 Data Flow Control receive check. Incorrect specification of RU category. SNA receive check sense data 4011 (hex) is displayed. Use corrective action C.
8 Data Flow Control receive check. The request code on a response does not match the original response. SNA receive check sense data 4012 (hex) is displayed. This should never happen and indicates that either mainframe or VINES software is in an inconsistent state. Use corrective action C.
9 Data Flow Control receive check. Incorrect specification of RU category. SNA receive check sense data 4011 (hex) is displayed. Use corrective action C.
10 Data Flow Control receive check. The request code on a response does not match the original response. SNA receive check sense data 4012 (hex) is displayed. This should never happen and indicates that either mainframe or VINES software is in an inconsistent state. Use corrective action C.
11 Data Flow Control receive check. Incorrect specification of RU category. SNA receive check sense data 4011 (hex) is displayed. Use corrective action C.
12 Data Flow Control receive check. Incorrect use of format indicator. SNA receive check sense data 400F (hex) is displayed. Use corrective action C.
13 Data Flow Control receive check. Both BC and EC must be included on a normal flow response. SNA receive check sense data 400b (hex) is displayed. Use corrective action C.
14 Data Flow Control receive check. Incorrect use of response indicators. SNA receive check sense data 4014 (hex) is displayed. Use corrective action C.
15 Data Flow Control receive check. Incorrect use of QRI. SNA receive check sense data 4015 (hex) is displayed. Use corrective action C.
16 Data Flow Control receive check. Incorrect use of bracket indicators. SNA receive check sense data 400C (hex) is displayed. Use corrective action C.
17 Data Flow Control receive check. The change direction indicator was incorrectly specified. SNA receive check sense data 4009 (hex) is displayed. Use corrective action C.
18 Data Flow Control receive check. Alternate code selection is not supported. SNA receive check sense data 4010 (hex) is displayed. Use corrective action B.
19 Data Flow Control receive check. Enciphered data indicator was incorrectly used. SNA receive check sense data 4016 (hex) is displayed. Use corrective action B.
20 Data Flow Control receive check. Padded data indicator was incorrectly used. SNA receive check sense data 4017 (hex) is displayed. Use corrective action B.
21 Data Flow Control receive check. An unsupported DFC request was received. SNA receive check sense data 1003 (hex) is displayed. Use corrective action B.
22 Data Flow Control receive check. An unsupported SIG request was received. Only the request-to-send form is supported. SNA receive check sense data 1003 (hex) is displayed. Use corrective action B.
23 Data Flow Control receive check. Incorrect use of format indicator. The format indicator was not set on a DFC request. SNA receive check sense data 400f (hex) is displayed. Use corrective action B.
24 Data Flow Control receive check. Chaining not supported. BC and EC must be set on DFC requests. SNA receive check sense data 400b (hex) is displayed. Use corrective action B.
25 Data Flow Control receive check. Alternate code set is not supported on DFC requests. SNA receive check sense data 4010 (hex) is displayed. Use corrective action B.
26 Data Flow Control receive check. Enciphered data indicator is not supported on DFC requests. SNA receive check sense data 4016 (hex) is displayed. Use corrective action B.
27 Data Flow Control receive check. Padded data indicator indicator is not supported on DFC requests. SNA receive check sense data 4017 (hex) is displayed. Use corrective action B.
28 Data Flow Control receive check. Incorrect use of DRI1, DRI2, or ERI with BID, BIS, or RTR. SNA receive check sense data 4014 (hex) is displayed. Use corrective action B.
29 Data Flow Control receive check. Incorrect use of EB or BB with BID, BIS, or RTR request. SNA receive check sense data 400c (hex) is displayed. Use corrective action B.
30 Data Flow Control receive check. Incorrect use of CDI with BID, BIS, or RTR request. SNA receive check sense data 4009 (hex) is displayed. Use corrective action B.
31 Data Flow Control receive check. Incorrect use of DRI1, DRI2, or ERI with CANCEL, QC, or CHASE request. SNA receive check sense data 4014 (hex) is displayed. Use corrective action B.
32 Data Flow Control receive check. BB is not allowed with CANCEL, QC, or CHASE request. SNA receive check sense data 4003 (hex) is displayed. Use corrective action B.
33 Data Flow Control receive check. CDI is not allowed on CANCEL, QC, or CHASE request. SNA receive check sense data 4009 (hex) is displayed. Use corrective action B.
34 Data Flow Control receive check. An unsupported normal flow DFC request was received. SNA receive check sense data 1003 (hex) is displayed. Use corrective action B.
35 Data Flow Control receive check. Brackets not supported. SNA receive check sense data 400c (hex) is displayed. Use corrective action B.
36 Data Flow Control receive check. Received CDI with no ECI on normal flow FMD request. SNA receive check sense data 4009 (hex) is displayed. Use corrective action C.
37 Data Flow Control receive check. Begin bracket was specified incorrectly on a normal flow FMD request. SNA receive check sense data 4003 (hex) is displayed. Use corrective action C.
38 Data Flow Control receive check. End bracket was specified incorrectly on a normal flow FMD request. SNA receive check sense data 4004 (hex) is displayed. Use corrective action C.
39 Data Flow Control receive check. This implementation does not support the format indicator on normal flow FMD requests. Sense data 400f (hex) is displayed. Use corrective action B.
40 Data Flow Control receive check. This implementation does not support alternate code selection on normal flow FMD requests. Sense data 4010 (hex) is displayed. Use corrective action B.
41 Data Flow Control receive check. Brackets selected when BIND indicated brackets would not be used. Sense data 400c (hex) is displayed. Use corrective action B.
42 Data Flow Control receive check. Chaining indicators were incorrectly used when BIND indicated the multi-request chains would not be used. Sense data 400b (hex) is displayed. Use corrective action B.
43 Data Flow Control receive check. Definite response was requested when not permitted. Sense data 4007 (hex) is displayed. Use corrective action B.
44 Data Flow Control receive check. Exception response was requested when not permitted. Sense data 4006 (hex) is displayed. Use corrective action B.
45 Data Flow Control receive check. No response was requested when not permitted. Sense data 400a (hex) is displayed. Use corrective action B.
46 Data Flow Control receive check. Mode inconsistent with request. SHUTD request received when processing of a previous SHUTD request was pending. Sense data 0809 (hex) is displayed. Use corrective action C.
47 Data Flow Control receive check. Immediate request mode error. Sense data200a (hex) is displayed. Use corrective action C.
48 Data Flow Control receive check. Half-duplex flip-flop direction error. Sense data 2004 (hex) is displayed. Use corrective action C.
49 Data Flow Control receive check. Contention error. Sense data 081b (hex) is displayed. This error should be ignored. Contention errors are resolved in favor of the 3270/SNA service.
50 Data Flow Control receive check. Chaining error. Sense data 2002 (hex) is displayed. Use corrective action C.
51 Data Flow Control receive check. Bracket error. Sense data 2003 (hex) is displayed. Use corrective action C.
52 Data Flow Control receive check. Bracket state error. Sense data 080b or 0813 (hex) is displayed. This error should be ignored.
53 Data Flow Control send check. Response owed before sending request. Sense data 200d is displayed Use corrective action E.
54 Data Flow Control send check. Improper use of change direction indicator. Sense data 4009 (hex) is displayed. Use corrective action E.
55 Data Flow Control send check. Immediate request mode error. Sense data 200a (hex) is displayed. Use corrective action E.
56 Data Flow Control send check. Chaining error. Sense data 2002 (hex) is displayed. Use corrective action E.
57 Data Flow Control send check. Half-duplex flip-flop direction error. Sense data 2004 (hex) is displayed. Use corrective action E.
58 Data Flow Control send check. Bracket error. Sense data 2003 (hex) is displayed. Use corrective action E.
59 Data Flow Control send check. Mode inconsistency. Sense data 0809 (hex) is displayed. Use corrective action E.
60 Data Flow Control send check. Data traffic stopped for an unknown reason. Sense data 2006 (hex) is displayed. Use corrective E.
62 NAU checks. Request type-session mismatch. Sense data 0809 (hex) is displayed. Use corrective action B.
63 NAU checks. Received ACTLU request while PU is inactive. Sense data 8008 (hex) is displayed. Use corrective action C.
64 NAU checks. Received ACTLU request while LU is inactive. Sense data 8009 (hex) is displayed. Use corrective action C.
65 NAU checks. Received DACTPU request while PU is inactive. Sense data 8008 (hex) is displayed. Use corrective action C.
66 NAU checks. Received UNBIND request while PU is inactive. Sense data 8008 (hex) is displayed. Use corrective action C.
69 NAU checks. Received ACTPU request containing an unsupported activation type. Sense data 0835 (hex) is displayed. Use corrective action B.
70 NAU checks. Received ACTPU request containing an unsupported FM profile type. Sense data 0835 (hex) is displayed. Use corrective action B.
71 NAU checks. Received ACTPU request containing an unsupported TS profile type. Sense data 0835 (hex) is displayed. Use corrective action B.
72 NAU checks. Received ACTLU request while PU is not activated. Sense data 8008 (hex) is displayed. Use corrective action C.
73 NAU checks. Received ACTLU request for unassigned LU. Sense data 8009 (hex) is displayed. Use corrective action E.
74 NAU checks. Received incorrectly formatted ACTLU request. Sense data 0835 (hex) is displayed. Use corrective action C.
75 NAU checks. Received ACTLU request containing an unsupported FM profile type. Sense data 0835 (hex) is displayed. Use corrective action B.
76 NAU checks. Received ACTLU request containing an unsupported TS profile type. Sense data 0835 (hex) is displayed. Use corrective action B.
77 NAU checks. Received BIND request while PU is not activated. Sense data 8008 (hex) is displayed. Use corrective action C.
78 NAU checks. Received BIND request while LU is not activated. Sense data 8009 (hex) is displayed. Use corrective action C.
79 NAU checks. Received BIND request while LU is already bound. Sense data 0815 (hex) is displayed. Use corrective action C.
80 NAU checks. Received BIND request which would exceed the LU session limit. Sense data 0805 (hex) is displayed. Use corrective action C.
81 NAU checks. Received BIND with an unsupported format. Sense data 0805 (hex) is displayed. Use corrective action B.
82 NAU checks. Received BIND request containing an unsupported FM profile type. Sense data 0835 (hex) is displayed. Use corrective action B.
83 NAU checks. Received BIND request containing an unsupported TS profile type. Sense data 0835 (hex) is displayed. Use corrective action B.
84 NAU checks. Illegal session control state. Sense data 2009 (hex) is displayed. Use corrective action B.
85 NAU checks. An ACTPU request for other than a cold start was received. Sense data 1003 (hex) is displayed. Use corrective action B.
86 NAU checks. An ACTPU request containing invalid session parameters was received. Sense data 0821 (hex) is displayed. Use corrective action B.
87 NAU checks. Received BIND request while LU is already bound. Sense data 0815 (hex) is displayed. Use corrective action C.
88 NAU checks. Received BIND request which would exceed the LU session limit. Sense data 0805 (hex) is displayed. Use corrective action C.
89 NAU checks. A BIND request for an unavailable LU was received. Sense data 0845 (hex) is displayed. Use corrective action B.
90 NAU checks. A BIND request containing illegal profiles was received. Sense data 0821 (hex) is displayed. Use corrective action B.
91 NAU checks. Mode inconsistency. Sense data 0809 (hex) is displayed. Use corrective action B.
92 NAU checks. Category not supported. Sense data 1007 (hex) is displayed. Use corrective action B.
93 NAU checks. SSCP-LU data flow in wrong session status. Sense data 0857 (hex) is displayed. Use corrective action C.
94 NAU checks. An unsupported session control request was received. Sense data 1003 (hex) is displayed. Use corrective action B.
95 NAU checks. An unsupported BIND request was received. Sense data 0821 (hex) is displayed. Use corrective action B.
96 TC receive checks. A request was received; however, the PU is not active. Sense data 8008 (hex) is displayed. Use corrective action C.
97 TC receive checks. A request was received; however, the LU is not active. Sense data 8009 (hex) is displayed. Use corrective action C.
98 TC receive checks. A request was received; however, the LU is not bound. Sense data 8005 (hex) is displayed. Use corrective action C.
99 TC receive checks. A DFC or FMD request was received; however, the session was never reset with an SDT request. Sense data 2005 (hex) is displayed. Use corrective action C.
100 TC receive checks. A request containing an unsupported request category was received. Sense data 1007 (hex) is displayed. Use corrective action B.
101 TC receive checks. The immediate request mode protocol was violated by the request. Sense data 200a (hex) is displayed. Use corrective action C.
102 TC receive checks. A pacing request was received but the session was bound with pacing off. Sense data 4008 (hex) is displayed. Use corrective action C.
103 TC receive checks. A nonsequential sequence number was received. Sense data 2001 (hex) is displayed. Use corrective action C.
104 TC receive checks. An SDT request was received; however, the LU does not support the SDT request. Sense data 1003 (hex) is displayed. Use corrective action E.
105 TC receive checks. An SDT request was received which cannot be acted upon in the present state. Sense data 0809 (hex) is displayed. Use corrective action C.
106 TC receive checks. A CLEAR request was received; however, the LU does not support the CLEAR request. Sense data 1003 (hex) is displayed. Use corrective action E.
107 TC receive checks. An STSN request was received; however, the LU does not support the STSN request. Sense data 1003 (hex) is displayed. Use corrective action B.
108 TC receive checks. An STSN request was received, and the LU supports it; however, data traffic state is not reset. Sense data 2007 (hex) is displayed. Use corrective action E.
109 TC receive checks. An RQR request was received; however, the LU does not support it. Sense data 1003 (hex) is displayed. Use corrective action B.
110 TC receive checks. A CRV request was received; however, the LU does not support it. Sense data 1003 (hex) is displayed. Use corrective action B.
111 TC send checks. The immediate request mode protocol was violated. Sense data 200A (hex) is displayed unless SNA SIG request is being processed. Use corrective action E.
112 TC send checks. Attempted to send a request while data traffic was not active. Sense data 2005 (hex) is displayed. Use corrective action E.
113 NAU check. RU is too long. Sense data 1002 (hex) is displayed. Use corrective action C.
114 Path Control check. Segmentation error. Sense data 8007 (hex) is displayed. Use corrective action C.
115 Path Control check. Segmentation error. Sense data 8007 (hex) is displayed. Use corrective action C.
116 Path Control check. OIS does not contain TH and RH. Sense data 8002 (hex) is displayed. Use corrective action C.
117 Path Control check. Segmentation error. Sense data 8007 (hex) is displayed. Use corrective action C.
118 Path Control check. Segmentation error. Sense data 8007 (hex) is displayed. Use corrective action C.
119 Path Control check. Segmentation error. Sense data 8007 (hex) is displayed. Use corrective action C.
120 Path Control check. Segmentation error. Sense data 8007 (hex) is displayed. Use corrective action C.
121 Path Control check. Segmentation error. Sense data 8007 (hex) is displayed. Use corrective action C.
122 Path Control check. Invalid address combination. Sense data 800f (hex) is displayed. Use corrective action B.
123 Path Control check. Invalid address/RU category combinations. Sense data 8003 (hex) is displayed. Use corrective action B.
124 Path Control check. PU is not active. Sense data 8008 (hex) is displayed. Use corrective action C.
125 Path Control check. LU is not active. Sense data 8009 (hex) is displayed. Use corrective action C.
126 Path Control check. No session bound. Sense data 8005 (hex) is displayed. Use corrective action C.
127 Path Control check. Incomplete TH. Sense data 800b (hex) is displayed. Use corrective action C.
128 Path Control check. Unrecognized destination address. Sense data 8004 (hex) is displayed. Use corrective action C.
129 Path Control check. Invalid FID. Sense data 8006 (hex) is displayed. Use corrective action C.
130 Path control check. Invalid FID. Sense data 8004 (hex) is displayed. Use corrective action C.
Un-numbered error messages are listed below in alphabetical order.
Attach request rejected: nn
nn is a number from 01 to 09.
During the process of attaching to the Advanced 3270/SNA service, the client software sends an Attach Request packet to the VINES service. The service parses the packet for various information. If the service finds something in the packet that prevents the attach request from being completed successfully, it returns one of these errors:
Attach request rejected: 01
The logical unit requested is not currently available.
Attach request rejected: 02
The logical unit requested is not of the specified type.
Attach request rejected: 03
The revision level of the client is not compatible with the revision of the Advanced 3270/SNA service. If this error recurs, you may need to re-install Advanced 3270/SNA.
Attach request rejected: 04
The LU number requested is outside the range of LU numbers available from the service.
Attach request rejected: 05
The service's attempt to verify your access to the requested LU was unsuccessful. Try rebooting the workstation and running the software again. If the error persists, call your Banyan service representative.
Attach request rejected: 06
You are not included on the Access Rights List for the specified LU. Refer to the 3270/SNA Option Guide or see your VINES system administrator for help.
Attach request rejected: 07
Refer to the section on Physical Location Security in the 3270/SNA Option Guide.
Attach request rejected: 08
The client type specified in the Attach Request Packet was not in the recognized range. Call your Banyan service representative.
Attach request rejected: 09
The protocol type specified in the Request Packet was not in the recognized range. Call your Banyan service representative.
Attach request rejected: 0A
All of the LUs that match your requested LU type are either in use or unavailable. Wait a few minutes, then try the command again. If the problem persists, call your VINES system administrator.
Attempting to reconnect...
This message occurs when you press <CTRL-R> to reconnect to the Advanced 3270/SNA gateway.
Attention sent
This message displays when you press <ATTN>. (The default key sequence on the PC keyboard is <F8>.)
Cancel already pending
You can cancel only one SCS print pending request at a time. Try CANCEL again after the host cancels the first print request.
Check_return svc: nn ret: nn
An error occurred in Advanced 3270/SNA while data was being sent or received. Call your Banyan service representative.
Check_send svc: nn ret: nn
An error occurred in Advanced 3270/SNA while data was being sent or received. Call your Banyan service representative.
Error opening PRN (no handles)
A DOS open file call resulted in an error due to an inadequate number of file handles. Try increasing the number of FILES declared in the CONFIG.SYS file on your boot drive. Reboot the PC and try the operation again.
File access error
You specified an incorrect path or file name. Retry the command using a different file name.
File close error
The emulator cannot close a redirection file. This can occur for one of the following reasons:
The diskette is no longer in the drive. You changed the default drive or directory before closing the file. The drive on which you were working suddenly became inaccessible.
Insert the correct diskette, or change to the original drive or directory and re-try the command.
File open error - network error
An error was returned from VINES when you attempted to open your redirection file. Check to see if you have access to the drive to which you are trying to write.
File open error - path error
The DOS file specification of your redirection file is incorrect. Check the file name to make sure you specified it correctly.
File open error - too many open
The DOS default allows eight open files at one time. If you switch between DOS applications and emulation, you might exceed this number. To use more than eight files, edit the DOS CONFIG.SYS file to change the default. You can also terminate the DOS application or reduce the number of files it uses.
File transfer complete
The file transfer has successfully completed.
File transfer ERROR no: nn
An error was received during file transfer. Record the error, reboot the PC and try the file transfer again. If the error persists, call your Banyan service representative.
File transfer in progress
Your file transfer request is being processed.
File write error - disk full
The redirection file is too large to fit in the space available on the diskette. Close the file when the disk is full. Change the diskette and reopen the file.
File write error - file not found
The emulator cannot find the printer redirection file because the diskette is no longer in the drive or you changed the default drive or directory before closing the file. Insert the correct diskette or change to the original drive or directory and retry the command.
File write error - file not open
You attempted to write to a redirection file that was not successfully opened. Make sure that you have access to the drive on which your file resides.
Host unavailable <nn>
Advanced 3270/SNA attempted to disconnect from a host that is no longer available. The session should terminate normally.
Maximum socket entries allocated.
This error is returned from the VINES socket interface. Write down the error, reboot your workstation, and try the function again. If the error occurs a second time, call your Banyan service representative.
Neg. response received xxxx xxxx
The host sent an SNA negative response. Refer to your IBM documentation for additional instructions.
Network error accessing PRN nn
This error message is returned from DOS when the application tried to open the PRN device. Check to make sure that your printer is properly connected and on-line. See your DOS manual for more information.
No data flow in unowned state
You tried to enter data without establishing a session. In an unowned session, press <SYSREQ> (<ALT-F8> on the PC keyboard) to switch to a system operator session.
No host: nn <c-r>
The gateway is unavailable. nn is the number of the LU that is attempting to connect, or the name of a VINES list. Press <CTRL-R> to retry.
No host connection. Please wait.
The PC was unable to connect to the gateway because host initialization is still in progress. Until initialization co es, the emulator will accept no keyboard input. Use <CTRL-R> to reconnect the gateway.
No more socket entries available.
This error is returned from the VINES socket interface. Write down the error, reboot your workstation and try the function again. If the error occurs a second time, call the Banyan Response Center.
No printer assigned
You attempted to send a print job to an LU that is not set up as a printer.
PA already pending
You can execute only one SCS PA function at a time. One function must complete before you can execute a second. Retry the PA function after the host co es the first PA function.
PIO error: nn
An error occurred in Advanced 3270/SNA while data was being sent or received. Call your Banyan service representative.
Post socket receive: nn
This error is returned from the VINES socket interface. Write down the error, reboot your workstation and try the function again. If the error occurs a second time, call the Banyan Response Center.
Post socket send error: nn
This error is returned from the VINES socket interface. Write down the error, reboot your workstation and try the function again. If the error occurs a second time, call the Banyan Response Center.
Printer busy - command not allowed.
You selected RESET TOP OF FORM from the Printer Functions menu while the printer was busy.
Printer nn does not exist
The printer LU to which you are trying to print is not configured.
Printer nn timeout
Printer nn is offline, jammed, out of paper, or otherwise unable to print data. Fix the printer, then use the Printer Functions menu to enable printing again. (Use the <F4> key.)
Printer started
Your printer was successfully started.
PRN nn appears to be offline
This error message is returned from DOS when the application tried to open the PRN device. Check that your printer is properly connected and on-line. See your DOS manual for more information.
Revision error: REQ [xxxx] RSP [xxxx]
The Advanced 3270/SNA client software checked the revision of the Advanced 3270/SNA service running on your server, and discovered a revision mismatch. Write down the hexadecimal values in brackets (xxxx) and call your Banyan service representative.
RU error received xx
Data sent from the host cannot be interpreted by Advanced 3270/SNA.
Service revision error: n
An Attach Request was rejected due to a revision mismatch between the Advanced 3270/SNA client software and the version of the Advanced 3270/SNA service installed on your server. If n equals 1, your service is designed for a version of VINES earlier than VINES 4.00. If n equals 2, your service is designed for a version of VINES 4.0 earlier than VINES 4.00 [1] patch level 1B. Call your Banyan service representative.
SNA error received xx
SNA detected a host protocol violation.
SNA send error attempt xxxx xxxx
SNA prevented an invalid operation.
Socket interrupt error: nn
This error is returned from the VINES socket interface. Write down the error, reboot your workstation and try the function again. If the error occurs a second time, call the Banyan Response Center.
Socket receive co ion error: nn
This error is returned from the VINES socket interface. Write down the error, reboot your workstation and try the function again. If the error occurs a second time, call the Banyan Response Center.
Socket send co ion error: nn
This error is returned from the VINES socket interface. Write down the error, reboot your workstation and try the function again. If the error occurs a second time, call the Banyan Response Center.
STGETPORT error: nn
This error is returned from the VINES socket interface. Write down the error, reboot your workstation and try the function again. If the error occurs a second time, call the Banyan Response Center.
STNICE error: nn
This error is returned from the VINES socket interface. Write down the error, reboot your workstation and try the function again. If the error occurs a second time, call the Banyan Response Center.
Unknown error opening PRN nn
This error message is returned from DOS when the application tried to open the PRN device. Check to make sure that your printer is properly connected and on-line. See your DOS manual for more information.
Unknown status code received: nn
This error is returned from the VINES socket interface. Write down the error, reboot your workstation and try the function again. If the error occurs a second time, call the Banyan Response Center.
Unknown write error on PRN nn
This error message is returned from DOS when the application tried to open the PRN device. Check to make sure that your printer is properly connected and on-line. See your DOS manual for more information.
Warning - printer is not paced
Printer pacing is a host feature that prevents the host from sending data faster than the printer can print it. Consult your site manager to see if pacing is available.
Write access error on PRN nn
This error message is returned from DOS when the application tried to open the PRN device. Check to make sure that your printer is properly connected and on-line. See your DOS manual for more information.
