Interval control

The CICS® interval control services provide functions that are related to time.

Java and C++

The application programming interface described in this chapter is the EXEC CICS API, which is not used in Java™ programs. For information about Java programs using the JCICS classes to access Interval Control services, see the Java Applications in CICS component of the CICS Information Center and the JCICS Javadoc html documentation. For information about C++ programs using the CICS C++ classes, see the CICS C++ OO Class Libraries manual.

Using interval control commands, you can:

Note:
Do not use EXEC CICS START TRANSID() TERMID(EIBTRMID) to start a remote transaction. Use EXEC CICS RETURN TRANSID() IMMEDIATE instead. START, used in this way, ties up communications resources unnecessarily and can lead to performance degradation across the connected regions.

If you use WAIT EVENT, START, RETRIEVE with the WAIT option, CANCEL, DELAY, or POST commands, you could create inter-transaction affinities that adversely affect your ability to perform dynamic transaction routing.

Storage for the timer-event control area on WAIT EVENT must reside in shared storage if you have specified ISOLATE(YES).

If CICS is executing with or without transaction isolation, CICS checks that the timer-event control area is not in read-only storage.

To help you identify potential problems with programs that issue these commands, you can use the Start of changeCICS Interdependency AnalyzerEnd of change. See the CICS Interdependency Analyzer for z/OS User's Guide and Reference for more information about this utility and Affinity for more information about transaction affinity.

This chapter describes:

[[ Contents Previous Page | Next Page Index ]]