HPE NonStop Remote Server Call (RSC/MP) Messages Manual

Transcription

1 HPE 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 HPE NonStop host and on RSC/MP workstations. Message descriptions include their cause, effect, and recovery procedures. Product Version RSC/MP R 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.09 and all subsequent J-series RVUs until otherwise indicated by its replacement publication. Part Number Published P October 2018

2 Document History Part Number Product Version Published RSC/MP R6.1 March RSC/MP R6.2 June RSC/MP R6.3 September RSC/MP R7.0 September RSC/MP R7.1 September RSC/MP R7.2 June RSC/MP R7.3.2 April P RSC/MP R7.3.7 RSC/MP R March 2012 October 2018

3 HPE NonStop Remote Server Call (RSC/MP) Messages Manual Glossary Index Examples Figures Tables What s New in This Manual iii Manual Information iii New and Changed Information 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 Messages Reported From the Host 3. API Messages 4. Pathsend Messages 5. UMS Messages 6. Piccolo Messages 7. EMS Token Values and Event Messages Index Token Definitions 7-1 RSC/MP-Specific Tokens 7-1 Common Tokens 7-6 Event Messages 7-7 Examples Figures

4 Hewlett Packard Enterprise P i

5 Contents Tables Tables Ta ble 1-1. Types of RSC/MP Messages 1-1 Ta ble 1-2. Base Values of RSC/MP Messages Reported on the Workstation 1-2 Ta ble 4-1. Pathsend Messages 4-1 ii

6 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 HPE NonStop host and on RSC/MP workstations. Message descriptions include their cause, effect, and recovery procedures. Product Version RSC/MP R 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.09 and all subsequent J-series RVUs until otherwise indicated by its replacement publication. Part Number Published P October 2018 Document History Part Number Product Version Published RSC/MP R6.1 March RSC/MP R6.2 June RSC/MP R6.3 September RSC/MP R7.0 September RSC/MP R7.1 September RSC/MP R7.2 June RSC/MP R7.3.2 April RSC/MP R7.3.7 March 2012 New and Changed Information This manual has the following changes for this RVU: Version number has been updated. Changed ACS error message 7108 to 7008 in Section 2, Messages Reported From the Host and updated the Recovery details. Added Pathsend message 911 in Section 4, Pathsend Messages. iii

7 What s New in This Manual New and Changed Information iv

8 About This Manual The HPE 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. Section 2, Messages Reported From the Host, describes the messages reported from the NonStop host. Section 3, API Messages, lists the workstation messages in numerical order and provides information about the type, severity, cause, effect, and recovery. Section 4, Pathsend Messages, lists the Pathsend messages that you can encounter while using RSC/MP. Section 5, UMS Messages, describes the Unsolicited Message System (UMS) messages that can be returned in the ncode parameter of the UMS header. Section 6, Piccolo Messages, describes the Piccolo messages. Section 7, EMS Token Values and Event Messages, provides information about the token values that can be used with the Event Management Service (EMS) and lists the event messages. Audience Requirements This manual is intended for application developers who use RSC/MP to create and maintain RSC/MP applications. These users must be familiar with: Programming in one of the supported workstation environments Writing applications using an API Using C or COBOL programming languages Designing and developing Pathway/TS applications Related Manuals The RSC/MP documentation set includes this manual and the following two manuals: Remote Server Call (RSC/MP) Installation and Configuration Guide Remote Server Call (RSC/MP) Programming Manual v

9 About This Manual Notation Conventions You can find detailed information about other NonStop system components in the appropriate HPE 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. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LIGHTS [ ON ] [ OFF ] [ SMOOTH [ num ] ] K [ X D ] address-1 { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON OFF } Vertical line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF ON SAVEABEND } vi

10 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 <error code> 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. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [, new-value ]... [ - ] { }... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( filename ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must enter as shown. For example: "[" repetition-constant-list "]" Item spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In the following example, there are no spaces permitted between the period and any other items: $process-name.#su-name Line spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] CONTROLLER [, attribute-spec ]... vii

11 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. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list might be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LDEV ldev [ CU %ccu CU %... ] UP [ (cpu,chan,%ctlr,%unit) ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list might be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LBU { X Y } POWER FAIL process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } Vertical line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK Failed } For example, this host error message contains two sets of alternatives, and reports one item from each set: <'Fatal' 'Unexpected'> file system error <error code> occurred during a <'ADD_NAME' 'LISTEN' 'RECEIVE_ANY' 'SEND'> attempt. The error message that you see contains this information: Fatal or Unexpected viii

