HLI: Threads - Revision history

ELowell: /* Overview */

2016-07-15T22:54:33Z

Overview

← Older revision		Revision as of 22:54, 15 July 2016
Line 8:		Line 8:
	The total number of Model 204 threads available to connect users is set by the system administrator. The total number of available threads equals the number of IODEV statements specified in the Model 204 online run. A host language application must start at least one thread in order to access Model 204 and process against the database. </p>		The total number of Model 204 threads available to connect users is set by the system administrator. The total number of available threads equals the number of IODEV statements specified in the Model 204 online run. A host language application must start at least one thread in order to access Model 204 and process against the database. </p>
	<p>		<p>
	Refer to ~~the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var>~~ for information about IODEVs required for HLI threads. </p></li>		Refer to [[HLI: Job requirements]] for information about IODEVs required for HLI threads. </p></li>
	<li>		<li>
	The host language application initiates a request to start a connection to Model 204 by issuing a call to IFSTRT (or IFSTRTN) or IFDIAL (or IFDIALN). If a connection is available for the host language program, Model 204 starts the thread.</li>		The host language application initiates a request to start a connection to Model 204 by issuing a call to IFSTRT (or IFSTRTN) or IFDIAL (or IFDIALN). If a connection is available for the host language program, Model 204 starts the thread.</li>

ELowell: /* IFDIAL thread line-at-a-time interface */

2016-07-15T22:49:29Z

IFDIAL thread line-at-a-time interface

