 |
» |
|
|
|
MESSAGE: None | CAUSE: RFA was
unable to obtain a free DST for its buffers. ACTION: If system is overloaded,
wait till resources free up; otherwise, see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: RFA was
unable to deallocate one of its internal buffers. ACTION: If program a has
opened too many NOWAIT RFA files,
or if it is attempting to read large blocks of data for each FREAD
(16000 bytes per FREAD), then the program has reached RFA's
resource limits. If the program does neither then see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: RFA failed
to create a connection to the remote machine. ACTION: Verify if the network
transport has not been shutdown by the system operator on the local
or remote system. If not see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: RFA was
unable to complete a connection with the remote machine. ACTION: Verify if the network
transport has not been shutdown by the system operator on the local
or remote system. If not see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: RFA encountered
a NetIPC error while sending an RFA request to the remote system. ACTION: If the user attempted
to FREAD or FWRITE more than 29980 bytes of data in one FREAD or
FWRITE call, then the user has reached the resource limits of RFA.
If user has enabled data compression for RFA transfers, this limit
is 29000 bytes. This error will also occur if the system operator
has brought down the network transport on the local or remote system.
If not see "Appendix A “Submitting an SR ”
of this manual. |
MESSAGE: None | CAUSE: An unexpected
error occurred while receiving data from the remote system. ACTION: This error will occur
if the system operator has brought down the network transport on
the local or remote system. It can also occur if the version of
NS on the remote system is older than this system and the user attempted
to use a newly supported file system intrinsic that is not supported
by RFA on the remote system. If neither is the case then see "Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: RFA could
not connect with the RFA server on the remote system. ACTION: Verify that the network
transport has been started on the remote system. Verify that the
remote system supports NS 3000/iX RFA. Also verify that
the remote system has started the RFA service. If RFA is started
then see Appendix A “Submitting an SR ” of
this manual. |
MESSAGE: None | CAUSE: RFA could
not turn on NetIPC socket data
tracing. ACTION: If the local system
is not out of disk space then see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: RFA could
not update information in the NS DSLINE
table. ACTION: RFA may have run
out of stack space. Run the program with an additional 2000 words
of stack space. If this is not the problem then see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: RFA could
not get information from the NS DSLINE
table. ACTION: RFA may have run
out of stack space. Run the program with an additional 2000 words
of stack space. If this is not the problem then see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: RFA could
not add a new process entry into the NS DSLINE
table. ACTION: RFA may have run
out of stack space or the DSLINE
table may be full. If there are more than 100 programs in the same
session using NS, the user has reached NS resource limits. Otherwise
run the program with an additional 2000 words of stack space. If
this is not the problem then see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: RFA could
not find an entry it created in the DSLINE
table. ACTION: RFA may have run
out of stack space. Run the program with an additional 2000 words
of stack space. If this is not the problem then see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: RFA was
unable to create or delete an entry in the DSSERVER's stack. ACTION: If the remote user
has opened many message files and/or their program FREADs or FWRITEs
large amounts of data per request (16000 bytes) then the user has
reached the resource limits of RFA. If not see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: The RFA
Server received a request it could not execute. ACTION: If the version of
NS on this system is older than the version of NS on the RFA user's
host system and the user attempted to execute a new file system
intrinsic or TurboIMAGE intrinsic
that is not supported by the older revision of NS, this error will
occur. This system must be updated. If not, it is possible that
this system has a duplicate IP address as another system on this
network. If this is not the case, then an RFA message has been corrupted,
see Appendix A “Submitting an SR ” of this
manual. |
MESSAGE: None | CAUSE: While the
RFA server was adopting in the remote session, it could not update
information in the AS process table. ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: RFA was
unable to allocate a buffer large enough to handle the user's
FREAD or FWRITE
request. ACTION: If the user's
program a has opened too many NOWAIT
RFA files or if it is attempting to read large blocks of data for
each FREAD (16000 bytes per FREAD)
then the program has reached RFA's resource limits. If
the program does neither then see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: The user
attempted to open a reverse RFA file using the $BACK
environment. RFA was unable to make contact with the originating
system. ACTION: This problem can
occur if the domain and/or organization of the originating node
is different than this node. If this is the case, add the remote
node name to the NS directory file on this system using the same
domain and organization as this node. If this is not the problem
then see Appendix A “Submitting an SR ” of
this manual. |
MESSAGE: None | CAUSE: RFA could
not call one of its Native Mode procedures. ACTION: The NS product has
been installed improperly. See Appendix A “Submitting an SR ” of this manual. |
|
