Open topic with navigation

TIBCO® Managed File Transfer Platform Server for z/OS 8.1.0

# SUBJCL Configuration Parameters

The SUBJCL DD statement of the Platform Server started task contains the configuration parameters that are used to control the SUBJCL processing.

These parameters are separated by commas. The last parameter must be followed by a space to indicate the end of the entry. If you want to continue a configuration entry, simply place a comma after the last entry on a line, and start the next parameter on the next configuration card. Comments are defined by placing an asterisk (*) in column 1. If a parameter is not defined, then it is assumed to be a match.

See the following table for the configuration parameters you can define.

Parameter | Description
--- | ---
`SUBMIT` | Defines the start of a SUBJCL parameter entry. This parameter is required. This must be the first parameter entry.
`JCL` | Defines the JCL that must be submitted. This parameter can be defined in one of two ways: Member name: The Platform Server uses the DSN defined by the GLOBAL `JOB_SUBMIT_DSN` parameter. Fully qualified dataset name: This can be a sequential file, or it can point to a member within a PDS. This parameter is required.
`SUBUSER` | Defines the user ID under whose authorization the job is submitted. This parameter can be defined in three ways: STC: Uses the user ID associated with the started task. TRANSFER: Uses the user ID and password associated with the file transfer request. Uses the user ID defined by the `SUBUSER` parameter. The default value is `TRANSFER`.
`TYPE` | Defines the type of file transfer request. Valid values are `SEND`, `RECEIVE`, or `BOTH`. `BOTH` indicates that both send and receive requests are considered as a match.
`SOURCE` | Defines the source of file transfer request. Valid values are `INITIATOR`, `RESPONDER`, or `BOTH`. `BOTH` indicates that both initiator and responder requests are considered as a match.
`STATUS` | Defines whether a transfer request is successful or unsuccessful. Valid values are `SUCCESS`, `FAILURE`, or `BOTH`. `BOTH` indicates that both successful and unsuccessful requests are considered as a match.
`DSN` | Defines the fully qualified dataset name. This field is compared against the local dataset name in the file transfer request. If a member is transferred, the member name must be included in this parameter.
`PROCESS` | Defines the process name associated with the transfer request.
`IPADDR` | Defines the IP address of the node that is communicating with the Platform Server for z/OS. If a request is not from an IP address, then this parameter does not match.
`NODE` | Defines the node name of a transfer request. For initiator requests, this parameter is used when the `NODE` parameter is used on a request. For responder requests, the Platform Server scans the NODE table for matches on the LUNAME or IP address. These entries are then matched against the value specified in the `NODE` parameter.

See the following examples of SUBJCL configuration entries.

Example 1:

    SUBMIT,JCL=ACCTJOB1,
           SUBUSER=TRANSFER,
           STATUS=SUCCESS,
           SOURCE=RESPONDER,
           TYPE=RECEIVE,
           DSN=PROD.ACCT.PAYROLL,
           NODE=NYACCT

A match on this entry occurs when all the following criteria are met.

- A responder request is detected.
- The node associated with the request is NYACCT.
- The request is a receive transfer.
- The file is successfully received.
- The dataset received is `PROD.ACCT.PAYROLL`.

When all of these fields match, the Platform Server logs on as the user associated with the file transfer, extracts the GLOBAL `JOB_SUBMIT_DSN` dataset name, allocates that dataset, and then submits member `ACCTJOB1` to the internal reader.

Example 2:

    SUBMIT,JCL=TECHSUP.JCL.CNTL(FAILED),
           SUBUSER=TECHSUP,STATUS=FAILED,
           SOURCE=BOTH,TYPE=BOTH

A match on this entry occurs when all the following criteria are met.

- An initiator or responder request is detected.
- The request is a send or receive transfer.
- The request is unsuccessful.

When all of these fields match, the Platform Server logs on as user TECHSUP and submits the data in `TECHSUP.JCL.CNTL(FAILED)`to the internal reader.

Copyright © 2003-2021. TIBCO Software Inc. All Rights Reserved.