[SYS21] Re: GLUPDATE running with DLYW status -- SYSTEM21

If you do the WRKACTJOB you will see the following...
Subsystem/Job  User        Type  CPU %  Function        Status
GLUPDATE     QPGMR       ASJ      .0  DLY-10           DLYW

Under function it says how many seconds (DLY-10 in this case)the job is delayed before it "wakes up" and reads the Q again for transactions...

I usually use the WRKSBSJOB GLBACK3 command to see the status of the GLUPDATE job, since WRKACTJOB is such a resource hog I've trained myself to not use that command at all... I do WRKSBS, Enter, F11 to see how many active jobs there are then put an 8 next to the subsystem I'm interested in and press enter... Going in this way you wouldn't see the DLYW status column... Which in this case might not be a bad thing...

I would suggest that 99.9999 % of the time this job runs it is in status DLYW... This is it's normal condition by definition as a background job... So unless you see something under function other than DLY-10 and there are not any MSGW in QSYSOPR or elsewhere I would not immediately suspect that something was wrong with the job...

Independent of the jobs status is the fact that you said, "...while the number of highlighted (unprocessed) GL account postings grows."... This is the bit that would cause me to suspect that there was indeed some cause for concern... Again the DLY-(duration) value would have to be something significantly larger than 10 to allow for these GL transactions to grow as you have reported...

I would be on the lookout for any job logs associated with the GLUPDATE job... But that means you would have to change the job's message logging level from the default of: Message logging: Level . . . . . . . . . . . . 2 Severity . . . . . . . . . . . 20 Text . . . . . . . . . . . . . *NOLIST Log CL program commands . . . . *NO

to something a bit more useful, for example...:

Message logging:
 Level  . . . . . . . . . . . .   4
 Severity . . . . . . . . . . .   00
 Text . . . . . . . . . . . . .   *seclvl
Log CL program commands  . . . .   *YES

I would also check the QSYSOPR message Q and look for any reports under the users name the GLUPDATE job runs under...

We're running V3.5.1 and GLUPDATE is quite stable and doesn't just 'HANG' for no reason... I've never seen it do that in the 9 years I've been working with the JBA package...

It must be something unique to your environment... An authority problem, an object locking problem, corrupt data or invalid AFI rules or something strange like that... GL Update is quite robust and I am not aware of any time I've ever lost a GL posting due to a failure in GLUPDATE.

Try changing the logging level on that job and be sure to change the: Job message queue full action... to *PRTWRAP if it's not already... That might give you a trail of bread crumbs to follow if indeed the cause of the problem is in GLUPDATE...

Good luck with that, and be sure to let us know if/when you solve the mystery...

----Original Message Follows----
From: "Ellsworth, Bob" <Bob.Ellsworth@xxxxxxxxxx>
Reply-To: GEAC/JBA System 21 Users <jbausers-l@xxxxxxxxxxxx>
To: GEAC/JBA System 21 Users <jbausers-l@xxxxxxxxxxxx>
Subject: [SYS21] Re: GLUPDATE running with DLYW status
Date: Wed, 26 Mar 2003 10:04:01 -0500

Just for clarification -
We take the GL subsystem down before the backups.
We also have separate procedures for recovering incomplete sessions
(recycling the subsystem alone won't help this situation)

Still, once every couple of months it will appear to the WRKACTJOB that
GLUPDATE is happily running in DLYW state, while the number of highlighted
(unprocessed) GL account postings grows.  Bringing the subsystem down and
back up via the standard System21 menu option will always 'kickstart' the
GLUPDATE, and it runs at full throttle (taking a majority of CPU to process
all the transactions in queue) for about a minute.  Then it goes back to its
DLYW state and processes perfectly for another couple of months.

It's more of a curiosity than a critical failure.
-BobE

> -----Original Message-----
> From:      Jeff Klipa [SMTP:jklipa@xxxxxxxxxxx]
> Sent:      Wednesday, March 26, 2003 9:38 AM
> To:        jbausers-l@xxxxxxxxxxxx
> Subject:   [SYS21] Re: GLUPDATE running with DLYW status
>
> I echo Margaret's comment about taking it down every night for backup...
> I would strongly suggest that this is the prescription to follow for all
> background processing jobs...  Otherwise your AMDAYEND job will not run
> due
> to a lock on APG25PHY...  And you really should be running the AMDAYEND
> job...  Every night...
>
>
> ----Original Message Follows----
> From: mslayton@xxxxxxxxxxx
> Reply-To: GEAC/JBA System 21 Users <jbausers-l@xxxxxxxxxxxx>
> To: GEAC/JBA System 21 Users <jbausers-l@xxxxxxxxxxxx>
> Subject: [SYS21] Re: GLUPDATE running with DLYW status
> Date: Tue, 25 Mar 2003 16:45:49 -0500
>
> We don't have this problem.  We take our subsystem down every night when
> we do the backup and then bring it back up.
>
>
>
>
>
>
> _________________________________________________________________
> Add photos to your e-mail with MSN 8. Get 2 months FREE*.
> http://join.msn.com/?page=features/featuredemail
>
> _______________________________________________
> This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
> To post a message email: JBAUSERS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/jbausers-l
> or email: JBAUSERS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/jbausers-l.
>
>
_________________________________________________________________
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.
_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/jbausers-l
or email: JBAUSERS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.

_________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail