ajsshow

Format

ajsshow
     [-F service-name]
     [{-s|-p|-l|-xw [-xi {b|c}]|-r|-f "format-indicator"|
          -i "two-byte-format-indicator"}]
     [-t "format-indicator"]
     [-k]
     [-g {number-of-generations|a}
         |-b year/month[/day] [-e year/month[/day]]
         |-v year/month[/day] [-w year/month[/day]]
         |-B execution-registration-number]
     [-u user-name]
     [-c]
     [-R]
     [-E]
     [-T]
     [-N|-J]
     [-d [[year/]month/]day]
     [-h hours[:minutes]]
     [-X {yes|no|auto}]
     job-name-or-jobnet-name-or-job-group-name...

To Page Top

Description

Outputs the results of the past execution, the current status, the next execution schedule, and other information on a jobnet or job already registered for execution to the standard output file. (For details about the output format, see Additional information 1 later.)

To Page Top

Execution privileges

You must have any of the following JP1 privileges:

• JP1_AJS_Admin privilege

• JP1_AJS_Manager privilege

• JP1_AJS_Editor privilege

• JP1_AJS_Operator privilege

• JP1_AJS_Guest privilege

To Page Top

Arguments

To Page Top

Notes

• When extracting data from the output information, extract the data based on its delimiting spaces, not by fixed byte count.

• Either of the following users can output unit information:

  • A user granted the reference privilege when the unit whose information is to be output was defined or when its attributes were changed

  • A JP1 user mapped to the OS user who has Administrators or superuser privileges

    Note, however, that if yes is set after changing the ADMACLIMIT environment setting parameter from its default, even a JP1 user who was mapped to an OS user with Administrators or superuser privileges must have the reference privilege.

• The period of information output can be specified through a combination of the -b and -e options or the -v and -w options. Such different combinations give different output results. For details, see Example 5.

• If you use the -b, -e, -v, or -w option to set the period of information output, the information is output in ascending order starting from the oldest generation.

• Information about a unit added to a suspended root jobnet is not output until the root jobnet is released from suspension. After the root jobnet is released from suspension, simulated results are output. Therefore, the results output when the root jobnet is suspended are different from the results output after the root jobnet is released from suspension.

• You may specify multiple units with the -c option and the -g option that specifies the number of generations. In this case, the system outputs execution result information on each jobnet or job in descending order from the latest generation to the specified generation.

• When you specify that a target unit automatically be selected from the units in a planning group, an error occurs if you do not have the appropriate operation privilege for the automatically selected unit.

• When the -X option is omitted, a target unit in a planning group is determined according to the value specified for the AJSAUTOJUDGE environment variable.

• For an explanation of how to specify the name of a unit in a planning group, see Additional information in ajsplan in 3. Commands Used for Normal Operations.

• If you specify none of the -s, -p, -r, -f, and -i options, the -l option is assumed.

• If you specify the -l, -r, -f, or -i option without specifying the -g, -b, -e, -v, -w, or -B option or execution ID, the system assumes -g 1.

• If you specify the -b, -e, -v, or -w option, a schedule simulation and an execution simulation are performed. When you specify -g (default), -B, or an execution ID, no simulation is performed. For details about simulations, see 4.4.2 Simulation in the manual JP1/Automatic Job Management System 3 Overview.

• If the -r, -f %r, or -i %so option is specified during external database connection, a standard output file or standard error output file is created. The update permission for these files is set to the user who executes the command. When a file is created, any existing file that has the same name as the file being created is deleted. If the specified job does not send information to the standard error output, a file is not created but the assumed standard error output file name is output to the standard output. The command terminates abnormally in the following cases:

  • The user who executed the command does not have access permissions for the directory specified for the STDFILEOUTDIR environment setting parameter.

  • The directory specified for the STDFILEOUTDIR environment setting parameter does not exist.

  • No directory is specified for the STDFILEOUTDIR environment setting parameter.

To Page Top

Arguments that can be specified when executing the command from JP1/AJS3 - View

You can specify the following arguments when executing the ajsshow command from JP1/AJS3 - View:

No.	Arguments	Required?
1	-F service-name	Y
2	-s	--
3	-p	--
4	-l	--
5	-xw	--
6	-xi {b|c}	--
7	-r	--
8	-f "format-indicator"	--
9	-i "two-byte-format-indicator"	--
10	-t "format-indicator"	--
11	-k	--
12	-g {number-of-generations|a}	--
13	-b year/month[/day]	--
14	-e year/month[/day]	--
15	-v year/month[/day]	--
16	-w year/month[/day]	--
17	-B execution-registration-number	--
18	-u user-name	--
19	-c	--
20	-R	--
21	-E	--
22	-T	--
23	-N	--
24	-J	--
25	-d [[year/]month/]day	--
26	-h hours[:minutes]	--
27	-X {yes|no|auto}	--
28	job-name-or-jobnet-name-or-job-group-name	Y

Legend:

Y: Required

--: Optional

You cannot specify any other options when executing the ajslogprint command from JP1/AJS3 - View.

For details about how to execute JP1/AJS3 commands from JP1/AJS3 - View, see 10.4 Executing JP1/AJS3 commands from JP1/AJS3 - View in the JP1/Automatic Job Management System 3 Operator's Guide.

To Page Top

Return values

0	Normal end
Multiple of 4 within the range from 4 to 124	Abnormal end

