PROCESS Statement

A PROCESS statement, or called process card, indicates the process name and is contained in a client job step.

The JCL client of TIBCO MFT Platform Server for z/OS communicates with the server through cross memory services to queue transfer requests. Every transfer request to a platform server is assigned a process name by the user who initiates the request. The process name can be used subsequently by operators who want to monitor the progress of the transfer. The process name is also displayed in a message at the end of every file transfer.

The process name is indicated by a process card. A client job step can contain one or more process cards. Each process is indicated by a PROCESS statement, which is a record in the SYSIN file.

The following example shows a client job step containing two process cards: 
//SYSIN DD  *
PROCESS,PAYROLL,TRANSFER,SEND
: 
: parameters

PROCESS,INVENTORY,TRANSFER,RECEIVE
: 
: parameters
/*

The following table lists the three positional parameters of the PROCESS card:

Parameter Description
Process Name This parameter is the first positional parameter and defines the name of the process.

The process name is the name by which this file transfer is known to the System Server. This parameter can contain 1 - 8 characters.

Activity Type This parameter is the second positional parameter and defines the activity type.

You must set this parameter to TRANSFER when sending, receiving, submitting, or running a script. You can also set this parameter to PING if you want to check whether a TIBCO MFT Platform Server for z/OS is active or not.

Activity

This parameter is the third positional parameter and defines the activity to perform.

The supported activities are as follows:
  • SEND: indicates sending a file from the local system to the remote system.
  • RECEIVE: indicates receiving a file from the remote system to the local system.
  • SUBMIT: indicates locally submitting a file transfer to the internal reader. The job is submitted to the CPU where the platform server started task is running. The submitted job runs under the authorization of the user that is running the Batch interface.
  • SCRIPT: indicates scheduling a script to run in the platform server started task.

    A node can be defined with the CONTENTION_WINNERS parameter to limit the number of concurrent scripts that can be run synchronously. For example, by defining the CONTENTION_WINNERS parameter to 1 and specifying the NODE parameter in the process, you can force scripts to be run single-threaded. The NODE parameter is ignored other than to limit the number of concurrent requests for a script.

Format of PROCESS Statements

Parameters in a PROCESS statement might be continued by using one of the following notations:
  • Put a non-space in column 72. Data is continued in column 1 of the next record.
  • Append a space plus space combination ( + ) to the end of a line. The first non-blank character of the next line is appended to the last non-blank character of the first line.
  • Append a space plus plus combination ( ++) to the end of a line. A space is added between the first non-blank character of the next line and the last non-blank character of the first line.

Parameters can also be enclosed in single or double quotation marks to accommodate imbedded quotations.

Examples of Process Statements

The following examples show how to define the PROCESS cards.

Example 1:

PROCESS MONTHLY,TRANSFER,RECEIVE

In this example, the process is named as MONTHLY, and is defined to receive a file from a remote computer. After this statement is issued, operators can refer to the process in commands by this name.

Example 2:

PROCESS PAYROLL,TRANSFER,SEND

In this example, the process is named as PAYROLL, and is defined to send a file to a remote computer.

Example 3:

PROCESS LOCALJOB,TRANSFER,SUBMIT

In this example, the process is named as LOCALJOB, and is defined to submit a job to the internal reader.

Example 4:

PROCESS RUNSCRPT,TRANSFER,SCRIPT

In this example, the process is named as RUNSCRPT, and is defined to schedule a script to run in the TIBCO MFT Platform Server for z/OS started task.

Example 5:

PROCESS,,PING

This process checks whether a TIBCO MFT Platform Server for z/OS is active. It returns 0 if the server is active, and returns a non-zero number if the server is not active. The PROCESS,,PING request can also be called from within the script program OSIUB000 or OSIUC000, or the API interface (FUSCFAPI).

Note: To perform this ping action, the TIBCO MFT Platform Server for z/OS must be version 6.5.1 or higher.