Why are Reports, that were Pre-Spool Processed by Deliver, No longer Processed that way?
search cancel

Why are Reports, that were Pre-Spool Processed by Deliver, No longer Processed that way?

book

Article ID: 24359

calendar_today

Updated On:

Products

Deliver View

Issue/Introduction

Customer would like to know the reason(s) that may be the cause of a report that is no longer pre-spool processed in Deliver.

Resolution

Utility programs SARINIT, SARDBB, SARDBASE, RMODBB, or RMODBASE output require post spool processing, because pre-spool capture of these View and Deliver programs' output is no longer allowed. Also reports generated by these programs are not candidates for dynamic report creation.

An S138 abend is caused by a database conflict with jobs being pre-spool processed that have steps that execute programs that are prefixed with SAR (for example, SARDBASE), RMO (for example, RMOGRW), ECx for release 12.2 (for example, EC2DRV), As a result, to prevent the abend,  Deliver was changed so that it will only post-spool process the output of  Deliver and View utilities.

So, if any sysouts are not being processed by  Deliver, then you may need to change the job from being processed pre-spool to being processed post-spool.