We have at least one task that at shutdown the end of task is missed and it remains in STOPPING status until we change the status to DOWN manually. It is a special case where this is in the TCPIP autolog list - it is a child to TCPIP so at shutdown TCPIP is not stopped until its status is DOWN, and TCPIP autologs it after a delay. Why this is mentioned is that this happens both in the general shutdown as many tasks are coming down and status is posted and then when it is basically the only activity on the system. It is not an issue of the OPSMAIN task relative importance as that task has the maximum importance on the system available.
20SEP 06:03:23 OPS7902H STATEMAN ACTION FOR STCTBL.SNMPD: UP_DOWN MVSCMD=P SNMPD
20SEP 06:03:23 P SNMPD
20SEP 06:03:23 EZZ6204I SIGTERM RECEIVED FOR SNMP DAEMON WHICH IS NOW SHUTTING DOWN
20SEP 06:03:23 BPXF024I (SNMPD) Sep 20 10:03:23 snmpagentÝ16908706¨: EZZ6204I
20SEP 06:03:23 SIGTERM received for SNMP daemon which is now shutting down.
20SEP 06:03:23 USSPROCEND SNMPD 00F7 16908706 1STCALL TERM EZASNMPD
20SEP 06:03:23 - --TIMINGS (MINS.)-- ----PAGING COUNTS---
20SEP 06:03:23 -JOBNAME STEPNAME PROCSTEP RC EXCP CPU SRB CLOCK SERV PG PAGE SWAP VIO SWAPS STEPNO
20SEP 06:03:23 -SNMPD SNMPD 00 3013 .00 .00 .00 2258 0 0 0 0 0 1
20SEP 06:03:23 IEF404I SNMPD - ENDED - TIME=06.03.23
20SEP 06:03:23 -SNMPD ENDED. NAME- TOTAL CPU TIME= .00 TOTAL ELAPSED TIME= .00
20SEP 06:03:23 SNMPD S0032908 ENDED MAXCC=00000 SUBSYS=STC
20SEP 06:03:23 $HASP395 SNMPD ENDED - RC=0000
20SEP 06:03:23 IEA989I SLIP TRAP ID=X33E MATCHED. JOBNAME=*UNAVAIL, ASID=00F7.
20SEP 06:03:23 STC SNMPD
20SEP 06:03:23 OPS7902H STATEMAN ACTION FOR STCTBL.CICTN05A: STOPPING_DOWN=NO ACTION FOUND
20SEP 06:03:23 OPS7902H STATEMAN ACTION FOR STCTBL.SNMPD: STOPPING_DOWN=NO ACTION FOUND
The Inactivation Completion Event is "EOM SNMPD"
Is there a way to configure OPS/MVS so it can keep up with this message traffic?
Release : 13.5
Component : OPS/MVS
An incorrect jobname for the SNMPD definition caused the problem where the SNMPD's current_state was not set to Down. Update and re-load the policy for SNMPD to correct.
Another issue is that SNMPD is being managed by 2 entities. It is possible to leave SNMPD to be controlled (started/stopped) by TCPIP and still leave SNMPD under SSM, either in Passive mode so no Actions from SSM occur. Or, alternatively, leave it in Active mode and have specific actions for it to not start nor stop but issue WTO's or send email/notifications based on the mismatch of states.