7.2 Collecting Job Operation Information window

This section describes the Collecting Job Operation Information window and settings for the Windows (GUI-based) edition. Because the available functionality is identical to the jprcollect command and used in the same manner, also refer to the description of the jprcollect command in 8. Commands.

In the Collecting Job Operation Information window, you can collect job operation information from JP1/AJS and generate job operation information files.

Figure 7‒3: Collecting Job Operation Information window

The following explains the displayed items.

Host name

Displays the name of the connection-destination host.

This item is unavailable when you display the Collecting Job Operation Information window from JP1/AJS3 - View.

Unit name

Specify the name of the unit whose job operation information you want to collect. JP1/AJS3 - Print Option collects information for the specified unit and all its subordinate units. You cannot leave this field blank.

This field does not accept wildcards (such as * and ?).

If you specify more than one unit name in the Unit name field, an error occurs when you attempt to output a job operation document. This item is unavailable when you display the Collecting Job Operation Information window from JP1/AJS3 - View.

You cannot display the Collecting Job Operation Information window from JP1/AJS3 - View if the name of the selected unit contains any of the following characters:

" & ' * < > ? [ \ ] ^ ` { | } ~ $

Collects all units under the root node

If you select this check box, you can specify a root job group in the Unit name field.

You cannot specify a root job group in Unit name when this check box is cleared.

If you select Collects all units under the root node and specify a root job group in Unit name, JP1/AJS3 - Print Option collects information for all units under the root job group.

This item is unavailable when you display the Collecting Job Operation Information window from JP1/AJS3 - View.

Service name

Specify the name of the JP1/AJS scheduler service. You can leave this field blank. If you do not specify a service name, JP1/AJS3 - Print Option uses the scheduler service set in JP1/AJS.

This item is unavailable when you display the Collecting Job Operation Information window from JP1/AJS3 - View.

Character code

Displays the character encoding used by the scheduler service to which the unit belongs.

This item is unavailable when you display the Collecting Job Operation Information window from JP1/AJS3 - View.

Collection period

Specify how you wish to define the collection period for execution schedules and execution results, and enter the period for which to collect information. The collection period lasts from the base time on the start date until 23 hours, 59 minutes, and 59 seconds after the base time on the end date.

Specify period

Select Date specification, Monthly specification, Relative month specification, Daily specification, or Not specified. Date specification is selected by default.

Also, select Calendar date or Execution date as the base period. Calendar date is selected by default.

However, Execution date can be specified for collection only in JP1/AJS3 - Print Option Manager 11-10 or later.

Date specification

Select this option when you want to define the collection period for execution schedules and results by specifying a start date and end date.

The figure below shows the contents of the Period area when you select this option.

Initially, the date on which you open the Collecting Job Operation Information window is set as the start date and end date.

[Figure]

Period

Specify the start date and end date of the collection period for execution schedules and results.

The earliest date you can specify is January 1st, 1994, and the latest is December 31st, 2036.

Monthly specification

Select this option when you want to define the collection period for execution schedules and results by month.

The figure below shows the contents of the Period area when you select this option.

By default, This month is selected.

[Figure]

Period

Specify the collection period for execution schedules and results. Select one or more of Last month, This month, and Next month.

JP1/AJS3 - Print Option collects execution schedules and results from the first day to the last day of the selected months.

You cannot click the Output button if only Last month and Next month are selected.

Last month

When selected, the execution schedules and results for the previous month are collected.
This month

When selected, the execution schedules and results for the current month are collected.
Next month

When selected, the execution schedules and results for next month are collected.

Relative month specification

Select this option when you want to define the collection period for execution schedules and results as a month relative to the current month.

The figure below shows the contents of the Period area when you select this option.

The default is From this month for xx months.

[Figure]

Period

Specify the month from which to begin collecting execution schedules and results, and the number of months for which to collect the information.

You can specify the current month, a month in the past, or a future month as the start of the collection period.

JP1/AJS3 - Print Option collects execution schedules and results for the specified number of months, starting from the first day of the first month in the collection period.

From xx months ago for xx months

