DEFINE LINK command: TPROCESS - Revision history

DCameron: /* Syntax */

2019-02-12T15:30:27Z

Syntax

← Older revision		Revision as of 15:30, 12 February 2019
Line 34:		Line 34:

	<li>		<li>
	<p><var>PROTOCOL</var> identifies the protocol to be used with the partner process. <var>MASTER</var> specifies the TPROCESS facility. If MASTER is specified, the only User Language statements allowed are [[Program_Communication_facilities#OPEN_PROCESS_statement\|OPEN PROCESS]], SEND, RECEIVE, SIGNAL PROCESS, and CLOSE PROCESS.</p>		<p><var>PROTOCOL</var> identifies the protocol to be used with the partner process. <var>MASTER</var> specifies the TPROCESS facility. If MASTER is specified, the only User Language statements allowed are [[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]].</p>
	</li>		</li>

DCameron: /* Syntax */

2019-02-12T15:28:03Z

Syntax

← Older revision		Revision as of 15:28, 12 February 2019
Line 34:		Line 34:

	<li>		<li>
	<p><var>PROTOCOL</var> identifies the protocol to be used with the partner process. <var>MASTER</var> specifies the TPROCESS facility. If MASTER is specified, the only User Language statements allowed are OPEN PROCESS, SEND, RECEIVE, SIGNAL PROCESS, and CLOSE PROCESS.</p>		<p><var>PROTOCOL</var> identifies the protocol to be used with the partner process. <var>MASTER</var> specifies the TPROCESS facility. If MASTER is specified, the only User Language statements allowed are [[Program_Communication_facilities#OPEN_PROCESS_statement\|OPEN PROCESS]], SEND, RECEIVE, SIGNAL PROCESS, and CLOSE PROCESS.</p>
	</li>		</li>

JAL: add `'s`

2018-03-19T20:22:51Z

add <var>'s

← Older revision		Revision as of 20:22, 19 March 2018
Line 6:		Line 6:
	<dd>Defines the transport type and the protocol to be used in communicating with the partner process		<dd>Defines the transport type and the protocol to be used in communicating with the partner process
	</dl>		</dl>

	==Syntax==		==Syntax==
	<p class="syntax">DEFINE LINK name [LIKE previousname] WITH		<p class="syntax">DEFINE LINK name [LIKE previousname] WITH
Line 37:		Line 38:

	<li>		<li>
	<p>MASTER specifies that the User Language request communicates with the remote partner process using a "Parent-Child" protocol, where the request is the parent (MASTER) and the partner process is the child. This protocol defines a relationship in which the actions of the parent determine what actions can be taken by the child. Specifically, when the parent issues a SEND, the child must issue a RECEIVE, and when the parent issues a RECEIVE, the child must issue a SEND.</p>		<p><var>MASTER</var> specifies that the User Language request communicates with the remote partner process using a "Parent-Child" protocol, where the request is the parent (MASTER) and the partner process is the child. This protocol defines a relationship in which the actions of the parent determine what actions can be taken by the child. Specifically, when the parent issues a SEND, the child must issue a RECEIVE, and when the parent issues a RECEIVE, the child must issue a SEND.</p>
	</li>		</li>
	</ul>		</ul>

	==Example==		==Example==
	In the following example, the TPROCESS link is identified by the transport type TERMINAL and the protocol MASTER:		In the following example, the TPROCESS link is identified by the transport type TERMINAL and the protocol MASTER:
Line 47:		Line 49:
	PROTOCOL=MASTER		PROTOCOL=MASTER
	</p>		</p>

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

Alex: Automatically generated page update

2013-02-28T01:04:43Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>System manager, User 0
<dt>Function
<dd>Defines the transport type and the protocol to be used in communicating with the partner process
</dl>
==Syntax==
DEFINE LINK name [LIKE previousname] WITH
SCOPE=SYSTEM
TRANSPORT=TERMINAL
PROTOCOL=MASTER


Where:
<ul>
<li>
name identifies the link. 
</li>

<li>
<var>LIKE</var> gives the current link the attributes of the link entity referred to by previousname.
</li>

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

<li>
<var>TRANSPORT</var> is the physical communication transmission method.
For TPROCESS links, TRANSPORT must be set to TERMINAL. The TERMINAL parameter means that under z/VM or CICS the terminal is "borrowed" to perform communications. 
</li>

<li>
<var>PROTOCOL</var> identifies the protocol to be used with the partner process. <var>MASTER</var> specifies the TPROCESS facility. If MASTER is specified, the only User Language statements allowed are OPEN PROCESS, SEND, RECEIVE, SIGNAL PROCESS, and CLOSE PROCESS.
</li>

<li>
MASTER specifies that the User Language request communicates with the remote partner process using a "Parent-Child" protocol, where the request is the parent (MASTER) and the partner process is the child. This protocol defines a relationship in which the actions of the parent determine what actions can be taken by the child. Specifically, when the parent issues a SEND, the child must issue a RECEIVE, and when the parent issues a RECEIVE, the child must issue a SEND.
</li>
</ul>
==Example==
In the following example, the TPROCESS link is identified by the transport type TERMINAL and the protocol MASTER:
DEFINE LINK M204PROD WITH -
SCOPE=SYSTEM -
TRANSPORT=TERMINAL -
PROTOCOL=MASTER

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

DEFINE LINK command: TPROCESS - Revision history

DCameron: /* Syntax */

DCameron: /* Syntax */

JAL: add 's

Alex: Automatically generated page update

JAL: add `'s`