Re: Spool file being converted to *AFPDS (Scott Klement)

Scott,

There are two OE300L on the system but the CMS.CUS library is ahead of the
other print file library. From the spool file attributes I would beleive the
proper print file is being used.

> Otherwise, could the customer have done an OVRPRTF FILE(*PRTF)
> DEVTYPE(*AFPDS) for use with another application?

This makes sense but I had the user signoff, signon and go straight to the
application and still the same results. That is how I ran the application
also.

More investigations tomorrow.

Thanks,

Jay

> Message: 7
> Date: Wed, 23 Jan 2002 16:47:28 -0600 (CST)
> From: Scott Klement <klemscot@klements.com>
> To: midrange-l@midrange.com
> Subject: Re: Spool file being converted to *AFPDS
> Reply-To: midrange-l@midrange.com
>
>
> Some guesses:
>
> Is it possible that there are two OE300L print files on the system?  One
> with DEVTYPE(*SCS) and one with DEVTYPE(*AFPDS)?   Maybe differing library
> lists explain why it works differently for you than it does for the
> customer?
>
> Otherwise, could the customer have done an OVRPRTF FILE(*PRTF)
> DEVTYPE(*AFPDS) for use with another application?   Maybe he's running
> code that does this, and he doesn't even know it?
>
>
> On Wed, 23 Jan 2002, Jay Peasley wrote:
>
> > Has anyone ever had an instance where a spool file, that was generated
from
> > a *SCS print file is converted by the system to a device type of *AFPDS?
> >
> > I have a customer who runs a invoice print program that does this, yet
if I
> > run it, it stays a *SCS device type.
> >
> > Here are some of the attributes from the two different print files:
> >
> > Job  . . . . . . . . :   QPADEV000F      File . . . . . . . . :   OE300L
> >   User . . . . . . . :     JHUNGER         Number . . . . . . :     15
> >   Number . . . . . . :     196499
> >
> > Device type  . . . . . . . . . . . . . :   PRINTER
> > Printer device type  . . . . . . . . . :   *AFPDS
> > Device file  . . . . . . . . . . . . . :   OE300L
> >   Library  . . . . . . . . . . . . . . :     CMS.CUS
> > User-specified data  . . . . . . . . . :   OE300R
> > Accounting code  . . . . . . . . . . . :
> > Program that opened file . . . . . . . :   OE300R
> >   Library  . . . . . . . . . . . . . . :     CMS.CUS
> > Date file was opened . . . . . . . . . :   01/23/02
> > Time file was opened . . . . . . . . . :   12:38:08
> > Date file was last used  . . . . . . . :   01/23/02
> > System where file created  . . . . . . :   XXXXXXX  (to protect the
> > innocent)
> > User who created file  . . . . . . . . :   JHUNGER
> >
> >  Job  . . . . . . . . :   QPADEV000D      File . . . . . . . . :
OE300L
> >   User . . . . . . . :     JPEASLEY        Number . . . . . . :     2
> >   Number . . . . . . :     196637
> >
> > Device type  . . . . . . . . . . . . . :   PRINTER
> > Printer device type  . . . . . . . . . :   *SCS
> > Device file  . . . . . . . . . . . . . :   OE300L
> >   Library  . . . . . . . . . . . . . . :     CMS.CUS
> > User-specified data  . . . . . . . . . :   OE300R
> > Accounting code  . . . . . . . . . . . :
> > Program that opened file . . . . . . . :   OE300R
> >   Library  . . . . . . . . . . . . . . :     CMS.CUS
> > Date file was opened . . . . . . . . . :   01/23/02
> > Time file was opened . . . . . . . . . :   16:32:41
> > Date file was last used  . . . . . . . :   01/23/02
> > System where file created  . . . . . . :   XXXXXXX ( to protect the
> > innocent)
> > User who created file  . . . . . . . . :   JPEASLEY
> >
> > Strange, eh.
> >
> > Thanks!
> >
> > Jay