DEFINE PROCESS command: Horizon for TCP/IP and VTAM - Revision history

DCameron: /* server-options */

2019-02-12T15:59:01Z

server-options

← Older revision		Revision as of 15:59, 12 February 2019
Line 40:		Line 40:

	<li>		<li>
	<p>Must be one of the following for Parallel Query Option/204 processes:</p>		<p>Must be one of the following for [[PQO:_Overview_of_Parallel_Query_Option/204\|Parallel Query Option/204]] processes:</p>
	<p> If a server, name must be CCAD2S </p>		<p> If a server, name must be CCAD2S </p>
	<p>If a client, name must be CCAD2C</p>		<p>If a client, name must be CCAD2C</p>

DCameron: /* server-options */

2019-02-12T15:57:23Z

server-options

← Older revision		Revision as of 15:57, 12 February 2019
Line 32:		Line 32:
	<ul>		<ul>
	<li>		<li>
	<p>Refers in client OPEN PROCESS statements to the client (outbound) process, which initiates the conversation</p>		<p>Refers in client [[Program_Communication_facilities#OPEN_PROCESS_statement\|OPEN PROCESS]] statements to the client (outbound) process, which initiates the conversation</p>
	</li>		</li>

DCameron: /* Summary */

2019-02-12T15:55:56Z

Summary

← Older revision		Revision as of 15:55, 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 Horizon process for reference by User Language statements		<dd>Defines a [[Model_204_intersystem_processing#Horizon\|Horizon]] process for reference by User Language statements
	</dl>		</dl>

	==Syntax==		==Syntax==
	<p class="syntax">DEFINE PROCESS name [LIKE previousname] WITH		<p class="syntax">DEFINE PROCESS name [LIKE previousname] WITH

ELowell: /* server-options */

2016-03-17T15:15:04Z

server-options

← Older revision		Revision as of 15:15, 17 March 2016
Line 42:		Line 42:
	<p> If a server, name must be CCAD2S </p>		<p> If a server, name must be CCAD2S </p>
	<p>If a client, name must be CCAD2C</p>		<p>If a client, name must be CCAD2C</p>
	<p>The length of name must be eight characters or ~~less~~. The keyword ALL and any names prefixed with CCA are reserved and cannot be used.</p>		<p>The length of name must be eight characters or fewer. The keyword ALL and any names prefixed with CCA are reserved and cannot be used.</p>
	</li>		</li>
	</ul>		</ul>

ELowell: /* Usage notes */

2016-02-04T20:52:46Z

Usage notes

← Older revision		Revision as of 20:52, 4 February 2016
Line 255:		Line 255:
	</li>		</li>
	</ul>		</ul>
	<p>For more information about Horizon network and entities, see ~~the <var>Model 204~~ Horizon~~: Intersystem Processing Guide</var>~~. For more information about PQO entities, see ~~the <var>Parallel Query Option/204 User's Guide</var>~~. </p>		<p>For more information about Horizon network and entities, see [[Horizon network management]]. For more information about PQO entities, see [[PQO: Defining a PQO network]]. </p>
	[[Category: System manager commands]]		[[Category: System manager commands]]
	[[Category:Commands]]		[[Category:Commands]]

ELowell: /* Server process options */

2016-02-04T20:50:54Z

Server process options

← Older revision		Revision as of 20:50, 4 February 2016
Line 221:		Line 221:
	<p>When the server subsystem is invoked, the SUBSYSPARM value string is stored in the command-line global variable specified in the subsystem definition. If the subsystem definition does not specify a command line global variable, SUBSYSPARM is ignored.</p>		<p>When the server subsystem is invoked, the SUBSYSPARM value string is stored in the command-line global variable specified in the subsystem definition. If the subsystem definition does not specify a command line global variable, SUBSYSPARM is ignored.</p>
	<p>When the SUBSYSPARM value string is stored in the command line global variable, Horizon automatically appends two characters: a blank and a semicolon (;), in that order.</p>		<p>When the SUBSYSPARM value string is stored in the command line global variable, Horizon automatically appends two characters: a blank and a semicolon (;), in that order.</p>
	<p>By varying the SUBSYSPARM values, Horizon developers can implement different server processes as single application subsystems. User Language programs can thereby be tested without having to define a new subsystem. For more information about testing application programs using this parameter with the Rocket-provided subsystem, RPI, see the ~~<i>Horizon: Intersystem Processing Guide</i>~~.</p>		<p>By varying the SUBSYSPARM values, Horizon developers can implement different server processes as single application subsystems. User Language programs can thereby be tested without having to define a new subsystem. For more information about testing application programs using this parameter with the Rocket-provided subsystem, RPI, see [[Horizon network management#Application testing with the RPI subsystem\|Application testing with the RPI subsystem]].</p>
	<p>Supply the subsystem parameter line within quotation marks, if it contains any blanks, commas, or equal signs. The quotation marks cause <var class="product">Model 204</var> to treat the entire quoted string as a single token. If the quotation marks are not supplied, then blanks, commas, and equal signs are taken as token delimiters, causing <var class="product">Model 204</var> to treat the subsystem parameter line as having multiple tokens, and thus reject the DEFINE PROCESS command.</p>		<p>Supply the subsystem parameter line within quotation marks, if it contains any blanks, commas, or equal signs. The quotation marks cause <var class="product">Model 204</var> to treat the entire quoted string as a single token. If the quotation marks are not supplied, then blanks, commas, and equal signs are taken as token delimiters, causing <var class="product">Model 204</var> to treat the subsystem parameter line as having multiple tokens, and thus reject the DEFINE PROCESS command.</p>
	</td>		</td>

ELowell: /* server-options */

2013-10-04T16:36:03Z

server-options

← Older revision		Revision as of 16:36, 4 October 2013
Line 57:		Line 57:
	<li>		<li>
	<p><var>DATALEN</var> specifies the size of a Horizon conversation buffer. Data is shipped over the session from the sending side's conversation buffer to the receiving side's conversation buffer. Set DATALEN greater than or equal to the largest IMAGE size, %variable length, or SQL data packet shipped over the session. An insufficiently large conversation buffer causes inefficient sending of data or some truncation of data received.</p>		<p><var>DATALEN</var> specifies the size of a Horizon conversation buffer. Data is shipped over the session from the sending side's conversation buffer to the receiving side's conversation buffer. Set DATALEN greater than or equal to the largest IMAGE size, %variable length, or SQL data packet shipped over the session. An insufficiently large conversation buffer causes inefficient sending of data or some truncation of data received.</p>
	<p>Each SQL logical record (SLR) is packaged as one or more chunks ~~call~~ general data streams (GDSs). ~~GES~~ size depends on the data buffer length. Each GDS is packaged and shipped across the network as on or more network units:</p>		<p>Each SQL logical record (SLR) is packaged as one or more chunks called general data streams (GDSs). GDS size depends on the data buffer length. Each GDS is packaged and shipped across the network as on or more network units:</p>
	<ul>		<ul>
	<li>		<li>
Line 227:		Line 227:

	</table>		</table>

	==Example==		==Example==
	Sample (non-PQO) client process:		Sample (non-PQO) client process:

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 Horizon process for reference by User Language statements
</dl>
==Syntax==
DEFINE PROCESS name [LIKE previousname] WITH
SCOPE=SYSTEM
DATALEN=nnnnn [TIMEOUT=nnnnn] [CONFIRM | NOCONFIRM]
{client-options | server-options}

==client-options==
DESTINATION={processgroup | (pg1,sym1,pg2,sym2,...)}
PARTNER=partnername
[UIDSOURCE={NONE | CURRENT | OPEN}]
[{ACCTSOURCE= | PROFSOURCE=}{NONE | CURRENT
| OPEN}]
[RESTRICT={NONE | APSY}]

==server-options==
FROM=(pg1 [,pg2]...) SUBSYSTEM=subsystemname
[SUBSYSPARM='subsystem-parameter-line']


Where:
<ul>
<li>
name:
<ul>
<li>
Refers in client OPEN PROCESS statements to the client (outbound) process, which initiates the conversation
</li>

<li>
Associates a server (inbound) process, which accepts a remote request, with a subsystem 
</li>

<li>
Must be one of the following for Parallel Query Option/204 processes:
 If a server, name must be CCAD2S 
If a client, name must be CCAD2C
The length of name must be eight characters or less. The keyword ALL and any names prefixed with CCA are reserved and cannot be used.
</li>
</ul>
</li>

<li>
<var>LIKE</var> is optional and gives the process being defined the attributes of the process referred to by previousname. If you specify LIKE previousname, you must specify WITH SCOPE=SYSTEM. 
</li>

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

<li>
<var>DATALEN</var> specifies the size of a Horizon conversation buffer. Data is shipped over the session from the sending side's conversation buffer to the receiving side's conversation buffer. Set DATALEN greater than or equal to the largest IMAGE size, %variable length, or SQL data packet shipped over the session. An insufficiently large conversation buffer causes inefficient sending of data or some truncation of data received.
Each SQL logical record (SLR) is packaged as one or more chunks call general data streams (GDSs). GES size depends on the data buffer length. Each GDS is packaged and shipped across the network as on or more network units:
<ul>
<li>
SNA Communications Server request units (RUs), the SNA Communications Server mode entry parameter RUSIZES sets the RU size.
</li>

<li>
TCP/IP transmission units (TUs), the TCP/IP size is fixed at 4096 bytes.
</li>
</ul>
To set DATALEN, you should consider both GDSs received and GDSs sent.
<ul>
<li>
To accommodate GDSs received, DATALEN must be greater than or equal to the client data length setting (the PC client configuration parameter Datalen or Data Buffer Length, or the TCP/IP environment variable datalen).
</li>

<li>
To optimize performance for GDSs sent, DATLEN should be equal to the since-last statistic setting plus five, to a maximum of 4101.
DATALEN is not used for PQO processes.
The DATALEN minimum is 537 and the maximum is 32763. 
DATALEN and the DEFINE LINK command parameter INBUFSIZE are independent. They refer to different buffers. 
</li>
</ul>
</li>

<li>
<var>TIMEOUT</var> provides a terminal timeout facility. It specifies the number of seconds a thread waits for the completion of a User Language request that involves a physical network transmission. 
</li>

<li>
CONFIRM, FLUSH, and RECEIVE are examples of User Language statements that cause a physical network transmission. For example RECEIVE may wait for a reply no longer than the value of TIMEOUT for a physical network transmission.
</li>

<li>
If the TIMEOUT limit is exceeded, the session is abnormally terminated. Specify the time in seconds. Zero is the default; it indicates no time limit. 
</li>

<li>
<var>CONFIRM</var> or <var>NOCONFIRM</var> specifies whether or not the applications can perform confirmation processing through the use of the User Language CONFIRM statement. CONFIRM or NOCONFIRM determines at OPEN PROCESS time the synchronization level (SYNCLEVEL) that the client and server processes can use on a conversation. The default is NOCONFIRM.
A client process and its corresponding server process must both specify the same CONFIRM value for any OPEN PROCESS request to succeed.
CONFIRM and NOCONFIRM are not used for PQO processes.
</li>
</ul>
Client process options 
<var>DESTINATION</var> associates the process with a processgroup. In turn, the processgroup links the process with a remote site and internal resource limit group. The processgroup can be either a single client processgroup or a list of paired items with the following format: 
pg1,sym1,pg2,sym2 ...


Where:
<table>
<tr>
<th>pg1, pg2, ...</th>
<td> are processgroup names and must be the same as the processgroup names specified on DEFINE PROCESSGROUP commands. </td>
</tr>

<tr>
<th>sym1, sym2, ...</th>
<td> are symbolic names that can be used with the AT parameter of the OPEN PROCESS User Language statement to refer to the processgroup(s) associated with the symbolic name(s).
<ul>
<li>
If DESTINATION=processgroup is specified, then the process is associated with that processgroup.
</li>

<li>
If DESTINATION=<var>(pg1,sym1, pg2,sym2, ...)</var> is specified, the process can be associated with any of processgroups pg1, pg2, and so on when the OPEN PROCESS statement is issued.
</li>

<li>
The AT parameter of the OPEN PROCESS must specify one of the symbolic destinations, whereupon the corresponding processgroup for that symbolic destination becomes the actual destination. If the AT parameter is not used in the OPEN PROCESS statement, the first processgroup (pg1) is used. 
For PQO processes, only a symbolic destination name specified here can be used with AT to specify a remote file location. 
</li>
</ul>
If the value of DESTINATION is specified in processgroup-symbolic name format, each processgroup included must be paired with a symbolic name (and vice versa) or the DEFINE PROCESS command is rejected.
A benefit of using symbolic names within a User Language request is that a system manager can change actual processgroup names without affecting the application program. For example, the DEFINE PROCESSGROUP command has:
DESTINATION=(PGRP1,BOSTON)

The OPEN PROCESS statement is: 
OPEN PROCESS name AT BOSTON

Then the system manager can change the processgroup name, PGRP1, without having to modify the User Language application.
</td>
</tr>

<tr>
<th><var>PARTNER</var></th>
<td> specifies the name of the conversation partner program. It is the same name used on the DEFINE PROCESS command for the server process at the remote node.
PARTNER is not used for PQO processes. 
</td>
</tr>

<tr>
<th><var>UIDSOURCE</var></th>
<td> specifies the source of the user ID to be used for login at the remote node:
<table>
<tr>
<th><var>NONE</var></th>
<td> causes <var class="product">Model 204</var> not to transmit any user ID, password, or account number to the remote node. This must be used when the remote partner does not accept any security information from <var class="product">Model 204</var>. NONE is the default value.</td>
</tr>

<tr>
<th><var>CURRENT</var></th>
<td> means that at OPEN PROCESS time, the current user ID is transmitted for LOGIN at the remote node. If the user is not currently logged in, no user ID is transmitted.</td>
</tr>

<tr>
<th><var>OPEN</var></th>
<td> permits the User Language request to specify the USERID and PASSWORD operands on OPEN PROCESS and override the current user ID value. The system manager might wish to disallow this to maintain tighter control over which user ID a local user can be known as at a remote node.</td>
</tr>

</table>
UIDSOURCE is not used for PQO processes. 
</td>
</tr>

<tr>
<th><var>ACCTSOURCE</var></th>
<td> and <var>PROFSOURCE</var> specify options for ACCOUNT or PROFILE on the OPEN PROCESS statement similar to those for UIDSOURCE.
ACCTSOURCE and PROFSOURCE are not used for PQO processes. 
</td>
</tr>

<tr>
<th><var>RESTRICT</var></th>
<td> specifies whether the User Language OPEN PROCESS statement can be issued outside of an application subsystem. If set to APSY, OPEN PROCESS fails if issued outside of an application subsystem. If set to NONE (the default), OPEN PROCESS is allowed outside of an application subsystem management facility subsystem.
RESTRICT is not used for PQO processes.
</td>
</tr>

</table>
====Server process options====
The following options are valid only for server processes.
<table>
<tr>
<th><var>FROM</var></th>
<td> associates the process with one or a set of processgroups.
The values of pg1, pg2, and so on must be the same as the processgroup names specified on DEFINE PROCESSGROUP commands at the server. A request for the server process received from a client node is accepted only if all the following requirements are met on a definition of one of the server processgroups pg1, pg2 and so on: 
<ul>
<li>
LINK value matches the link to which the request is directed.
</li>

<li>
REMOTEID value matches the client node name. 
</li>

<li>
LOGIN value matches the client processgroup at the remote node. 
</li>
</ul>
The first processgroup in the FROM list that matches the REMOTEID and LOGIN indicator on the incoming conversation request is always used. The matching processgroup associates the process with internal resource limits such as the maximum number of concurrent conversations. 
</td>
</tr>

<tr>
<th><var>SUBSYSTEM</var></th>
<td> indicates the <var class="product">Model 204</var> application subsystem invoked by an inbound conversation request.</td>
</tr>

<tr>
<th><var>SUBSYSPARM</var></th>
<td> indicates the subsystem parameter line to be passed to this SUBSYSTEM. The maximum length is 255 characters.
SUBSYSTEM and SUBSYSPARM are not used for PQO processes.
When the server subsystem is invoked, the SUBSYSPARM value string is stored in the command-line global variable specified in the subsystem definition. If the subsystem definition does not specify a command line global variable, SUBSYSPARM is ignored.
When the SUBSYSPARM value string is stored in the command line global variable, Horizon automatically appends two characters: a blank and a semicolon (;), in that order.
By varying the SUBSYSPARM values, Horizon developers can implement different server processes as single application subsystems. User Language programs can thereby be tested without having to define a new subsystem. For more information about testing application programs using this parameter with the Rocket-provided subsystem, RPI, see the Horizon: Intersystem Processing Guide.
Supply the subsystem parameter line within quotation marks, if it contains any blanks, commas, or equal signs. The quotation marks cause <var class="product">Model 204</var> to treat the entire quoted string as a single token. If the quotation marks are not supplied, then blanks, commas, and equal signs are taken as token delimiters, causing <var class="product">Model 204</var> to treat the subsystem parameter line as having multiple tokens, and thus reject the DEFINE PROCESS command.
</td>
</tr>

</table>
==Example==
Sample (non-PQO) client process:
DEFINE PROCESS TIRES WITH -
SCOPE=SYSTEM -
DESTINATION=PARTS -
PARTNER=QRYTIRES -
TIMEOUT=60

Sample (non-PQO) server process: 
DEFINE PROCESS QRYTIRES WITH -
SCOPE=SYSTEM -
FROM=(INVENTRY) -
SUBSYSTEM=QTIRES -
TIMEOUT=60

==Usage notes==
The DEFINE PROCESS command specifies client (outbound) and server (inbound) processes. The DESTINATION or FROM parameter associates the process name with a set of processgroups, each of which associates the process with a link. By assigning processes to specific processgroups, the system manager can control their use of network resources.
There are two types of processes: 
<ul>
<li>
A client process, typically identified by the use of a PARTNER name. The DEFINE PROCESS command associates a symbolic name with the actual conversation partner transaction name. This allows the actual name of the conversation transaction to be modified without requiring changes to User Language requests.
</li>

<li>
A server process, typically identified by the use of the SUBSYSTEM parameter. Identifying the inbound process with the SUBSYSTEM option allows modification of the subsystem name without having to change the name that selects the transaction. 
</li>
</ul>
For more information about Horizon network and entities, see the <var>Model 204 Horizon: Intersystem Processing Guide</var>. For more information about PQO entities, see the <var>Parallel Query Option/204 User's Guide</var>. 
[[Category: System manager commands]]
[[Category:Commands]]