Re: SRVMON Jobs - New Twist?

[Sergio Toscano Lomeli/Mexico/IBM <stlomeli@xxxxxxxxxxx>]

Reason code 8 is a normal reason code when a watch session is ending. This
is not a problem and none of the PTFs posted before will fix it. Even when
you did not use ENDWCH, Service Monitor did. Service Monitor ends all of
those watch sessions every time it is ended.
Service Monitor can be restarted because of the following reasons:
1. Changing the QSFWERRLOG value from *LOG to *NOLOG and back to *LOG (this
starts the QSYSWRK/QSRVMON job - which starts the QUSRWRK/SRVMONxxxx jobs)
2. IPLing the system or restarting QSYSWKR and QUSRWRK subsystems - when
the subsystem comes up, the QSRVMON jobs will start -  which starts the
SRVMONxxxx jobs




                                                                           
             ChadB@wheeling-ni                                             
             sshin.com                                                     
             Sent by:                                                   To 
             midrange-l-bounce         Midrange Systems Technical          
             s@xxxxxxxxxxxx            Discussion                          
                                       <midrange-l@xxxxxxxxxxxx>           
                                                                        cc 
             27/07/2007 09:03                                              
                                                                   Subject 
                                       Re: SRVMON Jobs - New Twist?        
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
             <midrange-l@midra                                             
                 nge.com>                                                  
                                                                           
                                                                           





That sounds like one of the inventory or service director jobs sending
something off to IBM to me.

It seems that the batch of SRVMON messages on our boxes have kicked off
only once or twice in the week we've been at V5R4.  Did you just recently
upgrade?




             Jerry Adams
             <jerry@bwwholesal
             e.com>                                                     To
             Sent by:                  Midrange Systems Technical
             midrange-l-bounce         Discussion
             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>
                                                                        cc

             07/27/2007 09:53                                      Subject
             AM                        Re: SRVMON Jobs - New Twist?


             Please respond to
             Midrange Systems
                 Technical
                Discussion
             <midrange-l@midra
                 nge.com>






Chad,

Thanks.  Looking forward to hearing your results.  In the meantime I'll
go ahead and download the PTF's in preparation.

I check QSYSOPR messages every morning on both of our machines, but this
is the first time I have seen these messages.  These were on our
production box; haven't seen anything of this nature on our backup box.

I did notice this one issued about 20 minutes later:

Message ID . . . . . . :
TCP2617
Date sent  . . . . . . :   07/27/07      Time sent  . . . . . . :
05:32:26


Message . . . . :   TCP/IP connection to remote system 207.25.252.200
closed,
  reason code
2.


Cause . . . . . :   The TCP/IP connection to remote system
207.25.252.200 has
  been closed. The connection was closed for reason code 2.  Full
connection
  details for the closed connection
include:
    - local IP address is
12.65.66.10
    - local port is
59292
    - remote IP address is
207.25.252.200
    - remote port is
443

I don't think there's a connection, but that's just a WAG.  I can
actually hit the 207.25.252.200 address (an IBM HTTP Server site), but
not the 12.65.66.10 address.  The HTTP server on our system, for what
it's worth, is stopped.


             * Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
             615.995.7024
fax
             615.995.1201
email
             jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



ChadB@xxxxxxxxxxxxxxxxxxxx wrote:
> Jerry - in looking closer at my jobs I saw the same thing and found these
3
> V5R4 PTFs that seemed like a match for the reason code '08' :
>
> SI26806
> SI26745
> SI26817
> SI24998 (coreq of one of the 3)
> SI23663 (coreq of one of the 3)
>
> I put them on our dev box yesterday (they were all immediate PTFs) and
will
> see if they resolve the messages.  It sounds like the high number of jobs
> is normal, but I think the messages we've got will probably get resolved
> with these PTFs.

>              Jerry Adams

>              <jerry@bwwholesal

>              e.com>
To
>              Sent by:                  Midrange-L

>              midrange-l-bounce         <midrange-l@xxxxxxxxxxxx>

>              s@xxxxxxxxxxxx
cc
>

>
Subject
>              07/27/2007 08:02          SRVMON Jobs - New Twist?

>              AM

>

>

>              Please respond to

>              Midrange Systems

>                  Technical

>                 Discussion

>              <midrange-l@midra

>                  nge.com>

>

>

> There's been a little bit of a discussion here about the SRVMONxx jobs.
> I, too, have 78 of these running but, after the discussion and
> investigation, decided they were OK.  But this morning, when I checked
> QSYSOPR's messages something strange popped out:
>
> Message ID . . . . . . :
> CPI3999
> Date sent  . . . . . . :   07/27/07      Time sent  . . . . . . :
> 05:03:58
>
>
> Message . . . . :   Watch session SRVMON0000 issued by
> 223998/QUSER/QZRCSRVS
>   at 07/23/07 11:31:43 has been ended. Reason code:
> X'08'
>
>
> Cause . . . . . :   Watch session SRVMON0000 issued by
> 223998/QUSER/QZRCSRVS
>   and associated with QSCSWCH has been ended. Reason code: X'08'. The
> possible
>   reason codes
> follow:
>     08 - End Watch (ENDWCH) command or End Watch (QSCEWCH) API was
issued.
> The above is just a sample of 78 such messages sent between 05:03:58 and
> 05:05:15.
>
>
> Now the other side of the coin is that the jobs are running again.  The
> start times range from 05:05:20 and 05:05:34.
>
>
> I know that I didn't issue the ENDWCH command.  Any clues?
>
> --
>              * Jerry C. Adams
> *IBM System i Programmer/Analyst
> B&W Wholesale Distributors, Inc.* *
> voice
>              615.995.7024
> fax
>              615.995.1201
> email
>              jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.