AAAAAAAARRRRRRRGGGGGGHHHHHH
It was there - right in front of my eyes
Again
AAAAAAAARRRRRRRGGGGGGHHHHHH
Frustration - Frustration - Frustration !!!
MUCH APPRECIATED Chuck
As well as to EVERYONE else that answered
MUCH APPRECIATED
Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Friday, December 30, 2011 2:22 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Can the device type (DEVTYPE) of an external print file be determined
Importance: Low
On 30-Dec-2011 10:44 , Alan Shore wrote:
<<SNIP>> I never thought of DSPFD command, however, unless I am
missing something (highly likely) running through all the parameters,
I am unable to capture the device type of the print file
Display the field descriptions for the model output file [System outfile for DSPFD TYPE(*ATR) FILEATR(*PRT)]:
DSPFFD QSYS/QAFDPRT /* Look for column name PRTDEVT to see: */
PRDEVT CHAR(1) byte-330 "Printer Device Type"
"In Hex 0=SCS,1=IPDS,2=AFPDS,3=LINE,4=2&3,5=U-ASCII"
<code>
DSPFD FILE(lib/thefile) TYPE(*ATR) OUTPUT(*OUTFILE) FILEATR(*PRTF)
OUTFILE(QTEMP/FDPRTF)
select hex(prdevt) from qtemp/fdprtf
DEVTYPE
00
*** End of data **
</code>
FWiW I seem to recall that a recent release had added a "retrieve device file" API.
Regards, Chuck
--
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
