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



Rob:

I always create a message queue called “backup”. Send the messages for SWA there. Now all the check point messages etc. are all in a similar spot for other uses, if any. I clear the queue as part of normal weekly maintenance so it does not cause a message queue full problem. Wrap is a possibility but I don’t do that so we can get back to the beginning if needed.

Avoids 1000s of places to look for messages and cleans up the system some.

Jim Oberholtzer
Agile Technology Architects



On Feb 21, 2020, at 3:06 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

We have a BRMS backup and control group we are using for nightly saves.
Quick-EDD has a recommended technique to initiate a save from your primary machine. It generates a special journal entry which the target machine picks up and does some stuff and then starts up the BRMS backup with the right control group. This way your save is done on your target machine without impacting production.

That is pretty much no problem.
The problem is that I am getting the message in the subject line regarding two message queues: LINK and one of our QRY* library names.

Here's the control group:
Weekly Retain Save SWA
Backup List ASP Activity Object While Message Sync
Seq Items Type Device SMTWTFS Detail Active Queue ID

10 *SAVSECDTA *DFTACT *NO
20 *SAVCFG *DFTACT *NO
30 *ALLDLO *DFTACT *NO *YES
40 *LINK *ALLAVL *DFTACT *YES *YES *LIB *NONE
50 QRY* *SYSBAS *DFTACT *OBJ *LIB *LIB *NONE
60 ALLULIBEXC *OBJ *SYSBAS *DFTACT *OBJ *SYNCLIB EDHSAVSYNC *NONE
70 *EXIT *DFTACT

I suspect the error is because the SWA Message Queue for entry 40 and 50 is *LIB. 40 generates the LINK message and 50 generates the QRY013007 message.
I wonder why I am getting that message in for these objects, especially the QRY013007 library, and none others. I'm sure there's a majority of libraries which do not have a message queue named after it.
I don't want to use the EDHSAVSYNC as I suspect that's one of the things Quick-EDD uses to know that the backup is done and it can start the apply processes back up.
Can I just stick some message queue in there like QSYSOPR?
I am doing no MONSWABRM stuff.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

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.