DEFINE PROCESS command: TPROCESS partner - Revision history

DCameron: /* Syntax */

2019-02-12T16:29:08Z

Syntax

← Older revision		Revision as of 16:29, 12 February 2019
Line 40:		Line 40:
	<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_command:_TPROCESS\|DEFINE LINK]]</var> 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_command:_TPROCESS\|DEFINE LINK]]</var> commands, respectively:
	<ul>		<ul>
	<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>		<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 [[Program_Communication_facilities#OPEN_PROCESS_statement\|OPEN PROCESS]], [[Program_Communication_facilities#SEND_statement\|SEND]], [[Program_Communication_facilities#RECEIVE_statement\|RECEIVE]], [[Program_Communication_facilities#SIGNAL_PROCESS_statement\|SIGNAL PROCESS]], and [[Program_Communication_facilities#CLOSE_PROCESS_statement\|CLOSE PROCESS]] statements.</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>		<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>

DCameron: /* Syntax */

2019-02-12T16:24:45Z

Syntax

← Older revision		Revision as of 16:24, 12 February 2019
Line 38:		Line 38:
	<tr>		<tr>
	<th><var>PARTNER</var></th>		<th><var>PARTNER</var></th>
	<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:		<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_command:_TPROCESS\|DEFINE LINK]]</var> commands, respectively:
	<ul>		<ul>
	<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>		<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>

DCameron: /* Syntax */

2019-02-12T16:22:01Z

Syntax

← Older revision		Revision as of 16:22, 12 February 2019
Line 33:		Line 33:
	<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 <var>[[DEFINE_PROCESSGROUP_command:_TPROCESS\|DEFINE PROCESSGROUP]]</var> command. You can specify only one processgroup.</td>
	</tr>		</tr>

DCameron: /* Summary */

2019-02-12T16:20:00Z

Summary

