Chapter 83 Remote Server Call Messages

The messages in this chapter are generated by the Remote Server Call (RSC) subsystem. The subsystem ID displayed by these messages includes RSC as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

0001

Backup started in CPU cpu_number.

cpu_number

indicates the number of the processor in which backup was started.

Cause The backup process was initiated in the specified processor.

Effect None.

Recovery This message is informational only. No corrective action is necessary.

0002

Takeover by backup in CPU cpu_number.

cpu_number

indicates the number of the processor in which backup was stopped.

Cause A takeover occurred, and the old backup process assumed the role of the primary process.

Effect Recovery is performed. The backup process now assumes the role of the primary process and attempts to restart a backup in the processor that held the old primary process.

Recovery This message is informational only. No corrective action is necessary.

0003

Failure starting backup in CPU cpu_number - error TDP_error-Guardian_error from NEWPROCESS.

`cpu_number`	indicates the number of the processor in which backup initiation failed.
`TDP_error`	indicates the RSC TDP error number.
`Guardian_error`	indicates the Guardian error number that occurred on the NEWPROCESS call.

Cause The attempt to initiate the backup process terminated with the specified error.

Effect The attempt to start the backup is abandoned.

Recovery Examine the error code values associated with the NEWPROCESS call and take appropriate action.

0004

Backup process in CPU cpu_number stopped.

cpu_number

indicates the number of the processor in which backup was stopped.

Cause The backup process stopped as a result of a previous request to stop or change the backup.

Effect The backup process terminates as expected.

Recovery This message is informational only. No corrective action is necessary.

0005

Primary process abended.

Cause A processing error occurred that caused the process to abend.

Effect The backup process attempts to recover. You can expect a message indicating that the backup process has taken over for the primary.

Recovery This message indicates a serious internal programming error. Determine the location of the SAVEABEND file created by the abend and forward it to your service provider.

0006

Primary process stopped; primary CPU cpu_number has failed.

cpu_number

indicates the number of the processor that failed.

Cause The primary process has stopped because of a failure of the primary processor.

Effect The backup process attempts to recover. You can expect a message indicating that the backup process has taken over for the primary.

Recovery This message is informational only. No corrective action is necessary.

0007

Backup CPU cpu_number has been restored.

cpu_number

indicates the processor number that has been restored.

Cause The processor that is configured for the backup process has been restored.

Effect The primary process attempts to start the backup.

Recovery This message is informational only. No corrective action is necessary.

0008

Backup stopped; backup CPU cpu_number has failed.

cpu_number

indicates the number of the processor that failed.

Cause The processor where the backup process was running failed.

Effect The process is no longer backed up. An attempt is made to restart the backup when the processor is restored.

Recovery Wait until the backup processor is restored, or move the backup process to an operational processor.

0009

Backup process in CPU cpu_number stopped unexpectedly.

cpu_number

indicates the number of the processor in which the backup has failed.

Cause The backup process stopped for some reason other than from a STOP being issued by the primary process. This error is usually caused by an operator stopping the backup process with a command interpreter.

Effect The process is no longer backed up. An attempt is made to restart the backup.

Recovery Determine why the backup stopped. If the process was terminated by an operator, it is restarted automatically by the primary process.

0010

Backup process in CPU cpu_number abended.

cpu_number

indicates the number of the processor in which the backup abended.

Cause The backup process abended.

Effect The process is no longer backed up. An attempt is made to restart the backup.

Recovery Determine why the backup abended. Locate the SAVEABEND file created by the abend and forward it to your service provider.

0011

Log recording to device_name has stopped.

device_name

indicates the name of the device or file to which logging has begun.

Cause Log recording stopped.

Effect None.

Recovery This message is informational only. No corrective action is necessary.

0012

Log recording has been started to device_name.

device_name

indicates the name of the device or file to which logging started.

Cause Log recording was started to the specified device.

Effect None.

Recovery This message is informational only. No corrective action is necessary.

0013

File system error Guardian_error occurred on log device_name. Log recording has been stopped.

`Guardian_error`	indicates the Guardian error number that occurred on the logfile.
`device_name`	indicates the name of the log device or file.

Cause File-system error <error code> occurred on log <device name>. Log recording has been stopped.

Effect Log recording stops.

Recovery Determine and correct the cause of the error and restart log recording.

0015

Object started.

Cause The operational state of the designated object has changed to STARTED.

Effect None.

Recovery This message is informational only. No corrective action is necessary.

0016

Object stopped.

