Re: Situation real name

I'm thinking that the lesson here is to take John's advice first, even if
it contradicts what you've read somewhere else :)

Dr. Frank Tate
Frank.Tate-9LkaxTQlAnxWk0Htik3J/[email protected]
Gulf Breeze Software Partners
http://www.gulfsoft.com


On Tue, Apr 16, 2013 at 10:46 AM, John Alvord <jalvord-r/[email protected]> wrote:

> When not specified, CMS_DUPER defaults to YES. That is why you see the _Z_
> situations.
>
> The doc may be confusing, but you can disable it by specifying
> CMS_DUPER=NO.
>
> Here are some notes I have for a technote:
>
> CMS_DUPER  has been around "forever".  For a long time it had many
> restrictions.  For example
>
> Duper Eligibility Requirements
> Same Table
> Same interval
> New combined _Z_ Situation <10 predicates
> Combine sits with different distribution lists
>
> Duper Exclusions
> Take Action
> Display Item
> Used in Policy
> Embedded situations
> Until clauses
> *MISSING
> *STR
> *COUNT
> =====================================
> For a long time it stayed like that. It can be disabled with an
> environment variable CMS_DUPER=NO - default is yes.
>
> In ITM 630 and [I think] ITM 623 FP2 the Take Action and DisplayItem
> exclusions were relaxed. Not ITM 623 FP1 level.
>
> It is a tremendous benefit for something like z/OS CICS Agent, where there
> can be hundreds or thousands of CICS regions in an LPAR. When just a few
> are combined or melded no gigantic benefit.
> ==================================================================
> The relaxation of restrictions mean it will show up in more places.
>
> It looks to me like you could get a definitive trace t with the following
>
> KBB_RAS1='error (unit:ko4lodge,Entry="newSitRec::buildNameAndPredicate"
> all er)'
>
> or service console
>
> ras1 set  error (unit:ko4lodge,Entry="newSitRec::buildNameAndPredicate"
> all er)
>
> A message something like
>
> Created new sit <%s> by melding <%s>
>
>
> Regards,
>
>
>   *John Alvord* - Ph: 1-720-396-2788    Cell: none
> Customer Support - Tivoli Software - *jalvord-r/[email protected]*<[email protected]>
> Advisory Engineer - Tivoli Monitoring - ITM infrastructure
> Developer Blog - *Wonderful World of Situations*<https://www.ibm.com/developerworks/mydeveloperworks/blogs/jalvord>
> Follow us on Twitter! *@Tivolisupport* <http://twitter.com/TivoliSupport>and
> *Facebook* <https://www.facebook.com/IBMTivoliSupport>
> Personalize your support needs with the *IBM Support Portal*<http://www.ibm.com/support/electronicsupport/>
> Use *Service Request*<http://www.ibm.com/software/support/servicerequest/quick_start.html>to get assistance!
> For emails regarding a PMR, copy *[email protected]*<[email protected]>
> For secure browser uploads: *https://www.ecurep.ibm.com/app/upload*<https://www.ecurep.ibm.com/app/upload>
> For Customer Support guidance: *IBM Software Support Handbook*<http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html>
>  <http://twitter.com/TivoliSupport>
>
>
>
>
> From:        "Liu, Jun Feng" <[email protected]>
> To:        "Discussion list for Tivoli product and Tivoli Ready
> products." <[email protected]>,
> Date:        04/16/2013 06:54 AM
> Subject:        RE: [TME10] Situation real name
> Sent by:        [email protected]
> ------------------------------
>
>
>
> Thanks, John
>
> I just checked the deployment guide, looks like it disable by default.
>
> CMS_DUPER
> This parameter enables or disables situation synchronization of common
> filter objects actually monitored by agents or endpoints. Enabling this
> setting in monitoring server environments with predominantly z/OS address
> space applications for example, OMEGAMON® XE for CICS® or Sysplex, improves
> performance and response time by limiting data collection samplings on
> behalf of running situations. Enable it by setting the value to YES.
> Disable by setting the value to NO. By default this parameter is not
> enabled.
>
>
> Thanks
>
> Jun Feng Liu
>
> TD| Enterprise IT Operations (EITO) I *Monitoring Tools Services *
>
> SOC: (416) 983-9293 | C: (416) 428-4932
>
>
>
> *http://w4.oam.td.com/oar/monitoring/client/Pages/Default.aspx*<http://w4.oam.td.com/oar/monitoring/client/Pages/Default.aspx>
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *John Alvord*
> Sent:* Monday, April 15, 2013 7:51 PM*
> To:* Discussion list for Tivoli product and Tivoli Ready products.*
> Subject:* Re: [TME10] Situation real name
>
> Until ITM 623 FP3 is is a pretty tough thing to figure out. I was told
> there was a trace at that level which clarifies what the duperized
> situation constituents are.
>
> The _Z_  situation are "Duperized Situations"  where multiple situations
> are merged into one under some specific conditions. I have sometimes
> figured it out by looking at the Situation "PREDICATE" SQL in the SITDB and
> then looking through the situations which might have been merged and
> figuring it out.
>
> One way to proceed is to temporarily add CMS_DUPER=NO - say to the
> [Linux/Unix] KBBENV file and recycling the TEMS. Then when the error is
> seen it will relate to one or more of the underlying situations. When you
> work that out you can remove the CMS_DUPER=NO and continue.
>
> Regards,
>
>
>
>
>
>
>   *John Alvord* - Ph: 1-720-396-2788    Cell: none
> Customer Support - Tivoli Software - *jalvord-r/[email protected]*<[email protected]>
> Advisory Engineer - Tivoli Monitoring - ITM infrastructure
> Developer Blog - *Wonderful World of Situations*<https://www.ibm.com/developerworks/mydeveloperworks/blogs/jalvord>
> Follow us on Twitter! *@Tivolisupport* <http://twitter.com/TivoliSupport>and
> *Facebook* <https://www.facebook.com/IBMTivoliSupport>
> Personalize your support needs with the *IBM Support Portal*<http://www.ibm.com/support/electronicsupport/>
> Use *Service Request*<http://www.ibm.com/software/support/servicerequest/quick_start.html>to get assistance!
> For emails regarding a PMR, copy *[email protected]*<[email protected]>
> For secure browser uploads: *https://www.ecurep.ibm.com/app/upload*<https://www.ecurep.ibm.com/app/upload>
> For Customer Support guidance: *IBM Software Support Handbook*<http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html>
>
>
>
>
>
>
> From:        "Liu, Jun Feng" <*[email protected]* <[email protected]>>
> To:        "Discussion list for Tivoli product and Tivoli Ready
> products." <*[email protected]* <[email protected]>>,
> Date:        04/15/2013 01:23 PM
> Subject:        [TME10] Situation real name
> Sent by:        *[email protected]*<[email protected]>
> ------------------------------
>
>
>
>
> In the kdsmain.msg, I saw below error message:
>
> 4/07/13 21:35:27 KDSPM021   Storage limit exceeded attempting to process
> situation _Z_KLOLOGPEVT17.
> 04/07/13 21:35:27 KO41039    Error in request _Z_KLOLOGPEVT17. Status=
> 1178. Reason= 50.
> 04/07/13 21:35:27 KO41039    Error in request _Z_KLOLOGPEVT17. Status=
> 1131. Reason= 1131.
>
> How can I find out the real name for the situation _Z_KLOLOGPEVT17. I
> tried use tacmd viewsit:
>
> tacmd viewsit -s _Z_KLOLOGPEVT17
>
> KUICVS005E: The situation _Z_KLOLOGPEVT17 does not exist on server *
> https://XXXX.com:3661* <https://xxxx.com:3661/>.
>
> The command did not complete because the specified situation was not found
> on the server.
>
> Specify a valid situation name and try running the viewsit command again.
>
>
> Thanks
>
> Jun Feng Liu
>
>
>
>
> NOTICE: Confidential message which may be privileged. Unauthorized
> use/disclosure prohibited. If received in error, please go to *
> www.td.com/legal* <http://www.td.com/legal> for instructions.
> AVIS : Message confidentiel dont le contenu peut être privilégié.
> Utilisation/divulgation interdites sans permission. Si reçu par erreur,
> prière d'aller au *www.td.com/francais/avis_juridique*<http://www.td.com/francais/avis_juridique>pour des instructions.
> _______________________________________________
> TME10 mailing list*
> **[email protected]* <[email protected]>
>
> Unsubscribe:[email protected]
> _______________________________________________
>
> TME10 mailing list
> [email protected]
> Unsubscribe:[email protected]
>
>
> _______________________________________________
> TME10 mailing list
> [email protected]
> Unsubscribe:[email protected]
>
>

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]