← Older revision		Revision as of 16:20, 12 February 2019
Line 4:		Line 4:
	<dd>User 0 or system manager		<dd>User 0 or system manager
	<dt>Function		<dt>Function
	<dd>Defines a TPROCESS (Terminal Process) partner process (CMS EXEC or CICS program) for reference by User Language statements		<dd>Defines a [[Program_Communication_facilities#TPROCESS_.28terminal_process.29_communication\|TPROCESS (Terminal Process)]] partner process (CMS EXEC or CICS program) for reference by User Language statements
	</dl>		</dl>

JAL: /* Usage notes */

2014-10-30T17:57:23Z

Usage notes

← Older revision		Revision as of 17:57, 30 October 2014
Line 78:		Line 78:

	==Usage notes==		==Usage notes==
	<p>		<ul>
	All three DEFINE commands (<var>[[DEFINE LINK command: TPROCESS\|DEFINE LINK]]</var>, <var>[[DEFINE PROCESSGROUP command: TPROCESS\|DEFINE PROCESSGROUP]]</var>, and <var>DEFINE PROCESS</var>) are necessary to fully define the partner process. </p>		<li>All three DEFINE commands (<var>[[DEFINE LINK command: TPROCESS\|DEFINE LINK]]</var>, <var>[[DEFINE PROCESSGROUP command: TPROCESS\|DEFINE PROCESSGROUP]]</var>, and <var>DEFINE PROCESS</var>) are necessary to fully define the partner process. </li>
	<p>
	For detailed information about TPROCESS communication, refer to [[Program Communication facilities#TPROCESS (terminal process) communication\|TPROCESS (terminal process) communication]] and to [[Using Program Communication facilities]]. </p>		<li>For detailed information about TPROCESS communication, refer to [[Program Communication facilities#TPROCESS (terminal process) communication\|TPROCESS (terminal process) communication]] and to [[Using Program Communication facilities]]. </li>
			</ul>

	[[Category: System manager commands]]		[[Category: System manager commands]]
	[[Category:Commands]]		[[Category:Commands]]

JAL: /* Usage notes */

2014-10-30T17:55:46Z

Usage notes

← Older revision		Revision as of 17:55, 30 October 2014
Line 79:		Line 79:
	==Usage notes==		==Usage notes==
	<p>		<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>		All three DEFINE commands (<var>[[DEFINE LINK command: TPROCESS\|DEFINE LINK]]</var>, <var>[[DEFINE PROCESSGROUP command: TPROCESS\|DEFINE PROCESSGROUP]]</var>, and <var>DEFINE PROCESS</var>) are necessary to fully define the partner process. </p>
	<p>		<p>
	For detailed information about TPROCESS communication, refer to [[Program Communication facilities#TPROCESS (terminal process) communication\|TPROCESS (terminal process) communication]] and to [[Using Program Communication facilities]]. </p>		For detailed information about TPROCESS communication, refer to [[Program Communication facilities#TPROCESS (terminal process) communication\|TPROCESS (terminal process) communication]] and to [[Using Program Communication facilities]]. </p>

JAL at 20:54, 20 October 2014

2014-10-20T20:54:21Z

← Older revision		Revision as of 20:54, 20 October 2014
Line 81:		Line 81:
	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>		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>		<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>		For detailed information about TPROCESS communication, refer to [[Program Communication facilities#TPROCESS (terminal process) communication\|TPROCESS (terminal process) communication]] and to [[Using Program Communication facilities]]. </p>

	[[Category: System manager commands]]		[[Category: System manager commands]]
	[[Category:Commands]]		[[Category:Commands]]

JAL: minor cleanup

2014-04-15T19:30:48Z

minor cleanup

← Older revision		Revision as of 19:30, 15 April 2014
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 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 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 204</var> system for the entire run.</td>		<td>Indicates that the definition is available to all users of the <var class="product">Model 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 — When PROTOCOL=MASTER.</li>
	<p>LINK - When PROTOCOL=MASTER.~~</p>~~
	</li>

	<li>		<li>EXEC — When PROTOCOL=MASTER and <var class="product">Model 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 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 204 User Language Manual</var>~~ and the "Program Communication Facilities" discussion in the <var>Model~~ ~~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]]

Alex: Automatically generated page update

2013-02-28T01:04:47Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>User 0 or system manager
<dt>Function
<dd>Defines a TPROCESS (Terminal Process) partner process (CMS EXEC or CICS program) for reference by User Language statements
</dl>
==Syntax==
DEFINE PROCESS name [LIKE previousname] WITH
SCOPE=SYSTEM
DESTINATION=processgroupname PARTNER=partnername
DATALEN=nnnnn MODE={EXEC | LINK}


Where:
<table>
<tr>
<th>name</th>
<td> is the local <var class="product">Model 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>
<th><var>LIKE</var></th>
<td> gives the current link the attributes of the link entity referred to by previousname.</td>
</tr>

<tr>
<th><var>SCOPE=SYSTEM</var></th>
<td> indicates that the definition is available to all users of the <var class="product">Model 204</var> system for the entire run.</td>
</tr>

<tr>
<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>
</tr>

<tr>
<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:
<ul>
<li>
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.
</li>

<li>
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. 
</li>
</ul>
The value specified for PARTNER can be as many as eight characters in length.
</td>
</tr>

<tr>
<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>
</tr>

<tr>
<th><var>MODE</var></th>
<td> specifies the program control mechanism to be used. Acceptable values are as follows:
<ul>
<li>
LINK - When PROTOCOL=MASTER.
</li>

<li>
EXEC - When PROTOCOL=MASTER and <var class="product">Model 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>
</ul>
</td>
</tr>

</table>
==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 "Program Communication Facilities" in the <var>Model 204 User Language Manual</var> and the "Program Communication Facilities" discussion in the <var>Model 204 System Manager's Guide.</var> 
[[Category: System manager commands]]
[[Category:Commands]]