NonStop NS-Series Operations Guide (H06.12+)

ManualsBrandsHP ManualsServerHP Integrity NonStop H-Series

Table 3-3 SCF Object States (continued)

ExplanationSubstateState

The object is in the hard-down state or

is physically inaccessible due to a

hardware error.

HARDDOWN

The object is inaccessible to user

processes.

INACCESSIBLE

The backup input/output (I/O) process

was asked to take over for the primary

I/O process before it had the proper

information.

PREMATURE-TAKEOVER

The input/output (I/O) process could

not obtain a necessary resource.

RESOURCE-UNAVAILABLE

The input/output (I/O) process is down

for an unknown reason.

UNKNOWN-REASON

The object is in transition to the

STOPPED state. No new links are

allowed to or from the object. Existing

links are in the process of being

deleted.

STOPPING

The flow of information to and from

the object is restricted. (It is typically

prevented.) A subsystem must clearly

distinguish between the type of

information that is allowed to flow in

the SUSPENDED state and that which

normally flows in the STARTED or

STOPPED state. In the SUSPENDED

state, the object must complete any

outstanding work defined by the

subsystem.

SUSPENDED

The object is in transition to the

SUSPENDED state. The subsystem

must clearly define the nature of the

restrictions that this state imposes on

its objects.

SUSPENDING

The object’s state cannot be determined

because the object is inaccessible.

UNKNOWN

Automating Routine System Monitoring

You can automate many of the monitoring procedures. Automation saves you time and helps

you to perform many routine tasks more efficiently.

Your operations environment might be using TACL macros, TACL routines, or command files

to perform routine system monitoring and other tasks. These items allow you to run many

procedures so that you can quickly determine system status, produce reports, or perform other

common tasks. The TACL Reference Manual contains an example that you can adapt to automate

system monitoring.

Example 3-2 contains an example of a command file you can use or adapt to check many of the

system elements:

Automating Routine System Monitoring 61