Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Operator's Guide


15.4.16 Detailed Definition - [Monitoring Files] dialog box

The Detailed Definition - [Monitoring Files] dialog box defines the details on monitoring a file.

This dialog box contains the items displayed in common, and also contains the following pages:

Organization of this subsection

(1) Items displayed in common

The following figure shows the items displayed in common.

Figure 15‒128: Items displayed in common in the Detailed Definition - [Monitoring Files] dialog box

[Figure]

The following explains the items displayed in common.

Unit name

Specify a unit name. Use a character string of up to 30 bytes. The default is Monitoring-Files.

Comment

Specify a comment for the unit. Use a character string of up to 80 bytes. The default is a blank.

Exec-agent

Specify the execution agent name to be assigned the task for monitoring a file. Use a character string of up to 255 bytes. If the version of the connection-target JP1/AJS3 - Manager is 09-50 or later, you can specify a macro variable instead. The default is a blank.

This item appears as a text box when either of the following applies:

  • The version of JP1/AJS - View or the connection-target JP1/AJS - Manager is earlier than 09-50

  • The unit is being defined under a remote jobnet

Otherwise, this item appears as a combo box in which you can select an execution agent. You can also directly enter an execution agent name into the combo box. The content of the list component of the combo box differs depending on whether execution agent profiles are enabled, and the contents of those profiles.

When execution agent profiles are disabled

The list is empty.

When execution agent profiles are enabled
  • If the specified job is associated with an execution agent profile

    The list displays the execution agents permitted for the specified job.

  • If the specified job is not associated with an execution agent profile

    If the upper-level unit is associated with an execution agent profile, the list displays the execution agents permitted for the upper-level unit.

    If the upper-level unit is not associated with an execution agent profile, the list will be empty.

For details about execution agents, see 5.1.1 Execution agents in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

Cautionary note

If you leave this text box blank, the system inherits the specification of the upper-level jobnet.

If an execution agent group for an upper-level jobnet has been specified, the system uses the execution agent group as the execution agent.

Because event jobs do not support an execution agent group, explicitly specify an execution agent name in Exec-agent. For details about the operation performed if an execution agent group is specified for an event job, see 7.6 Notes on using event jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Pass Info button

Specify information to be inherited by the subsequent job or jobnet. If you click the Pass Info button, the Detailed Definition - [Monitoring Files]- [Passing Information] dialog box appears. For more information, see 15.4.15 Detailed Definition - [event-job-icon-name] - [Passing Information] dialog box. This button is located at the bottom of the dialog box.

(2) Definition page

The following figure shows the Definition page in the Detailed Definition - [Monitoring Files] dialog box.

Figure 15‒129: Definition page in the Detailed Definition - [Monitoring Files] dialog box

[Figure]

The following explains the displayed items.

Monitoring file

Enter the name of the file you want to monitor. Use a character string of up to 255 bytes. If the version of the connection-target JP1/AJS3 - Manager is 09-50 or later, you can specify a macro variable instead. You must specify this item. The default is a blank.

You can specify the file name using either an absolute path name or wildcard characters consisting of an absolute path name and a wildcard (*).

You can click the ... button to select a file name from the dialog box that will appear.

Monitoring options

Select conditions for monitoring a file. The default is Create. You can select the following conditions:

  • Create

    Monitors whether a new file has been created. With Create selected, you can choose either Establish at file creation or Establish for existing files as the monitoring conditions. Choosing Establish for existing files starts the file monitoring job and, when there is already a file to be monitored, terminates the file monitoring job normally. If, however, the file to be monitored is busy, the file monitoring job continues its monitoring operation.

    The default is Establish at file creation.

  • Delete

    Monitors whether the file has been deleted.

  • Change size

    Monitors whether the file has been resized. You cannot select this item together with Final time write.

  • Final time write

    Monitors whether the last write time for the file has been changed. You cannot set this item together with Change size.

Monitoring interval

Specify a time interval to monitor the file. You can set 1 to 600 seconds. However, if you use wildcard characters to specify the target file, you can set 10 to 600 seconds. The default is a blank, meaning that the interval is 60 seconds. If you specify 60 for this item, the field will appear blank.

(3) Attributes page

The following figure shows the Attributes page in the Detailed Definition - [Monitoring Files] dialog box.

Figure 15‒130: Attributes page in the Detailed Definition - [Monitoring Files] dialog box

[Figure]

The following explains the displayed items.

Hold

Specify whether to place the unit in the hold status in advance. You can specify No or Yes. The default is No.

You cannot specify this item if you defined the file monitoring job in a start condition.

Type

Set the unit type to Normal or Recovery. The default is Normal.

You cannot specify this item if you defined the file monitoring job in a start condition.

Set timeout period

Select whether to set a time-out period for job execution. You can specify No or Yes. The default is No.

You cannot specify this item if you defined the file monitoring job in a start condition.

Timeout period

If you select Yes in Set timeout period, specify a time-out period in minutes. You can set 1 to 1,440 minutes. The default is a blank.

You cannot specify this item if you defined the file monitoring job in a start condition.

Status after close

If you select Yes for Set timeout period, select the status into which the event job is to be placed after the timeout period elapses. You can specify Killed, Ended normally, Ended with warning, and Ended abnormally. The default is Killed.

You cannot specify this item if you defined the file monitoring job in a start condition.

Delayed end

Specify whether to monitor delayed end of jobs based on time required for execution. Select the Time-required-for-execution check box to monitor delayed end of jobs. The check box is not selected by default.

When you select the Time-required-for-execution check box, specify the time required for execution for a job from 1 to 1,440 (in minutes).

This section appears for the JP1/AJS3 - View, or JP1/AJS2 - View of version 08-50 or later. For details about cautionary notes on monitoring of delayed end of jobs based on time required for execution, see 5.1.1(3) End delay monitoring based on time-required-for-execution in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

You cannot specify this item if you defined the file monitoring job in a start condition.

Owner

Even if you specify the owner, the owner will become invalid when the event job is executed.

JP1 resource group

Even if you specify the JP1 resource group, the JP1 resource group will become invalid when the event job is executed.

Executed by

Even if you specify the user who executes the job, the user will become invalid when the event job is executed. The user type for the event job is executed by the user authority activating JP1/AJS3.