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

Yes I compiled the PRTF as AFPDS otherwise it ignores *pagseg objects altogether.

I don't think that it works as you are suggesting.

I have *pagseg SIG123 in OLDLIB and also SIG123 in NEWLIB. Generally they are identical but a few are different. I am trying to locate those that are different (by printing both side by side and visually looking at the pair of signatures).

I created a PRTF (AFPDS) and named OLDLIB on one printer record and NEWLIB on a second printer record.

The pgm then writes both records.

I am thinking when the output writer goes to find the *pagseg at print time, it looks in the current *LIBL (which was the job's *LIBL that created the spool file) and uses that to find the *pagseg.

It seems to ignore the lib named on the printer DDS source.

I think that the printer DDS source uses the qualified lib at printer file CREATION time, but NOT at run time (print time).

I may be wrong but it SEEMS to be doing that!

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

Are you defining the file as SCS or AFPDS? I think you'll need to do AFPDS to get the libraries recognized.

The print writer is a completely different job and maintains its own library list. It picks up definitions from the spool file and incorporates those definitions in its library list. If you specify a library by name in those pagseg arguments, it should try to use them. There's, of course, a possibility that the user profile the print writer is running as doesn't have authority to those libraries where the pagsegs are. If it can't "see" the specified library, I'm not sure where it'll go to try to find the pagseg object.

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

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=/c
om.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!

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

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