QUERY EVENT (Display client schedules)

Edit online

Use the QUERY EVENT command to display scheduled and completed events for selected clients.

Privilege class

Any administrator can issue this command.

Syntax

Parameters

domain_name (Required)

Specifies the name of the policy domain to which the schedules belong. You can use a wildcard character to specify this name.

schedule_name (Required)

Specifies the name of the schedule for which events are displayed. You can use a wildcard character to specify this name.

Type=Client

Specifies that the query displays events for client schedules. This parameter is optional. The default is CLIENT.

Nodes

Specifies the name of the client node that belongs to the specified policy domain for which events are displayed. You can specify multiple client nodes by separating the names with commas and no intervening spaces. You can use wildcard characters to specify nodes. If you do not specify a client name, events display for all clients that match the domain name and the schedule name.

BEGINDate

Specifies the beginning date of the time range for events to be displayed. All events scheduled to start during this time are displayed. This parameter is optional. The default is the current date.

You can specify the date using one of the values below:

Value	Description	Example
MM/DD/YYYY	A specific date	09/15/1998
TODAY	The current date	TODAY
TODAY+days or +days	The current date plus days specified. The maximum number of days you can specify is 9999.	TODAY +3 or +3.
TODAY-days or -days	The current date minus days specified	TODAY-7 or -7. To query events scheduled to start during the past seven days, specify BEGINDATE=TODAY-7 ENDDATE=TODAY or BEGINDATE=-7 ENDDATE=TODAY.
EOLM (End Of Last Month)	The last day of the previous month.	EOLM
EOLM-days	The last day of the previous month minus days specified.	EOLM-1 To include files that were active a day before the last day of the previous month.
BOTM (Beginning Of This Month)	The first day of the current month.	BOTM
BOTM+days	The first day of the current month, plus days specified.	BOTM+9 To include files that were active on the 10th day of the current month.

BEGINTime

Specifies the beginning time of the range for events to be displayed. All events scheduled to start during this time are displayed. This parameter is optional. The default value is 00:00.

You can specify the time using one of the values below:

Value	Description	Example
HH:MM:SS	A specific time on the specified begin date	10:30:08
NOW	The current time on the specified begin date	NOW
NOW+HH:MM or +HH:MM	The current time plus hours and minutes on the specified begin date	NOW+03:00 or +03:00. If you issue this command at 9:00 to query events scheduled to start 3 hours from now, you can specify either BEGINTIME=NOW+03:00 or BEGINTIME=+03:00. IBM Storage Protect displays events at 12:00 on the specified begin date.
NOW-HH:MM or -HH:MM	The current time minus hours and minutes on the specified begin date	NOW-04:00 or -04:00. If you issue this command at 9:00 to query events scheduled to start during the last 4 hours, you can specify either BEGINTIME=NOW-04:00 ENDTIME=NOW or BEGINTIME=-04:00 ENDTIME=NOW. IBM Storage Protect displays events at 5:00 on the specified begin date.

ENDDate

Specifies the ending date of the time range for events to be displayed. All events that were schedule to start during this time are displayed. This parameter is optional. The default is the value used for the BEGINDATE.

You can specify the date using one of the values below:

Value	Description	Example
MM/DD/YYYY	A specific date	09/15/1998
TODAY	The current date	TODAY
TODAY+days or +days	The current date plus days specified. The maximum number of days you can specify is 9999.	TODAY +3 or +3.
TODAY-days or -days	The current date minus days specified	TODAY-8 or -8. To query events scheduled to start during a one-week period that ended yesterday, you can specify either BEGINDATE=TODAY-8 ENDDATE=TODAY-1 or BEGINDATE=-8 ENDDATE=-1.
EOLM (End Of Last Month)	The last day of the previous month.	EOLM
EOLM-days	The last day of the previous month minus days specified.	EOLM-1 To include files that were active a day before the last day of the previous month.
BOTM (Beginning Of This Month)	The first day of the current month.	BOTM
BOTM+days	The first day of the current month, plus days specified.	BOTM+9 To include files that were active on the 10th day of the current month.

ENDTime

Specifies the ending time of the range for events to be displayed. All events that were scheduled to start during this time are displayed. This parameter is optional. The default value is 23:59.

