Deliver - Want to consider using Pre-spool versus Post-spool processing

Products

• Deliver

Issue/Introduction

We are running Deliver 14.0 and almost all batch jobs are collected pre-spool. 

We have a PLEX with 2 LPARs.  The plex has LPARS <abc1> and <abc2>.  They share DASD and the spool. 

We are looking to upgrade <abc2>, so I have been tasked to see if we can only run one Deliver on <abc1>. 

My question is:

How can we switch to post-spool?

If we are using post-spool only, will <abc1> Deliver pick up system output on from <abc2> on the shared spool?

Is there something else I should consider besides the additional lines that need to be stored in the spool until they are archived?

Environment

Release : 14.0

Component : Deliver

Resolution

With two different systems:

 . There needs to be a RMOSTC task running on each system when using pre-spool processing. 

 . There can be a RMOSTC task running on one system when using post-spool processing, provided there is shared spool between the systems.

Post-spool processing occurs with use of the RMOPARMs NETCLSL/NETDEST/NETFORM. 

Other than the consideration of what extra space would be needed in the spool, there would be need to look at any other applications that also would be obtaining sysout from the JES spool, which would include CA View's SARSTC tasks.