12 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: % %B %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. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE). The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. ix

13 About This Manual Change Bar Notation x

14 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. Types of RSC/MP Messages Message Type Messages reported from the host Messages reported on the workstation * RSC/MP API Pathsend UMS Piccolo EMS Source Section 2, Messages Reported From the Host Section 3, API Messages through Section 7, EMS Token Values and Event Messages Section 3, API Messages Section 4, Pathsend Messages Section 5, UMS Messages Section 6, Piccolo Messages Section 7, EMS Token Values and Event Messages * For more information about workstation message return codes, subsystem error codes, extended error codes, device messages, and recovery from data communications failures, see the Remote Server Call (RSC/MP) Programming Manual. Workstation Message Numbers RSC/MP provides error and informational messages on the workstation from the Transaction Delivery Process (TDP) on the NonStop host. To interpret a message, you must know the message number. A typical message contains a message number and extension; these are coded in both decimal and hexadecimal: Error ( Hex) To find the description of a message, first look at its hex number: for example, This number is composed of a base value of 2000 plus the hex value of 385 (385 is equivalent to a decimal number 901). The base number 2000 indicates that this is a Pathsend message. Ta ble 1-2 shows the base values for all the types of RSC/MP messages. 1-1

15 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. Section 7, EMS Token Values and Event Messages The extension is the number after the hyphen and can contain a message code reported from a subsystem. For example, Pathsend messages have extended error numbers. Look up the extended error code in the appropriate document (see Documentation Sources in Table 1-2). 1-2

16 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. process-name The name of the process reporting the message. object-type object-name msg-id msg-text The type of TDP object: for example, PIPE or TERM. The name of the TDP object, as shown in the RSC.INI file. The internally generated numeric message ID. (This message is for HPE use only.) The text of the message. For example, this message displays message number 2803, which indicates that the TERM object in the TDP, named TERM05, has stopped: :30:13 TDP:$TDPA:TERM:TERM05:2803 TERM stopped. Finite state machine: action: <action>, state: <state>. Cause. An internal programming error has been detected. Recovery. This message is informational only. Backup started in CPU <cpu>. Cause. The backup process has been initiated in the specified CPU. 2-1

17 Messages Reported From the Host Takeover by backup in CPU <cpu number>. 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. Failure starting backup in CPU <cpu number>; <err-num> - <err-num> from NEWPROCESS. Cause. The attempt to initiate the backup process terminated with the specified error. See the Guardian Procedure Errors and Messages Manual for more information. Effect. The attempt to start the backup was abandoned. Recovery. Examine the error code values associated with the NEWPROCESS call and take appropriate action. Backup process in CPU <cpu> 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. Primary process in CPU <cpu> abended. Cause. A processing error occurred that caused the process to abend. Effect. The backup process will attempt 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 HPE Global Customer Support Center (GCSC). 2-2

18 Messages Reported From the Host Primary process stopped; primary CPU <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. Backup CPU <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. Backup stopped; backup CPU <cpu> has failed. Cause. The backup process stopped because of a failure of the backup CPU. Effect. No backup process runs until the CPU is restored. Recovery. Wait until the backup CPU is restored or move the backup process to an operational CPU. Backup process in CPU <cpu> stopped unexpectedly. Cause. The backup process has stopped unexpectedly. Effect. The TDP process is no longer backed up. Recovery. Determine the reason why the process stopped and restart the backup by using RSCCOM. 2-3

19 Messages Reported From the Host Backup process in CPU <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 HPE Global Customer Support Center (GCSC). Receive Depth critically low - <count> of <count> slots in use. Some operations will be suspended. Cause. TDP handling exceeding large amount of traffic. Effect. TDP operations will be suspended. Recovery. Restructure/Configure application to use multiple TDPs. Receive Depth now adequate - <count> of <count> slots in use. Suspended operations will be resumed. Cause. Previously suspended operations will operate properly. Log recording to <device name> has stopped. Cause. Log recording has stopped. 2-4

20 Messages Reported From the Host Log recording has been started to <device name>. Cause. Log recording has been started to the specified device. File system error <error code> occurred on log <device name>. Log recording has been stopped. Cause. A Guardian file system error has occurred on the log device. Effect. Log recording stops. Recovery. Determine and correct the cause of the error and restart log recording. MONITOR state table error... Event <event id>, Action <action id>, State <state id>. Cause. A Guardian file system error has occurred on the log device. Effect. Log recording stops. Recovery. Determine and correct the cause of the error and restart log recording. <TDP> - <product number> - Started by user <user name>. Cause. The TDP process has been started. 2-5

