Re: Spool File Duplicating -- MIDRANGE-L

Jerome,

It was a good thought but I checked the Maximux Spool file Size for the 
outq and it is set to none. Thanks though.

Nick Franco





Jerome Hughes <jromeh@xxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/04/2006 10:25 AM
Please respond to Midrange Systems Technical Discussion

 
        To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
        cc: 
        Subject:        Re: Spool File Duplicating



Nick--

Aware this may not be your issue, but it's too similar not to say 
something, maybe it will help lead to your answer...

Once had "phantom print" spool files appearing overnight, "out of 
nowhere" they would spew out of a 3rd floor printer until it was out 
of paper, and the next morning someone would come in and have to 
clean up.

After a month or so of sporadically investigating this intermittent 
mystery, it turned out the output queue had been set up with a 
Maximum spooled file size, above which the spool files would go to 
*DFR. Starting time was 00:00:00 or 00:00:01 and ending time was 
23:59:59. In the milliseconds between end time and start time, a *DFR 
spool file would leap to life, spew, and then get set back to *DFR.

Not sure if it was always the same spool file or a duplicate was 
getting created by the printer job or something.

thx & hth,

--Jerome


On Aug 4, 2006, at 8:36 AM, Nick Franco wrote:

We have a very unusual problem going on here. We have a job that runs
nightly that produces a report that prints on a printer set up as a 
remote
outq. Here's the strange part: a duplicate of that spool file is being
created and sent to the same printer. This has been happening only for
this spooled file/job/printer for about a month or so. The 
duplicate spool
file says it is created by user QSPLJOB. The job that created it is 
the
printer name. The printer device type is *USERASCII while the 
original one
is *SCS. The device file is QPTMPLPD in QUSRSYS. The accounting 
code is
*SYS. The program that opened file is left blank.The user defined data
shows the job name/user/file number of the original spolled file. The
other strange thing is that the spool file shows the total pages as 
being
1 with an asterick next to it. I've looked at the joblog for that 
printer
and every other spool file shows that the come from module QTMPLPRC
procedure main and goes to module SPRMTDR procedure 
SendTcpIpSpooledFile.
This spool file comes from module SPRMTDR procedure 
SendTcpIpSpooledFile
to module SPRMTDR procedure _C_pep. Does anyone have a clue why the 
system
is doing this and how I can stop it????


Nick Franco
-- 
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.