RE: similar *PAGSEG objects in two libs with same name - how to print both next to each other

I've not closely followed this thread - as I recall, it should be no
problem to have multiple page segments on one page. The OP seems to be
having some kind of issue with that, as I recall.

No, there is NO issue with printing multiple page segments on one page - that works great.

The issue: I cannot print the same name *pagseg from two DIFFERENT libs.

"You can specify the library-name, page-segment-name, position-down,
position-across, width, height and rotation parameters as constants,
program-to-system fields, or a combination of both,"

I agree that the lib-name can be specified in DDS. However, the output writer SEEMS to ignore this lib-name and instead seems to select it at print-time from a liblist.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Friday, January 24, 2014 12:17 AM
To: Midrange Systems Technical Discussion
Subject: Re: similar *PAGSEG objects in two libs with same name - how to print both next to each other

A *PAGSEG object is a page segment. You use them in PRTFs by specifying
the PAGSEG keyword. The name is suggestive - it's something graphical
that can become part of (a segment of) the printer page.

As it says in the DDS documentation:

"You can specify the library-name, page-segment-name, position-down,
position-across, width, height and rotation parameters as constants,
program-to-system fields, or a combination of both,"

Library can be *LIBL or a specific library - standard system behavior -
look in the library list for the former.

I've not closely followed this thread - as I recall, it should be no
problem to have multiple page segments on one page. The OP seems to be
having some kind of issue with that, as I recall.

We use page segments for signatures - I put together a simple program to
print one by itself, just to get an idea of size and all when converting
to PDF - I used program-to-system fields for the library and name - voila!

Enough education - this doesn't help the OP much - but maybe it'll give
you a better idea of what is in use.

Cheers
Vern

On 1/23/2014 9:14 PM, John Yeung wrote:

Two thoughts. I should warn you I have no idea what a *PAGSEG object
even is, but the way you're talking about them makes them sound like
some kind of image, which you can sort of embed or link in a printer
file.

First crazy, naive idea: Can you print each separately? You said
you'd like one on the left and the corresponding one on the right, but
are having trouble using multiple libraries "in one pass". So how
about using two passes? If you can physically print out each
library's *PAGSEG on its own, then could you just put the pieces of
paper they printed out on next to each other? Yeah, with 500 objects
(or pairs of objects), that would potentially be lots of paper, but
other than being wasteful and low-tech, it would work, no?

Second crazy, more technical idea: Is there absolutely no way to
compare the objects byte-for-byte? If not directly, then perhaps
after some kind of conversion, like saving to a save file or dumping
to an IFS stream file? If not on the i5/OS side (apologies if I'm
getting the terminology wrong) then perhaps in Qshell or PASE?

John