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

[Contents][Glossary][Index][Back][Next]

15.4.36 Define Details - [Custom Job] dialog box

The Define Details - [Custom Job] dialog box defines the details on a custom job provided by the windows version of JP1 series programs.

You can define the following custom jobs.

Cautionary note
You cannot specify any job other than shown above.

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

Organization of this subsection
(1) Items displayed in common
(2) Definition page
(3) Attributes page

(1) Items displayed in common

The following figure shows the items displayed in common.

Figure 15-172 Items displayed in common in the Define Details - [Custom Job] 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 depends on the defined custom job.

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 or execution agent group name to be assigned the task of custom job execution. Use a character string of up to 255 bytes. You can also use macro variables if the version of the connection-destination JP1/AJS3 - Manager is 09-50 or later.
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.

(2) Definition page

The following figure shows the Definition page (for a PC job) in the Define Details - [Custom Job] dialog box for the standard custom jobs. The items displayed in this Definition page for the custom PC jobs are the same as in the Define Details - [PC Job] dialog box. For details, see 15.4.7 Define Details - [PC Job] dialog box.

The items displayed in the Definition page for the Unix job are the same as in the Define Details - [UNIX Job] dialog box. For details, see 15.4.6 Define Details - [UNIX Job] dialog box.

Figure 15-173 Definition page in the Define Details - [Custom Job] dialog box

[Figure]

The following explains the displayed items.

Priority
Select the priority of job execution. You can set None, or 1 to 5. The highest priority is 5. The default is None.
When None is selected, the priority depends on the definition of the upper-level jobnet. If None is specified for the relevant job and all its upper-level jobnets up to the highest one, 1 is assumed as the priority.

Standard output
Specify the name of the standard output file to be used for job execution. Use a character string of up to 511 bytes. Specify a full path file name. You can use a macro variable and $JP1AJS2_JPQSTDOUTTEMP$ in this field if the version of the connection-target JP1/AJS3 - Manager is 09-50 or later. If you specify $JP1AJS2_JPQSTDOUTTEMP$, the standard output file is a temporary file. The default is a blank.

Standard error
Specify the name of the standard error output file to be used for job execution. Use a character string of up to 511 bytes. Specify a full path file name. You can also use macro variables if the version of the connection-destination JP1/AJS3 - Manager is 09-50 or later. The default is a blank.

End judgment
Select conditions for end judgment.
Rule
The displayed items vary depending on the rule selected in the Rule drop-down list. In the initial status, Judgment by threshold is selected and the thresholds for the Warning and Abnormal levels are displayed. You can select one of the following rules for end judgment.
  • Always normal
    Always terminates the custom job normally. You can specify neither Warning nor Abnormal.
  • Always abnormal
    Always terminates the custom job abnormally. You can specify neither Warning nor Abnormal.
  • Normal if specified file exists
    Ends normally the custom job if the file specified in the File name text box that appears below the drop-down list exists. You can use a character string of up to 511 bytes to specify a file. You can also use macro variables if the version of the connection-destination JP1/AJS3 - Manager is 09-50 or later. The default is a blank.
  • Normal if file was updated
    Ends normally the custom job if the file set in the File name text box that appears below the drop-down list is updated. You can use a character string of up to 511 bytes to specify a file. You can also use macro variables if the version of the connection-destination JP1/AJS3 - Manager is 09-50 or later. The default is a blank.
    The system uses the update time to determine whether a file was updated. When a job is executed in UNIX, because the system truncates the timestamp to the second when making this determination, it might not recognize that a file has been updated when there is less than one second between updates. In this case, the job will end abnormally.
  • Judgment by threshold
    Define reference values for the normal end and the warning end, or for the normal end and the abnormal end. In the Warning and Abnormal text boxes, you can set 0 to 2,147,483,647.The default is a blank for Warning, and 0 for Abnormal.
    By default, the system assumes an abnormal end if the return code is other than zero. If you set Warning, the system assumes a normal end if the return code is from zero to the value of Warning. It assumes warning end if the return code is larger than the value of Warning. If you set Abnormal, the system assumes a normal end if the return code is from zero to the value of Abnormal. It assumes an abnormal end if the return code is not larger than -1 or larger than the value of Abnormal. If you specify both Warning and Abnormal, the system assumes as follows:
    Normal end: The return code is from zero to the Warning value
    Warning end: The return code is larger than the Warning value but not larger than the Abnormal value
    Abnormal end: The return code is not larger than -1 or larger than the Abnormal value.
    In UNIX, the return codes only have positive values from 0 to 255.
    If the program exits with a negative value, the return code is assumed to be 256 + (exit code). For example, if the program exists with -1, the system assumes 256 - 1 = 255.

