OPS/MVS

 View Only
  • 1.  OPS7902H messages not being produced

    Posted May 19, 2023 03:17 PM

    Hello All, I have run across a v14 system that is not producing the OPS7902H message to allow monitoring of the tasks state changes in SSM.   I thought =4;1;1the STATENOACTMSG parm was the owner, but it is set to YES like my other systems.

    Does anyone know what the parm is to turn on these messages?  

    I don't see any rules or MPF entries that would be suppressing them

    Thank you 
    Chris Allamon



    ------------------------------
    Chris Allamon
    Navy Federal CU
    ------------------------------


  • 2.  RE: OPS7902H messages not being produced

    Posted May 19, 2023 03:25 PM

    forgot the text of the message to make it easier  
    OPS7902H STATEMAN ACTION FOR STCTBL.CICSCTA: STARTING_UP=NO ACTION FOUND    

    the OPS7914T message is also not appearing in the log and SSMAUDIT=YES is set.



    ------------------------------
    Chris Allamon
    Navy Federal CU
    ------------------------------



  • 3.  RE: OPS7902H messages not being produced

    Posted May 22, 2023 03:30 AM

    The STATENOACTMSG should only affect OPS7902H if no stateman action was found for the ssm mismatch. So OPS1270H should appeaer any way. Are you sure that other system does not have the msg severity changed (To be able to automate it)? 



    ------------------------------
    Automated Operations
    Atos
    Netherlands
    ------------------------------



  • 4.  RE: OPS7902H messages not being produced

    Posted Aug 04, 2023 05:59 AM

    Or if you have a rule like this: 

    )MSG OPS7902* NOOPSLOG  



    ------------------------------
    Automated Operations
    Atos
    Netherlands
    ------------------------------