ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

CA-Deliver Bundle processing via TASK rather than batch JCL

book

Article ID: 212940

calendar_today

Updated On:

Products

Deliver

Issue/Introduction

Is there a way to have the CA Deliver task perform it's bundle processing routine dynamically, rather than submitting the batch job (RMOJCLB - PGM=RMOBBP)?

We encountered a situation where there were no available initiators for the batch job to run in and as a consequence, the bundles/reports were delivered late.

Environment

14.0, CA Deliver, bundle, submit, task, batch, job, card, BOT, RMOSTC, print, output, statement, JCL, RMOBPP, RMOJCLB

Resolution

If you look at the Bundle Definition Attributes screen, there is a field entitled "Job Statement Information". If this field contains JOBCARD statements, then RMOSTC will submit a batch job to process the bundle.

However, if you leave this field EMPTY and do not code JOBCARD statements, then the bundle will be processed/created by the bundle output task (BOT), without the submission of a batch job, and the bundle will appear under the RMOSTC task itself.

If you access the Bundle Definition Attributes screen and then type HELP in the command line, you will find the following excerpt in the help text information:

(11) - Job statement - the job statement (comprised of 1-4 card images) to 
       be used to submit a batch job to create the bundle.  If the job     
       statement information is left blank, then the bundle will be created
       directly by the bundle output task without the submission of a batch
       job.