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: Taujar Kajiran
Country: Poland
Language: English (Spanish)
Genre: Business
Published (Last): 27 August 2008
Pages: 188
PDF File Size: 9.67 Mb
ePub File Size: 17.26 Mb
ISBN: 520-6-17692-314-4
Downloads: 60666
Price: Free* [*Free Regsitration Required]
Uploader: Dairan

Asynchronous processing Asynchronous processing distributes the processing required by an application between intercommunicating systems.

CICS – Intercommunication

Because the same terminal cannot always be used for the server program, it is impossible to predict the terminal ID. Wednesday, 31 May http: 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.

Defining intercommunication resources This topic tells you how to define the various resources that may be required in a CICS intercommunication environment.

The following steps detail the debugging procedure:. The processing is independent of the sessions on which requests are sent and replies are received. It is better to trap abends in the interommunication transaction, where you can observe the tasks that enter and leave the function-shipping CICS call.

Intercommunication concepts and facilities This section describes the basic concepts of CICS intercommunication and the various facilities that are provided. 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.

Performance in an intersystem environment This topic gives advice on improving aspects of CICS performance in a multi-system environment. Most recently used routing would be used when the programmer wants to reestablish or terminate the most recent debugging session.

  CREATIN KINASA PDF

“CICS Intercommunication Guide” IBM Library Server

Use the second terminal, as described below, to establish all breakpoints and traps in the server programs. Application programming in an intersystem environment This topic of the manual describes the application programming aspects of CICS intercommunication.

intrecommunication Distributed program links, once routed into an AOR, no longer match the trap criteria because of the impact of routing.

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 guiide installation and configuration requirements depending on whether a CICS system is to participate in intersystem communication or multiregion operation.

Enter XCB2 to run the test transaction. For example, entering the following Xpediter transaction:. Recovery and restart in an intersystem intercommunicatiin This topic tells you what CICS can do if things go wrong in an intercommunication environment, and what you can do to help.

Assuming that the client program is associated with a terminal, use that terminal to observe events in the test transaction.

Specific region routing would be used when a programmer wants the Xpediter transaction to routed to a specific CICS region. The steps below simplify the task of initiating Xpediter sessions in multiple AORs.

If your site is developing applications that make use of the Distributed Program Link DPL facility, you should review the following information. Information Feedback Last updated: Intercommuniation most cases, these observations provide the intecrommunication needed to debug the program. The system automatically establishes an abend trap for all abends that occurred on the terminal in region AOR1. This may also prevent execution of Xpediter transactions. It could also be useful when debugging a transaction that has affinities that limit the execution of the application to only certain CICS regions.

  CHOCOVISION REVOLATION X3210 PDF

EDITION “CICS Intercommunication Guide” IBM Library Server

Because the first trap mask has asterisks in every field considered for routing, every transaction in scope for 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. Setting these breakpoints or traps can cause the terminal to hang if it is busy with the test transaction. If global traps are set for server programs in only one region, then you can remain in Xpediter.

You can set a local trap for abends at the primary terminal.

EDITION Edition Notice

Assuming that the front-end transaction is associated with a terminal, use ccics terminal to observe events in the test transaction. It is convenient to stay on the List Abends screen 1. They use file control commands, temporary-storage commands, and other functions in the same way. This lockout escape procedure is not a recommended debugging technique.

Because you cannot always use the same terminal for the back-end transaction, you cannot predict the terminal ID. The actual transaction names may vary. Repeat Step 8 as required for additional AORs. The dump will continue the abend and free both the mirror and the test transaction. The system automatically establishes an abend trap for all abends that occur on the terminal in region AOR1.

The differences are described below:.

You can also stay on the List Abends screen 1. The Primary Menu is displayed. You should be as specific as possible when defining trap masks in Xpediter.