Sysout bundled separately from the rest of the initial CA Deliver bundle
search cancel

Sysout bundled separately from the rest of the initial CA Deliver bundle

book

Article ID: 217539

calendar_today

Updated On:

Products

Deliver

Issue/Introduction

For certain jobs we create a bundle of sysouts from the same job. Occasionally, a sysout from that job will not get bundled with the rest of the sysouts from that job, and as a result it gets processed separately.

Any idea what may be causing this? Is there a way to ensure that for an initial bundle, all the reports that are supposed to be in it are in it before it gets processed by CA Deliver?

Environment

Release : 14.0

Component : CA Deliver

Cause

Generally speaking, when a report isn't included in the bundle of reports you would expect it to be in, it's because that report was not available at the time Deliver processed the initial bundle. As a result, it's placed into a continuation bundle. These subsequently produced continuation bundles retain the same bundle identifier as the original bundle with which they are associated.

Resolution

In an effort to try and ensure that a bundle isn't processed until all of the reports that are supposed to be in the bundle are in the bundle, our suggestion would be to, on the Bundle Definition panel, define a value in the LATE field, and set WAIT LATE to 'Y'. If the execution times of the job(s) that create the reports in your bundles are pretty consistent, and you know when those jobs usually run, making this adjustment to the LATE and WAIT LATE fields may help reduce the frequency at which reports are placed into a continuation bundle.

In lieu of using the LATE parm, setting a value for INTERVAL and setting WAIT INT to 'Y' for the bundle is an alternative preventative measure you can take to ensure that a bundle isn't processed until all of the reports that are supposed to be in the bundle are in the bundle. But it's not necessarily a guarantee. The interval is how often Deliver checks to see if there are more reports ready to be printed. When a bundle will actually get processed by CA Deliver depends on where the interval is in it's countdown, in conjunction with when reports are being made available in the bundle.

Technically, there are two kinds of bundles. INITIAL bundles and CONTINUATION bundles...

The only way to ensure all the reports that are supposed to be in an INITIAL bundle are in that bundle before it is processed by CA Deliver is to pre-activate the reports (or at least the LAST report) in that bundle. Unfortunately, pre-activating of the reports requires an additional effort (manual or RMORAPS).

Additional Information

Article created from case #32732972