|
Oh, it's a remote output queue. I guess I might have made a mistake in my assumptions here. The duplicate is being produced on the source system and not the remote system? The duplicate spool file sounds like it's an IPDS. With LAN attached IPDS printers there's an option to convert them to IPDS while printing, which might have explained the duplicate. ----- Original Message ----- From: Nick Franco To: Midrange Systems Technical Discussion Sent: Monday, August 07, 2006 11:16 AM Subject: Re: Spool File Duplicating Peter, I don't see the PRTCVT attribute anywhere. This printer is set up as a remote outq, so is there a comparable attribute for that? Also, which spool file are you asking about, the original or the one that QSPLJOB created? Thanks. Nick Franco "Peter Levy" <plevy@xxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 08/07/2006 10:21 AM Please respond to Midrange Systems Technical Discussion To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc: Subject: Re: Spool File Duplicating Is the spool file an AFP spool file and is the PRTCVT attribute of the device set to *YES? ----- Original Message ----- From: Nick Franco To: Midrange Systems Technical Discussion Sent: Monday, August 07, 2006 9:50 AM Subject: Re: Spool File Duplicating Does anyone have any ideas on this problem? It is still happening daily. Thanks. Nick Franco Nick Franco 08/04/2006 09:36 AM To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc: Subject: Spool File Duplicating 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. -- 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. -- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.