Re: (see thread on RPG list) Re: Test program calls puts(), creates spool file here, but not on customer box

[CRPence <CRPbottle@xxxxxxxxx>]

  OK.  However the point was "to test", to investigate the /failing/ 
scenario rather than something to resolve or circumvent, and finally to 
review the results of that test.  Something that could be "more 
agreeable" [and very probably much easier] for a client than to have 
them "hold all the output queues and then run your test."

  I just do not see holding all of the output queues on a customer's 
system would be very agreeable to most customers, just to let the sfw 
provider test their code; I know I would hesitate even to have asked a 
customer to do something like that.  The OVRPRTF *PRTF OVRSCOPE(*JOB) 
could be the first command issued in a job that later did the host-print 
or puts().  That CL request could be in a routing program based-on 
specific entry Request Data, even limited to a subsystem setup just for 
that test; i.e. no requirement to change the program that does the "puts()".

Regards, Chuck

On 21-Dec-2011 13:24 , Monnier, Gary wrote:
> > > > But on their new box, while compilation listings and PRTTRGPGM
> > > > listings still produce spool files, the "host print" key
> > > > (wherever I've tried it) and "puts() in a batch job" don't.
> > > > There is no spool file if I do a WRKSPLF; there's no spool file
> > > > in WRKJOB option 4; there have been no reports of unexpected
> > > > pages coming out of unexpected printers.
>
> "puts() in a batch job" was also an issue wasn't it?
>
> On Wednesday, December 21, 2011 12:39 PM Rob wrote:
> >
> > Change what program? He was having an issue with Print Key. Enter
> > that command at the command line and test.
> >
> > "Monnier, Gary" on 12/21/2011 03:35 PM wrote:
> > > Yea, but who wants to change a program if you don't have to. :)