HP NonStop Remote Server Call (RSC/MP) Messages Manual Abstract This manual provides a listing and description of RSC/MP messages that are reported on the HP NonStop™ host and on RSC/MP workstations. Message descriptions include their cause, effect, and recovery procedures. Product Version RSC/MP R7.3.7 Supported Release Version Updates (RVUs) This publication supports G06.20 and all subsequent G-series RVUs, H06.20 and all subsequent H-series RVUs and J06.
Document History Part Number Product Version Published 425710-001 RSC/MP R6.1 March 2000 520228-001 RSC/MP R6.2 June 2001 522359-001 RSC/MP R6.3 September 2002 522359-002 RSC/MP R7.0 September 2003 522359-003 RSC/MP R7.1 September 2004 522359-004 RSC/MP R7.2 June 2005 522359-005 RSC/MP R7.3.2 April 2011 522359-006 RSC/MP R7.3.
HP NonStop Remote Server Call (RSC/MP) Messages Manual Glossary Index Examples What’s New in This Manual iii Manual Information iii New and Changed Information Figures iii About This Manual v Manual Contents and Organization Audience Requirements v Related Manuals v Notation Conventions vi v 1. Introduction How to Find an RSC/MP Message 1-1 Workstation Message Numbers 1-1 2. Messages Reported From the Host 3. API Messages 4. Pathsend Messages 5. UMS Messages 6. Piccolo Messages 7.
Contents Tables Tables Table 1-1. Table 1-2. Table 4-1.
What’s New in This Manual Manual Information Abstract This manual provides a listing and description of RSC/MP messages that are reported on the HP NonStop™ host and on RSC/MP workstations. Message descriptions include their cause, effect, and recovery procedures. Product Version RSC/MP R7.3.7 Supported Release Version Updates (RVUs) This publication supports G06.20 and all subsequent G-series RVUs, H06.20 and all subsequent H-series RVUs and J06.
What’s New in This Manual New and Changed Information HP NonStop Remote Server Call (RSC/MP) Messages Manual — 522359-006 iv
About This Manual The HP NonStop Remote Server Call (RSC/MP) product allows workstation-based client applications to communicate with servers on a NonStop host. This manual describes the messages returned by the NonStop host and by the client applications on remote workstations. Manual Contents and Organization This manual contains: Section 1, Introduction, describes how RSC/MP messages are numbered and how to find a description of these messages.
About This Manual Notation Conventions You can find detailed information about other NonStop system components in the appropriate HP manuals. Notation Conventions The following list summarizes the notation conventions for syntax presentation in this manual. Uppercase letters. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH Lowercase italic letters.
About This Manual Notation Conventions For example, this host error message contains two sets of alternatives, and reports one item from each set: <'Fatal' | 'Unexpected'> file system error occurred during a <'ADD_NAME' | 'LISTEN' | 'RECEIVE_ANY' | 'SEND'> attempt. The error message contains this information: Fatal or Unexpected ADD_NAME or LISTEN or RECEIVE_ANY or SEND … Ellipsis.
About This Manual Notation for Messages Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. Lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets.
About This Manual Change Bar Notation ADD_NAME or LISTEN or RECEIVE_ANY or SEND % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: %005400 %B101111 %H2F P=%p-register E=%e-register Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version.
About This Manual Change Bar Notation HP NonStop Remote Server Call (RSC/MP) Messages Manual — 522359-006 x
1 Introduction This manual describes all Remote Server Call (RSC/MP) messages that are reported by the RSC/MP Host running on a NonStop system or by an RSC/MP client running on a workstation. How to Find an RSC/MP Message Use Table 1-1 to locate the section of this manual that describes the message types. Table 1-1.
Introduction Workstation Message Numbers Table 1-2. Base Values of RSC/MP Messages Reported on the Workstation Subsystem Name HEX Base Value Documentation Sources RSC/MP API 0000 Section 3, API Messages Pathway/TS 1000 Pathway PATHCOM Reference Manual Pathsend 2000 Section 4, Pathsend Messages and the TS/MP Pathsend and Server Programming Manual UMS 6000 Section 5, UMS Messages Piccolo A000 Section 6, Piccolo Messages EMS N.A.
2 Messages Reported From the Host This section describes the messages reported from the NonStop host according to base values and describes their cause, effect, and recovery procedure. To learn more about host messages and recovery from data communications failures, see the Remote Server Call (RSC/MP) Programming Manual. Host messages have the format: date time TDP:process-name:object-type:[object-name]:msg-id msg-text where the parameters are defined as: date time The current date and time.
Messages Reported From the Host 0401 Takeover by backup in CPU . Cause. A takeover has just occurred, and the former backup process has 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 formerly held the primary process. Recovery. This message is informational only. No corrective action is necessary.
Messages Reported From the Host 0405 Primary process stopped; primary CPU has failed. Cause. The primary process has stopped because of a failure of the primary CPU. Effect. The backup process will attempt to recover. Recovery. This message is informational only. No corrective action is necessary. 0406 Backup CPU has been restored. Cause. The CPU that is configured for the backup process has been restored. Effect. The primary process will attempt to start the backup. Recovery.
Messages Reported From the Host 0409 Backup process in CPU 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 HP Global Customer Support Center (GCSC). 0411 Receive Depth critically low - of slots in use. Some operations will be suspended. Cause. TDP handling exceeding large amount of traffic.
Messages Reported From the Host 0452 Log recording has been started to . Cause. Log recording has been started to the specified device. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 0453 File system error occurred on log . Log recording has been stopped. Cause. A Guardian file system error has occurred on the log device. Effect. Log recording stops. Recovery.
Messages Reported From the Host 0803 SHUTDOWN completed. Cause. The current DEMO TDP has expired. Effect. None. Recovery. Contact your HP Global Customer Support Center (GCSC). 0804 Starting SHUTDOWN. Cause. The current DEMO TDP has expired. Effect. The TDP will be shut down shortly. Recovery. Contact your HP Global Customer Support Center (GCSC). 0805 The current DEMO TDP expires in days. Cause. The current DEMO TDP will expire in the number of days indicated. Effect. None. Recovery.
Messages Reported From the Host 2501 Connection established via
Messages Reported From the Host 2505 [] UMS check completed, result (), message size , I/O handle , UMS queue depth is now . Cause. A workstation RscUmsCheck request was completed. Effect. None. Recovery. This message is informational only. No corrective action is necessary.
Messages Reported From the Host 2509 [] Level UMS completion sent, I/O handle . Cause. The workstation has been notified that an unsolicited message has been received. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 2510 [] Level I/O completion sent, I/O handle . Cause. The workstation has been notified that an I/O completion has occurred. Effect. None. Recovery. This message is informational only.
Messages Reported From the Host 2513 [] UMS reply completed, result ,() reply size , I/O handle , UMS depth is now . Cause. The workstation replied to an unsolicited message. Effect. None. Recovery. This message is informational only. No corrective action is necessary.
Messages Reported From the Host 2517 [] Unable to start terminal in Pathway , second timeout has expired. Cause. The Pathway terminal associated with the session could not be started in the specified time frame. Effect. The workstation RscBeginSession request fails. Recovery. Examine the Pathway configuration to determine if the terminal SUSPENDED on startup. If it did not, increase the value of the TERM PWYTIMEOUT.
Messages Reported From the Host 2521 [] Session will be terminated due to an IDS requester protocol violation. Cause. The IDS requester program has 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. 2522 TERM created, TERM_TEMPLATE=, TERM_NAME=. Cause.
Messages Reported From the Host 2527 [] IDS I/O started, request size , reply Size , I/O handle , I/O tag . Cause. An IDS I/O has been started. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 2528 [] Server opening, name , file handle , I/O tag , I/O index . Cause. A server is being opened. Effect. None. Recovery. This message is informational only.
Messages Reported From the Host Effect. The application will be unable to utilize the server. The effect this has on the application depends on the application. Recovery. The recovery is specific to your application. See the Guardian Procedure Errors and Messages Manual for more information. 2532 [] Server already open, name , file handle , I/O index . Cause. The TDP found a server already open. Effect. None. Recovery. This message is informational only.
Messages Reported From the Host 2536 [] Implicit resume transaction failed, transaction id , TMF Error . Cause. An outstanding transaction could not be resumed prior to initiating an interprocess I/O. Effect. The workstation RscWrite or RscWriteRead request fails. Recovery. Determine the cause of the error and correct it before restarting the workstation application.
Messages Reported From the Host 2540 [] Implicit end transaction succeeded, transaction id . Cause. An outstanding transaction was ended at interprocess I/O completion. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 2541 [] Implicit end transaction failed, no transaction in progress. Cause. An implicit end transaction request failed because no transaction was in progress. Effect.
Messages Reported From the Host 2544 [] Explicit begin transaction failed, TMF Error . Cause. A workstation RscBeginSession request could not be completed because of a TMF error. Effect. The workstation request fails. Recovery. Determine the cause of the error and correct it before restarting the workstation application. 2545 [] Explicit begin transaction succeeded, transaction id . Cause.
Messages Reported From the Host 2548 [] Explicit end transaction succeeded, transaction id . Cause. A workstation RscEndTransaction request succeeded. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 2549 [] Explicit abort transaction failed, no transaction in progress. Cause. A workstation RscAbortTransaction request failed because no transaction was in progress. Effect. The workstation request fails. Recovery.
Messages Reported From the Host 2552 [] Unsolicited message queued, I/O type is , message size , reply size , I/O handle , UMS queue depth is now . Cause. An unsolicited message was queued. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 2553 Term Memory , Size , address , state , event , MemInUse . Cause. The TERM object has allocated the indicated memory block. Effect. None.
Messages Reported From the Host 2556 [] Attempt to access pathmon , serverclass by user ALLOWED. Cause. The ACS Server has allowed access to a PATHSEND serverclass or a PATHWAY serverclass through the IDS router. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 2557 [] Attempt to access by user REJECTED. Cause. The ACS server has rejected access to a named server.
Messages Reported From the Host 2802 TERM started. Cause. The operational state of the object has changed to STARTED.See the RSCCOM START command in the Remote Server Call (RSC/MP) Installation and Configuration Guide for more information. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 2803 TERM stopped. Cause. The operational state of the object has changed to STOPPED.
Messages Reported From the Host 2806 TERM stopping. Cause. The operational state of the object has changed to STOPPING. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 2807 Protocol violation detected. A message was received which could not be interpreted. Data: [ ]. 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.
Messages Reported From the Host 2812 Unsolicited message rejected, I/O Type is , Invalid size . Cause. An unsolicited message was rejected because of invalid size – less than 0 or greater than 56000. 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. 3001 COM state table error ... Event , Action , State .
Messages Reported From the Host 3003 *** Error 3003: Backup CPU is the same as the primary CPU. Cause. The specified backup CPU is the same as the current primary CPU. Effect. If the backup CPU specification was supplied with the TDP process RUN command, the backup will not be created. If it was supplied as an argument to the RSCCOM CONTROL command, the command fails. Recovery. Specify a CPU number for the backup that is not the same as the primary CPU.
Messages Reported From the Host 3006 *** Error 3006: The backup process is already running in CPU . Cause. The backup process is already running in the specified CPU. Effect. The request fails. Recovery. Specify a CPU number that does not already contain the TDP backup process. 3007 *** Warning 3007: The PATHSENDENABLE command is obsolete. Cause. The PATHSENDENABLE command is no longer supported. Pathsend availability is now determined programmatically. Effect. None. Recovery.
Messages Reported From the Host 3011 *** Error 3011: The '' command requires an object specifier. Cause. The command entered requires an object. Effect. The command is rejected. Recovery. Supply a valid object for the command. 3012 *** Error 3012: The object '
Messages Reported From the Host 3016 *** Error 3016:
Messages Reported From the Host 3020 *** Error 3020: Only specific objects may be ALTERed. Cause. An ALTER command was issued without a specific object name. The command ALTER
Messages Reported From the Host 3024 *** Error 3024: '' must be a valid file or process name. Cause. An invalid file or process name was supplied for the attribute. Effect. The command is rejected. Recovery. Supply a valid file or process name for the attribute. 3025 *** Error 3025: '' must be at least but not more than . Cause. The value supplied for the attribute is out of the valid range. Effect. The command is rejected. Recovery.
Messages Reported From the Host 3028 *** Error 3028:
Messages Reported From the Host 3032 *** Warning 3032:
Messages Reported From the Host 3036 *** Error 3036: A
Messages Reported From the Host 3041 *** Error 3041: No such line. Cause. A command line edit request was issued for a command line that does not exist. Effect. The command is rejected. Recovery. Use the HISTORY command to determine which lines can be edited and reissue the command if appropriate. 3042 *** Error 3042: Process is not a TDP or is a TDP which is not compatible with this release of RSCCOM. Cause.
Messages Reported From the Host 3045 *** Error 3045: You must supply a valid attribute type. Cause. An object SET or ALTER command was issued without an attribute argument. Effect. The command is rejected. Recovery. See the Remote Server Call (RSC/MP) Installation and Configuration Guide for the correct command syntax and reissue the command if appropriate. 3046 *** Error 3046: Attribute is not valid for this object type. Cause.
Messages Reported From the Host 3050 *** Error 3050: '' must be at least hex but not more than . Cause. The hexadecimal value supplied for the attribute is out of the valid range. Effect. The command is rejected. Recovery. Supply a valid hexadecimal value for the attribute. 3051 *** Error 3051: Argument <‘invalid argument’> is invalid. Cause. The command has an unrecognized argument. Effect. The command is rejected. Recovery.
Messages Reported From the Host 3056 *** Error 3056: <'name'> is not a valid security mask specifier. Cause. A CONTROL TDP SECURITY command has been issued with an invalid mask specifier. Effect. The command is rejected. Recovery. See the Remote Server Call (RSC/MP) Programming Manual for a list of valid security mask specifiers. 3057 *** Error 3057: Security mask missing. Cause. A CONTROL TDP SECURITY command has been issued with no mask specifier. Effect. The command is rejected. Recovery.
Messages Reported From the Host 3060 *** Error 3060: Unknown keyword - type HELP to review syntax. Cause. An unknown or invalid keyword was entered as an argument to a HELP command. Effect. None. Recovery. Reissue the Help command by using the correct syntax. 3061 *** Error 3061: RSCCOM internal error - unable to locate message . Cause. There is a problem with the help text file or the help file you have is incorrect. Effect. Help text is missing for an RSCCOM command. Recovery.
Messages Reported From the Host 3064 *** Error 3064: Help text file format error – HELP unavailable. Cause. There is a problem with the help text file. Effect. Help is not available. Recovery. Reinstall the RSC/MP software on the host. 3065 *** Error 3065: Insufficient memory for HELP function - HELP unavailable. Cause. There is not enough memory to load the HELP directory. Effect. The help file cannot be opened. Recovery. Make more memory available and try again.
Messages Reported From the Host 3068 *** Error 3068: is not a valid suppress specifier. Cause. A Control TDP SupressEMS command was issued with an invalid argument. Effect. The command is rejected. Recovery. Retry the command using ― Y‖ or ― N‖ as the argument. 3069 *** Error 3069: Suppress specifier missing. Cause. A Control TDP SupressEMS command was issued with a missing argument. Effect. The command is rejected. Recovery. Retry the command using ― Y‖ or ― N‖ as the argument.
Messages Reported From the Host 3502 Pathway terminal was not deleted from Pathway . The Pathway is not available. Cause. A Pathway terminal which was created by the primary process of a TDP process pair could not be deleted by the backup process after takeover by the backup. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 3801 PWYMGR state table error ... Event , Action , State . Cause.
Messages Reported From the Host 6503 A RECEIVE has completed on a closed socket: . Cause. The socket closed, probably because of a client shutdown or a network outage. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 6504 TCPIP Receive - Size: , Type: . Cause. The received message could not be processed because of an invalid message type (because of network errors) or because of inadequate TDP buffer space. Effect.
Messages Reported From the Host 6507 Retryable Error on socket occurred during a <'SEND' | 'RECEIVE'> attempt. Cause. A retryable error occurred on the socket. Effect. The Send or Receive operation was retried by the TDP. If errors continue, the TCPIPPORT object might be aborted. Recovery. This message is informational only. No corrective action is necessary. 6801 TCPIPPORT state table error ... Event , Action , State . Cause.
Messages Reported From the Host 6803 TCPIPPORT stopped. Cause. The operational state of the object has changed to STOPPED. See the RSCCOM STOP command in the Remote Server Call (RSC/MP) Installation and Configuration Guide for more information. Effect. None. Recovery. This message is informational only. No corrective action is necessary. 6804 TCPIPPORT aborted. Cause. The operational state of the object has changed to ABORTED.
Messages Reported From the Host 6806 <'Guardian' | 'Fatal' | 'TCP/IP' | 'Retryable' | 'Unexpected'> file system error occurred during a <'ACCEPT' | 'ACCEPT2' | 'BIND' | 'CLOSE' | 'CLSOCK' | 'GTSOCK' | 'SOCKOPT' | 'SOCKSND' | 'SOCKRCV' | 'SEND' | 'RECEIVE'> attempt. Cause. A fatal or unexpected error occurred while attempting the specified file system or TCP/IP run-time operation. Effect. The operation failed. Recovery. Recovery depends on the severity and type of error.
Messages Reported From the Host 6809 Message received with invalid length of on socket . Data: Cause. The message length is out of range, probably because of network errors. Effect. The TCPIPPORT object was aborted. Recovery. Correct the conditions that caused the network errors. 6810 Message Format Error ... Socket: , Type: . Cause.
Messages Reported From the Host 7301 ACS state table error ... Event , Action , State . Cause. The Access Control Server (ACS) received an unexpected combination of event ID and state ID. Effect. The event is ignored. Recovery. This message is informational only. No corrective action is necessary. 7302 ACS started. Cause. The operational state of the object has changed to STARTED.
Messages Reported From the Host 7305 ACS object not started due to an invalid configuration. Cause. ACS attributes ACSSERVERCLASS and ACSPROCESSNAME have been left blank. Effect. The ACS cannot be started. Recovery. Specify the server class and process name of the process associated with the ACS object. 7306 File system error occurred while trying to open Access Server Guardian 90 process. Cause. An error occurred while trying to open the Access Server. Effect.
Messages Reported From the Host 8503 PIPE Event Completed - . Cause. The PIPE event (the request that the TDP made of Piccolo) has completed. Effect. The PIPE will be closed and the session will be terminated. Recovery. This message is informational only. Additional messages can contain information about the completed event. 8504 PIPE Receive has been posted. Cause. The PIPE event (the request that the TDP made of Piccolo) has been received. Effect. None. Recovery.
Messages Reported From the Host 8507 PIPE Open Posted on , Listen Index . Cause. The TDP has opened a PIPE. Effect. Piccolo is available. Recovery. This message is informational only. No corrective action is necessary. 8508 PIPE Open Completed on , Listen Index , Session Index: , PipeHandle: . Cause. The TDP successfully opened a PIPE. Effect. Piccolo is available. Recovery. This message is informational only. No corrective action is necessary.
Messages Reported From the Host 8801 PIPE state table error ... Event , Action , State . Cause. An internal program error that should never occur has been 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 HP Global Customer Support Center (GCSC). 8802 PIPE started. Cause.
Messages Reported From the Host 8805 PIPE re-start in seconds. Cause. An automatic restart of the object has been scheduled. The value of the interval is specified by configuring the PIPE AUTORESTART attribute. Effect. An attempt to restart the object will occur after the specified interval. Recovery. This message is informational only. No corrective action is necessary.
Messages Reported From the Host HP NonStop Remote Server Call (RSC/MP) Messages Manual — 522359-006 2- 52
3 API Messages This section lists the workstation messages in numerical order and provides information about the type, severity, cause, effect, and recovery for each message. See the Remote Server Call (RSC/MP) Programming Manual for descriptions of the base values, error classes, and severity assignments. The RSC/MP API messages have a hexadecimal base value of 0000. 0 (0000 Hex) The operation was successful. Type. Unclassified Severity. Not applicable Cause. The operation was successful. Effect.
API Messages Recovery. Install the appropriate RSC/MP communications subsystem, or set the SUBSYSTEM_NAME option to the name of an installed RSC/MP communications subsystem. See the Remote Server Call (RSC/MP) Installation and Configuration Guide for installation procedures. 4 (0004 Hex) Duplicate IO handle. The IO handle you have used is currently outstanding on this session. Type. Program Severity. Fatal Cause. Duplicate I/O handle. The I/O handle used is already outstanding on this session. Effect.
API Messages 7 (0007 Hex) The specified IO handle is not valid. IO handles must be greater than 0. Type. Program Severity. Fatal Cause. The specified I/O handle is not valid. Effect. I/O handles must be greater than zero. Recovery. For nowaited I/O, the handle must be greater than zero. 9 (0009 Hex) The requested operation is not supported by this session type. Type. Program Severity. Fatal Cause. The requested operation is not supported. TMF transaction operations are not allowed for IDS type sessions.
API Messages 11 (000B Hex) The specified options selector does not reference a valid option. Type. Program Severity. Fatal Cause. The specified option selector does not reference a valid option. Effect. You cannot use this option selector. Recovery. Specify a valid option selector. See ― API Option Definitions‖ in the Remote Server Call (RSC/MP) Programming Manual for a list of valid option selectors. 13 (000D Hex) The specified request size is not valid for the current session type. Type.
API Messages Recovery. The maximum message size is limited by session type: 56,000 bytes for RSC_ST_INTERPROCESS when performing I/O to a named server 31,000 bytes for RSC_ST_INTERPROCESS when performing I/O to a Pathway serverclass via Pathsend 8192 for sessions of type RSC_ST_IDS UMS may be up to 56,000 bytes. 15 (000F Hex) The specified session handle is not valid. Type. Program Severity. Fatal Cause. The specified session handle is not valid. Effect. You cannot use this session handle. Recovery.
API Messages Recovery. Call the RscIoCheck function until the I/O completes. 18 (0012 Hex) There are no Nowait IO requests pending. Type. Program Severity. Fatal Cause. There are no nowaited I/O requests pending (RscIoCheck function) or unsolicited messages (RscUmsCheck function) outstanding. Effect. No data is returned in the buffer. Recovery. A nowaited I/O using the RscWriteRead function must be issued before calling the RscIoCheck function. This is a normal condition for the RscUmsCheck function.
API Messages 21 (0015 Hex) The Pathway terminal supporting this session was terminated unexpectedly. Type. Session Severity. Fatal Cause. The Pathway terminal supporting this session was aborted unexpectedly. Effect. The API function failed. Recovery. Check the status of the Pathway/TS terminal and try the operation again. 22 (0016 Hex) There are insufficient resources to complete the request. Type. Program Severity. Fatal Cause. Resources have been exhausted on this workstation. Effect.
API Messages Severity. Fatal Cause. Too many nowaited I/Os are outstanding. Effect. There can be only one nowaited I/O outstanding on an IDS session. Recovery. Try the operation again. 25 (0019 Hex) Heap space in the TDP is exhausted. Try the operation again. Type. I/O Severity. Configuration Cause. Heap space in the TDP is exhausted. Effect. The I/O operation failed. Recovery. Retry the operation. 27 (001B Hex) A BEGIN transaction was requested while a transaction was already in progress. Type.
API Messages Recovery. End or abort the transaction explicitly or ensure that the first word of the reply message falls within the range between SUCCESS_LO and SUCCESS_HI option values. 29 (001D Hex) The specified IO handle is unknown. Type. Program Severity. Fatal Cause. The specified I/O handle is unknown. Effect. The API function failed. Recovery. To check on a particular I/O completion, specify a valid I/O handle (a handle value used during the RscWriteRead request).
API Messages 37 (0025 Hex) The TDP you have contacted is not configured for this terminal. Type. Connect Severity. Configuration Cause. The TDP you have contacted is not configured for this terminal. Effect. The API function failed, and the workstation failed to connect to the host. Recovery. Configure the TDP on the host for the terminal indicated by the TERM_NAME option on the workstation, or utilize a dynamic terminal.
API Messages Severity. Fatal Cause. The specified PATHMON process is not a PATHMON process. Effect. The API function failed. Recovery. Correct the PATHMON_NAME or WRITEREAD_PATHMON option in the workstation to a valid PATHMON running on the host. 43 (002B Hex) The specified terminal is not started. Type. Connect Severity. Configuration Cause. The specified terminal is not started in the TDP.
API Messages Cause. The specified session alias is already in use by this terminal. Effect. You cannot use this session alias. Recovery. Specify the SESSION_ALIAS option so that it is unique among all sessions and applications running on your workstation. 49 (0031 Hex) The TDP you are connected to is not currently enabled for Pathsend I/O. Type. I/O Severity. Configuration Cause. The TDP you are connected to is not currently enabled for Pathsend I/O.
API Messages Effect. You cannot communicate with PATHMON. Recovery. Examine the extended error code for the Guardian file system error that caused this error. See the Guardian Procedure Errors and Messages Manual and the Pathway/TS System Management Manual to resolve the problem. 54 (0036 Hex) The specified terminal template has not been configured. Type. Connect Severity. Configuration Cause. The specified terminal template has not been configured. Effect.
API Messages 65 (0041 Hex) The ACS object specified is not started or does not exist. Type. Session Severity. Fatal Cause. The ACS object specified is not started or does not exist. Effect. The request fails. Recovery. Start the ACS object or specify another ACS object. 66 (0042 Hex) The TDP is unable to contact the Access Server. Type. Session Severity. Fatal Cause. The TDP is unable to contact the ACS. Effect. The request is denied. Recovery. Check to see if the ACS is running.
API Messages Cause. The TDP was unable to open the ACS. Effect. Request fails. Recovery. Check to see why the ACS cannot be opened and fix the problem. If the ACS is down, restart it. Also check to see whether too many OPEN requests are accessing the ACS. 69 (0045 Hex) The Access Server has reported an I/O error. Type. Session Severity. Fatal Cause. The ACS has reported an I/O error. Effect. Request fails. Recovery. Check to see why the ACS had an I/O error and fix the problem.
API Messages Effect. Request fails. Recovery. Ensure that the workstation and host that are accessing RSC/MP are compatible. If they are, contact your HP Global Customer Support Center (GCSC). 72 (0048 Hex) The specified term name has been used by another workstation. Type. Connect Severity. Configuration Cause. This TERM object name is already in use by another workstation. Effect. You cannot connect to the host TDP. Recovery.
API Messages 86 (0056 Hex) You are attempting to unregister a thread that was never registered. Type. Programming Severity. Fatal Cause. The RscUnRegisterThread function was called before the RscRegisterThread function. Effect. The operation is ignored. Recovery. Register a thread before trying to unregister it. 87 (0057 Hex) A thread may not be registered more than once. Type. Programming Severity. Fatal Cause. You attempted to register a thread more than once. Effect. The operation is ignored.
API Messages 97 (0061 Hex) Your API library and Communications Subsystem are not compatible. Type. Connect Severity. Configuration Cause. Your API library and communications subsystem (RSCPIPE) are not compatible. Effect. The API library and RSC/MP communications subsystem cannot communicate. Recovery. Install a compatible release of RSCPIPE or RSC/MP API DLL (for Windows applications), or relink your application with a compatible release of the API library.
API Messages 101 (0065 Hex) The API was re-entered. The API is Non Re-entrant. Check your application. Type. Program Severity. Retry Cause. This error occurs when one RSC/MP API call is outstanding from one process and session, and another RSC/MP API call comes into the DLL from the same process in the same session. This happens, for example, if RSC/MP API calls are issued from a call-back routine or if RSC/MP API calls are issued after receiving a message sent by the Win-32 SendMessage call. Effect.
API Messages 104 (0068 Hex) Unable to allocate/access system resource (shared memory, semaphore, etc.). Type. Unclassified Severity. Retryable Cause. The OS denied a request for a system resource. Effect. The request resource is not allocated and the calling routine fails. Recovery. Try to free system resources. 105 (0069 Hex) A parameter value supplied is not valid. Type. Program Severity. Fatal Cause.
4 Pathsend Messages This section lists the Pathsend messages that you might encounter while using RSC/MP. These messages have a hexadecimal base value of 2000. See the TS/MP Pathsend and Server Programming Manual for more detail about these messages. Table 4-1. Pathsend Messages Number Decimal Hex Mes s ag e 900 2384 The server class name specified is not syntactically correct. 901 2385 The PATHMON process name specified is not syntactically correct.
Pathsend Messages HP NonStop Remote Server Call (RSC/MP) Messages Manual — 522359-006 4- 2
5 UMS Messages This section describes the Unsolicited Message System (UMS) messages that might be returned in the nCode parameter of the UMS header. These messages have a base value of hexadecimal 6000. 1 (6001 Hex) The destination terminal is not configured in the TDP. Type. Programming Severity. Fatal Cause. The destination terminal is not configured in the TDP. Effect. The unsolicited message cannot be delivered. Recovery.
UMS Messages 4 (6004 Hex) The specified alias is not registered. Type. Programming Severity. Fatal Cause. The specified alias has not been registered by a workstation application. Effect. The unsolicited message cannot be delivered. Recovery. Start the workstation application that registers the alias or correct the application program so that the alias specified in the RSC_UMS_HEADER is a registered alias.
UMS Messages 8 (6008 Hex) The maximum number of UMS messages are already queued to the specified alias. Type. Session Severity. Fatal Cause. The UMS TERM limit was exceeded. When the sender attempted to queue a UMS to a specific alias, it was determined that 256 unsolicited messages were already queued to that alias. Effect. When more than 256 unsolicited messages are queued to an alias, the UMS cannot be delivered. Recovery. Re-queue the UMS later.
UMS Messages HP NonStop Remote Server Call (RSC/MP) Messages Manual — 522359-006 5- 4
6 Piccolo Messages This section describes Piccolo messages that can be returned by RSC/MP. Piccolo messages are indicated by a base value of hexadecimal A000. The specific message codes listed here are caused by configuration or operational problems in the RSC/MP product. Any Piccolo message (indicated by the A000 base value) that is not listed in this section indicates an internal error in RSC/MP and should be reported to your Global Customer Support Center (GCSC).
Piccolo Messages 4 (A004 Hex) PIPERC_NO_ANSWER Cause. This error code indicates that no TDP has a PIPE object started on the host with a name that matches the HOST_PIPENAME option setting. Effect. RscConnect fails. Recovery. If the HOST_PIPENAME setting is wrong, fix it. Otherwise, start the TDP PIPE object. 9 (A009 Hex) PIPERC_PIPE_CLOSED Cause. A Piccolo pipe was closed unexpectedly while being used by RSC/MP.
Piccolo Messages Recovery. Confirm that a communications path to the remote system exists, that an appropriate local network interface is running, and that the Pipeman process and appropriate network interfaces on the remote system are running. 17 (A011 Hex) PIPERC_PIPEMAN_OBSOLETE Cause. The Pipeman process that is running on the local system is not compatible with RSC/MP. Effect. Results are unpredictable. Recovery. Reinstall RSC/MP. 32 (A020 Hex) PIPERC_INVALID_RESOLVER_ENTRY Cause.
Piccolo Messages 37 (A025 Hex) PIPERC_SYSTEM_ADDRESS_INUSE Cause. A pipeOpen request was rejected by the remote system, because the remote system is already connected to a system having the same system address as the local system. This error can occur when two machines running Piccolo are configured to have the same SystemName and DomainName settings, which is not allowed.
7 EMS Token Values and Event Messages This section describes the token values that can be used with the Event Management Service (EMS) and lists the event messages. See the HP EMS Manual for more details about EMS. Token Definitions The following lists show the RSC/MP-specific tokens and tokens that are common to all EMS-formatted messages logged by the TDP. RSC/MP-Specific Tokens Each EMS message includes a text template that can be ― filled in‖ by using one or more data values from this list.
EMS Token Values and Event Messages RSC/MP-Specific Tokens ZRSC-TKN-DETAILERROR ZSPI-TYP-INT Appears in messages that indicate an occurrence of a two-part GUARDIAN API error using a process-specific error code in two parts (for example, NEWPROCESS). This token’s value represents the detail portion of the error code. ZRSC-TKN-ENTRYCOUNT ZSPI-TYP-INT Appears in messages where a specific table entry count must be displayed (for example, number of UMS entries).
EMS Token Values and Event Messages RSC/MP-Specific Tokens ZRSC-TKN-MESSAGEDUMP ZSPI-TYP-STRING Appears in messages where a portion of an internal buffer between a client and a TDP must be displayed as a hexadecimal dump. ZRSC-TKN-MESSAGESIZE ZSPI-TYP-INT Appears in messages where the size of an internal RSC/MP message must be displayed. ZRSC-TKN-TDMMESSAGE-TYPE ZSPI-TYP-INT Appears in messages that reference a buffer containing a specific RSC/MP message type (TDM protocol). It specifies the type.
EMS Token Values and Event Messages RSC/MP-Specific Tokens ZRSC-TKN-PROCESSFUNCTION ZSPI-TYP-STRING Appears in messages indicating difficulty opening another process. It describes the function of that process (for example, ACS server). ZRSC-TKN-PROCESSNAME ZSPI-TYP-STRING Appears in messages indicating difficulty opening another process. It describes the name of that process. ZRSC-TKN-PROD-ID ZSPI-TYP-STRING Indicates a product number (for example, T9711D43).
EMS Token Values and Event Messages ZRSC-TKN-SUBSYSERROR RSC/MP-Specific Tokens ZSPI-TYP-INT Appears in messages warning of an error in an underlying communications subsystem (for example, TCP/IP or SPX). It indicates the error ID. ZRSC-TKN-SUBSYS-TYPE ZSPI-TYP-STRING Appears in messages that indicate some issue with an underlying communications subsystem (for example, NETBIOS, TCP/IP, and so on).
EMS Token Values and Event Messages Common Tokens Common Tokens Header token types that appear in all EMS-formatted messages logged by the TDP are listed next. The description and format of each of these token types is available in the appropriate HP manuals.
EMS Token Values and Event Messages Event Messages Event Messages The event messages that are logged in EMS format are listed below. Each description includes the event identifier, the text template, and the tokens included as part of the event. ZRSC-EVT-ACS-INV-CONFIG ACS::ACS object not started due to an invalid configuration. This message IS highlighted.
EMS Token Values and Event Messages Event Messages ZRSC-EVT-BACKUP-CPUDOWN TDP:Backup stopped; backup CPU has failed. This message IS highlighted. RSC/MP-specific tokens present:ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-CPU-ID ZRSC-EVT-BACKUP-CPUUP TDP:Backup CPU has been restored. This message IS NOT highlighted. RSC/MP-specific tokens present:ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-CPU-ID ZRSC-EVT-BACKUP-FAILED TDP:Backup process in CPU stopped unexpectedly. This message IS highlighted.
EMS Token Values and Event Messages Event Messages ZRSC-EVT-BACKUP-TAKEOVER TDP:Takeover by backup in CPU . This message IS NOT highlighted. RSC/MP-specific tokens present:ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-CPU-ID ZRSC-EVT-INV-TAG ACS::ACS object received a message with an invalid tag. This message IS highlighted. RSC/MP-specific tokens present:ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-OBJECT-NAME ZRSC-EVT-LOG-FS-ERROR TDP:File system error occurred on log .
EMS Token Values and Event Messages ZRSC-EVT-LOG-STOPPED TDP:Log recording to has stopped. This message IS NOT highlighted. RSC/MP-specific tokens present:ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-FILENAME ZRSC-EVT-MON-ACCESSKEY-EXPIRED TDP:The current DEMO TDP has expired. This message IS highlighted. RSC/MP-specific tokens present:ZRSC-TKN-OBJECT-TYPE ZRSC-EVT-MON-EXPIRATION-INFO TDP:The current DEMO TDP expires in days OR TDP:The current DEMO TDP expires today.
EMS Token Values and Event Messages Event Messages ZRSC-EVT-MON-SHUTDOWN-STARTED TDP:Starting SHUTDOWN. This message IS highlighted. RSC/MP-specific tokens present:ZRSC-TKN-OBJECT-TYPE ZRSC-EVT-MON-STARTED TDP: - - Started by user . This message IS NOT highlighted. RSC/MP-specific tokens present:ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-PROD-NAME ZRSC-TKN-PROD-ID ZRSC-TKN-USERNAME ZRSC-EVT-OBJECT-ABORTED :: Object aborted. This message IS NOT highlighted.
EMS Token Values and Event Messages Event Messages ZRSC-EVT-OBJECT-BADMSG-NAME :: Message format error ... Path: , Type: . This message IS NOT highlighted. RSC/MP-specific tokens present: ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-OBJECT-NAME ZRSC-TKN-COMM-PATHNAME ZRSC-TKN-TDM-MESSAGE-TYPE ZRSC-EVT-OBJECT-BADMSG-NUMBER ::Message format error ... Socket: , Type: . This message IS NOT highlighted.
EMS Token Values and Event Messages Event Messages ZRSC-EVT-OBJECT-EXCESS-RETRIES
EMS Token Values and Event Messages Event Messages ZRSC-EVT-OBJECT-OPEN-ERROR ::File system error occurred while attempting to open . This message IS highlighted. RSC/MP-specific tokens present:ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-OBJECT-NAME ZRSC-TKN-FILESYS-ERROR ZRSC-TKN-PROCESS-FUNCTION ZRSC-TKN-PROCESS_NAME ZRSC-EVT-OBJECT-RESTARTED :: Object re-start in seconds.
EMS Token Values and Event Messages Event Messages ZRSC-EVT-OBJECT-STOPPING :: Object stopping. This message IS NOT highlighted. RSC/MP-specific tokens present:ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-OBJECT-NAME ZRSC-EVT-OBJECT-SUBSYS-ERROR :: error occurred during a attempt. This message IS highlighted.
EMS Token Values and Event Messages Event Messages ZRSC-EVT-OBJECT-TABLE-ERROR ::State table error ... Event: , Action: , State: . This message IS highlighted. RSC/MP-specific tokens present:ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-OBJECT-NAME ZRSC-TKN-EVENT-ID ZRSC-TKN-ACTION-ID ZRSC-TKN-STATE-ID ZRSC-EVT-PICCOLO-LIC-ERROR PIPE:
EMS Token Values and Event Messages Event Messages ZRSC-EVT-RECEIVEDEPTH-CRITICAL TDP::Receive Depth critically low of slots in use. Some operations will be suspended. This message IS highlighted. RSC/MP-specific tokens present: ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-OBJECT-NAME ZRSC-TKN-RESOURCE-COUNT ZRSC-TKN-RESOURCE-COUNT ZRSC-EVT-RECEIVEDEPTH-NORMAL TDP::Receive Depth now adequate of slots in use.
EMS Token Values and Event Messages Event Messages ZRSC-EVT-TERM-PVIOLATION TERM:
EMS Token Values and Event Messages Event Messages ZRSC-EVT-TERM-UMS-INV-SIZE TERM::Unsolicited message rejected, I/O Type is , Invalid size . This message IS highlighted. RSC/MP-specific tokens present ZRSC-TKN-OBJECT-TYPE ZRSC-TKN-OBJECT-NAME ZRSC-TKN-IO-TYPE ZRSC-TKN-REASON ZRSC-TKN-MESSAGE-SIZE ZRSC-EVT-TERM-UMS-NOTSENT TERM:
EMS Token Values and Event Messages HP NonStop Remote Server Call (RSC/MP) Messages Manual — 522359-006 7- 20 Event Messages
Index A Application program interface (API) messages 3-1 B T Tokens 7-1, 7-7 U Unsolicited Message Service (UMS) messages 5-1 Base value, messages 1-1 E Event Management Service (EMS) event messages 7-7 tokens 7-1 H Header token types 7-6 Host system messages 2-1 M Messages base value 1-1 EMS 7-1 extension 1-2 format of 2-1 from host system 2-1 locating description 1-1 types of 1-1 UMS 5-1 P Pathsend messages 4-1 Piccolo messages 6-1 R RSC.
