Deliver - Sharing a Deliver Database
Article ID: 267271
Updated On:
Products
Issue/Introduction
We have some reports that are created in more than one LPAR and need to be sent to a common repository.
1) Is it OK to share the Deliver database among several LPARs? If so, what are the concerns or additional setup required?
2) Is it OK to have 2 Deliver started tasks running in different LPARs sending reports to a shared View database? If so, what are the concerns or additional setup required?
Below is a diagram with 2 LPARS (SYSA and SYSB) and the proposed configuration:
Environment
Release : 14.0
Resolution
Some of the client's reports are created in more than one LPAR and need to be sent to a common repository.
To answer the case questions:
1) Is it okay to share the Deliver database among several LPARs?
If so, what are the concerns or additional setup required?
. . A Deliver database can be shared among LPARs, so long as those LPARs share DASD and catalog.
2) Is it okay to have 2 Deliver started tasks running in different LPARs sending
reports to a shared View database?
If so, what are the concerns or additional setup required?
. . Multiple Deliver RMOSTC started tasks, running in different LPARs, again with
shared DASD and catalog, can send reports to a shared View database.
. . The Deliver RMOSTC task(s) can be cloned across LPARs, since each LPAR is a different JES occurrence.
. . The post-spool processing (RMOPARMS NETCLSL, NETDEST, NETFORM) can be used from
either Deliver task, if there is shared spool between the LPARs.
. . With running multiple Deliver RMOSTC tasks, it is necessary to have a unique
RMOPARM SYSID for each task.
As well as unique SYSID parameters, there also needs to be unique BNDLCLS and
BOT parameters.
If multiple tasks have BOT=YES, then whichever one happens to find a bundle
ready will submit the print job.
To ensure that bundles run where they are supposed to, information should be in
the bundle print JCL for each.
Feedback
