Browse Prior Art Database

Condition/Error Handling for CICS Resource Objects

IP.com Disclosure Number: IPCOM000117882D
Original Publication Date: 1996-Jul-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 2 page(s) / 40K

Publishing Venue

IBM

Related People

Bordoli, RA: AUTHOR

Abstract

Each CICS API call is capable of returning one or more condition values that represent the outcome of the requested CICS* call. If the application is written in C the programmer must test the returned condition code after every CICS API call (or call another function to do the analysis). If the application is written in COBOL the programmer can request that CICS causes program execution to branch to a certain label if a certain condition is encountered. A problem arises when a particular CICS condition may be expected in one application scenario while in another it would be considered a definite error condition that requires handling or requires that the application be immediately terminated in order to maintain transactional integrity.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 84% of the total text.

Condition/Error Handling for CICS Resource Objects

      Each CICS API call is capable of returning one or more
condition values that represent the outcome of the requested CICS*
call.  If the application is written in C the programmer must test
the returned condition code after every CICS API call (or call
another function to do the analysis).  If the application is written
in COBOL the programmer can request that CICS causes program
execution to branch to a certain label if a certain condition is
encountered.  A problem arises when a particular CICS condition may
be expected in one application scenario while in another it would be
considered a definite error condition that requires handling or
requires that the application be immediately terminated in order to
maintain transactional integrity.  This results in a significant
amount of (often repeated or similar) application code to handle all
possible conditions that CICS may return.

      The problem is effectively dealt with by requiring, in the CICS
Foundation Classes, each CICS object to store state to indicate what
action is required for each CICS condition.  Thus, a CICS file object
can be configured such that a particular CICS condition causes the
application to be automatically terminated by the Foundation Classes.
Another object can be configured such that the CICS condition causes
a function to be automatically invoked before returning program
control to the next application code statement.  Anothe...