× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Glenn
It WAS started at 12:01
It did NOT sit in the jobq
There were MANY other jobs running ath the same time since this morning

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Glenn Gundermann
Sent: Thursday, May 25, 2017 3:01 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Running a program interactively or in batch

Hi Alan,

That's a high CPU number.
Did it actually start at 12:01 or did it get submitted to the job queue at
12:01 and it sat in the job queue for a while?
Were there other jobs running at the same time?


Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (905) 486-1162 x 239
Cell: (416) 317-3144


On 25 May 2017 at 14:56, Alan Shore <ashore@xxxxxxxx> wrote:

Thanks for the reply Glenn
I used your idea of looking at the CPU time used and it is gradually
increasing 631928 to 632119 As far as checking the QHST log - and
seeing if anything was locked - the job is STILL running Using WRKJOB
option 12 - there are NO locks being waited on

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Glenn Gundermann
Sent: Thursday, May 25, 2017 2:44 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Running a program interactively or in batch

Hi Alan,

Did it actually start at 00:01? Check using WRKJOB option 1, Started
Date and Time.

Using WRKJOB option 3, press F5=Refresh and see if the "CPU time used"
is increasing. What is the current amount right now?

Check the QHST history log and see what other jobs were running at the
same time. Perhaps the job was locked due to a backup that runs until
the morning. Perhaps the job was running but didn't get enough of the CPU.

Using WRKJOB option 12, are there any locks it is currently waiting on?


Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (905) 486-1162 x 239
Cell: (416) 317-3144


On 25 May 2017 at 14:35, Alan Shore <ashore@xxxxxxxx> wrote:

Hi everyone
Before I forget - we are on v7r1
I have a program that I have been running interactively now for a
couple of weeks with no problems Takes approximately 90 to 120
minutes This CLLE program copies files, clears some other files then
uses the command RUNSQLSTM using a text file containing a number of
SQL scripts with
COMMIT(*NONE) and creates files in QTEMP

I have now created a WRKJOBSCDE to run the same program at one
minute past midnight I came in this morning to see that the job was
still running No locks No msgw I looked at the job log - nothing out
of the ordinary But I am unable to determine where the program is in
the SQL run

I looked at option 14. Display open files, if active, then pressed
F11 to see the relative record number of files I have now been doing
this for a few hours and nothing seems to be moving The call stack
doesn't change either

Does anyone know what I can look at to determine whats happening?



Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill

--
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.

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: 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.

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: 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.

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: 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.

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.