Cause The operational state of the designated object has changed to STOPPED.

Effect None.

Recovery This message is informational only. No corrective action is necessary.

0017

Object stopping.

Cause The operational state of the designated object has changed to STOPPING.

Effect None.

Recovery This message is informational only. No corrective action is necessary.

0018

Object aborted.

Cause The operational state of the designated object has changed to ABORTED.

Effect None.

Recovery This message is informational only. No corrective action is necessary.

0019

Object restart in restart_count seconds.

restart_count

indicates the number of seconds between restart events.

Cause An automatic restart of the designated object was scheduled. The value of the interval is specified by configuring the object’s AUTORESTART attribute.

Effect An attempt to restart the object occurs after the specified interval.

Recovery This message is informational only. No corrective action is necessary.

0020

error_class file system error error_code occurred during a operation attempt.

`error_class`	indicates a gross error classification such as FATAL, RETRYABLE, CONFIGURATION, and so on.
`error_code`	indicates the error code defined by error class.
`operation`	indicates the file-system operation that was being attempted when the error occurred.

Cause A Guardian file-system error occurred while trying to perform the designated operation.

Effect The designated operation is unsuccessful. The operational state of the object depends upon the object type and the operation that was attempted.

Recovery Determine the cause of the error, correct the configuration if necessary, and if the object is in the STOPPED or ABORTED state, restart it.

0021

error_class subsystem_type error error_code occurred during a operation attempt.

`error_class`	indicates a gross error classification such as FATAL, RETRYABLE, CONFIGURATION, and so on.
`subsystem_type`	indicates the underlying transport subsystem whose function was invoked when the error occurred.
`error_code`	indicates the error code defined by error class.
`operation`	indicates the subsystem-dependent operation that was being attempted when the error occurred.

Cause A transport subsystem error in the specified subsystem occurred while trying to perform the designated operation.

Effect The designated operation is unsuccessful. The operational state of the object depends upon the object type and the operation that was attempted.

Recovery Determine the cause of the error, correct the configuration if necessary, and if the object is in the STOPPED or ABORTED state, restart it.

0022

A file system operation has terminated with error error_code and is being retried.

error_code

indicates the error code returned by file-system operation.

Cause A retryable Guardian file-system operation finished with an error.

Effect The operation is retried at 2-second intervals until it succeeds.

Recovery Depending on the cause of the error, this might indicate a serious configuration error. Contact your Guardian system administrator. When error_code is file-system error 28 (“A nowait I/O request brought the number of outstanding nowait requests on the given file to a value greater than the maximum nowait depth specified when the file was opened.”), the TDP may also issue event message 1557 every 2 seconds until FS error 28 is resolved. This is normal behavior; no corrective action is necessary.

0023

A subsystem_type operation has terminated with error error_code and is being retried.

`subsystem_type`	indicates the underlying transport subsystem whose function was invoked when the error occurred.
`error_code`	indicates the error code returned by the file-system operation.

Cause A retryable transport subsystem-level operation finished with an error.

Effect The operation is retried at 2-second intervals until it succeeds.

Recovery Depending on the cause of the error, this might indicate a serious configuration error. Contact your system administrator.

0024

Message Format Error ... Path:netname_or_linename, Type: message_type.

`netname_or_linename`	indicates the transport subsystem-oriented path such as NETBIOS network name or asynchronous line name.
`message_type`	indicates the TDM message type number.

Cause The operational state of the object changed to started.

Effect None.

Recovery None.

0025

Message Format Error ... Socket:socket_number, Type: message_type.

`socket_number`	indicates the transport subsystem-oriented socket number.
`message_type`	indicates the TDM message type number.

Cause The operational state of the object has changed to started.

Effect None.

Recovery None.

0026

An excessive number of retryable errors has been received from the process_name process.

process_name

indicates the name of another process with which the TDP is communicating, normally a transport process such as TC/PIP, SPX/IPX, and so on.

Cause The retryable error count was exceeded, possibly because of network errors.

Effect The designated object is aborted.

Recovery Correct the conditions that caused the network errors.

0027

Message received with invalid length of message_length on socket socket_number. Data: message_data.

`message_length`	indicates the number of characters actually received.
`socket_number`	indicates the number of the socket upon which the message was received.
`message_data`	indicates the first 32 message characters expressed in hexadecimal.

Cause An error occurred while the designated object was attempting a RECEIVE on the indicated socket.

Effect The designated object’s session is terminated.

Recovery This error should never occur. Report the error to your system administrator.

0028