Select this option to start the collection period in a past month. In the first field, specify the first month of the collection period as a number of months prior to the current month. In the second field, specify the number of months for which to collect information.

You can specify a value from 1 to 12 in each field.

You must specify a value in both fields.

Example:

Suppose that on July 17th, you specify From 3 months ago for 6 months:

JP1/AJS3 - Print Option collects execution schedules and results for the period from April 1st to September 30th.
From this month for xx months

Select this option to use the current month as the start of the collection period. Specify the number of months for which to collect execution schedules and results, starting from the current month.

You can specify a value from 1 to 12. You cannot leave the field blank.

Example

Suppose that on July 17th, you specify From this month for 3 months:

JP1/AJS3 - Print Option collects execution schedules and results for the period from July 1st to September 30th.
From xx months later for xx months

Select this option to use a future month as the start of the collection period. In the first field, specify the first month of the collection period as a number of months in the future. In the second field, specify the number of months for which to collect the information.

You can specify a value from 1 to 12 in each field.

You must specify a value in both fields.

Example:

Suppose that on July 17th, you specify From 2 months later for 3 months:

JP1/AJS3 - Print Option collects execution schedules and results for the period from September 1st to November 30th.

Daily specification

Select this option when you want to define the collection period for execution schedules and results by Daily.

The figure below shows the contents of the Period area when you select this option.

By default, Today is selected.

[Figure]

Period

Specify the collection period for execution schedules and results. Select one or more of Last Day, Today, and Next Day.

You cannot click the Output button if only Last Day and Next Day are selected.

Last Day

When selected, the execution schedules and results for the previous day are collected.
Today

When selected, the execution schedules and results for the today are collected.
Next Day

When selected, the execution schedules and results for next day are collected.

Not specified

Select this option if you do not want to collect execution schedules and results.

Collects the last update time

Select this check box to collect information about the last update times for the specified unit and its subordinate units. You can only collect last update times from JP1/AJS3 - Manager version 09-00 or later.

If this check box is cleared, JP1/AJS3 - Print Option does not collect last update times.

Collects the release IDs

Select this check box to collect jobnet information for each release ID when the registration information for the specified unit includes jobnet release information. If the unit has several release schedules, information is output for all release IDs. You can only collect information for specific release IDs from JP1/AJS3 - Manager version 09-00-04 or later.

For details on jobnet release, see the description of the jobnet release functionality in the manual JP1/Automatic Job Management System 3 Overview.

Job operation information output file name

Specify the name of the job operation information file to which to output the collected job operation information. You cannot leave this field blank.

