PQO: Defining a PQO network - Revision history

JAL: minor formatting

2018-08-08T16:53:06Z

minor formatting

← Older revision		Revision as of 16:53, 8 August 2018
Line 118:		Line 118:
	<th colspan="4">Model 204</tr>		<th colspan="4">Model 204</tr>
	<tr class="head">		<tr class="head">
	<th style="font-size:95%">Mode table</th>		<th style="font-size:90%">Mode table</th>
	<th style="font-size:95%">APPL statement</th>		<th style="font-size:90%">APPL statement</th>
	<th style="font-size:95%">DEFINE~~         <br/>~~LINK</th>		<th style="font-size:90%">DEFINE LINK</th>
	<th style="font-size:95%">DEFINE ~~<br/>~~PROCESSGROUP</th>		<th style="font-size:90%">DEFINE PROCESSGROUP</th>
	<th style="font-size:95%">DEFINE ~~<br/>~~PROCESS</th>		<th style="font-size:90%">DEFINE PROCESS</th>
	<th style="font-size:95%">Model 204 Online</th>		<th style="font-size:90%">Model 204 Online</th>
	</tr>		</tr>

JAL: minor formatting

2018-08-08T16:50:36Z

minor formatting

← Older revision		Revision as of 16:50, 8 August 2018
Line 115:		Line 115:
	<caption>Interrelated components of a PQO network for SNA Communications Server</caption>		<caption>Interrelated components of a PQO network for SNA Communications Server</caption>
	<tr class="head">		<tr class="head">
	<th ~~rowspan="1"~~ colspan="2">SNA</th>		<th colspan="2">SNA</th>
	<th ~~rowspan="1"~~ colspan="4">Model 204</tr>		<th colspan="4">Model 204</tr>
	<tr class="head">		<tr class="head">
	<th style="font-size:95%">Mode table</th>		<th style="font-size:95%">Mode table</th>
	<th style="font-size:95%">APPL statement</th>		<th style="font-size:95%">APPL statement</th>
	<th style="font-size:95%">DEFINE LINK</th>		<th style="font-size:95%">DEFINE         <br/>LINK</th>
	<th style="font-size:95%">DEFINE ~~PROCESS-GROUP~~</th>		<th style="font-size:95%">DEFINE <br/>PROCESSGROUP</th>
	<th style="font-size:95%">DEFINE PROCESS</th>		<th style="font-size:95%">DEFINE <br/>PROCESS</th>
	<th style="font-size:95%">Model 204 Online</th>		<th style="font-size:95%">Model 204 Online</th>
	</tr>		</tr>

	<tr>		<tr>
	<td> </td>		<td> </td>
	<td>One APPL for each link		<td>One APPL for each link
	<p>Label identifies LU application node</p>		<p>Label identifies LU application node</p></td>
	</td>		<td>Each link requires an APPL
	<td>		<p>LOCALID name must match APPL label</p></td>
	Each link requires an APPL		<td>REMOTEID applid must match LOCALID name on remote LU</td>
	<p>LOCALID name must match APPL label</p>
	</td>
	<td>REMOTEID applid must match LOCALID name on remote LU
	</td>
	<td> </td>		<td> </td>
	<td> </td>		<td> </td>
	</tr>		</tr>

	<tr>		<tr>
	<td> </td>		<td> </td>
Line 147:		Line 145:
	<td> </td>		<td> </td>
	</tr>		</tr>

	<tr>		<tr>
	<td> </td>		<td> </td>
Line 155:		Line 154:
	<td> </td>		<td> </td>
	</tr>		</tr>

	<tr>		<tr>
	<td> </td>		<td> </td>
Line 163:		Line 163:
	<td> </td>		<td> </td>
	</tr>		</tr>

	<tr>		<tr>
	<td> </td>		<td> </td>
Line 171:		Line 172:
	<td> </td>		<td> </td>
	</tr>		</tr>

	<tr>		<tr>
	<td> </td>		<td> </td>
