Abnormal Termination of a Quick Screen in Batch
Boyle, Joe
Joe.Boyle@cognos.com
Mon, 14 May 2001 05:25:23 -0400
Hi Roger,
you could try debugging the cause of the problem by adding records to a
sequential log file at key stages within the screen processing ( or at every
stage ) in order to identify the point at which the failure occurs.
You will get an idea of why the process stopped, hopefully, by observing the
last 'run command' or procedure processed in conjunction with the data
values in use at the point of failure.
see very crude example below, includes quick source code and log file output
as viewed from Quiz.
*____________________________________________________________________*
can cle
set dict sys$scratch:bulllock
set defa
screen sys$scratch:LOCKTEST.QKc
temp t-key char size 5 reset at startup
define d'getsystemval char * 2 = &
getsystemval ( "batch-flag", logical ,"lnm$job")
file bullp designer
file bulls designer
file rep-stats designer
temp t-p integer *10 reset at startup initial 0
temp t-s integer *10 reset at startup initial 0
PROCEDURE internal getdets
begin
let rep-stats-det of rep-stats &
= "starting loop in getdets proc " + " > " + ascii (systime )
put rep-stats reset
while ret bulls VIA SCHED-COMMENT-CD using SCHED-COMMENT-CD of bullp
begin
let t-s = t-s + 1
end
end
PROCEDURE initial
BEGIN
let rep-stats-det of rep-stats &
= "@ing dev$coms:setup com file in initial proc " + " > " + ascii (systime
)
put rep-stats reset
run command "@dev$coms:setup.com" on error terminate
let rep-stats-det of rep-stats &
= "starting loop in initial proc " + " > " + ascii (systime )
put rep-stats reset
while ret bullp sequential
begin
let rep-stats-det of rep-stats &
= "rec " + SCHED-COMMENT-CD of bullp + &
" in loop in initial proc " + " > " + ascii
(systime )
put rep-stats reset
do internal getdets
let t-p = t-p + 1
end
let rep-stats-det of rep-stats &
= ascii ( t-p ) + " > " + ascii ( t-s ) &
+ " > " + ascii (systime ) + d'getsystemval
put rep-stats reset
let rep-stats-det of rep-stats &
= "closing files " + " > " + ascii (systime )
put rep-stats reset
close bulls
close bullp
close rep-stats
RETURN
end
build list detail
*____________________________________________________________________*
Viewed from a Quiz such as,
can cle
set default
set pag len 0
set rep nolim
acc rep-stats
rep all
set pag wid 132
go
you would see log detail like that below,
@ing dev$coms:setup com file in initial proc > 5134007
starting loop in initial proc > 5134150
rec A in loop in initial proc > 5134222
starting loop in getdets proc > 5134225
rec AA in loop in initial proc > 5134227
starting loop in getdets proc > 5134230
rec B in loop in initial proc > 5134235
starting loop in getdets proc > 5134237
... more details ...
rec C in loop in initial proc > 5134249
starting loop in getdets proc > 5134251
rec D in loop in initial proc > 5134263
starting loop in getdets proc > 5134266
26 > 21538 > 5134551
closing files > 5134561
regards,
Joe Boyle.
-----Original Message-----
From: Kesterson, Roger [mailto:Roger.Kesterson@mtdsw.com]
Sent: 30 April 2001 21:50
To: PowerHouse List Server (E-mail)
Subject: Abnormal Termination of a Quick Screen in Batch
PH7.10.G2
Alpha OpenVMS 7.1
-----------------
Fellow PH Listers (no reference to Red Dwarf intended):
We have some Quick programs that execute in batch, using a WHILE loop in the
INITIALIZE procedure. QKOUT is sent to a file, but QKIN is not redefined in
any way. One of these programs just terminated, and the only message in the
QKOUT file is:
"The limit for backup movements (\\) has been reached."
Does any of you have any idea what might cause this?
Thanks,
Roger Kesterson
Senior Programming Analyst
MTD Southwest, Inc.
550 N. 54th Street
Chandler, AZ 85226
Phone: 480-961-1002 x4357
Fax: 480-940-5035
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.