Running Deliver in a Multiple SYSPLEX Environment

Products

• Deliver
• View

Issue/Introduction

The design of Deliver incorporates the ability to capture work from other SYSPLEXes or system complexes. This functionality is provided by the Network Input Feature, which can capture output from a remote location. The supported method to capture sysout-generated on remote systems is through network input.

Environment

Release: 12.1-Deliver-Output Management-Interface for Native TSO

Resolution

If Deliver runs against a common database on multiple images within a SYSPLEX, the sysout data sets can be captured, and the reports and bundles can be created without any problems. This is because all the Deliver-started tasks are running within the same JESMAS. The reports and bundles are printable on any image in the JESMAS.  

If Deliver runs against a common database on multiple images within multiple SYSPLEXes, the capturing and printing of reports and bundles is not as straightforward.  Bundle composition and printing will now depend on where the bundle-holding copy is kept.  

If the bundle-holding copy is kept in JES, then all of the reports in a bundle must be generated and printed in the same SYSPLEX. This means that the printer and remote definitions in all SYSPLEXes will have to be kept synchronized so that all output going to a specific printer or remote will go to the same destination, regardless of which SYSPLEX prints the output.

If the bundle-holding copy is kept in View, you will have to share the View database(s) across the SYSPLEXes.

The View database(s) will also have to be shared across SYSPLEXes if reports are archived into View.

NOTE: Before attempting to share databases across SYSPLEXes, verify that your GRS or equivalent environment will provide the proper protection for your databases. If hardware reserves are not preserved, then all View and Deliver converted global enqueues must be propagated to all system images in all SYSPLEXes.