Line 179:		Line 181:
	<td>SYSOPT includes X`10' to require login (server system)</td>		<td>SYSOPT includes X`10' to require login (server system)</td>
	</tr>		</tr>

	<tr>		<tr>
	<td> </td>		<td> </td>
Line 187:		Line 190:
	<td>NOTERM sets maximum number of threads for inbound conversations (server)</td>		<td>NOTERM sets maximum number of threads for inbound conversations (server)</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>LU 6.2 mode table for Model 204</td>		<td>LU 6.2 mode table for Model 204</td>
	<td>MODETAB specifies LU 6.2 table		<td>MODETAB specifies LU 6.2 table
	<p>DLOGMOD specifies entry in table (optional)</p>		<p>DLOGMOD specifies entry in table (optional)</p>

ELowell: /* Client process DESTINATION parameter */

2017-12-06T22:36:31Z

Client process DESTINATION parameter

← Older revision		Revision as of 22:36, 6 December 2017
Line 439:		Line 439:
	<span class="term">sym1</span> and <span class="term">sym2</span> are symbolic names, each from 1-8 characters in length. Each symbolic name is associated with the corresponding processgroup name in the pair.		<span class="term">sym1</span> and <span class="term">sym2</span> are symbolic names, each from 1-8 characters in length. Each symbolic name is associated with the corresponding processgroup name in the pair.

	A symbolic name defined here is used with AT in a remote file specification to refer to a processgroup that is associated with a particular remote location. ~~<A HREF="Chap5.htm~~#~~0_50778" CLASS="XRef">See~~ Specifying a remote file~~</A>~~ describes how symbolic location names are used to reference a remote file.		A symbolic name defined here is used with AT in a remote file specification to refer to a processgroup that is associated with a particular remote location. [[PQO:_Remote_files_and_scattered_groups#Specifying_a_remote_file\|Specifying a remote file]] describes how symbolic location names are used to reference a remote file.
	</li>		</li>
	</ul>		</ul>

JAL: typo

2017-03-29T16:41:51Z

typo

← Older revision		Revision as of 16:41, 29 March 2017
Line 813:		Line 813:
	MASK=255.255.255.0</p>		MASK=255.255.255.0</p>

	===~~APPLO~~ statements required for only SNA Communications Server network===		===APPL statements required for only SNA Communications Server network===

	====Client APPL statement====		====Client APPL statement====

JAL: misc formatting

2017-03-28T20:40:03Z

misc formatting

← Older revision		Revision as of 20:40, 28 March 2017
Line 632:		Line 632:
	SNA Communications Server communications support must be in place to use PQO. This section describes how to set up the SNA Communications Server network definition with parameters that correspond correctly to the Model 204 network definitions.</p>		SNA Communications Server communications support must be in place to use PQO. This section describes how to set up the SNA Communications Server network definition with parameters that correspond correctly to the Model 204 network definitions.</p>
	<p>		<p>
	The SNA Communications Server setup is similar to that required for Horizon without PQO. See [[Horizon network management]] for information about SNA Communications Server network support for Horizon. [[#netwk_config\|Basic network configuration]] shows the basic PQO communications pathway. </p>		The SNA Communications Server setup is similar to that required for Horizon without PQO. See [[Horizon network management]] for information about SNA Communications Server network support for Horizon. [[#netwk_config\|Basic network configuration]], above, shows the basic PQO communications pathway. </p>

	===Components of SNA Communications Server definition===		===Components of SNA Communications Server definition===

JAL: typo

2017-03-28T18:31:49Z

typo

← Older revision		Revision as of 18:31, 28 March 2017
Line 632:		Line 632:
	SNA Communications Server communications support must be in place to use PQO. This section describes how to set up the SNA Communications Server network definition with parameters that correspond correctly to the Model 204 network definitions.</p>		SNA Communications Server communications support must be in place to use PQO. This section describes how to set up the SNA Communications Server network definition with parameters that correspond correctly to the Model 204 network definitions.</p>
	<p>		<p>
	The SNA Communications Server setup is similar to that required for Horizon without PQO. See [[Horizon network management]] for information about SNA Communications Server network support for Horizon. [[##netwk_config\|Basic network configuration]] shows the basic PQO communications pathway. </p>		The SNA Communications Server setup is similar to that required for Horizon without PQO. See [[Horizon network management]] for information about SNA Communications Server network support for Horizon. [[#netwk_config\|Basic network configuration]] shows the basic PQO communications pathway. </p>

	===Components of SNA Communications Server definition===		===Components of SNA Communications Server definition===

JAL: link repair

2017-03-28T18:30:56Z

link repair

← Older revision		Revision as of 18:30, 28 March 2017
Line 43:		Line 43:
	<li>Optional use of APSY subsystems</li>		<li>Optional use of APSY subsystems</li>
	</ul>		</ul>
	<~~div id~~="~~netwk_config~~"~~></div>~~		<p class="caption" id="netwk_config" style="width:468px">Basic network configuration</p>
	~~<p class~~="~~caption~~" style="width:468px">Basic network configuration</p>
	<p class="figure">[[File:PQO_ch2_1.gif]] </p>		<p class="figure">[[File:PQO_ch2_1.gif]] </p>
	<p>		<p>
Line 633:		Line 632:
	SNA Communications Server communications support must be in place to use PQO. This section describes how to set up the SNA Communications Server network definition with parameters that correspond correctly to the Model 204 network definitions.</p>		SNA Communications Server communications support must be in place to use PQO. This section describes how to set up the SNA Communications Server network definition with parameters that correspond correctly to the Model 204 network definitions.</p>
	<p>		<p>
	The SNA Communications Server setup is similar to that required for Horizon without PQO. See [[Horizon network management]] for information about SNA Communications Server network support for Horizon. [[#~~Basic network configuration~~\|Basic network configuration]] shows the basic PQO communications pathway. </p>		The SNA Communications Server setup is similar to that required for Horizon without PQO. See [[Horizon network management]] for information about SNA Communications Server network support for Horizon. [[##netwk_config\|Basic network configuration]] shows the basic PQO communications pathway. </p>

	===Components of SNA Communications Server definition===		===Components of SNA Communications Server definition===

JAL: link repair

2016-11-29T16:31:35Z

link repair

← Older revision		Revision as of 16:31, 29 November 2016
Line 573:		Line 573:
	===Setting the NSUBTKS parameter===		===Setting the NSUBTKS parameter===
	<p>		<p>
	The NSUBTKS parameter is required for LU 6.2 pseudo-subtasks. ~~The syntax of the NSUBTKS parameter is: </p>~~		The <var>[[NSUBTKS parameter\|NSUBTKS]]</var> parameter is required for LU 6.2 [[Controlling system operations (CCAIN)#Pseudo subtasks\|pseudo subtasks]].

	~~<b>Syntax</b>~~

			The syntax of the <var>NSUBTKS</var> parameter is: </p>
	<p class="syntax">NSUBTKS=<span class="term">nnnnn</span></p>		<p class="syntax">NSUBTKS=<span class="term">nnnnn</span></p>
	<p>		<p>
	~~where~~:~~</p>~~		Where:</p>
	~~<p>~~
	<var class="term">nnnnn</var> is a number value that specifies the maximum number of pseudo-subtasks that can be used in a Model 204 run. For PQO, this number must be increased by two per link if running under z/OS, or by four per link if running under z/VM.</p>
	<p>		<p>
	For ~~performance reasons, Horizon and~~ PQO ~~conversations should not share links. However~~, ~~if the NSUBTKS parameter was previously~~ increased ~~for Horizon links and the PQO network is sharing~~ link ~~definitions with Horizon~~, ~~it is not necessary to increase NSUBTKS for PQO~~.</p>		<var class="term">nnnnn</var> is a number value that specifies the maximum number of pseudo subtasks that can be used in a Model 204 run. For PQO, this number must be increased by two per link if running under z/OS, or by four per link if running under z/VM.</p>
	<p>		<p>
	~~The~~ <var>[[NSUBTKS parameter\|NSUBTKS]]</var> ~~is located in the User 0 parameter line in the client and server Onlines~~.</p>		For performance reasons, Horizon and PQO conversations should not share links. However, if the <var>NSUBTKS</var> parameter was previously increased for Horizon links and the PQO network is sharing link definitions with Horizon, it is not necessary to increase <var>NSUBTKS</var> for PQO.</p>
	<p>		<p>
	~~For a description of pseudo-subtasks, see [[Controlling System Operations (SDN)]]~~.</p>		<var>NSUBTKS</var> is located in the User  0 parameter line in the client and server Onlines.</p>

	===Specifying IODEVs for PQO service threads===		===Specifying IODEVs for PQO service threads===
	<p>		<p>
	In PQO, the server application processes the file locally and sends the data back to the client. The server's Online must provide the PQO service threads, which are defined by a particular class of IODEV statements, to process client requests. </p>		In PQO, the server application processes the file locally and sends the data back to the client. The server's Online must provide the PQO service threads, which are defined by a particular class of IODEV statements, to process client requests. </p>
	<p>		<p>
	Each IODEV=51 line in a server Online CCAIN stream defines a PQO service thread. You must determine the number of IODEV=51 lines in each server Online that optimally service your client demand. </p>		Each IODEV=51 line in a server Online CCAIN stream defines a PQO service thread. You must determine the number of IODEV=51 lines in each server Online that optimally service your client demand. </p>
Line 600:		Line 597:
	<p class="syntax">IODEV=51,NOTERM=<span class="term">nn</span></p>		<p class="syntax">IODEV=51,NOTERM=<span class="term">nn</span></p>
	<p>		<p>
	~~where~~:</p>		Where:</p>
	<ul>		<ul>
	<li>		<li>

ELowell: /* DEFINE PROCESSGROUP command for TCP/IP service */

2016-03-17T16:19:06Z

DEFINE PROCESSGROUP command for TCP/IP service

← Older revision		Revision as of 16:19, 17 March 2016
Line 317:		Line 317:
	<ul>		<ul>
	<li>		<li>
	<span class="term">name</span> is used on DEFINE PROCESS commands to refer to this processgroup. The length of the name must be eight characters or ~~less~~. ALL is a reserved word and cannot be used. </li>		<span class="term">name</span> is used on DEFINE PROCESS commands to refer to this processgroup. The length of the name must be eight characters or fewer. <var>ALL</var> is a reserved word and cannot be used. </li>
	<li>		<li>
	LINK is required and associates the group with a locally defined link that implies the transport type and conversation protocol. <span class="term">linkname</span> must match the name used in a local DEFINE LINK command. </li>		LINK is required and associates the group with a locally defined link that implies the transport type and conversation protocol. <span class="term">linkname</span> must match the name used in a local DEFINE LINK command. </li>

ELowell: /* Setting session parameters */

2016-02-05T00:13:53Z

Setting session parameters

← Older revision		Revision as of 00:13, 5 February 2016
Line 690:		Line 690:
	The mode table showing the basic set of LU 6.2 session parameters recommended for both Horizon and PQO is shown in the following example. </p>		The mode table showing the basic set of LU 6.2 session parameters recommended for both Horizon and PQO is shown in the following example. </p>
	<p>		<p>
	See the [[#modetab\| Notes on MODETAB]] for a description of the APPL parameter used to reference this table. See [[Horizon network management#Modifications for specific systems and applications\|Modifications for specific systems and applications]] for ~~parameter descriptions and for information~~ about modifying the mode table parameters such as RUSIZES and SSNDPAC.</p>		See the [[#modetab\| Notes on MODETAB]] for a description of the APPL parameter used to reference this table.</p>
			<p>See [[Horizon network management]] for more information about APPL; specifically, see [[Horizon network management#Modifications for specific systems and applications\|Modifications for specific systems and applications]] for details about modifying the mode table parameters such as RUSIZES and SSNDPAC.</p>

	====Mode table example====		====Mode table example====