HLI: IFAM2 CICS processing - Revision history

JAL: add links

2017-04-04T22:32:16Z

add links

← Older revision		Revision as of 22:32, 4 April 2017
Line 10:		Line 10:
	==CICS program link-editing requirements==		==CICS program link-editing requirements==
	<p>		<p>
	The version of IFENTPS that is link-edited with your program must be assembled specifically for either macro- or command-level program code. To do this, set the conditional assembly flag &IFCALLR in the CICFG copy member. </p>		The version of [[CICS interface configuration#CICS interface components\|IFENTPS]] that is link-edited with your program must be assembled specifically for either macro- or command-level program code. To do this, set the conditional assembly flag <code>&IFCALLR</code> in the CICFG copy member. </p>
	<p>		<p>
	IFENTPS requires that register 13 contain the following address. </p>		IFENTPS requires that register 13 contain the following address. </p>
Line 18:		Line 18:
	<th>Register 13 must contain...</th>		<th>Register 13 must contain...</th>
	</tr>		</tr>

	<tr>		<tr>
	<td>Macro-level module</td>		<td>Macro-level module</td>
	<td>18-word register save area</td>		<td>18-word register save area</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Command-level module</td>		<td>Command-level module</td>
Line 39:		Line 41:
	===Transaction work area (TWA)===		===Transaction work area (TWA)===
	<p>		<p>
	The IFAM2 interface requires 88 bytes of CICS TWA area. When preparing an application program, ensure that the 88 bytes of the Transaction Work Area (TWA) are reserved for the CICS/Model 204 interface. The Model 204 TWA area may be displaced within the TWA area if application programs require the TWA area. </p>		The IFAM2 interface requires 88 bytes of CICS TWA area. When preparing an application program, ensure that the 88 bytes of the Transaction Work Area (TWA) are reserved for the CICS/Model 204 interface. The Model 204 TWA area may be displaced within the TWA area if application programs require the TWA area. </p>
	<p>		<p>
	The area that Model 204 uses may be displaced within the TWA by setting the &IFTWADP in the CICFG copy member. The &IFTWADP value in the CICFG copy member specifies the number of bytes to displace the Model 204 TWA area. The value must be expressed in multiples of four because the Model 204 TWA area fullword-aligns. </p>		The area that Model 204 uses may be displaced within the TWA by setting the <code>&IFTWADP</code> in the CICFG copy member. The <code>&IFTWADP</code> value in the CICFG copy member specifies the number of bytes to displace the Model 204 TWA area. The value must be expressed in multiples of four because the Model 204 TWA area fullword-aligns. </p>

	<p class="note"><b>Note:</b> Both IFENTPS and IFPS must be assembled with the same CICFG copy member values. The TWA area is used to pass parameters between the two and, thus, must refer to the same area. </p>		<p class="note"><b>Note:</b> Both IFENTPS and IFPS must be assembled with the same CICFG copy member values. The TWA area is used to pass parameters between the two and, thus, must refer to the same area. </p>
	<p>		<p>
	Your installation might include several compatible versions of IFENTPS and IFPS for applications that use different TWA areas. The CICS load module name that IFENTPS is linked to and its name in the CICS load library can be specified in &IFAM2LM within the CICFG copy member. During installation, take care that IFENTPS and IFPS are generated in compatible sets. </p>		Your installation might include several compatible versions of IFENTPS and IFPS for applications that use different TWA areas. The CICS load module name that IFENTPS is linked to and its name in the CICS load library can be specified in <code>&IFAM2LM</code> within the CICFG copy member. During installation, take care that IFENTPS and IFPS are generated in compatible sets. </p>
	<p>		<p>
	For example, consider a version of IFENTPS that has its TWA area displaced by 20 bytes and needs to link to a version of IFPS that also expects its TWA area to be displaced by 20 bytes. If the reference to the TWA area is the same, both a macro-level and a command-level version of IFENTPS can refer to the same copy of IFPS.</p>		For example, consider a version of IFENTPS that has its TWA area displaced by 20 bytes and needs to link to a version of IFPS that also expects its TWA area to be displaced by 20 bytes. If the reference to the TWA area is the same, both a macro-level and a command-level version of IFENTPS can refer to the same copy of IFPS.</p>
Line 81:		Line 83:

	===COBOL2 example of addressing the CICS areas===		===COBOL2 example of addressing the CICS areas===
	<p>The following excerpt from a COBOL2 program illustrates how you can address the CICS areas (CSA and TWA) for the interface from command-level CICS.</p>		<p>
			The following excerpt from a COBOL2 program illustrates how you can address the CICS areas (CSA and TWA) for the interface from command-level CICS.</p>
	<p class="code"><nowiki>IDENTIFICATION DIVISION.		<p class="code"><nowiki>IDENTIFICATION DIVISION.
	.		.
Line 111:		Line 114:
	===Temporary storage queue===		===Temporary storage queue===
	<p>		<p>
	A temporary storage queue is created for each Host Language Interface transaction when the IFSTRT or IFDIAL call is issued. No other user program can use this queue. The name of the queue is:</p>		A temporary storage queue is created for each Host Language Interface transaction when the <var>IFSTRT</var> or <var>IFDIAL</var> call is issued. No other user program can use this queue. The name of the queue is:</p>
	<p>CCA<var class="term">Ixxxx</var>		<p>CCA<var class="term">Ixxxx</var>
	</p>		</p>
	<p>where <var class="term">xxxx</var> is equal to EIBTRMID</p>		<p>
			where <var class="term">xxxx</var> is equal to EIBTRMID.</p>

	==CICS abend handling==		==CICS abend handling==
Line 126:		Line 130:
	===How to deactivate IFAM2 abend handling===		===How to deactivate IFAM2 abend handling===
	<p>		<p>
	To deactivate the automatic IFAM2 abend handling, set the &IFABEND parameter in the CICFG copy member to NO. </p>		To deactivate the automatic IFAM2 abend handling, set the <code>&IFABEND</code> parameter in the CICFG copy member to <code>NO</code>. </p>

	===Protecting against abend exposure===		===Protecting against abend exposure===
Line 132:		Line 136:
	Because CICS cancels abend handlers for pseudo conversational waits, an exposure gap in abend protection occurs after each pseudo conversational wait. During the time an application restarts after a pseudo conversational wait and before its next IFAM2 call, the transaction can abend without invoking the IFAM2 abend handler. </p>		Because CICS cancels abend handlers for pseudo conversational waits, an exposure gap in abend protection occurs after each pseudo conversational wait. During the time an application restarts after a pseudo conversational wait and before its next IFAM2 call, the transaction can abend without invoking the IFAM2 abend handler. </p>
	<p>		<p>
	To prevent such an exposure, the application program must establish an abend handler immediately upon entering the program. This abend handler must call IFFNSH to close all CRAM channels and release all CICS resources, and must contain any application-specific logic. The program examples in the next section show coding that protects against this abend exposure.</p>		To prevent such an exposure, the application program must establish an abend handler immediately upon entering the program. This abend handler must call <var>IFFNSH</var> to close all CRAM channels and release all CICS resources, and must contain any application-specific logic. The program examples in the next section show coding that protects against this abend exposure.</p>
	<p>		<p>
	If the application does not require its own abend handler, it can use the IFAM2 call, IFABXIT, which establishes the IFAM2 abend handler. IFABXIT is specific to the CICS environment and is for the convenience of the programmer.</p>		If the application does not require its own abend handler, it can use the IFAM2 call, <var>IFABXIT</var>, which establishes the IFAM2 abend handler. <var>IFABXIT</var> is specific to the CICS environment and is for the convenience of the programmer.</p>
	<p>		<p>
	Call IFABXIT as soon as possible after entering the program but only after the initial IFCSA call, which still must be the first call of any IFAM2 application session. The IFABXIT call protects the application against hung CRAM channels in the event of an abend prior to the first functional IFAM2 call. </p>		Call <var>IFABXIT</var> as soon as possible after entering the program but only after the initial <var>IFCSA</var> call, which still must be the first call of any IFAM2 application session. The <var>IFABXIT</var> call protects the application against hung CRAM channels in the event of an abend prior to the first functional IFAM2 call. </p>

	===How IFAM2 abend handling operates===		===How IFAM2 abend handling operates===
	<p>		<p>
	The Model 204 IFAM2 abend handler is set by the first IFAM2 CICS call (other than IFCSA) and remains active until an IFHNGUP or IFFNSH call occurs, the transaction ends, or a pseudo conversational wait is entered. After a pseudo conversational wait, the abend handler is reset on the next IFAM2 call.</p>		The Model 204 IFAM2 abend handler is set by the first IFAM2 CICS call (other than <var>IFCSA</var>) and remains active until an <var>IFHNGUP</var> or <var>IFFNSH</var> call occurs, the transaction ends, or a pseudo conversational wait is entered. After a pseudo conversational wait, the abend handler is reset on the next IFAM2 call.</p>
	<p>		<p>
	When it is invoked, the IFAM2 abend handler supersedes any user abend handler, operating differently in the macro- and command-level environments: </p>		When it is invoked, the IFAM2 abend handler supersedes any user abend handler, operating differently in the macro- and command-level environments: </p>
Line 147:		Line 151:
	Macro-level coded applications cannot use the PUSH and POP commands. Applications that need their abend handler to be in effect after an IFAM2 call must reset their abend handler after returning from each IFAM2 call. </li>		Macro-level coded applications cannot use the PUSH and POP commands. Applications that need their abend handler to be in effect after an IFAM2 call must reset their abend handler after returning from each IFAM2 call. </li>
	<li>		<li>
	For command-level applications, the IFAM2 interface issues a PUSH HANDLE command to save the existing application's abend handler before establishing the IFAM2 abend handler.		For command-level applications, the IFAM2 interface issues a <code>PUSH HANDLE</code> command to save the existing application's abend handler before establishing the IFAM2 abend handler.

	<p>In the event of an abend, the IFAM2 interface releases all CRAM channels and CICS resources. It issues a POP HANDLE command to restore the application's abend handler and then issues an abend call. The abend call drives the application's abend handler.</p>		<p>In the event of an abend, the IFAM2 interface releases all CRAM channels and CICS resources. It issues a <code>POP HANDLE</code> command to restore the application's abend handler and then issues an abend call. The abend call drives the application's abend handler.</p>
	</li>		</li>
	</ul>		</ul>

JAL: /* Overview */ add link

2017-04-04T22:21:03Z

Overview: add link

← Older revision		Revision as of 22:21, 4 April 2017
Line 3:		Line 3:
	<p>		<p>
	This topic describes special requirements of CICS programs for application programmers who are using the Host Language Interface facility. </p>		This topic describes special requirements of CICS programs for application programmers who are using the Host Language Interface facility. </p>
			<p>
	<p>See [[HLI: Job requirements]] for information about HLI jobs running in IFAM2 under CICS.</p>		See [[HLI: Job requirements]] for information about HLI jobs running in IFAM2 under CICS.</p>
			<p>
			See [[CICS interface configuration]] for information about the Model 204 CICS interface components. </p>

	==CICS program link-editing requirements==		==CICS program link-editing requirements==

ELowell: /* Overview */

2016-07-16T00:55:03Z

Overview

← Older revision		Revision as of 00:55, 16 July 2016
Line 4:		Line 4:
	This topic describes special requirements of CICS programs for application programmers who are using the Host Language Interface facility. </p>		This topic describes special requirements of CICS programs for application programmers who are using the Host Language Interface facility. </p>

	<p>~~Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var>~~ for information about HLI jobs running in IFAM2 under CICS.</p>		<p>See [[HLI: Job requirements]] for information about HLI jobs running in IFAM2 under CICS.</p>

	==CICS program link-editing requirements==		==CICS program link-editing requirements==

ELowell at 16:39, 29 April 2016

2016-04-29T16:39:24Z

← Older revision		Revision as of 16:39, 29 April 2016
Line 299:		Line 299:

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

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

ELowell: Created page with " ==Overview==
This topic describes special requirements of CICS programs for application programmers who are using the Host Language Interface facility.

Refer to..."

2016-01-29T23:15:34Z

Created page with " ==Overview== This topic describes special requirements of CICS programs for application programmers who are using the Host Language Interface facility. Refer to..."

New page

==Overview==

This topic describes special requirements of CICS programs for application programmers who are using the Host Language Interface facility. 

Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for information about HLI jobs running in IFAM2 under CICS.

==CICS program link-editing requirements==

The version of IFENTPS that is link-edited with your program must be assembled specifically for either macro- or command-level program code. To do this, set the conditional assembly flag &IFCALLR in the CICFG copy member. 

IFENTPS requires that register 13 contain the following address. 
<table>
<tr class="head">
<th>For...</th>
<th>Register 13 must contain...</th>
</tr>
<tr>
<td>Macro-level module</td>
<td>18-word register save area</td>
</tr>
<tr>
<td>Command-level module</td>
<td>DFHEISTG storage area</td>
</tr>
</table>

==CICS application program work areas==

Before issuing any IFAM2 call, ensure that you can address the following CICS areas: 
<ul>
<li>Common System Area (CSA)</li>
<li>Task Control Area (TCA) </li>
<li>Transaction Work Area (TWA) </li>
</ul>

===Transaction work area (TWA)===

The IFAM2 interface requires 88 bytes of CICS TWA area. When preparing an application program, ensure that the 88 bytes of the Transaction Work Area (TWA) are reserved for the CICS/Model 204 interface. The Model 204 TWA area may be displaced within the TWA area if application programs require the TWA area. 

The area that Model 204 uses may be displaced within the TWA by setting the &IFTWADP in the CICFG copy member. The &IFTWADP value in the CICFG copy member specifies the number of bytes to displace the Model 204 TWA area. The value must be expressed in multiples of four because the Model 204 TWA area fullword-aligns. 

Note: Both IFENTPS and IFPS must be assembled with the same CICFG copy member values. The TWA area is used to pass parameters between the two and, thus, must refer to the same area. 

Your installation might include several compatible versions of IFENTPS and IFPS for applications that use different TWA areas. The CICS load module name that IFENTPS is linked to and its name in the CICS load library can be specified in &IFAM2LM within the CICFG copy member. During installation, take care that IFENTPS and IFPS are generated in compatible sets. 

For example, consider a version of IFENTPS that has its TWA area displaced by 20 bytes and needs to link to a version of IFPS that also expects its TWA area to be displaced by 20 bytes. If the reference to the TWA area is the same, both a macro-level and a command-level version of IFENTPS can refer to the same copy of IFPS.

===COBOL example of addressing the CICS areas===

The following excerpt from a COBOL program illustrates how you can address the CICS areas (CSA, TCA, and TWA) for the interface from command-level CICS. You can also use this interface with macro-level CICS. 
IDENTIFICATION DIVISION.
.
.
.
DATA DIVISION.
WORKING-STORAGE SECTION.
.
.
.
LINKAGE-SECTION.
01 DYNAMIC-STORAGE-POINTERS.
05 FILLER PIC S9(8) COMP.
05 CSA-POINTER PIC S9(8) COMP.
05 TCA-POINTER PIC S9(8) COMP.
05 TWA-POINTER PIC S9(8) COMP.
COPY DFHCSADS.
COPY DFHTCADS.
01 TWA-AREA.
05 M204-INTERFACE-PORTION PIC X(88).
05 YOUR-TWA-PORTION PIC X(?).
PROCEDURE DIVISION.
EXEC CICS ADDRESS CSA(CSA-POINTER) END-EXEC.
SERVICE RELOAD DFHCSADS.
MOVE CSACDTA TO TCA-POINTER.
SERVICE RELOAD DFHTCADS.
EXEC CICS ADDRESS TWA(TWA-POINTER) END-EXEC.
CALL 'IFCSA' USING DFHCSADS. 

===COBOL2 example of addressing the CICS areas===
The following excerpt from a COBOL2 program illustrates how you can address the CICS areas (CSA and TWA) for the interface from command-level CICS.
<nowiki>IDENTIFICATION DIVISION.
.
.
.
DATA DIVISION.
WORKING-STORAGE SECTION.
*
*
*
01WK-ADR.
03CSA-POINTERPOINTER.
03TWA-POINTERPOINTER.
*
*
*
LINKAGE-SECTION.
COPY DFHCSADS.
*
PROCEDURE DIVISION.
*
*
EXEC CICS ADDRESS CSA(WKPTR1) END-EXEC.
EXEC CICS ADDRESS TWA(WKPTR2) END-EXEC.
SET ADDRESS OF DFHCSADS TO CSA-POINTER.
SET ADDRESS OF TWA-AREA TO TWA-POINTER.
CALL 'IFCSA' USING DFHCSADS. </nowiki>

===Temporary storage queue===

A temporary storage queue is created for each Host Language Interface transaction when the IFSTRT or IFDIAL call is issued. No other user program can use this queue. The name of the queue is:
CCA<var class="term">Ixxxx</var>

where <var class="term">xxxx</var> is equal to EIBTRMID

==CICS abend handling==

The Model 204 IFAM2 interface provides automatic abend handling that operates along with your application program abend handler, if any.

Whenever an abend occurs, open CRAM channels must be cleaned up and CICS resources must be released. If the IFAM2 abend handler is not in effect, the user application abend handler must perform these tasks. If the IFAM2 abend handler is in effect, the IFAM2 abend handler supersedes any user abend handler and performs these tasks automatically.

This section provides an overview of IFAM2 abend handling, followed by examples of suggested abend handling. 

===How to deactivate IFAM2 abend handling===

To deactivate the automatic IFAM2 abend handling, set the &IFABEND parameter in the CICFG copy member to NO. 

===Protecting against abend exposure===

Because CICS cancels abend handlers for pseudo conversational waits, an exposure gap in abend protection occurs after each pseudo conversational wait. During the time an application restarts after a pseudo conversational wait and before its next IFAM2 call, the transaction can abend without invoking the IFAM2 abend handler. 

To prevent such an exposure, the application program must establish an abend handler immediately upon entering the program. This abend handler must call IFFNSH to close all CRAM channels and release all CICS resources, and must contain any application-specific logic. The program examples in the next section show coding that protects against this abend exposure.

If the application does not require its own abend handler, it can use the IFAM2 call, IFABXIT, which establishes the IFAM2 abend handler. IFABXIT is specific to the CICS environment and is for the convenience of the programmer.

Call IFABXIT as soon as possible after entering the program but only after the initial IFCSA call, which still must be the first call of any IFAM2 application session. The IFABXIT call protects the application against hung CRAM channels in the event of an abend prior to the first functional IFAM2 call. 

===How IFAM2 abend handling operates===

The Model 204 IFAM2 abend handler is set by the first IFAM2 CICS call (other than IFCSA) and remains active until an IFHNGUP or IFFNSH call occurs, the transaction ends, or a pseudo conversational wait is entered. After a pseudo conversational wait, the abend handler is reset on the next IFAM2 call.

When it is invoked, the IFAM2 abend handler supersedes any user abend handler, operating differently in the macro- and command-level environments: 
<ul>
<li>
Macro-level coded applications cannot use the PUSH and POP commands. Applications that need their abend handler to be in effect after an IFAM2 call must reset their abend handler after returning from each IFAM2 call. </li>
<li>
For command-level applications, the IFAM2 interface issues a PUSH HANDLE command to save the existing application's abend handler before establishing the IFAM2 abend handler.

In the event of an abend, the IFAM2 interface releases all CRAM channels and CICS resources. It issues a POP HANDLE command to restore the application's abend handler and then issues an abend call. The abend call drives the application's abend handler.
</li>
</ul>

==CICS abend handling: macro-level program==

The following table shows recommended IFAM2 abend handling for a macro-level program. 

This example assumes that the application's abend handler calls IFFNSH to clean up open IFAM2 CRAM channels and CICS resources.
<table>
<caption>CICS Macro-level program</caption>
<tr class="head">
<th>Step</th>
<th>Program flow</th>
<th>Abend handler in effect</th>
</tr>
<tr>
<td>1.</td>
<td>Transaction start</td>
<td>No abend handler active</td>
</tr>
<tr>
<td>2.</td>
<td>IFCSA call</td>
<td>No abend handler active</td>
</tr>
<tr>
<td>3.</td>
<td>Next IFAM2 call</td>
<td>IFAM2 abend handler active</td>
</tr>
<tr>
<td>4.</td>
<td>Pseudo conversational wait</td>
<td>IFAM2 abend handler canceled</td>
</tr>
<tr>
<td>5.</td>
<td>Transaction restart</td>
<td>No abend handler active, exposure from CRAM channel recovery</td>
</tr>
<tr>
<td>6.</td>
<td>DFHPC TYPE=ABEND (or IFABXIT)</td>
<td>User abend handler active (IFAM2 abend handler active)</td>
</tr>
<tr>
<td>7.</td>
<td>IFAM2 call</td>
<td>IFAM2 abend handler active</td>
</tr>
<tr>
<td>8.</td>
<td>DFHPC TYPE=ABEND</td>
<td>User abend handler reset</td>
</tr>
</table>

The following points describe each step in the program flow: 
<ol>
<li>
The transaction program starts. Because no Model 204 CRAM channels are open and CICS resources are not allocated, there is no exposure.</li>
<li>
An IFCSA call is issued. Prior to Model 204 Version 3.1, IFCSA had to be the first call of any IFAM2 application session. For Model 204 Version 3.1 and later, the IFCSA call is not required. For upward compatibility, the IFCSA call is allowed, but performs no function.</li>
<li>
The first IFAM2 call after IFCSA is issued. During this call, the IFAM2 interface, IFENTPS, establishes the Model 204 abend handler. This remains in effect until the program ends or enters a pseudo conversational wait.</li>
<li>
The transaction enters a pseudo conversational wait. CICS cancels the abend handler.</li>
<li>
The transaction program resumes. No abend handler is active until the application program issues the first IFAM2 call. If an abend occurs, the CRAM channels are not closed, resulting in hung CRAM channels. Any CICS resources, such as storage and queue entries, are not released.</li>
<li>
The transaction establishes its own abend handler as the first CICS call upon entry. Because the user abend handler is coded with an IFFNSH call, an abend within the user program calls the IFAM2 interface to close existing CRAM channels and release CICS resources.

Note: An alternative is to call IFABXIT, establishing the IFAM2 abend handler before any functional IFAM2 call. 
</li>
<li>
An IFAM2 call is issued. The IFAM2 abend handler goes into effect. </li>
<li>
The transaction reestablishes its own abend handler. Macro-level applications requiring their own abend handlers must reset their own abend handlers after each IFAM2 call. </li>
</ol>

==CICS abend handling: command-level program==

The following table shows recommended IFAM2 abend handling for a command-level program.

This example assumes that the application's abend handler calls IFFNSH to clean up open IFAM2 CRAM channels and CICS resources.
<table>
<caption>CICS command-level program</caption>
<tr class="head">
<th>Step</th>
<th>Program flow</th>
<th>Abend handler in effect</th>
</tr>
<tr>
<td>1.</td>
<td>Transaction start</td>
<td>No abend handler active</td>
</tr>
<tr>
<td>2.</td>
<td>IFCSA call</td>
<td>No abend handler active</td>
</tr>
<tr>
<td>3.</td>
<td>Next IFAM2 call</td>
<td>IFAM2 abend handler active</td>
</tr>
<tr>
<td>4.</td>
<td>Pseudo conversational wait</td>
<td>IFAM2 abend handler canceled</td>
</tr>
<tr>
<td>5.</td>
<td>Transaction restart</td>
<td>No abend handler active. Exposure from CRAM channel recovery.</td>
</tr>
<tr>
<td>6.</td>
<td>HANDLE ABEND (OR IFABXIT)</td>
<td>User abend handler active (IFAM2 abend handler active)</td>
</tr>
<tr>
<td>7.</td>
<td>IFAM2 call</td>
<td>IFAM2 abend handler active</td>
</tr>
</table>

The following points describe each step in the program flow:

<ol>
<li>The transaction program starts.</li>
<li>
An IFCSA call is issued. The IFCSA call is not required; it is allowed for compatibility with pre-3.1 versions of Model 204, but it performs no function.</li>
<li>
The first IFAM2 call after IFCSA is issued. During this call, the IFAM2 interface, IFENTPS, establishes the Model 204 abend handler. This remains in effect until the program ends or enters a pseudo conversational wait.</li>
<li>
The transaction enters a pseudo conversational wait. CICS cancels the current abend handler.</li>
<li>
The transaction restarts.</li>
<li>
The transaction establishes its abend handler as the first CICS call upon entry. because the user abend handler is coded with an IFFNSH call, an abend within the user program calls the IFAM2 interface to close existing CRAM channels and release CICS resources.

Note: An alternative is to call IFABXIT, establishing the IFAM2 abend handler before any functional IFAM2 call. 
</li>
<li>
An IFAM2 call is issued. The IFAM2 call sets its own abend handler, which remains in effect until altered. </li>
</ol>

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

[[Category: Host Language Interface]]

HLI: IFAM2 CICS processing - Revision history

JAL: add links

JAL: /* Overview */ add link

ELowell: /* Overview */

ELowell at 16:39, 29 April 2016

ELowell: Created page with " ==Overview== This topic describes special requirements of CICS programs for application programmers who are using the Host Language Interface facility. Refer to..."

ELowell: Created page with " ==Overview==
This topic describes special requirements of CICS programs for application programmers who are using the Host Language Interface facility.

Refer to..."