View source for HLI: Job requirements

==Overview==
<p>
This topic details the job requirements for the application programmer using the Host Language Interface facility in the IFAM1, IFAM2, and IFAM4 Model 204 environments.</p>

===Contents of this topic===
<p>
There are three broad categories of batch jobs that you can run corresponding to the IFAM1, IFAM2, and IFAM4 Model 204 environments that support HLI processing. This topic presents job information in the following order:</p>
<ul>
<li>IFAM1 jobs
<ul>
<li>Under z/OS, VSE, CMS</li>
</ul>
</li>
<li>IFAM2 jobs
<ul>
<li>Under z/OS, VSE, CMS</li>
<li>Using the CICS interface</li>
</ul>
<p class="note"><b>Note:</b> The INTERCOMM interface (supporting the use of Teletype and 3270 terminals in line-at-a-time mode) is no longer supported as of Model 204 version 7.5.
</p>
</li>
<li>IFAM4 jobs (under z/OS only)</li>
</ul>
<p>
This topic describes each type of job and includes examples of job setup and execution in the different operating environments. </p>

===For more information ===
<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==
<p>
IFAM1 applications can run under z/OS, VSE, or CMS operating systems. An IFAM1 job involves a two-step procedure: step one is to link-edit the application program and step two is to run it. </p>
<p>
Examples of the IFAM1 job steps are provided in the sections which follow. Sample setups are shown for each of the operating systems. The following topics are covered for each system: </p>
<ul>
<li>Link-editing the application program</li>
<li>Running the application program</li>
</ul>
<p>
See [[#IFAM1 jobs: Job control statements|IFAM1 jobs: Job control statements]] for a description of the control statements that are used with an IFAM1 job. See [[#IFAM1 jobs: Using an IFSTRT or IFDIAL thread|IFAM1 jobs: Using an IFSTRT or IFDIAL thread]] for more information about applications in the IFAM1 environment. </p>

===IFAM1 dynamic loading===
<p>
Rocket recommends that the IFAM1 application load the Model 204 portion of the application at runtime.</p>
<p>
Invoke IFAM1 dynamic loading by link-editing the IFAM1 application program with the appropriate module:</p>
<ul>
<li>IFIF1OS for z/OS </li>
<li>IFIF1DOS for VSE </li>
<li>IFIF1 for CMS </li>
</ul>
<p>
See the examples of link-editing [[#IFAM1 jobs: Link-editing under z/OS|with IFIF1OS for z/OS]] and [[#IFAM1 jobs: Link-editing under VSE|with IFIF1DOS for VSE]].</p>

<blockquote class="note"><b>Notes:</b> The IFIF1 module is automatically invoked at runtime for CMS.

<p>In order to use the dynamic loading facility, the Model 204 system manager must initially build the IFAM1 load module for your installation site. </p></blockquote>
<p>
Contact your Model 204 system manager to get the name of the Model 204 load library that is used to run IFAM1 programs at your site. For more information about creating the IFAM1 module, refer to the Rocket Model 204 installation instructions for your operating system. </p>

===Advantages of dynamic loading===
<p>
The IFAM1 dynamic loading facility reduces application maintenance and storage by allowing the Model 204 IFAM1 interface to dynamically load the IFAM1 code at runtime. </p>
<p>
Dynamic loading provides the application programmer with the easiest and most efficient method for running IFAM1 applications and is the preferred method recommended by Rocket. </p>
<p>
Note that the direct link-edit method which statically link-edits IFAM1 applications with Model 204 routines can be used by the application programmer to run IFAM1 jobs. However, using this method requires that: </p>
<ul>
<li>
All IFAM1 application programs must be link-edited again each time any Model 204 routines change. </li>
<li>
Each IFAM1 application must carry its own copy of all the Model 204 routines, thereby increasing the application's load module size and load library disk space requirements. </li>
</ul>
<p>
Examples of directly link-editing IFAM1 applications are not provided in this document. </p>

==IFAM1 jobs: Compiling under Enterprise PL/I for z/OS==
<p>
When compiling a PL/I application under the Enterprise PL/I for z/OS compiler, the following compiler parameter is required:</p>
<p class="code">DEFAULT(LINKAGE(SYSTEM))</p>
<p>
This causes the parameter list to be built in the same way that it was built by the old compilers (including turning on the high-order bit of the address of the last parameter).</p>
<p>
For example:</p>
<p class="code">//PLICMPL EXEC PGM=IBMZPLI,PARM='OBJECT,OPTIONS,
//             DEFAULT(LINKAGE(SYSTEM))',REGION=512K,...</p>
<p>
If this compiler option is not specified, subsequent executions of the application will fail with 0C4 abends.</p>

==IFAM1 jobs: Link-editing under z/OS==

===Link with IFIF1OS===
<p>
To link-edit your IFAM1 job running under z/OS, link the IFAM1 application with the Model 204 module IFIF1OS using the INCLUDE CCA statement in SYSLIN DD.</p>
====Example of z/OS JCL to Link-Edit Application (IFAM1)====
<p>
The following sample code shows JCL that might be used to link-edit an IFAM1 application to build the application load module. In this example, the program name is IFAMTEST. </p>

<p class="code">//LINKAPPL JOB,LINKAPPL,MSGLEVEL=(1,1),CLASS=T,MSGCLASS=C
//LINK EXEC PGM=IEWL,PARM='LIST,MAP,LET,NCAL,SIZE=(250K,150K)'
//SYSPRINT DD SYSOUT=C
//SYSUT1 DD UNIT=WORK,SPACE=(TRK,(40,20))
//USEROBJ DD DSN=LOCAL.M204.OBJLIB,DISP=SHR
//OBJLIB DD DSN=M204.V220.OBJLIB,DISP=SHR
//SYSLMOD DD DSN=LOCAL.M204.IFAM1.APPLIC,DISP=OLD
//SYSLIN DD *
INCLUDE USEROBJ(IFAMTEST)
INCLUDE OBJLIB(IFIF1OS)
ENTRY IFAMTEST
NAME IFAMTEST(R)
/*</p>

<p class="note"><b>Note:</b> Before the individual Host Language Interface application programmer can link an IFAM1 application, the Model 204 system manager must build the IFAM1 load module containing the IFII1 member. Contact your Model 204 system manager to get the name of the Model 204 object and load libraries that are used to link-edit and run IFAM1 programs at your site. </p>

==IFAM1 jobs: Running under z/OS==

===Execute with dynamic loading===
<p>
Once you have link-edited the application program, run the IFAM1 application in z/OS.   </p>
====Example of z/OS JCL to Run Application (IFAM1)====
<p>
The following sample code shows an excerpt of the JCL that might be used to run an IFAM1 application that was link-edited as shown in [[#Example of z/OS JCL to Link-Edit Application (IFAM1)|the previous example]]. In the following example, the program name is IFAMTEST. </p>

<p class="syntax">//RUNIFAM1 JOB,'RUNIFAM1',MSGLEVEL=(1,1),MSGCLASS=C,CLASS=T
//*
//IFAM1	EXEC PGM=IFAMTEST
//*
//STEPLIB DD DSN=LOCAL.M204.IFAM1.APPLIC,DISP=SHR
// DD DSN=M204.V220.LOADLIB,DISP=SHR
//CCAAUDIT DD SYSOUT=C
//CCAPRINT DD SYSOUT=C
//CCASNAP DD SYSOUT=C
//SYSUDUMP DD SYSOUT=C
//CCATEMP DD DISP=NEW,UNIT=SYSDA,SPACE=(TRK,20)
//CCASTAT DD DSN=M204.CCASTAT,DISP=OLD
.
.&nbsp;...<span class="term">application program DD statements</span>
.</p>

===Using the STEPLIB statement===
<p>
The STEPLIB file points to the load module libraries where the application program and the Model 204 IFAM1 interface program reside. </p>
<p>
This statement must specify the load module library or libraries that contain IFAM1 and the Host Language Interface user's application program.</p>

<p class="note"><b>Note:</b> One of the following requirements must be met for IFAM1 applications:</p>
<ul>
<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>
The load library where the IFAM1 application resides (and all run-time concatenated libraries) must be APF authorized.</li>
</ul>
<p>
Unless one of these requirements is met, IFAM1 applications will terminate with:</p>
<p class="code">MODEL 204 IS NOT AUTHORIZED FOR THIS CPUID: 0000000000000000</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>

===Using the EXEC statement===
<p>
You can specify the following parameters in the EXEC statement: </p>
<ul>
<li>
PGM -- Required; Indicates the name of the application program being run. Note that application programs cannot be called IFAM1. </li>
<li>
REGION -- Optional; Indicates the size of the memory area to be allocated for IFAM1 and the application. Note that REGION can be specified depending on your site's Model 204 configuration. For information about setting the REGION parameter, see [[Defining the runtime environment (CCAIN)#Runtime environment specifications|Runtime environment specifications]].</li>
<li>
TIME -- Optional; Indicates how much time the application program and Model 204 together can use before being cancelled by the operating system. TIME depends on the requirements of the application.</li>
<li>
PARM -- Optional; Indicates any application runtime parameters to be set.</li>
</ul>
<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==

===Link with IFIF1DOS===
<p>
To link-edit your IFAM1 job running under VSE, link the IFAM1 application with the Model 204 module IFIF1DOS using the INCLUDE statement in OPTION CATAL.</p>
====Example of VSE JCL to Link-Edit Application (IFAM1)====

<p>
The following sample code shows JCL that might be used to link-edit an IFAM1 application to build the application load module. In this example, the program name is IFAMTEST. </p>

<p class="code">// JOB LINKAPPL FOR IFAM1TEST
// DLBL PRIVLIB,'PRIV.USER.LIBRARY'
// EXTENT,SYSnnn,volser,balance of extent information
// LIBDEF CL,TO=PVTCL
// DLBL M204LIB,'M204.PROD.LIBRARY'
// EXTENT,SYSnnn,volser,balance of extent information
// LIBDEF OBJ.SEARCH=(M204LIB.V220,PRIVLIB.XXXX)
// LIBDEF PHASE.CATALOG=PRIVLIB.xxxx
// OPTION CATAL
  PHASE IFAMTEST,*
  INCLUDE usermodule
  INCLUDE IFIF1DOS
/*
// EXEC LNKEDT
/&amp;</p>

<p class="note"><b>Note:</b> Before the individual Host Language Interface application programmer can link an IFAM1 application, the Model 204 system manager must build the IFAM1 load module containing the IFII1 member. IFAM1 is provided as a phase in the distribution sublibrary and may need to be relinked by the Model 204 system manager.</p>
<p>
Contact your Model 204 system manager to get the name of the Model 204 object and load sublibraries that are used to link-edit and run IFAM1 programs at your site. </p>

==IFAM1 jobs: Running under VSE==

===Execute with dynamic loading===
<p>
Once you have link-edited the application program, run the IFAM1 application in VSE.   </p>
====Example of VSE JCL to run application (IFAM1)====
<p>
The following sample code shows an excerpt of the JCL that might be used to run an IFAM1 application that was link-edited as shown in [[#Example of VSE JCL to Link-Edit Application (IFAM1)|the previous example]]. The EXEC statement specifies the name of the application program to be executed. In this example, the program name is IFAMTEST. </p>

<p class="code"> // JOB DOS IFAM1 DYNAMIC LINKEDIT TEST
 // DLBL PRIVLIB,'PRIV.USER.LIBRARY'
 // EXTENT,SYSnnn,volser,balance of extent information
 // LIBDEF CL,TO=PVTCL
 // DLBL M204LIB,'M204.PROD.LIBRARY'
 // EXTENT ,SYSnnn,volser,balance of extent information
 // LIBDEF PHASE.SEARCH=(PRIVLIB.xxxx,M204LIB.V220)
 // DLBL CCAJRNL,'MODEL204.CCAJRNL'
 // EXTENT SYS001,balance of extent information
 // DLBL CCATEMP,'MODEL204.CCATEMP',,DA
 // EXTENT SYS001
 // DLBL CCASTAT,'MODEL204.CCASTAT'
 // EXTENT SYS001,balance of extent information
 // ASSGN SYS001,DISK,VOL=SYSWK1,SHR
 // UPSI 10111000
 // EXEC IFAMTEST,SIZE=AUTO
 /*
 /&amp;</p>

===Using the LIBDEF statement===
<p>
In VSE, a LIBDEF JCL card must point to the library and sublibrary that contain the Model 204 IFAM1 interface program and the HLI user's application program. Use the name of the Model 204 load sublibrary that is used to run IFAM1 programs at your site. </p>
<p>
If the Model 204 load module library and application load library are in separate libraries, the LIBDEF must specify both the library and the sublibrary in the search chain. </p>

===For more information===
<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. Note that VSE allows a seven-character file name to be used for DLBL in the JCL. </p>

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

===Execute with dynamic loading===
<p>
In CMS, the process of generating an application module that uses IFAM1 can be done at runtime. No additional facility is required to make the process dynamic. </p>
====Example of CMS link-edit and execution (IFAM1)====
<p>
The following sample code shows CMS commands that might be used to run an IFAM1 application. This set of commands loads the application module and executes the program. In this example, the program name is IFM1PRGM. </p>

<p class="code"><nowiki>&CONTROL OFF
* EXAMPLE TO GENERATE AN APPLICATION MODULE THAT USES
* IFAM1. PROGRAM NAME = IFM1PRGM

GLOBAL TXTLIB M204IFM1

LOAD IFM1PRGM IFIF1 (RESET IFM1PRGM)

GENMOD IFM1PRGM
&amp;TYPE
&amp;TYPE IFM1PRGM MODULE A HAS BEEN GENERATED FOR YOUR USE.
&amp;TYPE
&amp;EXIT 0

IFAM1 FILES</nowiki></p>

===Using the IFAM1 command===
<p>
The [[#Example of CMS link-edit and execution (IFAM1)|previous example]] uses the IFAM1 command to execute a host language application that uses IFAM1. </p>
<p>
The IFAM1 command in the previous sample code specifies the name of an EXEC (FILES) that defines system and database files for IFAM1 and stacks the name of the application program to be executed. See the [[#Example of the FILES EXEC|following sample code]] for an example of the FILES EXEC that is used. </p>
<blockquote class="note"><b>Note:</b> You can use the IFAM1 EXEC command to run your IFAM1 program assuming that CMS Model 204 has been correctly installed and configured at your site. For IFAM1 under CMS, the IFAM1 saved segments must have been generated and the appropriate minidisks that contain Model 204 EXECs and MODULEs must be accessible.

<p> A return code of 0 from the EXEC invokes the application program. A return code of 1 bypasses the invocation of the program. Any other return code is considered an error condition and ends the response to the IFAM1 EXEC command.</p> </blockquote>

====Example of the FILES EXEC====
<p>
The following sample code shows FILES EXEC, the EXEC named in the IFAM1 command in [[#Example of CMS link-edit and execution (IFAM1)|the previous example]], which might contain the following statements (shown in REXX): </p>

<p class="code">'FILEDEF * CLEAR'
'FILEDEF CCATEMP DISK CCATEMP M204SYS A'
'FILEDEF CCAJRNL DISK CCAJRNL M204SYS A'
'FILEDEF CCAGRP DISK CCAGRP M204SYS A'
'FILEDEF CCASTAT DISK CCASTAT M204SYS A'
'FILEDEF CCASNAP DISK CCASNAP M204SYS A'
'FILEDEF CCAPRINT DISK CCAPRINT M204SYS A'
'FILEDEF CCAAUDIT DISK CCAAUDIT M204SYS A'
'FILEDEF CHKPOINT DISK CHKPOINT M204SYS A'

/**/
/*! include additional FILEDEF commands for database files */
/**/
push 'IFM1PGRM'
exit 0 </p>

==IFAM1 jobs: Job control statements==
<p>
The control statements in the following table are used in an IFAM1 job. </p>
<p class="caption" style="width:400px">IFAM1 control statements</p>
<table>
<tr class="head">
<th>Statement</th>
<th>Use</th>
</tr>
<tr>
<td>EXEC
</td>
<td>required</td>
</tr>
<tr>
<td>STEPLIB/LIBDEF/TXTLIB</td>
<td>required</td>
</tr>
<tr>
<td>CCAJRNL</td>
<td>optional (used for audit information only)</td>
</tr>
<tr>
<td>CCAJLOG</td>
<td>optional (used for audit information)</td>
</tr>
<tr>
<td>CCAAUDIT</td>
<td>optional</td>
</tr>
<tr>
<td>CHKPOINT</td>
<td>required for roll-back recovery</td>
</tr>
<tr>
<td>CCATEMP</td>
<td>required</td>
</tr>
<tr>
<td>CCASNAP, SYSUDUMP</td>
<td>required for error diagnostics</td>
</tr>
<tr>
<td>CCAPRINT</td>
<td>required</td>
</tr>
<tr>
<td>CCASTAT</td>
<td>required for security</td>
</tr>
<tr>
<td>CCAGRP</td>
<td>required for permanent file groups</td>
</tr>
<tr>
<td>Model 204 files</td>
<td>required</td>
</tr>
<tr>
<td>Application program files</td>
<td>optional</td>
</tr>
</table>

<p class="note"><b>Note:</b> VSE allows a seven-character DLBL name while z/OS allows an eight-character DD name. The actual names that are used in VSE JCL may differ in this regard from those that are listed above. </p>
<p>
General information about the EXEC, Model 204 file, and application program file statements for IFAM1 jobs is provided below. </p>
<p>
For a detailed description of the Model 204 data sets that are used for HLI jobs, see [[HLI: Model 204 data sets in HLI jobs]]. For additional information about the Model 204 job control statements, see [[Using HLI and batch configurations]].</p>

===EXEC statement===
<p>
For IFAM1, the EXEC statement does not refer to Model 204 directly. When an IFAM1 job is running, Model 204 parameters cannot be specified in the EXEC statement, that is, not in the PARM field for z/OS, and not in the OPTION SYSPARM statement for VSE. </p>
<p>
In IFAM1, any Model 204 parameter settings must be passed to Model 204 inside the application program using HLI calls. See [[#IFAM1 jobs: Using an IFSTRT or IFDIAL thread|IFAM1 jobs: Using an IFSTRT or IFDIAL thread]] for more information about using IFSTRT and IFDIAL threads in IFAM1. </p>

===Model 204 files===
<p>
The control statements must contain a data set or file definition statement for each data set of each Model 204 file to be used in the run. </p>
<p>
A disposition of either SHR or OLD can be specified, depending whether the Host Language Interface job runs concurrently with other Model 204 programs which use the file. Usually SHR is the recommended disposition. Model 204 uses its own system of enqueuing to resolve updating conflicts. </p>

===Application program files===
<p>
The application program may need data set or file definition statements of its own for various data sets. Be careful not to specify file names that are the same as the names of any of the data set or file definition statements needed by the IFAM1 Host Language Interface itself. </p>

==IFAM1 jobs: Using an IFSTRT or IFDIAL thread==

===Using a single thread===
<p>
IFAM1 is a single-region configuration of Model 204 that supports a single user using a private copy of Model 204. IFAM1 supports a single thread, either an IFSTRT thread or an IFDIAL thread.   </p>
<p>
The specific Model 204 interface modules that are used by the Host Language Interface for the IFAM1 job run are automatically invoked by Model 204 and depend on whether you are using an IFSTRT or an IFDIAL thread in your application program. </p>

===Specifying Model 204 runtime parameters===
<p>
In IFAM1 the EXEC parameter which is specified in the job control EXEC statement is not available to Model 204. </p>
<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>
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>

==IFAM2 jobs==
<p>
IFAM2 jobs can run under z/OS, VSE, or CMS. </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>
<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>

===Communications facilities (CRAM or IUCV) ===
<p>
For z/OS and VSE, communication between Model 204 and a host language program in a different region is enabled by the Model 204 Cross-Region Access Method (CRAM), a special inter-region communications facility.</p>
<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>
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>

===Subsystem names, channel names, and IODEV settings===
<p>
Model 204 uses the following subsystem names, channel names, and IODEV settings for IFAM2 threads: </p>
<ul>
<li>For IFSTRT 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 IFSTRTN 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.

<p>The following default channel names and IODEV settings are used for IFSTRT threads:</p>
<table>
<tr class="head">
<th>Facility</th>
<th>Parameter</th>
<th>Default subsystem name</th>
<th>Default channel name</th>
<th>IODEV setting</th>
</tr>
<tr>
<td>CRAM</td>
<td>IFAMCHNL</td>
<td>Value in the IGCLM244 load module</td>
<td>IFAMPROD</td>
<td>23</td>
</tr>
<tr>
<td>IUCV</td>
<td>VMIFCHNL</td>
<td>Not Applicable</td>
<td>M204VMIF</td>
<td>43</td>
</tr>
</table>
</li>
<li>
For IFDIAL 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 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.

<p>The following default channel names and IODEV settings are used for IFDIAL threads: </p>
<table>
<tr class="head">
<th>Facility</th>
<th>Parameter</th>
<th>Default subsystem name</th>
<th>Default channel name</th>
<th>IODEV setting</th>
</tr>
<tr>
<td>CRAM</td>
<td>CRIOCHNL</td>
<td>Value in the IGCLM244 load module</td>
<td>M204PROD</td>
<td>29</td>
</tr>
<tr>
<td>IUCV</td>
<td>VMIOCHNL</td>
<td>Not Applicable</td>
<td>M204VMIO</td>
<td>39</td>
</tr>
</table>
</li>
</ul>
<p class="note"><b>Note:</b> The IODEV settings listed above are the ones that are used by Model 204 for IFAM2 processing. You can specify VMIOCHNL and VMIFCHNL (and the corresponding IODEVs) only for CMS. You can specify CRIOCHNL and IFAMCHNL (and the corresponding IODEVs) only for z/OS and VSE. </p>
<p>
These threads must be defined in the Model 204 Online run to provide IFAM2 communications. One IODEV is required by Model 204 for each thread that is started in the HLI program. </p>

===Compiling under Enterprise PL/I for z/OS===
<p>
When compiling a PL/I application under the Enterprise PL/I for z/OS compiler, the following compiler parameter is required:</p>
<p class="code">DEFAULT(LINKAGE(SYSTEM))</p>
<p>
This causes the parameter list to be built in the same way that it was built by the old compilers (including turning on the high-order bit of the address of the last parameter).</p>
<p>
For example:</p>
<p class="code">//PLICMPL EXEC PGM=IBMZPLI,PARM='OBJECT,OPTIONS,
//             DEFAULT(LINKAGE(SYSTEM))',REGION=512K,...</p>
<p>
If this compiler option is not specified, subsequent executions of the application will fail with 0C4 abends.</p>

==IFAM2 jobs: Running under z/OS and VSE==

===Using the CRAM facility===
<p>
CRAM is an interregion facility that allows two or more programs to communicate with each other over an arbitrary number of distinct connections, called channels. </p>
<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>
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===
<p>
A batch IFAM2 program running under z/OS and VSE must be linked with the IFIF object module, which condenses the data pertinent to each Host Language Interface call, passes it to CRAM, and sends the information to an interface routine in the Model 204 region. </p>
<p>
Model 204 services the call and returns the information to the appropriate host language program that uses CRAM as the intermediary. </p>

===Link-editing and executing the application program ===
<p>
The IFAM2 application program requires its own job control statements to execute. </p>
<p>
Note that the IFAM2 job control statements are independent of the Model 204 job because the IFAM2 application program executes as a separate job in its own region. The control statements for Model 204 files are included in the Model 204 run. </p>
<p>
IFAM2 programs must be link-edited with the NODYNAM option set. If NODYNAM is not set, your program may abend when executed.</p>
====Example of z/OS JCL to run application (IFAM2)====
<p>
The following sample job excerpt shows the z/OS JCL that runs an IFAM2 application program. In this example, COBUCLG is a COBOL compile-link-and-go procedure. </p>

<p class="code">//CPLLKGO EXEC COBUCLG,
//PARM.COB='LOAD,NOSEQ,NODYNAM,APOST',
//REGION.LKED=200K,
//PARM.LKED='LIST,LET,SIZE=(192K,100K),MAP',REGION,GO=64K
//COB.SYSIN DD *
 IDENTIFICATION DIVISION.
 PROGRAM-ID. CRAMDIAL.
.
.
.
 STOP RUN.
//LKED.OBJLIB DD DSN=M204.V220.OBJLIB,DISP=SHR
//LKED.SYSIN DD * 
INCLUDE OBJLIB(IFIF) 
//GO.SYSUDUMP DD SYSOUT=A
//GO.SYSOUT DD SYSOUT=A
//GO.INFILE DD *
.
.
.
/*
//</p>
<p>
To link-edit your IFAM2 job running under z/OS, link the IFAM2 application with the Model 204 module IFIF using the INCLUDE OB statement in SYSIN DD.</p>

==IFAM2 jobs: Running under CMS==

===Using the M204IFAM object modules===
<p>
The IBM inter-user communication vehicle (iUCV) allows HLI programs running under CMS to communicate with a Model 204 system running in a separate virtual machine. </p>
<p>
The application program must be loaded to include a library of object modules, named M204IFAM TXTLIB, that contains the CMIF, IFIF, IFCM, and IUCV interface routines that are necessary for this communication. </p>

===Using the M204IFAM EXEC===
<p>
The CMIF routine in M204IFAM TXTLIB invokes a procedure called M204IFAM EXEC to obtain the name of the virtual machine that is running Model 204 and to obtain the needed IUCV communications method. </p>
<p>
Both M204IFAM TXTLIB and M204IFAM EXEC must be available on the CMS machine for an IFAM2 host language program. </p>
<p>
You can use any of the following values in the line that indicates the communication type to the M204IFAM EXEC:</p>
<ul>
<li>IUCVVMCF (the default)</li>
<li>IUCV</li>
<li>VMCF</li>
<li>VMCFIUCV</li>
</ul>

<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>
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>

===Using VM immediate commands===
<p>
You can use the HX, HT, and RT VM immediate commands described below when an IFAM2 host program is executing. </p>
<p>
If one of the following commands is entered after the attention key for the terminal is pressed, VM takes the immediate actions summarized below: </p>
<ul>
<li>The HX command abnormally terminates (ABENDs) execution of a program. Control returns to CMS. This is equivalent to cancelling a program under z/OS.</li>
<li>The HT command halts the display of output on the terminal, but continues execution. Use the RT command to resume output. </li>
</ul>

===Loading and executing an IFAM2 program ===
<p>
To load and execute an IFAM2 application program under CMS, use the following steps as guidelines. The specific procedures for loading and running IFAM2 programs depend upon the particular language in which the program is written. </p>
<ol>
<li>
Use the GLOBAL TXTLIB command to specify the list of object libraries (called TXTLIBs) that are used to resolve references by the IFAM2 program to library subroutines.

<p class="note"><b>Note:</b> The GLOBAL TXTLIB command includes M204IFAM TXTLIB in the list of libraries, which enables the CMS Loader to include the IFAM2 interface in the program.</p> 
<p>Specify the following command in the GLOBAL TXTLIB command: </p>
<p class="code">GLOBAL TXTLIB M204IFAM</p>
<p>
M204IFAM TXTLIB contains the interface routines necessary for communication with Model 204 using IUCV. </p>
</li>
<li>
Load the application program using the CMS Loader.

<p class="note"><b>Note:</b> The LOAD command that is normally used to invoke the CMS Loader must specify the Model 204 IFCM module in the list of programs to be loaded. If this is not done, IFCM is not included and an error occurs when the application program attempts to load the module named IGCLM244. </p>
<p>
To load a program named IFAMTEST, for example, specify the following command:</p>
<p class="code">LOAD IFAMTEST IFCM CLEAR</p>
</li>
<li>
To run the program immediately: 
<ul>
<li>
Specify START in the command line as follows:
<p class="code">LOAD IFAMTEST IFCM (START CLEAR</p></li>
<li>
<p>Or specify START as a separate command:</p>
<p class="code">LOAD IFAMTEST IFCM CLEAR
START</p></li>
<li>
Or use the GENMOD command to create a nonrelocatable program module (with external references resolved). 
<p>
For example, for the program named IFAMTEST, specify the following command:</p>
<p class="code">LOAD IFAMTEST IFCM
GENMOD IFAMTEST</p>
<p>
IFAMTEST is the file name assigned to the module (and the file type is MODULE).</p>
<p>
And next, enter the name of the program to run it. For example,</p>
<p class="code">IFAMTEST </p>
</li>
</ul>
</li>
</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>
For more information about running application programs under CMS, refer to the appropriate IBM User's Guide for your operating system. </p>

==IFAM2 jobs: Using an IFDIAL thread under CMS==

===Specifying the IFDIAL operand in the ONLINE command===
<p>
Under CMS, an IFAM2 job can start an IFDIAL thread, and this is the only connection that is allowed in the job.   </p>
<p>
Use the IFDIAL operand in the ONLINE command to specify a single-user IFDIAL connection to be made (saved segment mandatory). </p>
<p>
The IFDIAL connection must be made on the main (nonrecovery) step. Execution of the ONLINE command creates a Model 204 Online environment. For more information about this facility, refer to the Rocket Model 204 installation instructions for the IBM z/VM platform.</p>
<p>
If you specify IFDIAL, the main (nonrecovery) EXEC must provide only one parameter, the user program name, in the stack. IFDIAL connections require that the user program be placed first on the stack. </p>
<p>
When defining subsystems that contain Model 204 calls in the SCT for IFDIAL, do not set the DBASE parameter. </p>

==IFAM2 jobs: Running under CICS==
<p>
IFAM2 pseudo conversational support allows CICS users to include pseudo conversational applications in their IFAM2 programs. This allows the host IFAM2 program to enter a pseudo conversational wait at any time during an IFAM2 session with Model 204. The CICS interfaces are compatible with CICS Release 2.1 and later. </p>

===Transaction management ===
<p>
The CICS pseudo conversational programming technique ensures that no resources are held by a task during each conversational iteration with the terminal operator. </p>
<p>
Such resources include VSAM strings, file record enqueues, enqueues on Temporary Storage queues or transient data destinations, as well as the storage acquired by the transaction during execution. Note, however, that Model 204 found sets are retained.</p>
<p>
The pseudo conversational feature prevents potentially serious bottlenecks between transactions that could cause longer response times and deadlocks.</p>

===Using the CICS-resident program (DFHPSF)===
<p>
For applications running under CICS, the IFIF module along with a CICS-specific appendage called IFPS, are linked as a CICS-resident program, such as DFHPSF, when the CICS interface is installed. </p>
<p>
Once the CICS interface is installed using the CICS-resident program, CICS users can submit IFAM2 jobs to run by link-editing to IFENTPS, which is described in the next section. </p>

<p class="note"><b>Note:</b> The CICS-resident program name is site-specific and can be named on the CICFG configuration section of the CICS batch program. Several types of DFHPSF (IFIF/IFPS) CICS-resident programs can be available in the CICS environment. The particular copy can be selected through the configuration name. </p>
<p>
For more information about CICS-resident programs, see [[HLI: IFAM2 CICS processing]].</p>

===Linking to the IFENTPS module===
<p>
The IFENTPS module provides the IFAM2 application program interface for pseudo conversational CICS transactions and must be link-edited with the user CICS program. </p>
<p>
To use the IFAM2 CICS interface, link-edit your program with the IFENTPS module. No other direct changes to your program are required.</p>
<p>
Include the data set or file definition statements for Model 204 files that are accessed by CICS applications in the JCL for the Model 204 region, not the CICS region. </p>

<p class="note"><b>Note:</b> The IFENTPS module can be used with either macro-level or command-level CICS application programs. The configuration copy member, CICFG, contains a conditional assemble switch that determines whether a macro-level or command-level version is generated. The Model 204 system manager must ensure that the correct version of IFENTPS is used with the appropriate application programs. </p>

===Using macro or command level program code===
<p>
The version of IFENTPS that is link-edited with your IFAM2 CICS program must be assembled specifically for either macro or command level program code.</p>

===Addressing and storage requirements===
<p>
Note the following IFAM2 CICS requirements: </p>
<ul>
<li>The following CICS areas must be addressable: CSA, TWA, and TCA.</li>
<li>IFAM2 requires 88 bytes of CICS TWA. </li>
<li>A temporary storage queue is created for each HLI transaction when the first IFSTRT or IFDIAL call is issued. </li>
</ul>

===First and last calls in the program===
<p>
The following calls are required in the IFAM2 CICS program:</p>
<ul>
<li>Before Version 3.1 of Model 204, the IFCSA call was required and needed to be the first call issued during the IFAM2 session. For Model 204 Version 3.1 and later, the IFCSA call no longer performs any function and is not required. For purposes of upward compatibility, the IFCSA call can remain in your current programs.</li>
<li>The IFFNSH or IFHNGUP call is necessary as the last call in the program to ensure that all CRAM resources are released at program termination. </li>
</ul>

===Abend handling is required ===
<p>
Using the Model 204 IFAM2 CICS interface successfully depends on correct abend handling to prevent hung CRAM channels. </p>
<p>
A program must establish its own abend handler or use the IFABXIT call to establish the IFAM2 abend handler. The program must establish the abend handler or issue IFABXIT after any pseudo conversational waits, that is, after the initial connection is established. </p>
<p>
If you run CICS IFAM2 applications written in COBOL II, set the &amp;IFABEND parameter in CICFG to 'NO'. This prevents the abend handler in IFENTPS from causing ASRAs.</p>
<p>
If you do this, you might want to include an abend handler routine in your COBOL II applications to prevent hanging threads after an abend. If you do, the abend handler routine must issue an IFFNSH call.</p>

===For more information===
<p>
See [[HLI: IFAM2 CICS processing]] for detailed information about abend handling in an IFAM2 CICS program. Also refer to that topic for the following information about IFAM2 CICS programs:</p>
<ul>
<li>The IFENTPS link module</li>
<li>Addressable CICS areas (CSA, TCA, TWA) and coding example</li>
<li>TWA requirements, using the CICFG copy member</li>
<li>Temporary storage queue </li>
</ul>
<p>
See [[HLI: Function calls]] for a description of the IFCSA, IFFNSH, and IFABXIT calls.</p>

==IFAM4 jobs ==
<p>
An IFAM4 job involves a two-step procedure: step one is to link-edit the application program and step two is to execute the IFAM4 batch job which runs Model 204 and the application program.</p>
<p>
IFAM4 applications can run under the z/OS operating system. Examples of the IFAM4 job steps showing sample setups are provided in the sections which follow. The following topics are covered: </p>
<ul>
<li>Link-editing the application program</li>
<li>Running the application program</li>
</ul>
<p>
See [[#IFAM4 jobs: Control statements|IFAM4 jobs: Control statements]] for a description of the control statements that are used with an IFAM4 job. </p>

===Running the IFAM4 application and Model 204===
<p>
IFAM4 is a single-region configuration of Model 204 that supports a single user using a private copy of Model 204. </p>
<p>
When you use the IFAM4 interface, your application program and the Model 204 service routines run as separate tasks in a single region or virtual machine. </p>

<blockquote class="note"><b>Note:</b> In order to use the IFAM4 facility, the Model 204 system manager must initially build the IFAM4 load module for your installation site. IFAM4 must be link-edited with the REUS option and must be named IFAM4.
<p>
Contact your Model 204 system manager to get the name of the Model 204 load library that is used to run IFAM4 programs at your site. For more information about creating the IFAM4 module, refer to the Rocket [[Model 204 installation]] instructions for your operating system. </p>
</blockquote>

===Using IFSTRT threads===
<p>
IFAM4 supports an application that uses one or more threads. An IFAM4 application can use only IFSTRT threads. </p>
<p>
If your application uses single cursor IFSTRT threads, IFAM4 provides the most efficient way to run a multithreaded batch HLI program. IFAM4 is also useful in certain test and batch production situations.</p>

===Running concurrent IFAM4 applications===
<p>
Ordinarily, two concurrently running HLI programs do not use IFAM4 to interface with a single copy of Model 204. Each IFAM4 application program runs in its own region and must have its own copy of Model 204. </p>
<p>
However, the capability to use multiple applications or copies of an application with a single copy of Model 204 exists. To run multiple applications or copies, the host installation must provide a single controlling or monitor program to attach as subtasks each application program that is to communicate with Model 204. </p>
<p>
This monitor program is then considered to be the application referred to subsequently in the IFAM4 control statements. Each of these application programs must have its own copy of IFIF4 link-edited to do the Host Language Interface calls and data transfers. </p>

===IFAM1 jobs: Compiling under Enterprise PL/I for z/OS===
<p>
When compiling a PL/I application under the Enterprise PL/I for z/OS compiler, the following compiler parameter is required:</p>
<p class="code">DEFAULT(LINKAGE(SYSTEM))</p>
<p>
This causes the parameter list to be built in the same way that it was built by the old compilers (including turning on the high-order bit of the address of the last parameter).</p>
<p>
For example:</p>
<p class="code">//PLICMPL EXEC PGM=IBMZPLI,PARM='OBJECT,OPTIONS,
//             DEFAULT(LINKAGE(SYSTEM))',REGION=512K,...</p>
<p>
If this compiler option is not specified, subsequent executions of the application will fail with 0C4 abends.</p>

==IFAM4 jobs: Link-editing under z/OS==

===Link with IFIF4===
<p>
To link-edit your IFAM4 job running under z/OS, link the IFAM4 application with the Model 204 object module IFIF4 using the INCLUDE OB statement in SYSIN DD.</p>
====Example of z/OS JCL to link-edit COBOL application (IFAM4)====
<p>
The following sample code shows an example of the JCL that might be used to link-edit an IFAM4 application to build the application load module. In this example, COBUCL is a COBOL compile-and-link procedure and the program name is COBOLTST. </p>

<p class="code">//EXECCOBUCL
.
.
.
//LKED.SYSLMODDDDISP=(NEW,CATLG),
//DSNAME=LOCAL.M204.IFAM4.APPLIC
//LKED.OBDDDSN=LOCAL.M204.OBJECT,DISP=SHR
//LKED.SYSINDD*
INCLUDE OB(IFIF4)
NAME COBOLTST(R)</p>

====Example of z/OS JCL to link-edit PL/1 application (IFAM4)====
<p>
The sample code below shows another example of the JCL that might be used to link-edit an IFAM4 application to build the application load module. In this example, PL1LFCL is a PL/1 compile-and-link procedure and the program name is PL1TEST. </p>

<p class="code">//EXECPL1LFCL
.
.
.
//LKED.SYSLMODDDDISP=(NEW,CATLG),
//DSNAME=LOCAL.M204.IFAM4.APPLIC
//LKED.OBDDDSN=LOCAL.M204.OBJECT,DISP=SHR
//LKED.SYSINDD*
INCLUDE OB(IFIF4)
NAME PL1TEST(R)</p>

==IFAM4 jobs: Running under z/OS==

===Execute IFAM4===
<p>
Once you have link-edited the application program, run the IFAM4 application in z/OS. </p>

====Example of z/OS JCL to run application (IFAM4)====
<p>
The sample code below shows an example excerpt of the JCL that might be used to run an IFAM4 application which was link-edited as shown in [[#Example of z/OS JCL to link-edit PL/1 application (IFAM4)|the previous example]]. The sample job stream runs Model 204 and an IFAM4 application program (executing IFAM4) with three IFSTRT threads (IODEV=23). In this example, the program name in IFAM4IN DD is PL1TEST. </p>

<p class="code"><nowiki>//RUN  EXEC  PGM=IFAM4,REGION=1024K,TIME=10,
//           PARM='SYSOPT=160,LIBUFF=1024'
//STEPLIB    DD  DSN=LOCAL.M204.IFAM4.APPLIC,DISP=SHR
//           DD  DSN=LOCAL.M204.LOAD,DISP=SHR
//CCAAUDIT   DD  SYSOUT=A
//CCAJRNL    DD  DSN=M204.JRNL,DISP=OLD
//CCATEMP    DD  UNIT=3380,SPACE=(TRK,40),
//           DISP=(NEW,DELETE)
//CCASNAP    DD  SYSOUT=A
//SYSUDUMP   DD  SYSOUT=A
//VEHICLES   DD  DSN=M204.FILE.VEHICLES,DISP=SHR
//CUSTOMER   DD  DSN=M204.FILE.CUSTOMER,DISP=SHR
//EMPLOYEE   DSN=M204.FILE.EMPLOYEE,DISP=SHR
//CCAPRINT   DD  SYSOUT=A
//CCASERVR   DD  UNIT=3380,DISP=(NEW,DELETE),
//           SPACE=(CYL,2)
//CCAIN      DD  *
NUSERS=4,NSERVS=3,NFILES=3,NDIR=3
IODEV=23
IODEV=23
IODEV=23
*SLEEP 3600
/*
//IFAM4IN    DD  *
PL1TEST
P1=149,P2=ANDREW
/*
//SYSOUT     DD  SYSOUT=A
//INFILE     DD  DSN=RANDOM.INPUT.DATA,DISP=SHR
.
.
.
</nowiki></p>
<p>See [[#IFAM4 jobs: Job errors and ABENDs|IFAM4 jobs: Job errors and ABENDs]] for information about IFAM4 job step return codes and job run ABENDs.</p> 
<p class="note"><b>Note:</b> The IFAM4 load module must be installed at your site and must be named IFAM4.</p>

==IFAM4 jobs: Control statements==

===Overview of IFAM4 job control statements ===
<p>
The control statements listed in the following table are used in an IFAM4 job. </p>
<table>
<p class="caption" style="width:400px">IFAM4 control statements</p>
<tr class="head">
<th>Statement</th>
<th>Use</th>
</tr>
<tr>
<td>EXEC</td>
<td>Required</td>
</tr>
<tr>
<td>STEPLIB</td>
<td>Required</td>
</tr>
<tr>
<td>CCAJRNL</td>
<td>Required for roll-forward recovery</td>
</tr>
<tr>
<td>CHKPOINT</td>
<td>Required for roll-back recovery</td>
</tr>
<tr>
<td>CCAAUDIT</td>
<td>Optional</td>
</tr>
<tr>
<td>CCATEMP</td>
<td>Required</td>
</tr>
<tr>
<td>CCASNAP, SYSUDUMP</td>
<td>Required for error diagnostics</td>
</tr>
<tr>
<td>CCAPRINT</td>
<td>Required</td>
</tr>
<tr>
<td>CCAIN</td>
<td>Required</td>
</tr>
<tr>
<td>CCASERVR</td>
<td>Required for server swapping</td>
</tr>
<tr>
<td>CCASTAT</td>
<td>Required for security</td>
</tr>
<tr>
<td>CCAGRP</td>
<td>Required for permanent file groups</td>
</tr>
<tr>
<td>IFAM4IN</td>
<td>Required</td>
</tr>
<tr>
<td>Model 204 files</td>
<td>Required</td>
</tr>
<tr>
<td>Application program files</td>
<td>Optional</td>
</tr>
</table>
<p>
See below for information about the EXEC, STEPLIB file, CCAIN, IFAM4IN, Model 204 files, and application program file statements for IFAM4 jobs. </p>
<p>
For a detailed description of the Model 204 data sets that are used for HLI jobs, see [[HLI: Model 204 data sets in HLI jobs]].</p> 
<p>For additional information about the Model 204 job control statements, see [[Using HLI and batch configurations]].</p>

===EXEC statement===
<p>
You can specify the following parameters in the EXEC statement:</p>
<ul>
<li>PGM -- Required; Must specify IFAM4 (and not the name of the application program).</li>
<li>REGION -- Required; Indicates the size of the memory area to be allocated for both IFAM4 and the application. For information about setting the REGION parameter, see [[Defining the runtime environment (CCAIN)#Runtime environment specifications|Runtime environment specifications]].
</li>
<li>
TIME -- Required; Indicates how much time the application program and Model 204 together can use before being cancelled by the operating system.</li>
<li>
PARM -- Optional; Indicates any Model 204 runtime parameters, to be passed to Model 204. Note that user application parameters are not specified in the EXEC statement for IFAM4 and are handled instead by IFAM4IN, which is described below.
<p>
Specify any Model 204 parameters that can be set in the EXEC statement using the following format: </p>
<p class="syntax">,PARM='parameter=value[,parameter=value]...'</p>
<p>
Note that the following guidelines apply for specifying SYSOPT parameter settings: </p>
<ul>
<li>If option 16 is set, a valid LOGIN account must be specified in the IFSTRT call for each application thread that is started by the job. </li>
<li>Setting option 32 (print RK lines) provides an audit trail or journal log of each Host Language Interface call made to Model 204. This log is invaluable for debugging the application. </li>
</ul>
</li>
</ul>

===STEPLIB statement===
<p>
The STEPLIB file points to the load module libraries where the application program and the Model 204 IFAM4 interface program reside. </p>
<p>
The STEPLIB file statement must specify the Model 204 load module library or the library that contains IFAM4 and the user's application program. If the Model 204 load module library and application load library are in separate libraries, use concatenated DD data set definition statements. </p>

===CCAIN file===
<p>
The CCAIN input file is required for IFAM4 to specify Model 204 User 0 parameters that apply for the rest of the job run. For IFAM4 the following parameters and statements are required in the CCAIN DD: </p>
<ul>
<li>
NUSERS -- Required; NUSERS is required on the User 0 parameter line. Set NUSERS equal to the number of threads to be used (that is, the number of IODEV statements) plus one. </li>
<li>
IODEV=23 -- Required; Following the User 0 parameter lines, insert an IODEV=23 statement for each thread to be started in the application program. </li>
<li>
<nowiki>*SLEEP</nowiki> -- Required; You must use the *SLEEP command following the IODEV lines to specify an elapsed time in seconds longer than the time the application program needs to finish processing. *SLEEP suspends processing of the CCAIN input stream but allows the application program threads to continue. 
<blockquote class="note"><b>Notes:</b> <br />
IFAM4 immediately terminates when the application program ends. If *SLEEP times out before the application program completes, IFAM4 ends and, if the application is updating the database, file damage may occur.
<p>Model 204 expects the CCAIN data set to consist of 80-character lines. Data is in columns 1 through 71. Any nonblank character in column 72 indicates continuation of the line in to the next line. For a complete description of the CCAIN file, see [[Defining the runtime environment (CCAIN)]].</p></blockquote>
</li>
</ul>

===IFAM4IN file===
<p>
Use the IFAM4IN file definition statement to specify a data set that contains the following two control statements: </p>
<ol>
<li>
The first statement is required and contains the name of the your application program as specified in the compile-and-link job. It must start in Column 1. </li>
<li>
The second statement is used to specify parameters to be passed to the application program, as necessary. 

<p class="note"><b>Note:</b> If you are running the application program named APATTACH, omit the entire IFAM4IN data set. </p>
</li>
</ol>

===Model 204 files ===
<p>
The control statements must contain a data set or file definition statement for each data set of each Model 204 file to be used in the run. </p>
<p>
A disposition of either SHR or OLD can be specified, depending whether the Host Language Interface job runs concurrently with other Model 204 programs which use the file. Usually SHR is the recommended disposition. Model 204 makes use of operating system enqueuing to resolve updating conflicts. </p>

===Application program files ===
<p>
The application program may need data set or file definition statements of its own for various data sets. Be careful not to specify file names that are the same as the names of any of the data set or file definition statements needed by the Host Language Interface itself.</p>

==IFAM4 jobs: Job errors and ABENDs ==
<p>
Follow the guidelines in the following table for troubleshooting IFAM4 job ABEND codes.  </p>
<table>
<p class="caption" style="width:550px">IFAM4 job ABEND codes</p>
<tr class="head">
<th>Code</th>
<th>Solution</th>
</tr>
<tr>
<td>S806</td>
<td>
<p>Check that the following items are correctly specified:</p>
<ol>
<li>Verify that IFAM4 is named IFAM4 in the link-edit.</li>
<li>Verify that the STEPLIB DD statement points to the library or libraries containing IFAM4 and the application program.</li>
<li>Verify that the application program is correctly specified in Column 1 of the first statement of IFAM4IN. </li>
</ol>
</td>
</tr>
<tr>
<td>S804 or S80A</td>
<td>
<p>Verify that the REUS option was specified in the link-edit of IFAM4.</p>
<p>The following conditions indicate that the REUS option was not specified in the link-edit of IFAM4:</p>
<ul>
<li>IFSTRT returns a completion code of 1001.</li>
<li>A message appears that monitor requested IFAM4 termination.</li>
<li>IBM messages indicate that there is not enough storage for GETMAINS.</li>
</ul>
<p>Follow either step one or two:</p>
<ol>
<li>If the REUS option was not specified, relink IFAM4.</li>
<li>If the REUS option was specified, increase REGION by 10K and add 3000 to the SPCORE parameter.
<p class="note"><b>Note:</b> The SPCORE parameter defaults to 12288 in IFAM4 and can be set in the PARM field of the EXEC statement or on User 0's parameter line.</p>
</li>
</ol>
</td>
</tr>
</table>

===Job step return codes===
<p>
IFAM4 sets the return code for the job step according to the highest completion code from Model 204 and the application program. </p>
<p>
IFAM4 returns the job step return codes for the error conditions listed below. </p>
<table>
<tr class="head">
<th>Code</th>
<th>Error condition</th>
</tr>
<tr>
<td>999</td>
<td>Model 204 is not initialized properly.</td>
</tr>
<tr>
<td>998</td>
<td>Either the application or Model 204 ABENDs.</td>
</tr>
</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>

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

[[Category: Host Language Interface]]