If you display the Collecting Job Operation Information window from JP1/AJS3 - View, the default file name appears in this field. The path of the default file name is the value specified in the Saved job operation information file linking with View field in the Environment Settings window, and the file name is the date and time when the Collecting Job Operation Information window was displayed (in the format YYYYMMDDhhmmss^#). The extension is .aoi.

#: YYYY: four-digit year; MM: Month (01 to 12), DD: Day (01 to 31), hh: Hour (00 to 23), mm: minutes (00 to 59), ss: seconds (00 to 59)

Include the extension (.aoi) when you specify the file name. Do not use machine-dependent characters or any of the following symbols in the file name.

\ / : * ? " < > | $ ` -

If you use a hyphen (-), you can specify other than top of the file path name.

If you specify a file name but not a folder, the file is created in the installation folder. If you displayed the Collecting Job Operation Information window from JP1/AJS3 - View, the file is created in the JP1/AJS3 - View installation folder.

File names must be no more than 63 bytes, and the entire path must be no more than 255 bytes.

If you display the Collecting Job Operation Information window from JP1/AJS3 - View, the folder path must be no more than 194 bytes.

Browse

Click this button to select the output file for job operation information from an Open File dialog box.

Output

Starts the collection of job operation information.

Close

Closes the window.

Supplementary note: Execution logs for job operation information collection

Each time you collect job operation information, JP1/AJS3 - Print Option creates a file containing execution log information for the collection process. The file name is the same as the file name specified in Job operation information output file name, but with the extension .log.

JP1/AJS3 - Print Option collects job operation information by executing the ajsprint and ajsshow commands provided by JP1/AJS. Execution log information consists of the execution results of these commands. If the collection process fails, you can use the contents of this file to find out why.

The following figure shows the contents of an execution log file:

[Figure]

Supplementary note: Location of execution log files

If you display the Collecting Job Operation Information window from the Windows Start menu:

The execution log file is created in the same folder as the job operation information file.
If you display the Collecting Job Operation Information window from JP1/AJS3 - View:

No execution log file is created if the job operation information is output without any issues. If an error occurs, an execution log file is created in the following folder or directory:

In Windows

JP1/AJS3-Print-Option-Manager-installation-folder\Tmp

In UNIX

/opt/jp1ajs2pom/tmp

Supplementary note: How the Calendar date and Execution date options work differently

The following describes how the Calendar date and Execution date options work differently during collection:

Example 1: If Calendar date is selected in the Collecting Job Operation Information window to collect schedules on May 25, 2016:

Monthly schedule in 48-hour view: The schedule that is defined for PC job F at 00:30 on May 26, which extends over two days, is not collected.

[Figure]

Example 2: If Execution date is selected in the Collecting Job Operation Information window to collect schedules on May 25, 2016:

Monthly schedule in 48-hour view: The schedule that is defined for PC job F at 00:30 on May 26, which extends over two days, is collected because the jobnet is scheduled to run on May 25.

[Figure]

Example 3: If Calendar date is selected in the Collecting Job Operation Information window to collect schedules on June 14, 2016:

Monthly schedule in 48-hour view: The schedule that is defined for PC job F at 00:30 on June 14, which extends over two days, is collected even though the jobnet is scheduled to run on June 13.

[Figure]

Example 4: If Execution date is selected in the Collecting Job Operation Information window to collect schedules on June 14, 2016:

Monthly schedule in 48-hour view: The schedule that is defined for PC job F at 00:30 on June 14, which extends over two days, is not collected because the jobnet is scheduled to run on June 13.

[Figure]

Example 5: If Calendar date is specified in the Collecting Job Operation Information window to collect schedules of Today:

When the collection is executed on December 8, 2017, the information of the job that is scheduled at 00:05 on December 9 and extends over two days is not collected.

[Figure]

Example 6: If Execution date is specified in the Collecting Job Operation Information window to collect schedules of Today:

When the collection is executed on December 8, 2017, the information of the job that is scheduled at 00:05 on December 9 and extends over two days is collected because the upper-level jobnet is scheduled to run on December 8.

[Figure]

Cautionary notes:

A job whose execution schedule and execution results exist within the range of the specified collection period is output. For a job whose execution started within the range of the collection period but ended beyond the range of the collection period, if you collect job operation information after the end of its execution, you can obtain the execution result data within the range of the collection period. You cannot obtain the execution result data beyond the range of the collection period.
When JP1/AJS3 - Manager is operating in a cluster environment, collect job operation information from the active node. To do so, specify the name of the scheduler service on the logical host as the service name.
If you select Monthly specification or Relative month specification, the collection period is determined based on the system time of the physical host, not the local time of the scheduler service. If the local time of the scheduler service is different from the system time of the physical host, select the Date specification option and specify a collection period based on the local time.
If a user without administrator privileges in an environment where UAC (User Account Control) is enabled, displays the Collecting Job Operation Information window from JP1/AJS3 - View, and specifies a protected folder such as C:\Program Files as the output destination for job operation information, the information might be redirected and saved to each user's VirtualStore folder.

Files are redirected when the save destination is a folder in one of the following directories:
- system-drive:\Windows
- system-drive:\Program Files
- system-drive:\Program Files (x86) (for 64bit Windows)
The redirected files are stored in the following directories:
- %LocalAppData%\VirtualStore\Windows
- %LocalAppData%\VirtualStore\Program Files
- %LocalAppData%\VirtualStore\Program Files (x86)
The default value of the %LocalAppData% is system-drive:\Users\OS-user-name\AppData\Local.
If a non-Administrator user displays the Collecting Job Operation Information window from the Start menu in a Windows Server 2019, Windows Server 2016 or Windows Server 2012 environment with UAC enabled, an error occurs if a protected folder such as C:\Program Files is specified as the output destination for job operation information. In this scenario, open the Collecting Job Operation Information window from an account with Administrator privileges.

JP1/AJS3 - Print Option uses the following information acquired by the JP1/AJS command ajsshow to determine the schedule information for jobs in the collection period:

Scheduled execution start date and time obtained from a computed processing cycle
Scheduled execution end date and time obtained from a computed processing cycle

If a job has finished executing, JP1/AJS3 - Print Option outputs the actual execution start and end times for the job, as shown in the example below.

Figure 7‒4: Example of monthly schedule information (with timestamps) output after acquiring operation information for Feb 1 to 28 at 12:00 on Feb 16

You can make sure that a document does not include actual execution histories by specifying a future date as the start date of the collection period.

If you display the Collecting Job Operation Information window from the Windows Start menu and collect job operation information with the JP1/AJS3 environment setting parameter ADMACLIMIT set to yes, the KAVR1000-E or KAVR5010-E error might occur. In that case, log on to the OS, create a JP1 user with the same name as the user account name that displayed the Collecting Job Operation Information window from the Windows Start menu, and then set the JP1 permission level for the JP1 resource group of the target units for the ajsprint command and the ajsshow command.

For details about the JP1 permission levels that are required to execute the ajsprint command and the ajsshow command, see the documentation for JP1/AJS3.
If you display the Collecting Job Operation Information window from the JP1/AJS3 - View window and collect job operation information with the JP1/AJS3 environment setting parameter ADMACLIMIT set to yes, the KAVR1000-E or KAVR5010-E error might occur. In that case, implement either of the following:

If you are operating the JP1/AJS3 - Print Option Manager service using a local system account (The default after installation is set to local system account.)

Create a JP1 user named system and set the JP1 permission level for the JP1 resource group of the target units for the ajsprint command and the ajsshow command.

If you are operating the JP1/AJS3 - Print Option Manager service using a user account

Create a JP1 user with the same name as the user account and set the JP1 permission level for the JP1 resource group of the target units for the ajsprint command and the ajsshow command.
If the JP1/AJS3 environment setting parameter AJSPRINTSORTUNITINF is set to yes, the related line information is output to the job operation information file in the character code ascending order for the preceding unit and succeeding unit. If the environment setting parameter AJSPRINTSORTUNITINF is set to no or a value is not set, the related line information is output in the creation order for the preceding unit and succeeding unit. For details, see the documentation for JP1/AJS3.
Communication between JP1/AJS3 - Print Option and JP1/AJS3 - Print Option Manager is not encrypted. Take either of the following procedures:
- Use linkage with JP1/AJS3 - View in a network environment where security measures are taken.
- Using, for example, an FTP to which security mode is set, transfer a job operation information file that has been output by JP1/AJS3 - Print Option Manager to JP1/AJS3 - Print Option, and then output a document.
The execution date can be specified for collection only in JP1/AJS3 - Print Option Manager 11-10 or later. When you open the Collecting Job Operation Information window from JP1/AJS3 - View, the Calendar date option is forced or a KAVR5024-E error occurs if the version of the destination is JP1/AJS3 - Print Option Manager 11-00 or earlier.
When you open the Collecting Job Operation Information window from JP1/AJS3 - View, a KAVR5010-E error occurs if the version of the destination is JP1/AJS3 - Print Option Manager 11-10 or earlier and the number of months specified for the relative month exceeds 6.
If you select Calendar date in Collection period, JP1/AJS3 - Print Option collects job operation information by executing the ajsshow command with -b and -e options.

If you select Execution date in Collection period, JP1/AJS3 - Print Option collects job operation information by executing the ajsshow command with -v and -w options.
If you add new a unit or change a unit name on JP1/AJS during collecting the job operation information, the job operation information file has inconsistent data and an error occurs to output job operation information as documents.

To Page Top