TS/MP 2.5 Release Supplement

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

{ {[<system name>.]<pathmon name>}|<domain>}

Syntax Description

is the Expand name of the system containing the PATHMON process that must handle the

server link request.

is the process name of the PATHMON process that must handle the server link request.

is the Pathway domain name associated with the domain membership list.

<domain> is a character string and its definition is mentioned in Table 4 (page 24).

NOTE: The first character of an ACS environment must be %.

The Pathsend API and the ACSCTL file definition must follow the value characteristics defined

in the following table for the environment name.

Table 4 (page 24) specifies valid domain definitions for Pathway domain name.

Table 4 Valid Domain Definitions for Pathway Domain Name

Case SensitiveValid LengthValid Characters for Characters 2-8First Character

No2-8 characters- |_ | ‘a’ – ‘z’ | ‘A’ – ‘Z’ | ‘0’ – ‘9’%

Application Programming Compatibility and Pathway Domains

Any one of the PATHMON process names associated with the Pathway domain can be used to

access a set of PATHMON processes under the same domain and the domain name need not be

specified. This can be useful if a program has hard coded references to a PATHMON process

name and must access the set of PATHMON processes associated with a Pathway domain. You

can overwrite this functionality by setting bit 9 in the flags parameter of SERVERCLASS_SEND_,

SERVERCLASS_DIALOG_BEGIN_, SERVERCLASS_SENDL_,

SERVERCLASS_DIALOG_BEGINL_, SERVERCLASS_DIALOG_SENDL_,

SERVERCLASS_DIALOG_BEGINL64_, SERVERCLASS_DIALOG_SENDL64_, or

SERVERCLASS_SENDL64_ calls. In this case, the server class request is serviced by a process

controlled by the identified PATHMON process. If this bit is set and a Pathway domain name is

referenced, the Pathsend call initiation fails with error 29 (FEMissParam). If the PATHMON name

is not associated with a Pathway domain, this flag bit has no function.

NOTE: If a PATHMON is configured under multiple Pathway domains, the Pathsends issued with

that PATHMON’s name in the Pathsend API are treated as a domain send for the Pathway domain

that is configured last in the ACSCTL file having that PATHMON as a member. If you want the

Pathsend request to be served by a particular Pathway domain, you must use the Pathway domain

name in the Pathsend APIs.

Co-existence with other TS/MP systems

TS/MP 2.5 co-exists with Tuxedo (TS/MP 3.0) on the same NonStop system but not with TS/MP

2.0 or any version of TS/MP other than 3.0.

24 Application Cluster Services (ACS) Subsystem