HP 3000 Manuals HP 3000 Manuals
Control Process Logging Location Codes (contd)
627 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While stopping an NI because a network
was being shut down, NETCP encountered an error
trying to delete a mapping table it had
previously created for the NI (PARM = 32-bit
status returned by the call to
map_create_table).
Action: This error in itself was not fatal, and
shutdown continued. However, depending on the
error, the amount of system memory used by the
table and its secondary tables be inaccessible
until the next system restart. If the problem
occurs repeatedly, see "Submitting an SR" in
appendix A of this manual.
628 CLAS0002 Message: Bad status
Cause: While attempting to stop one of the
devices on an existing NI, NETCP disconnected
the device at the MAP level, then encountered an
error trying to send a device stop message to
the NI (PARM = 32-bit status returned by the
call to send_msg).
Action: This error in itself was not fatal, and
shutdown may continue. However, some versions
of Transport may hang if this problem occurs,
requiring a system restart to recover. On a non
critical terminal, attempt a :NETCONTROL STATUS
command; if results are reported, then try
restarting the network. If the network restarts
but the problem returns, see "Submitting an SR"
in appendix A of this manual.
629 CLAS0002 Message: PACKET DISCARD; Late reply
Cause: During processing of a Path Verify
operation on behalf of some other Transport
module because of a possible problem or change
in state of a certain network, NETCP sent Path
Verify request messages to all the general
protocols, but failed to receive a reply from
one of them within a 15-second timeout period
(PARM = 32-bit port number of the general
protocol module which failed to reply). One of
these errors will appear for each module that
fails to reply.
Action: This error in itself was not fatal, and
NETCP processing continued. This can mean
either that a temporary Path Verify storm is
occurring because a heavily used link has
failed, or it can mean there is a problem with
the general protocol module. In addition, if
the reply ever does arrive, NETCP will probably
discard it, but may instead get confused if it
arrives while awaiting some other reply. If the
problem persists, first look for previous errors
678 or 679. The PARM for these would contain
the interface code from the reply, and should
tell HP what module was sending to CP. If this
does not help, you can still determine which
module by restarting the network and taking note
of all port numbers printed on the console when
Transport starts up, and the modules which
printed those ports. Then when the next error
629 occurs, match those port numbers with the
PARM value printed for the error. Afterward see
"Submitting an SR" in appendix A of this manual,
to report a problem against the general protocol
module which is failing to reply.
630 CLAS0002 Message: Bad status
Cause: While processing a Path Verify operation
because NETCP detected a possible problem or
change in state of a certain network, or because
of a Path Verify message received from IPU in
response to a redirect packet IPU received from
a GATEWAY, NETCP encountered an error trying to
send a Path Verify message to one of the general
protocols (PARM = 32-bit status returned by the
call to send_msg).
Action: This error was not fatal; messages were
sent to all the other general protocols, and
NETCP will not expect a reply for the send that
failed. However, the affected protocol module
will not be aware there may be a problem with
the path, and may continue to try to use it. If
NETCP tracing was active, the tracefile will
show the message which could not be sent, and
the interface code in that message will indicate
which module was not accessible. If the problem
happens frequently, see "Submitting an SR" in
appendix A of this manual.
631 CLAS0002 Message: Bad status
Cause: While processing a Path Verify operation
because NETCP detected a possible problem or
change in state of a certain network, or because
of a Path Verify message received from IPU in
response to a redirect packet IPU received from
a GATEWAY, NETCP encountered an error trying to
send a path verify message to the ICMP Server
module of Transport (PARM = 32-bit status
returned by the call to send_msg).
Action: This error was not fatal; messages were
sent to all the general protocols, and NETCP
will not expect a reply to the send that failed.
However, the ICMP Server module will not be
aware there may be a problem with the path, and
may continue to try to use it. In addition,
PING commands from NETTOOL may report errors
against the affected network. If the problem
persists, see "Submitting an SR" in appendix A
of this manual.
632 CLAS0002 Message: Bad status
Cause: While processing a :NETCONTROL STOP
command or a system shutdown, NETCP encountered
an error trying to send a DCN stop message to
the IPU module of Transport (PARM = 32-bit
status returned by the call to send_msg). A DCN
stop message is required for a Directly
Connected Network such as X25.
Action: This error in itself was not fatal, and
shutdown may continue. However, some versions
of Transport may hang if this problem occurs or
if the IPU module initially failed to start (see
error 654), requiring a system restart to
recover. On a non critical terminal, attempt a
:NETCONTROL STATUS command; if results are
reported, then try restarting the network. If
the network restarts but the problem returns,
see "Submitting an SR" in appendix A of this
manual.
633 CLAS0002 Message: Bad status
Cause: While attempting to send a device stop
message to notify the DIAL module that an
existing ROUTER network was being shut down,
because of a :NETCONTROL DELLINK command or a
previous asynchronous link error, NETCP
encountered an error on the send (PARM = 32-bit
status returned by the call to send_msg).
Action: The error in itself was not fatal, and
shutdown of this network probably continued,
ending with deletion of this instance of the
DIAL module. However, DIAL was not notified the
device has stopped, which may have caused more
errors if it happened to run again before it was
deleted. In addition, some versions of
Transport may hang if this problem occurs,
requiring a system restart to recover. On a non
critical terminal, attempt a :NETCONTROL STATUS
command; if results are reported, then try
restarting the network. If the network restarts
but the problem returns, see "Submitting an SR"
in appendix A of this manual.
634 CLAS0002 Message: Bad status
Cause: While processing an asynchronous event
message from the DCLDM indicating that its LAPB
PSI link either experienced a problem related to
autodial, or else that an autodial succeeded,
NETCP encountered an error trying to send a
reply message back to DIAL telling the type of
event that occurred (PARM = 32-bit status
returned by the call to send_msg).
Action: DIAL did not receive the reply message,
and will be unaware of the results of the
autodial operation. It may take up to 30
minutes for DIAL to time out and reset itself,
and during this delay, new autodial connections
cannot be established, and sessions which
attempt it may hang. To clear this condition,
first try a :NETCONTROL DELLINK=linkname;
NET=niname command against the affected link,
followed by a :NETCONTROL ADDLINK=linkname;
NET=niname. If this does not help, a system
restart will probably be required to clear the
hang. If the problem occurs again, take a dump
when the error is reported and before any
attempts to recover, and see "Submitting an SR"
in appendix A of this manual.
635 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: NETCP received an asynchronous exception
event message from a link driver, but no device
having the SDI link ID in that message was found
in NETCP's device tables (PARM = 32-bit SDI
device ID from the message).
Action: Either the driver or NETCP are
confused. Though NETCP may continue working,
the affected network will most likely hang,
possibly requiring a system restart to recover.
See "Submitting an SR" in appendix A of this
manual.
636 CLAS0002 Message: Bad status
Cause: While attempting to send a debug message
to one of the Transport protocol modules in
response to a :NETCONTROL DIAG command, NETCP
encountered an error on the send (PARM = 32-bit
status returned by the call to send_msg).
Action: This error was not fatal, and NETCP
continued running. However, the desired module
did not receive its debug message, and will not
respond as expected. If the problem persists,
see "Submitting an SR" in appendix A of this
manual.
637 CLAS0002 Message: Bad status
Cause: While processing a :NETCONTROL DELLINK
command, and trying to send a DCN stop message
to the IPU module of Transport because at least
one network link was active, NETCP encountered
an error on the send (PARM = 32-bit status
returned by the call to send_msg). A DCN stop
message is required for a Directly Connected
Network such as X25.
Action: This error in itself was not fatal, and
the operation may continue. However, some
versions of Transport may hang if this problem
occurs or if the IPU module initially failed to
start (see error 654), requiring a system
restart to recover. On a non critical terminal,
attempt a :NETCONTROL STATUS command; if results
are reported, then try restarting the network.
If the network restarts but the problem returns,
see "Submitting an SR" in appendix A of this
manual.
638 CLAS0002 Message: Bad status
Cause: While attempting to start all the
general protocols because a :NETCONTROL START
command was starting a new instance of
Transport, NETCP successfully started some
modules, then encountered an error trying to
initialize the NETIPC Socket Timers module (PARM
= 32-bit status returned by the call to
sk_ti_start). May be preceded by another error
from NETIPC, logging the reason for the original
failure.
Action: Newer versions of Transport treat this
as a fatal error, and Transport startup will
fail. For older versions of Transport this
error was not fatal, and startup will continue,
but NETIPC and Sockets will not work correctly.
It is possible Socket Timers encountered an
unreported error during its last shutdown, and
exited early without finishing. Try stopping
and restarting transport. If the error still
happens, see "Submitting an SR" in appendix A of
this manual.
639 CLAS0002 Message: INTERNAL ERROR; Bad/unknown port
message
Cause: While waiting for a reply message, NETCP
received a message that was indeed a reply, but
the function code in the message was not the
expected value (PARM.(0:16) = the function code
that was expected and PARM.(16:16) = interface
code of received message).
Action: It is not possible to tell from the
console logging what function code NETCP
received, however if disc logging was enabled,
the entire received message was logged, which
may aid debugging. The flow of normal NETCP
operations has been interrupted, and a network
hang may be imminent, especially if new
:NETCONTROL commands are issued. It may be
necessary to restart the system to clear this
problem. See "Submitting an SR" in appendix A
of this manual.
640 CLAS0002 Message: INTERNAL ERROR; Data dictionary error
Cause: While attempting to send a reply message
back to NETUI to complete the blocked
:NETCONTROL START command that initially created
NETCP, no entry named "NETUI" was found in the
CM Port Dictionary to identify which session
port number issued the command (PARM = 16-bit
result code returned by the call to dict_find).
Usually this means the user session which issued
the command has somehow been aborted. The CM
Port Dictionary is an operating system lookup
service used by, but not part of, Transport.
Action: If a system shutdown was being done,
ignore this message. The network startup or
shutdown should run to completion, and other
network operations should continue to work
normally. Otherwise, if it still exists, the
user session which issued the command (typically
the system console) may be hung. Since it also
owns resources, it cannot be aborted, and a
system restart will be needed to recover. You
may attempt a network stop on another terminal,
then restart the system and restart the network.
In some versions of Transport, if this error
occurs NETCP will accidentally send the reply to
a random port number, and the effects of this
are indeterminate. If the same problem happens
again, see "Submitting an SR" in appendix A of
this manual.
641 CLAS0002 Message: INTERNAL ERROR; Module Deconfig Failed
Cause: While shutting down Transport due to a
system shutdown or a :NETCONTROL STOP command,
NETCP detected an error or warning while
attempting to stop the Net Timers module (PARM =
32-bit status returned by the call to
nettmr_module_deconfig). Always preceded by
other errors from Net Timers, indicating the
cause of the original failure.
Action: This error in itself was not fatal, and
shutdown continued. However, some system
resources may be lost until after the next
system restart. One possible cause would be if
a tool has already been used to stop Net Timers,
in which case NETCP cannot stop it; in this case
ignore the error. Inspect the previous error,
and if necessary, or if this problem occurs
repeatedly, see "Submitting an SR" in appendix A
of this manual.
642 CLAS0002 Message: INTERNAL ERROR; Module Deconfig Failed
Cause: While stopping an NI due to a system
shutdown or a :NETCONTROL STOP command, NETCP
detected an error trying to delete the NI (PARM
= 32-bit escape code returned by the call to
ni_module_deconfig). Always preceded by another
error from another entity (having a different
Entity number, such as 151-160), indicating the
cause of the original failure.
Action: This error in itself was not fatal, and
shutdown continued. However, some system
resources may be lost until after the next
system restart. Inspect the previous error and
if necessary, see "Submitting an SR" in appendix
A of this manual.
643 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While stopping an NI because a network
was being shut down, NETCP tried to free a NIB
(Network Interface Block) it had previously
allocated for the NI, but was unable to locate
that NIB in other NETCP tables (PARM = 32-bit
address of the missing NIB).
Action: This error in itself was not fatal, and
shutdown continued. However, NETCP may be
confused. If the problem occurs repeatedly, see
"Submitting an SR" in appendix A of this manual.
644 CLAS0002 Message: INTERNAL ERROR; Configuration file
error
Cause: While initializing an NI for a network
that was being started, NETCP was unable to read
the global information record from the
NETXPORT.NI.name path in the NMCONFIG file (PARM
= 32-bit status returned by the call to
nmconfgetdata).
Action: The NI did not start. Stop the
network, run NMMGR, and check the NI
configuration for the NI which did not start.
Validate the file. Then restart the network.
If the problem persists, the NMCONFIG file may
be corrupt, or there may be a bug in the NMS
subsystem, NMMGR, or NETCP; see "Submitting an
SR" in appendix A of this manual.
645 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While stopping an NI because of a system
shutdown or a :NETCONTROL STOP command, NETCP
was unable to delete the port message pool it
previously created for that NI and its attached
protocols (PARM = 32-bit status returned by the
call to purge_pool).
Action: This error in itself was not fatal, and
shutdown continued. However, some amount of
system memory that had been used by the message
pool may be inaccessible until after the next
system restart. If this problem happens
repeatedly, there may be an operating system
problem or a bug in NETCP; see "Submitting an
SR" in appendix A of this manual.
646 CLAS0003 Message: INTERNAL ERROR; NM Entry
Cause: While initializing a new NI for a
network that was being started, NETCP
successfully created a port message pool for use
by that NI and its attached protocols, but was
unable to put the pool ID into a new entity
named "IP-NI" in the NS Registry (PARM = 32-bit
status returned by the call to reg_add_entity).
Action: This error was not fatal, and startup
continued; use of the Registry here is not
critical. However, creation of the NS Registry
by NETCP may have failed (see error 285), or the
Registry may be full. If the message occurs
every time, see "Submitting an SR" in appendix A
of this manual.
647 CLAS0002 Message: INTERNAL ERROR; Module Deconfig Failed
Cause: While shutting down an NI due to a
system shutdown or a :NETCONTROL STOP command,
NETCP encountered an error while trying to stop
one of the NI specific protocols for that
network (PARM = 32-bit escape code returned by
the call to the module deconfigurator that
failed). Always preceded by another error from
another entity (having a different Entity
number, such as 151-160), indicating the cause
of the original failure.
Action: This error in itself was not fatal, and
shutdown continued. However, some system
resources may be lost until the next system
restart. Inspect the previous error, and if
necessary see "Submitting an SR" in appendix A
of this manual.
648 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While reading the home node's path
report during initial NETCP startup, or while
starting some network specific protocols for a
LAN, GATEHALF or ROUTER network because a
:NETCONTROL command was issued, NETCP
successfully read local node name data from the
NMCONFIG file, then encountered an error trying
to write that data into a buffer it obtained a
short time earlier (PARM = 32-bit status
returned by the call to bmgr_write_buffer).
Action: NETCP was unable to write all the
required data, and attempted to recover and free
the buffer. The network operation that was
being performed will not work correctly.
Because the buffer given to NETCP by the buffer
manager should have been large enough to contain
all data that was to be written, there may be a
problem in either NETCP, the buffer manager, the
NMS subsystem, or NMMGR, or the NMCONFIG file
may be corrupt. Stop the network and retry the
operation. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
649 CLAS0002 Message: Bad status
Cause: After successfully building a buffer
containing needed configuration data for an X25
network that was being started, NETCP
encountered an error trying to send the buffer
to the X25 protocol module (PARM = 32-bit status
returned by the call to send_msg).
Action: X25 did not receive its configuration
data, though the rest of network startup
continued. The X25 network will not operate
correctly in this condition. In addition, the
buffer may have been lost, which may result in
error 613 when the network is stopped. Try
stopping and restarting the network. If the
problem persists, see "Submitting an SR" in
appendix A of this manual.
650 CLAS0002 Message: INTERNAL ERROR; Module Deconfig Failed
Cause: During the final phases of shutdown
because of a :NETCONTROL STOP command or a
system shutdown, NETCP encountered and error
while attempting to stop the ICMP Server module
it previously started (PARM = 32-bit status
returned by the call to
icmp_server_module_deconfig).
Action: This error in itself was not fatal, and
shutdown continued. However, any system
resources owned by the ICMP Server may be lost
until after the next system restart. If this
problem occurs repeatedly, see "Submitting an
SR" in appendix A of this manual.
651 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While attempting to start all the
general protocols because a :NETCONTROL command
was starting a new instance of Transport, NETCP
encountered an error trying to start the TCP
protocol module (PARM = 32-bit status returned
by the call to tcp_module_config). Always
preceded by another error from another entity
(having a different Entity number, such as
151-160), logging the reason for the original
failure.
Action: None of the general protocols were
started, so Transport will not work. Older
versions of Transport will improperly continue
the startup after this error, and may also hang
when stopped. Record the previous error and
this error. Stop the network. If there is no
hang, then try restarting the network. If the
problem persists, see "Submitting an SR" in
appendix A of this manual.
652 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While attempting to start all the
general protocols because a :NETCONTROL command
was starting a new instance of Transport, NETCP
encountered an error trying to start the UDP
protocol module (PARM = 32-bit status returned
by the call to tcp_module_config). Always
preceded by another error from another entity
(having a different Entity number, such as
151-160), logging the reason for the original
failure.
Action: Some of the general protocols were
started, but Transport will not work. Older
versions of Transport will improperly continue
the startup after this error, and may also hang
when stopped. Record the previous error and
this error. Stop the network. If there is no
hang, then try restarting the network. If this
problem persists, see "Submitting an SR" in
appendix A of this manual.
653 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While attempting to start all the
general protocols because a :NETCONTROL command
was starting a new instance of Transport, NETCP
encountered an error trying to start the PXP
protocol module (PARM = 32-bit status returned
by the call to tcp_module_config). Always
preceded by another error from a different
entity (having a different Entity number, such
as 151-160), the configurator, logging the
reason for the original failure.
Action: This error in itself was not fatal, and
general protocol startup continued. However,
dynamic name resolution will fail. To clear the
problem, stop then restart the network. If this
problem persists, record the previous error and
this error, then see "Submitting an SR" in
appendix A of this manual.
654 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While attempting to start all the
general protocols because a :NETCONTROL command
was starting a new instance of Transport, NETCP
encountered an error trying to start the IPU (IP
Update) module (PARM = 32-bit status returned by
the call to tcp_module_config). Always preceded
by another error from another entity (having a
different Entity number, such as 151-160),
logging the reason for the original failure.
Action: The general protocols were started, but
Transport will not work. Older versions of
Transport will improperly continue the startup
after this error, however path resolution will
fail, and Transport may also hang when stopped.
Record the previous error and this error. Stop
the network. If there is no hang, then try
restarting the network. If the error still
occurs, a common cause is that NMMGR "Unguided
Config" mode was, at some time in the past, used
to create the first NS configuration ever put
into the NMCONFIG file, and that a bug in the
Validation function of an earlier version of
Transport then corrupted a hidden record in that
file, which specifies IPU startup information.
If you suspect "Unguided Config" mode was used,
you can try to repair the hidden record. First
make a copy of the old NMCONFIG file. Then one
way to fix it is to purge and recreate the
entire file using "Guided Config" mode. If your
file is complicated, you may first want to try
another way, which is to create a new dummy file
named, say, NMCONFGT, and using "Guided Config"
mode, configure any network NI (for instance, a
dummy LAN network). Then reopen the original
NMCONFIG file and use the "Copy Subtree" utility
function to copy the NETXPORT.GPROT.IPU path,
out of the dummy NMCONFGT file and into
NMCONFIG, overwriting the existing subtree.
Then try restarting the network. If the error
goes away, you can purge NMCONFGT. But if the
same error still happens, there may be more
corruption in the file than just that one
record; try recreating the entire file, but
using "Guided Config" mode wherever possible.
If, after recreating or attempting to repair the
file, the problem still persists, there is most
likely a bug in Transport; see "Submitting an
SR" in appendix A of this manual.
655 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While attempting to start all the
general protocols because a :NETCONTROL command
was starting a new instance of Transport, NETCP
successfully started some modules, then
encountered an error trying to start the ICMP
(PING) Server module (PARM = 32-bit escape code
returned by the call to pxp_module_config).
Always preceded by another error from another
entity (having a different Entity number, such
as 151-160), logging the reason for the original
failure.
Action: This error in itself was not fatal, and
general protocol startup continued. However,
the PING service will not be available, and
pings from other nodes will go unanswered. To
clear the problem, stop then restart the
network. If this problem persists, record the
previous error and this error, then see
"Submitting an SR" in appendix A of this manual.
656 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While attempting to start all the
general protocols because a :NETCONTROL command
was starting a new instance of Transport, NETCP
successfully started some modules, then
encountered an error trying to start the Net
Timers module (PARM = 32-bit status returned by
the call to nettmr_module_config). Always
preceded by another error from Net Timers,
logging the reason for the original failure.
Action: TCP and ARP will not work without
timers. Some versions of Transport will
erroneously continue the startup after this
error. Record the previous error and this
error. Stop the network. Then try restarting
the network. If the problem still occurs, then
depending on the error, it is possible too much
frozen memory is being used by the system, but
this can change with time. Use GLANCEXL or a
similar utility to check memory usage by the
system. If memory is not the cause and the
problem persists even if retried after a
suitable waiting period, see "Submitting an SR"
in appendix A of this manual.
657 CLAS0002 Message: Bad status
Cause: While attempting to start all the
general protocols because a :NETCONTROL command
was starting a new instance of Transport, NETCP
successfully started some modules, then
encountered an error trying to create the Socket
Registry (PARM = 16-bit result code returned by
the call to sock_registry_create). May be
preceded by another error from NETIPC, logging
the reason for the original failure.
Action: Newer versions of Transport treat this
as a fatal error, and Transport startup will
fail. For older versions of Transport this
error was not fatal, and startup will continue,
but NETIPC and Sockets will not work correctly.
It is possible the Socket Registry encountered
an unreported error during its last shutdown.
Try stopping and restarting transport. If the
error still happens, see "Submitting an SR" in
appendix A of this manual.
658 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While attempting to start all network
specific protocols, required for a given
network, such as IP, because a :NETCONTROL
command was issued, NETCP encountered an error,
either from a protocol's module configurator, or
while trying to rendezvous a protocol to the
link driver. (PARM = 32-bit status returned by
the call to a module configurator, or from
cp_rendezvous_protocol). May be preceded by
another error from another module, logging the
reason for the original failure.
Action: The general protocols were started, but
the specified network did not start, and NETCP
attempted to stop the partially started network
and any network specific protocols which did
start. Retry the operation. If the problem
still occurs, stop and restart Transport. If
the problem still persists, see "Submitting an
SR" in appendix A of this manual.
659 CLAS0002 Message: INTERNAL ERROR; Module Deconfig Failed
Cause: After an error occurred while NETCP was
attempting to start network specific protocols
for a given network, NETCP attempted to clean up
by stopping any of those protocols which did
start, but then encountered another error when
calling a protocol module deconfigurator (PARM =
32-bit status returned by the call to a module
deconfigurator, or from cp_rendezvous_protocol).
Should always be preceded by other errors,
logging the reasons for the original failures.
Action: This secondary error is not the main
concern, though it may indicate additional
problems. The general protocols were started,
but the specified network failed to start
because of the first error. Retry the
operation. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
660 CLAS0002 Message: INTERNAL ERROR; Data dictionary error
Cause: While stopping an X25 network because of
a system shutdown, or a :NETCONTROL STOP command
for one or all networks, NETCP first stopped all
devices before stopping any protocols, then
encountered an error trying to delete a CM Port
Dictionary entry it had previously added to keep
track of one of the X25 device ports (PARM =
16-bit result code returned by the call to
dict_delete). The CM Port Dictionary is an
operating system lookup service used by, but not
part of, Transport. There should be one entry
per X25 device, named "X25.linkid", where
"linkid" consists of 4 unprintable bytes
defining the binary SDI link ID for that link,
dynamically assigned by the Link Support
Services subsystem.
Action: This error in itself was not fatal, and
network shutdown continued. No resources were
lost. If the problem happens every time, see
"Submitting an SR" in appendix A of this manual.