TS/MP Release Supplement

ACS Subsystem
HP NonStop TS/MP Release Supplement546055-006
1-11
ACSCTL Configuration File Syntax
ACSCTL Configuration File Syntax
The ACSCTL file is a standard edit file using the following syntax definitions:
<file> = {[[<comment><eol>]&]<adsection><pdsection><osection>}
The syntax definition of the ACSCTL file sections is explained below:
<comment> = {#{any printable character}&}
<eol> = {?\n?}
<adsection> = {<sp>[ACS Domain]<sp><eol>[[<pline>]&]}
<pdsection> = {<sp>[Pathway Domain]<sp><eol>[[<dline>]&]}
<osection> = {<sp>[Owner Membership]<sp><eol>[[<oline>]&]}
<sp> = {{? ?|?\t?|NULL}&}
<pline> = {<adname>]<sp>=<sp><system>}
<dline> = {<pdname><sp>=<sp><PATHMON><sp>}
<oline> = {<owner><sp>=<sp><pdname>[,<sp><pdname>[,&]<sp>]<eol>}
<adname> = {ACS domain name}
<system> = {\{Valid NonStop system name on EXPAND network}}
<pdname> = {Pathway domain name}
<pathmon> = {<pname>[:<weight>]<sp>{[,<sp><pname>]&}}
<owner> = {NonStop user name }
<weight> = {percent of link requests to be provided by PATHMON based on the
processing capacity of a system available to the PATHWAY application}
<pname> = {NonStop system qualified PATHMON process name}
The following context checks are made in the above syntax:
The number of NonStop systems is limited to one.
The number of PATHMONs, used to define the Pathway domain, are limited to
four. However, there is no limit on the number of Pathway domains defined.
The PATHMON weight values associated with a Pathway domain must add up to
100.
The following is an example of an
ACSCTL file that defines two Pathway domains %PMX
and
%PMY. The %PMX Pathway domain comprises of three different PATHMON
processes (
$PM1, $PM2, and $PM3) while %PMY Pathway domain comprises of two
different PATHMON processes (
$PM4 and $PM5). However, all PATHMON processes
run on only one NonStop system
\A. The owners of the environments are defined in
Note. The operational validity of the definitions in the ACSCTL file are verified at run time. The
syntactical definitions in the ACSCTL file are verified at the time of configuration and all errors
encountered are reported through the SCF interface.