To Page Top

Additional information 1

Table 3-20 lists the format indicators to output jobnet and job definitions.

Table 3-21 lists the two-byte format indicators to output jobnet and job definitions.

Table 3-22 lists the other format indicators.

Table 3-23 provides the output formats of the format indicators.

Table 3‒20: Format indicators for jobnet and job output.

Format indicator	Output information	-f	-t
%J	Jobnet or job full-path name	Yes	Yes
%j	Jobnet or job name Character string of up to 30 bytes	Yes	Yes
%A	Character string specified for AJSPATH= Character string specified with %J except the part that follows the right-most slash (/)	Yes	Yes
%T	Unit type mgroup: Manager job group group: Job group mnet: Manager jobnet condn: Start condition (.CONDITION) net: Jobnet rnet: Jobnet for recovery rmnet: Remote jobnet rrnet: Remote jobnet for recovery job: Unix job rjob: Unix job for recovery pjob: PC job rpjob: PC job for recovery qjob: QUEUE job rqjob: QUEUE job for recovery jdjob: Judgment job rjdjob: Judgment job for recovery orjob: OR job rorjob: OR job for recovery cmsjb: OpenView status report job rcmsjb: OpenView status report job for recovery evwjb: JP1 event reception monitoring job revwjb: JP1 event reception monitoring job for recovery flwjb: File monitoring job rflwjb: File monitoring job for recovery mlwjb: Email reception monitoring job rmlwjb: Email reception monitoring job for recovery mqwjb: Message queue reception monitoring job rmqwjb: Message queue reception monitoring job for recovery mswjb: MSMQ reception monitoring job rmswjb: MSMQ reception monitoring job for recovery lfwjb: Log file monitoring job rlfwjb: Log file monitoring job for recovery ntwjb: Windows event-log monitoring job rntwjb: Windows event-log monitoring job for recovery tmwjb: Execution interval control job rtmwjb: Execution interval control job for recovery evsjb: JP1 event sending job revsjb: JP1 event sending job for recovery mlsjb: Email sending job rmlsjb: Email sending job for recovery mqsjb: Message queue sending job rmqsjb: Message queue sending job for recovery mssjb: MSMQ sending job rmssjb: MSMQ sending job for recovery pwljb: Local power control job rpwljb: Local power control job for recovery pwrjb: Remote power control job rpwrjb: Remote power control job for recovery cuujb: Custom Unix job rcuujb: Custom Unix job for recovery cupjb: Custom PC job rcupjb: Custom PC job for recovery netcn: Jobnet connector	Yes	Yes
%C	Jobnet or job status#30	Yes#10	--
%U	User name of a jobnet registered for execution Character string of up to 31 bytes	Yes#9	--
%D	Time when the jobnet was registered for execution#7	Yes#9	--
%L	Number of jobnet nests with respect to the root jobnet as 0	Yes#9	Yes
%p#3	Whether the next execution is scheduled exist none	Yes#27	--
%P#3	Date and time of the next execution schedule#7	Yes#1	--
%M#3	Next execution method schedule plan shift	Yes#1	--
%R	Return value or signal code *** if there is no return value or signal code	Yes#2	--
%S	Date and time when jobnet execution is started or when a job is submitted#7	Yes#12	--
%s	Date and time when jobnet execution is started or when a job is submitted#7	Yes#12	--
%K	Date and time when jobnet re-execution is started#7	Yes#1, #15	--
%k	Date and time when jobnet re-execution is started#7	Yes#1, #15	--
%E	Date and time when jobnet or job execution is ended#7	Yes	--
%e	Date and time when jobnet or job execution is ended#7	Yes	--
%V	Date and time when jobnet or job execution is started in another host#7	Yes#2	--
%Q	Date and time when jobnet or job execution was ended in another host#7	Yes#2	--
%W	$LANG value	Yes#9	Yes
%Z	$TZ value	Yes#9	Yes
%G	Generation number#8 (0 or less for scheduled generations) (1 or greater for generations being executed or execution result generations)	Yes#8	Yes
%N	Priority of execution#24 A value of 1 to 5	Yes	--
%H	Agent host name	Yes#2	--
%I	Job number	Yes#2, #17	--
%Y	The number of executions of jobnets or jobs that ended normally after the registration for execution#13	Yes	--
%B	Scheduled execution start date and time obtained from a computed processing cycle#7	Yes#4, #18, #22	--
%b	Scheduled execution start date and time obtained from a computed processing cycle#7	Yes#4, #19	--
%a	Estimated time required for execution#7	Yes#5, #16, #22	--
%O	Scheduled execution end date and time obtained from a computed processing cycle#7	Yes#4, #14, #20, #22	--
%o	Scheduled execution end date and time obtained from a computed processing cycle#7	Yes#4, #14, #21, #22	--
%v	Start time of the period that schedule and result information is output#7, #28	Yes#6	Yes#6
%w	End time of the period that schedule and result information is output#7	Yes#6	Yes#6
%F	Hold attribute of the next execution schedule#26 yes no Before Abnormal End Before Warning End	Yes	--
%i	Type of registration for execution immediate definit planned simulation	Yes#9	--
%l	Execution registration number#7	Yes#29	--
%r	Standard error output file name If the standard error output file does not exist, the default standard error output file name is output. The standard error output file will not exist when, for example, no jobs have been executed or no errors have occurred. If an external database is used, a standard error output file is created in the directory specified for the STDFILEOUTDIR environment setting parameter, and the file name is output to the standard output. Output example: /var/opt/jp1ajs2/jobinf/7.14a.0.8.err	Yes #8, #23	--
%d	Delay status none start-delay nest-start-delay end-delay nest-end-delay	Yes#25	--
%#	execution-ID	Yes#8	--
%m	Time at which start conditions are effective unlimited#7	Yes#11	--
%q	Number of times by which start conditions are effective A decimal value unlimited	Yes#11	--

