|
From the manual, what you're trying to do should work...but... :)
I should warn you I have no idea what a *PAGSEG object even is,
In my case each *pagseg object is a single signature image.
First crazy, naive idea: Can you print each separately?
Not crazy - that is what I did. So I ended up with two emails. A spool
file containing a *pagseg is not displayable on green-screen, so I email
them to myself.
Email #1:
*pagseg image from OLDlib
SIG001 John Doe
SIG002 Sally Smith
Email #2:
*pagseg image from NEWlib
SIG001 John Doe
SIG002 Sally Jones
Visually comparing the above two reports, it was determined that SIG002
was re-created with a different image at some time in the past.
I wanted to print a report showing BOTH signatures on one line, just
curious if it could be done.
Desired combined email report:
*pagseg image from OLDlib image from NEWlib
SIG001 John Doe John Doe
SIG002 Sally Smith Sally Jones
I don't think that the desired combined report is possible as the output
writer seems to "find" the *pagseg from a liblist and NOT from the DDS
keyword.
BTW I hard-coded the lib name - it was NOT a program variable.
R PFPAGESEG1 PAGSEG(OLDLIB/&PFPAGESEG1 +
&PF_VPOS_S1 3)
PFPAGESEG1 8 P
PF_VPOS_S1 5S 3P
R PFPAGESEG2 PAGSEG(NEWLIB/&PFPAGESEG2 +
&PF_VPOS_S2 6)
PFPAGESEG2 8 P
PF_VPOS_S2 5S 3P
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Thursday, January 23, 2014 9:15 PM
To: Midrange Systems Technical Discussion
Subject: Re: similar *PAGSEG objects in two libs with same name - how to
print both next to each other
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
--
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 inbound email has been scanned for all viruses by the MessageLabs
SkyScan
service.
________________________________________________________________________
______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs
Skyscan service.
For more information please visit http://www.symanteccloud.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.
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.