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):||9 June 2012|
|PDF File Size:||8.93 Mb|
|ePub File Size:||10.9 Mb|
|Price:||Free* [*Free Regsitration Required]|
The dump will continue the abend and free both the mirror and the test transaction. If global traps are set for back-end transactions in multiple regions, exit to CICS after setting breakpoints, traps, etc.
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.
The second abend trap is of little use, and it can lead to the false conclusion that a second terminal abend has occurred.
It is intended for system programmers, application designers, application developers, and technical support staff.
Defining intercommunication resources This topic tells you how to define the various resources that may be required in a CICS intercommunication environment. The steps below simplify the task of initiating Xpediter sessions in multiple AORs. The differences are described below:.
Proceed as normal for debugging other transactions. Assuming that the client program is associated with a terminal, use that terminal to observe events in the test transaction. They use file control commands, temporary-storage commands, and other functions in the same way.
Information Feedback Last updated: Most recently used routing would be used when the programmer wants to reestablish or terminate the most recent debugging session.
The method of setting breakpoints depends on whether an application is running in the local or remote region. 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.
4.0 Application programming in an intersystem environment
For example, entering the following Xpediter transaction:. 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.
Guice, 31 May http: Enter XASM to run the test transaction. Performance in an intersystem environment This intecrommunication gives advice on improving aspects of CICS performance in a multi-system environment.
At this point, the system allows single-stepping, resuming, and other available functions. The system automatically establishes an abend trap for all abends that occurred on the terminal in region AOR1. You can also stay on the Infercommunication Abends screen 1.
You should be as specific as possible when defining trap masks in Xpediter. The following steps detail the debugging procedure:. Use the second terminal, as described below, intercommunicatiin establish all breakpoints and traps in the server programs.
Repeat Step 8 as required for additional AORs. In most cases, these observations provide the information needed to debug the program. Specific region routing would be used when a programmer wants the Xpediter transaction to routed to a specific CICS region.
Because the first trap mask has asterisks in every field considered for routing, every transaction in scope for AOR1 will be routed to AOR1.
Because you cannot always use the same terminal for the back-end transaction, you cannot predict the terminal ID. When completed, request a dump from the Exit Session screen. Distributed program links, once routed into an AOR, no longer match the trap criteria cisc of the impact of routing.
Enter XCB2 to run the test transaction. The system automatically establishes an abend trap for all abends that occur on the terminal in region AOR1. This may overload intercommnuication region guive 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.
Enter the test transaction name TST1 to run 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.
EDITION Edition Notice
Process global parameters XDGB xxxx. 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. If the test transaction executes in the TOR, set the traps there. 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.
Set breakpoints, a program trace, or protection rules for the program in region AOR1. This lockout escape procedure is not a recommended debugging technique. If you set global traps for server programs in multiple regions, exit to CICS when you are done. The processing is independent of the sessions on which requests are sent and replies are received.
It is convenient to stay on the List Abends screen 1. Use the second terminal as described below to establish all breakpoints and traps in back-end transactions. Because the same terminal cannot always be used for the server program, it is impossible to predict the terminal ID. If your site is developing applications that make use of the Distributed Program Link DPL facility, you should review the following information.