Using Program Communication facilities - Revision history

ELowell: /* Overview */

2016-02-04T20:32:46Z

Overview

← Older revision		Revision as of 20:32, 4 February 2016
Line 10:		Line 10:
	In addition, <var class="product">Model 204</var> provides program-to-program processing support through its distributed application facility, Horizon, an optional feature. <var class="product">Model 204</var> applications can communicate through SNA Communications Server with one or more other programs using program-to-program processing. Communication takes place over an SNA network, using verbs and protocols conforming to LU 6.2 architecture. Horizon uses SOUL statements and <var class="product">Model 204</var> commands, and might require IODEV=27 threads. </p>		In addition, <var class="product">Model 204</var> provides program-to-program processing support through its distributed application facility, Horizon, an optional feature. <var class="product">Model 204</var> applications can communicate through SNA Communications Server with one or more other programs using program-to-program processing. Communication takes place over an SNA network, using verbs and protocols conforming to LU 6.2 architecture. Horizon uses SOUL statements and <var class="product">Model 204</var> commands, and might require IODEV=27 threads. </p>
	<p>		<p>
	This topic provides a summary of system management information for the support of the Program Communication facilities. Horizon is described in the ~~<var class="book">Rocket Model 204~~ Horizon~~: Intersystem Processing Guide</var>;~~ IODEV=27 threads are discussed in [[Defining the user environment (CCAIN)#Horizon (IODEV=27)\|Horizon (IODEV=27)]]. </p>		This topic provides a summary of system management information for the support of the Program Communication facilities. Horizon is described in the [[:Category: Horizon\|Horizon]] wiki topics. IODEV=27 threads are discussed in [[Defining the user environment (CCAIN)#Horizon (IODEV=27)\|Horizon (IODEV=27)]].</p>

	==Preparing for TPROCESS communication==		==Preparing for TPROCESS communication==

JALWiccan: Automatically generated page update

2014-11-06T17:08:23Z

Automatically generated page update

← Older revision		Revision as of 17:08, 6 November 2014
Line 124:		Line 124:
	Selection of these security options is discussed in [[Program Communication facilities#Security for Model 204-to-Model 204 transfers\|Security for Model 204-to-Model 204 transfers]].</p>		Selection of these security options is discussed in [[Program Communication facilities#Security for Model 204-to-Model 204 transfers\|Security for Model 204-to-Model 204 transfers]].</p>

	[[Category:System ~~Manager~~]]		[[Category:System management]]
	[[Category:System-level capabilities of Model 204]]		[[Category:System-level capabilities of Model 204]]

JALWiccan: Automatically generated page update

2014-11-05T17:13:07Z

Automatically generated page update

← Older revision		Revision as of 17:13, 5 November 2014
Line 125:		Line 125:

	[[Category:System Manager]]		[[Category:System Manager]]
	[[Category:System-level capabilities ~~available in~~ Model 204]]		[[Category:System-level capabilities of Model 204]]

JAL at 21:17, 29 October 2014

2014-10-29T21:17:51Z

← Older revision		Revision as of 21:17, 29 October 2014
Line 125:		Line 125:

	[[Category:System Manager]]		[[Category:System Manager]]
			[[Category:System-level capabilities available in Model 204]]

Admin at 20:58, 20 October 2014

2014-10-20T20:58:37Z

← Older revision		Revision as of 20:58, 20 October 2014
Line 36:		Line 36:
	You must link the CICS program identified by the <var>DEFINE</var> command with the IFPPCI module. </p>		You must link the CICS program identified by the <var>DEFINE</var> command with the IFPPCI module. </p>
	<p>		<p>
	IFPPCI has five entry points (<var>IFCSA</var>, <var>IFPREP</var>, <var>IFSEND</var>, <var>IFRECV</var>, and <var>IFSGNL</var>) that the CICS program can call. These calls are described in [[Program ~~communications~~ facilities#CICS TPROCESS calls\|CICS TPROCESS calls]]. </p>		IFPPCI has five entry points (<var>IFCSA</var>, <var>IFPREP</var>, <var>IFSEND</var>, <var>IFRECV</var>, and <var>IFSGNL</var>) that the CICS program can call. These calls are described in [[Program Communication facilities#CICS TPROCESS calls\|CICS TPROCESS calls]]. </p>

	====Installing the full-screen CICS Interface====		====Installing the full-screen CICS Interface====
Line 65:		Line 65:
	===For more information===		===For more information===
	<p>		<p>
	Functions and subcommands used in TPROCESS are described in [[Program ~~communications~~ facilities#CMS TPROCESS communication\|CMS TPROCESS communication]].		Functions and subcommands used in TPROCESS are described in [[Program Communication facilities#CMS TPROCESS communication\|CMS TPROCESS communication]].
	</p>		</p>

Line 72:		Line 72:
	In Transfer Control, SOUL requests transfer control to a CICS program or SNA Communications Server application by issuing the TRANSFER statement. Control is passed to the CICS or SNA Communications Server application partner process, and the CICS or SNA Communications Server application user is disconnected from <var class="product">Model 204</var>.</p>		In Transfer Control, SOUL requests transfer control to a CICS program or SNA Communications Server application by issuing the TRANSFER statement. Control is passed to the CICS or SNA Communications Server application partner process, and the CICS or SNA Communications Server application user is disconnected from <var class="product">Model 204</var>.</p>
	<p>		<p>
	This section presents overview information for the system manager about the Transfer Control facility. The primary source for operational information for the facility is [[Program ~~communications~~ facilities#Transfer Control facility\|Transfer Control facility]]. </p>		This section presents overview information for the system manager about the Transfer Control facility. The primary source for operational information for the facility is [[Program Communication facilities#Transfer Control facility\|Transfer Control facility]]. </p>

	===SNA Communications Server transfers are more complex===		===SNA Communications Server transfers are more complex===
Line 80:		Line 80:
	<li>Inter-regional security concerns might require a transfer to provide for login and password processing at the destination region.		<li>Inter-regional security concerns might require a transfer to provide for login and password processing at the destination region.
	<p>		<p>
	<var>DEFINE</var> command and [[Program ~~communications~~ facilities#TRANSFER statement format and execution\|TRANSFER statement format and execution]] options available only for SNA Communications Server transfers determine how the command string passed in the transfer is processed at the destination.</p>		<var>DEFINE</var> command and [[Program Communication facilities#TRANSFER statement format and execution\|TRANSFER statement format and execution]] options available only for SNA Communications Server transfers determine how the command string passed in the transfer is processed at the destination.</p>
	</li>		</li>

Line 122:		Line 122:
	<p>		<p>
	Proper login and handling of the passed command string requires coordination between the security options specified in the <var>DEFINE</var> commands and the <var>TRANSFER</var> statement.		Proper login and handling of the passed command string requires coordination between the security options specified in the <var>DEFINE</var> commands and the <var>TRANSFER</var> statement.
	Selection of these security options is discussed in [[Program ~~communications~~ facilities#Security for Model 204-to-Model 204 transfers\|Security for Model 204-to-Model 204 transfers]].</p>		Selection of these security options is discussed in [[Program Communication facilities#Security for Model 204-to-Model 204 transfers\|Security for Model 204-to-Model 204 transfers]].</p>

	[[Category:System Manager]]		[[Category:System Manager]]

JAL: /* Preparing for TPROCESS communication */

2014-10-20T20:13:15Z

Preparing for TPROCESS communication

← Older revision		Revision as of 20:13, 20 October 2014
Line 24:		Line 24:
	<p>		<p>
	The following sections describe the system manager actions required to enable TPROCESS.		The following sections describe the system manager actions required to enable TPROCESS.
	The operation of the TPROCESS and Transfer Control facilities is described in [[Program ~~communications~~ facilities]]. </p>		The operation of the TPROCESS and Transfer Control facilities is described in [[Program Communication facilities]]. </p>

	===Defining the partners===		===Defining the partners===
Line 67:		Line 67:
	Functions and subcommands used in TPROCESS are described in [[Program communications facilities#CMS TPROCESS communication\|CMS TPROCESS communication]].		Functions and subcommands used in TPROCESS are described in [[Program communications facilities#CMS TPROCESS communication\|CMS TPROCESS communication]].
	</p>		</p>

	==Preparing for Transfer Control communication==		==Preparing for Transfer Control communication==
	<p>		<p>

JAL: /* Overview */

2014-10-20T20:00:59Z

Overview

← Older revision		Revision as of 20:00, 20 October 2014
Line 10:		Line 10:
	In addition, <var class="product">Model 204</var> provides program-to-program processing support through its distributed application facility, Horizon, an optional feature. <var class="product">Model 204</var> applications can communicate through SNA Communications Server with one or more other programs using program-to-program processing. Communication takes place over an SNA network, using verbs and protocols conforming to LU 6.2 architecture. Horizon uses SOUL statements and <var class="product">Model 204</var> commands, and might require IODEV=27 threads. </p>		In addition, <var class="product">Model 204</var> provides program-to-program processing support through its distributed application facility, Horizon, an optional feature. <var class="product">Model 204</var> applications can communicate through SNA Communications Server with one or more other programs using program-to-program processing. Communication takes place over an SNA network, using verbs and protocols conforming to LU 6.2 architecture. Horizon uses SOUL statements and <var class="product">Model 204</var> commands, and might require IODEV=27 threads. </p>
	<p>		<p>
	This topic provides a summary of system management information for the support of the Program Communication facilities. Horizon is described in the <var class="book">Rocket Model 204 Horizon: Intersystem Processing Guide</var>; IODEV=27 threads are discussed in [[Defining the ~~User Environment~~ (CCAIN)#Horizon (IODEV=27)\|Horizon (IODEV=27)]]. </p>		This topic provides a summary of system management information for the support of the Program Communication facilities. Horizon is described in the <var class="book">Rocket Model 204 Horizon: Intersystem Processing Guide</var>; IODEV=27 threads are discussed in [[Defining the user environment (CCAIN)#Horizon (IODEV=27)\|Horizon (IODEV=27)]]. </p>

	==Preparing for TPROCESS communication==		==Preparing for TPROCESS communication==
	<p>		<p>

Admin: 1 revision: converted system mgr pages

2014-10-17T20:27:52Z

1 revision: converted system mgr pages

← Older revision	Revision as of 20:27, 17 October 2014
(No difference)

JAL: more conversion cleanup

2014-10-15T20:31:46Z

more conversion cleanup

New page

==Overview==

Program Communication, available on CICS, CMS, and SNA Communications Server (formerly VTAM) full-screen threads (IODEV=11, IODEV=41, and IODEV=7, respectively), allows [[SOUL]] requests to communicate with user-written CICS programs, CMS EXECs, or SNA Communications Server applications. The [[Program Communication facilities]], that is, TPROCESS (Terminal Process) and Transfer Control, allow a SOUL request to do the following: 
<ul>
<li>TPROCESS — Identify, trigger execution of, and communicate with a CICS partner program or CMS partner EXEC</li>

<li>Transfer Control — Identify a CICS partner program or SNA Communications Server partner application, transfer control to the program or application, and pass it a parameter area</li>
</ul>

In addition, <var class="product">Model 204</var> provides program-to-program processing support through its distributed application facility, Horizon, an optional feature. <var class="product">Model 204</var> applications can communicate through SNA Communications Server with one or more other programs using program-to-program processing. Communication takes place over an SNA network, using verbs and protocols conforming to LU 6.2 architecture. Horizon uses SOUL statements and <var class="product">Model 204</var> commands, and might require IODEV=27 threads. 

This topic provides a summary of system management information for the support of the Program Communication facilities. Horizon is described in the <var class="book">Rocket Model 204 Horizon: Intersystem Processing Guide</var>; IODEV=27 threads are discussed in [[Defining the User Environment (CCAIN)#Horizon (IODEV=27)|Horizon (IODEV=27)]]. 

==Preparing for TPROCESS communication==

TPROCESS communication works under CICS or CMS. SOUL requests communicate with a CICS program or CMS EXEC by issuing the OPEN PROCESS and CLOSE PROCESS commands and using SEND, RECEIVE, FLUSH PROCESS, and SIGNAL PROCESS statements. 

The calls used by CICS and CMS are the following: 
<ul>
<li>CICS communicates with the SOUL request by calling the <var>IFCSA</var>, <var>IFSEND</var>, <var>IFRECV</var>, and <var>IFSGNL</var> functions resolved by the IFPPCI module. </li>

<li>CMS EXEC communicates with the SOUL request through the <var>IFSENDX</var>, <var>IFRECV</var>, and <var>IFSGNL</var> subcommands.</li>
</ul>

The following sections describe the system manager actions required to enable TPROCESS.
The operation of the TPROCESS and Transfer Control facilities is described in [[Program communications facilities]]. 

===Defining the partners===

Before a SOUL request can communicate with either CICS or CMS, you must define a partner process (CICS program or CMS EXEC) for reference by SOUL statements. Define the process and its attributes with the <var>[[DEFINE LINK command: TPROCESS|DEFINE LINK]]</var>, <var>[[DEFINE PROCESSGROUP command: TPROCESS|DEFINE PROCESSGROUP]]</var>, and <var>[[DEFINE PROCESS command: TPROCESS partner|DEFINE PROCESS]]</var> commands. These commands connect the process to a link, identify the communication protocol to be used with the partner process, and define the partner process you must enable the link defined by the <var>DEFINE LINK</var> command with the <var>[[OPEN LINK command|OPEN LINK]]</var> command. 

===Preparing for CICS TPROCESS===

====Linking to IFPPCI====

You must link the CICS program identified by the <var>DEFINE</var> command with the IFPPCI module. 

IFPPCI has five entry points (<var>IFCSA</var>, <var>IFPREP</var>, <var>IFSEND</var>, <var>IFRECV</var>, and <var>IFSGNL</var>) that the CICS program can call. These calls are described in [[Program communications facilities#CICS TPROCESS calls|CICS TPROCESS calls]]. 

====Installing the full-screen CICS Interface====

The PPT entry for the full screen CICS Interface module name (<code>M204PSFS</code>) must specify a TWA size. 

====Specifying buffer sizes====

Screen and CRAM buffer sizes are dependent on the model type and <var>[[LOUTPB parameter|LOUTPB]]</var> size specification. The <var>LOUTPB</var> parameter for IODEV=11 determines the CRAM buffer size. Set <var>LOUTPB</var> slightly larger than the screen size for the 3270 model type used. If users are resetting model types, set <var>LOUTPB</var> to match the largest screen size. 

===Preparing for CMS TPROCESS===

====Installing the M204USR module====

In CMS, the reentrant <code>M204USR</code> module, which must be installed as a saved segment or as a nucleus extension (see the <var class="book">Rocket Model 204 z/VM Installation Guide</var>), acts as the interface that calls a CMS EXEC (REXX or EXEC2) to communicate with a SOUL request through subcommands. M204USR is the module name, if the M204USR module is installed as a saved segment. M204USR is the module name, if the M204USR module is installed as a nucleus extension. 

Installing M204USR as a saved segment or nucleus extension avoids the possibility of overlaying the interface module by commands that run in the user area.

====Constraints====

<var class="product">Model 204</var> supports communication between a SOUL request and one concurrent CMS partner process, subject to the following constraints:
<ul>
<li>The CMS partner process must be written in System Product Interpreter language (REXX) or EXEC2. Communication occurs through the standard CMS SUBCOM interface, which is supported by these languages.</li>

<li>If any program executed by the CMS partner process terminates abnormally, the user's thread is disconnected. </li>
</ul>

===For more information===

Functions and subcommands used in TPROCESS are described in [[Program communications facilities#CMS TPROCESS communication|CMS TPROCESS communication]].


==Preparing for Transfer Control communication==

In Transfer Control, SOUL requests transfer control to a CICS program or SNA Communications Server application by issuing the TRANSFER statement. Control is passed to the CICS or SNA Communications Server application partner process, and the CICS or SNA Communications Server application user is disconnected from <var class="product">Model 204</var>.

This section presents overview information for the system manager about the Transfer Control facility. The primary source for operational information for the facility is [[Program communications facilities#Transfer Control facility|Transfer Control facility]]. 

===SNA Communications Server transfers are more complex===

CICS transfers are within a single region (between the <var class="product">Model 204</var> CICS Interface and a CICS program running in the same region). SNA Communications Server transfers are between SNA Communications Server regions, using the PASS option of the CLSDST macro. SNA Communications Server transfers are more complex: 
<ul>
<li>Inter-regional security concerns might require a transfer to provide for login and password processing at the destination region.

<var>DEFINE</var> command and [[Program communications facilities#TRANSFER statement format and execution|TRANSFER statement format and execution]] options available only for SNA Communications Server transfers determine how the command string passed in the transfer is processed at the destination.
</li>

<li>You might have to specially format the passed command-line data to suit a non-<var class="product">Model 204</var> destination application.

When the destination application is another <var class="product">Model 204</var> region, the login string can be automatically formatted by specifying the appropriate <var>DEFINE PROCESSGROUP</var> option. In this case, the login string is also encrypted; it is decrypted at the destination <var class="product">Model 204</var> region. 
</li>

<li>A CICS transfer failure leaves the user in the CICS Interface, whereas a SNA Communications Server transfer failure can leave the user in SNA Communications Server between applications.

A user can successfully transfer via SNA Communications Server to an application in another region but fail login requirements at the destination application. A mechanism is required to return the user from SNA Communications Server to the original <var class="product">Model 204</var> environment or to another SNA Communications Server application.

The <var>[[$Remote]]</var> function returns the <var>[[VTAMNAME parameter|VTAMNAME]]</var> parameter value of the region from which the SNA Communications Server transfer issues. This facilitates the transfer of the user back to the initial <var class="product">Model 204</var> region. 
</li>

<li>If a SNA Communications Server TRANSFER fails, <var class="product">Model 204</var> attempts to get the terminal back by issuing an <code>OPNDST</code> with the <code>ACQUIRE</code> option. Therefore, if the Online is to support SNA Communications Server <var>TRANSFER</var>, the VTAMNAME APPL definition must contain <code>AUTH=(PASS,ACQ)</code>. </li>
</ul>

===Defining the partners===

Before a SOUL request can transfer control to either CICS or SNA Communications Server, you must define a partner process (CICS program or SNA Communications Server application) for reference by SOUL statements.
Define the partner and its attributes with the <var>[[DEFINE LINK command: Transfer Control|DEFINE LINK]]</var>, <var>[[DEFINE PROCESSGROUP command: Transfer Control|DEFINE PROCESSGROUP]]</var>, and <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> commands. These commands connect the process to a link, identify the communication protocol to be used with the partner process, and define the partner process. 

In addition, the link defined by the <var>DEFINE LINK</var> command must be enabled with the <var>[[OPEN LINK command|OPEN LINK]]</var> command. 

===Transferring to CICS===

The CICS partner process must be a CICS program defined to CICS. 

After the SOUL <var>TRANSFER</var> statement completes successfully, the user is disconnected from <var class="product">Model 204</var> and transferred to the specified CICS partner process. 

Data passed to CICS via the <var>TRANSFER</var> statement <var>PASSING</var> clause is written to a Temporary Storage Queue named by combining the CICS user's terminal ID and the string <code>PSFS</code>. The CICS partner reads the data from the Temporary Storage Queue and processing continues according to the CICS program.

===Transferring to SNA Communications Server===

After the SOUL request containing the <var>TRANSFER</var> statement transfers the user to the destination region, and a session is established with the destination SNA Communications Server application, the user is notified that the session is established and is disconnected from <var class="product">Model 204</var>. Data passed in the transfer (for example, <var class="product">Model 204</var> commands) is acted upon in the destination application.

If SNA Communications Server fails to establish a session with the destination application, the user is notified that the session is not established. The user is not disconnected from <var class="product">Model 204</var>, and control returns to the request that contains the <var>TRANSFER</var> statement. 

The application transferred to is responsible for transferring the user back to the original region or to another SNA Communications Server application.

Proper login and handling of the passed command string requires coordination between the security options specified in the <var>DEFINE</var> commands and the <var>TRANSFER</var> statement.
Selection of these security options is discussed in [[Program communications facilities#Security for Model 204-to-Model 204 transfers|Security for Model 204-to-Model 204 transfers]].

[[Category:System Manager]]