Program Communication facilities - Revision history

JAL: /* Input and output data streams */ add "Managing DCBLRECL to avoid an ABEND" (was on "Using HLI and batch configurations" page)

2018-06-19T21:32:51Z

Input and output data streams: add "Managing DCBLRECL to avoid an ABEND" (was on "Using HLI and batch configurations" page)

← Older revision		Revision as of 21:32, 19 June 2018
Line 2,708:		Line 2,708:
	<p>		<p>
	Because BATCH2 emulates a line-by-line terminal, the values of the User 0 parameters <var>[[OUTMRL parameter\|OUTMRL]]</var> and <var>[[OUTCCC parameter\|OUTCCC]]</var> for this thread determine, respectively, the maximum length of the output line and the continuation character position.</p>		Because BATCH2 emulates a line-by-line terminal, the values of the User 0 parameters <var>[[OUTMRL parameter\|OUTMRL]]</var> and <var>[[OUTCCC parameter\|OUTCCC]]</var> for this thread determine, respectively, the maximum length of the output line and the continuation character position.</p>

			====Managing DCBLRECL to avoid an ABEND====
			<p>
			If a BATCH2 job sends a line to CCAOUT that is longer than the DCBLRECL defined for CCAOUT, the line will be truncated at <code>DCBLRECL-4</code> length to avoid an S002-18 abend. This only occurs for RECFM=V data sets. The following message will be issued for each line that exceeds the DCBLRECL length:</p>
			<p class="code">M204ULIF.0009: PREVIOUS CCAOUT LINE LONGER THAN DCBLRECL-4; LINE TRUNCATED </p>
			<p>
			To avoid the error, specify <code>RESET OUTCCC</code> to a value less than <code>DCBLRECL-4</code>, or increase DCBLRECL for CCAOUT.</p>

	====Using *DEVICE command in BATCH2 jobs====		====Using *DEVICE command in BATCH2 jobs====
Line 2,731:		Line 2,738:
	<p>		<p>
	You do<var> not</var> need to be logged in to issue this command. </p>		You do<var> not</var> need to be logged in to issue this command. </p>

	===z/OS JCL using BATCH2===		===z/OS JCL using BATCH2===
	<p>		<p>

JAL: /* BATCH2 facility */ minor formatting

2018-06-19T21:17:01Z

BATCH2 facility: minor formatting

← Older revision		Revision as of 21:17, 19 June 2018
Line 2,556:		Line 2,556:
	<tr>		<tr>
	<td>Completes normally </td>		<td>Completes normally </td>
	<td>		<td>Highest return code received by the user of the BATCH2 thread.
	~~<p>~~
	Highest return code received by the user of the BATCH2 thread. ~~</p>~~
	<p>		<p>
	Unlike in a single user job, this value is independent of the highest return code value for the entire Online job. </p>		Unlike in a single user job, this value is independent of the highest return code value for the entire Online job. </p>
	<p>		<p>
	When invoking BATCH2, the job-step or exec specifies the type of return code to return: a batch or Online value.</p>		When invoking BATCH2, the job-step or exec specifies the type of return code to return: a batch or Online value.</p></td>
	</td>
	</tr>		</tr>

	<tr>		<tr>
	<td nowrap>Terminates abnormally </td>		<td nowrap>Terminates abnormally </td>
	<td>Same completion codes as in previous releases, 300 or 600. These are return codes for the BATCH2 job itself and are not user values.</td>		<td>Same completion codes as in previous releases, 300 or 600. These are return codes for the BATCH2 job itself and are not user values. </td>
	</tr>		</tr>
	</table>		</table>

JAL: /* BATCH2 completion codes */ minor formatting

2018-06-19T21:12:19Z

BATCH2 completion codes: minor formatting

← Older revision		Revision as of 21:12, 19 June 2018
Line 2,955:		Line 2,955:

	<tr>		<tr>
	<td ~~align="right"~~>0</td>		<td>0</td>
	<td>Successful completion</td>		<td>Successful completion</td>
	</tr>		</tr>

	<tr>		<tr>
	<td ~~align="right"~~>300</td>		<td>300</td>
	<td>		<td>Abnormal termination. Refer to CCAOUT for an error message.
	~~<p>~~
	Abnormal termination. Refer to CCAOUT for an error message.~~</p>~~
	<p>		<p>
	If a completion code of 300 is returned, an error message appears in the		If a completion code of 300 is returned, an error message appears in the
