Job Information
This topic explains how to specify the location where JCL for the job to be started is registered, for a Pre-send Job, Post-send Job, or Post-receive Job.
You can view and modify this information on the following screens:
- Register Job Information/Modify Job Information Record screen
- Collecting and Distributing System Management Information screen
You can also import and export this information on the following screen:
- Collecting and Distributing System Management Information screen
| [Note] | For versions lower than HULFT-HUB Server Ver.3.9, if the client is HULFT Ver.8.4 or higher and the Forced Strong Key Mode is set to 'Enabled' in the System Environment Settings, connection with the client is not supported. Therefore, it is not possible to view, update, or newly register the management information for that client. |
List of Fields
1. Job Information
<Table> List of Fields for Job Information
| No. | Field Name | Default Value | Setting Value | Specification | Remarks | Update | Distribute |
|---|---|---|---|---|---|---|---|
| A1 | Job ID | Alphanumeric characters | Mandatory | Within 50 bytes | ✓ | ✓ | |
| A2 | JCL Library | Alphanumeric characters | Mandatory | Within 44 bytes *1 | ✓ | ✓ | |
| A3 | JOB RC Criterion |
XSP: 10 Other than XSP: 0 |
XSP: From 10 to 99 Other than XSP: From 0 to 4095 |
Optional | ✓ | ✓ | |
| A4 | Startup Job | Alphanumeric characters | Mandatory | Within 8 bytes | ✓ | ✓ | |
| A5 | Comment |
|
Half-width characters *2 | Optional | Within 60 bytes | ✓ | ✓ |
| *1: | The length that you can specify varies depending on host type. For details, refer to Operation Manual for the client. |
| *2: | You cannot specify lowercase alphabetic characters. |
2. Additional information other than Job Information
You can view both the Job Information and the following additional information on each screen where you edit Transfer definitions.
<Table> List of Fields for Additional Information other than Job Information
| No. | Field Name | Default Value | Setting Value | Specification | Remarks | Update | Distribute |
|---|---|---|---|---|---|---|---|
| B1 | Alias | Alphanumeric characters | Optional | Within 256 bytes | ✓ | ✓ | |
| B2 | Business Group ID | *1 | Mandatory | ✓ | ✓ | ||
| B3 | Batch Distribution ID | Alphanumeric characters | *2 | - | ✓ |
| *1: | When you configure settings on the screen, select an option from the list that is shown on the screen. |
| *2: | You are allowed only to view this field on the screen. |
| [Legend] | |
| Default Value | Value that is set for the field when you create a new management information record on a screen |
| Specification | Whether the specification is mandatory or optional when you update the management information record on a screen |
| Update | Register Job Information/Modify Job Information Record screen |
| Distribute | Collecting and Distributing System Management Information screen |
| ✓ | Availability of the field |
Explanation of Each Field
The following describes the fields that are configured in the Job Information.
1. Job Information
This field specifies the ID to identify the job to be started.
This job ID is associated with the job ID in the Send Management Information and with the job ID in the Receive Management Information.
This field specifies the name of JCL library in which the member name for the Startup Job is stored.
Specify this field according to the naming rules for the JCL library for Mainframe.
You can specify only a Partitioned Organization file or a Partitioned Data Set Extended (PDSE) as a JCL library. Specify a JCL library which can be referenced from the STEPCAT catalog that is described in the TSO user's logon procedure or from within the JCL for XRSND, XRRCV, XRACCPT and XRSNDGO.
Do not enclose the JCL library name within single quotation marks (').
| [Note] | There is a slight difference in the types of data sets that you can specify based on the host type used. For details, refer to Operation Manual for the client. |
This field specifies the maximum value of successful return codes of the job to be executed.
When HULFT executes a user-specified job, if the return code of the job is equal to or lower than the value that is specified for the JOB RC Criterion, job execution is considered successful.
If you omit this specification in the CSV file for Collecting and Distributing System Management Information, HULFT-HUB sets the value to '0' if the distribution destination host type is zOS or MSP and to '10' if the distribution destination host type is XSP.
This field specifies the member names of the jobs to be started.
You can specify up to 90 member names. Do not enclose the member names within single quotation marks (').
This field specifies the comment regarding the job.
2. Additional information other than Job Information
This additional information is displayed together with the Job Information on each screen where you edit the Job Information. You can view and modify this information on screens in HULFT-HUB Manager.
| [Note] | You cannot view this additional information on the Management screen on the client (HULFT) side. |
This field specifies the alias for the job.
It is recommended that you assign a unique name in the Job Information so that each job ID that is displayed on screens in HULFT-HUB Manager can be easily identified.
This field specifies the Business Group ID that uses this Job Information.
This field shows the Batch Distribution Information ID with which the Job Information is registered as distribution data.
| [Remarks] | You can view this field on the Collecting and Distributing System Management Information screen (cannot be modified). |
Points to be Noted When Configuring Settings
1. Specification of multiple jobs
If you specify multiple jobs (member names), HULFT executes the jobs in order. HULFT does not execute the jobs in parallel. If the job ends unsuccessfully, HULFT will not execute subsequent jobs.
2. Error in Pre-send Job
If the Pre-send Job fails, an error occurs and the Send File ends.
3. Replacement message
You can replace variables with the messages that you specify when issuing the Send File or with received messages, by specifying the variables from '&MSG0' to '&MSG5' or from '&MSGL0' to '&MSGL1' in the following fields (Message Transmission function):
- JCL Library
- Member Name
| [Note] | |
| - | You cannot specify a name that includes multiple instances of '&MSG' for the JCL Library. |
| Example: &MSG0.&MSG1.JCL | |
| - | You can use the Message Transmission function if the version of the client is Ver.6 or higher on both the sending side and the receiving side. For details, refer to Administration Manual for the client. |
| - | Depending on the language settings on the remote host, replacement with message may not be carried out correctly and transfer may fail. For details, refer to Administration Manual. |
| - | You can use '&' instead of '$' as the first character of environment variables. The hexadecimal code for '$' is 0xE0. |