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: Kejar Kajiktilar
Country: Honduras
Language: English (Spanish)
Genre: Education
Published (Last): 25 February 2004
Pages: 417
PDF File Size: 15.39 Mb
ePub File Size: 17.5 Mb
ISBN: 315-3-80427-873-8
Downloads: 67753
Price: Free* [*Free Regsitration Required]
Uploader: Yonos

CICS – Intercommunication

Wednesday, 31 May http: Application programming in an intersystem environment This topic of the manual describes the application itnercommunication aspects of CICS intercommunication. Use the second terminal as described below to establish all breakpoints and traps in back-end transactions.

At this point, the system allows single-stepping, resuming, and other available functions. Gkide the same terminal cannot always be used for the server program, it is impossible to predict the terminal ID. If global traps are set for ijtercommunication programs in only one region, then you can remain in Xpediter. Enter the test transaction name TST1 to run the test transaction.

The following steps detail the debugging procedure:. 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.

If you set global traps for server programs in multiple regions, exit to CICS when you are done. Receiving Service Providers immediately delete information pertaining to regions, sessions, and routing masks that were intercommuniction to the Service Provider shutting down. It is intended for system programmers, application designers, application developers, and technical support staff.

  ALTEC BACKBEAT 903 MANUAL PDF

Set breakpoints, a program trace, or protection rules for the program in region AOR1. The actual transaction names may vary.

The dump will continue the abend and free both the mirror and the test transaction. If the test ciccs executes in the TOR, set the traps there. Intercommunication concepts and facilities This section describes the basic concepts of CICS intercommunication and the various facilities that are provided. Defining intercommunication resources This topic tells you how to define the various resources that may be required in a CICS intercommunication environment.

It could also be useful when debugging a transaction that has affinities that limit ihtercommunication execution of the application to only certain CICS regions. This lockout escape procedure is not a recommended debugging technique.

PREFACE “CICS Intercommunication Guide” IBM Library Server

Enter XCB2 to run the test transaction. For example, entering intervommunication following Xpediter transaction:. In most cases, these observations provide the information needed to debug the program. Information Feedback Last updated: The system automatically establishes an abend trap for all abends that occurred on the terminal in region AOR1.

1.0 Part 1. Concepts and facilities

This may also prevent execution of Xpediter transactions. Process global parameters XDGB xxxx. The second abend trap is of little use, and it can lead to the false conclusion that a second terminal abend has occurred.

Assuming that the front-end transaction is associated with a terminal, use that terminal to observe events in the test transaction. Performance in an intersystem environment This topic gives advice on improving aspects of CICS performance in a multi-system environment. If your site is developing applications that make use of the Distributed Program Link DPL facility, you should review the following information.

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. When completed, request a dump from the Exit Session screen. Use the second terminal, as described below, to establish all breakpoints and traps in the server programs.

  BRANDING PE FRONTUL DE EST PDF

EDITION “CICS Intercommunication Guide” IBM Library Server

You should be as specific as possible when defining trap masks in Xpediter. Most recently used routing would be used when the programmer wants to reestablish or terminate the most recent debugging session. Interommunication XASM to run the test transaction. 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.

You can also stay on the List Abends screen 1. The differences are described below:. 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. The processing is independent of the sessions on which requests are sent and replies are received. Setting these breakpoints or traps can cause the intercommuhication to hang if intwrcommunication is busy with the test transaction.

Proceed as normal for debugging other transactions. If global traps are set for back-end transactions in multiple regions, exit to CICS after setting breakpoints, traps, etc. Whenever possible, specify non-generic mask information for at least one field, excluding the PROGRAM field, which is not a routable attribute.