One of the folks who's working on this with me says it doesnt' work with IPDS but thanks for the info.

-----Original Message-----
From: Vern Hamberg <vhamberg@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Fri, Mar 16, 2012 5:07 pm
Subject: Re: Splf generated as IPDS when it should be SCS

If I remember, an IPDS can be copied to a physical file - it has SCS
ontent plus graphical stuff. I think.
So give CPYSPLF a try - if you get something, check the PF to make sure
t's everything - an image of a signature would not come through, for
Then use the technique found in an IBM knowledge base for overriding
omething like QPRINT, then copying the PF into QPRINT - when you
PYSPLF, be sure to copy it with *FCFC format codes (I hope I have the
erms right - I'm doing this from a steadily non-linear memory bank!).
In the OVRPRTF of QPRINT, be sure to specify *SCS.
On 3/16/2012 9:28 AM, fbocch2595@xxxxxxx wrote:
Hi Folks, I've got a splf created w/devtype=IPDS when it should have been SCS
nd now I can't get the the splf to print. When I release the splf it goes to
LD and gives me CPI400F, Writer can not process file. Any idea what I can do
o get the splf printed? I thought I'd try to drag the splf to my desktop (via
Nav) and then drop it back to a prtf w/SCS attributes but that doesn't work.
oes anyone have a way to get the splf to print?
Thanks, Frank
his is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
o post a message email: MIDRANGE-L@xxxxxxxxxxxx
o subscribe, unsubscribe, or change list options,
r email: MIDRANGE-L-request@xxxxxxxxxxxx
efore posting, please take a moment to review the archives

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].