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):||20 May 2009|
|PDF File Size:||3.94 Mb|
|ePub File Size:||20.45 Mb|
|Price:||Free* [*Free Regsitration Required]|
The second abend trap is of little use, and it can lead to the false conclusion that a second terminal abend has occurred. If the test transaction executes in the TOR, set the traps cifs.
2.0 Part 2. Installation and system definition
Setting these breakpoints or traps can cause the terminal to hang if it is busy with the test transaction. When completed, request a dump from the Exit Session screen. The dump will continue the abend and free both the mirror and the test transaction.
Intercommunicatiin lockout escape procedure is not a recommended debugging technique. 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. In most cases, these observations provide the information needed to debug the program. The following steps detail the debugging procedure:. The Primary Menu is displayed.
The system automatically establishes an abend trap for all abends that occurred on the terminal in region AOR1. Set breakpoints, a program trace, or protection rules for the program in region AOR1.
Enter the test transaction name TST1 to run the test transaction. 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. Proceed as normal for debugging other transactions.
Assuming that the front-end transaction is associated with a terminal, use that terminal to observe events in the test transaction.
Use 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. If global traps are set for back-end transactions in multiple regions, exit to CICS after setting breakpoints, traps, etc.
It is convenient to stay on the List Abends screen 1. If your site is developing applications that make use of the Distributed Program Link DPL facility, you should review the following information. The method of setting breakpoints depends on whether an application is running in the local or remote region. The differences are described below:. Local or remote traps may be used. Assuming that the client program is associated with a terminal, use that terminal to observe events in the test transaction.
Use the second terminal, as described below, to establish all breakpoints and traps in the imtercommunication programs. Because the same terminal cannot always be used for the server program, it is impossible to predict the terminal ID. If you set global traps for server programs in multiple intercommunicatino, exit to CICS when you are done. If global traps are set for server programs in only one region, then you can remain in Xpediter.
You can also stay on the List Iccs screen 1. 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. Specific region routing would be used when a programmer wants the Xpediter transaction to routed to a specific CICS region. It could also be useful when debugging a transaction that has affinities that limit the execution of the application to only certain CICS regions.
For example, entering the following Xpediter transaction:. Most recently used routing would be used when the programmer wants to reestablish or terminate intercommunnication most recent debugging session. This may also prevent execution of Xpediter transactions.
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. You should be as specific as possible when defining trap masks in Xpediter. Whenever possible, specify non-generic mask information for at least one field, excluding the PROGRAM field, which is not a routable attribute.
Because the first trap mask has asterisks in every field considered for routing, every transaction in scope ijtercommunication AOR1 will be routed to AOR1. This may overload the region and cause debugging sessions to be missed for the second and third trap masks.
This will result in the missing of debugging sessions for the third trap mask. Distributed program links, once routed intercommknication an AOR, no longer match the trap criteria because of the impact of routing. Receiving Service Providers immediately delete information pertaining to regions, sessions, and routing masks that were local to the Service Provider shutting down.
The steps below simplify the task of initiating Xpediter sessions in multiple AORs.
The actual transaction names may vary. The system automatically establishes an abend trap for all abends that occur on the terminal in region AOR1. Repeat Step 8 as cis for additional AORs. Enter XCB2 to run the test transaction. Enter XASM to run the test transaction. Process global parameters XDGB xxxx.