RE: [SYSTEM21] GL Subsystem stops without indication

["Ellsworth, Bob" <Bob.Ellsworth@xxxxxxxxxx>]

This sparked a thought with our administrator - the message queue angle
wasn't explored.  
Doug/Rose have us optimistically going down this new path.

We also stop/start the subsystems via Robot job scheduler nightly.
But the problem is strange in that it doesn't complain - it sits actively on
the system doing, well, apparently nothing.

Besides looking at the queue (and Robot/Console's effect on it, which was a
recent addition to our system and as such is automatically a suspect in
management's eyes), we also started running an FLP008-vs-FLP007 query every
few minutes to capture exactly when it stops updating.  This will help
identify the cause and subsequent cure.

Thanks all for the quick responses!  Significant findings will be posted.
-BobE
  bob.ellsworth@xxxxxxxxxx



-----Original Message-----
From: Rose Clarke [mailto:rclarke@xxxxxxxxx <mailto:rclarke@xxxxxxxxx> ] 
Sent: Monday, April 11, 2005 11:22 AM
To: System 21 Users
Subject: RE: [SYSTEM21] GL Subsystem stops without indication

We routinely stop and start these type of background jobs every night, this
prevents the message queues from 'filling up' and also means that if the job
has already stopped for an 'unknown' reason then it will be restarted
without too much bother. Since doing this we very rarely encounter any
problems.

________________________________

From: system21-bounces@xxxxxxxxxxxx on behalf of Doug Griffin
Sent: Mon 11/04/2005 16:16
To: 'System 21 Users'
Subject: RE: [SYSTEM21] GL Subsystem stops without indication



Bob,
I have had the GL update job stop, and complain something about message
queue full, no authority to increase, etc.  I just restarted without
investigation.
Doug

-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx
[mailto:system21-bounces@xxxxxxxxxxxx]On
<mailto:system21-bounces@xxxxxxxxxxxx]On>  Behalf Of Ellsworth, Bob
Sent: Friday, April 08, 2005 1:27 PM
To: 'System 21 Users'
Subject: [SYSTEM21] GL Subsystem stops without indication


Hi folks,

We've got the GLUPDATE subsystem running in Sys21 v352b/SP3, and every so
often the updating of the GL will cease on its own.  The job will still be
running, and there will be no indication that it's stopped posting except
for the UPDNOG in FLP007/FLP008 which remains at zero until the 32/GLU
(Start/end balances Utility) is run to bring it down and back up.  Upon
resetting it, the unprocessed transactions are picked up OK.

Has anyone else ever encountered this?  It's been a minor annoyance until it
just happened at month end without being detected before the finance reports
all ran, so now it's in the spotlight.

We run consolidated AFI, but the root cause, frequency and pattern of
failure has thus far eluded us.
I checked through the archives and finding nothing, it was worth a try to
see if anyone here's experienced it.

Any input is appreciated,
-Bob Ellsworth
 bob.ellsworth@xxxxxxxxxx




_________________________________________________________________ 
This electronic mail transmission contains confidential information intended
only for the person(s) and/or organization named. Any use, distribution,
copying or disclosure by or to any other person outside your organization is
strictly prohibited. If you received this transmission in error, please send
an electronic mail message to postmaster@xxxxxxxxxx so we may instruct you
regarding its disposition.