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: Gotilar Yozshuzuru
Country: Republic of Macedonia
Language: English (Spanish)
Genre: Environment
Published (Last): 25 March 2013
Pages: 276
PDF File Size: 19.18 Mb
ePub File Size: 18.88 Mb
ISBN: 564-9-97766-946-9
Downloads: 7362
Price: Free* [*Free Regsitration Required]
Uploader: Akisida

You should be as specific as possible when defining trap masks in Xpediter. The system automatically establishes an abend trap for all abends that occur on the terminal in region AOR1.

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

CICS Intercommunication

Performance in an intersystem environment This topic gives advice on improving aspects of CICS performance in a multi-system environment. The differences intercommnuication described below:. The dump will continue the abend and free both the mirror and 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 intercommunicarion.

Enter XASM to run the test transaction. If you set global traps for server programs in multiple regions, exit to CICS when you are done. Information Feedback Last updated: It is intended for system programmers, application designers, application developers, and technical support staff.

Because you cannot intercommunicatuon use the same terminal for the back-end transaction, you cannot predict the terminal ID. The following steps detail the debugging procedure:.

This will result in the missing of debugging sessions for the third trap mask.

Asynchronous processing Asynchronous processing distributes the processing required by an application between intercommunicating systems. When the Service Intercommunicafion 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. The system automatically establishes an abend trap for all abends that occurred on the terminal in region AOR1. If the test transaction executes in the TOR, set the traps there. Because the same terminal cannot always be used for the server program, it is impossible to predict the terminal ID.

Setting these breakpoints or traps can cause the terminal to hang if it is busy with the test transaction. Use the second terminal as described below to establish all breakpoints and traps in back-end transactions.

You can also stay on the List Abends screen 1. Receiving Service Providers immediately delete information pertaining to regions, sessions, and routing masks that were local to the Service Provider shutting down. The Primary Menu is displayed. If global traps are set for server programs in only one region, then you can remain in Xpediter. Set breakpoints, a program trace, or protection rules for the program in region AOR1. Enter XCB2 to run the test transaction.

Use the second terminal, as described below, to establish all breakpoints and traps in the server programs.

Because the first trap mask has asterisks in every field considered for routing, every transaction in scope for AOR1 will be routed to AOR1.

It could also be useful when debugging a transaction that has affinities that limit the execution of the application to only certain CICS regions. 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.

They use file control commands, temporary-storage commands, and other functions in the same way. 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.

Assuming that the client program is associated with a terminal, use that terminal to observe events in the test transaction. Process global parameters XDGB xxxx. The method of setting breakpoints depends on whether an application is running in the local or remote region. Proceed as normal for debugging other transactions. The actual transaction names may vary. Repeat Step 8 as required for additional AORs.


2.0 Part 2. Installation and system definition

Wednesday, 31 May http: 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. 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.

At this point, the system allows single-stepping, resuming, and other available functions. Defining intercommunication resources This topic tells you how to define the various resources that may be required in a CICS intercommunication environment. Intercommunication concepts and facilities This section describes the basic concepts of CICS intercommunication and the various facilities that are provided.

This lockout escape procedure is not a recommended debugging technique. In most cases, these observations provide the information needed to debug the program. Most recently used routing would be used gjide the programmer wants to reestablish or terminate the most recent debugging session.

Intercommunication Considerations

Application programming in an intersystem environment This topic of the manual describes the application programming aspects of CICS intercommunication. Distributed program links, once routed into an AOR, no longer match the trap criteria because of the impact of routing. This may also prevent execution of Xpediter transactions.

It is convenient gudie stay on the List Abends screen 1.