[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

1166.0. "Problem with cluster alias" by BIGCHZ::EZZELL (Mike Ezzell) Thu Oct 10 1996 15:28

I have a custome with multiple clusters with one full scheduler license per
cluster and agent licenses for the remaining systems in each cluster.  These
clusters utilize cluster alias for remote file accesses.  They run jobs under
scheduler with dependencies between clusters.  Apparently the cluster alias
is passed by scheduler between clusters and when the dependency is done,
scheduler attempts to notify the other cluster via the cluster alias.  The
problem with this is that more times than not, the node that is selected by
the alias only has an agent license and is unable to process the request.

Any ideas?
T.RTitleUserPersonal
Name		DateLines
1166.1RUMOR::FALEKex-TU58 KingTue Oct 15 1996 15:582
    can you use specific node names for the remote dependencies rather than
    the cluster alias ?
1166.2Elevated issue - no fix yetCSC32::WATERSThe Agony of DeleteMon Nov 04 1996 17:2611
    
     This issue has also been elevated to engineering. Scheduler fills in
    the "nodes depending on this job" with the alias name, you can't specify
    a specific node name.  The author of node 1170 wanted to code example
    to see if it is possible to modify the entry in DEPENDENCY.DAT to
    specify a specific node name. Don't know the results.
    
    Mark Waters
    CSC Colorado
    
    ps. Falek we sure miss not having you guys for support !