← Older revision		Revision as of 22:49, 15 July 2016
Line 314:		Line 314:
	<p class="note"><b>Note:</b> If you are using an IFDIAL thread, you must code the calls, specifications, and corresponding program logic that are valid for use with this thread. </p>		<p class="note"><b>Note:</b> If you are using an IFDIAL thread, you must code the calls, specifications, and corresponding program logic that are valid for use with this thread. </p>
	<p>		<p>
	~~Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual<~~/~~var>~~ for an example of an HLI application that uses an IFDIAL thread. Also ~~refer to that manual~~ for descriptions of HLI calls. </p>		See [[HLI: IFAM2/IFAM4 job program examples#IFDIAL thread example (z/OS)\|IFDIAL thread example (z/OS)]] for an example of an HLI application that uses an IFDIAL thread. Also see [[HLI: Function summary]] for descriptions of HLI calls. </p>
	===Starting an IFDIAL thread===		===Starting an IFDIAL thread===
	<p>		<p>

ELowell: /* Sample coding sequence for a multithreaded IFSTRT application */

2016-07-15T22:40:30Z

Sample coding sequence for a multithreaded IFSTRT application

← Older revision		Revision as of 22:40, 15 July 2016
Line 302:		Line 302:
	<p class="note"><b>Note:</b> To relate multiple records within the same file, you apply the same logic used to process records in separate files. </p>		<p class="note"><b>Note:</b> To relate multiple records within the same file, you apply the same logic used to process records in separate files. </p>
	<p>		<p>
	~~Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual<~~/~~var>~~ for a sample HLI application that uses multiple IFSTRT threads.</p>		See [[HLI: IFAM2/IFAM4 job program examples#Multithreaded (single_cursor) IFSTRT example\|Multithreaded (single cursor) IFSTRT example]] for a sample HLI application that uses multiple IFSTRT threads.</p>

	==IFDIAL thread line-at-a-time interface==		==IFDIAL thread line-at-a-time interface==
	<p>		<p>

ELowell: /* Starting a multiple cursor IFSTRT thread */

2016-07-15T22:33:06Z

Starting a multiple cursor IFSTRT thread

← Older revision		Revision as of 22:33, 15 July 2016
Line 169:		Line 169:
	</ul>		</ul>

	<p class="note"><b>Note:</b> In IFAM1, if you do not specify a thread type, the thread defaults to a single cursor IFSTRT thread (THRD-TYP is 0). ~~Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual<~~/~~var>~~ for a description of the IFSTRT call. </p>		<p class="note"><b>Note:</b> In IFAM1, if you do not specify a thread type, the thread defaults to a single cursor IFSTRT thread (THRD-TYP is 0). See [[IFSTRT (IFAM1) (HLI function)]] and [[IFSTRT (IFAM2/IFAM4) (HLI function)]] for a description of the IFSTRT call. </p>

	===Sample coding sequence===		===Sample coding sequence===

ELowell: /* Starting an IFDIAL thread */

2016-07-15T22:30:17Z

Starting an IFDIAL thread

← Older revision		Revision as of 22:30, 15 July 2016
Line 316:		Line 316:
	===Starting an IFDIAL thread===		===Starting an IFDIAL thread===
	<p>		<p>
	To start an IFDIAL thread, you must specify the IFDIAL call in your host language program. For example, the following COBOL statement starts an IFDIAL thread: </p>		To start an IFDIAL thread, you must specify the <var>[[IFDIAL (HLI function)\|IFDIAL]]</var> call in your host language program. For example, the following COBOL statement starts an IFDIAL thread: </p>
	<p class="code">CALL "IFDIAL" USING RETCODE,LANG-IND.</p>		<p class="code">CALL "IFDIAL" USING RETCODE,LANG-IND.</p>
	<p>		<p>
	where the following variable is specified in the WORKING-STORAGE SECTION of the program: </p>		where the following variable is specified in the WORKING-STORAGE SECTION of the program: </p>
	<p class="code">LANG-IND is 2 (COBOL) </p>		<p class="code">LANG-IND is 2 (COBOL) </p>
	~~<p>~~
	~~Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for a description of the IFDIAL call. </p>~~
	===Sample coding sequence===		===Sample coding sequence===
	<p>		<p>

ELowell: /* Different types of IFSTRT threads */

2016-07-15T22:28:21Z

Different types of IFSTRT threads

← Older revision		Revision as of 22:28, 15 July 2016
Line 55:		Line 55:
	Each IFSTRT thread supports one type of functionality. You must code only the calls, specifications, and corresponding program logic that are valid for the particular type of IFSTRT thread that you start. </p>		Each IFSTRT thread supports one type of functionality. You must code only the calls, specifications, and corresponding program logic that are valid for the particular type of IFSTRT thread that you start. </p>
	<p>		<p>
	For example, the call that opens a cursor, IFOCUR, is valid only on a multiple cursor IFSTRT thread; a particular updating call, IFPUT, is valid only on a single cursor IFSTRT thread with update privileges. ~~Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var>~~ for a description of individual calls.</p>		For example, the call that opens a cursor, IFOCUR, is valid only on a multiple cursor IFSTRT thread; a particular updating call, IFPUT, is valid only on a single cursor IFSTRT thread with update privileges. See [[HLI: Function summary]] for a description of individual calls.</p>

	==Comparison of multiple and single cursor IFSTRT threads==		==Comparison of multiple and single cursor IFSTRT threads==

ELowell: /* For more information */

2016-07-15T22:27:11Z

For more information

← Older revision		Revision as of 22:27, 15 July 2016
Line 18:		Line 18:
	<li>		<li>
	Read the section [[#Multiple cursor IFSTRT threads\|Multiple cursor IFSTRT threads]] if you are using multiple cursor functionality in your host language program for the first time. </li>		Read the section [[#Multiple cursor IFSTRT threads\|Multiple cursor IFSTRT threads]] if you are using multiple cursor functionality in your host language program for the first time. </li>
	<li>~~Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for~~ examples of HLI applications that use different types of threads and for information about IFAM1, IFAM2, and IFAM4.</li>		<li>For examples of HLI applications that use different types of threads and for information about IFAM1, IFAM2, and IFAM4, see [[HLI: Job design factors]] and [[HLI: IFAM2/IFAM4 job program examples]].</li>
	</ul>		</ul>

	==Types of threads: IFSTRT and IFDIAL==		==Types of threads: IFSTRT and IFDIAL==
	<p>		<p>

ELowell at 16:30, 29 April 2016

2016-04-29T16:30:48Z

← Older revision		Revision as of 16:30, 29 April 2016
Line 359:		Line 359:

	==See also==		==See also==
	{{Template: HLI topic list}}		{{Template: HLI programming topic list}}

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

ELowell: /* Multithreaded IFSTRT application */

2016-01-30T00:17:01Z

Multithreaded IFSTRT application

← Older revision		Revision as of 00:17, 30 January 2016
Line 269:		Line 269:
	Update units must begin and end on the same thread. If using IFDTHRD, assure that any in-progress update unit ends on the current thread by issuing an IFCMMT or IFCMTR on the current thread before the IFDTHRD call. </p>		Update units must begin and end on the same thread. If using IFDTHRD, assure that any in-progress update unit ends on the current thread by issuing an IFCMMT or IFCMTR on the current thread before the IFDTHRD call. </p>
	<p>		<p>
	See [[HLI ~~transactions~~]] for information about a multithreaded transaction. </p>		See [[HLI: Transactions]] for information about a multithreaded transaction. </p>

	===Sample coding sequence for a multithreaded IFSTRT application===		===Sample coding sequence for a multithreaded IFSTRT application===

ELowell: /* Types of threads: IFSTRT and IFDIAL */

2016-01-30T00:16:34Z

Types of threads: IFSTRT and IFDIAL

← Older revision		Revision as of 00:16, 30 January 2016
Line 28:		Line 28:
	The functionality of IFSTRT and IFDIAL threads is described in the following sections. </p>		The functionality of IFSTRT and IFDIAL threads is described in the following sections. </p>

	<p class="note"><b>Note:</b> In IFAM2 under z/OS or z/VSE, you can elect to start both types of threads in a host language job; however, IFDIAL and IFSTRT threads function independently of one another as separate transactions. See [[HLI ~~transactions~~]] for a description of HLI threads and Model 204 transactions in IFAM1, IFAM2, and IFAM4.</p>		<p class="note"><b>Note:</b> In IFAM2 under z/OS or z/VSE, you can elect to start both types of threads in a host language job; however, IFDIAL and IFSTRT threads function independently of one another as separate transactions. See [[HLI: Transactions]] for a description of HLI threads and Model 204 transactions in IFAM1, IFAM2, and IFAM4.</p>

	==IFSTRT threads==		==IFSTRT threads==