HP 3000 Manuals HP 3000 Manuals
Chapter 8 Remote File Access Error Messages
Remote File Access errors are returned only through the FCHECK intrinsic.
The FCHECK intrinsic is called when:
* a file system intrinsic (such as FOPEN) encounters an error
* during remote file access
The following error codes refer to Network Service Remote File
Access over Local Area Network (NS-Compatible) links.
49 MESSAGE HIERARCHICAL OR BYTE STREAM FILES NOT ALLOWED
THROUGH RFA. UNIMPLEMENTED FUNCTION. (Actual
Message Displayed)
CAUSE RFA was requested to FOPEN a byte stream or
hierarchical file.
ACTION Redirect the FOPEN to a non byte stream or
hierarchical file.
201 MESSAGE ERROR IN ACCESSING DELINE/ENVIRONMENT TABLE.
REMOTE DID NOT RESPOND WITH THE CORRECT REMOTE
ID. (Actual message displayed)
CAUSE Internal inconsistency in table or in RFA
services data structures.
ACTION Release the environment and set it up again.
204 MESSAGE UNABLE TO CREATE/EXPAND EXTRA DATA SEGMENT
BUFFERS FOR RFA. UNABLE TO ALLOCATE AN EXTRA
DATA SEGMENT FOR DS/3000. (Actual message
displayed)
CAUSE System does not have enough virtual memory or
maximum data segment table size is too small for
this RFA application.
ACTION See your system manager.
205 MESSAGE UNABLE TO ALLOCATE/MANAGE BUFFERS FOR RFA.
UNABLE TO EXPAND THE DS/3000 EXTRA DATA SEGMENT.
(Actual message displayed)
CAUSE RFA has run out of memory space to hold the
user's FREAD or FWRITE request.
ACTION The maximum data allowed per FREAD or FWRITE
with RFA is 29980 bytes per request. If data
compression is enabled, this limit is 29000
bytes. If reducing the size of the request does
not help, then see "Submitting an SR" in
appendix A of this manual.
214 MESSAGE ILLEGAL USE OF NODE NAME. DS LINE WAS NOT OPENED
WITH A USER :DSLINE COMMAND. (Actual message
displayed)
CAUSE The node does not exist or the specified node
name is invalid.
ACTION Correct the node name.
217 MESSAGE NOT ENOUGH STACK SPACE FOR RFA. INSUFFICIENT
AMOUNT OF USER STACK AVAILABLE. (Actual message
displayed)
CAUSE The MPE PREP command allocated the default
;MAXDATA or STACK values to the program, which
are too small.
ACTION Run the program again with 2000 additional words
allocated in the ;STACK=stacksize parameter of
PREP.
224 MESSAGE FILE EQUATIONS FOR REMOTE FILE CONSTITUTE AN
INFINITE LOOP. FILE EQUATIONS FOR A REMOTE FILE
CONSTITUTE A LOOP. (Actual message displayed)
CAUSE File equations on the remote machine loop back
to the local side causing reverse RFA.
ACTION Correct the file equations.
227 MESSAGE RFA/RDBA COULD NOT FIND OR CREATE A REMOTE
SESSION. RFA/RDBA COULD NOT FIND OR CREATE A
REMOTE SESSION. (Actual message displayed)
CAUSE This error could occur for one of the following
reasons:
1. Autologon is not enabled.
2. Autologon is enabled and the logon string
specified in the DSLINE command is
incorrect. Remember that if a remote
session is already established, logon
strings are ignored.
ACTION Depending on the cause:
1. Enable autologon (refer to Using
NS3000/iX Network Services), or establish
a VT session using the REMOTE command.
2. Establish a remote session and try again,
or use a correct logon string and try
again.
239 MESSAGE Network Service TRACING MALFUNCTION.
COMMUNICATIONS INTERFACE ERROR. TRACE
MALFUNCTION. (Actual message displayed)
CAUSE Tracing malfunction.
ACTION See "Submitting an SR" in appendix A of this
manual.
240 MESSAGE LOCAL COMMUNICATION LINE NOT OPENED BY OPERATOR.
LOCAL COMMUNICATION LINE WAS NOT OPENED BY
OPERATOR. (Actual message displayed)
CAUSE The RFA/RDBA service has not been started.
ACTION Use the NETCONTROL START command to open the
line.
242 MESSAGE INTERNAL ERROR. INTERNAL DS SOFTWARE ERROR
ENCOUNTERED. (Actual message displayed)
CAUSE This is an internal error.
ACTION See "Submitting an SR" in appendix A of this
manual.
246 MESSAGE REMOTE NODE DISCONNECTED CONNECTION.
COMMUNICATIONS INTERFACE ERROR. REMOTE
DISCONNECTED. (Actual message displayed)
CAUSE Remote node is no longer running on the network.
ACTION Contact the system operator of the remote node.
249 MESSAGE REMOTE SESSION ENVIRONMENT COULD NOT ADOPT RFA
SERVER. COMMUNICATIONS INTERFACE ERROR. REMOTE
REJECTED CONNECTION. (Actual message displayed)
CAUSE RFA was unable to initiate the RFA server in the
remote session.
ACTION If the remote session was not aborted by the
system operator, then see "Submitting an SR" in
appendix A of this manual.
255 MESSAGE TRANSPORT ERROR ON CONNECTION COMMUNICATIONS
INTERFACE ERROR. UNANTICIPATED CONDITION.
(Actual message displayed)
CAUSE RFA lost connection with the RFA server on the
remote system.
ACTION If you attempted to use a newly supported RFA
intrinsic, and the version of RFA on the remote
system is older than the version on this system,
then the remote system must be updated with
compatible versions of the Network Services.
Otherwise, see "Submitting an SR" in appendix A
of this manual.