IFABXIT (HLI function): Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (3 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== | ||
<dl> | <dl> | ||
<dt>Description | <dt>Description</dt> | ||
<dd>The IFABXIT call (ABEND EXIT) establishes the IFAM2 abend handler. | <dd>The IFABXIT call (ABEND EXIT) establishes the IFAM2 abend handler. | ||
<p>IFABXIT is available only for use with the IFAM2 CICS interface. </p> | <p>IFABXIT is available only for use with the IFAM2 CICS interface. </p></dd> | ||
<dt>Thread type | <dt>Thread type</dt> | ||
<dd>multiple cursor IFSTRT, single cursor IFSTRT | <dd>multiple cursor IFSTRT, single cursor IFSTRT</dd> | ||
<dt>IFCALL function number | <dt>IFCALL function number</dt> | ||
<dd>97 | <dd>97</dd> | ||
</dl> | </dl> | ||
| Line 16: | Line 16: | ||
<dl> | <dl> | ||
<dt>Compile-only form | <dt>Compile-only form</dt> | ||
<dd>Not available | <dd>Not available</dd> | ||
<dt>Execute-only form | <dt>Execute-only form</dt> | ||
<dd>Not available | <dd>Not available</dd> | ||
</dl> | </dl> | ||
| Line 41: | Line 41: | ||
CALL "IFABXIT".</p> | CALL "IFABXIT".</p> | ||
[[Category: HLI | [[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".