UPDOWN Configuration Syntax

This Configuration is used on HPE NONSTOP only

Process availability information is collected by the CPU collector (STCPU) and passed to the EMS collector (STEMS). STEMS will combine this availability information with device data that it collects to form the group availability information. The groups, and the devices and processes that comprise them, are defined in the UPDOWN Configuration. The configuration syntax for the UPDOWN Configuration is as follows.


ADD OBJECT (<object-name>, <n>, ...)
ADD OSSOBJECT (<oss-object-pathname>, <no-of-processes>[, <logical-object-name>])
ADD PROCESS (<process-name>, ...)
ADD GROUP (<group-name>, {<dev-name> | <process-name> | <object-name>, <n>}, ...)

Syntax Elements



Enter the names of objects that are to be monitored.


Specifies the count of instances of the running object which are required for it to be considered 100% available.

ADD OSSOBJECT (used for OSS Object and Process availability monitoring)


Full pathname of the OSS object to be monitored (e.g. /usr/nonstop/webserver/bin/HTTPD).

  • Entry must start with a forward slash (/) followed by the full pathname.
  • This must be a regular file,
  • When monitoring an OSS object that is a Symbolic Link (symlink), use the target of the symlink,
  • If the pathname exceeds 60 characters a corresponding logical-object-name> must be specified otherwise the entry will be rejected.


The total number of processes to be running for the object to be considered 100% available.


An optional name, of up to 60 characters that can be given to an OSSOBJECT entity. An OSS object name may extend up to 1024 characters, which would be impossible to show in full on a Display and would be truncated. Therefore, a logical name should be used in these cases to create shorter identifier that can be accommodated. When the <logical-object-name> is specified, it will appear in the Records in place of the <oss-object-pathname> and should be used in any subsequent UPDOWN Group or AVAILABILITY Application definitions.

The <logical-object-name> must be unique within the UPDOWN Configuration and should not overlap with any GROUP names.



Enter the names of processes that are to be monitored, separated by commas. A process will be considered UP if the process name exists.


Adds a device, process or object to an UPDOWN group. This is used to group together entities that form part of an application or business group that is to be monitored for availability. Use the <group-name> parameter to add a unique name to identify the group.

Items added to the ADD GROUP parameter must be either a device, all of which are monitored by default, or an Object or Process that has already been added with the ADD OBJECT, ADD OSSOBJECT or ADD PROCESS statements.




System Devices

Do not add system devices to the UPDOWN Configuration as these are monitored by default.

The following devices are included/monitored in the UPDOWN Configuration by default:

  • Device processes with any of the following device types: 3, 4, 7, 11, 13, 27, 56, 58, 61, 62, 63

  • All CPUs

  • All IPB busses

No configuration is needed to include these devices.

OSS Configuration Rules

The following rules apply when adding OSS objects to the UPDOWN configuration:

  • Duplicate <logical-object-name> entries will be rejected on Configuration start-up.

  • Multiple OBJECT definitions are not permitted within a single ADD OSSOBJECT entry. Where this is required, each must be specified as a separate ADD OSSOBJECT entry.

Provide feedback on this article