TS/MP Release Supplement

ManualsBrandsHP ManualsServerHP Integrity NonStop H-Series

HP NonStop TS/MP

Release Supplement

Abstract

This manual supplements the HP NonStop™ TS/MP manual set. It describes the new

features provided by TS/MP 2.3 and TS/MP 2.4; it is intended for system managers,

system operators, and application programmers using Pathway/ iTS 1.1 or Pathsend

programming under TS/MP 2.0, TS/MP 2.1, TS/MP 2.3, or TS/MP 2.4 environments.

Product Version

NonStop TS/MP 2.3 and 2.4

Supported Release Version Updates (RVUs)

This publication supports J06.03 and all subsequent J-series RVUs and H06.05 and all

subsequent H-series RVUs, until otherwise indicated by its replacement publications.

For TS/MP 2.4, you must be running J06.05 and all subsequent J-series RVUs and

H06.16 and all subsequent H-series RVUs.

Part Number Published

546055-006 November 2010

Summary of content (142 pages)

PAGE 1
HP NonStop TS/MP Release Supplement Abstract This manual supplements the HP NonStop™ TS/MP manual set. It describes the new features provided by TS/MP 2.3 and TS/MP 2.4; it is intended for system managers, system operators, and application programmers using Pathway/ iTS 1.1 or Pathsend programming under TS/MP 2.0, TS/MP 2.1, TS/MP 2.3, or TS/MP 2.4 environments. Product Version NonStop TS/MP 2.3 and 2.4 Supported Release Version Updates (RVUs) This publication supports J06.
PAGE 2
Document History Part Number Product Version Published 546055-002 TS/MP 2.3 December 2008 546055-003 TS/MP 2.3 and 2.4 May 2009 546055-004 TS/MP 2.3 and 2.4 July 2009 546055-005 TS/MP 2.3 and 2.4 May 2010 546055-006 TS/MP 2.3 and 2.
PAGE 3
Legal Notices  Copyright 2010 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
PAGE 4
PAGE 5
HP NonStop TS/MP Release Supplement Glossary Index Examples Figures Legal Notices What’s New in This Manual vii Manual Information vii New and Changed Information About This Manual xi Related Documentation xi Notation Conventions xii HP Encourages Your Comments vii xvi 1.
PAGE 6
1. ACS Subsystem (continued) Contents 1. ACS Subsystem (continued) Pathway Domain Support 1-18 Application Programming Compatibility and Pathway Domains 1-19 Coexistence with other TS/MP systems 1-19 Load Balancing PATHMON Link Requests in a Pathway Domain 1-19 Process Management 1-21 PATHTCP4 1-22 Statistics Collection 1-22 Error Handling 1-22 ACS Auto-Restart 1-22 Pathsend Errors 1-22 Event Management System (EMS) 1-23 Subsystem Control Facility (SCF) 1-23 2. Introduction to TS/MP 2.
PAGE 7
3. Introduction to TS/MP 2.4 (continued) Contents 3. Introduction to TS/MP 2.4 (continued) Centi-seconds Support for createdelay 3-5 4.
PAGE 8
7. Managing the ACS Subsystem (continued) Contents 7. Managing the ACS Subsystem (continued) Stopping the ACS Subsystem 7-3 8. SCF Command Reference for the ACS Subsystem Overview 8-1 Architecture 8-2 Supported Commands 8-3 ACS Object 8-4 Starting SCF 8-5 SCF Command Format 8-5 ACS Subsystem-specific SCF Commands 8-6 9. SCF Error Messages If You Have to Call Your Service Provider SCF Error Messages 9-2 9-1 A. Backing Out Your Installation to TS/MP 2.
PAGE 9
Figures Contents Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 8-1. ACS Subsystem Architecture: System View (Single NonStop System) 1-3 ACS Subsystem Architecture: Processor View 1-4 ACS Architecture with Pathway Domain 1-8 How Pathsend Requests are Processed by the ACS Subsystem SCF Management Interface for ACS Subsystem 8-2 Tables Table 1-1. Table 1-2. Table 1-3. Table 2-1. Table 2-2. Table 3-1. Table 8-1. Limits for Pathsend Requesters 1-13 TS/MP 2.
PAGE 10
Contents HP NonStop TS/MP Release Supplement—546055-006 vi
PAGE 11
What’s New in This Manual Manual Information HP NonStop TS/MP Release Supplement Abstract This manual supplements the HP NonStop™ TS/MP manual set. It describes the new features provided by TS/MP 2.3 and TS/MP 2.4; it is intended for system managers, system operators, and application programmers using Pathway/ iTS 1.1 or Pathsend programming under TS/MP 2.0, TS/MP 2.1, TS/MP 2.3, or TS/MP 2.4 environments. Product Version NonStop TS/MP 2.3 and 2.
PAGE 12
Changes to the 546055-005 Manual What’s New in This Manual • • • • • • • • • ° Table 1-2. TS/MP Capacity Increases Updated the description of Link Management on page 1-14. Added a Note about SCOBOL on page 1-17 . Updated a Note on page 1-17. Updated the description of how Pathsend requests use the ACS subsystem on page 1-17. Updated the description of Load Balancing PATHMON Link Requests in a Pathway Domain on page 1-19. Modified the title “Link Management” to “Event and Error Messages” on page 2-3.
PAGE 13
Changes to the H06.18/J06.07 Manual What’s New in This Manual • • • • Updated Process Management on page 1-21. Added ACS Auto-Restart on page 1-22. Removed the following steps from Restarting the ACS Subsystem on page 7-3: ° ° Stop the Pathsend Requesters Restart the Pathsend Requesters Updated Stopping the ACS Subsystem on page 7-3. Changes to the H06.18/J06.07 Manual • • • • • • • • • • Changed the title of Introduction to the ACS Subsystem in TS/MP 2.3 to ACS Subsystem on page 1-1.
PAGE 14
Changes to the 546055.002 Manual What’s New in This Manual • • • • • • • • • • • • • • • • Updated ACSCTL Configuration File Syntax on page 1-11. Updated introductory text on Configuration and Environment Limits on page 1-12. Updated Table 1-2, TS/MP Capacity Increases, on page 1-14. Added Table 1-2, TS/MP 2.3 Pathway Domain Limits, on page 1-14. Updated the following in the Pathsend API section: • • Note on page 1-16.
PAGE 15
About This Manual This manual supplements the HP NonStop™ TS/MP manual set. It describes the new features provided by TS/MP 2.4 and TS/MP 2.3 and is intended for system managers, system operators, and application programmers using Pathway/ iTS 1.1 or Pathsend programming under the TS/MP 2.0, TS/MP 2.1, TS/MP 2.3, or TS/MP 2.4 environments. Related Documentation This manual is one in a set of manuals for the TS/MP and Pathway/iTS products.
PAGE 16
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
PAGE 17
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
PAGE 18
Notation for Messages About This Manual a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]… !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program).
PAGE 19
Notation for Management Programming Interfaces About This Manual lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
PAGE 20
Change Bar Notation About This Manual UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type !r. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME !o. token-type ZSPI-TYP-STRING.
PAGE 21
1 ACS Subsystem The Application Cluster Services (ACS) provide link-management functions for applications using Pathsend requesters 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.
PAGE 22
Architecture Overview ACS Subsystem in a NonStop system. Only one instance of the domain coordinator process exists per NonStop system. The process broker, configuration subscriber, and redirector processes coordinate with other processes to provide link-management functions, as shown in Figure 1-1. The box encompassing the three processes indicates that they share memory and are tightly bound. If any of these processes fails, the other processes may fail soon thereafter.
PAGE 23
Architecture Overview ACS Subsystem Figure 1-1. ACS Subsystem Architecture: System View (Single NonStop System) CPU 0 PATHMON CPU 1 CPU n PATHCOM SCF Prod.Mod.
PAGE 24
Domain Coordinator Process ($ZACS) ACS Subsystem Figure 1-2. ACS Subsystem Architecture: Processor View In Any Processor in the same NonStop system In Any Processor Process Broker ($ZP nn) 3 TS/MP PATHMON Process Broker ($ZP nn) 6 2 ROUT ($ZL nn) ROUT ($ZL nn) 4 1 5 7 Requester Processes Server Processes Legend Possible additional communication Domain Coordinator Process ($ZACS) The domain coordinator process is the ACS subsystem manager process.
PAGE 25
ACS Subsystem Process Broker Process ($ZPnn) Process Broker Process ($ZPnn) The process broker manages links from the TS/MP PATHMON processes for Pathsend requests. The name of the process is $ZPnn, where nn is the number of the CPU in which the process is running. Configuration Subscriber Process ($ZCSnn) The configuration subscriber process publishes critical ACS subsystem configuration information to the other ACS subsystem processes.
PAGE 26
ACS Subsystem ACS Domains ACS Domains An ACS domain is a defined set of objects (resources) within a single physical NonStop system, which are controlled and managed as a unit by the ACS subsystem. The ACS subsystem and its resources are managed and controlled using the Subsystem Control Facility (SCF), as shown in Figure 8-1. You can use SCF commands to manage the ACS subsystem configuration. For more information on SCF and SCF commands, see Section 8, SCF Command Reference for the ACS Subsystem.
PAGE 27
ACS Subsystem Improved Application Availability For more information on the SCF interface and SCF commands for the ACS subsystem, see Section 8, SCF Command Reference for the ACS Subsystem. Before starting the TS/MP Pathsend requesters, you must first use SCF commands to start the ACS subsystem. For more information, see Starting the ACS Subsystem ($ZACS). Improved Application Availability ACS subsytem provides improved availability and scalability to the Pathway/iTS 1.
PAGE 28
ACS Subsystem Improved Application Availability Figure 1-3. ACS Architecture with Pathway Domain A C S C T L file % e n v 1 = \A .$ P M 1 , \A .$ P M 2 % e n v 2 = \A .$ P M 3 , \A .$ P M 4 BC % env1 $PM 1 CPU X PB SC1 ROUT $PM 2 cs SC1 C lie n t1 e n v 1 .S C 1 C lie n t2 e n v 1 .
PAGE 29
ACS Subsystem Pathway Domain Configuration Management 3. The ACS subsystem recognizes that the send request from requesters (Client1, Client2) is being sent to a Pathway domain and hence grabs a link (server process) from any one of the available PATHMON processes, $PM1 or $PM2. 4.
PAGE 30
ACS Subsystem ACSCTL File Configuration ACSCTL File Configuration The ACSCTL is a configuration file that defines constraints to the namespace used by the ACS subsystem. The file defines the associated PATHMON environments that comprise a Pathway domain. The following three sections must be defined in the ACSCTL file: ACS Domain section, the Pathway Domain section, and the Owner Membership section. ACS Domain Section The ACS Domain section defines the ACS domain being used for the current NonStop system.
PAGE 31
ACS Subsystem ACSCTL Configuration File Syntax ACSCTL Configuration File Syntax The ACSCTL file is a standard edit file using the following syntax definitions: = {[[]&]} The syntax definition of the ACSCTL file sections is explained below: = {#{any printable character}&} = {?\n?} = {[ACS Domain][[]&]} = {[Pathway Domain][[]&]} = {[Owner Membership][[
PAGE 32
ACS Subsystem Configuration and Environment Limits the owner membership section. Any user ID under the user name ACS.* is defined to be the owner of Pathway domain %PMX, while ACS.SMITH is the only owner of %PMY. [ACS Domain] # Name must match the name given in ADD ACS command # And the system name must match to the current system. A = \A [Pathway Domain] # Multiple PATHMONs on the same system %PMX = \A.$PM1:40, \A.$PM2:40, \A.$PM3:20 %PMY = \A.$PM4, \A.$PM5 [Owner Membership] ACS.* = %PMX ACS.
PAGE 33
ACS Subsystem Configuration and Environment Limits Table 1-1. Limits for Pathsend Requesters (page 1 of 2) Parameter Description TS/MP 2.3 TS/MP 2.4 Buffer length Maximum bytes for each server class send operation. 32,767 bytes 2,097,152 bytes Dialogs per requester Maximum active dialogs for each requester. 256 256 Dialogs per processor Approximate maximum active dialogs for each processor.
PAGE 34
ACS Subsystem Link Management Table 1-1. Limits for Pathsend Requesters (page 2 of 2) Parameter Description TS/MP 2.3 TS/MP 2.4 Requester send operation (per processor) Maximum outstanding send requests for all requesters in the processor. 4045 8191 Server classes Approximate maximum server classes to which all requesters in a processor can have outstanding sends. The exact number depends on the current memory utilization.
PAGE 35
ACS Subsystem System Management Interface Grouping long-running and short-running requests causes uneven response times and increases the number of links needed to maintain transaction throughput. If an application contains server programs that process both long and short-running requests, configure the server program to use multiple server classes in PATHMON. This separates the long and short-running requests into different queues.
PAGE 36
ACS Subsystem Pathsend API Pathsend API In TS/MP 2.3 and later versions, Pathsend APIs allow Pathway domain name syntax in place of the PATHMON process name. Note. SCOBOL Dialog and Send APIs also allow Pathway domain name syntax in place of the PATHMON process name. For more information on SCOBOL APIs, see the HP NonStop Pathway/iTS SCREEN COBOL Reference Manual. Figure 1-4 shows how Pathsend requests are processed by the ACS subsystem. Figure 1-4.
PAGE 37
ACS Subsystem Pathsend API 1. The application requester 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.
PAGE 38
ACS Subsystem Pathway Domain Support 9. Other process brokers in the system might also be requesting server processes from the PATHMON process at the same time. Server processes can be shared between process brokers if the MAXLINKS attribute is set to a value greater than 1. 10. Parallel requests to a server process are queued on the server's $RECEIVE file until they are handled by the server process.
PAGE 39
ACS Subsystem Application Programming Compatibility and Pathway Domains Table 1-3.
PAGE 40
ACS Subsystem Load Balancing PATHMON Link Requests in a Pathway Domain the distribution of link requests across PATHMONs is in line with the weights assigned to the PATHMONs. At low load levels, the link usage algorithm favors links that are more responsive. Requests are processed using the released links rather than requesting a new link. As a result, the load distribution of the links might appear uneven at low load levels, but this does not adversely affect the response time.
PAGE 41
ACS Subsystem Process Management 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.
PAGE 42
ACS Subsystem PATHTCP4 PATHTCP4 The PATHTCP4 and the Java library components of Pathway/iTS 1.1 support the Pathway domain name syntax in place of PATHMON name for SCOBOL SEND and DIALOG APIs. For compatibility purposes, the current name forms and their default values have been maintained. You are not required to make any changes to your SCOBOL application programs to do sends to Pathway domain.
PAGE 43
ACS Subsystem Event Management System (EMS) For information on the Pathsend API, link manager, and PDMCOM errors, see the TS/MP System Management Manual. Event Management System (EMS) The TS/MP PATHMON does not generate any new EMS messages. However, the ACS subsystem does generate EMS messages, which might require changes in message tokenization to conform to current standards. All operator messages, for TS/MP and for ACS, are documented in the Operator Messages Manual.
PAGE 44
ACS Subsystem Subsystem Control Facility (SCF) HP NonStop TS/MP Release Supplement—546055-006 1- 24
PAGE 45
2 Introduction to TS/MP 2.3 TS/MP 2.3 is a new version of TS/MP software, which can be used as replacement to TS/MP 2.0. This section includes these topics: • • • • • • • Overview of TS/MP 2.3 New and Changed Features New Pathsend Limits New PATHMON/Pathcom Configuration Limits New ACS Subsystem Enhanced PATHMON/PATHCOM Components Compatibility with TS/MP 2.0 Overview of TS/MP 2.3 TS/MP 2.3 is intended for Pathway/iTS 1.1 or Pathsend users running TS/MP 2.0. It does not apply to Tuxedo (TS/MP 3.
PAGE 46
Introduction to TS/MP 2.3 New and Changed Features The TS/MP 2.3 product has the following components: • • • • Pathsend system library Enhanced TS/MP PATHMON and Pathcom components ACS subsystem components New management interface (PDMI) Table 2-1 summarizes the architecture comparison of all TS/MP versions. Table 2-1. Architecture Comparison of TS/MP Versions TS/MP 2.3 TS/MP 2.1 TS/MP 2.
PAGE 47
Introduction to TS/MP 2.3 Applications Applications If you are not using any new feature from the TS/MP 2.3 product, you do not need to modify your existing application. However, as TS/MP 2.3 has new link management algorithms, you may want to make some configuration modifications in the existing application for performance tuning purposes. For information on how to modify the configuration of your existing application, see Link Management.
PAGE 48
Introduction to TS/MP 2.3 New PATHMON/Pathcom Configuration Limits configuration and processing limits to support a higher link capacity for client processes, and efficient acquisition and usage of server processes. TS/MP 2.3 is designed without any architectural limits. However, the practical limits may be lower depending on the physical hardware available on the system (for example, memory) or on file-system constraints.
PAGE 49
Introduction to TS/MP 2.3 Wild Card Support Table 2-2. New PATHMON Configuration Limits Item Limit Description MAXASSIGNS 8191 ASSIGNs per Pathway (and per server-class) MAXDEFINES 8191 DEFINEs per Pathway (and per server-class Wild Card Support The following server commands in PATHCOM allow management and operation of server objects, by specifying “*” as wildcard in the object names. • • • • • • FREEZE INFO START STATS STATUS STOP Note.
PAGE 50
Introduction to TS/MP 2.3 • • • • • Compatibility with TS/MP 2.0 LINKMON(ROUT) name: The ACS subsystem redirector process uses the $SYSTEM.SYSnn.ROUT file name and the $ZLnn process name as used by the LINKMON process in TS/MP 2.0 (although the content of the file and the functionality of the process is different). For information on the ACS subsystem components, see Architecture Overview.
PAGE 51
3 Introduction to TS/MP 2.4 TS/MP 2.4 is a new version of TS/MP software, which can be used as a replacement to TS/MP 2.0 and TS/MP 2.3. TS/MP 2.4 is derived from TS/MP 2.3. It provides the features supported by TS/MP 2.
PAGE 52
Introduction to TS/MP 2.4 Synchronous Upgrade class attributes. After a successful ALTER, the ACS subsystem queues all new Pathsend requests to this server class. 3. The FREEZE command is issued on all other PATHMONs and the altered server is THAWed. The ACS subsystem starts processing new requests that are queued. Because only the upgraded server is in THAW state and others servers are frozen, all requests go to the upgraded server. 4.
PAGE 53
Introduction to TS/MP 2.4 • • • • Improved Server Process Distribution FILE_COMPLETEL_ FILE_GETRECEIVEINFOL_ READUPDDATEXL REPLYXL For information on new file system APIs, see the Guardian Procedure Calls Reference Manual. Improved Server Process Distribution TS/MP 2.4 allows you to assign the weights to processors specified in the CPU attribute of the server class.
PAGE 54
Introduction to TS/MP 2.4 Limits Enhancement Table 3-1. Server Processes Distribution Step A: Server class is started and receives 20 requests at the same time. Step B: CPU 3 failed. All server processes on CPU 3 will get killed. But the static server processes will get auto-restarted on the other CPUs. (0, 1, and 2) Step C: When all the outstanding requests are replied to, dynamic server processes will stop. Step D: CPU 3 is reloaded and 20 new requests are issued at the same time.
PAGE 55
Introduction to TS/MP 2.4 Domain-level Commands Support Domain-level Commands Support TS/MP 2.4 supports domain-level commands such as OPEN, CONTROL, and STATUS in PDMCOM: Command Description ALTER-DOMAIN To achieve automated online upgrade. See ALTERDOMAIN Command. CONTROL DOMAIN To temporarily change the domain behavior. See CONTROL DOMAIN Command. HISTORY To display previous PDMCOM commands. See HISTORY Command. OPEN To open one or more PATHMONs or a Pathway domain. See OPEN Command.
PAGE 56
Introduction to TS/MP 2.
PAGE 57
4 Introduction to PDMCOM Pathway Domain Management Command interpreter (PDMCOM) is a new command line interface used to start PDMI. By default, it resides in $SYSTEM.SYSTEM, 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 in TS/MP 2.3, eliminates application outages through online changes to the Pathway configuration. Note.
PAGE 58
Introduction to PDMCOM PDMCOM RUN Options You can enter the remainder of the commands from your terminal, or you can create a command file that contains the commands and then run the commands in that file. Running PDMCOM interactively is most useful when you plan to enter only a few commands. It is a good way to monitor the status of objects, dynamically start and stop objects, run a program, and send messages to user terminal operators about changing conditions.
PAGE 59
Introduction to PDMCOM Using PDMCOM in Noninteractive Mode message number 1002 in a TERM status report, you can determine the meaning of that number by entering: PDMI 4>> HELP 1002. In response, PDMCOM displays: PATHMON STATUS - *1002* ABORTED Using PDMCOM in Noninteractive Mode To specify lengthy configurations, create a command file or a TACL routine that contains your PDMCOM commands. This method permits PDMCOM to read and act upon the commands very quickly.
PAGE 60
Introduction to PDMCOM Using PDMCOM in Noninteractive Mode TACL Routines The TACL INLINE facility enables you to incorporate PDMCOM commands into a TACL routine to manage multiple PATHMON environments. The following example displays a few lines from 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 ] . .
PAGE 61
Introduction to PDMCOM PDMCOM Commands PDMCOM Commands PDMCOM supports all the PATHCOM Commands and the commands listed below: • • • • • • • • • ALTER-DOMAIN Command CONTROL DOMAIN Command ENV Command FC Command HISTORY Command OPEN Command STATUS DOMAIN Command ! Command SERVER Commands Note. The RUN PROGRAM prog-name command does not execute from PDMCOM. ALTER-DOMAIN Command Use the ALTER-DOMAIN command to achieve an automated online upgrade of the domain-based Pathway applications.
PAGE 62
Introduction to PDMCOM ALTER-DOMAIN Command Considerations • • The ALTER-DOMAIN command is a combination of SERVER commands. When one of the SERVER commands fails to execute, the ALTER-DOMAIN command terminates abnormally. However, the SERVER commands executed till the failure occurs are irreversible. During ALTER-DOMAIN command execution, the server entry is locked such that no other STOP, START, FREEZE, THAW, ALTER, or ALTER-DOMAIN command can be issued for this server throughout the domain.
PAGE 63
Introduction to PDMCOM CONTROL DOMAIN Command $Z11M: SERVER SVR2, $Z11M: SERVER SVR2, PATHMON : \ACS.$PM4 $Z11M: SERVER SVR2, $Z11M: SERVER SVR2, $Z11M: SERVER SVR2, THAWED STARTED STOPPED THAWED STARTED 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.
PAGE 64
Introduction to PDMCOM • CONTROL DOMAIN Command You can partition up to 128 server classes per domain.
PAGE 65
Introduction to PDMCOM CONTROL DOMAIN Command Example Configure a PDMCOM, %pdm, with $PM1, $PM2, $PM3, and $PM4 and then execute the CONTROL DOMAIN command: PDMI 1>> open %pdm PATHMON : \ACS.$PM3 PATHMON : \ACS.$PM1 PATHMON : \ACS.$PM2 PATHMON : \ACS.$PM4 PDMI 2>> status domain PATHMON WEIGHT STATUS \ACS.$PM3 70 RUNNING \ACS.$PM1 10 RUNNING \ACS.$PM2 10 RUNNING \ACS.
PAGE 66
Introduction to PDMCOM ENV Command 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.$PM2 PATHMON : \NSSYS.$PM3 PDMI 2>> env PATHMON : \NSSYS.$PM1 PATHMON : \NSSYS.$PM2 PATHMON : \NSSYS.$PM3 PDMI 3>> open $PM4 PATHMON : \NSSYS.$PM4 PDMI 4>> env PATHMON : \NSSYS.
PAGE 67
Introduction to PDMCOM FC Command Considerations • You can enter subcommands and their associated strings beneath 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 subcommand (R,I,D). Subcommand R replaces characters in the command line with replacementstring on a one-for-one basis.
PAGE 68
Introduction to PDMCOM • HISTORY Command If the following commands are entered at the PDMCOM prompt: \NSSYS.$VOL.SUBVOL 11> PDMCOM PDMI - T0845H02 - (01MAY2009) - 01 April 2009, 15:34:49 (C)2008 Hewlett Packard Development Company, L.P. PDMI 1>> [ SERVER SRV1 is configured in $PM1 PDMI 2>> OPEN $PM1 PATHMON : \NSSYS.$PM1 PDMI 3>> ALTER SRV1, NUMSTATIC 1 PATHMON : \NSSYS.
PAGE 69
Introduction to PDMCOM • • HISTORY Command The HISTORY command displays command numbers for each command. You can use command numbers in the FC and ! commands. The HISTORY command can display a maximum of 99 commands. Example When the following commands are executed at PDMCOM prompt: PDMI 1>> OPEN $PM1 PATHMON : \NSSYS.$PM1 PDMI 2>> OPEN $PM2 PATHMON : \NSSYS.$PM2 PDMI 3>> OPEN $PM3 PATHMON : \NSSYS.$PM3 PDMI 4>> OPEN $PM4 PATHMON : \NSSYS.$PM4 PDMI 5>> OPEN $PM5 PATHMON : \NSSYS.
PAGE 70
Introduction to PDMCOM OPEN Command OPEN Command Use the OPEN command to open one or more PATHMONs or a Pathway domain. OPEN { domain name } { pathmon name [ , pathmon name ... ] } domain name specifies the name of the Pathway domain to be opened. The domain name must start with '%'. Note. The domain name is supported by TS/MP 2.4 and is available only on systems running J06.05 and later J-series RVUs and H06.16 and later H-series RVUs.
PAGE 71
Introduction to PDMCOM STATUS DOMAIN Command STATUS DOMAIN Command Use the STATUS DOMAIN command to get the status of the domain. STATUS DOMAIN Note. The STATUS DOMAIN command is supported by TS/MP 2.4 and is available only on systems running J06.05 and later J-series RVUs and H06.16 and later H-series RVUs. Display Format The format of the display returned by the STATUS DOMAIN command is shown in Example 4-1. The fields are described below. Example 4-1.
PAGE 72
Introduction to PDMCOM ! Command Example To display the status of the domain opened by the OPEN domain name command: PDMI 1>> OPEN %dom PATHMON : \NSSYS.$PM1 PATHMON : \NSSYS.$PM2 PATHMON : \NSSYS.$PM3 PDMI 2>> STATUS DOMAIN PATHMON WEIGHT STATUS $PM1 50 RUNNING $PM2 20 RUNNING PARTITIONS SERVER2 SERVER3 $PM3 30 RUNNING SERVER4 ! Command Use the ! command to execute an existing command. ! [ [-]number | string ] number is the number of a command line.
PAGE 73
Introduction to PDMCOM ! Command Example • If the following commands are entered at the PDMCOM prompt: \NSSYS.$VOL.SUBVOL 11> PDMCOM PDMI - T0845H02 - (01MAY2009) - 01 April 2009, 15:34:49 (C)2008 Hewlett Packard Development Company, L.P. PDMI 1>> [ SERVER SRV1 is configured in $PM1 PDMI 2>> OPEN $PM1 PATHMON : \NSSYS.$PM1 PDMI 3>> ALTER SRV1, NUMSTATIC 1 PATHMON : \NSSYS.
PAGE 74
Introduction to PDMCOM SERVER Commands SERVER Commands From TS/MP 2.
PAGE 75
5 Migrating Applications to TS/MP 2.3 and Later Versions This section includes these topics: • • TS/MP 2.3 Environment Similarities TS/MP 2.3 Environment Differences Note. The migration details desribed in this section are applicable to TS/MP 2.3 and later versions. All TS/MP 2.0 applications that use Pathsend requesters and TS/MP configuration scripts (also called OBEY files) can run in a TS/MP 2.3 environment.
PAGE 76
Migrating Applications to TS/MP 2.3 and Later Versions TS/MP 2.3 Environment Differences TS/MP 2.3 Environment Differences TS/MP 2.3 is different from TS/MP 2.0 in the following ways: • • • • • • • • • Process name: For applications using Pathsend requesters, PATHMON processes communicate with the process broker process ($ZPnn); they no longer communicate with the link manager process, $ZLnn. The $ZLnn process continues to perform link management functions.
PAGE 77
Migrating Applications to TS/MP 2.3 and Later Versions TS/MP 2.3 Environment Differences required for functional compatibility are now supplied by the ACS subsystem; minimal, if any, updates to your applications are needed. For information on ACS subsystem Pathsend API errors, see the TS/MP System Management Manual.
PAGE 78
Migrating Applications to TS/MP 2.3 and Later Versions TS/MP 2.
PAGE 79
6 Installing and Configuring This section includes these topics: • • • • Prerequisites Installing TS/MP 2.3 / 2.4 versions Configuring and Starting the ACS Subsystem Starting TS/MP PATHMON and Requesters Note. Before starting TS/MP PATHMON processes or Pathsend requesters, you must install TS/MP 2.3 or later versions, configure, and start the ACS subsystem. The installation and configuration steps of TS/MP 2.3 are also applicable for later versions.
PAGE 80
Installing and Configuring Installing TS/MP 2.3 / 2.4 versions Installing TS/MP 2.3 / 2.4 versions Use the standard Distributed Systems Management/Software Configuration Manager (DSM/SCM) installation tool to install TS/MP 2.3 or TS/MP 2.4. Perform the following steps to install TS/MP 2.3: Note. The installation procedure for TS/MP 2.4 is exactly the same as that for TS/MP 2.3. The following procedure uses TS/MP 2.
PAGE 81
Installing and Configuring Migration Considerations $ZZKRN process to use the ROUT program file residing at the current SYSnn subvolume. The TS/MP 2.0 LINKMON or ROUT program file is always installed at current SYSnn, and the $ZZKRN process always uses the ROUT program file at the current SYSnn subvolume to start the ROUT process during the system load, or a processor reload, or when the ROUT process must be restarted. As a result, the $ZZKRN process acts as the process manager for TS/MP 2.
PAGE 82
Installing and Configuring Migration Considerations Symbolic Name Name State Sub Primary Backup PID PID None None ROUT $ZL00 STOPPED ROUT $ZL01 STOPPED None None ROUT $ZL02 STOPPED None None ROUT $ZL03 STOPPED None None ROUT $ZL04 STOPPED None None ROUT $ZL05 STOPPED None None ROUT $ZL06 STOPPED None None 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
PAGE 83
Installing and Configuring Configuring and Starting the ACS Subsystem c. Change the name of the renamed TS/MP 2.3 ROUT program file in the latest SYSnn subvolume, back to ROUT, as follows: TACL>RENAME $SYSTEM.., $SYSTEM..ROUT • • • The TS/MP 2.0 LINKMON or ROUT process in each processor is started implicitly when the processor is initially loaded or reloaded. The TS/MP 2.3 processes in each processor are started when the ACS subsystem is started.
PAGE 84
Installing and Configuring Configuring the Domain Coordinator Process ($ZACS) STOPMODE STANDARD, HOMETERM home-term & where: PROGRAM $SYSTEM.SYSnn.BC specifies the physical file name of the ACS domain coordinator process. This file is located in the ACS installation subvolume (ISV) of the ACS components. This attribute is mandatory. DEFAULTVOL $SYSTEM.SYSnn specifies the physical location where the ACS software and the ACS subsystem configuration file (BCINI) is installed. This attribute is mandatory.
PAGE 85
Installing and Configuring Starting Domain Coordinator Process ($ZACS) 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.
PAGE 86
Installing and Configuring Starting the ACS Subsystem ($ZACS) Example 6-1. SCF ADD Command for Adding and Configuring ACS Subsystem ADD ACS $ZACS, DOMAIN "MARS" , & HIGHPINROUTS ON , & ALL , ENABLE , & LOG1 $APPS.LOGFILES.LOG1:"EMS":"ALL" , & LOG2 $APPS.LOGFILES.LOG2:"TEXT":"ERROR" , & ACSCTL $SYSTEM.ZACS.ACSCTL Starting the ACS Subsystem ($ZACS) This step starts the ACS subsystem. When this step is completed, the ACS subsystem functions can be used by Pathsend applications.
PAGE 87
7 Managing the ACS Subsystem This section includes these topics: • • • • • 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 ACS Subsystem Stopping the ACS Subsystem Modifying the Configuration Use the SCF ALTER command to permanently modify attribute values for the ACS
PAGE 88
Managing the ACS Subsystem Displaying Information 5. Use the START command to start the ACS subsystem. The ACS subsystem functions are available again, according to the new (and permanent) values you specified. For more information on this command, see START Command. Note. You can use the CONTROL command to modify the configuration of the ACS subsystem without stopping it. For more information on the CONTROL command, see CONTROL Command on page 8-12.
PAGE 89
Managing the ACS Subsystem Restarting the ACS Subsystem the ACS subsystem, not the ACS subsystem configuration. For more information on this command, see CONTROL Command. For example: CONTROL ACS $ZACS, PROCESSORLIST (2, 3), ENABLE Restarting the ACS Subsystem A complete description for configuring and starting the ACS subsystem during installation of TS/MP 2.3 (or later version) is described in Section 6, Installing and Configuring.
PAGE 90
Managing the ACS Subsystem Stopping the ACS Subsystem 2. Stop the ACS Subsystem 1. Use the SCF STOP command to stop the ACS subsystem. For more information on this command, see STOP Command. For example: STOP ACS $ZACS, FORCED 2. Use the SCF STATUS command to verify that the ACS subsystem has stopped. For more information on this command, see STATUS Command. For example: STATUS ACS $ZACS, DETAIL 3. Stop the $ZACS Process 1.
PAGE 91
8 SCF Command Reference for the ACS Subsystem This section includes these topics: • • • • • • • Overview Architecture Supported Commands ° ° List of ACS Subsystem-specific Commands Syntax Help for SCF Commands ACS Object Starting SCF SCF Command Format ACS Subsystem-specific SCF Commands ° ° ° ° ° ° ° ° ° ° ° ADD Command ALTER Command CONTROL Command DELETE Command INFO Command NAMES Command START Command STATS Command STATUS Command STOP Command VERSION Command Overview The Subsystem Control Facili
PAGE 92
SCF Command Reference for the ACS Subsystem Architecture The ACS subsystem-specific SCF commands control and inquire about the ACS object. This section describes the SCF commands that are interpreted specifically for ACS. The SCF Reference Manual provides general information about SCF commands. You must be familiar with the SCF commands before reading the ACS subsystemspecific information provided here.
PAGE 93
SCF Command Reference for the ACS Subsystem Supported Commands (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. The domain coordinator process must be started before you can run any ACSspecific SCF commands.
PAGE 94
SCF Command Reference for the ACS Subsystem ACS Object Table 8-1. SCF Commands for ACS Subsystems Command SCF Sensitive SCF Nonsensitive Valid in These States STATUS - X UNKNOWN, DEFINED, STARTING, STARTED, STOPPING, STOPPED STOP X - STARTING, STARTED VERSION - X UNKNOWN, DEFINED, STARTING, STARTED, STOPPING, STOPPED SCF sensitive commands can change the state or configuration of subsystem objects. Therefore, the use of sensitive commands is restricted to users with special qualifications.
PAGE 95
SCF Command Reference for the ACS Subsystem Starting SCF 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.
PAGE 96
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands object-spec specifies the object type, and one or more object names. The object type identifies the product module ($ZNET) to which the command is addressed. The object name identifies the specific objects to which the command is directed. The exceptions to this format are commands that are directly processed by SCF itself, for example, the ASSUME command.
PAGE 97
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands Syntax Summary ADD [/OUT /] {, DOMAIN } {, { ALL } ,{ENABLE | DISABLE} } [, ACSCTL ] [, LOG1 [::]] [, LOG2 [::]] [, HIGHPINROUTS {ON | OFF}] Syntax Description OUT file-spec specifies a file for the output of this command.
PAGE 98
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands ALL specifies that ACS subsystem functions are configured for all processors in the system. This attribute is mandatory. Note. For TS/MP 2.3, the ACS subsystem functions are automatically configured for all CPUs in the system. ENABLE For TS/MP 2.3, the ENABLE attribute is required but not functional. DISABLE For TS/MP 2.3, the DISABLE attribute is not functional. It is reserved for future use.
PAGE 99
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands "FATAL" Only fatal messages are logged. "ERROR" Messages of this level or higher are logged. "WARNING" Messages of this level or higher are logged. "STATUS" Messages of this level or higher are logged. "INFO" Messages of this level or higher are logged. "ALL" All messages are logged. ACSCTL acsctl-file specifies the ACSCTL configuration file that ACS subsystem reads to configure the Pathway domain feature.
PAGE 100
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands Example 8-2. 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.ACSCTL ALTER Command Use the ALTER command to modify the configuration of an existing ACS subsystem.
PAGE 101
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands object-spec specifies the name of the ACS object. The fully qualified object-spec has the format: [ ACS ] [ system-name.]$ZACS is the physical, Guardian name of the system in which the object is being added and configured. system-name If you have specified 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.
PAGE 102
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands "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" Only fatal messages are logged. "ERROR" Messages of this level or higher are logged. "WARNING" Messages of this level or higher are logged. "STATUS" Messages of this level or higher are logged.
PAGE 103
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands This command is updated to enable the changing of LOG file and to update the ACSCTL file after ACS has started. Note. The ACS sub-system must be in the STARTED state when this command is issued.
PAGE 104
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands ENABLE restarts the ACS subsystem processes in the specified CPUs, if required. LOG1 and LOG2 The new LOG1 and LOG2 options instruct all processors to stop using their current log file and start using the new specified file. If the specified file is not supplied, that log is disabled. If both logs are unusable or disabled, ACS uses $0.”EMS”:”ALL” for log messages. For more information, see ADD Command.
PAGE 105
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands For more information on the ACSCTL file syntax, see ACSCTL File Configuration. Note. Not following the above-mentioned procedures can produce an inconsistent ACS environment. Any syntax error in the ACSCTL file will cause the CONTROL command to fail. All new errors have been documented in the TS/MP Reference Manual. Example 8-3 shows an old ACSCTL file and Example 8-4 shows a new ACSCTL file. Example 8-3.
PAGE 106
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands The new ACSCTL file removes PATHMON \A.$PM3 from Pathway domain %PMX. To update the ACS subsystem with the new ACSCTL file, perform the following steps: 1. Shutdown all PATHMONs in the Pathway domain %PMX. 2. Update the ACSCTL file. 3. Use the CONTROL command and ACSCTL option. 4. Start PATHMONs \A.$PM1 and \A.$PM2.
PAGE 107
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands object-spec specifies the name of the ACS object to be deleted. The fully qualified objectspec 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 have specified 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.
PAGE 108
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands 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. 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.
PAGE 109
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands \system-name.object-name is the name of the physical system from which the command was run and the name of the ACS object. domain-name is the name of the ACS domain. nnnnnnnnnnnnnnnn are the processors in which the ACS subsystem processes are enabled. Each digit represents a specific processor, beginning with CPU 0 on the left through CPU 15 on the far right.
PAGE 110
SCF Command Reference for the ACS Subsystem Application Cluster Services ACS Subsystem-specific SCF Commands INFO ACS \MARS.$ZACS ZACS *Domain.............MARS Processor status...1111111111111111 *LOG1...............\MARS.$VOL1.LOGFILES.LOG1 *LOG2...............\MARS.$VOL1.LOGFILES.LOG2 *ACSCTL.............\MARS.$SYSTEM.ZACS.ACSCTL *HIGHPINROUTS........OFF In this example, the MARS domain is located in the \MARS system and the ACS subsystem processes are up and running in all available CPUs.
PAGE 111
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands If you have specified the SCF object type (ACS) or any portion of the object name (acs-spec) in a prior ASSUME command, you can omit it in this command. For information on the ASSUME command, see the SCF Reference Manual. If you have not used a prior ASSUME command and you omit system-name, the command defaults to the local physical system.
PAGE 112
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands Syntax Summary START [ /OUT file-spec/ ] [ object-spec ] 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.
PAGE 113
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands Syntax Summary STATS [/OUT ] {[,DETAIL] [,RESET]} Syntax Description DETAIL breaks down the processor statistics on a Pathway domain, server class basis. RESET resets the ACS subsystems internal counts in its associated system. Note. The RESET option does not reset the internal counts maintained within the PATHMON and Pathcom processes.
PAGE 114
SCF Command Reference for the ACS Subsystem • ACS Subsystem-specific SCF Commands Average, Standard Deviation, and Maximum for the time it takes to perform a server class dialog (from Dialog begin to Dialog end) Example Command Output ->STATS ACS \A.$ZACS,DETAIL PROCESSOR : 00 Domain Count SrvClass Count Link Count Link Max Requester Count Send Avg (STD) Send Max 02 03 08 08 01 2.0(3.3) 08 DOMAIN : \A.%PDM1 SERVERCLASS: \A.$PM2.
PAGE 115
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands Domain Count SrvClass Count Link Count Link Max Requester Count Send Avg (STD) Send Max 00 00 00 00 00 0.0(0.0) 00 PROCESSOR: 01 Domain Count SrvClass Count Link Count Link Max Requester Count Send Avg (STD) Send Max 00 00 00 00 00 0.0(0.0) 00 STATUS Command Use the STATUS command to display the current operational status of the ACS subsystem.
PAGE 116
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands 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 must include additional detail information. Example 8-7 shows the display format with DETAIL option. Example 8-7.
PAGE 117
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands acsctl-location is a fully qualified ACSCTL file location given in ADD or Control command. acsctl-state the state of the ACSCTL file. Valid values are ACTIVE and INACTIVE. Example 8-8 shows a display format without the DETAIL option. Example 8-8. Display format without DETAIL option ACS Domain: domain-name System system-name Status Processor Status subsystem-state Note. 1.
PAGE 118
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands STOP Command 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. SCF displays a prompt asking you to verify the command before the command is run. This is a sensitive command.
PAGE 119
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands Examples The following command immediately stops the ACS subsystem on the local system \MARS: STOP ACS $ZACS, FORCED The following command immediately stops the ACS subsystem on the remote system \PLUTO: STOP ACS \PLUTO.$ZACS, FORCED VERSION Command Use the VERSION command to display the ACS subsystem version number and other version information. This is a nonsensitive command.
PAGE 120
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands Example 8-9 shows the display format with the DETAIL option. Example 8-9. Display Format with DETAIL Option VERSION ACS object-name SYSTEM system-name subsystem-name version-banner GUARDIAN- T9050 -tos SCF KERNEL- Txxxxvff - ddmmmyy - ddmmmyy ACS PM- Txxxxvff - ddmmmyy - AAA - ddmmmyy object-name is the name of the object. system-name is the name of the physical system on which the subsystem is configured.
PAGE 121
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands displays the following version information for the local system \MARS: VERSION ACS \MARS.$ZACS SYSTEM \MARS ACS Version 1.
PAGE 122
SCF Command Reference for the ACS Subsystem ACS Subsystem-specific SCF Commands HP NonStop TS/MP Release Supplement—546055-006 8- 32
PAGE 123
9 SCF Error Messages This section includes these topics: • • If You Have to Call Your Service Provider SCF Error Messages 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.
PAGE 124
SCF Error Messages SCF Error Messages 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.
PAGE 125
SCF Error Messages SCF Error Messages 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.
PAGE 126
SCF Error Messages SCF Error Messages 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. A STOP ACS command was issued while the ACS subsystem was already in the STOPPED state. Effect.
PAGE 127
SCF Error Messages SCF Error Messages 00018 ACS object does not exist ACS 00018 ACS object does not exist Cause. The ACS object specified in the command does not exist. Effect. The command fails. Recovery. Issue the command again and specify 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.
PAGE 128
SCF Error Messages SCF Error Messages 00022 zacs^err^required^attr ACS 00022 Required attributes are missing Cause. A required attribute was missing from the command. Effect. The command fails. Recovery. Issue the command again and include all required attributes. 00023 zacs^err^dup^format ACS 00023 Format is specified more than once Cause. The format value for a LOG1 or LOG2 attribute in an ADD or ALTER command was specified more than once. Effect. The command fails. Recovery.
PAGE 129
SCF Error Messages SCF Error Messages 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. 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.
PAGE 130
SCF Error Messages SCF Error Messages HP NonStop TS/MP Release Supplement—546055-006 9 -8
PAGE 131
A Backing Out Your Installation to TS/MP 2.0 This appendix includes these topics: • • Planning the Backout Performing the Backout 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 requesters. Planning the Backout You must fulfill the following prerequisites before planning to backout your system: • • • • TS/MP 2.0 cannot reside in the same system as TS/MP 2.1 or later releases.
PAGE 132
Backing Out Your Installation to TS/MP 2.0 Adding TS/MP 2.0 LINKMON Configuration Adding TS/MP 2.0 LINKMON Configuration The TS/MP 2.0 LINKMON must be added under the Kernel Subsystem Manager process ($ZZKRN)using the SCF ADD PROCESS command. To add the TS/MP 2.0 LINKMON configuration, use the SCF ADD PROCESS command interactively or in an OBEY file. ASSUME PROCESS $ZZKRN ADD PROCESS #ROUT, AUTORESTART 10, CPU ALL, DEFAULTVOL $SYSTEM.
PAGE 133
Backing Out Your Installation to TS/MP 2.0 Adding TS/MP 2.0 LINKMON Configuration specifies the name of the ROUT processes. Each ROUT process starting in a processor appends the two-digit decimal CPU number to $ZL. For example, the ROUT process starting in CPU 4 will start as $ZL04. This attribute-value pair is mandatory. PRIORITY 199 specifies the process priority of the ROUT processes. This attribute-value pair is mandatory. PROGRAM $SYSTEM.SYSTEM.
PAGE 134
Backing Out Your Installation to TS/MP 2.0 Adding TS/MP 2.
PAGE 135
Glossary Application Cluster Services (ACS) subsystem. An infrastructure used by transactionprocessing 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. client.
PAGE 136
Glossary Pathway Domain Management Command interpreter (PDMCOM) Pathway Domain Management Command interpreter (PDMCOM). A new command-line interface used to start PDMI and configure and operate on multiple Pathway environments at the same time. It is a superset of PATHCOM. Pathway Domain Management Interface (PDMI). A management interface with a set of commands for configuring, controlling, and monitoring multiple PATHMON processes.
PAGE 137
Glossary sensitive command group. Sensitive commands can change the state of the configuration of objects. See also nonsensitive command.
PAGE 138
Glossary sensitive command HP NonStop TS/MP Release Supplement—546055-006 Glossary- 4
PAGE 139
Index A ACS starting 6-8 ACS not yet started (SCF 00017) 9-4 ACS object cannot be deleted (SCF 00007) 9-3 ACS object does not exist (SCF 00018) 9-5 ACS object (SCF) adding 8-6 name and states 8-4 ACS subsystem architecture 1-1 auto-restart 1-22 configuration limits 1-1 configuring 6-7 descriptions of components 1-4 displaying information about 7-2 management interface 1-5 manager process 6-5 managing 7-1 modifying the configuration 7-1 overview 2-4 product module 1-5 start before Pathsend requesters 1-5 sta
PAGE 140
Index D CONTROL DOMAIN command 4-7/4-9 D DEFAULTVOL attribute 6-6 DEFINED state (ACS objects) 8-4 DELETE command (SCF) 8-16 DELETEDELAY attribute 5-2 Deleting characters 4-11 DETAIL attribute INFO command 8-17 STATUS command 8-25 VERSION command 8-29 Displaying ACS subsystem information 7-2 DOMAIN attribute 8-7 Domain coordinator process (see $ZACS process) 1-5 Domains description of ACS 1-5 management interface for 1-5 Filter is specified more than once (SCF 00024) 9-6 FORCED attribute (SCF) 8-28 Forma
PAGE 141
Index N $0 before ADD command 8-9 Migrating applications 5-1 Modifying subsystem configurations 7-1 N Nonsensitive commands 8-3 O Object names does not exist (SCF 00001) 9-2 OPEN command 4-14 Operational status, displaying 8-25 OUT attribute HELP command 4-12 overview of changes 2-1 P Pathsend requesters overview of new limits 2-3 processing steps by ACS subsystem 2-3 Performance and DELETEDELAY attribute 5-2 PM and subsystems versions are not compatible (SCF 00015) 9-4 PRIMARYCPU attribute 6-5 Process
PAGE 142
Index V V VERSION command 8-29 Special Characters ! command 4-16/4-17 $ZACS process configuring 6-5 description of 1-4 starting 6-7 $ZCSnn process description of 1-5 $ZLnn process description of 1-5 $ZNET (SCP) process 8-2 $ZPnn process description of 1-5 HP NonStop TS/MP Release Supplement—546055-006 Index -4