Legend:

Yes: Format indicators specifiable in the -f or -t option

--: Format indicators not specifiable in the -f or -t option

#1

Valid only for a unit type of net. In the other cases, an asterisk (*) is output.

#2

Valid only for a unit type of job. In the other cases, an asterisk (*) is output.

#3

Information about a jobnet having a generation number of 0.

#4

****/**/** **:** and ****/**/** **:**:** are output if you also specify the -g option.

#5

For a jobnet and job not executed, a value of 1 is assumed.

#6

****/**/** **:**:** is output if you do not specify the -b -e, -v, or -w option.

#7

For details about the output format, see Table 3-23.

#8

For simulation, three asterisks (***) are output.

#9

Effective only when the unit type is net. Otherwise, three asterisks (***) are output.

#10

For a unit that is added while it is suspended, its output reads "plan unexecuted" if the existing upper-level unit is completed. Otherwise, the output reads "unplanned".

#11

Effective only when the unit type is net or condn. Otherwise, three asterisks (***) are output.

#12

For a job, the submitted time is output. For a queueless job, the time when the execution of the job was requested is output.

#13

The total count after registration is output, regardless of the number of logs to keep or generations to be output.

#14

The sum of the values of Scheduled execution start date and time obtained from a computed processing cycle and Estimated time required for execution is output as the time.

#15

The start time at which the unit was re-executed is displayed.

When the unit is re-executed, the date/time re-execution started is set at the point re-execution of the upper-level jobnets started. If the root jobnet is being executed, however, the date/time of re-execution start is not set for the root jobnet.

When the root jobnet has been completed, the date/time re-execution started is set only for the root jobnet if the root jobnet is specified at the point re-execution started.

#16

Output when -b, -e, -v, -w, -B, or an execution ID is specified.

In other cases, 00:00:00 is output.

#17

For a queueless job, three asterisks (***) are output.

#18

For a jobnet or job that has been completed, the date/time that is output here is the same as the actual date/time execution started for the jobnet or job (%St).

#19

For a jobnet or job that has been completed, the date/time that is output here is the same as the actual date/time execution started for the jobnet or job (%st).

#20

For a jobnet or job that has been completed, the date/time that is output here is the same as the actual date/time execution was completed for the jobnet or job (%E).

#21

For a jobnet or job that has been completed, the date/time that is output here is the same as the actual date/time execution was completed for the jobnet or job (%e).

#22

A result of execution simulation is output. For details about execution simulations, see 4.4.2(2) Execution simulation in the manual JP1/Automatic Job Management System 3 Overview.

If the schedule is changed temporarily, execution simulation is performed based on the new time.

#23

Effective only when the unit type is job, netcn, or a connection-destination jobnet.

Otherwise, three asterisks (***) are output.

#24

Effective only when the unit type is net.

Otherwise, none is output (when the language type is English).

#25

Effective only when the unit type is any of the following:

net, pjob, job, qjob, evwjb, flwjb, mlwjb, mqwjb, mswjb, lfwjb, ntwjb, tmwjb, evsjb, mlsjb, mqsjb, mssjb, cmsjb, pwljb, pwrjb, cupjb, cuujb

Otherwise, three asterisks (***) are output.

#26

Effective only when the status of the jobnet or job is any of the following:

Wait for start time, Wait for prev. to end, Waiting to execute, Being held

Otherwise, three asterisks (***) are output.

#27

Effective only when the unit type is net or rmnet. Otherwise, three asterisks (***) are output.

#28

For a flexible job, the following time is output.

When a relay agent is used:

Start time or end time of execution of the relay agent

When no relay agent is used:

Start time or end time of execution of the manager host

#29

For simulation, a non-scheduled generation, or a generation in Shutdown status, three asterisks (***) are output.

#30

For details about the status of a jobnet or job, see 6.1 Status levels of jobnets, jobs, and jobnet connectors in the manual JP1/Automatic Job Management System 3 Overview.

Table 3‒21: Two-byte format indicators for outputting definition information about jobnets and jobs

