Re: Page Segments, Library List, QTEMP

Hi Alan -

QTEMP is the first user library in the library list. The page segment
object is not in any other library on the system, much less the
library list.

And this is interesting...when I do a WRKOBJ and the page segment is
just in my QTEMP, it's found with the *ALL, *LIBL, and *USRLIBL
library options; it's not found with *ALLUSR or *CURLIB. I wonder if
the print processor is using *ALLUSR instead of *LIBL.

On Thu, Oct 25, 2012 at 11:55 AM, Alan Shore <ashore@xxxxxxxx> wrote:

Hi Michael
Where is QTEMP in the library list?
Does the library list contain the same name in a different library ABOVE
QTEMP?

Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Thursday, October 25, 2012 11:51 AM
To: Midrange Systems Technical Discussion
Subject: Page Segments, Library List, QTEMP

Hi folks -

I have a program that produces an AFP file by combining overlays and
page segments. Works well, been in production for years. I've changed
the location of the page segments (for archival reasons) to QTEMP.
And, QTEMP is in the interactive job's library list. However, when I run
the program and print the AFP spooled file, it's not picking up the page
segment from QTEMP. When I CRTDUPOBJ from QTEMP to some other library in
the library list, it's found and is printed. Anyone know if there's
something different about QTEMP in this context? I'm using variable
names for the page segment name in my program and printer file, and I'm
not qualifying the name of the page segment. I do a DSPFD on the printer
file and don't see anything that makes me think anything is hardcoded.

Thanks!

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


Disclaimer: This message contains confidential information and is
intended only for the individual named. If you are not the named
addressee you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system. E-mail
transmission cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the contents of this
message, which arise as a result of e-mail transmission. If verification
is required please request a hard-copy version. Any views or opinions
presented are solely those of the author and do not necessarily
represent those of the company.
--
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 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.