× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. October 2008

RE: HPT API vs. HPT Printer.. different results?

Build your own WSCST. Instructions in the Printing guide. Most of the
parameters are ignored when output is TIFF. Again, check the PTF's.
There was a lot done several years ago for TIFF output, I don't know if
it ever made a release or cume.

Font substitutions will get you as well. I'd forgotten about that one.
HPT will use a different font substitution when going to an HP printer,
for instance, than when going to TIFF. There are only a few raster fonts
on a typical System i. When going to TIFF those are used. If you get a
font that is a little wider or the kerning is different, your overlay
will be off.

Overlay offsets tend to be mucked up when going to TIFF. This is
influenced by the actual origin of the page. When going to an HP
printer, theres an unprintable band of about half an inch on the left
side. That affects the origin but not the overlay offset. Going to TIFF
the origin is top left exactly and the overlay offset is from this same
point.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bradley V. Stone
Sent: Thursday, October 09, 2008 3:24 PM
To: Midrange Systems Technical Discussion
Subject: RE: HPT API vs. HPT Printer.. different results?

Yes, that is all being done. The HPT printer works fine. The API
version converting it to a TIFF is the issue. The WSCSTs are pretty
limited for those that I've found only alloing different Manufacturer
parms like *WSCST or *WSCSTLETTER

What's odd is it works fine on 90% of the spooled files. But now and
then the API shifts the data. Sometimes using *WSCSTLETTER fixes
things, but other times it doesn't.

Brad

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Dan Kimmel
Sent: Thursday, October 09, 2008 2:32 PM
To: Midrange Systems Technical Discussion
Subject: RE: HPT API vs. HPT Printer.. different results?


I don't think HPT picks up anything from the spool file attributes.
Some of the print attributes, like font, are in-lined in the AFP. HPT
will pick up info from the AFP. There are HPT API parameters to define

the page size, etc. You have to extract that information from the
spool file attributes and pass it to HPT when you call the API's as I
recall.

Also look at the *WSCST objects. In particular, there's a page size in

the WSCST whose only function is to set up the amount of memory
allocated for the created page bitmap. We've often made that the
maximum, which is 11 x 17, I think, in order to allocate enough memory

for a busy page.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bradley V. Stone
Sent: Thursday, October 09, 2008 11:07 AM
To: Midrange Systems Technical Discussion
Subject: RE: HPT API vs. HPT Printer.. different results?

Dan,

I do understand this, but could you expand on "if you're not careful"?

The customer is using the following before creating the spooled file:

OVRPRTF FILE(PSX012CPRT) DEV(XXXXXX) DEVTYPE(*AFPDS) PAGESIZE(88 145)
LPI(8) FONT(252) OVRFLW(66) PRTQLTY(*NLQ) FRONTOVL(xxxx) COPIES(XX)

Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Dan Kimmel
Sent: Thursday, October 09, 2008 9:59 AM
To: Midrange Systems Technical Discussion
Subject: RE: HPT API vs. HPT Printer.. different results?


I haven't worked with HPT API in several years, but as I recall, the

problem is in setting the page size, orientation and the overrun. If

you aren't careful, the page sets up as 8.5 x 11 *COR with
shrink-to-fit.
That really messes up the overlay. Also be sure to get the HPT
PTF's.
They aren't on any cume.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bradley V.
Stone
Sent: Thursday, October 09, 2008 8:51 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: HPT API vs. HPT Printer.. different results?

Has anyone see this?

I have a client that has a HPT printer that prints an AFPDS spooled
file "as it should". Everything is lined up with the overlay, etc.

But, when they use the HPT API, the data is shifted and things don't

line up.

The fonts appear ok, so it appears that fonts used in the report are

on the system. I would expect the HPT printer to have the same
issues

as the HPT API. But I know the API is "touchy" when things aren't
just perfect (cpi, lpi, length, width, margins, etc).

Anyone have any ideas where to look for answers to this?

Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com

--
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.



--
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.

--
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.



--
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.



--
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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.