[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference humane::scheduler

Title:	SCHEDULER
Notice:	Welcome to the Scheduler Conference on node HUMANEril
Moderator:	RUMOR::FALEK

Created:	Sat Mar 20 1993
Last Modified:	Tue Jun 03 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1240
Total number of notes:	5017

1235.0. "VSS_REPORT loops" by ATZIS1::50008::BACHNER (Mouse not found. Click OK to continue) Fri Apr 04 1997 06:02

OpenVMS V6.1, Scheduler V2.1b-7

A customer tries to run reports, but VSS_REPORTS keeps looping. For the reports,
they only specify a Begin date and a Job Name mask of %%_%%_*; they also request
accounting information.

They have seen the problem as well with version V2.1b-2.

In the past (with V2.1b) they were able to workaround the problem by compressing
the database with DB_UTILITY. They also tried to rebuild VSS.DAT (converted it
into a sequential file, converted it back to indexed with a suitable FDL file).

Is this a known problem, or even more important, is there a known workaround ?

Thanks for your help,
Hans.

T.R	Title	User	Personal Name	Date	Lines
1235.1	corruption in the job history data ?	RUMOR::FALEK	ex-TU58 King	`Fri Apr 04 1997 17:22`	8
	I suspect there may be something may be wrong with the job history data. It could be that a bug in VSS_REPORTS that is being triggered by bad history data (although I haven't heard of such a bug) You can check if the problem is corruption in the job history records by doing $ sched sho history/records/comp=all for that job specification.
1235.2		ATZIS3::50008::BACHNER	Mouse not found. Click OK to continue	`Mon Apr 07 1997 10:15`	7
	Thanks for the hint, I'll ask the customer to check for history corruption. If he finds some corruption, is there a way to fix it, maybe remove the corrupt records ? Thanks, Hans.
1235.3		RUMOR::FALEK	ex-TU58 King	`Mon Apr 07 1997 21:56`	2
	You might be able to get rid of the problem with $ sched close log /summarize (I think that's the DCL command) or maybe not.
1235.4	show history worked fine	ATZIS1::50008::BACHNER	Mouse not found. Click OK to continue	`Thu Apr 10 1997 13:12`	13
	The customer reported that $ sched show history /record /comp=all completed without an error. What would $ sched close log /summ actually do ? Would the summary information copied to the new log file be sufficient to create reports from the jobs in the old log file ? Or does this command modify the old log as well, implicitely fixing the apparent problem ? Thanks for your help, Hans. PS: if I need to IPMT this case, which file(s) do you need to track the problem down (in addition to the log file, of course) ?
1235.5	what it does	RUMOR::FALEK	ex-TU58 King	`Thu Apr 10 1997 17:57`	13
	We're only guessing that there might be a problem with the history records, we don't know for sure... But I think that VSS_REPORTS uses the same API routine to get job history information as the DCL command does. If the DCL command completed, the call to vss$get_hist_rec() is probably not the problem - It could still be a bug in VSS_REPORTS itself... $ sched close log/summarize reads all the history records. For each job that has history, it generates a summary record (so as to preserve the min/max/average resource counts for things like $ sched show schedule). It writes a new, blank history file and puts the summary records at the beginning - so the detail of the individual job runs is lost.