You can specify the time using one of the values below:

Value	Description	Example
HH:MM:SS	A specific time on the specified end date	10:30:08
NOW	The current time on the specified end date	NOW
NOW+HH:MM or +HH:MM	The current time plus hours and minutes on the specified end date	NOW+03:00 or +03:00. If you issue this command at 9:00 to query events scheduled to start 3 hours from now, you can specify either BEGINTIME=NOW ENDTIME=NOW+03:00 or BEGINTIME=NOW ENDTIME=+03:00.
NOW-HH:MM or -HH:MM	The current time minus hours and minutes on the specified end date	NOW-04:00 or -04:00

EXceptionsonly

Specifies the type of information you want on scheduled or completed events. This parameter is optional. The default is NO. You can specify one of the following values:

No: Specifies that the information on past and projected events is displayed.
Yes: Specifies that the events that failed or did not process as scheduled are displayed.

Format

Specifies how information displays. This parameter is optional. The default is STANDARD. The following values are possible:

Standard: Specifies that partial information for events displays.
Detailed: Specifies that complete information for events displays.

Display partial information for unsuccessful events

Display partial information for all events that are scheduled for DOMAIN1 that did not run successfully. Limit the search to the client named JOE. Limit the events that are displayed to events that were scheduled to occur from February 11, 2001 (02/11/2001) to February 12, 2001 (02/12/2001).

query event domain1 * nodes=joe begindate=02/11/2001 
enddate=02/12/2001 exceptionsonly=yes

Scheduled Start      Actual Start          Schedule  Node    Status
                                            Name     Name
-------------------- --------------------  --------- ----   ---------
02/11/1999 01:00:00  02/11/1999 01:13:55   BACK1      JOE   Failed
02/12/1999 01:00:00                        DAILYBKP   JOE   Missed

See Field descriptions for field descriptions.

Display partial information for scheduled events for a client

Display complete information for all events that are scheduled for processing. Use the start time as 10 days previous to today, and the finish includes today.

query event * * begindate=today-10 enddate=today


