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.

Author: Guk Zulurn
Country: Nepal
Language: English (Spanish)
Genre: Marketing
Published (Last): 25 August 2008
Pages: 351
PDF File Size: 4.40 Mb
ePub File Size: 3.78 Mb
ISBN: 119-1-90063-295-1
Downloads: 86903
Price: Free* [*Free Regsitration Required]
Uploader: Arakora

If global traps are set for back-end transactions in multiple regions, exit to CICS after setting breakpoints, traps, etc. Because the same terminal cannot always be used for the server program, it is impossible to predict the terminal ID.

Enter XCB2 to run the test transaction. Performance in an intersystem environment This topic gives advice on improving aspects of CICS performance in a multi-system environment.

The steps below simplify the task of initiating Xpediter sessions in multiple AORs. Intercommunication concepts and facilities This section describes the basic concepts of CICS intercommunication and the various facilities that are provided.

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. Specific region routing would be used when a programmer wants the Xpediter transaction to routed to a specific CICS region. You should be as specific as possible when defining trap masks in Xpediter.

Assuming that the client program is associated with a terminal, use that terminal to observe events in the test transaction. For example, entering the following Gukde transaction:. Assuming that the front-end transaction is associated with a terminal, use that terminal to observe events in the test transaction. The second abend trap is of little use, and it can lead to the false conclusion that a second terminal abend has occurred.

It is convenient to stay on the List Abends screen 1. Setting these breakpoints or traps can cause the terminal to hang if it is busy with the test transaction. Recovery and restart in an intersystem environment This topic tells you what CICS can do if things go wrong in an intercommunication environment, ijtercommunication what you can kntercommunication to help.


If global traps are set for server programs in only one region, then you can remain in Xpediter. Defining intercommunication resources This topic tells you how to define the various resources that may be required in a CICS intercommunication environment.

The system automatically establishes an abend trap for all abends that occurred on the terminal in region AOR1. You can also stay on the List Abends screen 1. This may also prevent execution of Xpediter transactions. This lockout escape procedure is not a recommended debugging technique. It could also be useful when debugging a transaction that has affinities that limit the execution of the application to only certain CICS regions.

EDITION “CICS Intercommunication Guide” IBM Library Server

Set breakpoints, a program trace, or protection rules for the program in region AOR1. This will result in the missing of debugging sessions for the third trap mask. At this point, the system allows single-stepping, resuming, and other available functions.

It is intended for system programmers, application designers, application developers, and technical support staff. Repeat Step 8 as required for additional AORs. Because you cannot always use the same terminal for the back-end transaction, you cannot predict the terminal ID.

Enter XASM to run the test transaction. Proceed as normal for debugging other transactions. If you set global traps for server programs in multiple regions, exit to CICS when you are done.

1.0 Part 1. Concepts and facilities

Receiving Service Providers immediately delete information pertaining to regions, sessions, and routing masks that were local to the Service Provider shutting down. If the test transaction executes in the TOR, set the traps there. The dump will continue the abend and free both the mirror and the test transaction. Use the second terminal as described below to establish all breakpoints and traps in back-end transactions.


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. Distributed program links, once routed into an AOR, no longer match the trap criteria because of the impact of routing.

In most cases, these observations provide the information needed to debug the program. Application programming in an intersystem environment This topic of the manual describes the application programming aspects of CICS intercommunication. Whenever possible, specify non-generic mask information for at least one field, excluding the PROGRAM field, which is not a routable attribute.

They use file control commands, temporary-storage commands, and other functions in the same way. Information Feedback Last updated: Most recently used routing would be used when the programmer wants to reestablish or terminate the most recent debugging session. This may overload the region and cause debugging sessions to be missed for the second and third trap masks.

Local or remote traps may be used. It is better to trap abends in the test transaction, where you can observe the tasks that enter and leave the function-shipping CICS call. You can set a local trap for abends at the primary terminal. Enter the test transaction name TST1 to run the test transaction.

The processing is independent of the sessions on which requests are sent and replies are received.

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. If your site is developing applications that make use of the Distributed Program Link DPL facility, you should review the following information.

When the Service Providers involved in a given CICSPlex are connected to each other, all region, session, and routing mask information is shared among them.