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: Kazuru Fenrinris
Country: Finland
Language: English (Spanish)
Genre: Spiritual
Published (Last): 25 September 2017
Pages: 398
PDF File Size: 2.10 Mb
ePub File Size: 4.86 Mb
ISBN: 862-1-98391-582-9
Downloads: 53559
Price: Free* [*Free Regsitration Required]
Uploader: Narg

In most cases, these observations provide the information needed to debug the program. If you set global traps for server programs in multiple regions, exit to CICS when you are done.

If global traps are set for back-end transactions in multiple regions, exit to CICS after setting breakpoints, traps, etc. If global traps are set for server programs in only one region, then you can remain in Xpediter.

Intercommunication Guide

The inteercommunication automatically establishes an abend trap for all abends that occurred on the terminal in region AOR1.

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

Because the same terminal cannot always be used for the server program, it is impossible to predict the terminal ID. Whenever possible, specify non-generic mask information for at least one field, excluding the PROGRAM field, which is not a routable attribute. You can set a local trap for abends at the primary terminal. 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.

Distributed transaction processing The technique of distributing the functions of a transaction over several transaction programs within a network intercommunucation called distributed transaction processing DTP. Setting these breakpoints or traps can cause the terminal to intercommuhication if it intercpmmunication busy with the ijtercommunication transaction.


For example, entering the following Xpediter transaction:. Use the second terminal as described below to establish all breakpoints and traps in back-end transactions. Specific region routing would be used when a programmer wants the Xpediter transaction to routed to a specific CICS region. Enter XASM to run the test transaction. At this point, the system allows single-stepping, resuming, and other available functions.

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. When completed, request a dump from the Exit Session screen. Asynchronous processing Asynchronous processing distributes the processing required by an application between intercommunicating systems.

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

Distributed program guiee, once routed into an AOR, no longer match the trap criteria because of the impact of routing. This may overload the region and cause debugging sessions to be missed for the second and third trap masks. Assuming that the front-end transaction is associated with a terminal, use that terminal to observe events in the test transaction.

Proceed as normal for debugging other transactions. Process global parameters XDGB xxxx. You should be as specific as possible when defining intercommunicatio masks in Xpediter.

This lockout escape procedure is not a recommended debugging technique. The following steps detail the debugging procedure:. Use the second terminal, as described below, to establish all breakpoints and traps in the server programs. Workload intercommunicatiin 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.

Local or remote traps may be used. The steps below simplify the task of initiating Xpediter sessions in multiple AORs. Information Feedback Last updated: Intercommuncation recently used routing would be used when the programmer wants to reestablish or terminate the most recent debugging session.


The dump will continue the abend and free both the mirror and the test transaction. The actual transaction names may vary. This will result in the missing of debugging sessions for the third trap mask.

Intercommunication concepts and facilities This section describes the basic concepts of CICS intercommunication and the various facilities that are provided. Set breakpoints, a program trace, or protection rules for the program in region AOR1. Wednesday, 31 May http: It is guidr for system programmers, application designers, application developers, and technical support intetcommunication.

6.1 Recovery and restart in interconnected systems

The processing is independent of the sessions on which requests are sent and replies are received. Receiving Service Providers immediately delete information pertaining to regions, sessions, and routing masks that were local to the Service Provider shutting down.

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

This may also prevent execution of Xpediter transactions. 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. The method of setting breakpoints depends on whether an application is running in the local or gyide region.

Enter the test transaction name TST1 to run the test transaction.