ajsreport
- Organization of this page
Format
ajsreport
[-F scheduler-service-name]|[-d performance-log-file-storage-directory]
[-n [-r minutes]|
[-b year/month/day] [-s hours:minutes]
[-e year/month/day] [-f hours:minutes]]
[-i collection-interval]
[-H]
Description
The ajsreport command outputs JP1/AJS3 performance reports.
Execution privileges
In Windows: Administrators privileges
In UNIX: Superuser privileges
Arguments
-F scheduler-service-name
Specify the name of the target scheduler service.
You can specify a character string of 1 to 30 bytes.
If you omit this option, the system assumes the default scheduler service name.
You cannot specify this option with the -d option.
-d performance-log-file-storage-directory
Specify the name of the directory in which performance log files are to be stored.
If you omit this option, the value set in the AJSREPORTDIR environment setting parameter is used as the storage directory.
Use the absolute path to specify the directory name. If you want to specify a directory whose name contains spaces, enclose the entire path in double quotation marks (").
You cannot specify this option with the -F option.
-n
Specify this option to output the operation status that is most recent as of the date and time when the command was executed.
If you specify -r, the command outputs the operation status for the number of minutes (specified for -r) immediately before the zero seconds (.000) of the command execution time. The value specified for -r is based on the zero seconds on the date and time that the command was executed.
If you specify -i, you can specify the interval at which the operation status is to be collected within the time range specified for -r.
You cannot specify this option with the -b, -s, -e, and -f options.
-r minutes
Specify the number of minutes before the time at which the command was executed.
The default is 1 (minute).
You cannot specify this option with the -b, -s, -e, and -f options.
-
minutes
You can specify a value between 1 and 1,440 for the minute.
-b year/month/day
Specify the start date of the period for which the operating status is to be output.
If you omit this option, the start date is assumed to be the date on which the command was executed.
You cannot specify this option with the -n and -r options.
-
year
You can specify a value between 1994 and 2036 for the year.
-
month
You can specify a value between 1 (or 01) and 12.
-
day
You can specify a value between 1 (or 01) and 31.
-s hours:minutes
Specify the start time of the period for which the operating status is to be output.
If you omit this option, the start time is assumed to be 00:00.
You cannot specify this option with the -n and -r options.
-
hours
You can specify a value between 0 (or 00) and 23.
-
minutes
You can specify a value between 0 (or 00) and 59.
-e year/month/day
Specify the end date of the period for which the operating status is to be output.
If you omit this option, the end date is assumed to be the same as the start date specified for -b.
You cannot specify this option with the -n and -r options.
You cannot specify a date earlier than the start date that is specified for the -b option or that is set by default.
-
year
You can specify a value between 1994 and 2036 for the year.
-
month
You can specify a value between 1 (or 01) and 12.
-
day
You can specify a value between 1 (or 01) and 31.
-f hours:minutes
Specify the end time of the period for which the operating status is to be output.
If you omit this option, the end time is assumed to be 24 hours after the start time.
If you omit both the -e option and -f option, the end date and time are calculated by adding 24 hours to the start date and time.
You cannot specify this option with the -n and -r options.
The date and time you specify for the -e and -f options cannot be same or earlier than the date and time you specify for the -b and -s options.
-
hours
You can specify a value between 0 (or 00) and 23.
-
minutes
You can specify a value between 0 (or 00) and 59.
The following table shows examples of performance report collection periods specified by using combinations of the -b, -s, -e, and -f options.
|
No. |
-b option |
-s option |
-e option |
-f option |
Start date and time |
End date and time |
Collection period |
|---|---|---|---|---|---|---|---|
|
1 |
Omitted |
Omitted |
Omitted |
Omitted |
2018/04/08 00:00 |
2018/04/09 00:00 |
1 day from 2018-04-08 00:00:00.000 to 2018-04-08 23:59:59.999 |
|
2 |
2018/04/01 |
Omitted |
Omitted |
Omitted |
2018/04/01 00:00 |
2018/04/02 00:00 |
1 day from 2018-04-01 00:00:00.000 to 2018-04-01 23:59:59.999 |
|
3 |
Omitted |
09:00 |
Omitted |
Omitted |
2018/04/08 09:00 |
2018/04/09 09:00 |
Approximately 1 day from 2018-04-08 09:00:00.000 to 2018-04-09 08:59:59.999 |
|
4 |
2018/04/01 |
11:00 |
Omitted |
Omitted |
2018/04/01 11:00 |
2018/04/02 11:00 |
Approximately 1 day from 2018-04-01 11:00:00.000 to 2018-04-02 10:59:59.999 |
|
5 |
Omitted |
Omitted |
2018/04/08 |
Omitted |
2018/04/08 00:00 |
2018/04/09 00:00 |
1 day from 2018-04-08 00:00:00.000 to 2018-04-08 23:59:59.999 |
|
6 |
Omitted |
Omitted |
Omitted |
20:00 |
2018/04/08 00:00 |
2018/04/08 20:00 |
Approximately 1 day from 2018-04-08 00:00:00.000 to 2018-04-08 19:59:59.999 |
|
7 |
Omitted |
Omitted |
2018/04/08 |
22:30 |
2018/04/08 00:00 |
2018/04/08 22:30 |
Approximately 1 day from 2018-04-08 00:00:00.000 to 2018-04-08 22:29:59.999 |
|
8 |
2018/04/01 |
Omitted |
2018/04/07 |
Omitted |
2018/04/01 00:00 |
2018/04/08 00:00 |
7 days from 2018-04-01 00:00:00.000 to 2018-04-07 23:59:59.999 |
|
9 |
Omitted |
11:00 |
Omitted |
22:30 |
2018/04/08 11:00 |
2018/04/08 22:30 |
Approximately 0.5 days from 2018-04-08 11:00:00.000 to 2018-04-08 22:29:59.999 |
|
10 |
2018/04/01 |
08:00 |
2018/04/07 |
21:30 |
2018/04/01 08:00 |
2018/04/07 21:30 |
Approximately 7 days from 2018-04-01 08:00:00.000 to 2018-04-07 21:29:59.999 |
-i collection-interval
Specify the interval at which to collect the operating status.
The default is 1 (minute).
If you specify this option at the same time as the -r option, the value you specify for this option must not be greater than the value you specify for the -r option.
-
collection-interval
You can specify a value between 1 and 1,440 for the minute.
-H
Specify this option if you do not want to output header information (including the date and time when the command was executed, the command specification details, and item names) for the operating status.
Notes
-
This command cannot be executed remotely.
-
Always separate the option and its value by at least one space character.
-
You cannot use regular expressions when you specify scheduler service names.
-
This command outputs the results collected at the system time. The local date and time setting of a scheduler service is not applied.
-
If you execute this command while a jobnet or job is running, information about the jobnet or job whose status changed during execution is not included in the collection results. This information is assumed as the information after the start of the collection.
-
You cannot execute this command by specifying a directory path on another host for the -d option, or by specifying a performance log file that was recorded in a different OS environment.
-
If the message "KAVS1112-E" is output when the ajsreport command is executed, make sure that the performance log file storage directory exists.
-
This command increases the execution time and memory usage of the command as the report period increases. If you want to shorten the execution time of the ajsreport command, or reduce the impact of increased memory usage, specify a shorter report output period and execute the ajsreport command separately.
-
When the ajsreport command is executed, the CPU load is temporarily increased by the process of the ajsreport command. We recommend to execute the ajsreport command when the CPU load is low.
Return values
|
0 |
Normal end |
|
4 |
An environment variable used for command execution is incorrect. |
|
8 |
An argument specified in the command is incorrect. |
|
12 |
Memory became insufficient during command processing. |
|
24 |
Permission to execute the command is not granted. |
|
32 |
The performance log file contains an invalid record. |
|
40 |
A system limit was exceeded during allocation of shared memory, file descriptors, or resources for exclusive use. |
|
120 |
An unexpected error was detected for an OS system call. |
|
124 |
An unexpected error was detected in JP1/AJS internal processing. |
Items output to a performance report
The following describes the items that are output to a performance report.
|
No. |
Item |
Description |
Collection type#1 |
|---|---|---|---|
|
1 |
RJ_EXEC_START_NUM |
Number of root jobnets or root remote jobnets whose execution has started. This value is incremented according to the number of jobnets that are placed in the Now running status. |
Number/time |
|
2 |
CONDRJ_MONITOR_START_NUM |
Number of monitoring generations of jobnets with start conditions for which monitoring has started. This value is incremented according to the number of monitoring generations that are placed in the Now monitoring status. |
Number/time |
|
3 |
CONDRJ_EV_DETECTED_NUM |
Number of satisfied start conditions for a jobnet with start conditions. This value is incremented according to the number of jobnets whose start conditions are satisfied. |
Number/time |
|
4 |
CONDRJ_EXEC_START_NUM |
Number of execution generations (of jobnets with start conditions) whose execution has started. This value is incremented according to the number of execution generations that are placed in the Now running status. |
Number/time |
|
5 |
NEST_EXEC_START_NUM |
Number of nested jobnets or nested remote jobnets whose execution has started. This value is incremented according to the number of jobnets that are placed in the Now running status. |
Number/time |
|
6 |
JOB_EXECWAIT_NUM |
Number of jobs#2 that changed to the Waiting to execute status. This value is incremented according to the number of jobs that are placed in the Waiting to execute status. |
Number/time |
|
7 |
JOB_TRANSITTED_QUEUING_NUM |
Number of jobs#2 that changed to the Now queuing status. This value is incremented according to the number of jobs that are placed in the Now queuing status. |
Number/time |
|
8 |
JOB_EXEC_START_NUM |
Number of jobs#2 whose execution has started. This value is incremented according to the number of jobs that are placed in the Now running status. |
Number/time |
|
9 |
EVJOB_EXEC_START_NUM |
Number of event jobs whose execution has started. This value is incremented according to the number of jobs that are placed in the Now running status. |
Number/time |
|
10 |
QLJOB_EXEC_START_NUM |
Number of queueless jobs whose execution has started. This value is incremented according to the number of jobs that are placed in the Now running status. |
Number/time |
|
11 |
OTHERJOB_EXEC_START_NUM |
Number of OR jobs and judgment jobs whose execution has started. This value is incremented each time execution of an OR job or a judgment job begins. |
Number/time |
|
12 |
JOBCON_EXEC_START_NUM |
Number of jobnet connectors whose execution has started. This value is incremented according to the number of jobnet connectors that are placed in the Now running status. |
Number/time |
|
13 |
RJ_EXEC_END_N_NUM |
Number of root jobnets or root remote jobnets that terminated normally. This value is incremented according to the number of jobnets that are placed in the Ended normally status. This item is also applicable to cases where rerunning of monitoring generations of jobnets with start conditions terminated normally. |
Number/time |
|
14 |
RJ_EXEC_END_W_NUM |
Number of root jobnets or root remote jobnets that ended with warning detected. This value is incremented according to the number of jobnets that are placed in the Ended with warning status. This item is also applicable to cases where rerunning of monitoring generations of jobnets with start conditions terminated with a warning detected. |
Number/time |
|
15 |
RJ_EXEC_END_E_NUM |
Number of root jobnets or root remote jobnets that ended abnormally. This value is incremented according to the number of jobnets that are placed in any of the following statuses:
|
Number/time |
|
16 |
CONDRJ_MONITOR_END_N_NUM |
Number of monitoring generations of jobnets with start conditions that changed to the Monitor-end normal status. This value is incremented according to the number of jobnets that are placed in the Monitor-end normal status. |
Number/time |
|
17 |
CONDRJ_NOMONITOR_END_NUM |
Number of monitoring generations of jobnets with start conditions that changed to the Unmonitored + Ended status. This value is incremented according to the number of jobnets that are placed in the Unmonitored + Ended status. |
Number/time |
|
18 |
CONDRJ_MONITOR_END_E_NUM |
Number of monitoring generations of jobnets with start conditions that changed to the Monitor terminated status. This value is incremented according to the number of jobnets that are placed in the Monitor terminated status. |
Number/time |
|
19 |
CONDRJ_MONITOR_STOPPED_END_NUM |
Number of monitoring generations of jobnets with start conditions that changed to the Interrupted monitoring status. This value is incremented according to the number of jobnets that are placed in the Interrupted monitoring status. |
Number/time |
|
20 |
CONDRJ_EXEC_END_N_NUM |
Number of execution generations of jobnets with start conditions that changed to the Ended normally status. This value is incremented according to the number of jobnets that are placed in the Ended normally status. |
Number/time |
|
21 |
CONDRJ_EXEC_END_W_NUM |
Number of execution generations of jobnets with start conditions that changed to the Ended with warning status. This value is incremented according to the number of jobnets that are placed in the Ended with warning status. |
Number/time |
|
22 |
CONDRJ_EXEC_END_E_NUM |
Number of execution generations of jobnets with start conditions that ended abnormally. This value is incremented according to the number of jobnets that are placed in any of the following statuses:
|
Number/time |
|
23 |
NEST_EXEC_END_N_NUM |
Number of nested jobnets or nested remote jobnets that terminated normally. This value is incremented according to the number of jobnets that are placed in the Ended normally status. |
Number/time |
|
24 |
NEST_EXEC_END_W_NUM |
Number of nested jobnets or nested remote jobnets that ended with warning detected. This value is incremented according to the number of jobnets that are placed in the Ended with warning status. |
Number/time |
|
25 |
NEST_EXEC_END_E_NUM |
Number of nested jobnets or nested remote jobnets that ended abnormally. This value is incremented according to the number of jobnets that are placed in any of the following statuses:
|
Number/time |
|
26 |
JOB_END_NOTIFICATION_DETECTED_NUM |
Number of jobs#2 whose end was detected. This value is incremented when a job end notification is received from an agent. Note that this value is also incremented when a job is terminated either forcibly or due to an error. However, as in the following cases, if an error occurs before the reception of a job finishes, the job is not counted.
|
Number/time |
|
27 |
JOB_EXEC_END_N_NUM |
Number of jobs#2 that terminated normally. This value is incremented according to the number of jobs that are placed in the Ended normally status. |
Number/time |
|
28 |
JOB_EXEC_END_W_NUM |
Number of jobs#2 that ended with a warning detected. This value is incremented according to the number of jobs that are placed in the Ended with warning status. |
Number/time |
|
29 |
JOB_EXEC_END_E_NUM |
Number of jobs#2 that terminated abnormally. This value is incremented according to the number of jobs that are placed in any of the following statuses:
|
Number/time |
|
30 |
EVJOB_DETECTED_EV_NUM |
Number of event job notifications received from an agent. This value does not match the number of detected events because the number of satisfied start conditions for a jobnet with start conditions depends on the valid range setting. To confirm the number of satisfied start conditions, see CONDRJ_EV_DETECTED_NUM. |
Number/time |
|
31 |
EVJOB_EXEC_END_N_NUM |
Number of event jobs that terminated normally. This value is incremented according to the number of jobs that are placed in the Ended normally status. |
Number/time |
|
32 |
EVJOB_EXEC_END_W_NUM |
Number of event jobs that ended with a warning detected. This value is incremented according to the number of jobs that are placed in the Ended with warning status. |
Number/time |
|
33 |
EVJOB_EXEC_END_E_NUM |
Number of event jobs that terminated abnormally. This value is incremented according to the number of jobs that are placed in any of the following statuses:
|
Number/time |
|
34 |
QLJOB_EXEC_END_N_NUM |
Number of queueless jobs that terminated normally. This value is incremented according to the number of jobs that are placed in the Ended normally status. |
Number/time |
|
35 |
QLJOB_EXEC_END_W_NUM |
Number of queueless jobs that ended with a warning detected. This value is incremented according to the number of jobs that are placed in the Ended with warning status. |
Number/time |
|
36 |
QLJOB_EXEC_END_E_NUM |
Number of queueless jobs that terminated abnormally. This value is incremented according to the number of jobs that are placed in any of the following statuses:
|
Number/time |
|
37 |
OTHERJOB_EXEC_END_N_NUM |
Number of OR jobs and judgment jobs that changed to the Ended normally or Normal end + False status. This value is incremented according to the number of jobs that are placed in the Ended normally or Normal end + False status. |
Number/time |
|
38 |
OTHERJOB_EXEC_END_E_NUM |
Number of judgment jobs that terminated with an error detected. This value is incremented according to the number of jobs that are placed in the Ended abnormally status. |
Number/time |
|
39 |
JOBCON_EXEC_END_N_NUM |
Number of jobnet connectors that terminated normally. This value is incremented according to the number of jobnet connectors that are placed in the Ended normally status. |
Number/time |
|
40 |
JOBCON_EXEC_END_W_NUM |
Number of jobnet connectors that ended with a warning detected. This value is incremented according to the number of jobnet connectors that are placed in the Ended with warning status. |
Number/time |
|
41 |
JOBCON_EXEC_END_E_NUM |
Number of jobnet connectors that terminated abnormally. This value is incremented according to the number of jobnet connectors that are placed in any of the following statuses:
|
Number/time |
|
42 |
CONDRJ_EXEC_START_BACKLOG_NUM |
Total number of execution generations among the jobnets that have start conditions whose conditions were satisfied but that did not start, and whose statuses are waiting for start condition or being held. For potential reasons behind the failure of a jobnet to start even though the jobnet's start condition was satisfied, see 3.4.6 Retention of execution generations with satisfied start conditions in the manual JP1/Automatic Job Management System 3 Overview or 3.4.7 Suppressing further executions of a jobnet with start conditions after it abnormally terminates in the manual JP1/Automatic Job Management System 3 Overview. |
Total |
|
43 |
JOB_SUBMIT_RETRY_BACKLOG_NUM |
Total number of submission-enabled jobs#2 that failed to be submitted due to overflow of the job-execution information communication buffer.The communications buffer for job execution information overflows if many jobs are submitted at the same time. |
Total |
|
44 |
JOB_QUEUING_BACKLOG_NUM |
Total number of jobs#2 in the following statuses:
|
Total |
|
45 |
EVJOB_QUEUING_BACKLOG_NUM |
Total number of event jobs in the Now queuing status. |
Total |
|
46 |
EVJOB_START_BACKLOG_NUM |
Number of unprocessed jobs for which the scheduler service has not received a start notification, among the jobs that started event monitoring on an agent. |
Total |
|
47 |
CONDRJ_EXEC_END_BACKLOG_NUM |
Total number of unprocessed jobnets for which the scheduler service has not received a notification of satisfied conditions, among the jobnets for which start conditions are satisfied. |
Total |
|
48 |
JOB_EXEC_END_BACKLOG_NUM |
Total number of jobs that have not changed to an end status after the end of job#2 was detected. This value is incremented when the end of a job is detected, and is decremented when a job changes to an end status. |
Total |
|
49 |
EVJOB_DETECTED_NOTIFICATION_WITHOUT_EV_END_BACKLOG_NUM |
Total number of unprocessed notifications that failed to be sent to the scheduler service, except for the notifications of satisfied events received from the agent. |
Total |
|
50 |
EVJOB_DETECTED_EV_END_BACKLOG_NUM |
Total number of unprocessed notifications that failed to be sent to the scheduler service, among the notifications of satisfied events received from the agent. |
Total |
|
51 |
JOB_EXCEEDED_MAX_CON-EXE |
Indicates whether the maximum number of concurrently executable jobs#2 (except for QUEUE jobs) is reached. 0: The maximum number of concurrently executable jobs is not reached. 1: The maximum number of concurrently executable jobs is reached. If one of the following conditions is met, the system assumes that the maximum number of concurrently executable jobs is not reached:
|
Presence/time |
|
52 |
JOB_MAXIMUM_TRANSFER_FILE_SIZE |
The size (in bytes) of the transfer file for the largest job#2 in the collection interval (excluding QUEUE jobs) is displayed. If multiple transfer files are specified for one job, the total size of those files is indicated. Note that the indicated value is larger than the actual file size by hundreds of bytes. If the value of the ReceiveFileSizeStatus environment setting parameter is set to 1, 2, or 3, the system does not receive a transfer file when the maximum reception size is reached. At this time, the maximum size of the transfer file is set to 0. |
Max./time |
|
53 |
JOB_ERROR_AGENT_DETECTED |
Indicates whether an error agent exists when jobs#2 (except for QUEUE jobs) are executed. 0: No error agent exists. 1: An error agent exists. The system indicates 1 if job transfer to an execution agent failed. Note that, if the job is sent directly to an execution agent that is working normally (without first being sent to an agent that has failed), 0 is displayed. Example: When execution agents AGT1 and AGT2 are linked to execution agent group AGTGR
|
Presence/time |
|
54 |
EVJOB_ERROR_AGENT_DETECTED |
Indicates whether an error agent exists when event jobs#2 are executed. 0: No error agent exists. 1: An error agent exists. |
Presence/time |
|
55 |
JOB_MAXIMUM_RESULT_FILE_SIZE |
The size (in bytes) of the result files for the largest job#2 in the collection interval (excluding QUEUE jobs) is displayed. When 1, 2, or 3 is specified for the environment setting parameter ReceiveFileSizeStatus, data in excess of the upper limit on the size of received files is discarded. However, the data size displayed for this item includes the size of the discarded data. Note that the indicated value is larger than the actual file size by hundreds of bytes. |
Max./time |
|
56 |
RUNNING_AND_SCHEDULED_NEXT_GENERATIONS_NUM |
Total number of generations that are being executed, or that are scheduled to be executed next. Result generations for which execution is complete and generations that are scheduled for execution after the generations to be executed next are not included. Generations that are being executed, or that are scheduled to be executed next applies to the generations that have the following statuses.
|
Total |
|
57 |
ALL_NOEXEC_END_UNITS_NUM |
The number of units that ended without being executed. This number increases when a unit transitions to one of the following statuses. The calculation of this number does not include status transitions that occur when the scheduler service is started.
|
Number/time |
|
58 |
DELAY_NET_START_NUM |
Number of jobnet-start delays. This value is incremented when the jobnet delay monitor function detects a start delay. |
Number/time |
|
59 |
DELAY_NET_END_NUM |
Number of jobnet-end delays. This value is incremented when the jobnet delay monitor function detects an end delay. |
Number/time |
|
60 |
DELAY_ALLJOB_END_NUM |
Number of end delays of jobs#2 and event jobs. This value is incremented when the end delay monitor function based on the time required for executing jobs#2 and event jobs detects an end delay. |
Number/time |
|
61 |
CONTENTJOB_NUM |
Number of concurrently executed jobs #2 (sum total of the number of jobs#2 in the Now queuing status and Now running status). The largest value in the collection intervals is displayed. |
Max./time |
|
62 |
EVJOB_UNREPORTED_EVENT_NUM |
Total number of the following reports that were not sent to the scheduler service. The largest value in the collection intervals is displayed.
|
Max./time |
- #1
-
The following shows the collection type of performance reports.
Collection type
Description
Number/time
Indicates the number as a result of increment starting from 0 in the collection period.
Max./time
Indicates the maximum value recorded for the target item in the collection period.
Presence/time
Indicates whether an event of the target item occurred in the collection period.
Total
Indicates the sum total for the target item when the collection period has elapsed.
- #2
-
Jobs indicate PC jobs, Unix jobs (excluding queueless jobs), QUEUE jobs, flexible jobs, HTTP connection jobs, custom jobs, action jobs (excluding queueless jobs), and passing information setting jobs.
- #3
-
The calculation of this number does not include units that transition to the Unmonitored + Ended status after monitoring of their corresponding monitoring generation starts. However, the calculation of this number does include units that transition to the Unmonitored + Ended status without their corresponding execution generation starting.
Example 1
The following command outputs the operating status on the current date (2018-01-01).
ajsreport
- Output example
#exectime: 2018/01/01 19:00:13 #command: ajsreport #DATE,RJ_EXEC_START_NUM,CONDRJ_MONITOR_START_NUM,CONDRJ_EV_DETECTED_NUM,... 2018/01/01 00:00,0,0,0,... 2018/01/01 00:01,0,0,0,... : ,:,:,:,... 2018/01/01 23:59,0,0,0,...
Example 2
The following command outputs the operating status, without header information, on the current date (2018-01-01).
ajsreport -H
- Output example
2018/01/01 00:00,0,0,0,... 2018/01/01 00:00,0,0,0,... : ,:,:,:,... 2018/01/01 23:59,0,0,0,...
Example 3
The following command outputs the operating status for the command execution time (15:10) on the current date (2018-01-01).
ajsreport -n
- Output example
#exectime: 2018/01/01 15:10:34 #command: ajsreport -n #DATE,RJ_EXEC_START_NUM,CONDRJ_MONITOR_START_NUM,CONDRJ_EV_DETECTED_NUM,... 2018/01/01 15:09,0,0,0,...
Example 4
The following command outputs the operating status for 10 minutes before the command execution time (15:10) on the current date (2018-01-01).
ajsreport -n -r 10
- Output example
#exectime: 2018/01/01 15:10:34 #command: ajsreport -n -r 10 #DATE,RJ_EXEC_START_NUM,CONDRJ_MONITOR_START_NUM,CONDRJ_EV_DETECTED_NUM,... 2018/01/01 15:00,0,0,0,... 2018/01/01 15:01,0,0,0,... : ,:,:,:,... 2018/01/01 15:09,0,0,0...
Example 5
The following command outputs the operating status for the period from 9:00 to 21:30 on the current date (2018-01-01).
ajsreport -s 9:00 -f 21:30
- Output example
#exectime: 2018/01/01 22:02:51 #command: ajsreport -s 9:00 -f 21:30 #DATE,RJ_EXEC_START_NUM,CONDRJ_MONITOR_START_NUM,CONDRJ_EV_DETECTED_NUM,... 2018/01/01 09:00,0,0,0,... 2018/01/01 09:01,0,0,0,... : ,:,:,:,... 2018/01/01 21:29,0,0,0,...
Example 6
The following command outputs the operating status of the scheduler service AJSROOT2 for the period from 9:00 on 2018-01-02 to 09:00 on 2018-01-03 at intervals of 7 minutes.
The last row is less than the collection interval of 7 minutes. Therefore, the command outputs the operating status for the period up to the end time of the collection range (in this case, 5 minutes from 08:55 on 2018-01-03).
ajsreport -F AJSROOT2 -b 2018/01/02 -s 9:00 -i 7
- Output example
#exectime: 2018/01/03 12:17:26 #command: ajsreport -F AJSROOT2 -b 2018/01/02 -s 9:00 -i 7 #DATE,RJ_EXEC_START_NUM,CONDRJ_MONITOR_START_NUM,CONDRJ_EV_DETECTED_NUM,... 2018/01/02 09:00,0,0,0,... 2018/01/02 09:07,0,0,0,... : ,:,:,:,... 2018/01/03 08:55,0,0,0,...
Example 7
The following command outputs the operating status for the period of seven days from 2018-07-01 to 2018-07-07 at intervals of five hours (300 minutes).
The last row is less than the collection interval of 5 hours (300 minutes). Therefore, the command outputs the operating status for the period up to the end time of the collection range (in this case, 180 minutes from 21:00 on 2018-07-07).
ajsreport -b 2018/07/01 -e 2018/07/07 -i 300
- Output example
#exectime: 2018/07/10 18:31:57 #command: ajsreport -b 2018/07/01 -e 2018/07/07 -i 300 #DATE,RJ_EXEC_START_NUM,CONDRJ_MONITOR_START_NUM,CONDRJ_EV_DETECTED_NUM,... 2018/07/01 00:00,0,0,0,... 2018/07/01 05:00,0,0,0,... : ,:,:,:,... 2018/07/07 21:00,0,0,0,...
Example 8
The following command outputs the operating status for the period from 2018/09/01 8:00 to 2018/9/15 17:30 at intervals of 2 hours (120 minutes).
The last row is less than the collection interval of 2 hours (120 minutes). Therefore, the command outputs the operating status for the period up to the end time of the collection range (in this case, 90 minutes from 16:00 on 2018-9-15).
ajsreport -b 2018/09/01 -s 8:00 -e 2018/9/15 -f 17:30 -i 120
- Output example
#exectime: 2018/12/04 08:43:35 #command: ajsreport -b 2018/09/01 -s 8:00 -e 2018/9/15 -f 17:30 -i 120 #DATE,RJ_EXEC_START_NUM,CONDRJ_MONITOR_START_NUM,CONDRJ_EV_DETECTED_NUM,... 2018/09/01 08:00,0,0,0,... 2018/09/01 10:00,0,0,0,... : ,:,:,:,... 2018/09/15 16:00,0,0,0,...