Scheduled Start         Actual Start            Schedule Name    Node Name        Status
--------------------    --------------------    -------------    -------------    ---------
02/04/2013 14:00:00                             SCHD_INCR-DM1    TSM_CET_DM1      Missed
02/04/2013 14:00:00     02/04/2013 14:12:49     VDATAMVR1-IN1    VDATAMVR1-T1     Completed
02/04/2013 14:30:00     02/04/2013 14:33:10     VDATAMVR1-IN2    VDATAMVR1-T2     Completed
02/04/2013 15:00:00     02/04/2013 15:01:49     VDATAMVR1-IN3    VDATAMVR1-T3     Completed
02/04/2013 15:30:00     02/04/2013 15:42:00     VDATAMVR1-IN4    VDATAMVR1-T4     Completed
02/05/2013 14:00:00                             SCHD_INCR-DM1    TSM_CET_DM1      Missed
02/05/2013 14:00:00     02/05/2013 14:05:22     VDATAMVR1-F1     VDATAMVR1-F1     Completed
02/05/2013 14:30:00     02/05/2013 14:32:53     VDATAMVR1-F2     VDATAMVR1-F2     Failed 12
02/05/2013 15:00:00     02/05/2013 15:00:38     VDATAMVR1-F3     VDATAMVR1-F3     Completed
02/05/2013 15:30:00     02/05/2013 15:36:41     VDATAMVR1-F4     VDATAMVR1-F4     Completed
02/06/2013 14:00:00                             SCHD_INCR-DM1    TSM_CET_DM1      Missed
02/06/2013 14:00:00     02/06/2013 14:06:42     VDATAMVR1-F1     VDATAMVR1-F1     Completed
02/06/2013 14:30:00     02/06/2013 14:35:41     VDATAMVR1-F2     VDATAMVR1-F2     Completed
02/06/2013 15:00:00     02/06/2013 15:08:56     VDATAMVR1-F3     VDATAMVR1-F3     Completed
02/06/2013 15:30:00     02/06/2013 15:40:49     VDATAMVR1-F4     VDATAMVR1-F4     Completed
02/07/2013 14:00:00                             SCHD_INCR-DM1    TSM_CET_DM1      Missed
02/07/2013 14:00:00     02/07/2013 14:03:43     VDATAMVR1-F1     VDATAMVR1-F1     Completed
02/07/2013 14:30:00     02/07/2013 14:35:10     VDATAMVR1-F2     VDATAMVR1-F2     Completed
02/07/2013 15:00:00     02/07/2013 15:09:12     VDATAMVR1-F3     VDATAMVR1-F3     Completed
02/07/2013 15:30:00     02/07/2013 15:40:21     VDATAMVR1-F4     VDATAMVR1-F4     Completed
02/08/2013 14:00:00                             SCHD_INCR-DM1    TSM_CET_DM1      Missed
02/08/2013 14:00:00     02/08/2013 14:10:17     VDATAMVR1-F1     VDATAMVR1-F1     Completed
02/08/2013 14:30:00     02/08/2013 14:39:16     VDATAMVR1-F2     VDATAMVR1-F2     Completed
02/08/2013 15:00:00     02/08/2013 15:08:17     VDATAMVR1-F3     VDATAMVR1-F3     Completed
02/08/2013 15:30:00     02/08/2013 15:41:16     VDATAMVR1-F4     VDATAMVR1-F4     Completed
02/09/2013 14:00:00                             SCHD_INCR-DM1    TSM_CET_DM1      Missed
02/09/2013 14:02:16                             VDATAMVR1-F1     VDATAMVR1-F1     Failed 12
02/09/2013 14:30:00     02/09/2013 14:44:26     VDATAMVR1-F2     VDATAMVR1-F2     Failed 12
02/09/2013 15:00:00     02/09/2013 15:06:24     VDATAMVR1-F3     VDATAMVR1-F3     Failed 12
02/09/2013 15:30:00     02/09/2013 15:32:18     VDATAMVR1-F4     VDATAMVR1-F4     Completed
02/11/2013 14:00:00                             SCHD_INCR-DM1    TSM_CET_DM1      Missed
02/11/2013 14:00:00     02/11/2013 14:01:05     VDATAMVR1-F1     VDATAMVR1-F1     Failed 12
02/11/2013 14:30:00     02/11/2013 14:31:42     VDATAMVR1-F2     VDATAMVR1-F2     Failed 12
02/11/2013 15:00:00     02/11/2013 15:06:17     VDATAMVR1-F3     VDATAMVR1-F3     Failed 12
02/11/2013 15:30:00     02/11/2013 15:30:19     VDATAMVR1-F4     VDATAMVR1-F4     Completed
02/12/2013 14:00:00                             SCHD_INCR-DM1    TSM_CET_DM1      Missed
02/12/2013 14:00:00     02/12/2013 14:03:37     VDATAMVR1-F1     VDATAMVR1-F1     Completed
02/12/2013 14:30:00     02/12/2013 14:33:07     VDATAMVR1-F2     VDATAMVR1-F2     Completed
02/12/2013 15:00:00     02/12/2013 15:03:56     VDATAMVR1-F3     VDATAMVR1-F3     Completed
02/12/2013 15:30:00     02/12/2013 15:36:44     VDATAMVR1-F4     VDATAMVR1-F4     Completed
02/13/2013 14:00:00                             SCHD_INCR-DM1    TSM_CET_DM1      Missed
02/13/2013 14:00:00     02/13/2013 14:06:24     VDATAMVR1-F1     VDATAMVR1-F1     Completed
02/13/2013 14:30:00     02/13/2013 14:34:50     VDATAMVR1-F2     VDATAMVR1-F2     Completed
02/13/2013 15:00:00     02/13/2013 15:15:01     VDATAMVR1-F3     VDATAMVR1-F3     Completed
02/13/2013 15:30:00     02/13/2013 15:30:18     VDATAMVR1-F4     VDATAMVR1-F4     Completed
02/14/2013 14:00:00                             SCHD_INCR-DM1    TSM_CET_DM1      Future
02/14/2013 14:00:00                             VDATAMVR1-F1     VDATAMVR1-F1     Future
02/14/2013 14:30:00                             VDATAMVR1-F2     VDATAMVR1-F2     Future
02/14/2013 15:00:00                             VDATAMVR1-F3     VDATAMVR1-F3     Future

