|
We do have the Admin Domain configured currently. However, we have many
objects in *SYSBAS that are not one of the Admin Domain capable or MRE
types that we are trying to keep in sync as well as objects that the
Admin's may have neglected to add to the Admin Domain. Some of the
objects are vendor objects that are not IASP compatible.
Jack Kingsley wrote on 08/07/2012 09:51:15 AM:
From: Jack Kingsley <iseriesflorida@xxxxxxxxx>send
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 08/07/2012 09:51 AM
Subject: Re: QcstListClusterResourceGroupIn API issue question
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Not sure what you need to send, there are object type(s) that you can
to make sure they are in sync at the sysbase level within your admindomain
setups. From the wrkclu screen take an option 8, then by your admindomain
take an option 7, then hit a 1 to add, you should see all the differentyou
resource types that you can keep in sync, will this work for you, maybe
could give more information.--
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 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.