21 Messages Reported From the Host SHUTDOWN completed. Cause. The current DEMO TDP has expired. Recovery. Contact your HPE Global Customer Support Center (GCSC). Starting SHUTDOWN. Cause. The current DEMO TDP has expired. Effect. The TDP will be shut down shortly. Recovery. Contact your HPE Global Customer Support Center (GCSC). The current DEMO TDP expires in <n> days. Cause. The current DEMO TDP will expire in the number of days indicated. Recovery. This message is informational. It applies only to a demo TDP. No action is required. The current DEMO TDP has expired. Cause. The current DEMO TDP has expired. Effect. The TDP will be shut down shortly. Recovery. Contact your HPE Global Customer Support Center (GCSC). 2-6

22 Messages Reported From the Host Connection <connect id> established via <object type> <object name> at duplex level <duplex level>. Workstation type is <workstation type>. Cause. Workstation connection was established. TERM deleted. Cause. A terminal was deleted. Effect. The terminal no longer exists. Connection <connect id> from <object type> <object name> terminated. Cause. A workstation connection was terminated. [<session id>] UMS check not completed, cause: <cause description>, result <result code>-<extended result code>, ( <result description> ). Cause. A workstation RscUmsCheck request could not be completed for the specified reason. 2-7

23 Messages Reported From the Host [<session id>] UMS check completed, result <result code>- <extended result code> (<result description>), message size <count>, I/O handle <I/O handle>, UMS queue depth is now <count>. Cause. A workstation RscUmsCheck request was completed. [<session id>] I/O check not completed, cause: <cause description>, result <result code>-<extended result code> (<result description>), I/O handle <I/O handle>. Cause. A workstation RscIoCheck request could not be completed for the specified reason. [<session id>] I/O check completed, result <result code>- <extended result code> (<result description>), reply size <count>, I/O handle <I/O handle>. Cause. A workstation RscIoCheck request was completed. [<session id>] <I/O type> I/O completed, result <result code>-<extended result code> (<result description>), reply size <count>, I/O handle <I/O handle>, I/O tag <I/O tag>. Cause. An I/O request to a server has completed. 2-8

24 Messages Reported From the Host [<session id>] Level <level> UMS completion sent, I/O handle <handle>. Cause. The workstation has been notified that an unsolicited message has been received. [<session id>] Level <level> I/O completion sent, I/O handle <handle>. Cause. The workstation has been notified that an I/O completion has occurred. [<session id>] UMS completion confirmed, I/O handle <handle>. UMS queue depth is now <count>. Cause. The workstation has confirmed that an unsolicited message has been received. [<session id>] I/O completion confirmed, I/O handle <handle>. Cause. The workstation has confirmed that an I/O completion has occurred. 2-9

25 Messages Reported From the Host [<session id>] UMS reply completed, result <result code>- <extended result code>,(<result resolutions>) reply size <count>, I/O handle <handle>, UMS depth is now <count>. Cause. The workstation replied to an unsolicited message. Starting <'Pathway' 'IDS'> session terminal in Pathway <process name> using TCP <tcp name>, TERM <term name>, TCLPROG <file name>, initial program unit <program id>. Cause. A Pathway terminal is being started to support a workstation session. [<session id>] <'Interprocess'> session established. Cause. A workstation session of the specified type has been established. [<session id>] Unable to start terminal <term name> in Pathway <process name>, <subsystem type> error <result code>- <extended result code>. Cause. The Pathway terminal associated with the session could not be started due to the specified error. Effect. The workstation RscBeginSession request fails. Recovery. Examine the Pathway configuration to determine the cause of the error before restarting the workstation application. 2-10

26 Messages Reported From the Host [<session id>] Unable to start terminal <term name> in Pathway <process name>, <count> 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. [<session id>] Session suspended pending deletion of terminal <term name> in Pathway <pathway name>. Cause. A workstation has requested termination of a Pathway or IDS session. The session is suspended while the Pathway terminal supporting the session is deleted. Effect. The session remains outstanding in a suspended state until the Pathway terminal is deleted. [<session id>] Session terminated. Cause. A workstation session was terminated. [<session id>] Session will be terminated due to an unexpected Pathway terminal failure. Cause. The Pathway terminal associated with the session sent an unexpected CLOSE message to the TDP. Effect. The session is terminated. Recovery. This may be the result of a Pathway terminal abort or a TCP failure. Examine the Pathway to determine the cause before restarting the workstation application. 2-11

