CICS System Definition Guide. Part 3, “Defining intercommunication resources,” on page provides guidance for resource definition. It tells you how to define. Introduction to CICS intercommunication. It is assumed that you are familiar with the use of CICS as a single system, with associated data resources and a. Recovery and restart in interconnected systems. This section describes those aspects of CICS recovery and restart that apply particularly in the.
|Published (Last):||9 February 2004|
|PDF File Size:||7.81 Mb|
|ePub File Size:||16.66 Mb|
|Price:||Free* [*Free Regsitration Required]|
1.1 Introduction to CICS intercommunication
When completed, request a dump from the Exit Session screen. Local or remote traps may be used. If you set global traps for server programs in multiple regions, exit to CICS when you are done.
The system automatically establishes an abend trap for all abends that occurred on the terminal in region AOR1.
Workload balancing routing would be used when a programmer knows that the transactions to be debugged do not have affinities and the CICSplex is composed of identical members.
Because you cannot always use the same terminal for the back-end transaction, you cannot predict the terminal ID. Information Feedback Last updated: Enter the test transaction name TST1 to run the test transaction. You should be as specific as possible when defining trap masks in Xpediter.
The processing is independent of the sessions on which requests are sent and replies are received.
If global ccs are set for back-end transactions in multiple regions, exit to CICS after setting breakpoints, traps, etc. The second abend trap is of little use, and it can lead to the false conclusion that a second terminal abend has occurred. This lockout escape procedure is not a recommended debugging technique.
The Primary Menu is displayed. It is convenient to stay on the List Abends screen 1.
Enter Guice to run the test transaction. Installing and configuring intercommunication support There are different installation and configuration requirements depending on whether a CICS system is to participate in intersystem communication or multiregion operation.
Set breakpoints, a program trace, or protection rules for the program in region AOR1. If global traps are set for server programs in only one region, then you can remain in Xpediter. Use the second terminal, as described below, to establish all breakpoints and traps in the server programs. Defining intercommunication resources This topic tells you how to define the various resources that may be required in a CICS intercommunication environment.
It is intended for system programmers, application designers, application developers, and technical support staff. Performance in an intersystem environment Intercomkunication topic gives advice intercommuniation improving aspects of CICS performance in a multi-system environment.
Because the same terminal cannot always be gguide for the server program, it is impossible to predict the terminal ID. This may also prevent execution of Xpediter transactions. The dump will continue the abend and free both the mirror and the test transaction.
Repeat Step 8 as required for additional AORs.
EDITION Edition Notice
Distributed transaction processing The technique of distributing the functions of a transaction over several transaction programs within a network is called distributed transaction processing DTP. Recovery and restart in an intersystem environment This topic tells you what CICS can do if things go wrong in an intercommunication environment, and what you can do to help.
Setting these breakpoints or traps can cause the terminal to hang if it is busy with the test transaction. The differences are described below:. Intercommunication concepts and facilities This section describes the basic concepts of CICS intercommunication and the various facilities that are provided.
The guife steps detail the debugging procedure:. They use file control commands, temporary-storage commands, and other functions in the same way.
You can set a local trap for abends at the primary terminal. If the test transaction executes in the TOR, set the traps there. At this point, the system allows single-stepping, resuming, and other available functions. Use the second terminal as described below to establish all breakpoints intercomminication traps in back-end transactions.