I thought that was remarkable. I only have one (QSYS). I might have
suspected that it would have been in QUSRSYS. If you have two (QSYS and
QGPL), the one you're likely using is in QSYS (based on system values and
library lists).

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

"i" comes before "p", "x" and "z"
e gads

Our system's had more names than Elizabeth Taylor!

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com
http://www.systemiconnection.com/




Mike Cunningham
<mcunning@xxxxxxx
> To
Sent by: "'Midrange Systems Technical
midrange-l-bounce Discussion'"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc

02/14/2008 09:40 Subject
AM RE: path to a message queue on a
SAV command

Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>






Looking again I actually show two. Looking at each the one I want is the
one in QSYS

Library . . . . . . . : QGPL Library ASP dev
Library ASP gro

Type options, press Enter.
5=Display full attributes 8=Display service attribut

Opt Object Type Attribute Size
QSYSOPR *MSGQ 196608

Library . . . . . . . : QSYS Library ASP dev
Library ASP gro

Type options, press Enter.
5=Display full attributes 8=Display service attribut

Opt Object Type Attribute Size
QSYSOPR *MSGQ 176128

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, February 14, 2008 8:57 AM
To: Midrange Systems Technical Discussion
Subject: Re: path to a message queue on a SAV command

WRKOBJ QSYSOPR on my machine shows QSYSOPR to be in QSYS, not QGPL.
Then, yes, modify your statement to '/QSYS.LIB/QSYSOPR.MSGQ' and you
should be in.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Mike Cunningham <mcunning@xxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/14/2008 08:52 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
path to a message queue on a SAV command






If I wanted to use a SAV command with save-while-active (SAVACT(*YES)) and
have the checkpoint messages go to QSYSOPR like on a SAVLIB command is the
correct path to the QSYSOPR message queue look like this?
'/QSYS.LIB/QGPL.LIB/QSYSOPR.MSGQ' I can't find any examples of how to
specify a message queue in path format.
--
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.

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

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.