Retry on abnormal end
Select whether to retry execution when the program ends in an error.
You can select this option when all of the following conditions are met:
  • The version of the connection-target JP1/AJS3 - Manager is 10-00 or later
  • The database of the connection-target JP1/AJS3 - Manager is a standard configuration
  • Judgment by threshold is selected in the Rule drop-down list
You can specify No or Yes. The default is No.
This item is displayed in JP1/AJS3 - View version 10-00 and later.

Return code
If Yes is selected for Retry on abnormal end, specify the range of return codes for which to retry jobs. The default is a blank.
  • Greater than or equal to
    Specify the lowest return code for jobs that are to be retried. A job is retried when its return code is greater than or equal to this value.
    You can specify a value in the range from 1 to 4,294,967,295. The default is a blank. If you omit this setting, a value one greater than the value specified in Abnormal is used.
  • Less than or equal to
    Specify the highest return code for jobs that are to be retried. A job is retried when its return code is less than or equal to this value.
    You can specify a value in the range from 1 to 4,294,967,295. The default is a blank. If you omit this setting, 4,294,967,295 is used.
This item is displayed in JP1/AJS3 - View version 10-00 and later.

Maximum retry times
When Yes is selected for Retry on abnormal end, specify the maximum number of times a job can be retried. You can specify a value in the range from 1 to 12. The default is 1.
This item is displayed in JP1/AJS3 - View version 10-00 and later.

Retry interval
When Yes is selected for Retry on abnormal end, specify how long the system waits between the error occurring and retrying the job. You can specify a value in the range from 1 to 10 (minutes). The default is 1.
This item is displayed in JP1/AJS3 - View version 10-00 and later.

User name
Specify the OS user name of JP1/AJS3 - Agent for job execution. Use a character string of up to 63 bytes. You can also use macro variables if the version of the connection-destination JP1/AJS3 - Manager is 09-50 or later. The default is a blank.
You must map this user to User who registered or User who owns for Executed by. However, if the execution-user fixing function is configured for the upper-level unit, you must map this user name to a fixed user regardless of the contents of the Executed by field.
By default, the primary user in the user mapping is applied for execution. For details about the user mapping, see the Job Management Partner 1/Base User's Guide.

Define detailed info.
If you click the Details button, the window for defining a program to be linked appears. For details about the items displayed in this window, see the program documentation.

(3) Attributes page

The following figure shows the Attributes page in the Define Details - [Custom Job] dialog box.

Figure 15-174 Attributes page in the Define Details - [Custom Job] dialog box

[Figure]

The following explains the displayed items.

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

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

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

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.

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(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.

Owner
Specify the owner of the unit. Use a character string of up to 31 bytes. The default is the login JP1 user name. Note that if the upper-level unit-attribute inheritance function has been set for the upper-level jobnet, the default is the owner of the upper-level unit.

JP1 resource group
Specify a JP1 resource group name. Use a character string of up to 63 bytes. You can specify alphanumeric characters and underscores (_). The default is the JP1 resource group name of the upper-level unit. If you specify a blank, you are not authorized to access this group.

Executed by
Select the user who executes the job. The default is User who registered. You can select either of the following.
  • User who registered
    The JP1 user who registered the job executes the job.
  • User who owns
    The JP1 user who owns the job executes the job.
You must perform user mapping on the host where you want to execute the job so that the specified user is converted to a OS user.
If the execution-user fixing function is configured for the upper-level unit, the execution user conforms to the unit-attribute profile regardless of the contents of this field.