Re: QcstListClusterResourceGroupIn API issue question

Are you using IASP or is all of this in sysbase

On Tue, Aug 7, 2012 at 9:09 AM, <mgarrison@xxxxxxxxxx> wrote:

Jack,

Thanks for responding. I am not sure what option the information is
displayed using WRKCLU as I am not authorized to use the service programs
associated with it. Maybe if I explain in a bit more detail as to what I
am looking for that might help. It is hard to test new processes when you
don't have authority to all of the required information. I do not have
authority to even run my code that is in question.

What I am calling the API to try and determine is what is the role at the
current moment of the system in which the program is running on. As an
example we have SystemA which is configured as the Primary, SystemB which
is configured as the Backup, and SystemC which is our off-site Disaster
Recovery system. We have done a role swap and are currently running on
the Backup System B and when I call the API it is retrieving the Current
node role for SystemA as the Primary and SystemB as the Backup and I
thought it should be reversed since the role swap. So, in short I would
like my program to know when it runs on each system as to which of the
systems is the current Production system. Is there a better/correct way
to determine the role of the system that my code is running on?

Thanks,
Mike Garrison

Jack Kingsley wrote on 08/07/2012 06:58:02 AM:

From: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 08/07/2012 06:58 AM
Subject: Re: QcstListClusterResourceGroupIn API issue question
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Mike, from a WRKCLU screen which option are you talking about or are you
referring to a dspaspssn.

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