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



Oops - this didn't work. It seemed like such a great idea.

An idea why the library is ignored on the DDS printer definition? And how to get the output writer to comply with the DDS specified library name?

It seems that the output writer ignores this library and always uses the *LIBL to find the *pagseg object.

Thanks!



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Thursday, January 23, 2014 11:34 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

Oh yeah - of course.

That should work perfectly.

Thanks!



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan Kimmel
Sent: Thursday, January 23, 2014 11:24 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

Use the PAGSEG keyword in a DDS Print File. It allows the library name and pagseg name to be specified. That path goes into the spool file to be resolved at print time. Use a program-to-system fields for the library name and the pagseg name. This example is from the infocenter page on the PAGSEG keyword; http://publib.boulder.ibm.com/infocenter/iadthelp/v7r0/index.jsp?topic=/com.ibm.etools.iseries.langref2.doc/rzakdmstptpagse.htm

A R REC2 PAGSEG(&LIB/&PSEG &POSD &POSA);
A LIB 10A P
A PSEG 8A P
A POSD 5S 3P
A POSA 5S 3P

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Thursday, January 23, 2014 11:01 AM
To: 'Midrange Systems Technical Discussion'
Subject: similar *PAGSEG objects in two libs with same name - how to print
both next to each other

I am trying to clean house a bit. There are two hopefully identical *PAGSEG
objects. They are signatures.

PAG123 is in OLDLIB, and also in NEWLIB.

How can I validate that they are the same signature?

The create date and other dates are of no use as they have been moved
around over the years and dates were altered during the moves.

The sizes are all the same so that doesn't help.

Any ideas?


The concern is that Sally Jones got married and changed her name to Sally
Smith.

Her signature PAG123 may be in OLDLIB as "Jones", but in NEWLIB as "Smith".

The best way I can think of is to print the old and new next to each other and
visually check.

There are about 500 signatures.



In RPG, I want to print the old on the left, the new on the right. So I need to
CHGCURLIB OLDLIB, load the pagseg into the print buffer, and then
CHGCURLIB NEWLIB and load it again.

But I am afraid that the *PAGSEG objects don't get resolved until print time,
so that wont work.


How can I print the OLDLIB and NEWLIB next to each other in RPG or COBOL?
Or is it not possible since they are not married up until the output writer
starts?

Thanks in advance!



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.