Re: Printing when system is in a restricted state.

[CRPence <CRPbottle@xxxxxxxxx>]

On Thu 05-May-2011 11:54 , rob@xxxxxxxxx wrote:
> I have a scheduled computer move coming up shortly.  We will do a
> full system save with BRMS.  This generates their "QP1ARCY -
> Recovering the Entire System" and their "QP1A2RCY - Recovery Volume
> Summary Report".  Well, actually, running their maintenance does.
> Since we will be loading equipment into the truck and sending it down
> the road I would like these printed, emailed, something for/to me.  I
> really do not want to bring the system out of restricted state just
> to do this. One report is 29 pages and one is 2 pages.
>
> Suggestions?

  If a writer is needed to get a spool file to write to the device, 
then STRSBS QSPL could be issued.  That STRSBS request alone is not 
fully equivalent to bringing the system out of restricted state via the 
STRSBS &QCTLSBSD.  Starting only the spool\writer subsystem can be 
[preceded by HLDJOBQ of any job queues that will be allocated by 
QSYSWRK] followed by ENDSBS QSYSWRK to end that "automatically started" 
subsystem; though I am not sure if other work outside of QSYSWRK might 
also get started.?  Although officially no longer in restricted state, 
that only the QSPL subsystem is left running, neither the controlling 
subsystem nor other subsystems would be active to allow work entering 
the system.  The QSYSWRK probably even could be replaced temporarily by 
a *SBSD without all those autostart and prestart jobs to prevent the 
other activity from being started if that other activity starting was 
problematic.?

Regards, Chuck