See Field descriptions for field descriptions.

Display detailed information for scheduled events for a client

Display the detailed information for events that are scheduled for processing by client DOC between the hours of 10:00 AM and 11:00 AM on November 1, 2005 (11/01/2005). Notice that when the status is FAILED, the result code is displayed.

query event domain1 * nodes=doc begindate=11/01/2005
begintime=10:00 endtime=11:00 enddate=11/01/2005
exceptionsonly=yes format=detailed

Scheduled Start      Actual Start         Schedule   Node    Status 
                                          Name       Name    
-------------------- -------------------- ---------  ------  -------
11/01/2005 10:01:01  11/01/2005 10:03:46  T1         DOC     Failed 8
11/01/2005 10:16:01  11/01/2005 10:16:10  T1         DOC     Failed 4
11/01/2005 10:31:01  11/01/2005 10:33:08  T1         DOC     Completed
11/01/2005 10:46:01                       T1         DOC     Missed
11/01/2005 10:57:49  11/01/2005 10:58:07  T0         DOC     Failed 12

Field descriptions

Policy Domain Name

Specifies the name of the policy domain to which the schedule is assigned.

Schedule Name

Specifies the name of the schedule that initiated this event.

Node Name

Specifies the client that is scheduled to perform the operation.

Scheduled Start

Specifies the scheduled starting date and time for the event.

Actual Start

Specifies the date and time at which the client began processing the scheduled operation. No information is displayed if the scheduled operation has not started.

Completed

Specifies the date and time the scheduled event is completed.

Status

Specifies the status of the event at the time the QUERY EVENT command is issued. The following values are possible:

Completed: Specifies that the scheduled event is completed.
Failed: Specifies that the client reports a failure when you run the scheduled operation and successive retries failed.
Failed - no restart: Specifies an intermediate status, when a client session is interrupted by a communications error or timeout on the server. This status can be changed to a final status of "Completed" or "Failed" when the event completes.
Future: Specifies that the beginning of the startup window for the event is in the future. This status also indicates that an event record has not been created for this event.
In Progress: Specifies that the scheduled event is running and has not yet reported the completion state to the server.
Periodically check the status for completion of the scheduled event. If this status is not updated in a reasonable amount of time, review your client dsmsched.log and dsmerror.log to determine why the client did not report the outcome of this event to the server. If the scheduled backup failed, rerun the scheduled event or perform a manual incremental backup to ensure the data backup.
Missed: Specifies that the scheduled startup window for this event passed and the schedule did not begin.
Pending: Specifies that the QUERY EVENT command was issued during the startup window for the event, but processing the scheduled operation did not begin.
Restarted: Specifies that the client has tried to process the scheduled operation again.
Severed: Specifies that the communications with the client is severed before the event can complete.
Started: Specifies that the event has begun processing.
Uncertain: Specifies that the state of the event cannot be determined. The server specifies Uncertain if the QUERY EVENT command does not find an event record. An event record is not found if the record was deleted or if the server was unavailable during the scheduled startup window (the schedule was never started). Records with Uncertain status are not stored in the database. If you do not want these records to display, either specify EXCEPTIONSONLY=YES or delete the schedule if it is no longer needed.

Attention: When a scheduled operation is processing, and is not restarted within its specified duration, the Status field shows Started. If the operation continues beyond the specified duration, no event record is created. If a query is issued after the specified duration has passed, the Status shows as Failed even if the operation is still running. After the operation completes, an event record is created, and a subsequent query shows the result in the Status field.

Result

Specifies the return code that indicates whether the schedule processed successfully. If the return code is a value other than 0, examine the server activity log and the client's error log and schedule log.

Return code	Explanation
0	All operations were completed successfully.
4	The operation was completed, but some files were not processed.
8	The operation was completed with at least one warning message.
12	The operation was completed with at least one error message. The count of error messages does not include notifications about skipped files.
-99	The operation failed because the session between the client and the server ended for an unknown reason. It is unknown whether the client can reconnect to the server to complete the schedule event.

If a schedule has ACTION=COMMAND as a parameter, and the command is not an IBM Storage Protect command, the command can produce other values in the Result field.

Reason

Specifies the reason for the return code.