Deliver - Post-spool capture producing inconsistent results in View database
Article ID: 231123
Updated On:
Products
Issue/Introduction
We have configured a new View/Deliver environment which uses the following:
. Post-spool report capture (via RMOPARMS NETCLSL/NETDEST/NETFORM).
. SARSTC1X is the View SARSTC task, RMOSTC1X is the Deliver RMOSTC task.
SARSTC1X and RMOSTC1X both run in the same LPAR.
. The View SARINIT parameters include DEST=VW1X.
. The Deliver RMOPARMS include NETCLSL=5.
. SYSOUT statements for all reports use SYSOUT=5,DEST=VW1X.
. Sometimes reports collect in View, via the SARSTC task, and sometimes the reports process in Deliver.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
We would like to see all reports be processed by Deliver, rather than the processing be inconsistent.
QUESTIONS
. Is this a timing issue between SARSTC1X and RMOSTC1X that results in the inconsistent processing?
. How can this be prevented from happening?
Environment
Release : 14.0
Component :
Resolution
If sysout is in the spool, and it matches both the Deliver post-spool criteria as well as the View collection criteria, then it will be a "toss up" as to which product is able to get to the output first.
If View is busy, then RMOSTC would be the one to process it.
If Deliver is busy, then SARSTC would be the one to process it.
The suggestion would be to not use the DEST value that matches the View criteria, so that Deliver would be the one to always process it.
Feedback
