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.

Author: Kekinos Fenrizilkree
Country: New Zealand
Language: English (Spanish)
Genre: Software
Published (Last): 28 June 2007
Pages: 449
PDF File Size: 7.18 Mb
ePub File Size: 11.66 Mb
ISBN: 244-3-48284-177-1
Downloads: 87014
Price: Free* [*Free Regsitration Required]
Uploader: JoJolkree

Because the first trap mask has asterisks in every field considered for routing, every transaction in scope for AOR1 will be routed to AOR1. Receiving Service Providers immediately delete information pertaining to regions, intercmomunication, and routing masks that were local to the Service Provider shutting down.

Enter the test transaction name TST1 to run the test transaction. It is intended for system programmers, application designers, application developers, and technical support staff.

Xics is better to trap abends in the test transaction, where you can observe the tasks that enter and leave the function-shipping CICS call. The processing is independent guiee the sessions on which requests are sent and replies are received. Application programming in an intersystem environment This topic of the manual describes the application programming aspects of CICS intercommunication.

The system automatically establishes an abend trap ccs all abends that occur on the terminal in region AOR1. Because you cannot always use the same terminal for the back-end transaction, you cannot predict the terminal ID. Assuming that the front-end transaction is associated with a terminal, use that terminal to observe events in the test transaction. You can also stay on the List Abends screen 1.

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. When the Service Providers involved in a given CICSPlex are connected to each other, all dics, session, and routing mask information is shared among them.

  CP HORARIOS CASCAIS PDF

6.1 Recovery and restart in interconnected systems

If the test transaction executes in the TOR, set the traps there. 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.

In most cases, these observations provide the information needed to debug the program. Defining intercommunication resources This topic tells you how to define the various resources that may be required in a CICS intercommunication environment.

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

Local or remote traps may be used. It is convenient to stay on the List Abends screen 1. Most recently used routing would be used when the programmer wants to reestablish or terminate the most recent debugging session. This may also prevent execution of Xpediter transactions. They use file control commands, temporary-storage commands, and other functions in the same way. The Primary Menu is displayed. Setting these breakpoints or traps can cause the terminal to hang if it is busy with the test transaction.

Wednesday, 31 May http: If your site is developing gyide that make use of the Distributed Program Link DPL facility, you should review the following information. Specific region routing would be used when a programmer wants the Xpediter transaction to routed to a specific CICS region.

Intercommunication Considerations

Distributed program links, once routed into an AOR, no longer match the trap criteria because of the impact of routing. Assuming that the client program is associated with a terminal, use that terminal to observe events in the test transaction. Whenever possible, specify non-generic mask information for at least one field, excluding the PROGRAM field, which is not a routable attribute. Process global parameters XDGB xxxx.

The actual transaction names may vary. If global traps are set for server programs in only one region, then you can remain in Xpediter. Use the second terminal as described below to establish all breakpoints and traps in back-end transactions.

  EJERCICIOS DE FOTOMETRIA PDF

PREFACE “CICS Intercommunication Guide” IBM Library Server

The differences are described below:. Intercommunication concepts and facilities This section describes the basic concepts of CICS intercommunication and the various facilities that are provided. The second abend trap is of little use, and it can lead to the false conclusion that a second terminal abend guife occurred. 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.

1.0 Part 1. Concepts and facilities

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. The system automatically establishes an abend trap for all abends that occurred on the terminal in region AOR1.

Information Feedback Last updated: Enter XCB2 to run the test transaction. You can set a local trap for abends at the primary terminal.

When completed, request a dump from the Exit Session screen. This will result in the missing of debugging sessions for the third trap mask. You should be as specific as possible when defining trap masks in Xpediter.

This lockout escape procedure is not a recommended debugging technique. For example, entering the following Xpediter transaction:. The dump will continue the abend and free both the mirror and the test transaction.

Set breakpoints, a program trace, or protection rules for the program in region AOR1. Repeat Step 8 as required for additional AORs. Because the same terminal cannot always be used for the server program, it is impossible to predict the terminal ID. Proceed as normal for debugging other transactions.