HLI: Job design factors - Revision history

JAL: /* Recovery considerations for single and multicursor IFAM2 threads */ typo

2017-11-29T21:59:29Z

Recovery considerations for single and multicursor IFAM2 threads: typo

← Older revision		Revision as of 21:59, 29 November 2017
Line 126:		Line 126:
	===Recovery considerations for single and multicursor IFAM2 threads===		===Recovery considerations for single and multicursor IFAM2 threads===
	<p>		<p>
	Single cursor IFAM update threads differ from SOUL and multicursor IFAM threads in that the single cursor threads start an update unit during their IFSTRTN call and end the update unit when IFFNSH is issued. This means that with single cursor IFAM threads active, all transaction checkpoints fail--meaning: time-out. For these threads, you must use IFCHKPT calls to end single cursor update units, wait for a transaction checkpoint attempt, and then start new single cursor update units.</p>		Single cursor IFAM update threads differ from SOUL and multicursor IFAM threads in that the single cursor threads start an update unit during their IFSTRTN call and end the update unit when IFFNSH is issued. This means that with single cursor IFAM threads active, all transaction checkpoints fail — meaning: time-out. For these threads, you must use IFCHKPT calls to end single cursor update units, wait for a transaction checkpoint attempt, and then start new single cursor update units.</p>
	<p>		<p>
	Multicursor IFAM, like SOUL, starts an update unit at the first file update and ends the update unit at update commit (IFCMMT ccall in IFAM). Therefore, multicursor IFAM threads do not require IFCHKPT calls to let a transaction checkpoint proceed, although they may issue IFCHKPT calls to initiate transaction checkpoint attempts or query transaction checkpoint status.</p>		Multicursor IFAM, like SOUL, starts an update unit at the first file update and ends the update unit at update commit (IFCMMT ccall in IFAM). Therefore, multicursor IFAM threads do not require IFCHKPT calls to let a transaction checkpoint proceed, although they may issue IFCHKPT calls to initiate transaction checkpoint attempts or query transaction checkpoint status.</p>

JAL: /* Processing in different Model 204 environments */ minor formatting

2017-04-03T19:02:08Z

Processing in different Model 204 environments: minor formatting

