HLI: Job requirements - Revision history

JAL: /* IFAM2 jobs */ add `s`

2017-04-03T20:02:45Z

IFAM2 jobs: add <var>s

← Older revision		Revision as of 20:02, 3 April 2017
Line 401:		Line 401:
	IFAM2 jobs can run under z/OS, VSE, or CMS. </p>		IFAM2 jobs can run under z/OS, VSE, or CMS. </p>
	<p>		<p>
	Except for IFDIAL under CMS, an IFAM2 job can establish multiple threads. Under z/OS and VSE, an IFAM2 job can start one or more IFSTRT threads and one IFDIAL thread. Under CMS, a IFAM2 job can start either an IFSTRT thread (or threads) or an IFDIAL thread.</p>		Except for <var>IFDIAL</var> under CMS, an IFAM2 job can establish multiple threads. Under z/OS and VSE, an IFAM2 job can start one or more <var>IFSTRT</var> threads and one <var>IFDIAL</var> thread. Under CMS, an IFAM2 job can start either an <var>IFSTRT</var> thread (or threads) or an <var>IFDIAL</var> thread.</p>
	<p>		<p>
	The Model 204 service program operates in its own region or virtual machine. The region processes requests from an arbitrary number of host language programs, each of which operates in its own region or virtual machine. IFAM2 requires the use of communications facilities.</p>		The Model 204 service program operates in its own region or virtual machine. The region processes requests from an arbitrary number of host language programs, each of which operates in its own region or virtual machine. IFAM2 requires the use of communications facilities.</p>
Line 411:		Line 411:
	For CMS, a host language program communicates with Model 204 in a separate virtual machine through the IBM inter-user communication vehicle (IUCV). </p>		For CMS, a host language program communicates with Model 204 in a separate virtual machine through the IBM inter-user communication vehicle (IUCV). </p>
	<p>		<p>
	See the next section for specific information about the subsystem name, channel names and IODEV settings that are used for IFAM2 jobs running under z/OS, VSE, and CMS. </p>		See the next section for specific information about the subsystem name, channel names and <var>IODEV</var> settings that are used for IFAM2 jobs running under z/OS, VSE, and CMS. </p>

	===Subsystem names, channel names, and IODEV settings===		===Subsystem names, channel names, and IODEV settings===
