I've been told that before :) The one in QGPL has nothing but printer messages. File printed, printer started, printer ended, for all the hundreds of client access printers we have. Someone here must have duplicated that queue name which I should get rid of before it causes problems
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, February 14, 2008 9:53 AM
To: Midrange Systems Technical Discussion
Subject: RE: path to a message queue on a SAV command
Checked a couple of different lpars.
You're a freak of nature.
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 09:40 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc
Subject
RE: path to a message queue on a SAV command
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.
--
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.