Line 2,972:		Line 2,970:
	Invalid OMC parameter value.</p>		Invalid OMC parameter value.</p>
	<p>		<p>
	CCAIN data stream could not be opened.</p>		CCAIN data stream could not be opened.</p></td>
	</td>
	</tr>		</tr>

	<tr>		<tr>
	<td ~~align="right"~~>600</td>		<td>600</td>
	<td>The CCAOUT data stream could not be opened.</td>		<td>The CCAOUT data stream could not be opened.</td>
	</tr>		</tr>

ELowell: /* Requirements for using CMS TPROCESS */

2017-10-26T19:22:53Z

Requirements for using CMS TPROCESS

← Older revision		Revision as of 19:22, 26 October 2017
Line 1,180:		Line 1,180:
	<p>		<p>
	Many CMS commands that an EXEC can call run in the User Area. These commands would overlay the interface module if it also ran in the User Area, causing unpredictable results. </p>		Many CMS commands that an EXEC can call run in the User Area. These commands would overlay the interface module if it also ran in the User Area, causing unpredictable results. </p>
	~~<p>~~
	See the description of the M204 EXEC in the <var class="book">[http://www.rocketsoftware.com/m204/products/model204/documentation/v7r4/M204-System-Mgr/view Rocket Model 204 System Manager's Guide]</var> for more information about invoking the user interface module. </p>

	==CMS TPROCESS subcommands==		==CMS TPROCESS subcommands==
	<p>		<p>

JAL: add link

2017-10-19T23:39:51Z

add link

← Older revision		Revision as of 23:39, 19 October 2017
Line 12:		Line 12:
	===Horizon===		===Horizon===
	<p>		<p>
	<var class="product">Model 204</var> also offers, as an optional feature, its distributed application facility, Horizon, which supports the LU 6.2 protocol of IBM's Systems Network Architecture (SNA). Horizon allows <var class="product">Model 204</var> applications to participate in program-to-program processing by communicating through SNA Communications Server with one or more other programs. Communication takes place over an SNA network, using verbs and protocols conforming to LU 6.2 architecture. Horizon uses ~~User Language~~ statements and <var class="product">Model 204</var> commands.</p>		<var class="product">Model 204</var> also offers, as an optional feature, its distributed application facility, Horizon, which supports the LU 6.2 protocol of IBM's Systems Network Architecture (SNA). Horizon, [[#HorizonMain\|described in greater detail later on this page]], allows <var class="product">Model 204</var> applications to participate in program-to-program processing by communicating through SNA Communications Server with one or more other programs. 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.</p>

	===BATCH2===		===BATCH2===
Line 2,440:		Line 2,440:
	Since the transfer to M204B is to a non-trusted <var class="product">Model 204</var> Online, the LINK and PROCESSGROUP definitions for that Online are not necessary. The PROCESS definition for that Online is optional unless a transfer out of that Online is anticipated. </p>		Since the transfer to M204B is to a non-trusted <var class="product">Model 204</var> Online, the LINK and PROCESSGROUP definitions for that Online are not necessary. The PROCESS definition for that Online is optional unless a transfer out of that Online is anticipated. </p>

	==Horizon==		==<b id="HorizonMain"></b>Horizon==
	<p>		<p>
	This section provides a brief overview of the optional distributed application facility, Horizon, and the User Language statements that support it.		This section provides a brief overview of the optional distributed application facility, Horizon, and the User Language statements that support it.

JAL: link repair

2017-08-21T21:22:14Z

link repair

← Older revision		Revision as of 21:22, 21 August 2017
Line 116:		Line 116:
	<p>		<p>
	After the CLOSE PROCESS statement is issued, the request can resume output to the terminal if the output was suppressed by the OPEN PROCESS statement. </p>		After the CLOSE PROCESS statement is issued, the request can resume output to the terminal if the output was suppressed by the OPEN PROCESS statement. </p>
	<p class="note"><b>Note:</b> The syntax for this statement with Horizon varies slightly; see the [[Horizon SOUL interface#CLOSE PROCESS ~~Statement~~\|Horizon syntax]].</p>		<p class="note"><b>Note:</b> The syntax for this statement with Horizon varies slightly; see the [[Horizon SOUL interface#CLOSE PROCESS statement\|Horizon syntax]].</p>

	===OPEN PROCESS statement===		===OPEN PROCESS statement===
Line 139:		Line 139:
	If TERMINAL=LOCAL is specified, the terminal is assumed to be under control of the User Language request, and the partner program should not write to it. </p>		If TERMINAL=LOCAL is specified, the terminal is assumed to be under control of the User Language request, and the partner program should not write to it. </p>

	<p class="note"><b>Note:</b> The syntax for this statement with Horizon varies slightly; see the [[Horizon SOUL interface#OPEN PROCESS ~~Statement~~\|Horizon syntax]].</p>		<p class="note"><b>Note:</b> The syntax for this statement with Horizon varies slightly; see the [[Horizon SOUL interface#OPEN PROCESS statement\|Horizon syntax]].</p>

	===RECEIVE statement===		===RECEIVE statement===
Line 191:		Line 191:
	</ul>		</ul>

	<p class="note"><b>Note:</b> The syntax for this statement with Horizon varies slightly; see the [[Horizon SOUL interface#Receive ~~Statement~~\|Horizon syntax]].</p>		<p class="note"><b>Note:</b> The syntax for this statement with Horizon varies slightly; see the [[Horizon SOUL interface#Receive statement\|Horizon syntax]].</p>

	===SEND statement===		===SEND statement===
Line 225:		Line 225:
	Truncation occurs and a warning message is issued if the data being sent exceeds the length (that is, the value of the DATALEN option) specified on the DEFINE PROCESS command. </p>		Truncation occurs and a warning message is issued if the data being sent exceeds the length (that is, the value of the DATALEN option) specified on the DEFINE PROCESS command. </p>

	<p class="note"><b>Note:</b> The syntax for this statement with Horizon varies slightly; see the [[Horizon SOUL interface#Send ~~Statement~~\|Horizon syntax]].</p>		<p class="note"><b>Note:</b> The syntax for this statement with Horizon varies slightly; see the [[Horizon SOUL interface#Send statement\|Horizon syntax]].</p>

	===SIGNAL PROCESS statement===		===SIGNAL PROCESS statement===
Line 249:		Line 249:
	The SIGNAL PROCESS statement causes the next communication attempted by the partner process to be suppressed, and to return an indication that the signal occurred with the value sent by the SIGNAL PROCESS statement. </p>		The SIGNAL PROCESS statement causes the next communication attempted by the partner process to be suppressed, and to return an indication that the signal occurred with the value sent by the SIGNAL PROCESS statement. </p>

	<p class="note"><b>Note:</b> The syntax for this statement with Horizon varies slightly; see the [[Horizon SOUL interface#SIGNAL PROCESS ~~Statement~~\|Horizon syntax]].</p>		<p class="note"><b>Note:</b> The syntax for this statement with Horizon varies slightly; see the [[Horizon SOUL interface#SIGNAL PROCESS statement\|Horizon syntax]].</p>

	===Error handling for TPROCESS statements===		===Error handling for TPROCESS statements===
	<p>		<p>

ELowell: /* CMS partner */ - fixed one special character that had gotten changed

2017-04-11T16:59:23Z

CMS partner: - fixed one special character that had gotten changed

← Older revision		Revision as of 16:59, 11 April 2017
Line 1,581:		Line 1,581:
	qd = queued()		qd = queued()
	'EXECIO * DISKR' fileid'(FIFO FINIS'		'EXECIO * DISKR' fileid'(FIFO FINIS'
	if rc �= 0 then call exit 'reading CMS file' fileid		if rc ¬= 0 then call exit 'reading CMS file' fileid

	/* Send the records to User Language: */		/* Send the records to User Language: */

ELowell: /* User access protection */ - typo

2017-04-11T16:33:29Z

User access protection: - typo

← Older revision		Revision as of 16:33, 11 April 2017
Line 2,009:		Line 2,009:
	For more information about login privileges, see the login security description in		For more information about login privileges, see the login security description in
	[[DEFINE PROCESSGROUP command: Transfer Control]]		[[DEFINE PROCESSGROUP command: Transfer Control]]
	and see [[Model 204 security features#Subsystem_security\|~~Subsystem_security~~]]. </p>		and see [[Model 204 security features#Subsystem_security\|Subsystem security]]. </p>
	<p class="note"><b>Note:</b> Only ACF2 is supported for Trusted Login; Security Server (formerly RACF) and Top Secret are not. Also, Guest User is not supported for SNA Communications Server Transfer Control. </p>		<p class="note"><b>Note:</b> Only ACF2 is supported for Trusted Login; Security Server (formerly RACF) and Top Secret are not. Also, Guest User is not supported for SNA Communications Server Transfer Control. </p>
	<p>		<p>
	You can optionally include a password in the data passed in a transfer where both sides have LOGIN=TRUST. However, such a transfer thereby becomes non-trusted. The password is checked at the receiving side and the user is processed according to normal <var class="product">Model 204</var> login security. Non-trusted transfers between <var class="product">Model 204</var> Onlines always require that a valid password be supplied to the receiving side. </p>		You can optionally include a password in the data passed in a transfer where both sides have LOGIN=TRUST. However, such a transfer thereby becomes non-trusted. The password is checked at the receiving side and the user is processed according to normal <var class="product">Model 204</var> login security. Non-trusted transfers between <var class="product">Model 204</var> Onlines always require that a valid password be supplied to the receiving side. </p>

	====System-level protection====		====System-level protection====
	<p>		<p>

JALWiccan: Automatically generated page update

2017-04-07T21:27:05Z

Automatically generated page update

← Older revision		Revision as of 21:27, 7 April 2017
Line 1,581:		Line 1,581:
	qd = queued()		qd = queued()
	'EXECIO * DISKR' fileid'(FIFO FINIS'		'EXECIO * DISKR' fileid'(FIFO FINIS'
	if rc ¬= 0 then call exit 'reading CMS file' fileid		if rc �= 0 then call exit 'reading CMS file' fileid

	/* Send the records to User Language: */		/* Send the records to User Language: */
Line 2,009:		Line 2,009:
	For more information about login privileges, see the login security description in		For more information about login privileges, see the login security description in
	[[DEFINE PROCESSGROUP command: Transfer Control]]		[[DEFINE PROCESSGROUP command: Transfer Control]]
	and see [[~~Security~~#Subsystem_security\|Subsystem_security]]. </p>		and see [[Model 204 security features#Subsystem_security\|Subsystem_security]]. </p>
	<p class="note"><b>Note:</b> Only ACF2 is supported for Trusted Login; Security Server (formerly RACF) and Top Secret are not. Also, Guest User is not supported for SNA Communications Server Transfer Control. </p>		<p class="note"><b>Note:</b> Only ACF2 is supported for Trusted Login; Security Server (formerly RACF) and Top Secret are not. Also, Guest User is not supported for SNA Communications Server Transfer Control. </p>
	<p>		<p>

Admin: typo

2017-03-24T21:24:11Z

typo

← Older revision		Revision as of 21:24, 24 March 2017
Line 2,764:		Line 2,764:
	Where:		Where:
	<ul>		<ul>
	<li><var class="term">subsysname</var> is the zOS subsystem that Batch2 will use to communicate with the XDM task in order to make an IFDIAL connection. If subsysname is not specified, in which case the : would also be removed, then the subsysname would be picked up from the ~~cram~~ IGCLM244 module that the BATCH2 program loads. </li>		<li><var class="term">subsysname</var> is the zOS subsystem that Batch2 will use to communicate with the XDM task in order to make an IFDIAL connection. If subsysname is not specified, in which case the : would also be removed, then the subsysname would be picked up from the CRAM IGCLM244 module that the BATCH2 program loads. </li>

	<li><var class="term">channel</var> is the Online region channel name. If channel is not specified, the name defaults to M204PROD. </li>		<li><var class="term">channel</var> is the Online region channel name. If channel is not specified, the name defaults to M204PROD. </li>