RE: 5770 SP/QWPZHPT1 MSGMCH1211 RC500 with QWPTIFFG4 *WSCST

I've had a couple problems with Host Print Transform converting to TIFF using that customization object. It's been years and years ago, so there's no telling if they're related.

One, it used to have a memory leak. If you run it over and over in the same job using the API, it'll overflow the job memory max. You're not using the API directly, you're using CPYSPLF; under the covers it may be running the API.

Second, there's a boundary problem. I don't remember exactly how it goes, but something about one of the dimensions of the PAGSEG being bigger than the page size allocated for the TIFF. Maybe that's picture size which is page size less borders. When using the API there are shrink to fit options. Don't know if you have that using CPYSPLF.

MCH1211 is a divide by zero error. That might apply to either of the above. I'm sure you've done this, but I'll say anyway: check the job log carefully for related messages before or after this one.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Tuesday, August 27, 2013 4:27 PM
To: Midrange Systems Technical Discussion
Subject: 5770 SP/QWPZHPT1 MSGMCH1211 RC500 with QWPTIFFG4 *WSCST

Uffda!


I had a job running all day - we have signatures stored in page segments. We
need to send them with the text of an invoice to a service company. Am
converting the PAGSEGs to TIFFs.


This is the 17th and 3rd-to-last day of running this stuff. Has been going fine
so far.


Any experience with this?