Two-byte format indicator	Output information
%SP	The state of being suspended (or not) exist none
%OP	Execution date for a jobnet#1
%St	Actual execution start date and time of a jobnet or job#1
%st	Actual execution start date and time of a jobnet or job#1
%Pt	Date and time at which jobnet execution is to start#2, #10
%Jm	Full-path jobnet or job name (a root jobnet name is omitted for a unit in a planning group)
%Am	Character string specified with AJSPATH= (a root jobnet name is omitted for a unit in a planning group). Character string specified with %Jm except the part that follows the right-most slash (/).
%Ed	Whether or not to suppress the execution if the scheduled time for execution has passed during startup of the scheduler service.#3 yes: Suppress the execution no: Do not suppress the execution
%cm	Comment#4 (character string of up to 80 bytes)
%ab	Estimated time between the start of the abnormally ended job and the end of the root jobnet#1, #5
%an	Estimated time between the start of the unit next to the abnormally ended job and the end of the root jobnet#1, #5
%FG	Number of future generations #6 (from 1 to 99)
%ds	Date/time for monitoring the start delay #1
%de	Date/time for monitoring the termination delay #1, #7
%Ft	Hold attributes hold: Holds not-hold: Does not hold abend-hold: Holds if the previous state was abend warning-hold: Holds if the previous state was warning hold-set: Sets the hold attribute temporarily, or sets hold when jobs or jobnets are registered for execution hold-release: Releases the hold attribute temporarily
%MV	Macro variable name and passing information specified at the time jobnets are registered for execution or the macro variable name and inherit result information taken over when jobs are executed#1, #4, #8, #9, #21
%CN	Unit full name of the connection-destination#11, #14 If a jobnet connector is specified, the unit full name of the connection-destination jobnet is output. If a connection-destination jobnet is specified, the unit full name of the jobnet connector is output.
%CI	Execution ID of the connection-destination#11, #12 If a jobnet connector is specified, the execution ID of the connection-destination jobnet is output. If a connection-destination jobnet is specified, the execution ID of the jobnet connector is output.
%CS	Method for controlling the execution order of the connection-destination jobnet#13
%CH	Host name of the connection-destination#11, #15 If this format indicator is specified for a jobnet connector, the host name of the connection-destination jobnet is output. If this format indicator is specified for a connection-destination jobnet, the host name of the jobnet connector is output.
%CF	Name of the scheduler service for the connection-destination#11, #15 If this format indicator is specified for a jobnet connector, the name of the scheduler service for the connection-destination jobnet is output. If this format indicator is specified for a connection-destination jobnet, the name of the scheduler service for the jobnet connector is output.
%RI	Release-ID#16
%so	Standard output file name#17, #18 The assumed standard output file name is output even if the standard output file does not exist. For example, the file does not exist if you specify a unit that does not use the standard output (an OR job, judgment job, event job, jobnet connector, or connection-destination jobnet) or specify a job that has not been executed. If an external database is used, a standard output file is created in the directory specified for the STDFILEOUTDIR environment setting parameter, and the standard output file name is output to the standard output.
%PW	Whether any aspect of the wait condition is yet to be satisfied. exist: The wait condition is not satisfied none: The wait condition is satisfied ***: No wait condition is defined
%RY	Number of retry executions#19
%RC	Retry status wait: An error occurred in an executable file of a job. Waiting is in progress for the time set as the retry interval to pass. exec: The job is being executed as a retry execution. end: They retry execution of the job finished. ***: No retry execution is performed.
%RS	Retry registration time#1, #20 The date and time of submission for a retry execution (year, month, date, hour, and minute are output)
%Rs	Retry registration time#1, #20 The date and time of submission for a retry execution (year, month, date, hour, minute, and second are output)
%RT	Retry start time#1 The execution start date and time for a retry execution (year, month, date, hour, and minute are output)
%Rt	Retry start time#1 The execution start date and time for a retry execution (year, month, date, hour, minute, and second are output)

Note

The format indicators shown in Table 3-20 allow specifying a set of two alphabetic characters as a two-byte format indicator. For example, %S can be specified as -i %SS. The -f and -t options will not accept two-byte format indicators. That is, all of the following are incorrect: -f %JJ, -t %JJ, and -f %SP.

#1

For details about the output format, see Table 3-23.

#2

Effective only when the unit is a jobnet. Otherwise, an asterisk (*) is output.

#3

Effective only when the type of the unit is net, netcn, rmnet, or hlnet.

Otherwise, three asterisks (***) are output.

#4

