RE: QS9SFWMON job missing.

[Justin Taylor <JUSTIN@xxxxxxxxxxxxx>]

My 7.3 system has one active.  It looks like for us a new one start every day.



-----Original Message-----
From: Jeff Crosby [mailto:jlcrosby@xxxxxxxxxxxxxxxx] 
Sent: Tuesday, February 20, 2018 9:04 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: QS9SFWMON job missing.

In the FWIW department -

On our 7.1 production system, all 5 jobs are active.  DSPLOG of job QS9SFWMON shows it ending/starting every day before/after the backup.

On the 7.3 system in the cloud (that we will be moving to fairly soon) only the 4 jobs you show running are running.  QS9SFWMON is not running.  If I do a DSPLOG of job QS9SFWMON the only entry I get is:

                         Display History Log Contents



Job 557417/QSRVAGT/QS9SFWMON ended on 01/22/18 at 10:00:07; .556 seconds used

Details:

                         Additional Message Information



 Message ID . . . . . . :   CPF1164

 Date sent  . . . . . . :   01/22/18      Time sent  . . . . . . :
 10:00:07


 Message . . . . :   Job 557417/QSRVAGT/QS9SFWMON ended on 01/22/18 at

   10:00:07; .556 seconds used; end code 50



                     X.



 Cause . . . . . :   Job 557417/QSRVAGT/QS9SFWMON completed on 01/22/18 at

   10:00:07 after it used .556 seconds processing unit time. The maximum

   temporary storage used was 3 megabytes. The job had ending code 50. The job
   ended after 1 routing steps with a secondary ending code of 0.  The job

   ending codes and their meanings are as follows:

      0 - The job completed normally.

     10 - The job completed normally during controlled ending or controlled
   subsystem ending.

     20 - The job exceeded end severity (ENDSEV job attribute).
     30 - The job ended abnormally.
     40 - The job ended before becoming active.
     50 - The job ended while the job was active.
     60 - The subsystem ended abnormally while the job was active.
     70 - The system ended abnormally while the job was active.
     80 - The job ended (ENDJOBABN command).
     90 - The job was forced to end after the time limit ended (ENDJOBABN
   command).
 Recovery  . . . :   For more information, see the Work management topic
   collection in the Systems management category in the IBM i Information
   Center, http://www.ibm.com/systems/i/infocenter/.


Note that was back on 1/22.  We have IPL'ed that machine at least twice since then.  It appears there was no attempt to start that job on our system either.



On Tue, Feb 20, 2018 at 9:35 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

> I opened a ticket, copying and pasting this email.
> Apparently IBM failed to read it because they requested that I send in 
> the joblog from the QS9SFWMON job.  I told them it doesn't even try to 
> start it.  Why not?
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
> To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Date:   02/20/2018 09:29 AM
> Subject:        RE: QS9SFWMON job missing.
> Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
>
>
>
> I'm not familiar with it, but it appears to be part of ESA.  I'm 
> guessing you already found this doc:
> http://www-01.ibm.com/support/docview.wss?uid=nas8N1010756
>
> I found this unofficial source for v5r4:
> QS9SFWMON - This job analyzes software problems sent from QS9PRBMON 
> and determines if they should be reported to the service provider. If 
> they should be reported, it sends them to data queue QS9SND.
> http://systemicommunity.blogspot.com/2010/03/electronic-service-agent-
> v5r4m0-jobs.html
>
>
>
>
> -----Original Message-----
> From: Rob Berendt [mailto:rob@xxxxxxxxx]
> Sent: Tuesday, February 20, 2018 6:20 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: QS9SFWMON job missing.
>
> QS9SFWMON
> What exactly is this job and how do you control it's running?
>
> When I do the following:
> GO SERVICE
>  8. End jobs
>  9. Start jobs
> 10. Work with jobs
> I only see:
> Job
> QS9HDWMON
> QS9PALMON
> QS9PRBMON
> QS9PRBSND
> And I am missing the usual
> QS9SFWMON
> Near as I can tell it didn't even try to start it.
> Job 478076/QSRVAGT/QS9PALMON submitted Job 478077/QSRVAGT/QS9PRBMON 
> submitted Job 478078/QSRVAGT/QS9HDWMON submitted Job 
> 478079/QSRVAGT/QS9PRBSND submitted DSPLOG PERIOD((*AVAIL *BEGIN)) 
> JOB(QS9SFWMON) shows nothing Google search for QS9SFWMON shows nothing 
> as to why this may not have started.
> It's only missing on 2 of our 15 lpars.  Matching release (7.3) and 
> PTF levels.
> I'm guessing it's some configuration issue but I can't figure it out.
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 
> Mail
> to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
> --
> 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: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take 
> a moment to review the archives at 
> https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related 
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
>
>
> --
> 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: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take 
> a moment to review the archives at 
> https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related 
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD