Conference humane::scheduler

    
    We'll look into the specific problem I think there is 
    a sintax problem in the address specifier which should
    have been caught prior to making it to the TXM server
    component. Is there anymore information you can send 
    our way to re-create this error message (maybe a copy
    of the actual script being run would help allot).
    
    Sorry I can't break the problem down further but was
    hoping some more information could help such as the
    shell this is being run from, etc.
     

    Hi.  Thanks for the reply.
    
    I'll request to customer the shell script.  Meanwhile, here's the
    log, if it would help little...
    
    sxkac@glacier> cat glacier_engine.log
    SchedTrace::OpenSchedulerLog: Opened log file
    /var/sched/glacier_engine.log
    SchedTrace::OpenSchedulerLog: Start of Trace Information
    /var/sched/glacier_engine.log
    ...Number of arguments specified: 1
    Command line arguments (Default = -1):
            1: process code. Default to 2.
            2: use simulated agents. Default to FALSE(0).
            3: use realtime clock. Default to TRUE(1).
            4: debug level (-1/all to 3). Default to 2.
            5: start without waiting for TXM/verification.  Default to
    FALSE.
            6: process code for V3 agents. Default to 3.
            7: port number for V21 agents. Default to 5482.
            8: activate interface to V21 agents. Default to FALSE.
            9: alternative log file name.
    
    -->Engine status initialized to: SchedArglist {
            Build Date = "Oct 16 1995"
            Component Type = "Engine"
            Database is attached = 0
            OS Type = "OSF/1"
            Scheduler Version = "V3.0-02"
            Sender Process Id = SchedProcessAddress SchedArglist {
            SCHEDULER PROCESS CODE = 2
            Server = "glacier.alaska.edu"
            }
    
            Server = "glacier.alaska.edu"
            Startup Time = May 5, 1996 9:03:32 am
            }
    !!! Unsupported SCHED_IP message: 28
    !!! Unsupported SCHED_IP message: 28
    !!! Unsupported SCHED_IP message: 28
    
    Thanks.
    
    Jay So CSC/DECsched & UCX Support
    
    P.S. Please excuse me if I sound ignorant, I'm very new to this
    product...

    I got the script from the customer:
    
    Attached is the script which generated this error.
    Please note the script was  generated from an application which has
    generated
    comparable scripts successfully hundreds of times.
    Kurt Carlson, U of Alaska
    
    create  job     ANKLW12152      acl ASAP        -
    mainstep        /users/sx/sxprod/log/banner/ANKLW12152.shl      -
    output          /users/sx/sxprod/log/banner/ANKLW12152.log      -
    partition       dbanner_glacier -
    poststep "schedule delete job ANKLW12152 server glacier.alaska.edu" -
    schedule start_time "+0 00:01:00"       -
    notification (by broadcast when none)   -
    notification (by mail when (stall,timeout)       -
    address "[email protected], [email protected]"  )
    exit

    I've got more info from customer:
    
    From:   (85299) [email protected]
    
    ========
    
    Looks like I didn't fully answer the previous question...
    the job create would have been via a 'schedule -f filename'
    command from a korn shell script:
            schedule -f ${BANSCH_LOG}.sch >${BANSCH_LOG}.out
    I found today the job was partially created, show job follows.
    Note it doesn't resemble the command very closely other.  Kurt
    
    SCHEDULE>  show job anklw12152 sel own anklw display full
    
    Job Name      Job Number    Owner         Job State     Next Sched Time
    --------      ----------    -----         ---------     ---------------
    ANKLW12152    1736          anklw         SCHEDULED     NEVER
    There are no steps on this job
    Success Count    : 1                  Failure Count    : 0
    Output File      : /users/sx/sxprod/log/banner/ANKLW12152.log
    Job Status       : SUCCESS
    Account          : anklw
    Partition        : DBANNER_GLACIER
    Agent List       :
    Run Priority     :
    Stall Job        :                   Stall Time       :
    Stall action     : IGNORE
    Timeout Job      :                   Timeout Interval :
    Timeout action   : IGNORE
    Fail Job         :
    Retry Interval   : +0 00:15:00       Job Retry Attempts : 100
    Job Retry Count  : 0
    On failure RESCHEDULE
    On crash RESTART
    Last Start Time  : 12-May-96 0:48:50
    Last Finish Time : 12-May-96 0:48:50
    Last Sched Time  : 8-May-96 18:26:21
    Next Sched Time  : NEVER
    Sched Interval   :
    Sched Priority   : 100
    Days             : ( MON, TUE, WED, THU, FRI, SAT, SUN )
    Special Day Class List :
    Special Day restrict from action skip
    Reschedule from ACTUAL
    There are no notification records on this job
    ACL Name         : ASAP
    There are no attributes on this job
    Jobset Name List :
    There are No Predecessors on this job
    There are No Successors on this job
    Dependency Timeout :
    Job Description  :