CA Deliver Bundling jobs are failing with "RMOBBP15 Invalid or missing control card - ABEND=S000 U0015" after applying maintenance.

Products

• Deliver

Issue/Introduction

Bundling jobs (PGM=RMOBBP) are failing with a  "RMOBBP15 Invalid or missing control card" message, followed by a S000/U0015 abend, after we applied Deliver maintenance on one of our LPARs.
 

Environment

Release : 14.0

Cause

Our environment has 3 shared LPARs (abc1, abc2 & abc3) with 3 Deliver STC's running that all share the same database. With weekend maintenance, PTF LU08140 (Deliver enhancement to submit batch bundle JCL with 80-character SYSIN control cards instead of 100-character control cards) was applied on one LPAR (abc3) and not on the other two.

When bundling jobs were submitted on the updated system (abc3) but ran on the other 2 non-updated systems (abc1 or abc2), the bundle jobs issued "RMOBBP15 Invalid or missing control card" message and abended with ABEND=S000 U0015 due to not recognizing the new format of control statements.

Resolution

To circumvent the problem, turn off the Bundle Output Task (BOT) by issuing the "F rmostc,BOT OFF" modify command against the the updated (abc3) systems Deliver started task.

With that change, the bundle jobs would only be submitted by the non-updated systems (abc1 & abc2), with the old format for the control statements, and those submitted jobs can run on any of the systems.

The permanent solution is to implement the updated code from PTF LU08140 into the other LPARs running a Deliver STC as soon as possible.

Additional Information

For additional information on the Bundl Output task, please refer to the INITIALIZATION PARAMETERS section of the Deliver documentation and scroll down to the following section:

 
Bundle Output Task and the BOT Initialization Parameter

The BOT (Bundle Output Task) initialization parameter is a subtask of the started task that periodically scans the active bundle queue for bundles that are ready to print. The time period between scan actions is specified by the BNDLSCAN initialization parameter.

When Deliver runs on multiple operating systems in an installation, a bundle output task normally executes under Deliver on each operating system. BOT specifies whether the bundle output task is initially started. Also, operator commands are provided to start and stop the bundle output task.

Running BOT on multiple operating systems that share the same database can affect performance.

You can choose to not run the bundle output task on an operating system.

If a bundle is defined with JOB statements, the bundle output task submits a batch job to compose and print the bundle. The job that is submitted corresponds to skeleton JCL member RMOJCLB.

You can achieve parallel processing by submitting separate batch jobs to comprise the bundles. If no JOB statements are defined for a bundle, it is printed directly by the bundle output task.