TS/MP 2.5 Release Supplement

The DISABLE attribute is not functional. It is reserved for future use.DISABLE
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
LOG1 log-file-name:"format"
: "filter" and LOG2
or application program through the Event Management Service (EMS). Log files
LOG1 and LOG2 can be used to override a previously configured log file.
log-file-name: "format":
"filter"
LOG1 and LOG2 are optional parameters. If the specified file is not supplied for
LOG1 or LOG2 options, then that log is disabled. If the both logs are unusable
or disabled then ACS will use the $0.”EMS”:” ALL” for log messages.
specifies a Guardian disk file or process name. If you specify a disk file, an
unstructured file is automatically created if the file does not exist.
log-file-name
NOTE: If you turn off the logging function by closing a current log file, all the
internally queued messages are lost.
specifies the format in which the log messages are logged, enclosed in double
quotes (") character. Valid values are:
"format"
Log messages are formatted as event messages."EMS"
Log messages are formatted as text messages."TEXT"
specifies which type of messages are logged, enclosed in double quotes (")
character. Valid values are:
"filter"
Only fatal messages are logged."FATAL"
Messages of this level or higher 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"
All messages are logged."ALL"
specifies the ACSCTL configuration file that ACS subsystem reads to configure
the Pathway domain feature.
ACSCTL acsctl-file
For more information on ACSCTL file syntax, see “ACSCTL File Configuration”
(page 18).
specifies whether the ACS subsystem starts the ROUT process with high PIN
ON. If not specified, ACS subsystem starts the ROUT process with high PIN
OFF.
HIGHPINROUTS
Considerations
• This command creates the BCINI file in the $SYSTEM.SYSnn directory or in the default
volume. The BCINI file contains the SCF configuration for the ACS subsystem. If a BCINI file
already exists from a previous ADD command, the ADD command fails because only one ACS
object can exist in a system.
• Before the ADD command is run, all ACS messages are sent to $0.
• Any given attribute can appear only once in an ADD command.
• The state of an ACS object after being added is DEFINED.
Example 3 (page 68) shows how to add an ACS object to the local \MARS system and Example 4
(page 68) shows how to add an ACS object to the remote system \PLUTO.
ACS Subsystem-specific SCF Commands 67