CICS INTERCOMMUNICATION GUIDE PDF
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):||27 January 2004|
|PDF File Size:||13.67 Mb|
|ePub File Size:||8.13 Mb|
|Price:||Free* [*Free Regsitration Required]|
It is convenient to stay on the List Abends screen 1. Set breakpoints, a program trace, or protection rules for the program in region AOR1.
EDITION Edition Notice
It could also be useful when debugging a transaction that has affinities that limit the execution of the application to only certain CICS regions. Intercommnuication the second terminal as described below to establish all breakpoints and traps in back-end transactions.
Because you cannot always use the same terminal for the back-end transaction, you cannot predict the terminal ID. Intercommunication concepts and facilities This section describes the basic concepts of CICS intercommunication and the various facilities that are provided. The dump will continue the abend and free both the mirror and the test transaction.
Most recently used routing would be used when the programmer wants to reestablish or terminate the most recent debugging session. When completed, request a dump from the Exit Session screen. Defining intercommunication resources This topic tells you how to define the various resources that may be required in a CICS intercommunication environment. The ciccs is independent of the sessions on which requests are sent and replies are received.
The system automatically establishes an abend trap for all abends that occur on the terminal in region AOR1.
You can also stay on the List Abends screen 1. Performance in an intersystem environment This topic gives advice on improving aspects of CICS performance in a multi-system environment.
Use the second terminal, as described below, to establish all breakpoints and traps in the server programs. Information Feedback Last updated: Asynchronous processing Asynchronous processing distributes imtercommunication processing required by an application between intercommunicating systems.
Proceed as normal for debugging other transactions. Because the first trap mask has asterisks in every field considered for routing, every transaction in scope for AOR1 will be routed to AOR1. If the test transaction executes in the TOR, set the traps there.
In most cases, these observations interccommunication the information needed to debug the program. Whenever possible, specify non-generic mask information for at least one field, excluding the PROGRAM field, which is not a routable attribute.
You should be as specific as possible when defining trap masks in Xpediter. The system cucs establishes an abend trap for all abends that occurred on the terminal in region AOR1. 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. If global traps are set for server programs in only one region, then you can remain in Xpediter.
CICS – Intercommunication
At this point, the system allows single-stepping, resuming, and other available functions. You can set a local trap for abends at the primary terminal.
This lockout escape procedure is not a recommended debugging technique. This may also prevent execution of Xpediter transactions. The Primary Menu is displayed. The method of setting breakpoints depends on whether an application is running in the local or remote region.
PREFACE “CICS Intercommunication Guide” IBM Library Server
Intercomjunication that the client program is associated with a terminal, use that terminal to observe events in the test transaction. For example, entering the following Xpediter transaction:. Receiving Service Providers immediately delete information pertaining to regions, sessions, and routing masks that were local to the Service Provider shutting down.
This will result in the missing of debugging sessions for the third trap mask.