27 Messages Reported From the Host [<session id>] 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. TERM created, TERM_TEMPLATE=<template name>, TERM_NAME=<term name>. Cause. A dynamic TERM object was created using the specified parameters. [<session id>] Interprocess I/O started, process <process name>, request size <count>, reply size <count>, I/O handle <I/O handle>, I/O tag <I/O tag>, TMF option <option value>. Cause. An interprocess I/O has been initiated. [<session id>] Pathsend I/O started, serverclass <server class name>, pathmon name <process name>, request size <count>, reply size <count>, I/O handle <I/O handle>, I/O tag <I/O tag>, TMF option <option value>. Cause. A Pathsend I/O has been initiated. 2-12

28 Messages Reported From the Host [<session id>] IDS I/O started, request size <count>, reply Size <count>, I/O handle <I/O handle>, I/O tag <I/O tag>. Cause. An IDS I/O has been started. [<session id>] Server opening, name <name>, file handle <handle>, I/O tag <I/O tag>, I/O index <index>. Cause. A server is being opened. [<session id>] Server open already pending, name <name>, file handle <handle>, I/O index <index>. Cause. While attempting to open a server, an open was already in progress. [<session id>] Server successfully opened, name <name>, file handle <handle>, I/O tag <tag>, I/O index <index>. Cause. A server was successfully opened by the TDP. [<session id>] Server open failed, name <name>, file handle <handle>, I/O tag <tag>, I/O index <index>, Result <result>. Cause. An attempt by the TDP to open a server has failed. 2-13

29 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. [<session id>] Server already open, name <name>, file handle <handle>, I/O index <index>. Cause. The TDP found a server already open. [<session id>] Transaction <transaction id> aborted by session cleanup. Cause. A transaction that was still outstanding at the time of session termination was aborted. Effect. The transaction will not be processed. [<session id>] Implicit begin transaction failed, transaction <transaction id>, TMF Error <guardian transaction error>. Cause. An implicit begin transaction request failed. Effect. The workstation RscWrite or RscWriteRead request fails. Recovery. Determine the cause of the error and correct it before restarting the workstation application. [<session id>] Implicit begin transaction succeeded, transaction id <transaction id>. Cause. An implicit begin transaction request succeeded. 2-14

30 Messages Reported From the Host [<session id>] Implicit resume transaction failed, transaction id <transaction id>, TMF Error <guardian transaction 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. [<session id>] Implicit resume transaction succeeded, transaction id <transaction id>. Cause. An outstanding transaction was resumed prior to initiating an interprocess I/O. [<session id>] Implicit begin transaction failed, transaction id <transaction id> already in progress. Cause. An implicit begin transaction was requested while a transaction was already outstanding. Effect. The workstation RscWrite or RscWriteRead request fails. Recovery. Correct the workstation application program. [<session id>] Implicit end transaction failed, transaction id <transaction id>, TMF Error <guardian transaction error>. Cause. An outstanding transaction could not be ended at interprocess I/O completion because of a TMF error. Effect. The workstation RscWrite or RscWriteRead request returns an error. Recovery. Determine the cause of the error and correct it before restarting the workstation application. 2-15

31 Messages Reported From the Host [<session id>] Implicit end transaction succeeded, transaction id <transaction id>. Cause. An outstanding transaction was ended at interprocess I/O completion. [<session id>] Implicit end transaction failed, no transaction in progress. Cause. An implicit end transaction request failed because no transaction was in progress. Effect. The RscWrite or RscWriteRead request returns an error. Recovery. Correct the workstation application program. [<session id>] Implicit end transaction rejected, transaction id <transaction id> reply code <value> is out of success range <low value> - <high value>. Cause. An implicit end transaction could not be completed because the reply code was out of the application-specified success range. Effect. The workstation RscWrite or RscWriteRead request returns an error. Recovery. Recovery is specific to your application. [<session id>] Explicit begin transaction failed, transaction id <transaction id> already in progress. Cause. An RscBeginTransaction request could not be completed because a transaction is already in progress. Effect. The workstation request fails. Recovery. Correct the workstation application program. 2-16

