[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 |
1215.0. "I need help with a anormal funcionality of DecScheduler over Motif" by LATINA::GREGORIO (MCS Madrid) Thu Feb 13 1997 10:29
Hello,
I need help with a anormal funcionality of DecScheduler over Motif
interface.
When the customer runs several jobs and he use scheduler/inter=decw,
the interface inform me of state of completion of jobs bad, but this
event does not happen always.
One case:
A job finish a it end well and it must wait for dependencies,
but it waits for schedule (in X windows interface). If you
push refresh key the state of job does not change.
And if I go out to decwindows interface and I execute
schedule /inter=decw this job is waitting for dependencies
The job is:
Job Name Entry User_name State Next Run Time
-------- ----- --------- ----- -------------
SCLI046X 108 EXPLOTA DEP Wait 13-FEB-1997 12:41
VMS_Command : @ISIS_COM:SCLI046X.COM
Group : ISIS_D_MA�ANA Type : MA�ANA
Last Start Time : 13-FEB-1997 12:41
Last Finish Time : 13-FEB-1997 12:45 Last Exit Status : SUCCESS
Schedule Interval : 0 Mode : Batch
Mail to : EXPLOTA (No Mail)
Days : ALL
Output File : ISIS_LOG:SCLI046X.LOG
Cluster_CPU : <Ignored> Notify user upon completion
Submit Queue : EXPLOTA_BATCH
CPULimit (x100ms) : 0 QPriority : 100
Max_Time Warning : None Job Always retained
Stall Notify : None No Retry on Error
Success Count : 614 Failure Count : 5
Owner UIC : [1,5] Restart on Crash
Send Opcom Completion Message
No Pre or Post Function for this job
No local jobs depend upon this job.
All dependencies must successfully complete after: 13-FEB-1997 12:45:18.46
Job Dependencies: (SC_LD_APDIA_RO070)
In other case, the job finish bad, but the display is waitting for scheduling.
I don't know by this it occurs.
The system is a 8200 with OpenVMS V6.2-1H3 on node ABEL
The version of decscheduler is 2.1B eco 9 04
Image Identification Information
image name: "SCHEDULER"
image file identification: "V2.1B-904"
image file build identification: ""
link date/time: 5-FEB-1997 18:57:06.11
linker identification: "A11-20"
Motif version is 1.2-4
Image Identification Information
image name: "DECW$TERMINAL_CREATE"
image file identification: "DW V1.2-4960312"
image file build identification: ""
link date/time: 19-MAR-1996 14:10:09.33
linker identification: "T11-11"
If you need more information, please tell me.
Thanks
Goyo Fdez.
T.R | Title | User | Personal Name | Date | Lines
|
---|