Displays unit and server status.

pdls -d svr [-a [-b]]

• -a

Specifies that the unit and server status is to be displayed in DAT format.

• -b

When the -a option is also specified, specifies that a title line is to be displayed.

1. Return code 0 for the pdls -d svr command indicates normal termination, return code 4 indicates warning termination, and return code 8 indicates abnormal termination. When the return code is 8, see the previous message and eliminate the cause of the error.
2. For a HiRDB/Parallel Server, if a unit that does not contain the system manager is terminated abnormally or forcibly, the command may display the status at the time the unit was terminated until the system manager detects the unit's termination.
3. When the standby-less system switchover (effects distributed) facility is used, a server switched over to another unit is displayed as the target unit's server.
4. You can specify the -a [-b] option even if you omit -d svr (example: pdls -a -b).
5. When the standby-less system switchover (effects distributed) facility is used, a server subject to system switchover may be displayed on both source and target units.
6. Depending on the host and unit status, unit and server information may not be displayed (if all hosts and units are in error status, specifying the -b option displays only the title line).
7. Even though an error message is output, an error value return code may not be set. Therefore, you must check for both an error message and a value indicating abnormality in the return code to determine the execution result of the pdls -d svr -a [-b] command.
8. If HiRDB was started by the pdstart -r command, the pdls -d svr command terminates with return code 4.
9. If all front-end servers have been terminated by the pdstop -s command since HiRDB started, the pdls -d svr command terminates with return code 0.

• When the -a option is omitted
  

  HOSTNAME(aabbcc) UNITID SVID STATUS STARTTIME dd...d eeee ff...f gg...g hhiijj : : : : :

• When the -a option is specified
  

  "dd...d","eeee","ff...f","gg...g","hhiijj" : : : : :

• When the -a and -b options are both specified
  

  "HOSTNAME","UNITID","SVID","STATUS","STARTTIME" "dd...d", "eeee", "ff...f", "gg...g", "hhiijj"

Explanation

aabbcc

Time of pdls command execution (hour:minute:second).

dd...d

Host name (up to 32 characters).

eeee

Unit identifier (4 characters).

ff...f

Server name (up to 8 characters).

If the status of a unit is being displayed, ******** is displayed.

gg...g

Status information (up to 8 characters):

ACTIVE

Active

STOP

Stopped (server)

STOP(N)

Terminated normally by the pdstop command

STOP(F)

Terminated forcibly by the pdstop command

(-f option specified)

STOP(A)

One of the following:

• Abnormal termination was detected during system operation.
• Communication with unit bbbb or data reception from unit bbbb was disabled.
• Client connection failed on unit bbbb.

Execute the ps command on unit bbbb to see if the HiRDB process is active.

If the HiRDB process is active:

A communication error or service slowdown may have occurred on unit bbbb. Check the cause of the error on the basis of the message that was output before the KFPS05289-E message, enter the pdstop -z command to terminate the unit, then restart the unit.

If the HiRDB process is not active:

The HiRDB process may have terminated abnormally. Take an appropriate action according to the message output during the abnormal termination. To restart, execute the pdstart -x command.

START(I)

Waiting for execution of the database initialization utility (dictionary not initialized)

SUSPEND

The front-end server is waiting for recovery of the data dictionary RDAREA or startup of the dictionary server (in this case, remove the cause of the wait, and then start the front-end server by entering the pdstart -a command).

STARTING

Preparing for startup

STOPPING

Preparing for shutdown

TRNPAUSE:

Scheduling of a new transaction is suppressed

Scheduling of a new transaction is suppressed at the corresponding server. If the KFPS01160-E message has been issued, eliminate the cause of the space shortage for the system log. For details about determining the cause of a space shortage for the system log and how to handle the error, see Action to be taken by the HiRDB administrator when the available space is less than the warning value in the HiRDB Version 8 System Operation Guide.

hhiijj

Activation time (hour:minute:second).