DEFINE PROCESS command: Overview of intersystem network process - Revision history

JAL at 20:55, 20 October 2014

2014-10-20T20:55:58Z

← Older revision		Revision as of 20:55, 20 October 2014
Line 14:		Line 14:
	A server process definition is associated with the inbound conversation which accepts a remote request to start a subsystem. It is identified by the use of the <var>SUBSYSTEM</var> parameter. The use of a symbolic name for the server process allows the name of the subsystem to be modified without requiring remote users to modify the name used to select the transaction.</p>		A server process definition is associated with the inbound conversation which accepts a remote request to start a subsystem. It is identified by the use of the <var>SUBSYSTEM</var> parameter. The use of a symbolic name for the server process allows the name of the subsystem to be modified without requiring remote users to modify the name used to select the transaction.</p>
	<p>		<p>
	The following pages contain descriptions and examples of DEFINE PROCESS requirements for the Model 204 [[Program ~~communications facilities\|program communications~~ facilities]]:</p>		The following pages contain descriptions and examples of <var>DEFINE PROCESS</var> requirements for the Model 204 [[Program Communication facilities]]:</p>

	:[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM]]		:[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM]]

JAL at 20:50, 10 October 2014

2014-10-10T20:50:32Z

← Older revision		Revision as of 20:50, 10 October 2014
Line 1:		Line 1:
	==Description==		==Description==
	<p>A process is a <i>conversation</i> program that participates in a conversation with another program. The DEFINE PROCESS command associates the process name with a set of processgroups, each of which associates it with a link. </p>		<p>
	<p>By assigning processes to specific processgroups, the system manager can control their use of network resources and also can select sessions with special characteristics to support conversations with special requirements. </p>		A process is a <i>conversation</i> program that participates in a conversation with another program. The <var>DEFINE PROCESS</var> command associates the process name with a set of processgroups, each of which associates it with a link. </p>
	<p>The two types of processes are client and server.</p>		<p>
			By assigning processes to specific processgroups, the system manager can control their use of network resources and also can select sessions with special characteristics to support conversations with special requirements. </p>
			<p>
			The two types of processes are client and server.</p>

	==The client process==		==The client process==
	A client process definition is associated with the outbound conversation partner which initiates the conversation. A client process is identified by the presence of the PARTNER parameter. The partner name is the same name used on the server DEFINE PROCESS command at the remote node. The DEFINE PROCESS command associates a symbolic name with the actual transaction name of the conversation partner. This allows the actual name of the service transaction to be modified without requiring changes to any ~~User Language~~ request.		A client process definition is associated with the outbound conversation partner which initiates the conversation. A client process is identified by the presence of the <var>PARTNER</var> parameter. The partner name is the same name used on the server <var>DEFINE PROCESS</var> command at the remote node. The <var>DEFINE PROCESS</var> command associates a symbolic name with the actual transaction name of the conversation partner. This allows the actual name of the service transaction to be modified without requiring changes to any SOUL request.

	==The server process==		==The server process==
	<p>A server process definition is associated with the inbound conversation which accepts a remote request to start a subsystem. It is identified by the use of the SUBSYSTEM parameter. The use of a symbolic name for the server process allows the name of the subsystem to be modified without requiring remote users to modify the name used to select the transaction.</p>		<p>
	<p>The following pages contain descriptions and examples of DEFINE PROCESS requirements for the ~~above~~ facilities.</p>		A server process definition is associated with the inbound conversation which accepts a remote request to start a subsystem. It is identified by the use of the <var>SUBSYSTEM</var> parameter. The use of a symbolic name for the server process allows the name of the subsystem to be modified without requiring remote users to modify the name used to select the transaction.</p>
			<p>
			The following pages contain descriptions and examples of DEFINE PROCESS requirements for the Model 204 [[Program communications facilities\|program communications facilities]]:</p>

			:[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM]]
			:[[DEFINE PROCESS command: SQL]]
			:[[DEFINE PROCESS command: TPROCESS partner]]
			:[[DEFINE PROCESS command: Transfer Control partner]]
			:[[DEFINE PROCESS command: User Language to DB2]]

	[[Category:Commands]]		[[Category:Commands]]

Alex: Automatically generated page update

2013-02-28T01:04:44Z

Automatically generated page update

New page

==Description==
A process is a conversation program that participates in a conversation with another program. The DEFINE PROCESS command associates the process name with a set of processgroups, each of which associates it with a link. 
By assigning processes to specific processgroups, the system manager can control their use of network resources and also can select sessions with special characteristics to support conversations with special requirements. 
The two types of processes are client and server.
==The client process==
A client process definition is associated with the outbound conversation partner which initiates the conversation. A client process is identified by the presence of the PARTNER parameter. The partner name is the same name used on the server DEFINE PROCESS command at the remote node. The DEFINE PROCESS command associates a symbolic name with the actual transaction name of the conversation partner. This allows the actual name of the service transaction to be modified without requiring changes to any User Language request.
==The server process==
A server process definition is associated with the inbound conversation which accepts a remote request to start a subsystem. It is identified by the use of the SUBSYSTEM parameter. The use of a symbolic name for the server process allows the name of the subsystem to be modified without requiring remote users to modify the name used to select the transaction.
The following pages contain descriptions and examples of DEFINE PROCESS requirements for the above facilities.
[[Category:Commands]]