Horizon connections to non-Model 204 systems - Revision history

ELowell: /* Connecting to OS/2 EE */ - deleted obsolete section

2015-10-16T21:44:06Z

Connecting to OS/2 EE: - deleted obsolete section

@@ Line 273: / Line 273: @@
 </ul>
 <p>Either side may now restart the connection at any time.</p>
 ==Connecting to UNIX System V and AT&amp;T LU 6.2 Facility==
 <p>

ELowell: /* Connecting to VAX/VMS */ - deleted obsolete section

2015-10-16T21:43:28Z

Connecting to VAX/VMS: - deleted obsolete section

@@ Line 273: / Line 273: @@
 </ul>
 <p>Either side may now restart the connection at any time.</p>
 ==Connecting to OS/2 EE==
 <p>

ELowell: /* Security considerations */

2015-09-30T20:59:57Z

Security considerations

← Older revision		Revision as of 20:59, 30 September 2015
Line 212:		Line 212:
	</table>		</table>

	<~~blockquote~~ class="note"><b>Note:</b> For conversations invoked on the CICS side, the security level is always equivalent to "identify": CICS always sends a user ID but never sends a password.</~~blockquote~~>		<p class="note"><b>Note:</b> For conversations invoked on the CICS side, the security level is always equivalent to "identify": CICS always sends a user ID but never sends a password.</p>

	===Specifying the Model 204 partner program===		===Specifying the Model 204 partner program===

ELowell: /* Security considerations */

2015-09-30T20:59:12Z

Security considerations

← Older revision		Revision as of 20:59, 30 September 2015
Line 212:		Line 212:
	</table>		</table>

	<p class="note"><b>Note:</b> For conversations invoked on the CICS side, the security level is always equivalent to "identify": CICS always sends a user ID but never sends a password.</p>		<blockquote class="note"><b>Note:</b> For conversations invoked on the CICS side, the security level is always equivalent to "identify": CICS always sends a user ID but never sends a password.</blockquote>

	===Specifying the Model 204 partner program===		===Specifying the Model 204 partner program===

ELowell: /* Security considerations */

2015-09-30T20:58:47Z

Security considerations

← Older revision		Revision as of 20:58, 30 September 2015
Line 184:		Line 184:
	The levels of security support for conversations invoked from the Model 204 side are specified on the ATTACHSEC parameter (on CONNECTION). They should correspond to Horizon security values as shown in the following table: </p>		The levels of security support for conversations invoked from the Model 204 side are specified on the ATTACHSEC parameter (on CONNECTION). They should correspond to Horizon security values as shown in the following table: </p>
	<table>		<table>
	<p class="caption">CICS LU 6.2 Security Support Compared to Horizon </p>		<p class="caption" style="width:468px">CICS LU 6.2 Security Support Compared to Horizon</p>
	<tr class="head">		<tr class="head">
	<th>CICS side</th>		<th>CICS side</th>

ELowell at 20:57, 30 September 2015

2015-09-30T20:57:29Z

← Older revision		Revision as of 20:57, 30 September 2015
Line 24:		Line 24:

	<b id="HorizonCICS"></b><p class="caption" style="width:468px">The Horizon/CICS environment</p>		<b id="HorizonCICS"></b><p class="caption" style="width:468px">The Horizon/CICS environment</p>
	<p class="figure">[[File:~~Horizon_fig_D~~-1_Horizon_CICS.gif~~\|468px~~]] </p>		<p class="figure">[[File:Horizon_figD-1_Horizon_CICS.gif]] </p>

	===One LU for CICS; multiple LUs for Model 204===		===One LU for CICS; multiple LUs for Model 204===
