Rob,
That is just it. They were not there in FIN state. That is part of what drove me crazy.
Gary
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, December 21, 2011 12:19 PM
To: Midrange Systems Technical Discussion
Subject: RE: (see thread on RPG list) Re: Test program calls puts(), creates spool file here, but not on customer box
James,
By your WRKJOB test I am going to assume they weren't there, period. And not that they were there in a FIN state. Because, if like Gary says they quickly printed, they would be there in a FIN state in WRKJOB.
Also, WRKJOB OPTION(*FILOVR) doesn't show any particular overrides? I tried overriding to a stream file (supported) OVRPRTF FILE(QPDSPJOB) DEVTYPE(*AFPDS) TOSTMF('/rob/dspjob.txt') This one will not show up in WRKJOB OPTION(*SPLF) but does show up in WRKLNK '/rob/*' (uglier than sin, though).
You could try turning on spool file auditing also.
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Monnier, Gary" <Gary.Monnier@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 12/21/2011 03:02 PM
Subject: RE: (see thread on RPG list) Re: Test program calls
puts(), creates spool file here, but not on customer box
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Hi James,
Is it possible the output from the Host Print key and puts are actually
printing before you can see the spooled files? I had something similar
occur to me a couple of weeks ago. I had the program in debug and watched
the spooled file be printed. But when it came time to e-mail the report
it wasn't there! Drove me crazy for a while. It turned out I had it
outputting to an outq that was active. By the time my program printed the
report to when it was to be e-mailed the report had printed! The time gap
was only a few seconds.
Maybe this is happening at your client? Can you hold all the output
queues and then run your test? I know it's a lot to ask of a client but
maybe they'll be agreeable.
HTH.
Gary
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Wednesday, December 21, 2011 11:37 AM
To: Midrange Systems Technical Discussion
Subject: (see thread on RPG list) Re: Test program calls puts(), creates
spool file here, but not on customer box
This problem began at the top of the month, when I tried to use the c
puts() function to provide quick-and-dirty diagnostics to a headless
server program, and was discussed briefly on the RPG list, without any
resolution so far. Then it got shoved aside in favor of more pressing
matters. But it has abruptly returned to the foreground.
Here is what we know so far:
On our boxes, and on the customer's old box, all of the usual ways to
produce spool files (e.g., compilation listings, PRTTRGPGM listings, the
"Host Print" key [from QuestView, or from a system menu], calling the
puts() function in the C runtime within a batch job, and so forth) all
produce spool files.
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.
It acts as if a spool file was produced, but there's no evidence that this
happened.
One note: the print key takes about 2 seconds to produce the spool file
and unlock the keyboard on our 170, about half a second to do so on our
E4A, about 24 seconds to do so on the customer's old box (an M25), and
11 seconds to unlock the keyboard and come back with "Print operation
complete to the default printer device file" (but no actual spool file) on
the customer's new box (also an M25).
I don't suppose there's something that bypasses spool files entirely, is
there?
QPRINT and QSYSPRT both exist, and they're both PRTFs. QPRINT is in QGPL,
and while QGPL is not in the default *LIBL, adding it has no effect on the
weird behavior.
--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