← Older revision		Revision as of 19:02, 3 April 2017
Line 10:		Line 10:
	==Processing in different Model 204 environments==		==Processing in different Model 204 environments==
	<p>		<p>
	~~[[#~~Summary of HLI processing environments~~\|Summary of HLI processing environments]]~~ summarizes host language application program processing in the different Model 204 environments. </p>		The "Summary of HLI processing environments" table summarizes host language application program processing in the different Model 204 environments: </p>
	<table>		<table>
	<p class="caption">Summary of HLI processing environments</p>		<p class="caption">Summary of HLI processing environments</p>
Line 19:		Line 19:
	<th>IFAM4</th>		<th>IFAM4</th>
	</tr>		</tr>

	<tr>		<tr>
	<td>Operating system</td>		<td>Operating system</td>
Line 25:		Line 26:
	<td>z/OS</td>		<td>z/OS</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Teleprocessing monitors</td>		<td>Teleprocessing monitors</td>
	<td>--</td>		<td>--</td>
	<td>CICS INTERCOMM</td>		<td>CICS, INTERCOMM</td>
	<td>--</td>		<td>--</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Model 204 copy</td>		<td>Model 204 copy</td>
Line 37:		Line 40:
	<td>Private</td>		<td>Private</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Threads</td>		<td>Threads</td>
Line 43:		Line 47:
	<td>Multiple</td>		<td>Multiple</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Protocol</td>		<td>Protocol</td>
Line 52:		Line 57:
	IFSTRT</td>		IFSTRT</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Enqueuing, with other application programs</td>		<td>Enqueuing, with other application programs</td>
	<td>File</td>		<td>File</td>
	<td>Record, with those sharing Model 204</td>		<td>Record, with those sharing Model 204</td>
	<td>File</td>		<td>File</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Recovery</td>		<td>Recovery</td>
Line 65:		Line 72:
	<td>RESTART</td>		<td>RESTART</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Performance</td>		<td>Performance</td>

JAL: /* IFAM2 */ add link

2017-04-03T14:50:09Z

IFAM2: add link

← Older revision		Revision as of 14:50, 3 April 2017
Line 141:		Line 141:

	<p class="note"><b>Note:</b> A batch utility program, BATCH2, is provided by Rocket for use in the IFAM2 environment. For information about the BATCH2 utility, see [[Program_Communication_facilities#BATCH2_facility\|BATCH2 facility]].</p>		<p class="note"><b>Note:</b> A batch utility program, BATCH2, is provided by Rocket for use in the IFAM2 environment. For information about the BATCH2 utility, see [[Program_Communication_facilities#BATCH2_facility\|BATCH2 facility]].</p>

			For more information about IFAM2, see [[#IFAM2 configurations\|IFAM2 configurations]], below.

	===IFAM4===		===IFAM4===

ELowell: /* IFSTRT and IFDIAL protocols */

2016-07-11T17:02:49Z

IFSTRT and IFDIAL protocols

← Older revision		Revision as of 17:02, 11 July 2016
Line 84:		Line 84:
	To use IFSTRT protocols, you start an IFSTRT thread (by coding an IFSTRT or IFTSTRTN call in your HLI application). To use IFDIAL protocols, you start an IFDIAL thread (by coding an IFDIAL or IFDIALN call). The functionality that is available using a particular thread is determined by the type of protocol that it uses. </p>		To use IFSTRT protocols, you start an IFSTRT thread (by coding an IFSTRT or IFTSTRTN call in your HLI application). To use IFDIAL protocols, you start an IFDIAL thread (by coding an IFDIAL or IFDIALN call). The functionality that is available using a particular thread is determined by the type of protocol that it uses. </p>
	<p>		<p>
	See [[~~:Category:~~ HLI ~~functions~~\|HLI ~~functions~~]] ~~for descriptions of the IFSTRT~~ and IFDIAL ~~calls~~. For more information about coding applications using the two protocols, see [[HLI: Threads]]. </p>		See the [[IFSTRT (IFAM1) (HLI function)\|IFSTRT (IFAM1)]], [[IFSTRT (IFAM2/IFAM4) (HLI function)\|IFSTRT (IFAM2/IFAM4)]], and [[IFDIAL (HLI function)\|IFDIAL]] pages for details. For more information about coding applications using the two protocols, see [[HLI: Threads]]. </p>

	===IFDIAL thread===		===IFDIAL thread===

ELowell at 16:58, 11 July 2016

2016-07-11T16:58:32Z

← Older revision		Revision as of 16:58, 11 July 2016
Line 84:		Line 84:
	To use IFSTRT protocols, you start an IFSTRT thread (by coding an IFSTRT or IFTSTRTN call in your HLI application). To use IFDIAL protocols, you start an IFDIAL thread (by coding an IFDIAL or IFDIALN call). The functionality that is available using a particular thread is determined by the type of protocol that it uses. </p>		To use IFSTRT protocols, you start an IFSTRT thread (by coding an IFSTRT or IFTSTRTN call in your HLI application). To use IFDIAL protocols, you start an IFDIAL thread (by coding an IFDIAL or IFDIALN call). The functionality that is available using a particular thread is determined by the type of protocol that it uses. </p>
	<p>		<p>
	See [[HLI~~: Function calls~~]] for descriptions of the IFSTRT and IFDIAL calls. For more information about coding applications using the two protocols, see [[HLI: Threads]]. </p>		See [[:Category: HLI functions\|HLI functions]] for descriptions of the IFSTRT and IFDIAL calls. For more information about coding applications using the two protocols, see [[HLI: Threads]]. </p>

	===IFDIAL thread===		===IFDIAL thread===
Line 313:		Line 313:
	</ul>		</ul>
	<p>		<p>
	See [[HLI~~: Function calls~~]] for information about individual calls and their usage. </p>		See [[:Category:HLI functions\|HLI functions]] for information about individual calls and their usage. </p>
	==See also==		==See also==
	{{Template: HLI reference topic list}}		{{Template: HLI reference topic list}}

	[[Category: Host Language Interface]]		[[Category: Host Language Interface]]

ELowell at 21:36, 2 May 2016

2016-05-02T21:36:10Z

← Older revision		Revision as of 21:36, 2 May 2016
Line 314:		Line 314:
	<p>		<p>
	See [[HLI: Function calls]] for information about individual calls and their usage. </p>		See [[HLI: Function calls]] for information about individual calls and their usage. </p>
			==See also==
			{{Template: HLI reference topic list}}

	[[Category: Host Language Interface]]		[[Category: Host Language Interface]]

ELowell: /* Logical view of IFAM4 under z/OS */

2016-04-25T20:19:10Z

Logical view of IFAM4 under z/OS

← Older revision		Revision as of 20:19, 25 April 2016
Line 256:		Line 256:

	<p class="caption" style="width:360px">IFAM4 under z/OS</p>		<p class="caption" style="width:360px">IFAM4 under z/OS</p>
	<p class="figure">[[File:HLI_Ref_ch2_5.png]] </p>		<p class="figure">[[File:HLI_Ref_ch2_5.png\|360px]] </p>

	==Converting HLI applications for different environments==		==Converting HLI applications for different environments==

ELowell: /* IFAM1 under CMS */

2016-04-25T20:16:02Z

IFAM1 under CMS

← Older revision		Revision as of 20:16, 25 April 2016
Line 199:		Line 199:
	<div id="IFAM1_CMS"></div>		<div id="IFAM1_CMS"></div>
	<p class="caption" style="width:320px">IFAM1 under CMS</p>		<p class="caption" style="width:320px">IFAM1 under CMS</p>
	<p class="figure">[[File:HLI_Ref_ch2_2.png]] </p>		<p class="figure">[[File:HLI_Ref_ch2_2.png\|300px]] </p>

	==IFAM2 configurations==		==IFAM2 configurations==

ELowell: /* IFAM1 under z/OS and VSE */

2016-04-25T20:14:31Z

IFAM1 under z/OS and VSE

← Older revision		Revision as of 20:14, 25 April 2016
Line 190:		Line 190:

	<p class="caption" style="width:330px">IFAM1 under z/OS and VSE</p>		<p class="caption" style="width:330px">IFAM1 under z/OS and VSE</p>
	<p class="figure">[[File:HLI_Ref_ch2_1.png]] </p>		<p class="figure">[[File:HLI_Ref_ch2_1.png\|300px]] </p>

	===IFAM1 under CMS ===		===IFAM1 under CMS ===

ELowell: /* Logical view of IFAM4 under z/OS */

2016-04-25T20:10:58Z

Logical view of IFAM4 under z/OS

← Older revision		Revision as of 20:10, 25 April 2016
Line 255:		Line 255:
	The following figure shows the logical view of the IFAM4 processing environment for an HLI application running under z/OS.</p>		The following figure shows the logical view of the IFAM4 processing environment for an HLI application running under z/OS.</p>

	<p class="caption" style="width:~~468px~~">IFAM4 under z/OS</p>		<p class="caption" style="width:360px">IFAM4 under z/OS</p>
	<p class="figure">[[File:HLI_Ref_ch2_5.png]] </p>		<p class="figure">[[File:HLI_Ref_ch2_5.png]] </p>