HP NonStop TS/MP 2.5 Release Supplement HP Part Number: 679663-001 Published: February 2012 Edition: J06.03 and all subsequent J-series RVUs and H06.
© Copyright 2012 Hewlett-Packard Development Company L.P. Legal Notice 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.
Contents About This Manual........................................................................................6 Product Version........................................................................................................................6 Supported Release Version Updates (RVUs)..................................................................................6 Intended Audience....................................................................................................................
Pathway Configuration Limits..........................................................................................32 Wildcard Support.........................................................................................................33 Default Security Attribute................................................................................................33 HISTORY, !, and FC Command Support...........................................................................33 Security Logging..............
Stopping the ACS Subsystem....................................................................................................61 7 SCF Command Reference for the ACS Subsystem..........................................62 Overview..............................................................................................................................62 Architecture...........................................................................................................................
About This Manual This manual supplements the HP NonStop™ TS/MP manual set. It describes the new features provided by TS/MP 2.5. Product Version NonStop TS/MP 2.5. Supported Release Version Updates (RVUs) This publication supports J06.11 and all subsequent J-series RVUs and H06.22 and all subsequent H-series RVUs, until otherwise indicated by its replacement publications. Intended Audience This manual is intended for system managers, system operators, and application programmers using Pathway/iTS 1.
Documentation Organization This manual is structured as: Sections Description Section 1, “Application Cluster Services (ACS) Subsystem” (page 12) Describes the details of ACS Subsystem that includes architecture overview, domains, security, configuration, link management, and so on. Section 2, “Introduction to TS/MP Describes the features of TS/MP 2.5. 2.5” (page 28) Section 3, “Introduction to PDMCOM” (page 38) Describes the commands for starting and using PDMCOM.
[ ] Brackets Brackets enclose optional syntax items. For example: TERM [\.system-name]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list 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.
Line Spacing If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections.
A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list 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.
Document History Part Number Product Version Published 679663–001 TS/MP 2.5 February 2012 HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to docsfeedback@hp.com. Include the document title, part number, and any comment, error found, or suggestion for improvement concerning this document.
1 Application Cluster Services (ACS) Subsystem The Application Cluster Services provide link-management functions for applications using Pathsend requestors on the NonStop server platform. ACS replaces the traditional TS/MP 2.0 LINKMON (TS/MP ROUT) process to provide the Pathsend functionality on the system.
Figure 1 ACS Subsystem Architecture: System View (Single NonStop System) Architecture Overview 13
Figure 2 ACS Subsystem Architecture: Processor View Domain Coordinator Process ($ZACS) The domain coordinator process is also the ACS subsystem manager process. Only one instance of this process runs in a system that coordinates and manages the ACS domain resources configured for the subsystem. It also creates the initialization file (BCINI), which contains the ACS subsystem configuration.
NOTE: The ACS core processes are: • Domain Coordinator Process ($ZACS) • Process Broker Process ($ZPnn) • Configuration Subscriber Process ($ZCSnn) • Redirector (ROUT) Process ($ZLnn) NOTE: In TS/MP 2.5, the PB process performs the link acquisition, and the ROUT process performs the link management. Therefore, from the PATHMON perspective, the PB process is the link manager.
Sensitive and Non-Sensitive SCF Commands SCF commands that change the state or configuration of SCF objects are called sensitive commands. These commands can be run only by Super ID users. For more information on the SCF interface and SCF commands for the ACS subsystem, see “SCF Command Reference for the ACS Subsystem” (page 62). Before starting the TS/MP Pathsend requestors, you must use SCF commands to start the ACS subsystem. For more information, see “Starting the ACS Subsystem ($ZACS)” (page 57).
Figure 3 ACS Architecture with Pathway Domain 1. 2. 3. 4. The ACSCTL file, provided in the “ADD Command” (page 66) during startup of the ACS subsystem, contains information about two Pathway domains. Pathway domain %env1 comprises of PATHMONs $PM1 and $PM2 on NonStop system \A and Pathway domain %env2 comprises of PATHMONs $PM3 and $PM4 on the same NonStop system. Assumption is that you have configured the Pathway domains with similar Pathway configuration for the participating PATHMON processes.
the existing PATHCOM interface where all the existing PATHCOM commands are supported. However, unlike the existing PATHCOM interface, PDMI has the capability to communicate to multiple PATHMON processes simultaneously so that the same set of PATHCOM commands are run for multiple PATHMON processes. For more information, see “Introduction to PDMCOM” (page 38). ACSCTL File Configuration The ACSCTL is a configuration file that defines constraints to the namespace used by the ACS subsystem.
= {Pathway domain name} = {[:]{[,]&}} = {NonStop user name } = {percent of link requests to be provided by PATHMON based on the nl processing capacity of a system available to the PATHWAY application} = {NonStop system qualified PATHMON process name} The following context checks are made in the syntax: • The number of PATHMON processes used to define the Pathway domain is limited to four.
Table 1 Validation and Error Message for Node Names Validation Error Message The node name contains more than Invalid node name length. eight characters. The node name does not have “\” as first character. Invalid node name - node name must start with a “\”. The node name contains some Node name syntax error - only alphanumeric characters are expected. special characters (other than “\”). The second character is not an alphabet. First character of node name must be an alphabet.
Table 2 Limits for Pathsend Requestors (continued) Parameter Description TS/MP 2.5 Requestors send operation (per processor) Maximum outstanding send requests for all requestors in the 8191 processor. Server classes Approximate maximum server classes to which all requestors 4045 in a processor can have outstanding sends. The exact number depends on the current memory utilization. NOTE: When both TS/MP for NonStop Tuxedo (TROUT) and TS/MP 2.
processes while maintaining the same transactional throughput. Therefore, to achieve optimum performance, modify the PATHMON process configuration. To tune the PATHMON configuration, follow the steps outlined in Section 3, Steps to Optimum Link Configuration in the TS/MP 2.5 System Management Manual. NOTE: Context-free and context-sensitive links from a requestor to the same server class are not shared, but separate links are used for each.
1. The application requestor calls the Pathsend API, either to a specific PATHMON process or to a configured Pathway domain. The system library checks the supplied parameters, formats a message, and sends it to the local ROUT process. NOTE: For SCOBOL APIs, the application requestor calls the SCOBOL API, either to a specific PATHMON process or to a configured Pathway domain.
The application environment (PATHMON) parameter used in the Pathsend APIs now support the Pathway domain name passed for this parameter. The Pathway domain name is established through the ACSCTL file domain membership section. This name is used to identify a set of PATHMON processes that can be used to obtain links for an identified server class. Syntax Summary { {[.
Load Balancing PATHMON Link Requests in a Pathway Domain The Pathway domain list in the ACSCTL file defines the percentage (weight) of link requests that must be accepted by each PATHMON process associated with the requested domain. The weight value of the specified PATHMONs must consider the processing capacity of the server classes that are configured under those PATHMONs.
Consider that the ACSCTL file on system \A has the following weights defined for domain %DOM. %DOM = \A.$PM1:80, \A.$PM2:20 The PATHMONs $PM1 and $PM2 have server DEMO-SERVER configured. The LINKDEPTH and MAXLINKS parameter values are set to 1. The MAXSERVERS and NUMSTATIC parameter value is: PATHMON Names $PM1 $PM2 MAXSERVERS 16 4 NUMSTATIC 4 1 Parameters Under heavy load conditions, all the server processes (links) are active.
dynamics, and changes to management algorithms and some data points. The differences in statistical results must be minimal. Error Handling The ACS subsystem provides the following error handling components. ACS Auto-Restart The ACS subsystem detects any failure of its core processes. All the core processes on the processor are automatically restarted when any core process fails on that processor. No manual intervention is required from the operators.
2 Introduction to TS/MP 2.5 TS/MP 2.5 is a newer version of TS/MP software, which is used as a replacement for TS/MP 2.0 and later versions. This section includes these topics: • “Overview of TS/MP” (page 28) • “TS/MP Features” (page 29) • “TS/MP Earlier Version Features” (page 32) • “Compatibility with TS/MP 2.
Table 5 Architecture Comparison of TS/MP Versions TS/MP 2.3, 2.4, and 2.5 TS/MP 2.1 TS/MP 2.0 TS/MP with NonStop Tuxedo Application TS/MP Application Environment TS/MP Application Environment TS/MP Application Environment Management and Control TS/MP 2.3, 2.4, and TS/MP 2.1 (Existing 2.5 (Updated PATHMON and PATHMON, PATHCOM Processes) PATHCOM, and new PDMI Processes) TS/MP 2.
For example, a user can configure ACSCTL file on two nodes in this way: System 1:\sys1 [PATHWAY DOMAIN] %DOM1 = \sys1.$exam1, \sys2.$exam2 System 2: \sys2 [PATHWAY DOMAIN] %DOM1 = \sys1.$exam1, \sys2.$exam2 The example shows that on both systems %DOM has the same PATHMONs, and the domain sends issued on both systems are served by either of the PATHMON processes. NOTE: TS/MP 2.5 does not support the sync-upgrade feature for a domain which has a remote PATHMON process.
is optional. If a user does not set this attribute, PATHMON exhibits the existing behavior. For more information, see section SET PATHWAY command in the TS/MP 2.5 System Management Manual. Considerations • The link manager processes other than from TS/MP 2.5 ROUT (TS/MP 2.0 LINKMON, TS/MP 3.0 ROUTER, and TS/MP 2.4, 2.3 and 2.1 ROUT) displays an error 905 (FESCNoServerLinkAvailable), while a server process is rebalanced. A server process rebalancing needs special processing on the part of the link manager.
Log Event 1006 as WARNING or FATAL The ACS subsystem is updated to log event 1006 as a WARNING message when a Pathsend request is issued for a non running PATHMON. In the existing implementation, ACS logs it as a FATAL message. For all other 1006 event conditions, ACS continues to log a FATAL message. For more information on this error, see the TS/MP 2.5 System Management Manual.
Wildcard Support The following server commands in PATHCOM allow management and operation of server objects, by specifying “*” as wildcard in the object name: • FREEZE • INFO • START • STATS • STATUS • STOP NOTE: Only one instance of the wildcard character ("*") is accepted. If two or more asterisks are used, the Illegal Syntax error appears. Therefore, for example, A*BD, AB*D, or ABD* is supported. However, A*B*D or AB**D is not supported.
For each replicated server class under PATHMON processes in a Pathway domain (representing a single logical server class to requestor applications), you can specify different CPU-Weight combinations. In conjunction with the weights assigned to each PATHMON process in the domain through the domain configuration in the ACSCTL file, this feature will help to create the server processes with most appropriate distribution on processors of your choice.
For more information on the ACS API errors, see Section 7, Pathsend Errors for ACS Subsystem in the TS/MP 2.5 Pathsend and Server Programming Manual. Automated Online Upgrade The planned outage elimination feature is enhanced in the latest version of the TS/MP. It provides capability to upgrade a server class application object online while maintaining application consistency.
Large Message Support TS/MP supports data transmission of up to 2 MB for context free Pathsend requests. A new Pathsend API, SERVERCLASS_SENDL_, allows you to send and receive messages of up to 2 MB. See the SERVERCLASS_SENDL_ procedure in the HP NonStop TS/MP 2.5 Pathsend and Server Programming Manual.
• SPI commands: All system management interfaces are hosted and processed by the PATHMON process for the environment. No changes exist in version or message format. NOTE: • PDMCOM does not support SPI Commands. Scripts: TS/MP 2.5 supports TS/MP 2.0 scripts and configurations. For information on application migration and back out, see “Migrating Applications to TS/MP 2.5” (page 50) and “Backing Out Your Installation to TS/MP 2.0” (page 90). Compatibility with TS/MP 2.
3 Introduction to PDMCOM Pathway Domain Management Command interpreter (PDMCOM) is a command line interface used to start PDMI. By default, it resides in $SYSTEM.SYSTEM, which is a superset of PATHCOM, and supports wildcarded object names. PDMCOM provides an easy configuration and management interface for multiple Pathway environments grouped together in a domain. This domain feature, provided by ACS, eliminates application outages through online changes to the Pathway configuration.
Getting HELP for PDMCOM Syntax and Errors To use the HELP command through PDMCOM, the PDMHELP file must also reside in the same subvolume as PDMCOM.
TACL Routines The TACL INLINE facility enables you to incorporate PDMCOM commands into a TACL routine to manage multiple PATHMON environments. The following sample shows a TACL routine that shuts down two PATHMON processes: . . PDMCOM/inline,cpu 1/ [#loop |do| #set count [#compute [count] + 1 ] #OUTPUT OPENING $PM[COUNT] + open $PM[count] + shutdown2,mode im #OUTPUT SHUTDOWN $PM[COUNT] |until| [count] >= 2 ] . .
pathmon name specifies the name of the PATHMON whose server upgrades first. If the PATHMON directive is omitted, the PATHMON with maximum weight is selected. server name specifies the name of the server, which is upgraded. ad-scparam specifies the name of the server-class attributes except process attribute. Considerations • The ALTER-DOMAIN command is a combination of SERVER commands. When a SERVER command fails to execute, the ALTER-DOMAIN command terminates abnormally.
PDMI 3>> CONTROL DOMAIN Command Use the CONTROL DOMAIN command to temporarily change the domain behavior. The CONTROL DOMAIN command is applicable when a domain is opened using an earlier OPEN command. CONTROL DOMAIN { PARTITION PATHMON pathmon name} { UNDO PARTITION } SERVER server name pathmon name specifies the name of the PATHMON whose server class needs to be partitioned. server name specifies the name of the server class that needs to be partitioned or unpartitioned.
\ACS.$PM1 10 RUNNING \ACS.$PM2 10 RUNNING \ACS.$PM4 10 RUNNING PDMI 6>> control domain undo partition server svr2 PDMI 7>> status domain PATHMON WEIGHT STATUS \ACS.$PM3 70 RUNNING \ACS.$PM1 10 RUNNING \ACS.$PM2 10 RUNNING \ACS.$PM4 10 RUNNING PARTITIONS ENV command Use ENV command to display PATHMON processes with which the PDMI process is currently communicating. ENV Example • To display current environment: PDMI 1>> OPEN $PM1, $PM2, $PM3 PATHMON : \NSSYS.$PM1 PATHMON : \NSSYS.
Considerations • You can enter sub commands and their associated strings below the display command line and terminate these commands with a carriage return. Begin replacement, insertion, and deletion commands with the character positioned directly above the sub command (R, I, and D). Sub command R replaces characters in the command line with replacement-string on a one-for-one basis. Sub command I inserts insertion-string in the command-line before the character that is above insertion-string.
PATHMON : \NSSYS.$PM1 PDMI 6>> To edit and execute a command using string, enter: PDMI 6>> FC AL The command starting with “AL” that is executed last, is displayed: PDMI 6>> ALTER SRV1, DEBUG ON HISTORY Command Use the HISTORY command to display previous PDMCOM commands. HISTORY|H [ number ] number is the number of previous commands that you want to retrieve. The default value is 10. Considerations • If you omit number, the HISTORY command displays the last ten commands.
domain name specifies the name of the Pathway domain to be opened. The domain name must start with '%'. pathmon name specifies the name of the PATHMON process to be opened. Considerations • The OPEN command is used to open multiple PATHMON processes or a Pathway domain. Additionally, it groups a set of PATHMON processes against which the operational commands are run. For example, the ADD SERVER command is run for all PATHMON processes used in the above command.
Example 1 STATUS DOMAIN Display Format PATHMON WEIGHT STATUS PARTITIONS pathmon name number RUNNING server class pathmon name number RUNNING server class pathmon name number RUNNING server class The fields in this display format are as follows: Display Field Description PATHMON PATHMON name. WEIGHT Weight of the PATHMON specified in the ACSCTL file. STATUS The current state of the PATHMON. Possible state values are: STOPPED: The PATHMON process is not running.
Considerations • The ! command executes the command indicated by the number. By default, the last command is processed. • You can specify a string after the ! command. If the string matches the starting letters of any of the previous ten commands, the corresponding command is executed. • If you use the ! command without a number or text string, PATHCOM executes the last command you entered. Example • If the following commands are entered at the PDMCOM prompt: \NSSYS.$VOL.
NOTE: If PDMCOM fails to communicate with the ACS subsystem, it executes a command with information message.
4 Migrating Applications to TS/MP 2.5 This section includes these topics: • “Environment Similarities” (page 50) • “Environment Differences” (page 50) All TS/MP 2.0 applications that use Pathsend requestors and TS/MP configuration scripts (also called OBEY files) can run in a TS/MP 2.5 environment. However, to take advantage of the new features and to understand slight differences in behavior, it is important to understand the similarities and differences between the two versions of TS/MP.
is also updated to override the default domain feature of TS/MP 2.5. For more information on the new domain name syntax and the updated flags parameter, see the TS/MP 2.5 Pathsend and Server Programming Manual. • SCF commands: The SCF interface includes a new set of commands to manage the configuration and operation of the ACS subsystem. For information on managing ACS subsystems, see “Managing the ACS Subsystem” (page 59) and “SCF Command Reference for the ACS Subsystem” (page 62).
interface, see “PDMCOM Commands” (page 40). TS/MP 2.5 also contains updated versions of the PATHMON and PATHCOM components that support higher PATHMON configuration limits and support wildcard characters for PATHCOM commands for SERVER objects. • 52 Changes to switching between context-free and context-sensitive sends: When a link performs a context-free send, it is not immediately available to perform context-sensitive sends and vice versa.
5 Installing and Configuring This section includes these topics: • “Prerequisites” (page 53) • “Installing TS/MP 2.5 version” (page 53) • “Configuring and Starting the ACS Subsystem” (page 56) • “Starting TS/MP PATHMON and Requestors” (page 58) NOTE: Before starting TS/MP PATHMON processes or Pathsend requestors, you must install and configure TS/MP 2.5, and then start the ACS subsystem. For information on backing out your installation from TS/MP 2.5 to TS/MP 2.
1. On HP Integrity NonStop servers, the TS/MP 2.0 LINKMON or ROUT process is added directly under the Persistence Manager $ZZKRN process using the SCF ADD PROCESS command. The $ZZKRN process maintains a persistent table of its own where it maintains all added entries. An added entry remains in the table (until it is explicitly deleted using SCF DELETE PROCESS command) irrespective of the number of sysgens and processor reloads performed. The SCF ADD PROCESS command for TS/MP 2.
ROUT $ZL07 STOPPED None None ROUT $ZL08 STOPPED None None ROUT $ZL09 STOPPED None None ROUT $ZL10 STOPPED None None ROUT $ZL11 STOPPED None None ROUT $ZL12 STOPPED None None ROUT $ZL13 STOPPED None None ROUT $ZL14 STOPPED None None ROUT $ZL15 STOPPED None None 4-> DELETE PROCESS $ZZKRN.#ROUT 5-> NAMES * NONSTOP KERNEL - NAMES PROCESS \.$ZZKRN.* Process $ZZKRN.#OSM-APPSRVR $ZZKRN.#OSM-CIMOM $ZZKRN.#OSM-CONFLH-RD $ZZKRN.#OSM-OEV $ZZKRN.
Configuring and Starting the ACS Subsystem Starting SCF This step starts the SCF management interface, which is typically located in the file $SYSTEM.SYSTEM.SCF. Procedure: 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.
supported. For a description of all values, see the SCF Reference Manual for the Kernel Subsystem. This attribute is mandatory. HOMETERM home-term specifies the home terminal for the ACS manager process. home-term has the format: hometerm-file-spec. This attribute is mandatory. Starting Domain Coordinator Process ($ZACS) You must start the $ZACS process before you configure the ACS subsystem.
START ACS $ZACS The START command starts the configuration subscriber, PB, and redirector process in each processor of 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 the subsequent SCF commands.
6 Managing the ACS Subsystem This section includes these topics: • “Modifying the Configuration” (page 59) • “Displaying Information” (page 60) ◦ “Displaying ACS Subsystem Configuration” (page 60) ◦ “Displaying ACS Domain Coordinator ($ZACS) Name” (page 60) ◦ “Displaying ACS Subsystem and Processor Status” (page 60) ◦ “Displaying ACS Subsystem Version” (page 60) • “Restarting ACS Subsystem Processes in a CPU” (page 60) • “Restarting the ACS Subsystem” (page 60) • “Stopping the ACS Subsystem”
Displaying Information You can use different commands to display the ACS subsystem information. Displaying ACS Subsystem Configuration Use the INFO command to display the configuration values set by the ADD and ALTER commands. For more information on this command, see “INFO Command” (page 72). For example: INFO ACS $ZACS, DETAIL Displaying ACS Domain Coordinator ($ZACS) Name Use the NAMES command to display the name of the domain coordinator process.
START ACS $ZACS b. Use the SCF STATUS command to verify that the ACS subsystem has started. For more information on this command, see “STATUS Command” (page 80). For example: STATUS ACS $ZACS, DETAIL Stopping the ACS Subsystem If you are stopping the subsystem to change the configuration, you need to perform Step 2 only. If you want to remove the TS/MP 2.5 from your system, perform the following steps. 1. Stop the Pathsend Requestors For information on stopping Pathsend Requestors, see the TS/MP 2.
7 SCF Command Reference for the ACS Subsystem This section includes these topics: • “Overview” (page 62) • “Architecture” (page 62) • “Supported Commands” (page 63) ◦ “List of ACS Subsystem-specific Commands” (page 63) ◦ “Syntax Help for SCF Commands” (page 64) • “ACS Object” (page 64) • “Starting SCF” (page 65) • “SCF Command Format” (page 65) • “ACS Subsystem-specific SCF Commands” (page 65) ◦ “ADD Command” (page 66) ◦ “ALTER Command” (page 68) ◦ “CONTROL Command” (page 69) ◦ “DELET
Figure 5 SCF Management Interface for ACS Subsystem The SCF process determines which subsystem runs the command (the ACS subsystem in this case). It launches the product module responsible for that subsystem (for example, ACSPM for the ACS subsystem) and forwards the command to that product module. The domain coordinator ($ZACS) processes the commands; the ACS product module parses the commands specific to the ACS subsystem and formats the display of results.
Table 8 SCF Commands for ACS Subsystems Command SCF Sensitive SCF Non-sensitive Valid in These States ADD X — UNKNOWN ALTER X — DEFINED, STOPPED CONTROL X — STARTED DELETE X — DEFINED, STOPPED INFO — X UNKNOWN, DEFINED, STARTING, STARTED, STOPPING, STOPPED NAMES — X UNKNOWN, DEFINED, STARTING, STARTED, STOPPING, STOPPED START X — DEFINED, STOPPED STATS — X STARTED STATUS — X UNKNOWN, DEFINED, STARTING, STARTED, STOPPING, STOPPED STOP X — STARTING, STARTED VERSION
The following operational states are valid for ACS objects: UNKNOWN The ACS object is not defined in the specified physical system. In other words, the ACS subsystem has not been added to the physical system by the ADD ACS command. An ACS object is in this state after the ACS subsystem is deleted by the DELETE ACS command. DEFINED The ACS object is defined in the specified physical system. In other words, the ADD ACS command was issued and it completed successfully.
9. “STATUS Command” (page 80) 10. “STOP Command” (page 82) 11. “VERSION Command” (page 83) ADD Command This command is used to define and add a physical system (an ACS object) to an ACS domain, specify the filenames for log files, and specify a domain name. (In this version of ACS, an ACS domain can contain only one physical system.) This is a sensitive command and has been updated to: • optionally configure ROUT process to run as a high PIN process. • make LOG1/LOG2 optional.
DISABLE The DISABLE attribute is not functional. It is reserved for future use. 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. Event messages are used to report to an operator or application program through the Event Management Service (EMS). Log files LOG1 and LOG2 can be used to override a previously configured log file.
Example 3 Adding an ACS object to the local system \MARS ADD ACS $ZACS, DOMAIN "MARS" , & ALL , ENABLE , & LOG1 $VOL1.LOGFILES.LOG1:"EMS":"ALL" , & LOG2 $VOL1.LOGFILES.LOG2:"TEXT":"ERROR", & ACSCTL $SYSTEM.ZACS.ACSCTL Example 4 Adding an ACS object to the remote system \PLUTO ADD ACS \PLUTO.$ZACS, DOMAIN "PLUTO" , & ALL , ENABLE , & LOG1 \PLUTO.$VOL9.LOGFILES.LOG1:"EMS":"ALL" , & LOG2 \PLUTO.$VOL9.LOGFILES.LOG2:"TEXT":"ERROR" , & ACSCTL \PLUTO.$SYSTEM.ZACS.
NOTE: HP 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. LOG1 specifies the names of files used to log events and specifies the format and filters of those log-file-name:"format": messages. LOG1 and LOG2 can be used to override a previously configured log file. "filter" and LOG2 If the LOG1 or LOG2 attribute is specified with no values, the current log file is closed.
NOTE: The ACS subsystem must be in the STARTED state when this command is issued. Syntax Summary CONTROL [/OUT /] [,{{PROCESSORLIST ()} | ALL },{ENABLE} ] [, LOG1 [::]] [, LOG2 [::]] [, ACSCTL ] Syntax Description OUT file-spec specifies a file for the output of this command.
1. 2. 3. 4. Shut down all PATHMONs in the Pathway domain. Update the ACSCTL file. Use the ACSCTL option in the CONTROL command Start the PATHMONs in the Pathway domain. For more information on the ACSCTL file syntax, see “ACSCTL File Configuration” (page 18). NOTE: If you fail to follow the above-mentioned procedures, an inconsistent ACS environment can be resulted. Any syntax error in the ACSCTL file will cause the CONTROL command to fail.
The following command restarts ACS processes in all CPUs on the remote system \PLUTO: CONTROL ACS \PLUTO.$ZACS, ALL, ENABLE DELETE Command Use the DELETE command to remove the ACS subsystem. This command deletes the ACS object from the SCF subsystem configuration file (BCINI), and then deletes the BCINI file; it does not uninstall the ACS subsystem. NOTE: Before issuing this command, you must do the following: 1. Stop the TS/MP server classes and PATHMON processes. 2. Stop the ACS subsystem.
Syntax Description 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 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.
Example 8 Display Format without DETAIL Option subsystem-name INFO ACS [\ system-name.object-name] ZACS *Domain............domain-name Example The following INFO command with the DETAIL option: INFO ACS $ZACS, DETAIL returns the following information about the local system: Application Cluster Services INFO ACS \MARS.$ZACS ZACS *Domain.............MARS Processor status...1111111111111111 *LOG1...............\MARS.$VOL1.LOGFILES.LOG1 *LOG2...............\MARS.$VOL1.LOGFILES.LOG2 *ACSCTL.............\MARS.
nl object-name where: subsystem-name is the name of the subsystem. object-name is the name of the object. Example The NAMES command: NAMES ACS $ZACS displays the ACS subsystem manager process on the local system, as follows: ACS Names ACS \MARS.$ZACS ACS $ZACS START Command Use the START command to start the ACS subsystem. The START command reads the configuration values stored in the BCINI file and starts the subsystem.
The following START command initiates the process of starting the ACS subsystem on the remote system \PLUTO: START ACS \PLUTO.$ZACS STATS Command Use the STATS command to instruct each processor to return current operational statistics about its requestor and server class link usage. The ACS command is modified to accept the server classname as a parameter.
• Average, Standard Deviation, and Maximum for the time it takes to perform a server class dialog (from Dialog begin to Dialog end). • Domain under which the server class is configured. NOTE: If a Pathmon is configured under more than one domains, the domain name appearing last in ACSCTL file is displayed. • Fully qualified server class name. Processing The STATS command accepts an optional parameter server-name and DETAIL or RESET option.
Domain Count SrvClass Count Link Count Link Max Requestor Count Send Avg (STD) Send Max 00 00 00 00 00 0.0(0.0) 00 PROCESSOR : 03 Domain Count SrvClass Count 01 02 DOMAIN : \NSSYS.$PM SERVERCLASS: \NSSYS.$PM.SC1 Static Count Dynamic Count Link Time Avg(STD)Max Req/sec Avg(STD)Max Send Avg(STD)Max Dialog Duration Avg(STD)Max Link Count Link Max Requestor Count Send Avg (STD) Send Max 02 02 00 0.0(0.0) 00 : : : : : : 01 00 0.0(0.0)0.0 0.0(0.0)1.0 0.0(0.0)0.0 0.0(0.0)0.
DOMAIN : \NSSYS.$PM SERVERCLASS: \NSSYS.$PM.SC1 Static Count Dynamic Count Link Time Avg(STD)Max Req/sec Avg(STD)Max Send Avg(STD)Max Dialog Duration Avg(STD)Max DOMAIN : \NSSYS.$PM SERVERCLASS: \NSSYS.$PM.SC2 Static Count Dynamic Count Link Time Avg(STD)Max Req/sec Avg(STD)Max Send Avg(STD)Max Dialog Duration Avg(STD)Max : : : : : : 01 00 0.0(0.0)0.0 0.0(0.0)1.0 0.0(0.0)0.0 0.0(0.0)0.0 : : : : : : 01 00 0.0(0.0)0.0 0.0(0.0)1.0 0.0(0.0)0.0 0.0(0.0)0.
Req/sec Avg(STD)Max : 0.0(0.0)0.0 nl Send Avg(STD)Max : 2.3(1.4)4.0 Dialog Duration Avg(STD)Max : 0.0(0.0)0.0 nl DOMAIN : \A.%PDM2 nl SERVERCLASS: \A.$PM3.SC2 nl Static Count : 02 nl Dynamic Count : 00 nl Link Time Avg(STD)Max : 0.0(0.0)0.0 Req/sec Avg(STD)Max : 0.0(0.0)0.0 Send Avg(STD)Max : 1.2(0.4)3.0 Dialog Duration Avg(STD)Max : 0.0(0.0)0.
Syntax Description 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.
Example 10 Display format without DETAIL option ACS Domain: domain-name System system-name1 Status subsystem-state Processor Status NOTE: 1. Use the STATUS command to track the progress of the START, STOP, or CONTROL commands. 2. ACS subsystem processes are available to process Pathsend requests if $ZACS is running and the ACS subsystem is in the STARTED state. 3. To display configuration information for an ACS object, use the INFO command.
NOTE: 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: 1. Stops all the ACS subsystem processes in the system except $ZACS. 2. Aborts all active transactions. The status of any outstanding transactions is unknown.
subsystem-name is the name of the subsystem. version-banner is the version banner for the subsystem. tos is the version of the Guardian kernel operating system. Txxxxvff is the product number and version. For example, T9082G06 indicates product number T9082, version G06. ddmmmyy is the compilation and release date for the ACS product module.
8 SCF Error Messages This section includes these topics: • “If You Have to Call Your Service Provider” (page 85) • “SCF Error Messages” (page 85) This section describes the SCF error messages returned by the ACS subsystem interface to the SCF utility. For more information on the list of SCF messages for all subsystems, see the SCF Reference Manual.
Recovery. Issue the command again with the correct attribute value. 00005 zacs^err^alter^inv ACS 00005 Error in executing ALTER command Cause. An ALTER ACS command was issued while the ACS subsystem was in the STARTING, STARTED, or STOPPING state. Effect. The command fails. Recovery. Use the STATUS command to check the current state of the ACS subsystem. Issue the ALTER ACS command again when the ACS subsystem is in the STOPPED state. 00006 zacs^err^case^val^inv ACS 00006 Error in command Cause.
Recovery. Use the STATUS command to check the current state of the ACS subsystem before issuing the STOP command again. 00012 zacs^err^acs^alrdy^started 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.
Effect. The command fails. Recovery. Terminate the SCF session. Start a new SCF session 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” (page 85)) and contact your service provider. 00020 zacs^err^inv^cpu^count ACS 00020 Invalid processor count Cause. The number of processors specified in the command exceeds the maximum value of 16.
Cause. The option value specified in a command is not valid for TS/MP 2.5 or the ACS subsystem. Effect. The command fails. Recovery. Issue the command again specifying the correct values. 00026 zacs^err^file^io ACS 00026 File operation failed: file-name.file-system-error Cause. SCF encountered an error while processing the indicated operation. Effect. The command fails. Recovery. Issue the command again. If the problem persists, correct the condition that is causing the problem.
A Backing Out Your Installation to TS/MP 2.0 This appendix includes these topics: • “Planning the Backout” (page 90) • “Performing the Backout” (page 90) NOTE: Before backing out and returning to TS/MP 2.0, you must consult HP support if you have installed TS/MP 2.1 or later releases and have run applications that use Pathsend requestors. Planning the Backout The following prerequisites are required before planning to back out your system: • TS/MP 2.0 cannot reside in the same system as TS/MP 2.5.
This attribute is mandatory. CPU ALL specifies that the ROUT processes will be started in all processors of the system. This attribute-value pair is mandatory. DEFAULTVOL $SYSTEM.SYSTEM specifies the physical location where the TS/MP 2.0 LINKMON software is installed. The value must be $SYSTEM.SYSTEM even if the TS/MP 2.0 LINKMON software is installed at $SYSTEM.SYSnn. The $ZZKRN process always searches for the ROUT software first at $SYSTEM.SYSTEM, and then at the current $SYSTEM.SYSnn location.
Glossary A-B 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. Application Cluster Services (ACS) subsystem An infrastructure used by transaction-processing middleware products to manage and access server classes.
process broker (PB) process A process that executes in each processor within a system to manage the resources and link reservations for the processor. NOTE: product module The PB is part of the ACS Subsystem. A process that resides in each ACS subsystem for communicating with SCF. The product module is responsible for subsystem-specific command processing. Q-R redirector (RD) process Processes that provide link management functionality to Pathsend requestors.
Index deleting, 72 description of, 14 Symbols ! command, 48 A ACS Starting, 57 ACS not yet started (SCF 00017), 87 ACS object (SCF) adding, 66 name and states, 64 ACS object cannot be deleted (SCF 00007), 86 ACS object does not exist (SCF 00018), 87 ACS subsystem architecture, 12 auto-restart, 27 configuration limits, 20 configuring, 57 descriptions of components, 14 displaying information about, 60 management interface, 15 manager process, 56 managing, 59 modifying the configuration, 59 overview, 28 prod
Format is specified more than once (SCF 00023), 88 ROUT process, replaced by $ZLnn, 14 H S HELP command (SCF), 39 HISTORY command, 45 HOMETERM attribute, 57 Security sensitive SCF commands, 63 Sensitive commands, 63 Special Characters ! command, 47 $ZACS process configuring, 56 description of, 14 starting, 57 $ZCSnn process description of, 14 $ZLnn process description of, 14 $ZNET (SCP) process, 62 $ZPnn process description of, 14 START command (SCF), 75 STARTED state (ACS objects), 64 Starting ACS sub
