DEFINE PROCESS command: TPROCESS partner

Summary

Privileges

User 0 or system manager

Function

Defines a TPROCESS (Terminal Process) partner process (CMS EXEC or CICS program) for reference by User Language statements

Syntax

DEFINE PROCESS name [LIKE previousname] WITH SCOPE=SYSTEM DESTINATION=processgroupname PARTNER=partnername DATALEN=nnnnn MODE={EXEC | LINK}

Where:

name	The local Model 204 name for the partner process being defined. User Language statements refer to this remote partner process by the name specified. The length of the name must be 1 to 8 characters.
LIKE	Gives the current link the attributes of the link entity referred to by previousname.
SCOPE=SYSTEM	Indicates that the definition is available to all users of the Model 204 system for the entire run.
DESTINATION	Associates the process with the processgroup, processgroupname, defined by the DEFINE PROCESSGROUP command. You can specify only one processgroup.
PARTNER	The name of the partner process (as known in the remote environment) that is the object of SOUL TPROCESS statements. Acceptable values for partnername depend on what MODE and PROTOCOL options are defined on the DEFINE PROCESS and DEFINE LINK commands, respectively: When MODE=LINK and PROTOCOL=MASTER, partnername must be the name of a CICS program. The CICS program is the partner process and the object of the OPEN PROCESS, SEND, RECEIVE, SIGNAL PROCESS, and CLOSE PROCESS statements. When MODE=EXEC and PROTOCOL=MASTER, partnername must be the name of a z/VM EXEC. The z/VM REXX or EXEC2 EXEC is the partner process and the object of the OPEN PROCESS, SEND, RECEIVE, SIGNAL PROCESS, and CLOSE PROCESS statements. The value specified for PARTNER can be as many as eight characters in length.
DATALEN	The maximum size of the data area that can be specified in the TRANSFER and SEND statements. The maximum value for the length is the CRAM or IUCV buffer size, less 12 bytes. For IODEV 11 and 41, the CRAM buffer size is determined by the value of LOUTPB.
MODE	The program control mechanism to be used. Acceptable values are as follows: LINK — When PROTOCOL=MASTER. EXEC — When PROTOCOL=MASTER and Model 204 is operating in a z/VM environment. The z/VM partner process must be written in System Product Interpreter language (REXX) or EXEC2. This EXEC must reside in a file with a file type of EXEC. No parameters are passed upon entry to this EXEC.

Example

DEFINE PROCESS CICSTRN1 WITH - SCOPE=SYSTEM PARTNER=CICSPGM - DESTINATION=GRP1 - DATALEN=256 MODE=LINK DEFINE PROCESS CMSEXEC WITH - SCOPE=SYSTEM PARTNER=TRDMRK - DESTINATION=SERVGP1 - DATALEN=10002 MODE=EXEC

Usage notes

All three DEFINE commands (DEFINE LINK, DEFINE PROCESSGROUP, and DEFINE PROCESS) are necessary to fully define the partner process.

For detailed information about TPROCESS communication, refer to TPROCESS (terminal process) communication and to the "Program Communication Facilities" discussion in the Rocket Model 204 System Manager's Guide.