DEFINE PROCESS command: TPROCESS partner: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (Automatically generated page update)
 
m (minor cleanup)
Line 6: Line 6:
<dd>Defines a TPROCESS (Terminal Process) partner process (CMS EXEC or CICS program) for reference by User Language statements
<dd>Defines a TPROCESS (Terminal Process) partner process (CMS EXEC or CICS program) for reference by User Language statements
</dl>
</dl>
==Syntax==
==Syntax==
<p class="syntax">DEFINE PROCESS name [LIKE previousname] WITH
<p class="syntax">DEFINE PROCESS <span class="term">name</span> [LIKE <span class="term">previousname</span>] WITH
   SCOPE=SYSTEM
   SCOPE=SYSTEM
   DESTINATION=processgroupname PARTNER=partnername  
   DESTINATION=<span class="term">processgroupname</span> PARTNER=<span class="term">partnername</span>
   DATALEN=nnnnn MODE={EXEC | LINK}
   DATALEN=<span class="term">nnnnn</span> MODE={EXEC | LINK}
</p>
</p>
   
   
Line 17: Line 18:
<tr>
<tr>
<th>name</th>
<th>name</th>
<td> is the local <var class="product">Model&nbsp;204</var> 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. </td>
<td>The local <var class="product">Model&nbsp;204</var> 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. </td>
</tr>
</tr>
   
   
<tr>
<tr>
<th><var>LIKE</var></th>
<th><var>LIKE</var></th>
<td> gives the current link the attributes of the link entity referred to by previousname.</td>
<td>Gives the current link the attributes of the link entity referred to by previousname.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th><var>SCOPE=SYSTEM</var></th>
<th><var>SCOPE=SYSTEM</var></th>
<td> indicates that the definition is available to all users of the <var class="product">Model&nbsp;204</var> system for the entire run.</td>
<td>Indicates that the definition is available to all users of the <var class="product">Model&nbsp;204</var> system for the entire run.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th><var>DESTINATION</var></th>
<th><var>DESTINATION</var></th>
<td> associates the process with the processgroup, processgroupname, defined by the DEFINE PROCESSGROUP command. You can specify only one processgroup.</td>
<td>Associates the process with the processgroup, processgroupname, defined by the DEFINE PROCESSGROUP command. You can specify only one processgroup.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th><var>PARTNER</var></th>
<th><var>PARTNER</var></th>
<td> specifies the name of the partner process (as known in the remote environment) that is the object of User Language TPROCESS statements. Acceptable values for partnername depend on what MODE and PROTOCOL options are defined on the DEFINE PROCESS and DEFINE LINK commands, respectively:  
<td>The name of the partner process (as known in the remote environment) that is the object of SOUL TPROCESS statements. Acceptable values for <var class="term">partnername</var> depend on what MODE and PROTOCOL options are defined on the <var>DEFINE PROCESS</var> and <var>DEFINE LINK</var> commands, respectively:  
<ul>  
<ul>  
<li>
<li>When MODE=LINK and PROTOCOL=MASTER, <var class="term">partnername</var> 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.</li>
<p>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.</p>
</li>
   
   
<li>
<li>When MODE=EXEC and PROTOCOL=MASTER, <var class="term">partnername</var> 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. </li>
<p>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. </p>
</li>
  </ul>
  </ul>
<p>The value specified for PARTNER can be as many as eight characters in length.</p>
<p>
The value specified for PARTNER can be as many as eight characters in length.</p>
</td>
</td>
</tr>
</tr>
Line 53: Line 51:
<tr>
<tr>
<th><var>DATALEN</var></th>
<th><var>DATALEN</var></th>
<td> determines 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.     </td>
<td>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 <var>[[LOUTPB parameter|LOUTPB]]</var>. </td>
</tr>
</tr>
   
   
<tr>
<tr>
<th><var>MODE</var></th>
<th><var>MODE</var></th>
<td> specifies the program control mechanism to be used. Acceptable values are as follows:
<td>The program control mechanism to be used. Acceptable values are as follows:
<ul>  
<ul>  
<li>
<li>LINK &mdash; When PROTOCOL=MASTER.</li>
<p>LINK - When PROTOCOL=MASTER.</p>
</li>
   
   
<li>
<li>EXEC &mdash; When PROTOCOL=MASTER and <var class="product">Model&nbsp;204</var> 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. </li>
<p>EXEC - When PROTOCOL=MASTER and <var class="product">Model&nbsp;204</var> 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. </p>
</ul>
</li>
</ul>
</td>
</td>
</tr>
</tr>  
</table>
</table>
==Example==
==Example==
<p class="code">DEFINE PROCESS CICSTRN1 WITH -
<p class="code">DEFINE PROCESS CICSTRN1 WITH -
   SCOPE=SYSTEM PARTNER=CICSPGM -
   SCOPE=SYSTEM PARTNER=CICSPGM -
   DESTINATION=GRP1 -
   DESTINATION=GRP1 -
   DATALEN=256 MODE=LINK
   DATALEN=256 MODE=LINK
DEFINE PROCESS CMSEXEC WITH -
DEFINE PROCESS CMSEXEC WITH -
   SCOPE=SYSTEM PARTNER=TRDMRK -
   SCOPE=SYSTEM PARTNER=TRDMRK -
   DESTINATION=SERVGP1 -
   DESTINATION=SERVGP1 -
   DATALEN=10002 MODE=EXEC  
   DATALEN=10002 MODE=EXEC  
</p>
</p>
==Usage notes==
==Usage notes==
<p>All three DEFINE commands-DEFINE LINK, DEFINE PROCESSGROUP, and DEFINE PROCESS-are necessary to fully define the partner process. </p>
<p>
<p>For detailed information about TPROCESS communication, refer to "Program Communication Facilities" in the <var>Model&nbsp;204 User Language Manual</var> and the "Program Communication Facilities" discussion in the <var>Model&nbsp;204 System Manager's Guide.</var> </p>
All three DEFINE commands (<var>[[DEFINE LINK command|DEFINE LINK]]</var>, <var>[[DEFINE PROCESSGROUP command|DEFINE PROCESSGROUP]]</var>, and <var>[[DEFINE PROCESS command|DEFINE PROCESS]]</var>) are necessary to fully define the partner process. </p>
<p>
For detailed information about TPROCESS communication, refer to [[Program communications facilities#TPROCESS (terminal process) communication|TPROCESS (terminal process) communication]] and to the "Program Communication Facilities" discussion in the <var class="book">[http://docs.rocketsoftware.com/nxt/gateway.dll/RKBnew556/model%20204/v7.4/m204_v7r4_system_manager.pdf Rocket Model 204 System Manager's Guide]</var>. </p>
 
[[Category: System manager commands]]
[[Category: System manager commands]]
[[Category:Commands]]
[[Category:Commands]]

Revision as of 19:30, 15 April 2014

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.