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: Nikora Taull
Country: Serbia
Language: English (Spanish)
Genre: Marketing
Published (Last): 2 March 2016
Pages: 86
PDF File Size: 9.65 Mb
ePub File Size: 1.70 Mb
ISBN: 606-2-45493-232-9
Downloads: 12167
Price: Free* [*Free Regsitration Required]
Uploader: Shaktizahn

It could also be useful when debugging a transaction that has affinities that limit the execution of the application to only certain CICS regions. The steps below simplify the task of initiating Xpediter sessions in multiple AORs.

The guie will continue the abend and free both the mirror and the test transaction. Receiving Service Providers immediately delete information pertaining to regions, sessions, and routing masks that were local to the Service Provider shutting down.

“CICS Intercommunication Guide” IBM Library Server

Asynchronous processing Asynchronous processing distributes the processing required by an application between intercommunicating systems.

Because the first trap kntercommunication has asterisks in every field considered for routing, every transaction in scope for AOR1 will be routed to AOR1. If you set global traps for server programs in multiple regions, exit to CICS when you are done.

You can set a local trap for abends at the primary terminal. Specific region routing would be used when a programmer wants the Xpediter transaction to routed to a specific CICS region. 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.

Enter the test transaction name TST1 to run the test transaction. Because the same terminal cannot always be used for the server program, it is impossible to predict the terminal ID. The actual transaction names may vary.


This may overload the region and cause debugging sessions to be missed for the second and third trap masks. Because you cannot always use the same terminal for the back-end transaction, you cannot predict tuide terminal ID. It is intended for system programmers, application designers, application developers, and cifs support staff. In most guidde, these observations provide the information needed to debug the program.

Whenever possible, specify non-generic mask cicd for at least one field, excluding the PROGRAM field, which is not a routable attribute.

1.1 Introduction to CICS intercommunication

Performance in an intersystem environment This topic gives advice on improving aspects of CICS performance in a multi-system environment. It is convenient to stay on the List Abends screen 1. The second abend trap is of little use, and it can lead to the false conclusion that a second terminal abend has occurred.

Distributed program links, once routed into an AOR, no longer match the trap criteria because of the impact of routing.

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. Defining intercommunication resources This topic tells you how to define the various resources that may be required in a CICS intercommunication environment.

Enter XASM to run the test transaction. Set breakpoints, a program trace, or protection rules for the program in region AOR1. Most recently used routing would be used when the programmer wants to reestablish or terminate the most recent debugging session.

CICS Intercommunication

Process global parameters XDGB xxxx. At this point, the system allows single-stepping, resuming, and other available functions. Repeat Step 8 as required for additional AORs.


If your site is developing applications that make use of the Distributed Program Link DPL facility, you should review the following information. If global traps are set for back-end transactions in multiple regions, exit to CICS after setting breakpoints, traps, etc. Wednesday, 31 May http: For example, entering the following Xpediter transaction:.

If global inyercommunication are set for server programs in only one region, then you can remain in Xpediter. This may also prevent execution of Xpediter transactions.

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, and what you can do to help. The system automatically establishes an abend trap for all abends that occurred on the terminal in region AOR1. This will result in the missing of debugging sessions for the third trap mask.

When completed, request a dump from the Exit Session screen. Assuming that the front-end transaction is associated with a terminal, use that terminal to observe events in the test transaction. The processing is independent of the sessions on which requests are sent and replies are received.

Intercommunication concepts and facilities This section describes the basic concepts of CICS intercommunication and the various facilities that are provided. The system automatically establishes an abend trap for all abends that occur on the terminal in region AOR1. Proceed as normal for debugging other transactions.

The following steps detail the debugging procedure:.