HP 3000 Manuals HP 3000 Manuals
RFA Logging Location Codes
1 CLAS0003 Cause: RFA was unable to obtain a free DST for
its buffers.
Action: If system is overloaded, wait till
resources free up; otherwise, see "Submitting an
SR" in appendix A of this manual.
2 CLAS0003 Cause: RFA was unable to obtain enough memory
to create an internal buffer entry.
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 "Submitting an SR" in appendix A of
this manual.
3 CLAS0003 Cause: RFA was unable to deallocate one of its
internal buffers.
Action: See "Submitting an SR" in appendix A of
this manual.
4 CLAS0003 Cause: RFA encountered an unexpected error from
one of its buffer management routines.
Action: See "Submitting an SR" in appendix A of
this manual.
5 CLAS0003 Cause: RFA could not delete a DST it allocated.
Action: See "Submitting an SR" in appendix A of
this manual.
7 CLAS0003 Cause: RFA could not create a socket connection
for NOWAIT IO.
Action: NOWAIT IO is not currently supported on
XL. See "Submitting an SR" in appendix A of this
manual.
8 CLAS0003 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 "Submitting
an SR" in appendix A of this manual.
9 CLAS0003 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 "Submitting
an SR" in appendix A of this manual.
10 CLAS0003 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 "Submitting an SR" in appendix A of this
manual.
11 CLAS0003 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
"Submitting an SR" in appendix A of this manual.
12 CLAS0003 Cause: RFA was unable to completely receive all
the data from a NOWAIT FWRITE.
Action: NOWAIT IO is not currently supported on
XL. See "Submitting an SR" in appendix A of this
manual.
13 CLAS0003 Cause: While attempting to adjust a NetIPC
socket, RFA encountered an unexpected error.
Action: See "Submitting an SR" in appendix A of
this manual.
14 CLAS0003 Cause: RFA could not shutdown a NetIPC socket
it created.
Action: See "Submitting an SR" in appendix A of
this manual.
15 CLAS0003 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 NS3000/XL RFA. Also
verify that the remote system has started the
RFA service. If RFA is started then see
"Submitting an SR" in appendix A of this manual.
16 CLAS0003 Cause: RFA could not turn on NetIPC socket data
tracing.
Action: If the local system is not out of disc
space then see "Submitting an SR" in appendix A
of this manual.
17 CLAS0003 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 "Submitting an SR" in appendix A of this
manual.
18 CLAS0003 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 "Submitting an SR" in appendix A of this
manual.
19 CLAS0003 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 "Submitting an SR" in appendix
A of this manual.
20 CLAS0003 Cause: NS has lost track of how many programs
are using the DSLINE table.
Action: See "Submitting an SR" in appendix A of
this manual.
21 CLAS0003 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 "Submitting an SR" in appendix A of this
manual.
22 CLAS0003 Cause: Insufficient memory in the port DST to
create a new port for NOWAIT IO.
Action: NOWAIT IO is not currently supported on
XL. See "Submitting an SR" in appendix A of this
manual.
23 CLAS0003 Cause: Unexpected error while creating an
IOWAIT port for NOWAIT IO. NOWAIT IO is not
currently supported on XL. See "Submitting an
SR" in appendix A of this manual.
Action: NOWAIT IO is not currently supported on
XL. See "Submitting an SR" in appendix A of this
manual.
24 CLAS0003 Cause: Unexpected error while creating an
IOWAIT port for NOWAIT IO.
Action: NOWAIT IO is not currently supported on
XL. See "Submitting an SR" in appendix A of this
manual.
25 CLAS0003 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 "Submitting
an SR" in appendix A of this manual.
27 CLAS0003 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 "Submitting an SR" in appendix A
of this manual.
28 CLAS0003 Cause: RFA was unable to setup its data area or
NetIPC connection for NOWAIT IO.
Action: NOWAIT IO is not currently supported on
XL. See "Submitting an SR" in appendix A of this
manual.
29 CLAS0003 Cause: RFA was unable to setup parameters for
the TCP connection.
Action: See "Submitting an SR" in appendix A of
this manual.
30 CLAS0003 Cause: While the RFA server was adopting in the
remote session, it could not update information
in the AS process table.
Action: See "Submitting an SR" in appendix A of
this manual.
31 CLAS0003 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 "Submitting an SR" in appendix
A of this manual.
32 CLAS0003 Cause: The RFA Server's state tables indicate
it is in an expected state.
Action: See "Submitting an SR" in appendix A of
this manual.
33 CLAS0003 Cause: An unexpected error was returned from
DBCLOSE.
Action: See "Submitting an SR" in appendix A of
this manual.
35 CLAS0003 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 "Submitting an SR" in appendix
A of this manual.
36 CLAS0003 Cause: RFA was unable to obtain an NM memory
object for the RFA data compression buffer.
Action: See "Submitting an SR" in appendix A of
this manual.
37 CLAS0003 Cause: RFA failed to delete an NM memory object
it created.
Action: See "Submitting an SR" in appendix A of
this manual.
38 CLAS0003 Cause: RFA could not call one of its Native
Mode procedures.
Action: The NS product has been installed
improperly. See "Submitting an SR" in appendix
A of this manual.
39 CLAS0003 Cause: One of many possible errors encountered
in Native Mode RFA.
Action: See "Submitting an SR" in appendix A of
this manual.