Re: Creating page segments natively

I did not have to change device descriptions.

Sent from my iPhone

On Mar 30, 2016, at 12:22 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> wrote:

Yeah, I looked briefly at your process - might still need to look more - just that this is on a really tight timeline, and we would likely have to change DEVDs, right? I'm wondering about Host Print Transform - I don't remember if it ignores *USERASCII data streams.

But this is looking better and better - I'm going to try the API and all, see what happens.

Thanks much for pushing me!

Vern

On 3/30/2016 10:48 AM, Michael Schutte wrote:
We're on 7.1 too. Explains why it didn't work for me too.

Did you see where I took the PDF on the IFS and used QimgCvtI to convert
back to a *USERASCII spool file? Just curious. It sucked having to do
that but that's how I was able to get the image to print on the spool file.

On Tue, Mar 29, 2016 at 4:08 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Hi Michael

I took a look and tried the keyword - runs OK, except, apparently, Host
Print Transform does not support it until 7.2 - and we are at 7.1. Sigh!
So it does not show up on the printed output.

I suspect that is what you ran into - because Transformation Services does
support the keyword, it can create the PDF.

BTW, for me, in the PDF I get when looking at the spooled file in the ACS
printer output window, the images are in reverse image - weird!!

Thanks for the tip, though - it will likely come into play in the future.

Vern

On 3/28/2016 3:48 PM, Michael Schutte wrote:

Have you looked into the AFPRSC on the printer file? This sounds pretty
close to the question I was posing a few months back that I had and was
pointed in this direction. My example was putting an image coming from a
webservice on an AFPDS print file.

For some reason, I wasn't able to get the image to print from the
generated
spool file, instead I had to generate the spool file as a PDF then convert
the PDF to a *USERASCII spool file. I didn't use any overlays or page
segments.

Hope that helps. I documented what I needed to do.

Here are my results.
http://archive.midrange.com/midrange-l/201601/msg00413.html



On Mon, Mar 28, 2016 at 3:45 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx
wrote:

Hi Carl

I think I'll mention this stuff here - I'm getting good support of this
process here in the list.

Cheers
Vern


On 3/28/2016 12:12 PM, Carl J Novit wrote:

Vern,

We use iForms for several forms, including invoices and purchase orders.
They are printed, emailed, or run through RJS's Sign Here depending on
the
situation. We have it set up to be user driven.


Thanks,


Carl Novit
Vice President
Extension: 7708



From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/28/2016 12:00 PM
Subject: Re: Creating page segments natively
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Hi Rich

iforms has been in the back of my mind. The issue for now is, we still
need to print to local printers from both batch and interactive
processes on the i.

If you have ideas for this withOUT too big a change to process, I'm all
ears!

Vern

On 3/28/2016 9:35 AM, Richard Schoen wrote:

Hey Vern,

Maybe it's time to consider a new forms product ?

Our iForms product can consume those images without custom conversion.

Might even be able to generate those forms with SEQUEL.

Food for thought.

Regards,

Richard Schoen | Director of Document Management Technologies,

HelpSystems

T: + 1 952-486-6802

RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
Visit me on: Twitter | LinkedIn

------------------------------

message: 2
date: Mon, 28 Mar 2016 07:58:18 -0500
from: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
subject: Creating page segments natively

Y'all

I have to look at converting signature images to page segments. I am
looking at examples of the output from the AFP printer drive, as well
as
the MO:DCA & IO:CA documentation, and I feel I'm close. I think I can
put together most of the structured fields.

Where I am is figuring out what to put into the image picture data
(IPD)
structured field. I think my best bet is to use TIFF Group 4 - a bitmap
(regular, not RLE) would be too large.

And then, which part of a TIFF file do I use.

One thing I've seen that is confusing, I think - I have used the AFP
driver with a BMP to create the PRN used to create a page segment. I
also have converted the BMP to a TIFF using ImageMagick (BTW, got that
installed on our 7.1 box and it works great). The content of the PRN is
larger than that of the TIFF - the PRN describes the picture data as
Group 4 compression - so is the TIFF option I selected - so maybe Group
4 can have different results? Ah to be such a novice!

So if anyone has done this and is willing to share, please post here or
contact me privately.

Thanks
Vern



--

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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related questions.