Line 417:		Line 417:
	Model 204 uses the following subsystem names, channel names, and <var>[[IODEV parameter\|IODEV]]</var> settings for IFAM2 threads: </p>		Model 204 uses the following subsystem names, channel names, and <var>[[IODEV parameter\|IODEV]]</var> settings for IFAM2 threads: </p>
	<ul>		<ul>
	<li>For IFSTRT threads, Model 204 uses the default channel name supplied by Rocket. </li>		<li>For <var>IFSTRT</var> threads, Model 204 uses the default channel name supplied by Rocket. </li>

	<li>For IFSTRTN threads, Model 204 uses the channel name that is specified in the HLI call. </li>		<li>For <var>IFSTRTN</var> threads, Model 204 uses the channel name that is specified in the HLI call. </li>

	<li>For IFSTRTN threads and z/OS with [[Defining the user environment (CCAIN)#CRAM options for z/OS\|CRAM-XDM]], Model 204 uses the default [[Defining the user environment (CCAIN)#cramssn\|subsystem name]] found in the IGCLM244 load module or the subsystem name found in the HLI, as well as the channel name in the HLI call.		<li>For <var>IFSTRTN</var> threads and z/OS with [[Defining the user environment (CCAIN)#CRAM options for z/OS\|CRAM-XDM]], Model 204 uses the default [[Defining the user environment (CCAIN)#cramssn\|subsystem name]] found in the IGCLM244 load module or the subsystem name found in the HLI, as well as the channel name in the HLI call.
	<p>		<p>
	The following default channel names and <var>IODEV</var> settings are used for IFSTRT threads:</p>		The following default channel names and <var>IODEV</var> settings are used for <var>IFSTRT</var> threads:</p>
	<table>		<table>
	<tr class="head">		<tr class="head">
Line 451:		Line 451:
	</li>		</li>

	<li>For IFDIAL threads, Model 204 uses the default channel name supplied by Rocket.</li>		<li>For <var>IFDIAL</var> threads, Model 204 uses the default channel name supplied by Rocket.</li>

	<li>For IFDIALN threads, Model 204 uses the channel name specified in the HLI call. </li>		<li>For <var>IFDIALN</var> threads, Model 204 uses the channel name specified in the HLI call. </li>

	<li>For IFDIALN threads and z/OS with XDM, Model 204 uses the default subsystem name found in the IGCLM244 load module or the subsystem name found in the HLI, as well as the channel name in the HLI call.		<li>For <var>IFDIALN</var> threads and z/OS with CRAM-XDM, Model 204 uses the default subsystem name found in the IGCLM244 load module or the subsystem name found in the HLI, as well as the channel name in the HLI call.
	<p>		<p>
	The following default channel names and IODEV settings are used for IFDIAL threads: </p>		The following default channel names and <var>IODEV</var> settings are used for <var>IFDIAL</var> threads: </p>
	<table>		<table>
	<tr class="head">		<tr class="head">
Line 485:		Line 485:
	</li>		</li>
	</ul>		</ul>
	<p class="note"><b>Note:</b> The <var>IODEV</var> settings listed above are the ones that are used by Model 204 for IFAM2 processing. You can specify <var>VMIOCHNL</var> and <var>VMIFCHNL</var> (and the corresponding ~~IODEVs~~) only for CMS. You can specify <var>CRIOCHNL</var> and <var>IFAMCHNL</var> (and the corresponding IODEVs) only for z/OS and VSE. </p>		<p class="note"><b>Note:</b> The <var>IODEV</var> settings listed above are the ones that are used by Model 204 for IFAM2 processing. You can specify <var>VMIOCHNL</var> and <var>VMIFCHNL</var> (and the corresponding <var>IODEV</var> values) only for CMS. You can specify <var>CRIOCHNL</var> and <var>IFAMCHNL</var> (and the corresponding IODEVs) only for z/OS and VSE. </p>
	<p>		<p>
	These threads must be defined in the Model 204 Online run to provide IFAM2 communications. One <var>IODEV</var> is required by Model 204 for each thread that is started in the HLI program. </p>		These threads must be defined in the Model 204 Online run to provide IFAM2 communications. One <var>IODEV</var> is required by Model 204 for each thread that is started in the HLI program. </p>

JAL: misc formatting

2017-02-27T21:04:42Z

misc formatting

Show changes

JAL: /* Using the STEPLIB statement */ add links

2017-01-30T20:30:09Z

Using the STEPLIB statement: add links

← Older revision		Revision as of 20:30, 30 January 2017
Line 147:		Line 147:
	<p class="note"><b>Note:</b> One of the following requirements must be met for IFAM1 applications:</p>		<p class="note"><b>Note:</b> One of the following requirements must be met for IFAM1 applications:</p>
	<ul>		<ul>
	<li>		<li>M204XSVC must be installed as an SVC, and that SVC number must be passed to Model 204 in the IFSTRT or IFLOG call as the value of the <var>[[XMEMSVC parameter\|XMEMSVC]]</var> parameter. <var>[[XMEMOPT parameter\|XMEMOPT]]</var> must also be set to 2 or 4.</li>
	M204XSVC must be installed as an SVC and that SVC number must be passed to Model 204 in the IFSTRT or IFLOG call as the value of the XMEMSVC parameter. XMEMOPT must also be set to 2 or 4~~, or~~</li>
	<li>		<li>The load library where the IFAM1 application resides (and all run-time concatenated libraries) must be APF authorized.</li>
	The load library where the IFAM1 application resides (and all run-time concatenated libraries) must be APF authorized.</li>
	</ul>		</ul>
	<p>		<p>
Line 156:		Line 155:
	<p class="code">MODEL 204 IS NOT AUTHORIZED FOR THIS CPUID: 0000000000000000</p>		<p class="code">MODEL 204 IS NOT AUTHORIZED FOR THIS CPUID: 0000000000000000</p>
	<p>		<p>
	Use the DSN of the Model 204 load library that is used to run IFAM1 programs at your site. If the Model 204 load module library and application load library are in separate libraries, use concatenated data set or file definition statements. </p>		Use the DSN of the Model 204 load library that is used to run IFAM1 programs at your site. If the Model 204 load module library and application load library are in separate libraries, use concatenated data set or file definition statements. </p>

	===Using the EXEC statement===		===Using the EXEC statement===

ELowell: /* Specifying Model 204 runtime parameters */

2016-07-11T19:46:31Z

Specifying Model 204 runtime parameters

← Older revision		Revision as of 19:46, 11 July 2016
Line 396:		Line 396:
	The IFAM1 application programmer can optionally specify Model 204 system and User 0 runtime parameters inside the application program using either the IFSTRT call, if the job starts an IFSTRT thread, or the IFSETUP call, if the job starts an IFDIAL thread. </p>		The IFAM1 application programmer can optionally specify Model 204 system and User 0 runtime parameters inside the application program using either the IFSTRT call, if the job starts an IFSTRT thread, or the IFSETUP call, if the job starts an IFDIAL thread. </p>
	<p>		<p>
	Note that there are other differences in coding calls when using either an IFSTRT or an IFDIAL thread. See ~~[[HLI: Function calls]]~~ for detailed descriptions of the IFSTRT (IFAM1) and IFSETUP calls. [[HLI: IFAM1 job program examples]] for sample IFAM1 applications. </p>		Note that there are other differences in coding calls when using either an IFSTRT or an IFDIAL thread. See the individual wiki pages for detailed descriptions of the [[IFSTRT (IFAM1) (HLI function)\|IFSTRT]] and [[IFSETUP (HLI function)\|IFSETUP]] calls. See [[HLI: IFAM1 job program examples]] for sample IFAM1 applications. </p>

	==IFAM2 jobs==		==IFAM2 jobs==

ELowell at 19:43, 11 July 2016

2016-07-11T19:43:37Z

← Older revision		Revision as of 19:43, 11 July 2016
Line 396:		Line 396:
	The IFAM1 application programmer can optionally specify Model 204 system and User 0 runtime parameters inside the application program using either the IFSTRT call, if the job starts an IFSTRT thread, or the IFSETUP call, if the job starts an IFDIAL thread. </p>		The IFAM1 application programmer can optionally specify Model 204 system and User 0 runtime parameters inside the application program using either the IFSTRT call, if the job starts an IFSTRT thread, or the IFSETUP call, if the job starts an IFDIAL thread. </p>
	<p>		<p>
	Note that there are other differences in coding calls when using either an IFSTRT or an IFDIAL thread. See [[HLI: Function calls]] for detailed descriptions of the IFSTRT (IFAM1) and IFSETUP calls. [[HLI: IFAM1 job program ~~samples~~]] for sample IFAM1 applications. </p>		Note that there are other differences in coding calls when using either an IFSTRT or an IFDIAL thread. See [[HLI: Function calls]] for detailed descriptions of the IFSTRT (IFAM1) and IFSETUP calls. [[HLI: IFAM1 job program examples]] for sample IFAM1 applications. </p>

	==IFAM2 jobs==		==IFAM2 jobs==
Line 573:		Line 573:
	<p class="note"><b>Note:</b> Regardless of the option specified, Model 204 establishes communications with IUCV. The VMCF facility is not supported as of Version 2, Release 2 of Model 204. To ensure compatibility with existing programs, the VMCF option is still accepted but has no effect. The VMCF option might be dropped in future releases of Model 204. If this occurs, you will need to change your HLI programs to eliminate all references to VMCF.</p>		<p class="note"><b>Note:</b> Regardless of the option specified, Model 204 establishes communications with IUCV. The VMCF facility is not supported as of Version 2, Release 2 of Model 204. To ensure compatibility with existing programs, the VMCF option is still accepted but has no effect. The VMCF option might be dropped in future releases of Model 204. If this occurs, you will need to change your HLI programs to eliminate all references to VMCF.</p>
	<p>		<p>
	See [[HLI: IFAM1 job program ~~samples~~]] and [[HLI: IFAM2/IFAM4 job program ~~samples~~]] for examples of a CMS M204IFAM EXEC, which establishes the IUCV link.</p>		See [[HLI: IFAM1 job program examples]] and [[HLI: IFAM2/IFAM4 job program examples]] for examples of a CMS M204IFAM EXEC, which establishes the IUCV link.</p>

	===Using VM immediate commands===		===Using VM immediate commands===
Line 632:		Line 632:
	</ol>		</ol>

	<p>See [[HLI: IFAM2/IFAM4 job program ~~samples~~]] for examples of CMS EXECs to compile and link and to run an IFAM2 application. </p>		<p>See [[HLI: IFAM2/IFAM4 job program examples]] for examples of CMS EXECs to compile and link and to run an IFAM2 application. </p>
	<p>		<p>
	For more information about running application programs under CMS, refer to the appropriate IBM User's Guide for your operating system. </p>		For more information about running application programs under CMS, refer to the appropriate IBM User's Guide for your operating system. </p>

ELowell: /* For more information */

2016-07-11T17:14:14Z

For more information

← Older revision		Revision as of 17:14, 11 July 2016
Line 723:		Line 723:
	</ul>		</ul>
	<p>		<p>
	See ~~[[HLI: Function calls]]~~ for a description of the IFCSA, IFFNSH, and IFABXIT calls.</p>		See the individual wiki pages for a description of the [[IFCSA (HLI function)\|IFCSA]], [[IFFNSH (HLI function)\|IFFNSH]], and [[IFABXIT (HLI function)\|IFABXIT]] calls.</p>

	==IFAM4 jobs ==		==IFAM4 jobs ==

ELowell: /* Using the CRAM facility */

2016-07-11T17:12:12Z

Using the CRAM facility

← Older revision		Revision as of 17:12, 11 July 2016
Line 505:		Line 505:
	In any communication handled by CRAM, one program is the master and the other is a user. The master is always the Model 204 service program, which can communicate with several users over the same channel. After a connection is established, the user thread can issue requests, as required, for the application.</p>		In any communication handled by CRAM, one program is the master and the other is a user. The master is always the Model 204 service program, which can communicate with several users over the same channel. After a connection is established, the user thread can issue requests, as required, for the application.</p>
	<p>		<p>
	Several versions of Model 204 can run concurrently by establishing a distinct CRAM channel name for each version. Also, one user program can simultaneously communicate with multiple Model 204 service programs in different regions. For more information about CRAM, see [[Defining the ~~User Environment~~ (CCAIN)#CRAM (IODEV=11,23,29)\|CRAM (IODEV=11,23,29)]].</p>		Several versions of Model 204 can run concurrently by establishing a distinct CRAM channel name for each version. Also, one user program can simultaneously communicate with multiple Model 204 service programs in different regions. For more information about CRAM, see [[Defining the user environment (CCAIN)#CRAM (IODEV=11, 23, 29)\|CRAM (IODEV=11, 23, 29)]].</p>

	===Linking with the IFIF module===		===Linking with the IFIF module===

ELowell: /* For more information */

2016-07-11T17:08:36Z

For more information

← Older revision		Revision as of 17:08, 11 July 2016
Line 27:		Line 27:
	===For more information ===		===For more information ===
	<p>		<p>
	See [[HLI~~: Function calls~~]] for a detailed description of HLI calls and call parameters. See [[HLI: IFAM1 job program ~~samples~~]] and [[HLI: IFAM2/IFAM4 job program ~~samples~~]] for examples of applications using HLI calls. </p>		See the individual HLI function pages in [[:Category:HLI functions\|HLI functions]] for a detailed description of HLI function calls and call parameters. See [[HLI: IFAM1 job program examples]] and [[HLI: IFAM2/IFAM4 job program examples]] for examples of applications using HLI function calls. </p>

	==IFAM1 jobs==		==IFAM1 jobs==

ELowell at 21:37, 2 May 2016

2016-05-02T21:37:02Z

← Older revision		Revision as of 21:37, 2 May 2016
Line 1,063:		Line 1,063:
	</table>		</table>
	<p class="note"><b>Note:</b> Option 64 of the SYSOPT parameter can be set to force an ABEND without a dump at termination when the return code is nonzero. The SYSOPT parameter is specified in the [[#EXEC statement\|EXEC statement]].</p>		<p class="note"><b>Note:</b> Option 64 of the SYSOPT parameter can be set to force an ABEND without a dump at termination when the return code is nonzero. The SYSOPT parameter is specified in the [[#EXEC statement\|EXEC statement]].</p>

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

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

JAL: link repair

2016-04-29T19:00:12Z

link repair

← Older revision		Revision as of 19:00, 29 April 2016
Line 172:		Line 172:
	</ul>		</ul>
	<p>		<p>
	See [[IFAM1 jobs: Job control statements]] for more information about the job control statements that are used with an IFAM1 job.</p>		See [[#IFAM1 jobs: Job control statements\|IFAM1 jobs: Job control statements]] for more information about the job control statements that are used with an IFAM1 job.</p>

	==IFAM1 jobs: Link-editing under VSE==		==IFAM1 jobs: Link-editing under VSE==

HLI: Job requirements - Revision history

JAL: /* IFAM2 jobs */ add s

JAL: misc formatting

JAL: /* Using the STEPLIB statement */ add links

ELowell: /* Specifying Model 204 runtime parameters */

ELowell at 19:43, 11 July 2016

ELowell: /* For more information */

ELowell: /* Using the CRAM facility */

ELowell: /* For more information */

ELowell at 21:37, 2 May 2016

JAL: link repair

JAL: /* IFAM2 jobs */ add `s`