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

On 23-Jan-2014 14:09 -0800, Stone, Joel wrote:

Dan Kimmel on Thursday, January 23, 2014 11:24 AM wrote:

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://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzakd/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

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

An idea why the library is ignored on the DDS printer definition?

This seems to imply that the value for &LIB did not find its way into the associated resources for the spool file.? Was a review made of the AFP resources for the SPLF; i.e. to reveal whence the resources should come? Here is an ad-hoc script to perform, after a spooled file named EXAMPLESPL was just created in the same job [adjust the Splf name accordingly within the scripted request to the List Spooled File AFPDS Resources (QGSLRSC) API]:


DLTUSRSPC QTEMP/USRSPC

call QUSCRTUS ('USRSPC QTEMP' ' ' x'00000010' x'00' '*EXCLUDE'
' ')

call QGSLRSC ('USRSPC QTEMP' LRSC0100 '*' ' ' ' ' EXAMPLESPL
x'FFFFFFFF' '*ALL' '*PAGSEG' '1' x'0000000000000000')

DMPOBJ QTEMP/USRSPC *USRSPC

DSPSPLF QPSRVDMP SPLNBR(*LAST) /* PgDn and review eye-catcher data */

And how to get the output writer to comply with the DDS specified
library name?

This seems to imply that the value for &LIB did find its way into the associated resources for the spooled file, but that in printing, the writer seemed not to use that specifically named resource.?

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

Use of *LIBL is expected during spool file creation whenever the library-name is not specified or its value is *LIBL. If the system-to-program field [aka p-Field] &LIB was not populated with a name, thus remains blank [as default], the effect may be the same as what is documented to occur when the library-name is not specified.