CA Mainframe Application Tuner

Expand all | Collapse all

Currently we have the following program in our PLT TC00CPLT.

  • 1.  Currently we have the following program in our PLT TC00CPLT.

    Posted 06-17-2016 02:57 PM


    We get a lot of these in MSGUSR and want to stop them.

    1. 01.28.16 STC49608 +TN0894W Field=pggcl accumulation over maximum value.  TRAN=SI61 
    2. 02.27.51 STC49608  +TN0894W Field=pgpcl accumulation over maximum value. TRAN=SI61 
    3. 03.53.46 STC49608  +TN0894W Field=pggcl accumulation over maximum value. TRAN=PAD5 

      03.53.46 STC49608  +TN0894W Field=pgpcl accumulation over maximum value.  TRAN=PAD5 

     

    Can we remove the program from the PLT and then MANUALLY START CA-MAT with CICS up if we want to take statistics on the fly ?

    Thanks,

    Ed 



  • 2.  Re: Currently we have the following program in our PLT TC00CPLT.

    Posted 06-20-2016 08:52 AM

    HI Ed,

     

    When CICS statistics are enabled we collect most of the stats available for a transaction. The counters are running counters. In the case of these two messages we are counting channel gets and puts for the transactions mentioned in the message (ie.SI61, PAD5).     

     

    The message is indicating that we have exceeded the max number of occurrences that we can accumulate. There is no harm here, we know we have maxed the counter and the message is just a warning. We won't overflow, or cause any issues. This message was added via PTF about 5 years ago when we first introduced this part of the CICS feature specifically because we overflowed a counter and had some problems. We need to prevent the overflow from causing issues and we need to issue the message so users will know that if they start collecting stats about the transaction(s) in question, the stats won't be accurate we put into the monitor file and report on will not be accurate because of the overflow.     

                       

    To suppress the messages, you need to ask yourself how the CICS region you are having issues with, is configured?

    Do you only request data for specific transactions using the CICS option in monitor definition?

    If yes, you can run an unfiltered monitor so that we actually report on the mentioned transactions, those buckets will get cleared and the message will not be produced.                    

     

    Regards Hennie Hermans, CA Technologies, Support.                                     



  • 3.  Re: Currently we have the following program in our PLT TC00CPLT.

    Posted 06-20-2016 01:11 PM

    Well,

    Here is what we really want.

    1) The messages to go away

    2) Turn off gathering stats

    3) turn on ONLY when we want to in a CICS region , on the fly, without recycling CICS.

     

    If we take out the PLT program:  PROGRAM=TC00CPLT

    If our Global options are coded as this:

    MONITOR=YES,MAXTRANS=2000,COLLECT_TRAN=TUNC,RESET_TRAN=TUNS,COLLECT=0   

     

    Can we then go into individual CICS regions and perform a : TUNS and now that CICS region will be initialized for CA-MAT?

     

    Thanks for your response.

    Ed 

     



  • 4.  Re: Currently we have the following program in our PLT TC00CPLT.

    Posted 06-21-2016 03:13 PM

    So we have made some progress, yet we still have a new question:

    It is in the as an aside section at the bottom..................

     

    In
    conclusion, I have verified that if we STOP initializing CA-MAT in the PLT, and
    keep the Parm MONITOR=YES in the
    SYSOT.CAMAT.R10.UTRPARM(CICSGLBL), then we can manually start CA-MAT from any CICS region with the TUNS transaction.

    I
    talked with Steve and we will set this up for the August DC RLSE.

    I
    will begin in the lower environments.

     

     

     

     

    CA-MAT initialized from the PLT messages:

    TN0896I 06/19/2016 03:38:34
    0000008 SERVERID parameter <MATUNER > ( ACTIVE  ) entered from SIT INITPARM
    .                      

    TN0882I 06/19/2016 03:38:34 0000008 CICSGLBL: CA MAT monitoring ON
    <MATUNER >                                                 

    TN0876I 06/19/2016 03:38:34 0000008 CICSGLBL: Summary statistics
    collection frequency set to 00 minute(s) <MATUNER >          

    TN0872I 06/19/2016 03:38:34 0000008 CICSGLBL: MAXTRANS value set to
    2000 <MATUNER >                                           

    TN0824I 06/19/2016 03:38:34 0000008 CICSGLBL: CA MAT COLLECT
    transaction=TUNC <MATUNER >                                      

    TN0890I 06/19/2016 03:38:34 0000008 CICSGLBL: CA MAT RESET
    transaction=TUNS <MATUNER >           
                               

    TN0823I 06/19/2016 03:38:34 0000008 CA MAT TC69CMPX user exit
    program loaded at: A5665D00                                     

    TN0830I 06/19/2016 03:38:34 0000008 CA MAT TC69CMPX global workarea
    at: 00064000                                              

    TN0823I 06/19/2016 03:38:34 0000008 CA MAT TC69CSTO user exit
    program loaded at: A5667700                                     

    TN0830I 06/19/2016 03:38:34 0000008 CA MAT TC69CSTO global workarea
    at: 0006C000                                              

     

    • The
      first message is not getting loaded if we take out the PLT:

    I
    believe this entry is what causes the first message above

    1. SYSCT.CICS.SYSIN(CICSTEST)
      -

    INITPARM=(TC69FSET='SERVERID=MATUNER')

     

    TN0896I

    Last
    update June 5, 2015

    SERVERID parameter <ssssssss> (*********)
    entered from yyyyyyyyyyyyyyyyy.



    Reason:

    This message is issued if the SERVERID parameter is specified either by SIT or RESET transaction.

    • ssssssss

          
      Specifies
           the CA Mainframe Application Tuner ServerID.
    • *********

          
      Is
           either ACTIVE or NOT FOUND indicating the CA Mainframe Application Tuner
           Server is either active or not found.
    • yyyyyyyyyyyyyyyyy

          
      Is
           either 'SIT INITPARM' (from SIT) or 'RESET transaction' (from CICS terminal).

     

     

     

    CA-MAT initialized from a TUNS transaction in
    CICS with no initialization from the PLT messages:

    TN0882I 06/20/2016 16:24:32 0000141 CICSDFLT: CA MAT monitoring ON
    <CICSTRD >                                                     

    TN0876I 06/20/2016 16:24:32 0000141 CICSDFLT: Summary statistics
    collection frequency set to 01 minute(s) <CICSTRD >               

    TN0872I 06/20/2016 16:24:32 0000141 CICSDFLT: MAXTRANS value set to
    2000 <CICSTRD >                                               

    TN0824I 06/20/2016 16:24:32 0000141 CICSDFLT: CA MAT COLLECT
    transaction=TUNC <CICSTRD >                                           

    TN0890I 06/20/2016 16:24:32 0000141 CICSDFLT: CA MAT RESET
    transaction=TUNS <CICSTRD >                                             

    TN0823I 06/20/2016 16:24:33 0000141 CA MAT TC69CMPX user exit
    program loaded at: A5561000                                          

    TN0830I 06/20/2016 16:24:33 0000141 CA MAT TC69CMPX global workarea
    at: 00078000                                                  

    TN0823I 06/20/2016 16:24:33 0000141 CA MAT TC69CSTO user exit
    program loaded at: A55C7D00                                          

    TN0830I 06/20/2016 16:24:33 0000141 CA MAT TC69CSTO global workarea
    at: 00200000                                                  

    TN0880I 06/20/2016 16:24:33
    0000141 CA MAT/CICS options successfully refreshed
                                                         

     

    • I believe it
      is still initializing with the correct CICS version module, TC69FSET

     

     

     

    TN0880I

    Last update March 13, 2015

    CA MAT/CICS options successfully refreshed



    Reason:

    This is the last of a series of normal messages issued during RESET transaction (TUNS) processing.
    For more information, seeInstalling section.



    Action:

    Processing continues. Information message only.



    Origin:

    TCnnFSET

     

     

     

    Of course with this method, once it is loaded with TUNS, it will
    stay on until either the region is recycled or we change the Monitor=YES to =NO
    in 
    SYSOT.CAMAT.R10.UTRPARM(CICSGLBL)

     

     

     

    An
    aside,

    Today
    Ted and I tried to figure exactly where we are loading the CICSGLBL parms from.

    He
    changed SYSOT.CAMAT.R10.UTRPARM(CICSGLBL) MONITOR from YES to NO and I reran
    the TUNS transaction in a CICS region. Nothing changed.

    He
    then recycled the CA-MAT address space and the PLT ran and the region came up
    with Monitor=NO

    I
    then reran the CICS transaction TUNS and the TDQ showed Monitor=YES !

    Ted
    will ask CA about this and I will update my community question as well.

      

    Ed



  • 5.  Re: Currently we have the following program in our PLT TC00CPLT.

    Posted 06-27-2016 10:32 AM

    Hi Ed,

     

    To prevent these message from appearing you don't need to remove the PLT entry from CA MAT in your CICS environment..

    It's only necessary to set the COLLECT value to 0...

    When you have CA MAT v9 you will need to change this in the CA MAT UTRPARM member CICSOPTS.

    If you are at CA MAT v10 or above you will need to change this in the UTRPARM member CICSGLBL, or if you have region specific parameter settings in the CICSREGN member.

    After you set the COLLECT=0 parameter you need to recycle the CA MAT server started task and run the TUNS transaction in CICS when the CA MAT server task is fully started.

     

    If you have the COLLECT=0 specified you still will get the statistics in the ISPF Option 6 TranView and in the transaction details.

    However to get statistics in the ISPF Option 14, CICS Summary Stats, you will need to change the COLLECT to a value above 0.

     

    With kind regards,

    Hennie Hermans, CA Technologies, Support.      



  • 6.  Re: Currently we have the following program in our PLT TC00CPLT.

    Posted 07-28-2016 02:32 PM

    Thanks Hennie for your answer, this would definatly work.

    I think at this point, because no one ever uses this product except maybe 1 or 2 times a year, We would like to just keep it off and only turn it on at will in specific CICS regions.

    So this is how far we have gotten so far:

    I can turn Monitoring on and off but only once.

    I can’t turn it on again while keeping CICS and CA-MAT up.

    Are there any other parms I can use with the CICS transactions: TUNS ? 

    Besides the following:

    TUNS

    TUNS MATUNER

     

     

    Here is my scenario:

    If I don’t start CA-MAT from the CICS PLT but it is still in our SYSIN: INITPARM=(TC69FSET='SERVERID=MATUNER')  

    I can start it in CICS by typing : TUNS

    I get the results from CICSDFLT

    Result:

    TN0882I 07/28/2016 14:04:04 0063051 CICSDFLT: CA MAT monitoring ON <CICSU

    TN0876I 07/28/2016 14:04:04 0063051 CICSDFLT: Summary statistics collecti

    TN0872I 07/28/2016 14:04:04 0063051 CICSDFLT: MAXTRANS value set to 2000

    TN0824I 07/28/2016 14:04:04 0063051 CICSDFLT: CA MAT COLLECT transaction=

    TN0890I 07/28/2016 14:04:04 0063051 CICSDFLT: CA MAT RESET transaction=TU

    TN0823I 07/28/2016 14:04:04 0063051 CA MAT TC69CMPX user exit program loa

    TN0830I 07/28/2016 14:04:04 0063051 CA MAT TC69CMPX global workarea at: 0

    TN0823I 07/28/2016 14:04:04 0063051 CA MAT TC69CSTO user exit program loa

    TN0830I 07/28/2016 14:04:04 0063051 CA MAT TC69CSTO global workarea at: 0

    TN0880I 07/28/2016 14:04:04 0063051 CA MAT/CICS options successfully refr

     

    If I then type in: TUNS MATUNER

    I get the parms from the CICSGLBL member 

    We have coded Montor=off

    Results:

    TN0896I 07/28/2016 14:06:18 0063225 SERVERID parameter <MATUNER > ( ACTIV

    TN0883W 07/28/2016 14:06:18 0063225 CICSGLBL: CA MAT monitoring OFF. Use

    TN0876I 07/28/2016 14:06:18 0063225 CICSGLBL: Summary statistics collecti

    TN0872I 07/28/2016 14:06:18 0063225 CICSGLBL: MAXTRANS value set to 2000

    TN0824I 07/28/2016 14:06:18 0063225 CICSGLBL: CA MAT COLLECT transaction=

    TN0890I 07/28/2016 14:06:18 0063225 CICSGLBL: CA MAT RESET transaction=TU

    TN0827I 07/28/2016 14:06:18 0063225 CA MAT XMNOUT   user exit program dis

    TN0827I 07/28/2016 14:06:18 0063225 CA MAT XSTOUT   user exit program dis

    TN0880I 07/28/2016 14:06:18 0063225 CA MAT/CICS options successfully refr

     

     

    This all works great !

     

    But now if I want to turn Monitoring on in the same CICS region for a second time, without any recycles, I get the following:

    If I type TUNS:

    Result:

    TN0802I 07/28/2016 14:08:01 0063307 Currently saved existing CICS parameters

    TN0883W 07/28/2016 14:08:01 0063307 CICSDFLT: CA MAT monitoring OFF. Use

    TN0876I 07/28/2016 14:08:01 0063307 CICSDFLT: Summary statistics collecti

    TN0872I 07/28/2016 14:08:01 0063307 CICSDFLT: MAXTRANS value set to 2000

    TN0824I 07/28/2016 14:08:01 0063307 CICSDFLT: CA MAT COLLECT transaction=

    TN0890I 07/28/2016 14:08:01 0063307 CICSDFLT: CA MAT RESET transaction=TU

    TN0884W 07/28/2016 14:08:01 0063307 Exit program TC69CMPX already disable

    TN0884W 07/28/2016 14:08:01 0063307 Exit program TC69CSTO already disable

    TN0880I 07/28/2016 14:08:01 0063307 CA MAT/CICS options successfully refr

     

     

    I can’t turn it back on again and leave everything up.

    Ed



  • 7.  Re: Currently we have the following program in our PLT TC00CPLT.

    Posted 08-04-2016 08:57 AM

    Hi Ed,

     

    thanks for the info.. I would advice to open a case for this last behavior so that we can investigate the cause of this 'strange' behavior of CA MAT and the activation/deactivation of the monitor.. This will give us the opportunity to get some documentation and also do some tests...

    Sorry for the inconvenience...

     

    With kind regards,

    Hennie Hermans, CA Technologies, Support.      



  • 8.  Re: Currently we have the following program in our PLT TC00CPLT.

    Posted 08-11-2016 07:15 AM

    Hennie,

    We do have a case #

    Case Comment 00460568

    Ed