TS/MP Supplement for Limits Relief Next Version and Copyright Information Published April 2005 Table of Contents What's New in This Guide About This Guide Notation Conventions Hypertext Links General Syntax Notation Notation for Messages 1. Overview of New and Changed Information for TS/MP Overview of TS/MP 2.1 New Pathsend Limits New ACS Subsystem Changes to LINKMON (ROUT) Process Compatibility With TS/MP 2.0 2. Changes to TS/MP 2.
Subsystem Control Facility (SCF) Changes to TS/MP 2.0 Documentation TS/MP System Management Manual TS/MP Pathsend and Server Programming Manual TS/MP Management Programming Manual 3. Migrating Applications to TS/MP 2.1 TS/MP 2.1 Environment Similarities TS/MP 2.1 Environment Differences 4. Introduction to the ACS Subsystem ACS Subsystem Support for TS/MP 2.
Restarting ACS Subsystem Processes in a CPU Restarting the Subsystem 1. Stop the Pathsend Requesters 2. Start $ZACS 3. Start the ACS Subsystem 4. Restart the Pathsend Requesters Stopping the Subsystem 1. Stop the Pathsend Requesters 2. Stop the ACS Subsystem 3. Stop $ZACS 4. Delete the $ZACS Process Configuration 7.
Descriptions of Pathsend Errors 9. SCF Error Messages If You Have to Call Your Service Provider SCF Error Messages 10. ACS EMS Event Tokens ACS Subsystem Identifiers Event-Message SPI Format Listed Tokens Unlisted Tokens ACS Event Severity Levels EMS Messages 1000 through 1009 EMS Messages 1010 through 1019 EMS Messages 1020 through 1029 EMS Messages 1030 through 1039 EMS Messages 1040 through 1049 EMS Messages 1050 through 1059 EMS Messages 1060 through 1069 EMS Messages 1070 through 1071 A.
Next What's New in This Guide 528626.
What's New in This Guide Prev Next What's New in This Guide This is a new, supplemental manual. Information in this manual changes and enhances information in the TS/MP 2.0 manual set, which consists of the following manuals: TS/MP System Management Manual TS/MP Management Programming Manual TS/MP Pathsend and Server Programming Manual Prev TS/MP Supplement for Limits Relief 528626.
About This Guide Prev Next About This Guide Notation Conventions Hypertext Links General Syntax Notation Notation for Messages Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This attribute is described under the ADD command. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual.
Brackets enclose optional syntax items. For example: INFO [ , DETAIL ] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can 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.
"[" 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 this example, no spaces are permitted between the period and any other items: $process-name.
528626.
Chapter 1. Overview of New and Changed Information for TS/MP Prev Next Chapter 1. Overview of New and Changed Information for TS/MP Overview of TS/MP 2.1 New Pathsend Limits New ACS Subsystem Changes to LINKMON (ROUT) Process Compatibility With TS/MP 2.0 Overview of TS/MP 2.1 TS/MP 2.1 is intended solely for Pathsend users on S-series systems using TS/MP 2.0; it does not apply to SCOBOL users or TS/MP 3.0 users.
The major new and changed features are as follows: ● ● ● Applications ❍ No syntax changes to application configurations are required in PATHMON environments. However, you may want to make some configuration modifications for performance tuning. ❍ The TS/MP 2.1 Pathsend library replaces the TS/MP 2.0 Pathsend library. Although the two Pathsend libraries function similarly, they are internally different and cannot be used interchangeably.
New ACS Subsystem The ACS subsystem provides link management functions for applications using Pathsend requesters. For information about the ACS subsystem, see Chapter 4, Introduction to the ACS Subsystem. Changes to LINKMON (ROUT) Process In TS/MP 2.1, the functions performed by the TS/MP 2.0 LINKMON (or ROUT) process are performed by the ACS subsystem components. Messages formerly returned by the LINKMON (or ROUT) process are replaced by similar messages returned by the ACS subsystem components.
Chapter 2. Changes to TS/MP 2.0 Prev Next Chapter 2. Changes to TS/MP 2.0 Start ACS Subsystem Before PATHMON Configuration and Environment Limits PATHMON and PATHCOM Link Management System Management Interface Pathsend API Process Management Statistics Collection Error Handling Pathsend errors Event Management System (EMS) Subsystem Control Facility (SCF) Changes to TS/MP 2.
Buffer length Dialogs 32,767 bytes Maximum bytes for each server class send operation. 256 Maximum active dialogs for each requester. Approximate maximum active dialogs for each processor. The exact limit depends upon the total number of outstanding context-free sends at the time Dialogs 4045* the last dialog-begin call was issued. The exact limit also depends upon the utilization of the current process file segment (PFS) size; the limit may be higher. Approximate maximum concurrent links per processor.
PATHMON and PATHCOM There are no changes to the PATHCOM command interface. Although there are no operational changes to the SPI interface to PATHMON processes, there are some data changes, described in System Management Interface in this chapter. Link Management To provide transparent migration for TS/MP 2.0 applications, the ACS subsystem link management functions use the same program file name ($SYSTEM.SYSnn.ROUT) and process name ($ZLnn) used by TS/MP 2.0. However, because the contents of $SYSTEM.SYSnn.
● TS/MP 2.0: The SPI interface returns the TS/MP link manager process name $ZLnn. ● TS/MP 2.1: Link management is handled by both the ACS subsystem process broker ($ZPnn) and the redirector process ($ZLnn). Therefore, the SPI interface returns either of these process names, depending upon which process encounters the problem. This is particularly evident in the STATUS command. Pathsend API Figure 2.1. How Pathsend Requests Are Processed by the ACS Subsystem 1.
4. If the PATHMON process does not have a server process available and the maximum server processes has not yet been reached, the PATHMON process starts a server process. When the process broker acquires the server process from the PATHMON process, it creates the objects needed to control the link through the redirector process. 5. The local redirector process checks for security rights and configuration information.
Differences in statistical results should be minimal. Error Handling Pathsend errors Some TS/MP 2.0 errors are no longer generated but that does not cause compatibility problems. New errors generated by TS/MP 2.1 can easily be handled by applications and are highly unlikely to occur. The new errors always indicate that the transaction has not been processed and that the transaction can be aborted, which is standard for unhandled errors.
● broker process ($ZPnn). Section 12, FREEZE SERVER command: Remove the following sentence: If no incomplete or outstanding requests exist for any server in the server class, the PATHMON process immediately freezes the server class. Add the following sentence in its place: When all incomplete and outstanding requests are completed, the PATHMON process freezes the server class.
Chapter 3. Migrating Applications to TS/MP 2.1 Prev Next Chapter 3. Migrating Applications to TS/MP 2.1 TS/MP 2.1 Environment Similarities TS/MP 2.1 Environment Differences In general, all TS/MP2.0 applications that use Pathsend requesters and TS/MP 2.0 scripts (also called OBEY files) can run in a TS/MP 2.1 environment. However, to take advantage of new features and to understand slight differences in behavior, see the following topics. TS/MP 2.1 Environment Similarities ● No need to recompile.
SCF commands to start the ACS subsystem. See Restarting the Subsystem in Chapter 6. ● New Pathsend library. The TS/MP 2.1 Pathsend library replaces the TS/MP 2.0 Pathsend library. Although the two Pathsend libraries function similarly, they are internally different and cannot be used interchangeably. ● New SCF commands. The SCF interface includes a new set of commands to manage the configuration and operation of the ACS subsystem.
the error 905. However, TS/MP is aware of the waiting available link and gives that link without returning an error. HP recommends that you increase the number of links available in the server class configuration or retry the request. If you retry the request, it typically completes without an error unless there are no links to that server class in the CPU and none available from the PATHMON process. ● Changes to TS/MP server DELETEDELAY attribute.
Chapter 4. Introduction to the ACS Subsystem Prev Next Chapter 4. Introduction to the ACS Subsystem ACS Subsystem Support for TS/MP 2.1 ACS Subsystem Architecture Architecture Overview ACS Subsystem Components ACS Domains Security ACS Subsystem-Specific Security Features Sensitive and Nonsensitive SCF Commands ACS Subsystem Support for TS/MP 2.1 The Application Cluster Services (ACS) provides link-management functions for applications using Pathsend requesters on the NonStop server platform.
configuration subscriber, and redirector process in the CPU in which it resides and is, therefore, also tightly bound to those processes in that CPU. For purposes of simplicity, Figure 4-1 and Figure 4-2 show only one PATHMON and one PATHCOM process. However, a system can contain multiple PATHMON and PATHCOM processes, as well as multiple server classes and clients. Figure 4.1. ACS Subsystem Architecture: System View (Single NonStop System) Figure 4.2.
ACS Subsystem Components Domain Coordinator Process ($ZACS) The domain coordinator process is the ACS subsystem manager process. One instance of this process occurs in a system; it coordinates and manages the ACS domain resources configured for the subsystem. It also creates the initialization file (BCINI) which contains the ACS subsystem configuration. Process Broker Process ($ZPnn) The process broker manages links from TS/MP PATHMON processes for Pathsend requests.
link-management to obtain a server link from the process broker. After it verifies that the requester has the authority to perform a send operation to the specified server class, the redirector process performs the send operation. ACS Subsystem Product Module (ACSPM) The product module provides part of the ACS subsystem interface to the Subsystem Control Facility, shown in Figure 7-1 in Chapter 7. The program file for the ACSPM is installed in $SYSTEM.SYSTEM.ZACLSCF.
interface and SCF commands for the ACS subsystem. Prev Chapter 3. Migrating Applications to TS/MP 2.1 528626.001 Up Home Next Chapter 5.
Chapter 5. Installing and Configuring Prev Next Chapter 5. Installing and Configuring Plan your TS/MP 2.1 Installation 1. Install TS/MP 2.1 2. Start SCF 3. Configure the Domain Coordinator Process ($ZACS) 4. Start Domain Coordinator Process ($ZACS) 5. Configure the ACS Subsystem 6. Start the ACS Subsystem ($ZACS) 7. Start TS/MP PATHMON and Requesters Use the standard SUT-based utilities to install TS/MP 2.1.
Use the standard Distributed Systems Management/Software Configuration Manager (DSM/SCM) installation tool to install TS/MP 2.1, as documented in the softdoc. ACS components are automatically installed in $SYSTEM.SYSnn. 2. Start SCF This step starts the SCF management interface, which is typically located in the file $SYSTEM.SYSTEM.SCF. How to do it. Use the TACL RUN command interactively or in an OBEY file, as follows: 1> SCF After SCF is started, you can use the SETPROMPT command to change the prompt.
This attribute is required. DEFAULTVOL $SYSTEM.SYSnn specifies the physical location where the ACS software and the ACS subsystem configuration file (BCINI) is installed. This attribute is required. PRIMARYCPU primary-cpu specifies the processor on which the primary domain coordinator process is to be started. This attribute is required. STARTUPMSG "num" indirectly specifies a processor for the backup domain coordinator process, enclosed in double quotes (").
How to do it. Use the SCF START command interactively or in an OBEY file to start $ZACS in the local system, as follows: ASSUME PROCESS $ZZKRN START #ZACS The ACS domain coordinator process is started as $ZZKRN.#ZACS. The TACL name for the process is $ZACS. Use the SCF STATUS and INFO commands to obtain information about $ZACS, as follows: STATUS PROCESS $ZZKRN.#ZACS, DETAIL INFO PROCESS $ZZKRN.#ZACS, DETAIL 5.
START ACS $ZACS The START command starts the configuration subscriber, process broker, and redirector process in each processor in the system. When the configuration subscriber is successfully started, it identifies the associated log files and builds the internal configuration. Use the STATUS command to monitor the progress of the START command, as follows: STATUS ACS $ZACS If you use an OBEY file, include some delay time between the START command and subsequent SCF commands. 7.
Chapter 6. Managing the ACS Subsystem Prev Next Chapter 6. Managing the ACS Subsystem Modifying The Configuration Displaying Information Displaying ACS subsystem configuration Displaying ACS domain coordinator ($ZACS) name Displaying ACS subsystem and processor status Displaying ACS subsystem version Restarting ACS Subsystem Processes in a CPU Restarting the Subsystem 1. Stop the Pathsend Requesters 2. Start $ZACS 3. Start the ACS Subsystem 4. Restart the Pathsend Requesters Stopping the Subsystem 1.
1. Stop the Pathsend See the TS/MP System Management Manual. requesters. Use the STOP command. For detailed information about this command, 2. Stop the ACS see STOP in Chapter 7. For example: subsystem. STOP ACS $ZACS, FORCED Use the STATUS command. For detailed information about this 3. Verify the ACS command, see STATUS in Chapter 7. For example: subsystem is stopped. 4. Modify the subsystem configuration. 5. Start the ACS subsystem.
STATUS ACS $ZACS, DETAIL Displaying ACS subsystem version Use the SCF VERSION command to display the version number of the ACS subsystem. For detailed information about this command, see VERSION in Chapter 7. For example: VERSION ACS $ZACS, DETAIL Restarting ACS Subsystem Processes in a CPU Use the CONTROL command to restart ACS subsystem processes in one or more CPUs. Changes made with the CONTROL command modify the operational status of the ACS subsystem, not the ACS subsystem configuration.
3. Start the ACS Subsystem 1. Start the ACS subsystem. Use the SCF START command. For detailed information about this command, see START in Chapter 7. For example: START ACS $ZACS Use the SCF STATUS command. For detailed information about this command, see STATUS in 2. Verify the ACS subsystem is started. Chapter 7. For example: STATUS ACS $ZACS, DETAIL 4. Restart the Pathsend Requesters For information on starting Pathsend requesters, see the TS/MP System Management Manual.
3. Stop $ZACS 1. Check whether $ZACS is Use the SCF STATUS PROCESS command. For example: stopped. STATUS PROCESS $ZZKRN.#ZACS, DETAIL Use the SCF ABORT command interactively or in an OBEY file, as follows: 2. If $ZACS is running, abort it. ASSUME PROCESS $ZZKRN ABORT #ZACS The ABORT PROCESS command stops $ZACS but does not delete the process configuration. In other words, you can use the SCF START command to start $ZACS again. 3. Verify that $ZACS is stopped.
Chapter 7. SCF Command Reference for the ACS Subsystem Prev Next Chapter 7.
chapter describes the SCF commands that are interpreted specifically for ACS. The SCF Reference Manual for G-Series RVUs provides general information about SCF commands. You should be familiar with that information before reading the ACS subsystem-specific information provided here. Architecture As shown in Figure 7-1, the SCF interface locates and communicates with the appropriate product module, in this case ACSPM.
The communication between SCP and the subsystem takes place using Subsystem Programmatic Interface (SPI) messages. Supported commands List of ACS Subsystem-Specific Commands Most ACS subsystem commands are valid only for specific states, as shown in Table 7-1. The table also lists which ACS subsystem commands are SCF sensitive and nonsensitive commands. Table 7.1.
is the ACS subsystem-specific command name. object-type is the object type, which is always ACS for ACS subsystems. For detailed information on the SCF HELP command, see the SCF Reference Manual for G-Series RVUs . ACS Object The ACS object represents an ACS subsystem configured for a single physical system. The object is used to query and control the configuration of the subsystem. ACS object names are in the format: [ system-name. ] $ZACS system-name is the physical, Guardian name of the system.
Starting SCF SCF is located in the file $SYSTEM.SYSTEM.SCF. To start SCF, use the TACL RUN command, as follows: 1>\system.SCF If \system. is omitted, SCF is started on the local system. You can use the SETPROMPT command to change the prompt. SCF Command Format The general format of SCF commands is as follows: command [ /OUT file-spec/ ] [ object-spec ] [ attribute-spec ] OUT file-spec directs SCF to send the command output to a file.
ADD [ /OUT file-spec / ] , [ object-spec ] , , , [ , DOMAIN " domain-name" ALL , ENABLE LOG1 log-file-name:"format":" filter" ,LOG2 log-file-name:"format":" filter" ] ACSCTL $SYSTEM.ZACS.ACSCTL Syntax Descriptions. OUT file-spec specifies a file for the output of this command. The file can be on the same physical system as the ACS subsystem or on any system in the same Expand network. object-spec specifies the name of an ACS object to be added to the specified physical system.
This attribute is required. Note: For this version of TS/MP, ACS subsystem functions are automatically configured for all CPUs in the system. ENABLE For this version of TS/MP, the ENABLE attribute is required but not functional. LOG1 log-file-name:"format":"filter" and LOG2 log-file-name:"format":"filter" specifies the names of the files used for logging events and specifies the format and filters of those messages.
is not functional in this version of TS/MP; it is reserved for future use. Usage Notes. ● This command creates the BCINI file in $SYSTEM.SYSnn or in the default volume. The BCINI file contains the SCF configuration for the ACS subsystem. If a BCINI file already exists from a previous ADD command, the ADD command fails because only one ACS object can exist in a system. ● Before the ADD command is executed, all ACS messages are sent to $0. ● Any given attribute can appear only once in an ADD command.
Syntax Summary. ALTER [ /OUT file-spec / ] [ object-spec ] [ , DOMAIN " domain-name" ] [ , LOG1 log-file-name:"format":" filter" ] [ , LOG2 log-file-name:"format":" filter" ] Syntax Descriptions. OUT file-spec specifies a file for the output of this command. The file can be on the same physical system as the ACS subsystem or on any system in the same Expand network. object-spec specifies the name of the ACS object. The fully qualified object-spec has the format: [ ACS ] [ system-name.
If the LOG2 attribute is specified with no values, the current log file is closed. log-file-name specifies a Guardian disk file or process name. If you specify a disk file, an unstructured file is automatically created if the file does not exist. Caution: If you turn off logging by closing a current log file, all internally queued messages are lost. "format" specifies the format in which the log messages are logged, enclosed in double quotes (").
The system must be in the STARTED state. This is a sensitive command. Syntax Summary. CONTROL [ /OUT file-spec/ ] [ object-spec ] , { PROCESSORLIST ( processor-list ) } , ENABLE { ALL } Syntax Descriptions. OUT file-spec specifies a file for the output of this command. The file can be on the same physical system as the ACS subsystem or on any system in the same Expand network. object-spec specifies the name of the ACS object to be added to the specified physical system.
specifies all CPUs in the system. ENABLE restarts the ACS subsystem processes in the specified CPUs, if required. Examples. The following command restarts ACS subsystem processes in CPUs 2 and 3 on the local system: CONTROL ACS $ZACS, PROCESSORLIST (2, 3), ENABLE The following command restarts ACS processes in all CPUs on the remote system \PLUTO: CONTROL ACS \PLUTO.$ZACS, ALL, ENABLE DELETE Use the DELETE command to remove the ACS subsystem.
system-name is the physical, Guardian name of the system in which the object is being added and configured. If you specify the SCF object type (ACS) or any portion of the object name ( acs-spec) in a prior ASSUME command, you can omit it in this command. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs. If you have not used a prior ASSUME command and you omit system-name, the command defaults to the local physical system. Examples.
object-spec specifies the name of the ACS object. The fully qualified object-spec has the format: [ ACS ] [ system-name.]$ZACS system-name is the physical, Guardian name of the system in which the object is being added and configured. If you specify the SCF object type (ACS) or any portion of the object name ( acs-spec) in a prior ASSUME command, you can omit it in this command. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs.
The value displayed is usually 1, which indicates that the ACS subsystem processes are configured. However, in this release of TS/MP the value 0 may be displayed but has the same meaning as 1 and all 16 digits are displayed regardless of the physical configuration of your system. logfile-name the names of the LOG1 and LOG2 files, devices, or processes, to which messages are directed. Display Format Without DETAIL Option. subsystem-name INFO ACS [\ system-name.object-name] ZACS *Domain............
Syntax Summary. NAMES [ /OUT file-spec/ ] [ object-spec ] Syntax Descriptions. OUT file-spec specifies a file for the output of this command. The file can be on the same physical system as the ACS subsystem or on any system in the same Expand network. object-spec specifies the name of the object. The fully qualified object-spec has the format: [ ACS ] [ system-name.]$ZACS system-name is the physical, Guardian name of the system in which the object is being added and configured.
NAMES ACS $ZACS displays the ACS subsystem manager process on the local system, as follows: ACS Names ACS \MARS.$ZACS ACS $ZACS START Use the START command to start the ACS subsystem. The START command reads the configuration values stored in the BCINI file and begins the process of starting the subsystem. When the subsystem successfully completes processing this command, ACS subsystem processes are available in each processor in the system. Note: 1.
If you have not used a prior ASSUME command and you omit system-name, the command defaults to the local physical system. Usage Note. The START command initiates the process of starting the ACS subsystem. In the background, $ZACS performs all the tasks necessary to start the ACS subsystem. Because START is a no-waited command, use the STATUS command to track the progress of the START command. Examples.
[ ACS ] [ system-name.]$ZACS system-name is the physical, Guardian name of the system in which the object is being added and configured. If you specify the SCF object type (ACS) or any portion of the object name ( acs-spec) in a prior ASSUME command, you can omit it in this command. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs. If you have not used a prior ASSUME command and you omit system-name, the command defaults to the local physical system.
d Either one or more ACS subsystem processes in the CPU have failed but the CPU is still enabled, or the ACS object is in the STOPPED state. Pathsend requests are not accepted. Display format without DETAIL attribute. ACS Domain: domain-name System Status system-name subsystem-state Processor Status Usage Notes. ● Use the STATUS command to track the progress of the START, STOP, or CONTROL commands.
Syntax Descriptions. OUT file-spec specifies a file for the output of this command. The file can be on the same physical system as the ACS subsystem or on any system in the same Expand network. object-spec specifies the name of the object. The fully qualified object-spec has the format: [ ACS ] [ system-name.]$ZACS system-name is the physical, Guardian name of the system in which the object is being added and configured.
VERSION Use the VERSION command to display the ACS subsystem version number and other version information. This is a nonsensitive command. Syntax Summary. VERSION [ /OUT file-spec/ ] [ object-spec ] [ , DETAIL ] Syntax Descriptions. OUT file-spec specifies a file for the output of this command. The file can be on the same physical system as the ACS subsystem or on any system in the same Expand network. object-spec specifies the name of the ACS object.
subsystem-name version-banner GUARDIAN- T9050 -tos SCF KERNEL- Txxxxvff - ddmmmyy - ddmmmyy ACS PM- Txxxxvff - ddmmmyy - AAA - ddmmmyy object-name system-name subsystem-name version-banner tos Txxxxvff ddmmmyy The name of the object. The name of the physical system in which the subsystem is configured. The name of the subsystem. The version banner for the subsystem. The version of the Guardian kernel operating system. The product number and version.
Chapter 8. Pathsend Errors Prev Next Chapter 8. Pathsend Errors Types of Errors Returned by the Pathsend Procedures Descriptions of Pathsend Errors This chapter describes the error codes that can be returned by the TS/MP Pathsend procedure calls. These errors can be returned by processes that call the Pathsend procedures directly and also by software that uses these procedures internally, such as the ACS subsystem.
Guardian Procedures Errors and Messages Manual; however, specific Pathsend considerations for some of the file-system errors are given in this chapter in the descriptions of the associated Pathsend errors. Descriptions of Pathsend Errors The Pathsend error codes are described in numeric order.
Recovery. Correct the PATHMON name syntax. Refer to Section 5, Pathsend Procedure Call Reference, in the TS/MP Pathsend and Server Programming Manual for details about the correct syntax for PATHMON process names. 902 FEScPathmonConnect Cause. An error has occurred in the requester’s communication with the PATHMON process. For example, an open operation has failed, an I/O error has occurred, or the PATHMON process has failed.
FEScPathmonMessage Cause. The ACS subsystem process broker received an unrecognizable message from the PATHMON process while processing a SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ request. You might be using incompatible versions of the ACS subsystem and PATHMON processes, or this could be an ACS subsystem or PATHMON process internal error. Typical file-system error: 0 (FEOK). Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an error.
If this error is returned from SERVERCLASS_DIALOG_BEGIN_ or SERVERCLASS_DIALOG_SEND_, use SERVERCLASS_DIALOG_END_ or SERVERCLASS_DIALOG_ABORT_ to terminate the requester's portion of the dialog. 905 FEScNoServerLinkAvailable Cause. The ACS subsystem process broker had no links to the server class and was unable to get a link from a PATHMON process to satisfy this request. This is most likely caused by PATHMON configuration problems. Typical file-system error: 0 (FEOK). Effect.
Cause. The caller set bits in the flags parameter that are reserved and must be 0. This is a programming error. Typical file-system error: 2 (FEInvalOp). Effect. The send initiation fails with an error. Recovery. Set the reserved bits in the flags parameter to 0. 910 FEScMissingParameter Cause. A required parameter was not supplied. This is a programming error. Typical file-system error: 29 (FEMissParam). Effect. The send initiation fails with an error. Recovery.
Recovery. Correct the programming error. 913 FEScServerClassFrozen Cause. A process attempted to send to a frozen server class. Typical file-system error: 0 (FEOK). Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an error. The message is not sent to the server class. Recovery. Resend after the system manager or operator has thawed the server class. 914 FEScUnknownServerClass Cause. The server class is not configured through the specified PATHMON process.
Recovery. If the PATHMON process is shutting down, determine the reasons for the shutdown and perform appropriate recovery actions. If a server process is in debug mode and a timeout error (file-system error 40) occurred, do the following: ● Use the PATHCOM STATUS PATHMON command to find the server classes that are in the LOCKED state. ● Identify the server program file for each locked server class. ● Issue the TACL command STATUS *, PROG object-file-name to list all running processes.
Recovery. Correct your program or change the server-class configuration setting to TMF ON. 918 FEScSendOperationAborted Cause. The send operation was terminated at an indeterminate point. Typical file-system error: 40 (FETimedOut). Effect. The send fails. A message might or might not have been sent to the server process, depending on when the send was aborted. Recovery. The recovery action depends on which file-system error occurred.
Cause. The maximum number of concurrent server-class send operations allowed was exceeded. The maximum number is 255 for each requester. This error can occur on a call to SERVERCLASS_SEND_, SERVERCLASS_DIALOG_BEGIN_, or SERVERCLASS_DIALOG_SEND_. Note: This error is no longer returned when the limit of concurrent send operations is exceeded; instead error 947 (FEScRoutConnect) is returned with file-system error 30. Typical file-system error: 0 (FEOK). Effect. The call is completed with an error.
FEScOutstandingSend Cause. The requester has an outstanding send operation on this dialog. This error can occur on a call to SERVERCLASS_DIALOG_SEND_. This error can also occur when the ACS subsystem processes in a CPU fail and the Pathsend requesters on that CPU continue running. When ACS subsystem processes fail, TSMP 2.1 does not automatically terminate the Pathsend requesters in the CPU.
Effect. The operation fails with an error. Recovery. Use RESUMETRANSACTION to make the correct transaction identifier current, and reissue the call that failed. 931 FEScDialogEnded Cause. A call to SERVERCLASS_DIALOG_SEND_ failed because the server had already ended the dialog, either by replying with FEOK or FEEOF or by terminating while a send was still outstanding. This error can also occur when the ACS subsystem processes in a CPU fail and the Pathsend requesters on that CPU continue running.
934 FEScTransactionAborted Cause. The transaction associated with the dialog was aborted. Typical file-system error: 0 (FEOK). Effect. The procedure initiation fails with an error. The dialog is aborted. Recovery. Use SERVERCLASS_DIALOG_END_ or SERVERCLASS_DIALOG_ABORT_ to terminate the requester's portion of the dialog. 947 FEScRoutConnect Cause. There is a problem communicating with the ROUT process in this processor. Typical file-system errors: 14 (FENoSuchDev), 30 (FENOLCB), and 201 (FEPATHDOWN).
963 FEScNonPathsend Cause. The server process is not accepting Pathsend messages due to an internal failure. Effect. The operation is not performed. Recovery. None; contact your HP analyst. Prev Chapter 7. SCF Command Reference for the ACS Subsystem 528626.001 Up Home Next Chapter 9.
Chapter 9. SCF Error Messages Prev Next Chapter 9. SCF Error Messages If You Have to Call Your Service Provider SCF Error Messages This chapter describes the SCF error messages returned by the ACS subsystem interface to SCF. Refer to the SCF Reference Manual for G-Series RVUs for the list of SCF messages for all subsystems.
SCF Error Messages 00001 zacs^err^objname^unknown ACS 00001 Object name does not exist Cause. The object named in a command was not found. Effect. The command fails. Recovery. Issue the command again with the correct object name. 00004 zacs^err^attr^val^inv ACS 00004 Invalid value for attribute: attribute-name Cause. The value specified for the named attribute is incorrect. For example, the domain name or log file names specified in an ADD or ALTER command is incorrect. Effect. The command fails. Recovery.
Recovery. Restart SCF and issue the command again. If repeated attempts to issue the command fail, gather all relevant EMS logs and SaveAbend files and other information relevant to the error (see If You Have to Call Your Service Provider) and contact your service provider. 00007 zacs^err^delete^obj ACS 00007 The ACS object cannot be deleted Cause. A DELETE ACS command was issued while the ACS subsystem was in the STARTING, STARTED, or STOPPING state. Effect. The command fails. Recovery.
ACS 00012 The ACS subsystem is already started Cause. A START ACS command was issued while the ACS subsystem was already in the STARTED state. Effect. The command fails. Recovery. This is an informational message only; no corrective action is needed. 00013 zacs^err^acs^alrdy^stopped ACS 00013 The ACS subsystem is already stopped Cause. A STOP ACS command was issued while the ACS subsystem was already in the STOPPED state. Effect. The command fails. Recovery.
ACS 00018 ACS object does not exist Cause. The ACS object specified in the command does not exist. Effect. The command fails. Recovery. Issue the command again specifying a valid object name. 00019 zacs^err^api^error ACS 00019 API Internal error Cause. An unexpected Guardian procedure call error occurred within the product module. Effect. The command fails. Recovery. Terminate the SCF session. Start a new SCF session and issue the command again.
Cause. A required attribute was missing from the command. Effect. The command fails. Recovery. Issue the command again and include all required attributes. 00023 zacs^err^dup^format ACS 00023 Format is specified more than once Cause. The format value for a LOG1 or LOG2 attribute in an ADD or ALTER command was specified more than once. Effect. The command fails. Recovery. Issue the command again specifying the correct values for the LOG1 or LOG2 attribute.
Effect. The command fails. Recovery. Issue the command again. If the problem persists, correct the condition that is causing the problem. 00027 zacs^err^invalid^log^file ACS 00027 Invalid or corrupt log file: log-file-name Cause. An error occurred when attempting to access the specified log file. Effect. The operation fails. Recovery. Use the ALTER command to specify a new log file. 00028 zacs^err^secur^viol ACS 00028 Security violation Cause.
Chapter 10. ACS EMS Event Tokens Prev Next Chapter 10.
Event-Message SPI Format Each event message in this chapter includes the following information: ● The number and name of the event message ● A description of the event-message cause ● A syntax box listing the tokens associated with the message ● Token descriptions ● Effect and recovery information The syntax box contains the text version of the event message, which is available through the EMSTEXT procedure.
● ZEMS-TKN-TEXT token-type ZSPI-TYP-STRING. Contains the message text for each event message. Placeholders for conditional tokens that are omitted from an event message are replaced by empty strings. Null values of tokens included in the event message are converted to strings similar to like non-null values.
In this release, the ACS subsystem does not generate info events. This event level is reserved for future use. ZACL-VAL-EVENT-LEVEL-STATUS. Status events indicate the ACS subsystem made an orderly change in the state or status of an object, resource, or process under its control or it detected an orderly change in the state of an external resource or process. No recovery actions are required for status events. ZACL-VAL-EVENT-LEVEL-WARNING.
contains the number of the CPU on the local system in which the backup domain coordinator process was started. This token is the subject of the event message. Cause. The backup domain coordinator process was successfully created in the indicated CPU. Effect. The backup domain coordinator process runs in the indicated CPU. Recovery. This is an informational message only; no corrective action is needed. 1002 ZACL-EVT-BACKUP-LAUNCH-ERROR Event-Message Text.
1003 - Backup process in CPU cpu-number terminated abnormally, comp-code error-code, [ stopper stopper-id, ] [ term-ssid term-ssid, ] term-info term-info, [ term-text term-text ] Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-WARNING. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT. contains the number of the CPU on the local system in which the backup domain coordinator process was terminated.
1004 ZACL-EVT-CP-LAUNCH-ERROR Event-Message Text. 1004 - Core process creation in CPU cpu-number failed, name process-name, error errnum, detail error-detail, [ file file-name ] Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-WARNING, ZACL-VAL-EVENT-LEVEL-ERROR, or ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT. contains the number of the CPU on the local system in which the process could not be started.
Recovery. Correct the condition that caused the process creation failure then use the CONTROL ACS command to restart the ACS subsystem processes in the CPU. If the event is fatal or the problem persists, contact your HP support analyst. 1005 ZACL-EVT-CP-ABENDED Event-Message Text.
ZACL-TKN-EVENT-TERM-TEXT token-type ZSPI-TYP-STRING. contains the termination text associated with the process-termination. This token is omitted if no termination text was associated with the termination. Cause. An ACS subsystem process terminated unexpectedly. Effect. The ACS subsystem process is not available in the indicated CPU; other ACS subsystem processes continue to run on the CPU. Recovery. Correct the condition that caused the file error and try the operation again.
Recovery. Correct the condition that caused the file error and try the operation again. 1007 ZACL-EVT-OSS-ERROR Event-Message Text. 1007 - OSS operation procedure() failed, pathname path-name,error oss-errno Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has one of the values ZACL-VAL-EVENT-LEVEL-WARNING, ZACL-VAL-EVENT-LEVEL-ERROR, or ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-PROCEDURE token-type ZSPI-TYP-STRING.
ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-ERROR. ZACL-TKN-EVENT-PROCEDURE token-type ZSPI-TYP-STRING. contains the name of the Guardian process management procedure that reported the failure. This token is the subject of the event message. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING. contains the name of the ACS subsystem process associated with the failure. ZACL-TKN-EVENT-ERROR-CODE token-type ZSPI-TYP-INT.
contains the file-system error code returned by the failed operation. If the value of this token is zero in an event message, the token is null and is omitted from the message. Conditional Token ZACL-TKN-EVENT-SERVER-NAME token-type ZSPI-TYP-STRING. contains the PATHMON process name and server class name supplied to the failed operation, separated by a period. This token is omitted for link manager procedures that do not operate on server classes. Cause.
ZACL-TKN-EVENT-ERROR-DETAIL token-type ZSPI-TYP-INT. contains the memory management error detail code returned by the failed operation. If the value of this token is 0 (zero), the token is null and can be regarded as omitted from the message. Cause. An ACS subsystem process invoked a Guardian memory-segment management procedure and the operation failed unexpectedly. Effect. The process that invoked the failed operation terminates abnormally and produces a SaveAbend file. Recovery.
Event-Message Text. 1012 - Memory semaphore operation procedure() failed, segment segment-id, error errnum Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-PROCEDURE token-type ZSPI-TYP-STRING. contains the name of the Guardian binary semaphore procedure that reported the failure. This token is the subject of the event message. ZACL-TKN-EVENT-SEGMENT-ID token-type ZSPI-TYP-INT.
Cause. A process terminated while holding the lock on one of the ACS subsystem shared memory semaphores. Effect. The process that detected the abandoned semaphore terminates immediately. The shared memory may be corrupt. Recovery. Use the CONTROL ACS command to restart the ACS subsystem processes in the CPU where the semaphore was abandoned. 1015 ZACL-EVT-MEMPOOL-ERROR Event-Message Text.
Event-Message Text. 1016 - Insufficient free space in shared memory segment-id pool Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-SEGMENT-ID token-type ZSPI-TYP-INT. contains the identifier of the memory segment containing the pool from which space was to be allocated. This token is the subject of the event message. Cause.
ZACL-TKN-EVENT-ACCESS-ID token-type ZSPI-TYP-INT. contains the process-access user identifier of the unauthorized requester process. ZACL-TKN-EVENT-CREATOR-ID token-type ZSPI-TYP-INT. contains the process-creator user identifier of the unauthorized requester process. ZACL-TKN-EVENT-FILE-NAME token-type ZSPI-TYP-STRING. contains the file name of the ACS subsystem process that the unauthorized process supplied to the OPEN or FILE_OPEN_ operation.
returned to the requester process. Recovery. Correct the requester program. 1019 ZACL-EVT-INCOMP-RQST-VER Event-Message Text. 1019 - Incompatible request version received from process process-id Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-WARNING. ZACL-TKN-EVENT-PROCESS-ID token-type ZSPI-TYP-PHANDLE. contains the process handle of the requester process that sent the incompatible request message.
has one of the values ZACL-VAL-EVENT-LEVEL-ERROR or ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-PROCESS-ID token-type ZSPI-TYP-PHANDLE. contains the process handle of the server process that sent the invalid reply message. This token is the subject of the event message. If the process identified by this token still exists when the event message text is generated, the EMS event message formatting facilities convert process handle tokens to named or unnamed process descriptor strings.
2 - PATHMON process-name I/O operation timed out Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-WARNING. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING. contains the name of the PATHMON process. This token is the subject of the event message. Cause. An I/O operation from an ACS subsystem process to a PATHMON process timed out. ACS subsystem processes use a timeout value of 5 minutes for an I/O to a PATHMON process. Effect.
Cause. The PATHMON process communication with the ACS subsystem does not follow the TSMP protocol. Effect. The send operation fails with Pathsend error FEScPathmonMessage and file-system error FEOK. Recovery. Retry the send operation. If the problem persists, check the PATHMON process. You may need to shutdown and restart your application. 1024 ZACL-EVT-PATHMON-IO-ERROR Event-Message Text.
Event-Message Text. 1025 - PATHMON process-name OPEN operation failed, error errnum Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-WARNING. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING. contains the name of the PATHMON process. This token is the subject of the event message. ZACL-TKN-EVENT-ERROR-CODE token-type ZSPI-TYP-INT. contains the file-system error code returned by the failed operation. Cause.
1027 ZACL-EVT-PATHMON-EXT-SHUTDOWN Event-Message Text. 1027 - PATHMON process-name was externally shut down Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-WARNING. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING. contains the name of the PATHMON process. This token is the subject of the event message. Cause. A PATHMON process sent a PATHMONSHUTDOWN request to the ACS subsystem.
Recovery. No recovery action is required. 1029 ZACL-EVT-CPU-STARTED Event-Message Text. 1029 - Core processes started in CPU cpu-number Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-STATUS. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT. contains the number of the physical CPU that was started on the system where the event message was generated. This token is the subject of the event message. Cause.
of the event message. Cause. One or all of the ACS subsystem processes in a CPU on the local system failed or were stopped in response to a STOP command. If due to a failure, the physical CPU may have failed. Effect. Pathsend operations initiated in the CPU fail with FESCLINKMONCONNECT errors until the core processes are restarted. Recovery. Use the CONTROL ACS command to restart the ACS subsystem processes in the CPU. 1031 ZACL-EVT-LOG-FILE-ERROR Event-Message Text.
1032 ZACL-EVT-LOG1-OPENED Event-Message Text. 1032 - LOG1 opened on file file-name Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-STATUS. ZACL-TKN-EVENT-FILE-NAME token-type ZSPI-TYP-STRING. contains the Guardian name of the event log file. This token is the subject of the event message. Cause. The LOG1 event log file was opened successfully. Effect. None. Recovery. This is an informational message only; no corrective action is needed.
1034 ZACL-EVT-LOG2-OPENED Event-Message Text. 1034 - LOG2 opened on file file-name Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-STATUS. ZACL-TKN-EVENT-FILE-NAME token-type ZSPI-TYP-STRING. contains the Guardian name of the event log file. This token is the subject of the event message. Cause. The LOG2 event log file was opened successfully. Effect. None. Recovery. This is an informational message only; no corrective action is needed.
message for a detailed description of the problem. If the event was issued in response to an operator command, this is an informational message only; no corrective action is needed. 1036 ZACL-EVT-ENV-NAME-UNDEF Event-Message Text. 1036 - PATHMON process process-name is not running Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-WARNING. ZSPI-TKN-EVENT-ENV-NAME token-type ZSPI-TYP-STRING.
Cause. The server class name supplied to a Pathsend operation is not defined in the PATHMON process specified with it. Effect. The Pathsend operation fails. Recovery. Correct the Pathsend requester program. 1038 ZACL-EVT-SERVER-FILE-ERROR Event-Message Text. 1038 - Server pathmon-name.serverclass-name file operation procedure() failed, process process-id, file file-name, error errnum Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL.
Cause. A Guardian file-system operation on a server process failed unexpectedly or completed with an unexpected error code. Effect. The Pathsend operation associated with the file-system operation is aborted. Recovery. Correct the condition that caused the operation to fail. EMS Messages 1040 through 1049 1042 ZACL-EVT-SERVER-UNAUTH-MSG Event-Message Text. 1042 - Unauthorized attempt to invoke server pathmon-name.
EMS Messages 1050 through 1059 TS/MP 2.1 does not contain messages in this number range. EMS Messages 1060 through 1069 1062 ZACL-EVT-NO-BACKUP-CPU-AVAIL Event-Message Text. 1062 - ( process-name): No backup CPU available Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-WARNING. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING. contains the name of the domain coordinator process followed by its CPU and PIN enclosed in parentheses.
contains the invalid CPU number. This token is the subject of the event message. Cause. An invalid CPU number was specified in the domain coordinator process startup string. Effect. The primary domain coordinator process terminates immediately. Recovery. Start the domain coordinator process. Specify a valid CPU for the backup process or specify the value -1 to allow the domain coordinator process to select a backup CPU. 1064 ZACL-EVT-ACS-PROCNAME-IN-USE Event-Message Text.
ZACL-TKN-EVENT-FILE-NAME token-type ZSPI-TYP-STRING. contains the Guardian name of the domain-coordinator process-initialization file (BCINI). This token is the subject of the event message. Cause. The ACS subsystem domain-coordinator process-initialization file (BCINI) is invalid or contains invalid data. Effect. The domain coordinator cannot save the current ACS subsystem configuration to the BCINI file. Recovery.
Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-FILE-NAME token-type ZSPI-TYP-STRING. contains the name of the Guardian subvolume where the domain coordinator program resides. This token is the subject of the event message. ZACL-TKN-EVENT-SYSNN token-type ZSPI-TYP-STRING. contains the name of the Guardian subvolume that contains the OSIMAGE file used to load the system. Cause.
1069ZACL-EVT-PROCESS-SWITCH Event-Message Text. 1069 - Process pair for process-name is switching over Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-INFO. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING. contains the name of the process pair. Cause. The primary process can no longer continue. Effect. Primary process terminates and the backup process takes over. Recovery. Informational message only; no corrective action is needed.
Effect. The process pair cannot switch; ACS subsystem processes may not be available to handle requests. Recovery. If the backup-process CPU is down, reload it. If the backup-process CPU is up, use the CONTROL command to restart the ACS subsystem processes. 1071 1071. ZACL-EVT-PRIMARY-ABENDED Event-Message Text.
termination. ZACL-TKN-EVENT-TERM-TEXT token-type ZSPI-TYP-STRING. contains the termination text associated with the primary process termination. This token is omitted if no termination text was associated with the process termination. ZACL-TKN-EVENT-ERROR-DETAIL token-type ZSPI-TYP-INT. contains the termination information code associated with the process termination. If the value of this token is 0 (zero), the token is null and can be regarded as omitted from the message.
Appendix A. Backing Out Your Installation to TS/MP 2.0 Prev Next Appendix A. Backing Out Your Installation to TS/MP 2.0 You must consult HP support if you have installed TS/MP 2.1 and have run applications that use Pathsend requesters, then decide to backout and return to TS/MP 2.0. Plan the Backout ● ● ● TS/MP 2.0 cannot reside in the same system as TS/MP 2.1. The ACS subsystem must be stopped and removed from the system configuration before re-installing TS/MP 2.0. TS/MP 2.
Glossary Prev Next Glossary A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z A Application Cluster Services (ACS) subsystem An infrastructure used by transaction-processing middleware products to manage and access server classes. ACS domain A defined set of objects (resources) within a single physical NonStop system that are controlled and managed as a unit by the ACS subsystem. ACSCTL The ACS control file is the persistent store of environment configuration data.
E EMS The Event Management Service is part of the Distributed Systems Management (DSM) used to provide event collection, logging, and distribution facilities. environment A set of objects configured under and managed by a PATHMON process that monitors and manages a TS/MP application. F free pool The set of processes associated with server classes, which are managed by the process broker process.
M There are no entries for this section N nonsensitive command A command that can be issued by any user or program allowed to access the subsystem. In other words, a command for which the subsystem does not impose security restrictions. Nonsensitive commands cannot change the state or configuration of the objects; they are usually informational commands. See also sensitive command. O object A resource controlled by a subsystem. Objects include processes, disks, and data communications lines.
Q There are no entries for this section R redirector (RD) process Processes that provide link management functionality to Pathsend requesters. requester A process that uses the Pathsend API to communicate with server class processes. This is also called the client process. S Subsystem Control Point (SCP) he management process for a number of subsystems. There can be several instances of this process.
T There are no entries for this section U There are no entries for this section V There are no entries for this section W There are no entries for this section X There are no entries for this section Y There are no entries for this section Z There are no entries for this section Prev Appendix A. Backing Out Your Installation to TS/MP 2.0 528626.
Index Prev Index Symbols $ZACS process configuring, 3. Configure the Domain Coordinator Process ($ZACS) description of, Domain Coordinator Process ($ZACS) starting, 4.
configuration limits, Configuration and Environment Limits configuring, 5. Configure the ACS Subsystem descriptions of components, ACS Subsystem Components displaying information about, Displaying Information management interface, ACS Subsystem Product Module (ACSPM) manager process, 3.
B Backing out the TS/MP installation, Backing Out Your Installation to TS/MP 2.0 Backup process ... terminated (message 1003), EMS Messages 1000 through 1009 Backup process created ... (message 1001), EMS Messages 1000 through 1009 Backup process creation ... failed (message 1002), EMS Messages 1000 through 1009 Backward compatibility, Compatibility With TS/MP 2.
D DDL definitions for event messages, ACS Event Severity Levels DEFAULTVOL attribute, 3. Configure the Domain Coordinator Process ($ZACS) DEFINED state (ACS objects), ACS Object DELETE command (SCF), DELETE DELETEDELAY attribute, TS/MP 2.
associated with Pathsend errors, Pathsend Errors FEInUse (error 12), Descriptions of Pathsend Errors FENoBufSpace (error 31), Descriptions of Pathsend Errors FENoSuchDev (error 14), Descriptions of Pathsend Errors, Descriptions of Pathsend Errors FEPathDown (error 201), Descriptions of Pathsend Errors, Descriptions of Pathsend Errors FESecViol (error 48), Descriptions of Pathsend Errors, Descriptions of Pathsend Errors FETimeout (error 40), Descriptions of Pathsend Errors, Descriptions of Pathsend Errors Er
FEScMissingParameter (error 910), Descriptions of Pathsend Errors FEScNonPathsend (error 963), Descriptions of Pathsend Errors FEScNoSegmentInUse (error 908), Descriptions of Pathsend Errors FEScNoSendEverCalled (error 906), Descriptions of Pathsend Errors FEScNoServerLinkAvailable error description (error 905), Descriptions of Pathsend Errors increased frequency, TS/MP 2.
G Guardian file operation ... failed (message 1006), EMS Messages 1000 through 1009 H HELP command (SCF), Syntax Help for SCF Commands Hometerm ... not valid (message 1068), EMS Messages 1060 through 1069 HOMETERM attribute, 3. Configure the Domain Coordinator Process ($ZACS) I Incompatible request version received ... (message 1019), EMS Messages 1010 through 1019 INFO command (SCF), INFO Installing prerequisites for, Plan your TS/MP 2.1 Installation TS/MP 2.1 and ACS components, 1. Install TS/MP 2.
L Link management changes to, Link Management DELETEDELAY attribute, TS/MP 2.1 Environment Differences new features for, Overview of TS/MP 2.1 pin value changes, TS/MP 2.1 Environment Differences LINKMON process changes to, Changes to LINKMON (ROUT) Process connect error (error 947), Descriptions of Pathsend Errors pin value, TS/MP 2.1 Environment Differences replaced, Redirector (ROUT) Process ($ZLnn) LOG1/LOG2 attributes ADD command, ADD ALTER command, ALTER LOG1 closed ...
event, severity levels for, ACS Event Severity Levels Pathsend, Pathsend Errors SCF error, SCF Error Messages unrecognizable message (error 903), Descriptions of Pathsend Errors Migrating applications, Migrating Applications to TS/MP 2.
not running (message 1036), EMS Messages 1030 through 1039 OPEN ... failed (message 1025), EMS Messages 1020 through 1029 relationship to ACS subsystem, Process Management shutdown (error 915), Descriptions of Pathsend Errors unrecognizable message (error 903), Descriptions of Pathsend Errors Pathsend application program interface (API) error handling, Pathsend Errors errors, changes to, Pathsend errors Pathsend operation ...
Protocol conflict error (error 960), Descriptions of Pathsend Errors Protocol error ...
ACS subsystem, 6. Start the ACS Subsystem ($ZACS) domain coordinator process, 4. Start Domain Coordinator Process ($ZACS) restarting processes in a CPU, CONTROL restarting the ACS subsystem, Restarting ACS Subsystem Processes in a CPU SCF, 2. Start SCF STARTING state (ACS objects), ACS Object STARTMODE attribute, 3. Configure the Domain Coordinator Process ($ZACS) STARTUPMSG attribute, 3.
identifier changed (error 930), Descriptions of Pathsend Errors TS/MP ACS subsystem support for, ACS Subsystem Support for TS/MP 2.1 architecture comparison, Overview of TS/MP 2.1 backing out your installation, Backing Out Your Installation to TS/MP 2.0 backward compatibility, Compatibility With TS/MP 2.0 changes to documentation, Changes to TS/MP 2.0 Documentation migrating applications, Migrating Applications to TS/MP 2.1 new features, Overview of TS/MP 2.1 overview of changes to, Overview of TS/MP 2.
Glossary 528626.
Legal Notice © Copyright 2004 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
OSF software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California.
Version and Copyright Information Document Title TS/MP Supplement for Limits Relief Abstract This manual supplements the HP NonStop Transaction Services/MP (TS/MP) manual set. It describes the limits relief provided by TS/MP 2.1 and is intended for system managers, system operators, and application programmers using Pathsend requesters in TS/MP 2.0 environments. Product Version TS/MP 2.1 Supported Releases This manual supports G06.
