TS/MP Supplement for Limits Relief Next Version and Copyright Information Published December 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 supplement has been revised to include information on managing and using TS/MP 2.1 on HP NonStop S-series servers and HP Integrity NonStop servers. Information in this supplement changes and enhances information in the TS/MP 2.
About This Guide Prev Next About This Guide Notation Conventions Hypertext Links General Syntax Notation Notation for Messages Notation Conventions Hypertext Links General Syntax Notation Notation for Messages 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.
keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.c [ ] Brackets 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.
LOG1 log-file-name:"format":"filter" 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 type 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.
[ term-ssid term-ssid , ] Prev What's New in This Guide 528626.002 Up Home Next Chapter 1.
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 running TS/MP 2.0; it does not apply to SCOBOL users or TS/MP 3.0 users.
HP NonStop S-Series HP NonStop S-Series HP NonStop S-Series or HP Integrity or HP Integrity or HP Integrity Operating System NonStop Operating NonStop Operating NonStop Operating System System System Note: TS/MP for NonStop Tuxedo users is included in Table 1.1 solely for comparative purposes; TS/MP 2.1 does not apply to NonStop Tuxedo users. The major new and changed features are as follows: ● ● ● Applications ❍ No syntax changes to application configurations are required in PATHMON environments.
New Pathsend Limits TS/MP 2.1 contains a link-management architecture designed for the more powerful processors typically installed in today's NonStop systems. It provides higher configuration and processing limits to support higher link capacity for client processes and more efficient acquisition and usage of server processes. TS.MP 2.1 is designed with no architectural limits, which allows TS/MP applications to run without encountering limit errors.
● Pathway/XM. You can use Pathway/XM to manage TS/MP 2.1 environments. ● Server processes. TS/MP 2.1 supports Guardian and OSS-based server processes. ● PATHCOM. PATHCOM commands are supported and are unchanged. ● SPI commands. All system management interfaces are hosted and processed by the PATHMON process for the environment. There are no changes in version or message format. ● Scripts. TS/MP 2.
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. On servers running TS/MP 2.
3. If the process broker does not have a server process available to handle the request, it communicates with the environment's PATHMON process to fulfill the request. 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.
Statistics Collection You can collect and report statistics using PATHCOM exactly as documented for TS/MP 2.0. However, the values reported for TS/MP 2.1 may not be identical to the values reported for TS/MP 2.0 for the same application. The difference is due to different collection mechanisms, operational dynamics, and changes to management algorithms and some data points. Differences in statistical results should be minimal.
TS/MP Management Programming Manual TS/MP System Management Manual All sections of this manual apply to TS/MP 2.1 with the following exceptions: ● Replace all references to LINKMON with the ACS subsystem redirector, process broker, and configuration subscriber processes. For a description of these processes, see ACS Subsystem Components in Chapter 4 of this supplement. ● Section 7, Tuning Your System by Using Statistics: In general, these documented definitions continue to hold.
Prev Chapter 1. Overview of New and Changed Information for TS/MP 528626.002 Up Home Next Chapter 3. Migrating Applications to TS/MP 2.
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.
share memory and, therefore, are tightly bound. If any of these processes fails, the other processes may fail soon thereafter. As shown in Figure 4.1, the domain coordinator process also shares memory with the process broker, 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.
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.
Sensitive and Nonsensitive SCF Commands SCF commands that change the state or configuration of SCF objects are called sensitive commands. These commands can be executed only by super-ID users. See Chapter 7, SCF Command Reference for the ACS Subsystem for detailed information on the SCF interface and SCF commands for the ACS subsystem. Prev Chapter 3. Migrating Applications to TS/MP 2.1 528626.002 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.
How to do it. 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.
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 (").
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.
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. Start TS/MP PATHMON and Requesters For applications that use Pathsend requesters, you must start $ZACS and the ACS subsystem before starting PATHMON processes and your applications. See the TS/MP System Management Manual for information on starting PATHMON. Prev Chapter 4.
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 requesters. 2. Stop the ACS subsystem. 3. Verify the ACS subsystem is stopped. 4. Modify the subsystem configuration. 5. Start the ACS subsystem. See the TS/MP System Management Manual. Use the STOP command. For detailed information about this command, see STOP in Chapter 7. For example: STOP ACS $ZACS, FORCED Use the STATUS command. For detailed information about this command, see STATUS in Chapter 7.
Displaying ACS subsystem and processor status Use the STATUS command to display the current, operational status of the ACS subsystem. For detailed information about this command, see STATUS in Chapter 7. For example: 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.
2. If $ZACS is not started, start it. 3. Verify that $ZACS is started. Use the SCF START command interactively or in an OBEY file, as follows: ASSUME PROCESS $ZZKRN START #ZACS Use the SCF STATUS command as described in Step 1. 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.
2. Stop the ACS Subsystem 1. Stop the ACS subsystem. 2. Verify the ACS subsystem is stopped. Use the SCF STOP command. For detailed information about this command, see STOP in Chapter 7. For example: STOP ACS $ZACS, FORCED Use the SCF STATUS command. For detailed information about this command, see STATUS in Chapter 7. For example: STATUS ACS $ZACS, DETAIL 3. Stop $ZACS 1. Check whether $ZACS is Use the SCF STATUS PROCESS command. For example: stopped. STATUS PROCESS $ZZKRN.
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 and the SCF Reference Manual for H-Series RVUs provide 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 Syntax Help for SCF 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.
Syntax Help for SCF Commands To display the syntax for any SCF command supported by the ACS subsystem, use the HELP command, as follows: HELP ACS [ command ] [ object-type ] command 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 or the SCF Reference Manual for H-Series RVUs.
The ACS subsystem is in the process of being stopped in the specified physical STOPPING system. This is a transient state during the processing of the STOP ACS command. The ACS subsystem is stopped in the specified physical system and is not ready STOPPED for normal operations. In other words, the STOP ACS command was issued and it completed successfully. 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.
DELETE INFO NAMES START STATUS STOP VERSION ADD Use the ADD command to define and add a physical system (an ACS object) to an ACS domain, specify the file names for log files, and specify a domain name. (In this version of ACS, an ACS domain can contain one physical system.) This is a sensitive command. Syntax Summary 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.
information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs or the SCF Reference Manual for H-Series RVUs. If you have not used a prior ASSUME command and you omit system-name, the command defaults to the local physical system. DOMAIN "domain-name" specifies the name of the ACS domain to which the physical system is being added. This attribute is required.
quotes ("). Valid values are: "EMS" Log messages are formatted as event messages. "TEXT" Log messages are formatted as text messages. "filter" specifies which type of messages are logged, enclosed in double quotes ("). Valid values are: "FATAL" "ERROR" "WARNING" "STATUS" "INFO" "ALL" Only fatal messages are logged. Messages of this level or higher are logged. Messages of this level or higher are logged. Messages of this level or higher are logged. Messages of this level or higher are logged.
LOG1 \PLUTO.$VOL9.LOGFILES.LOG1:"EMS":"ALL" , & LOG2 \PLUTO.$VOL9.LOGFILES.LOG2:"TEXT":"ERROR" , & ACSCTL \PLUTO.$SYSTEM.ZACS.ACSCTL ALTER Use the ALTER command to modify the configuration of an existing ACS subsystem. This command changes only the attributes specified in the command; the values for all unspecified attributes remain unchanged. The ALTER command modifies the ACS subsystem configuration file (BCINI). The new configuration values are retained until they are modified by another ALTER command.
command defaults to the local physical system. DOMAIN " domain-name" specifies the domain name of the ACS subsystem being altered. For this version of TS/MP, HP strongly recommends that you specify the system name for the domain name; the specified domain name must be unique to domain names specified for any other ACS subsystems in other physical systems. domain-name is a string from one to seven alphanumeric characters enclosed in double quotes (").
configuration values are unchanged: ALTER ACS $ZACS, LOG1 $VOL1.LOGFILES.LOG10:"EMS":"ALL" The following command names a new log file for LOG1on the remote system \PLUTO; all other configuration values are unchanged: ALTER ACS \PLUTO.$ZACS, & LOG1 \PLUTO.$VOL9.LOGFILES.LOG10:"EMS":"ALL" CONTROL Use the CONTROL command to restart ACS subsystem processes in one or more processors. Changes made with the CONTROL command modify the operational status of the ACS subsystem, not the ACS subsystem configuration.
command defaults to the local physical system. PROCESSORLIST ( processor-list) | ALL specifies the CPUs in which you are restarting ACS subsystem processes. PROCESSORLIST ( processor-list) lists one or more CPUs. Specify the processors as a list of CPU numbers separated by commas and enclosed within parentheses (). The range of values for the processors is 0 through 15. For example, the string ( 1, 3, 5, 7) specifies CPUs 1, 3, 5 and 7. ALL specifies all CPUs in the system.
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 deleted. 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.
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.]$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.
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 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.
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. Before issuing this command, you must start the domain coordinator process ($ZACS). 2.
local system: START ACS $ZACS The following START command initiates the process of starting the ACS subsystem on the remote system \PLUTO: START ACS \PLUTO.$ZACS STATUS Use the STATUS command to display the current operational status of the ACS subsystem. The information displayed depends upon the state of the ACS subsystem, including any modifications specified by the CONTROL command. This is a nonsensitive command. Syntax Summary.
system-name subsystem-state ACSCTL: Location $SYSTEM.ZACS.ACSCTL domain-name State INACTIVE the name of the ACS domain. system-name the name of the physical system in which the subsystem is configured. subsystem-state the state of the ACS subsystem. Valid values are: DEFINED, STARTING, STARTED, STOPPING, STOPPED, and UNKNOWN. the status of each processor.
STATUS ACS $ZACS, DETAIL displays the following detailed status information about ACS availability on the local system: ACS Domain: MARS System Status \MARS STARTED ACSCTL: Location \MARS.$SYSTEM.ZACS.ACSCTL Processor Status <1111, 1111, 1111, 1111> State INACTIVE STOP Use the STOP command to stop the ACS subsystem. When the command successfully completes, the subsystem is in the STOPPED state and cannot process Pathsend requests.
performed. This attribute is required. Usage Notes. ● The STOP command initiates the process of stopping the ACS subsystem. In the background, $ZACS performs all the tasks necessary to stop the ACS subsystem. Use the STATUS command to track the progress of the STOP command. ● The STOP FORCED command performs the following: ❍ Stops all ACS subsystem processes in the system except $ZACS. ❍ Aborts all active transactions. The status of any outstanding transactions is unknown. Examples.
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 or the SCF Reference Manual for H-Series RVUs. If you have not used a prior ASSUME command and you omit system-name, the command defaults to the local physical system. DETAIL specifies that the display is to include the complete version information.
The following VERSION command: VERSION ACS $ZACS, DETAIL displays the following version information for the local system: VERSION ACS \MARS.$ZACS SYSTEM \MARS ACS Version 1.0 (01JUL2003) GUARDIAN - T9050 - (Q06) SCF KERNEL - T9082G02 - (05AUG03) (02JUL03) ACS PM - T0620G05 - 01JUN2003 - AAA - 24FEB03 Prev Chapter 6. Managing the ACS Subsystem 528626.002 Up Home Next Chapter 8.
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.
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. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an error.
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. Check the syntax of the procedure call and supply the required parameters. 911 FEScInvalidBufferLength Cause.
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.
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. ● Use the TACL STOP command to stop these processes.
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. If error 40 (FETimedOut) occurred, you might want to try a larger timeout value. 919 FEScInvalidTimeoutValue Cause.
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. The message is not sent to the server process. Recovery. In some cases, you can recover from this error by retrying the call. Whether a retry will work depends upon the design and operating environment of your application. 926 FEScDialogInvalid Cause.
requesters on that CPU continue running. When ACS subsystem processes fail, TSMP 2.1 does not automatically terminate the Pathsend requesters in the CPU. Therefore, some of the requesters might be in an inconsistent state and may continue to receive this error for dialog-based send initiations. This can occur even after the ACS subsystem processes are restarted on the CPU. Typical file-system error: 0 (FEOK). Effect. The send initiation fails with an error. Recovery.
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. When ACS subsystem processes fail, TSMP 2.1 does not automatically terminate the Pathsend requesters in the CPU.
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). Effect. The send initiation fails with an error. Recovery.
Recovery. None; contact your HP analyst. Prev Chapter 7. SCF Command Reference for the ACS Subsystem 528626.002 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 or the SCF Reference Manual for H-Series RVUsfor 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.
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. Use the STOP command to stop the ACS subsystem completely before issuing the DELETE command again.
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. This is an informational message only; no corrective action is needed.
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.
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. 00024 zacs^err^dup^filter ACS 00024 Filter is specified more than once Cause. The filter value for a LOG1 or LOG2 attribute in an ADD or ALTER command was specified more than once. Effect. The command fails.
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. SCF detected an attempt to execute a sensitive command by a user or requester with insufficient privilege. Effect. The attempt fails. Recovery. None; this is an informational message only.
Chapter 10. ACS EMS Event Tokens Prev Next Chapter 10.
Event-Message SPI Format Listed Tokens Unlisted Tokens 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-EVENTNUMBER token-type ZSPI-TYP-INT. Contains the ACS subsystem event message number. ● 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.
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.
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. 1002 - Backup process creation in CPU cpu-number failed, error errnum, detail error-detail 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.
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. This token is the subject of the event message. ZACL-TKN-EVENT-ERROR-CODE token-type ZSPI-TYP-INT. contains the completion code associated with the backup process termination. A completion code of -4 indicates that only the backup process, not both members of the process pair, terminated.
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. This token is the subject of the event message. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING. contains the name of the process that was not created. ZACL-TKN-EVENT-ERROR-CODE token-type ZSPI-TYP-INT.
comp-code comp-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-ERROR. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT. contains the number of the CPU on the local system in which the process terminated. This token is the subject of the event message. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING.
Event-Message Text. 1006 - Guardian file operation procedure() failed, [ file file-name, ] error errnum 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. the name of the Guardian file-system procedure that reported the failure. This token is the subject of the event message.
contains the name of the OSS procedure that reported the failure. This token is the subject of the event message. ZACL-TKN-EVENT-OSS-ERRNO token-type ZSPI-TYP-INT2. contains the file OSS error number returned by the failed operation. Conditional Token ZACL-TKN-EVENT-FILE-NAME token-type ZSPI-TYP-STRING. contains the path name of the OSS file or directory that was accessed by the failed operation. This token is omitted for OSS procedures that do not operate on files or directories. Cause.
operation failed unexpectedly. Effect. The operation associated with the process-management operation is aborted. Recovery. Correct the condition that caused the error and try the operation again. 1009 ZACL-EVT-PATHSEND-ERROR Event-Message Text. 1009 - Pathsend operation procedure() failed, server server-name, error errnum, detail error-detail Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-ERROR.
EMS Messages 1010 through 1019 1010 ZACL-EVT-SEGMENT-ERROR Event-Message Text. 1010 - Memory segment operation procedure() failed, segment segment-id, error errnum, detail error-detail 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 memory-segment management procedure that reported the failure. This token is the subject of the event message.
1011 - Corruption detected in shared memory segment segment-id 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 segment identifier of the memory segment in which the corruption was detected. This token is the subject of the event message. Cause. An ACS subsystem process detected corruption in the ACS subsystem shared-memory segment in its CPU. Effect.
SaveAbend file. Recovery. This is an internal error; contact your HP analyst. 1014 ZACL-EVT-BINSEM-ABANDONED Event-Message Text. 1014 - Process failed holding memory segment segment-id semaphore 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 protected by the semaphore that was being accessed by the failed operation.
contains the error code returned by the failed operation. Cause. An ACS subsystem process invoked a Guardian memory-pool management procedure and the operation failed unexpectedly. Effect. The process that invoked the failed operation terminates abnormally and produces a SaveAbend file. Recovery. This is an internal error; contact your HP analyst. Refer to the Operator Messages Manual, Appendix B, File-System Errors, for a definition of the specified error.
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 process that sent the unauthorized OPEN request 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.
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. If the process no longer exists, EMS generates a question mark instead of the process descriptor string. Cause. An ACS subsystem process received an invalid request message. Effect. The invalid request message is ignored.
1020 - Invalid reply message received from process process-id Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. 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.
Event-Message Text. 1022 - 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.
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. 1024 - PATHMON process-name I/O 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-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. An attempt to open a PATHMON process failed. Effect. The send operation fails with Pathsend error FEScPathmonConnect. Recovery.
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. This condition typically occurs in response to a TS/MP SHUTDOWN command. Effect.
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. The ACS subsystem processes in the specified CPU were started in response to a START command or were restarted in response to a CONTROL command. Effect. Pathsend operations initiated in the CPU no longer fail with FESCLINKMONCONNECT errors. Recovery.
Unconditional Tokens 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 file-system procedure that reported the failure. ZACL-TKN-EVENT-ERROR-CODE token-type ZSPI-TYP-INT. contains the file-system error code returned by the failed operation. ZACL-TKN-EVENT-FILE-NAME token-type ZSPI-TYP-STRING. contains the name of the event log file that was accessed by the failed operation.
1033 ZACL-EVT-LOG1-CLOSED Event-Message Text. 1033 - LOG1 closed 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 closed either in response to an operator command or because an error occurred while writing to the log file.
1035 ZACL-EVT-LOG2-CLOSED Event-Message Text. 1035 - LOG2 closed 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 closed either in response to an operator command or because an error occurred while writing to the log file.
1037 ZACL-EVT-SERVER-NAME-UNDEF Event-Message Text. 1037 - Server name pathmon-name.serverclass-name is not defined Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-WARNING. ZACL-TKN-EVENT-SERVER-NAME token-type ZSPI-TYP-STRING. contains the server class name supplied to the Pathsend operation. This token is the subject of the event message. ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32.
contains the process handle of the server process accessed by the failed operation. 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. If the process no longer exists, EMS generates a question mark instead of the process descriptor string. ZACL-TKN-EVENT-FILE-NAME token-type ZSPI-TYP-STRING.
class that the process is not authorized to communicate with. Authority to communicate with a Pathway server class is determined by the OWNER and SECURITY configuration attributes of the server class. Effect. The Pathsend operation fails with an FESERVERLINKCONNECT Pathsend error and FESECVIOL file-system error detail. Recovery. None. This event message indicates a possible attempt to breach the security of a Pathway application. EMS Messages 1050 through 1059 TS/MP 2.
Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. has the value of ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT. 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.
has the value of ZACL-VAL-EVENT-LEVEL-WARNING. 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.
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. The domain coordinator program does not reside in the current subvolume used to load the system ($SYSTEM.SYSnn). Effect.
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.
comp-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 primary domain coordinator process was running. This token is the subject of the event message. ZACL-TKN-EVENT-ERROR-CODE token-type ZSPI-TYP-INT.
Effect. The backup domain coordinator process becomes the primary domain coordinator process and creates a new backup process. Recovery. If the problem persists, contact your HP support analyst. Prev Chapter 9. SCF Error Messages 528626.002 Up Home Next Appendix A. Backing Out Your Installation to TS/MP 2.
Appendix A. Backing Out Your Installation to TS/MP 2.0 Prev Next Appendix A. Backing Out Your Installation to TS/MP 2.0 Plan the Backout General Backout Steps 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.
Glossary Prev Next Glossary A|C|D|E|F|L|N|P|R|S 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.
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. L LINKMON A TS/MP 2.0 privileged process executing in each processor of a NonStop system to provide link management to multiple TS/MP PATHMON-defined server classes.
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.
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 LINKMON process changes to, Changes to LINKMON (ROUT) Process connect error (error 947), Descriptions of Pathsend Errors replaced, Redirector (ROUT) Process ($ZLnn) LOG1/LOG2 attributes ADD command, Syntax Descriptions ALTER command, ALTER LOG1 closed ... (message 1033), EMS Messages 1030 through 1039 LOG1 opened ...
SCF error, SCF Error Messages unrecognizable message (error 903), Descriptions of Pathsend Errors Migrating applications, Migrating Applications to TS/MP 2.1 Missing parameter (error 910), Descriptions of Pathsend Errors Modifying subsystem configurations, Modifying The Configuration N NAMES command (SCF), NAMES No backup CPU available (message 1062), EMS Messages 1060 through 1069 Nonsensitive commands, List of ACS Subsystem-Specific Commands No OPEN received ...
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 ...
R Redirector process (see $ZLnn process) Required attributes are missing (SCF 00022), SCF Error Messages Restarting ACS processes, CONTROL Return errors, Pathsend, Types of Errors Returned by the Pathsend Procedures ROUT process, changes to, Changes to LINKMON (ROUT) Process ROUT process, replaced by $ZLnn, Redirector (ROUT) Process ($ZLnn) S Security features, Security sensitive SCF commands, List of ACS Subsystem-Specific Commands Send operation aborted (error 918), Descriptions of Pathsend Errors Send o
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. Configure the Domain Coordinator Process ($ZACS) States, for ACS objects, ACS Object Statistics, changes to results, Statistics Collection STATUS command, STATUS STOP command (SCF), STOP STOPMODE attribute, 3.
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.1 TSMP protocol violation ...
528626.
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.26 and all subsequent G-series releases and H06.