error_class Completion on socket socket_number occurred during a operation attempt.

`error_class`	indicates gross error classification such as FATAL, RETRYABLE, CONFIGURATION, and so on.
`socket_number`	indicates the number of the socket upon which the message was received.
`operation`	indicates the subsystem-dependent operation that was being attempted when the error occurred.

Cause A fatal file system error occurred on the socket, the socket closed unexpectedly without notice, or an unexpected file system error was received.

Effect The designated object was aborted.

Recovery Correct the conditions that caused the file system error.

0029

File system error error_code occurred while attempting to open process-function process_name.

`error_code`	indicates the Guardian file-system error code.
`process-function`	indicates the function or purpose of the external process being opened.
`process_name`	indicates the name of the external process being opened.

Cause An error occurred while trying to open the designated process.

Effect The designated process is not opened. Begin session or writeread fails.

Recovery Make sure that the referenced object is correctly configured, and check the designated process for errors.

0030

State table error ... Event event_id, Action action_id, State state_id

`event_id`	indicates internal TDP parameter.
`action_id`	indicates internal TDP parameter.
`state_id`	indicates internal TDP parameter.

Cause An internal program error was detected.

Effect The object that reported the error might be in an invalid state.

Recovery Abort and restart the object. If the object is not accessible through RSCCOM, restart the TDP. Record the message text and report it to your service provider.

0031

TDP - product_id - Started by user user_name.

`product_id`	indicates the TDP product ID code.
`user_name`	indicates the name of the user who initiated the TDP.

Cause The TDP process was started.

Effect None.

Recovery This message is informational only. No corrective action is necessary.

0032

Starting SHUTDOWN.

Cause The current DEMO RSC TDP expired.

Effect The TDP is soon shut down.

Recovery Contact your service provider for further information.

0033

SHUTDOWN completed.

Cause The current DEMO RSC TDP expired.

Effect None.

Recovery Contact your service provider for further information.

0034

The current RSC DEMO TDP expires in <nnnn> days.

nnnn	indicates the number of days in which the DEMO TDP expires.

Cause The DEMO TDP is nearing the end of the trial period.

Effect The DEMO TDP does not run after expiration.

Recovery Contact your service provider for further information.

0035

The current DEMO RSC TDP has expired.

Cause The current DEMO RSC TDP has expired.

Effect The TDP is soon shut down.

Recovery Contact your service provider for further information.

0036

The Multilan gateway name table is full.

Cause The network name table on the Multilan gateway is full. No additional network names can be added.

Effect The designated NETNAME object cannot be started.

Recovery Ask your Multilan administrator to configure the resource, or use an existing resource.

0037

Network name is already in use on the Multilan gateway.

Cause The specified network name was already added to the Multilan gateway by another application.

Effect The NETNAME object cannot be started.

Recovery NetBIOS network names must be unique on the LAN. Determine a unique network name for the NETNAME object.

0038

Multilan resource_type resource resource_name has not been configured.

`resource_type`	indicates the type of Multilan resource that is unconfigured.
`resource_name`	indicates the name of the Multilan resource that is unconfigured.

Cause The specified resource was not configured in the Multilan environment.

Effect The NETNAME object cannot be started.

Recovery Ask your Multilan administrator to configure the resource, or use an existing resource.

0039

The specified Multilan gateway adapter is not installed or the specified gateway is not operational.

Cause The specified network adapter was not installed in the Multilan gateway, or the specified gateway was configured but not started.

Effect The NETNAME object cannot be started. Restart is attempted if configured.

Recovery Make sure that the gateway is operational. If it is, correct the NETNAME ADAPTER attribute so that it is valid for the gateway.

0040

The value of MAXLISTENS has been increased to count because of increased gateway session resources.

count

indicates the value of MAXLISTENS.

Cause The value of MAXLISTENS, which was previously reduced because of a gateway resource shortage, was increased.

Effect The NETNAME object can issue additional NetBIOS LISTEN commands on the gateway.

Recovery This message is informational only. No corrective action is necessary.

0041

The value of MAXLISTENS has been reduced to count because of insufficient gateway session resources.

count

indicates the value of MAXLISTENS.

Cause Insufficient NetBIOS session availability on the Multilan gateway has caused the MAXLISTENS count to be reduced by one.

Effect If the count becomes zero, no other workstations will be able to connect to the TDP.

Recovery The MAXLISTENS count automatically increases when session resources become available. If the problem persists, report it to your Multilan system administrator.

0042