Line 48:		Line 48:
	===Preparing the log mode definitions===		===Preparing the log mode definitions===
	<p>		<p>
	Mode table configuration, including an example of recommended mode table entry values for Horizon, is discussed in [[~~Network~~ management#Defining the network to SNA Communications Server\|Defining the network to SNA Communications Server]]. </p>		Mode table configuration, including an example of recommended mode table entry values for Horizon, is discussed in [[Horizon network management#Defining the network to SNA Communications Server\|Defining the network to SNA Communications Server]]. </p>
	<p>		<p>
	The following are recommendations for mode table configuration: </p>		The following are recommendations for mode table configuration: </p>
	<ul>		<ul>
	<li>		<li>
	Use <i>only</i> one table for all LU 6.2 sessions, between all systems. Let this table's first entry--which serves as the default entry--be the most widely applicable one, such as the one with the values for single-session support recommended in [[~~Network~~ management]].</li>		Use <i>only</i> one table for all LU 6.2 sessions, between all systems. Let this table's first entry--which serves as the default entry--be the most widely applicable one, such as the one with the values for single-session support recommended in [[Horizon network management]].</li>
	<li>		<li>
	If using CNOS sessions, include an SNASVCMG entry and an entry with parallel session support somewhere in the table.</li>		If using CNOS sessions, include an SNASVCMG entry and an entry with parallel session support somewhere in the table.</li>
Line 75:		Line 75:

	<b id="SNAparam"></b><p class="caption" style="width:468px">SNA Communications Server Session Parameter Selection</p>		<b id="SNAparam"></b><p class="caption" style="width:468px">SNA Communications Server Session Parameter Selection</p>
	<p class="figure">[[File:~~Horizon_fig_D~~-2_SNA_Comm_Serv.gif~~\|468px~~]] </p>		<p class="figure">[[File:Horizon_figD-2_SNA_Comm_Serv.gif]]</p>

	<p>		<p>
Line 301:		Line 301:
	<ul>		<ul>
	<li>		<li>
	When defining the VAX's and their LUs to SNA Communications Server/NCP, the VAX requires outbound pacing on the data flow to it from the NCP. Make the alteration to the [[~~Network~~ management#MODETAB, also called logon mode table\|logmode table for LU 6.2]]. Add the following parameter setting: <br />		When defining the VAX's and their LUs to SNA Communications Server/NCP, the VAX requires outbound pacing on the data flow to it from the NCP. Make the alteration to the [[Horizon network management#MODETAB, also called logon mode table\|logmode table for LU 6.2]]. Add the following parameter setting: <br />
	<code>SRCVPAC=4</code></li>		<code>SRCVPAC=4</code></li>

Line 327:		Line 327:
	<ul>		<ul>
	<li>		<li>
	In addition to the logmode table modifications for LU 6.2 suggested in [[~~Network~~ management#Recommended mode table parameter values\|Recommended mode table parameter values]]:		In addition to the logmode table modifications for LU 6.2 suggested in [[Horizon network management#Recommended mode table parameter values\|Recommended mode table parameter values]]:
	<p>		<p>
	For LOCADDR, DECnet/SNA Gateway supports a range of values of 1 to 128; VMS/SNA supports a range of values of 1 to 64.</p> </li>		For LOCADDR, DECnet/SNA Gateway supports a range of values of 1 to 128; VMS/SNA supports a range of values of 1 to 64.</p> </li>
Line 415:		Line 415:
	On a switched SDLC line, the NODE ID on the SNA BASE PROFILE in Communications Manager must be in sync with the IDNUM parameter on the PU macro for the IBM PS/2 LU. Also, you must enter a value of "05D" in the IDBLK parameter in the PU macro. </li>		On a switched SDLC line, the NODE ID on the SNA BASE PROFILE in Communications Manager must be in sync with the IDNUM parameter on the PU macro for the IBM PS/2 LU. Also, you must enter a value of "05D" in the IDBLK parameter in the PU macro. </li>
	<li>		<li>
	You can use the recommended logmode table entry shown in the [[~~Network~~ management#MODETAB, also called logon mode table\|logon table]] section.</li>		You can use the recommended logmode table entry shown in the [[Horizon network management#MODETAB, also called logon mode table\|logon table]] section.</li>
	</ul>		</ul>

ELowell: Created page with "==Connecting to CICS==
Compared to a Model 204-to-Model 204 Horizon conversation, a Model 204-to-CICS Horizon conversation requires some additional conceptual understandin..."

2015-09-30T20:51:13Z

Created page with "==Connecting to CICS== <p> Compared to a Model 204-to-Model 204 Horizon conversation, a Model 204-to-CICS Horizon conversation requires some additional conceptual understandin..."

Show changes

Horizon connections to non-Model 204 systems - Revision history

ELowell: /* Connecting to OS/2 EE */ - deleted obsolete section

ELowell: /* Connecting to VAX/VMS */ - deleted obsolete section

ELowell: /* Security considerations */

ELowell: /* Security considerations */

ELowell: /* Security considerations */

ELowell at 20:57, 30 September 2015

ELowell: Created page with "==Connecting to CICS== Compared to a Model 204-to-Model 204 Horizon conversation, a Model 204-to-CICS Horizon conversation requires some additional conceptual understandin..."

ELowell: Created page with "==Connecting to CICS==
Compared to a Model 204-to-Model 204 Horizon conversation, a Model 204-to-CICS Horizon conversation requires some additional conceptual understandin..."