32 Messages Reported From the Host [<session id>] Explicit begin transaction failed, TMF Error <guardian transaction 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. [<session id>] Explicit begin transaction succeeded, transaction id <transaction id>. Cause. A workstation RscBeginTransaction request has succeeded. [<session id>] Explicit end transaction failed, no transaction in progress. Cause. A workstation RscEndTransaction request failed because no transaction was in progress. Effect. The workstation request fails. Recovery. Correct the workstation application program. [<session id>] Explicit end transaction failed, transaction id <transaction id>, TMF Error <guardian transaction error>. Cause. A workstation RscEndTransaction request failed 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. 2-17

33 Messages Reported From the Host [<session id>] Explicit end transaction succeeded, transaction id <transaction id>. Cause. A workstation RscEndTransaction request succeeded. [<session id>] 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. Correct the workstation application program. [<session id>] Explicit abort transaction failed, transaction id <transaction id>, TMF Error <guardian transaction error>. Cause. A workstation RscAbortTransaction request failed 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. [<session id>] Explicit abort transaction succeeded, transaction id <transaction id>. Cause. A workstation RscAbortTransaction request succeeded. 2-18

34 Messages Reported From the Host [<session id>] Unsolicited message queued, I/O type is <type>, message size <count>, reply size <count>, I/O handle <handle>, UMS queue depth is now <count>. Cause. An unsolicited message was queued. Term Memory <type>, Size <size>, address <addr>, state <state>, event <evnt>, MemInUse <mem>. Cause. The TERM object has allocated the indicated memory block. Term Memory <type>, address <addr>, state <state>, event <evnt>, MemInUse <mem>. Cause. The TERM object has freed the indicated memory block. [<session id>] Attempt to access <process name> by user <user id> ALLOWED. Cause. The ACS server has allowed access to a named server. 2-19

35 Messages Reported From the Host [<session id>] Attempt to access pathmon <process name>, serverclass <server class name> by user <user id> ALLOWED. Cause. The ACS Server has allowed access to a PATHSEND serverclass or a PATHWAY serverclass through the IDS router. [<session id>] Attempt to access <process name> by user <user id> REJECTED. Cause. The ACS server has rejected access to a named server. Effect. A write or writeread request will not be processed. Recovery. This message may result from an inappropriate attempt by a client to access a server for which it does not have access. [<session id>] Attempt to access pathmon <process name>, serverclass <server class name> by user <user id> REJECTED. Cause. The ACS server has rejected access to a PATHSEND serverclass or a PATHWAY serverclass through the IDS router. Effect. A write or writeread request will not be processed. Recovery. This message may result from an inappropriate attempt by a client to access a server for which it does not have access. TERM state table error... Event <event id>, Action <action id>, State <state id>. Cause. An internal program error 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 HPE Global Customer Support Center (GCSC). 2-20

36 Messages Reported From the Host 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. TERM 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. TERM aborted. Cause. The operational state of the object has changed to ABORTED. See the RSCCOM ABORT command in the Remote Server Call (RSC/MP) Installation and Configuration Guide for more information. File system error 2805 occurred while attempting to open the Access Control Server. Cause. A Guardian file system error occurred while attempting to open the Access Control Server for the TERM object. Effect. The TERM object cannot be started. Recovery. Determine the cause of the file system error, correct the situation, and restart the TERM object. 2-21

