|
I set up this same scenario a year or so ago using the jpeg2afp.exe. Working with IBM my size problem was corrected changing the parms in the jpeg2afp command. Below is what I used to make the jpeg work correctly. Also the URL for the DDS part. jpeg2afp -scale 480% -thresh 4320.ibm106lpi.ta.ps -gcorr 4320.ibm106lpi.tf.dt.ps -pagetype pseg -o rl320final.afp rl320.jpg I believe the TIFF parms are similar and the -scale is the key to how big it will look once it is printed. web site talking about the DDS part. http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rzakd /rzakdmstafprsc.htm Hope this helps even if its jpeg and not tiff. I do have some additional explanations (from IBM) I can send if interested. Dean -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of michael@xxxxxxxxxxxxxxxxxx Sent: Tuesday, January 03, 2006 2:22 PM To: Midrange Systems Technical Discussion Subject: PAGSEG/*SIZE I'm using IBM's tiff2afp.exe tool to generate page segments. I bring them up to the iSeries (V5R3) and can use them as page segments (after using CRTPAGSEG). I can include them in my print file and they print fine...but too small. So I tried the *SIZE parameter on the PAGSEG keyword. However, when I do, the page segment doesn't print...at all. I've tried different sizes and different positions, and nothing works. Anyone successfully use the *SIZE parameter on the PAGSEG keyword?
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.