Spool file being converted to *AFPDS

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