Command Reference

10.5.5
- 10.5.4
- 10.5.3
- 10.0

Back Next

DISPLAY STATUS Command

Displays the current status of the Controller task, Command Handler subtask, and Condense subtask of a PowerExchange Condense started task or job.

Alternatively, on a Linux, UNIX, or Windows system, you can issue a pwxcmd displaystatus command from the command line, a batch file, or a script to a PowerExchange Condense process running on the local or a remote system.

Syntax

The syntax varies by platform.

On an i5/OS system, use the following syntax:

SNDPWXCMD CMDHDLRLIB(condlib) DTLCMD(DISPLAY) DISPLAYOPT(STATUS)

The condlib variable is the name of the library that contains the condense files, which you specified in the COND_DIR parameter of the CAPTPARM configuration file.

On an z/OS system, use the following syntax:

F task_name,DISPLAY STATUS

The task_name variable is the name of the Condense started task or batch job for which you want to display information. Usually, PowerExchange Condense runs as a started task.

Example Output

The following example output was produced by the DISPLAY STATUS command on z/OS:

PWX-26011 Command handler received command "DISPLAY STATUS"
****************** STATUS ************************
COMMAND_HANDLER NOT waiting
CONDENSE WAITING
PWX-26021 Controller waits on events ALL_TASK_SHUTDOWN, CMDH_ENDED, CONDENSE_ENDED, CHKPT_COND_DONE, CONDENSING_COMPLETE,
PWX-26022 Command Handler waits on events ALL_TASK_SHUTDOWN, GOT_A_COMMAND, CONDENSE_INIT_COMPLETE, CAPTURE_STARTUP_COMPLETE,
PWX-26023 Writer waits on events ALL_TASK_SHUTDOWN, START_CONDENSING, CAPTURE_STARTUP_COMPLETE,
PWX-26024 Writer is sleeping, waiting for an event or timeout
**************************************************

In this output, "CONDENSE WAITING" means that the Condense subtask is waiting for the number of minutes that is defined in the NO_DATA_WAIT parameter before starting the next condense cycle.

PWX-26021 reports the event types to which the Controller task responds. The Controller task has the following responses to these event types:

ALL_TASK_SHUTDOWN. The Controller waits for the CONDENSE_ENDED and CMDH_ENDED events to complete and then shuts down.

CMDH_ENDED. The Controller detects that the Command Handler subtask has ended.

CONDENSE_ENDED. The Controller detects that the Condense subtask has ended.

CHKPT_COND_DONE. The Controller deletes old CDCT records for which the retention period has expired.

CONDENSING_COMPLETE. The Controller does not respond to this event type.

PWX-26022 reports the event types to which the Command Handler responds. The Command Handler has the following responses to these event types:

ALL_TASK_SHUTDOWN. The Command Handler subtask ends.

GOT_A_COMMAND. The Command Handler processes the command.

CONDENSE_INIT_COMPLETE. The Command Handler flags certain commands, such as CONDENSE, as eligible for processing now that Condense initialization is complete.

CAPTURE_STARTUP_COMPLETE. The Command Handler subtask has completed initialization and is beginning its main processing.

PWX-26023 reports the event types to which the Condense subtask, also called the Writer, responds. The Condense subtask has the following responses to these event types:

ALL_TASK_SHUTDOWN. The Condense subtask ends.

START_CONDENSING. The Condense subtasks starts looking for changes for the next condense cycle.

CAPTURE_STARTUP_COMPLETE. The Condense subtask has completed initialization and is beginning its main processing.

Rename Saved Search

Table of Contents

Command Reference

Command Reference

DISPLAY STATUS Command

DISPLAY STATUS Command

Syntax

Example Output