IFABXIT (HLI function): Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (ELowell moved page IFABXIT (HLI function call) to IFABXIT (HLI function): remove "function call" terminology; keep "function")
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
The conventions used on this page are described in [[HLI: Function summary#Function call notation conventions|Function call notation conventions]].
==Summary==
==Summary==
<p>
<dl>
The IFABXIT call (ABEND EXIT) establishes the IFAM2 abend handler.</p>
<dt>Description</dt>
<p>IFABXIT is available only for use with the IFAM2 CICS interface. </p>
<dd>The IFABXIT call (ABEND EXIT) establishes the IFAM2 abend handler.
<p>IFABXIT is available only for use with the IFAM2 CICS interface. </p></dd>
<dt>Thread type</dt>
<dd>multiple cursor IFSTRT, single cursor IFSTRT</dd>
<dt>IFCALL function number</dt>
<dd>97</dd>
</dl>


==Thread type==
==Syntax==
multiple cursor IFSTRT, single cursor IFSTRT


==Syntax==
===Full syntax (97)===
<p class="syntax">IFABXIT</p>
<p class="syntax">IFABXIT</p>


===Compile-only syntax===
<dl>
<p>
<dt>Compile-only form</dt>
A compile-only form of IFABXIT is not available.</p>
<dd>Not available</dd>
 
<dt>Execute-only form</dt>
===Execute-only syntax===
<dd>Not available</dd>
<p>
</dl>
An execute-only form of IFABXIT is not available.</p>


===Parameters===
<p>There are no parameters available with IFABXIT.</p>
<p>
No parameters available for use with the IFABXIT call.</p>


===Notes and tips===
==Usage notes==
<p>
<ul>
Use the IFABXIT call with an IFAM2 connection to Model 204 only in a CICS environment. </p>
<li>Use the IFABXIT call with an IFAM2 connection to Model 204 only in a CICS environment. </li>
<p>
<li>Use IFABXIT if the host language application does not require its own abend handler. Using IFABXIT protects the application against a hung CRAM channel in the event of an abend prior to the first functional IFAM2 call.</li>
Use IFABXIT if the host language application does not require its own abend handler. Using IFABXIT protects the application against a hung CRAM channel in the event of an abend prior to the first functional IFAM2 call. </p>
<li>Issue the IFABXIT call as soon as possible after entering the program, after the initial IFCSA call.</li>
<p>
<li>See [[HLI: IFAM2 CICS processing#CICS abend handling|CICS abend handling]] for more information about CICS abend handling in IFAM2.</li>
Issue the IFABXIT call as soon as possible after entering the program, after the initial IFCSA call. </p>
</ul>
<p>
See [[HLI: IFAM2 CICS processing#CICS abend handling|CICS abend handling]] for more information about CICS abend handling in IFAM2. </p>


==Coding example (COBOL)==
==Coding example (COBOL)==
Line 43: Line 41:
   CALL "IFABXIT".</p>
   CALL "IFABXIT".</p>


[[Category: HLI function calls]]
[[Category: HLI functions]]

Latest revision as of 22:02, 12 July 2016

The conventions used on this page are described in Function call notation conventions.

Summary

Description
The IFABXIT call (ABEND EXIT) establishes the IFAM2 abend handler.

IFABXIT is available only for use with the IFAM2 CICS interface.

Thread type
multiple cursor IFSTRT, single cursor IFSTRT
IFCALL function number
97

Syntax

IFABXIT

Compile-only form
Not available
Execute-only form
Not available

There are no parameters available with IFABXIT.

Usage notes

  • Use the IFABXIT call with an IFAM2 connection to Model 204 only in a CICS environment.
  • Use IFABXIT if the host language application does not require its own abend handler. Using IFABXIT protects the application against a hung CRAM channel in the event of an abend prior to the first functional IFAM2 call.
  • Issue the IFABXIT call as soon as possible after entering the program, after the initial IFCSA call.
  • See CICS abend handling for more information about CICS abend handling in IFAM2.

Coding example (COBOL)

. . . PROCEDURE DIVISION. . . CALL "IFABXIT".