[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 |
1236.0. "SCHED_DECNET and OSI - revisited." by ATZIS1::PIEBER (chaos has many faces) Tue Apr 08 1997 11:24
Hi folks,
I peeked around in this conference, but the following does not seem to
be covered up to a solution yet.
If installing the scheduler on an OSI system it will fail with a contraint
violation, which stems from number=0 for the ADRESSES field of the session
control application. This is already in this conference.
I now checked 2.1B VAX and ALPHA as well as ECO9 for VAX and ALPHA kits
for the startup procedure. 2.1B did not check for the VMS version, ECO9
does. However, this has nothing got to do with the VMS version, as far
as I could track this down, but simply fails, when a session control
application with number=0 exists.
I all instances I had, removing 'number=0' from the SCHEDULER startup,
removing the incomplete session control application SCHED_DECNET from
NCL (no image and user name present) and restarting SCHEDULER succeeded.
As far as I can tell checking for Phase 5 - as does base 2.1B - and
removing 'number=0' from the NCL command will do the trick for all VMS
versions.
rgds,
Ewald.
T.R | Title | User | Personal Name | Date | Lines
|
---|