[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

1233.0. "VSS$MODIFY_ITEM PROBLEM!" by MDR01::NIEVES (MCS Madrid) Wed Apr 02 1997 06:14

    Hi,
    
    this customer thinks there is a problem with the VSS$MODIFY_ITEM
    rutine.
    
    He has an Alpha with VMS 6.2, DECScheduler V2.1-B9
    
    He created 3 jobs (.com), first one, second one and third one (they go
    one after the other).
    
    They use the VSS$MODIFY_ITEM so that it changes the ending state of the
    first job, implementing that if the first procedure ends incorrectly, it
    marks it as ending correctly, so that the two next procedures execute.
    
    They start executing job one, and from the scheduler they abort
    it, and if VSS$MODIFY_ITEM would be working correctly, the two
    following jobs will have to execute, but this doesn't occur. 
    The second job has "next run time": 1-APR-1997 16:00 (this is a past
    hour). In state it has :depwait (as it depends of the first one and
    this first one hasn't finished correctly).
    
    This is an SOS to find someone that could help me,
    
    regards,
    
    Nieves
T.RTitleUserPersonal
Name		DateLines
1233.1I don't think it is supposed to be able to do thatRUMOR::FALEKex-TU58 KingWed Apr 02 1997 19:405
    I doubt that the last completion status of a job is writable
    via VSS$MODIFY_ITEM,  please check the documentation...
    Also, is the customer's code correctly checking the return status from the
    call to VSS$MODIFY_ITEM?  It may be returning a code indicating that
    not all items were modified.