RE: Queries regarding Indications behaviour.

Thank you Marek and Ashok, we will look on these two and get back to you soon.

Regards,
Karthik P K

From: Marek Szermutzky [mailto:[email protected]]
Sent: Thursday, November 08, 2012 2:24 PM
To: Karunanithy, Karthik
Cc: Subbaiah, Kamalalochana; [email protected]
Subject: Re: Queries regarding Indications behaviour.

As Ashok wrote, the "Out of order" indication delivery was fixed in OP 2.12 and using the released version should not exhibit out of order delivery.
Regarding number 1, that is not expected behavior. If OP behaves that way it definitely is a Bug. Can you reproduce using OP 2.12 ? We have fixed quite a number of things for indications in that release.


Kind regards,
Marek Szermutzky

Software Engineer / OpenPegasus Maintainer (PMC) and z/OS PlatformRep.
IBM Systems &Technology Group, Systems Software Development / z/OS Capacity Management and Support
-------------------------------------------------------------------------------------------------------------------------------------------
IBM Deutschland
Schoenaicher Str. 220
71032 Boeblingen
Phone: +49-7031-16-5182
E-Mail: [email protected]<mailto:[email protected]>
-------------------------------------------------------------------------------------------------------------------------------------------
IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294



From:        Ashok K Pathak <[email protected]<mailto:[email protected]>>
To:        "Karunanithy, Karthik" <[email protected]<mailto:[email protected]>>
Cc:        "Subbaiah, Kamalalochana" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Date:        07.11.2012 12:42
Subject:        Re: Queries regarding Indications behaviour.
________________________________



For question 2  I think you can look the defect   9013(Indications arrives
out-of-order from provider to handler. ) which is part of already  released
2.12  version  which seems to address  the issue

     Regards
     Ashok



            "Karunanithy,
            Karthik"
            <KarthikPachaiapp                                          To
            an.Karunanithy@ne<mailto:an.Karunanithy@ne>         "[email protected]<mailto:[email protected]>"
            tapp.com>                 <[email protected]<mailto:[email protected]>>
                                                                       cc
            07-11-2012 16:40          "Subbaiah, Kamalalochana"
                                      <[email protected]<mailto:[email protected]>>
                                                                  Subject
                                      Queries regarding Indications
                                      behaviour.










Hi ,

               We have some queries related to the functionality of
indications in Open Pegasus. It would be great if someone can confirm on
these behaviors.

     1.       Cimserver shutdown fails with pending Indication delivery –
     Indications were subscribed. Indication listener was shut down. Stop
     the cimserver. Cimserver does not shut down.

     2.       Out of order indication delivery – Indication subscription
     was created for ClassA followed by indication subscription to ClassB.
     Two life cycle indications were generated(IndicationA for instance
     Class A followed by IndicationB for instance of Class B).
     IndicationB(indication  for class B) was delivered followed by
     delivery of IndicationA (indication for class A). The expected
     behavior is IndicationA delivered first and then IndicationB. We
     suspect that indication thread created for indicationB finding the
     subscription  earlier in the list when compared to subscription for
     class A causing it to deliver the indication out of order.

Regards
Karthik