|
On May 25, 2017, at 3:29 PM, Alan Shore <ashore@xxxxxxxx> wrote:--
The call stack just showed that it was on the RUNSQLSTM call
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
Justin Taylor
Sent: Thursday, May 25, 2017 4:27 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Running a program interactively or in batch
Have you checked the call stack? That should give you some idea where it's currently at in your code.
-----Original Message-----
From: Alan Shore [mailto:ashore@xxxxxxxx]
Sent: Thursday, May 25, 2017 1:36 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Running a program interactively or in batch
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.