[SYS21] Re: [SYS21] SP4 System Manager uplift issues.

Kevin,

One more thing that just occurred to me when my calendar reminder popped up just
now...

The JOBSCH job that runs in QCTL subsystem used to get deleted and a fresh copy
of that job would be executed whenever the RUNADSJOB command was issued...  That
is no longer the case, at least for us...  The day start and day end routines do
get executed in their normal cycle but the JOBSCH job in QCTL will be the same
one that was launched when you last performed an IPL...

That is until it exceeds the nesting level for the operating system and it
suddenly and rather ungracefully fails and produces several thousand pages of
job log...  I think I logged this as a problem on Answerlink but do not know if
they ever accepted it as a problem...  Or if they are ever going to fix it...

So I have a calendar reminder to manually delete and restart the JOBSCH job in
QCTL every Friday...  Once I delete the current iteration of the JOBSCH job in
QCTL I have to go into the Auto Day Start list of jobs and override on and off
the jobs I want to run/not run and then issue the RUNADSJOB command again...

I don't know if something in the OS/400 (we're are V4R5) changed or if someone
"fixed" the RUNADSJOB command but it used to delete the current iteration of
JOBSCH and launch a new job called JOBSCH in QCTL...  It doesn't do that for us
any more...

I don't know if anyone else is having this problem or not, I vaguely recall
posting this on the list a couple of years ago but my mind is going, I can feel
it...

Regards...







"Brunk, Kevin" <Kevin.Brunk@wabutler.com> on 10/09/2002 04:16:22 PM

Please respond to jbausers-l@midrange.com



  To:          jbausers-l@midrange.com

  cc:          (bcc: Jeff Klipa/Harvard)



  Subject      [SYS21]   SP4 System Manager uplift issues.
  :







This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
We recently uplifted our System Manager to SP4 (leaving our apps at 3.5.0b) on
our test machine.  We have encountered some problems that I'm wondering if
anyone else has experienced and can shed light on remedies.

1.     Coincident with the uplift, we noticed that WRKSBMJOB now responds more
slowly (a lot slower) than it used to.  I've used DSPOBJD *ALL/WRKSBMJOB *CMD to
see if the uplift somehow created it's own copy of WRKSBMJOB (I realize what a
ridiculous idea that is...but I leave no stone unturned!) I further looked to
see if the command processing program QWCCDSUC was duplicated by the uplift.  In
both instances, as I expected, no such duplications were created by the uplift.
We have found no other explanation of the slowdown of this command.  This leaves
me with the question...is it really coincidental that the slowdown of WRKSBMJOB
occurred alongside the uplift or is there something I'm not considering.

2.  A few days after the install, the job scheduler began looping and ended up
submitting 40,000 repetitions of the same job by the time we caught it.  To
correct this, we ended the job scheduler, cleared the job queue, spent hours
getting rid of the resulting job logs, and restarted the job scheduler.  Since
then it has worked fine.  Our GEAC consultant thought this was related to our
using 99:99:99 as the submit time in some entries.  However, this is the
documented way to run jobs at day start.

3.  We discovered that Verify Allocations can no longer be run through the job
scheduler - it must be manually submitted.

[4.] In addition to the above, we use Explorer at our remote telecenters and
have continual problems on individual PCs of Explorer suddenly ending all
sessions.  We are wondering if simply by upgrading System Manager on our
production system to SP4 these problems will be solved.  Again, does anyone have
any experience with this Explorer problem and how it was solved?

==Kevin Brunk
The Butler Company
Dublin, Ohio
_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.