[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | SCHEDULER |
Notice: | Welcome to the Scheduler Conference on node HUMANE ril |
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 |
1154.0. "Job stays in "queued" state after db_utility" by BACHUS::WILLEMS (Johan Willems @BRO DTN 856-8739) Mon Sep 09 1996 12:05
Job stays queued after stopping and restarting scheduler.
A customer asked me the correct way to compact the scheduler database
VSS.DAT. The way he did it left a job in "queued" state.
He did:
1 - stop all schedulers ($ SCHED STOP/ALL)
2 - run db_utility
3 - restart all schedulers.
This customer is running V2.1B-9
$ sched sh stat
Node Version Started Jobs Jmax Log Pri Rating
BKS004 V2.1B-9 6-SEP-1996 10:43:35 0 6 5 4 2057 <-- Default
BIGSYS V2.1B-9 6-SEP-1996 10:43:36 0 6 5 4
Job info
6-SEP-1996 09:50:46 138 JOB QUEUED BKS004
entry=
93 queue=SYS$BATCH
6-SEP-1996 09:51:44 138 JOB START BKS004 2097F8FB
6-SEP-1996 09:51:46 138 JOB FINISH BKS004 2097F8FB Success
6-SEP-1996 10:06:04 138 JOB QUEUED BKS004 entry = 229
queue=SYS$BATCH
no more info in the previous vermont_creamery.log
Customer found job today still "queued".
Any info is welcome
Johan
T.R | Title | User | Personal Name | Date | Lines
|
---|