Double quotation marks (") are output at the beginning and end of the character string.

If there is no value to be output, only "" is output.

#5

The required time is estimated based on the execution result after the root jobnet is registered for execution only when the -b, -e, -v, or -w option is specified. One minute is the estimate for a job that has never been executed in the generation containing a job that has ended abnormally. 0 seconds is the estimate for a job that has already ended normally. The information about a unit that has ended without being executed is not output by specifying the -b or -e option. To output the information about a unit that has ended without being executed, use the -v or -w option.

For details about the estimated required time, see Additional information 3 below.

#6

The *** string is output if the number of future generations is not specified at the time of registration for execution. This is the information about the root jobnet, which is 0 in the generation number sequence.

#7

If you use the time-required-for-execution to monitor the date/time for end delay, the monitoring date/time is not output. The * string is output instead.

#8

This is effective only when the unit type is root jobnet (excluding remote jobnets) or job. Otherwise, the *** string is output.

#9

The "" string is output for a pseudo schedule.

#10

The date and time that execution has been scheduled is output. If the schedule is temporarily changed, the new schedule is output.

#11

This is effective only when the unit type is a jobnet connector or jobnet (connection-destination jobnet).

Otherwise, the *** string is output. The *** string is also output when permission to view the jobnet connector or connection-destination jobnet is not granted.

If an invalid unit is specified as the unit to be connected by the jobnet connector or connection-destination jobnet, the execution ID, unit full name, host name, and scheduler service name are displayed. However, the status of the unit changes to Ended abnormally because a definition error occurs during execution.

To check whether the definition is correct, specify the jobnet connector in the ajschkdef command. For details on the ajschkdef command, see ajschkdef in 3. Commands Used for Normal Operations and 8. Definition Pre-Check in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

#12

If a jobnet connector or connection-destination jobnet is defined on a different host or in a different scheduler service, the *** string is output for a generation scheduled to be executed.

For details about how to check the execution ID of a jobnet connector or connection-destination jobnet defined on a different host or in a different scheduler, see Additional information 4 below.

#13

This is effective only for a connection-destination jobnet. Otherwise, three asterisks (***) are output.

#14

If Connection range is Other service, the information defined for the unit is output.

#15

If Connection range is Same service, the *** string is output.

#16

For a release target jobnet (a root jobnet for which release entry is made) or its subordinate unit, the release ID is output. Otherwise, three asterisks (***) are output.

#17

This is effective only when the unit type is any of the following:

net,pjob,job,qjob,evwjb,flwjb,mlwjb,mqwjb,mswjb,lfwjb,ntwjb,tmwjb,evsjb,mlsjb,mqsjb,mssjb,cmsjb,pwljb,pwrjb,cupjb,cuujb,orjob,jdjob,netcn

Otherwise, three asterisks (***) are output.

#18

For simulation, three asterisks (***) are output.

#19

0 is output if retry execution is not performed. For units that are not subject to automatic retry, *** is output.

#20

For a job, the time when the job was submitted is output. For a queueless job, the time when job execution was requested is output.

#21

For details about the result of inheriting information via macro variables, see 2.2.6(2)(b) Viewing the result of inheriting information via macro variables in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Table 3‒22: Other format indicators

Format indicator	Output information
%%	%
%n	Line feed character
%t	Tab character
%x	Current date#
%X	Current time#

#

Time at which you started executing the ajsshow command. For details about the output format, see the following table:

Table 3‒23: Output format of format indicators

Format indicator	Output format
	Japanese	English
%D %P %S %E %K %V %Q %B %O %m %St %Pt %ds %de %RS %RT	YYYY/MM/DD hh:mm For MM, DD, hh and mm, a zero (0) is prefixed. Example: 2009/07/01 12:30 Note, however, that if there is no information to be output for the unit, ****/**/** **:** is output.	MMM DD YYYY hh:mm For DD, if the value to be output is one digit, a space is prefixed. For hh and mm, a zero (0) is prefixed. Example: Jul 1 2010 12:30 Note, however, that if there is no information to be output for the unit, *** ** **** **:** is output.
%s %e %k %b %o %v %w %st %Rs %Rt	YYYY/MM/DD hh:mm:ss For MM, DD, hh, mm and ss, a zero (0) is prefixed. Example: 2009/07/01 12:30:00 Note, however, that if there is no information to be output for the unit, ****/**/** **:**:** is output.	MMM DD YYYY hh:mm:ss For DD, if the value to be output is one digit, a space is prefixed. For hh and mm, a zero (0) is prefixed. Example: Jul 1 2010 12:30:00 Note, however, that if there is no information to be output for the unit, *** ** **** **:** is output.
%x %OP	YYYY/MM/DD For MM and DD, a zero (0) is prefixed. Example: 2009/07/01 Note, however, that if there is no information to be output for the unit, ****/**/** is output.	MMM DD YYYY For DD, if the value to be output is one digit, a space is prefixed. Example: Jul 1 2010 Note, however, that if there is no information to be output for the unit, *** ** **** **:** is output.
%X %a %ab %an	hh:mm:ss Example: 12:30:30
%l	YYYYMMDDNNN Example: Job whose execution registration number is 20100701001 20100701001
%MV	"information-1:information-2"[,"information-1:information-2"[...]] information-1: macro variable name information-2: passing information, or inherit result information (Example 1) For the root jobnet "AJS2ENV:/data/job_report","AJS2COM:c:\temp\test.exe" (Example 2) For a job "AJS2ENV:/data/job_report","AJS2COM:c:\temp\test.exe"

To Page Top

Additional information 2

The following table shows differences between information output when a target unit is automatically selected from the units in a planning group and that output when a target unit is not automatically selected.

Table 3‒24: Differences in output information depending on whether a target unit is automatically selected from the units in a planning group

Format indicator	When a target unit is automatically selected	When a target unit is not automatically selected
%p %P %M	Information about the unit to be executed next in the planning group	Schedule for the next execution of the specified unit
%G	Generation number obtained by integrating execution information for the root jobnets in the planning group	Generation number for the specified unit only
%l	Execution registration number obtained by integrating execution information for the root jobnets in the planning group	Execution registration number for the specified unit only
%Y %a	This information is maintained for each unit. Information for each unit is output even if you specify the function for automatically selecting a target unit.
%B %b %O %o	Information obtained from processing cycle calculation is calculated based on information maintained for each unit. Information for each unit is output even if you specify the function for automatically selecting a target unit.

The following example planning group definition shows differences in information output with %P, %G, and %l depending on the specification with the -X option.

Example planning group definition

Planning group (/group1) has three units, /group1/jobnet001, /group1/jobnet002, and /group1/jobnet003.

The scheduled start times for the units are as follows:

The scheduled start time for /group1/jobnet001 is 08:00 (absolute time).

The scheduled start time for /group1/jobnet002 is 09:00 (absolute time).

The scheduled start time for /group1/jobnet003 is 10:00 (absolute time).

Example 1:

Information output with %P when the -X option is set to yes.

ajsshow -f "Next schedule=%P %C %J" -g  1 -X yes  /group1

Output result

Next schedule=Aug 13 20XX 08:00 normal /group1/jobnet003

Explanation:

In this case, the command outputs the next scheduled execution time for the unit to be executed next (/group1/jobnet001) under the root jobnets in the planning group.

Example 2:

Information output with %P when the -X option is set to no.

ajsshow -f "Next schedule=%P %C %J" -g  1 -X no  /group1/jobnet003

Output result

Next schedule=Aug 15 20XX 10:00 normal /group1/jobnet003

Explanation:

In this case, the command outputs the next scheduled execution time for the specified unit (/group1/jobnet003).

Example 3:

Information output with %G when the -X option is set to yes.

ajsshow -f "Generation=%G Start time=%S %C %J" -g  3 -X yes  /group1

Output result

Generation=1 Start time=Aug 12 20XX 10:00 normal /group1/jobnet003
Generation=2 Start time=Aug 11 20XX 09:00 normal /group1/jobnet002
Generation=3 Start time=Aug 10 20XX 08:00 normal /group1/jobnet001

Explanation:

In this case, the command outputs the generation number obtained by integrating execution information for the root jobnets in the planning group.

Example 4:

Information output with %G when the -X option is set to no.

ajsshow -f "Generation=%G Start time=%S %C %J" -g  3 -X no  /group1/jobnet001

Output result

Generation=1 Start time=Aug 10 20XX 08:00 normal /group1/jobnet001
Generation=2 Start time=Aug  7 20XX 08:00 normal /group1/jobnet001
Generation=3 Start time=Aug  4 20XX 08:00 normal /group1/jobnet001

Explanation:

In this case, the command outputs the generation number based on execution information for the specified unit.

Example 5:

Information output with %l when the -X option is set to yes.

ajsshow -f "Registration number=%l Start time=%S %C %J" -b 20XX/8/3  -X yes  /group1

Output result

Registration number=20XX0803001 Start time=Aug  3 20XX 08:00 normal /group1/jobnet001
Registration number=20XX0803002 Start time=Aug  3 20XX 09:00 normal /group1/jobnet002
Registration number=20XX0803003 Start time=Aug  3 20XX 10:00 normal /group1/jobnet003

Explanation:

In this case, the command outputs the execution registration number obtained by integrating execution information for the root jobnets in the planning group.

Example 6:

Information output with %l when the -X option is set to no.

ajsshow -f "Registration number=%l Start time=%S %C %J" -b 20XX/8/3  -X no  /group1/jobnet003

Output result

Registration number=20XX0803001 Start time=20XX/08/03 10:00 Normal end /group1/jobnet003

Explanation:

In this case, the command outputs the execution registration number based on execution information for the specified jobnet.

To Page Top

Additional information 3

The following example shows how to calculate the estimated required time for a job that has ended abnormally.

Example 1:

The following describes how to calculate the estimated required time to determine whether to immediately re-execute a job that has ended abnormally, using the example jobnet configuration as shown below.

The jobs /jobnet1/nestjobnet001/job3 and /jobnet1/nestjobnet002/job2 have ended abnormally.

The following shows the output information and output results for %ab when the -v and -w options are specified.

Output information

ajsshow -i "Estimated required time=%ab UnitName=%JJ" -v 20XX/2/12 -w 20XX/2/12 -RN /jobnet1

Output result

Estimated required time=07:00:00 UnitName=/jobnet1
Estimated required time=07:00:00 UnitName=/jobnet1/nestjobnet001
Estimated required time=03:00:00 UnitName=/jobnet1/nestjobnet002

Explanation:

The output results indicate that the execution of jobnet001 will require seven hours so that you might decide to re-execute only this unit (jobnet1/nestjobnet001) at night or immediately re-execute only the jobnet1/nestjobnet002 unit, which will require three hours.

Example 2:

Suppose the jobnet that follows the abnormally ended job has a scheduled start time specified. The result of calculating the estimated required time may vary with whether the time when the job ends due to the start of re-execution precedes or follows the scheduled start time for the next jobnet.

• If the time when the job ends due to the start of re-execution precedes the scheduled start time for the next jobnet

  

  The job /jobnet1/nestjobnet001/job2 has ended abnormally. The scheduled start time for the next jobnet (/jobnet1/nestjobnet002) is 05:00.

  If re-execution starts at 03:00, the job /jobnet1/nestjobnet001/job2 is executed between 03:00 and 04:00 and nestjobnet001 ends at 04:00. The jobnet nestjobnet002 waits until 05:00 (scheduled start time) and then starts at 05:00 and ends at 07:00. The following shows the output information and output results:

Output information

ajsshow -i "Estimated required time=%ab UnitName=%JJ" -v 20XX/8/21 -w 20XX/8/21 -d 20XX/8/21 -h 3:00 -RN /jobnet1

Output result

Estimated required time=04:00:00 UnitName=/jobnet1
Estimated required time=01:00:00 UnitName=/jobnet1/nestjobnet001
Estimated required time=02:00:00 UnitName=/jobnet1/nestjobnet002

Explanation:

The output results indicate that jobnet1 will require four hours, 3:00 to 7:00.

• If the time when the job ends due to the start of re-execution follows the scheduled start time for the next jobnet

  

  The job /jobnet1/nestjobnet001/job2 has ended abnormally. The scheduled start time for the next jobnet (/jobnet1/nestjobnet002)is 05:00.

  If re-execution starts at 05:00, the job /jobnet1/nestjobnet001/job2 is executed between 05:00 and 06:00 and nestjobnet001 ends at 06:00. The jobnet nestjobnet002, for which the scheduled start time, 05:00 is already passed, is immediately executed and ends at 08:00. The following shows the output information and output results:

Output information

ajsshow -i "Estimated required time=%ab UnitName=%JJ" -v 20XX/8/21 -w 20XX/8/21 -d 20XX/8/21 -h 5:00 -RN /jobnet1

Output result

Estimated required time=03:00:00 UnitName=/jobnet1
Estimated required time=01:00:00 UnitName=/jobnet1/nestjobnet001
Estimated required time=02:00:00 UnitName=/jobnet1/nestjobnet002

Explanation:

The output results indicate that jobnet1 will require three hours, 5:00 to 8:00.

As shown above, you can specify the -d and -h options when calculating the estimated required time to determine how long re-execution will take depending on the time when re-execution is started.

To Page Top

Additional information 4

If a jobnet connector or a connection-destination jobnet connector is defined on a different host or in a different scheduler service, *** is output even if %CI is specified in the -i option.

If you want to check the execution ID of a jobnet connector or connection-destination jobnet defined on a different host or in a different scheduler, remotely execute the ajsshow command as described in the following procedure.

To check the execution ID of a jobnet connector or connection-destination jobnet defined on a different host or in a different scheduler:

1. Remotely execute the ajsshow command to display the host name, scheduler service name, and unit full name of the connection-destination.

   Execute the following command:

   ajsshow -v 20XX/07/01 -i "%CH %CF %CN" unit-name

2. Display the execution ID of the connection-destination from the information displayed in step 1.

   Execute the following command:

   host-name-displayed-in-step-1:scheduler-service-name-displayed-in-step-1:ajsshow -v 20XX/07/01 -i "%CI" unit-name

To Page Top

Additional information 5

If you specify a for the -g option, execution result information for jobnets with start conditions specified is output in order from the generation with the latest scheduled start time to the one with the earliest.

If you register a jobnet for execution with start conditions specified, a generation for monitoring the start conditions is created when the start time is reached. At the same time, generations in the Wait for start cond. status are also created and are executed when the start conditions are satisfied.

The scheduled start time for the generation being monitored is also assumed for the generations in the Wait for start cond. status and the generations executed when start conditions are satisfied. If you are using jobnets with start conditions and jobnets without start conditions, note the order in which the execution result information is output.

The following shows an example when the number of logs to keep is 10. In this example, a jobnet (net) with start conditions specified is registered for execution, and later a jobnet without start conditions specified is registered for execution.

As shown, a jobnet (net) with start conditions specified is registered for execution on March 1 and a generation for monitoring the start conditions is created (1-0 in the figure). At the same time, generations in the Wait for start cond. status are created. These generations are executed on March 2, March 4, and March 5 when their start conditions are satisfied (1-1, 1-2, and 1-3 in the figure).

In addition, a jobnet (net) without start conditions specified is registered for execution on March 3(2 in the figure).

Output information

ajsshow -f "Generation=%G %J %# %C" -g a -T /net

Output result

Generation=1 /net @A103 Normal end
Generation=2 /net @A105 Wait for start cond.#
Generation=3 /net @A104 Normal end#
Generation=4 /net @A102 Normal end#
Generation=5 /net @A101 Normal end#
Generation=6 /net @A100 Now monitoring#

# Execution result information for a generation with start conditions specified

Explanation:

When you execute the ajsshow command to output execution result information, the result of executing the jobnet that was registered for execution on March 3 is output as generation 1, since it is the latest execution result of the jobnet (net). For generations 2 to 6, the results of executing the jobnet with start conditions registered for execution on March 1 are output in order by generation according to the generation whose start conditions were satisfied last.

To Page Top

Example 1

The following command outputs the results of executing jobnet net1, and jobnets and jobs in it to the standard output file.

ajsshow -l net1

To Page Top

Example 2

The following command outputs two generations of results of executing a jobnet in the job group group1. The information to be displayed is the full-path jobnet name, the execution start time, and the execution end time.

ajsshow -t"Generation: %G" -g2 -f"%J %S %E" -RE /group1

Output example

Generation: 1
/group1/net1 Jun  8 20XX  10:00 Jun  8 20XX  12:00
Generation: 2
/group1/net1 Jun  1 20XX  10:00 Jun  1 20XX  11:30
Generation: 1
/group1/net2 Jun  8 20XX  11:00 Jun  8 20XX  11:30
Generation: 2
/group1/net2 Jun  1 20XX  11:00 Jun  1 20XX  12:00

To Page Top

Example 3

The following command outputs scheduled execution information (jobnet name, generation number and execution start time) on jobnet net for July 2010 (July 1, 2010 to July 31, 2010), displaying the target output period on the title row.

ajsshow -t "Period  %v-%w" -f" %j %G %B"-b 2010/7/1 -e 2010/7/31 /net

Output example

Period   Jul  1 2010  00:00:00-Jul 31 2010 23:59:59
 net -5  Jul  7 2010    10:00
Period   Jul  1 2010  00:00:00-Jul 31 2010 23:59:59
 net -6  Jul 14 2010    10:00
Period   Jul  1 2010  00:00:00-Jul 31 2010 23:59:59
 net -7  Jul 21 2010    10:00
Period   Jul  1 2010  00:00:00-Jul 31 2010 23:59:59
 net -8  Jul 31 2010    10:00

To Page Top

Example 4

The following command outputs the name of the standard error output file for job job1 in jobnet net, whose execution registration number is 20100701001. Assume that the job error information directory (/var/opt/jp1ajs2/jobinf) is set for the JOBINFDIR environment setting parameter.

ajsshow -B 20100701001 -r /net/job1

Output example

/var/opt/jp1ajs2/jobinf/e/67/0.e.err

To Page Top

Example 5

For the following jobnet (net) and jobs (job1, job2, and job3) under the jobnet, this example specifies the period using the -b, -e, -v, and -w options to output the execution start and end dates and times.

Specifying 2010/07/21 in the -b and -e options

ajsshow -b 2010/07/21 -e 2010/07/21  -f "%S %E %J"  -R /net

Output example

Jul 21 2010 10:00 Jul 22 2010 06:00 /net
Jul 21 2010 16:00 Jul 21 2010 21:00 /net/job1
Jul 21 2010 21:00 Jul 22 2010 02:00 /net/job2

Explanation:

The calendar date is the target of output.

The output covers the information about net as well as job1 and job2 under net where execution is started on 2010/07/21.

Specifying 2010/07/21 in the -v and -w options

ajsshow -v 2010/07/21 -w 2010/07/21  -f "%S %E %J"  -R /net

Output example

Jul 21 2010 10:00 Jul 22 2010 06:00 /net
Jul 21 2010 16:00 Jul 21 2010 21:00 /net/job1
Jul 21 2010 21:00 Jul 22 2010 02:00 /net/job2
Jul 22 2010 02:00 Jul 22 2010 06:00 /net/job3

Explanation:

The execution date for the jobnet is the target of output.

The output covers the information about net as well as the three jobs under net where execution is started on 2010/07/21.

Specifying 2010/07/22 in the -b and -e options

ajsshow -b 2010/07/22 -e 2010/07/22 -f "%S %E %J"  -R /net

Output example

Jul 21 2010 10:00 Jul 22 2010 06:00 /net
Jul 21 2010 21:00 Jul 22 2010 02:00 /net/job2
Jul 22 2010 02:00 Jul 22 2010 06:00 /net/job3

Explanation:

The calendar date is the target of output.

The output covers the information about job2 where execution is ended on 2010/07/22, and job3 where execution is started on 2010/07/22.

Specifying 2010/07/22 in the -v and -w options

ajsshow -v Jul 22 2010 -w Jul 22 2010  -f "%S %E %J"  -R /net

Explanation:

The execution date for the jobnet is the target of output.

The output covers no information even if you specify 2010/07/22 in the -v and -w options because the execution date for net is 2010/07/21.

To Page Top

Example 6

This example explains how you can output information about a jobnet connector or connection-destination jobnet by using the -i option.

• jobnet connector

  host name: HOSTA

  scheduler service name: AJSROOT1

  unit name: /JC/jobnet-connector

  execution ID: @A544

• connection-destination jobnet

  host name: HOSTB

  scheduler service name: AJSROOT2

  unit name: /JC-NET

  execution ID: @A546

When a jobnet connector is specified for the -i option:

ajsshow -i "%JJ %TT %CH %CF %CN %CI %CS" /JC/jobnet-connector

Output example

/JC/jobnet-connector netcn HOSTB AJSROOT2 /JC-NET @A546 ***

When a connection-destination jobnet is specified for the -i option:

ajsshow -i "%JJ %TT %CH %CF %CN %CI %CS" /JC-NET

Output example

/JC-NET net HOSTA AJSROOT1 /JC/jobnet-connector @A544 nosync

To Page Top

Example 7

The following command outputs the name of the standard output file used by job job1 in jobnet net executed in the period from 2010/08/06 to 2010/08/07. Assume that the job information storage directory (C:\Program Files\HITACHI\JP1AJS2\jobinf) is set for the JOBINFDIR environment setting parameter.

ajsshow -b 2010/08/06 -e 2010/08/07 -i "%so" /net/job1

Output example

C:\Program Files\HITACHI\JP1AJS2\jobinf\d\6e\0.e.std

To Page Top

Example 8

The following figure shows an example of using the -xi option for registering jobnet execution. 7/1 is registered when a start condition is used, and 7/2 is registered when a start condition is not used.

Information about the jobnet (netB) in the figure is output.

Example 1: When all generations are output and the -xi b option is specified

ajsshow -xw -xi b -g a /netB

Output example

Explanation:

Information about the monitoring generations, execution generations, and generations that do not use a start condition are output. Generations 1 to 4 in the figure are subject to output. Note, however, that the ajsshow command ends abnormally because generations 2 and 3 are execution generations and there is no wait information.

Example 2: When all generations are output with the -xi c option specified

ajsshow -xw -xi c -g a /netB

Output example

Explanation:

Generations 1 and 4 are subject to output, because information about the monitoring generation and generations that do not use a start condition is to be output. Generations 2 and 3 are not output because they are execution generations.

To Page Top

Output example 1

• When you specify the -s option

  

• When you specify the -p option

  

• When you specify the -l option

  

To Page Top

Output example 2

• When the -xw and -xi b options are specified

  

• When the -xw and -xi c options are specified

  

To Page Top