37 Messages Reported From the Host TERM stopping. Cause. The operational state of the object has changed to STOPPING. Protocol violation detected. A message was received which could not be interpreted. Data: [ <message 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. This problem indicates a serious network hardware or protocol problem. Report the problem to your network administrator. [<session id>] Unsolicited message rejected, UMS queue limit of <count> entries has been reached. Cause. An unsolicited message was rejected because too many unsolicited messages are outstanding. This error is sent back to the sender of a UMS WRITE or WRITEREAD call. 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. [<session id>] Unsolicited message rejected, I/O Type is <type>, Error 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. 2-22

38 Messages Reported From the Host Unsolicited message rejected, I/O Type is <type>, Invalid <reqrep> size <size>. Cause. An unsolicited message was rejected because of invalid size less than 0 or greater than 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. COM state table error... Event <event id>, Action <action id>, State <state id>. Cause. An internal program error 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 HPE Global Customer Support Center (GCSC). *** Error 3002: The TDP process must be named. Cause. An attempt was made to start the TDP process without a Guardian process name. Effect. The TDP process stops. Recovery. Supply a process name by using the NAME option in the RUN command that is used to start the TDP. 2-23

39 Messages Reported From the Host *** Error 3003: Backup CPU <cpu number> 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. *** Error 3004: The specified backup CPU number is not valid. Cause. The specified backup CPU number is not syntactically correct. Valid CPU numbers range from 0 to 15 inclusive. 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 within the valid range. *** Error 3005: Backup CPU <CPU number> is down or not installed. Cause. The specified backup CPU is either not installed in the system or is not operational. 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 the number of a CPU that is installed and operational. 2-24

40 Messages Reported From the Host *** Error 3006: The backup process is already running in CPU <cpu number>. 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. *** Warning 3007: The PATHSENDENABLE command is obsolete. Cause. The PATHSENDENABLE command is no longer supported. Pathsend availability is now determined programmatically. *** Warning 3008: The PATHSENDDISABLE command is obsolete. Cause. The PATHSENDDISABLE command is no longer supported. Pathsend availability is now determined programmatically. *** Error 3010: The command '<command>' is not recognized. Cause. An invalid command was issued. Effect. The command is rejected. Recovery. See the Remote Server Call (RSC/MP) Installation and Configuration Guide for a list of valid RSCCOM commands. 2-25

41 Messages Reported From the Host *** Error 3011: The '<command>' 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. *** Error 3012: The object '<object type>' is not recognized. Cause. The command contains an unrecognized object type. Effect. The command is rejected. Recovery. Supply a valid object specifier. *** Error 3013: An object name must be alphanumeric and start with an alphabetic character. Cause. The command contains an invalid object name specification. Effect. The command is rejected. Recovery. Supply a valid object name. *** Error 3014: An object name must be supplied. Cause. The command requires an object name. Effect. The command is rejected. Recovery. Supply the name of an existing object. *** Error 3015: Object '<object name>' already exists. Cause. An object already exists with the specified name. Effect. The command is rejected. Recovery. Supply a unique object name. 2-26

42 Messages Reported From the Host *** Error 3016: <object type> object '<object name>' has not been configured. Cause. The specified object has not been configured. Effect. The command is rejected. Recovery. Supply the name of an existing object. *** Error 3017: There is no log recording device currently open. Cause. A LOGCLOSE command was issued when no log recording device was opened. Effect. The command is rejected. *** Error 3018: You must supply the name of an existing log device as the log record destination. Cause. A LOGOPEN command was issued with no destination name. Effect. The command is rejected. Recovery. Supply a valid log recording destination. *** Error 3019: File system error <error code> occurred while attempting to open log device <device name>. Cause. A Guardian file system error occurred while attempting to open the log recording device. Effect. The command is rejected. Recovery. Determine the cause of the error and correct it before restarting the workstation application. 2-27

43 Messages Reported From the Host *** Error 3020: Only specific objects may be ALTERed. Cause. An ALTER command was issued without a specific object name. The command ALTER <object> * is not valid. Effect. The command is rejected. Recovery. Supply the name of an existing object. *** Error 3021: No <object type> objects have been configured. Cause. An object-specific command was issued when no objects of that type were configured. Effect. The command is rejected. Recovery. Supply an object type for which one or more objects have been configured. *** Warning 3022: The TDPSTATUS command is obsolete and has been replaced by the STATUS TDP command. Cause. The TDPSTATUS command is no longer supported. Effect. The STATUS TDP command is executed. Recovery. This message is informational only. *** Error 3023: No value for '<attribute>' has been supplied. Cause. The attribute requires a value. Effect. The command is rejected. Recovery. Supply a valid value for the attribute. 2-28

44 Messages Reported From the Host *** Error 3024: '<attribute>' 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. *** Error 3025: '<attribute>' must be at least <minimum value> but not more than <maximum value>. Cause. The value supplied for the attribute is out of the valid range. Effect. The command is rejected. Recovery. Supply a value in the valid range. *** Error 3026: '<attribute>' must be YES or NO. Cause. The supplied attribute value must be YES or NO. Effect. The command is rejected. Recovery. Supply YES or NO for the attribute value. *** Warning 3027: Command output has been truncated to <n> bytes. Cause. RSCCOM command output is limited to approximately 30,000 bytes. The result of the command exceeded that size. Effect. Command processing is terminated. Recovery. Issue the command in such a way that the output size falls within the specified limit. 2-29

45 Messages Reported From the Host *** Error 3028: <object type> object names are limited to <count> characters. Cause. The specified object name is too long. Effect. The command is rejected. Recovery. Supply a valid object name. *** Error 3029: The <object type> object does not support '<request type>' requests. Cause. The object does not support the specified request type. Effect. The command is rejected. Recovery. See the Remote Server Call (RSC/MP) Installation and Configuration Guide for a list of valid request types for each object. *** Warning 3030: <object type> <object name> is currently stopping or stopped. Cause. An attempt was made to stop an object that is already stopping or stopped. Effect. The command is rejected. *** Warning 3031: <object type> <object name> must be stopped before being deleted. Cause. An attempt was made to delete an object that is not stopped. Effect. The command is rejected. Recovery. Stop the object and reissue the DELETE command. 2-30

46 Messages Reported From the Host *** Warning 3032: <object type> <object name> cannot be stopped because <count> connection(s) are outstanding. Cause. An attempt was made to stop an object that has connections outstanding. Effect. The command is rejected. Recovery. Ensure that all outstanding connections are terminated, and reissue the command or ABORT the object. *** Warning 3033: <object type> <object name> cannot be stopped because <count> session(s) are outstanding. Cause. An attempt was made to stop an object that has sessions outstanding. Effect. The command is rejected. Recovery. Ensure that all outstanding sessions are terminated, and reissue the command or abort the object. *** Warning 3034: <object type> <object name> is currently started. Cause. An attempt was made to start an object that is already started. Effect. The command is rejected. *** Error 3035: '<selector>' is not a valid <object type> LOGEVENTS selector. Cause. The specified LOGEVENTS selector is not valid for the specified object type. Effect. The command is rejected. Recovery. See the section on Message Handling in the Remote Server Call (RSC/MP) Programming Manual for a list of valid selectors for each object type. 2-31

47 Messages Reported From the Host *** Error 3036: A <object type> object must be stopped before its '<attribute>' attribute may be ALTERed. Cause. The object must be in a stopped state before you can alter the specified attribute. Effect. The command is rejected. Recovery. Stop the object and reissue the command. *** Error 3038: File system error <error code> occurred while attempting to open OBEY file <file name>. Cause. A Guardian file system error occurred while attempting to open the specified OBEY file. Effect. The command is rejected. Recovery. Determine the cause of the error and reissue the command if appropriate. *** Error 3039: File system error <error code> occurred while attempting to open TDP process <process name>. Cause. A Guardian file system error occurred while attempting to open the specified TDP process. Effect. The command is rejected. Recovery. Determine the cause of the error and reissue the command if appropriate. *** Error 3040: There is no TDP process open. Cause. The command requires communication with a TDP process but none is open. Effect. The command is rejected. Recovery. Open a TDP process with the OPEN command and reissue the command if appropriate. 2-32

48 Messages Reported From the Host *** 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. *** Error 3042: Process <process number> is not a TDP or is a TDP which is not compatible with this release of RSCCOM. Cause. The process supplied in the OPEN command is not a TDP process, or it is a TDP that is not compatible with this version of RSCCOM. Effect. The command is rejected. Recovery. Determine the correct name of the TDP process you want to manage and reissue the OPEN command. *** Error 3043: File system error <error code> occurred while communicating with TDP process <process name>. Cause. A Guardian file system error occurred while communicating with the TDP. Effect. The command fails and the TDP is closed. Recovery. Determine the cause of the error and reopen the TDP if appropriate. *** Error 3044: The OPEN command requires a valid process name as its argument. Cause. No process name argument was supplied with the OPEN command. Effect. The command is rejected. Recovery. Reissue the command with a valid TDP process name. 2-33

49 Messages Reported From the Host *** 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. *** Error 3046: Attribute <name> is not valid for this object type. Cause. An object SET or ALTER command was issued with an attribute that is not valid for the specified object. Effect. The command is rejected. Recovery. See the Remote Server Call (RSC/MP) Installation and Configuration Guide for a list of valid attributes for each object and reissue the command if appropriate. *** Warning 3047: TERM <term name> is configured as a template. Its object state cannot be altered. Cause. A START, STOP, or ABORT command was issued on a TERM object that is configured as a template. Effect. The command is rejected. *** Error 3049: <attribute name> is limited to <count> characters. Cause. The specified attribute name is too long. Effect. The command fails. Recovery. Reissue the command with a valid attribute name. 2-34