A NetBIOS SEND to terminal network_terminalname has not completed in count seconds. The session with the terminal will be aborted.

`network_terminalname`	indicates the name of a TDP TERM object.
`count`	indicates the maximum number of allowable seconds for a SEND to complete.

Cause The NETNAME could not complete a NetBIOS SEND operation to the terminal within the specified timeframe.

Effect The session with the terminal is aborted.

Recovery This error should not happen during normal operation but can happen if the workstation's NetBIOS subsystem hangs while processing a RECEIVE request. Restart the workstation.

0043

Session session_id will be terminated due to an unexpected Pathway terminal failure.

session_id

indicates the value of a TDP TERM object’s session identifier.

Cause The Pathway terminal associated with the session sent an unexpected CLOSE message to the TDP.

Effect The session is terminated.

Recovery This might be the result of a Pathway terminal abort or a TCP failure. Examine the Pathway terminal to determine the cause before restarting the workstation application.

0044

Session session_id will be terminated due to an IDS requester protocol violation.

session_id

indicates the value of a TDP TERM object’s session identifier.

Cause An IDS requester program issued a SEND MESSAGE statement to the TDP without a YIELDS clause.

Effect The session is terminated.

Recovery RSC requires that IDS requesters use the WRITEREAD form of the SEND MESSAGE statement. Correct the IDS requester program.

0045

Protocol violation.detected. A message was received which could not be interpreted. Data: message_data.

message_data

indicates the first 32 message characters expressed in hexadecimal.

Cause The TERM object received a message that it could not recognize.

Effect The TERM object attempts to return an error to the workstation.

Recovery This problem indicates a serious network hardware or protocol problem. Report the problem to your network administrator.

0046

Missing or invalid license code received from workstation.

Cause A workstation application sent a BeginSession request with a missing or invalid license code. A license code is required to start RSC Lite. This message is obsolete.

Effect The session is denied.

Recovery Verify that the workstation application code in the workstation application is the same as the code delivered by HP. If it is not, correct the program, and try again. If it is the same, contact your service provider.

This message displays on the Compaq system in a ViewPoint screen and is not returned to the API. It is for operational use only.

0047

Session session_id Unsolicited message rejected, UMS queue limit of count entries has been reached.

`session_id`	indicates value of a TDP TERM object’s session identifier.
`count`	indicates UMS queue limit count.

Cause An unsolicited message was rejected because too many unsolicited messages are outstanding.

Effect Unsolicited messages are not delivered to the workstation.

Recovery Check the number of unsolicited messages on the workstation. You can end the session to clear the queue for unsolicited messages. This error is sent back to the server on a UmsWriteRead call.

0048

Session session_id Unsolicited message rejected, I/O Type is IO_type, Error error_code.

`session_id`	indicates value of a TDP TERM object’s session identifier.
`IO_type`	indicates Pathway, Pathsend, IDS or Interprocess.
`error_code`	indicates Guardian error code.

Cause An unsolicited message was rejected because it could not be delivered to the terminal.

Effect The message is not delivered and an error is returned to the sender if appropriate.

Recovery Determine the cause of the error and correct it before restarting the workstation application.

0049

Unsolicited message rejected, I/O Type is IO_type, Invalid reason size size.

`IO_type`	indicates Pathway, Pathsend, IDS or Interprocess.
`reason`	indicates text string indicating reason for failure.
`size`	indicates size of UMS.

Cause An unsolicited message was rejected because of invalid size-less than 0 or greater than 31000.

Effect The message is not delivered and an error is returned to the sender if appropriate.

Recovery Determine the cause of the error and correct it before restarting the workstation application.

0050

An excessive number of zero-length receives has been detected on LINENAME linename.

linename

indicates the device name of the async line encountering the errors.

Cause The workstation cable might be disconnected.

Effect The ASYNCPORT is aborted.

Recovery Make sure that the workstation cable is attached and restart the ASYNCPORT.

0051

ACS not started due to an invalid configuration.

Cause ACS attributes ACSSERVERCLASS and ACSPROCESSNAME were left blank.

Effect The ACS cannot be started.

Recovery Specify the server class and process name of the process associated with the ACS object.

0052

The ACS object received a message with an invalid tag.

Cause The ACS object received a message with a tag that does not match any tag sent out.

Effect There might be no effect, a begin session or writeread hangs.

Recovery Check the message the access control server passes to the ACS object.

0053

The TDP cannot set Piccolo runtime license in pipe.

Cause The pipeSetInfo failed.

Effect The pipe is unregistered.

Recovery None.