× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Part two of this is for anyone doing save-while-active on IFS directories. We have 260,000 objects in the IFS (outside our optical image directory that is saved using a different process) that are getting backed up. If we turn on save-while-active and specify a message queue will the SAV send one message per object to that message queue? I was going to use the SAVACT(*YES) parameter and not the SAVACT(*SYNC) since I don't think I need to sync all of the IFS on a backup.

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.