Conference humane::scheduler

1105.0. "Unix account set up for running Scheduler" by WOTVAX::DAVIESG (Guy Davies) Tue May 21 1996 13:54

    I am running POLYCENTER Scheduler on an Alpha 1000 4/233 with Digital
    Unix v3.2d as the operating system.
    
    The Unix platform has client/server/agent software and license
    installed on it. However, when I try and run a job through the GUI I
    always encounter the same failure.
    
    For example, 
    
    # xschedule
    
    select new button at the bottom left of screen
    enter through GUI Job Name : test1
    		      Main Step: date > test1-runtimes
    		      Output File: test1.log
    		      Job interval: H 1:00
    Select Job menu and save
    Select the DEFAULT jobset
    open jobset button
    select test1 icon
    select single job menu
    select realtime ON button
    select run option
    
    (as you can see this is merely a test to make sure I can run something
    through the installed software)
    
    the realtime window shows the job start and then fail, when I look at
    the test1.log.err I get the following output...
    
    stty:tcgetattr: Not a typewriter
    Not a terminal
    date: bad conversion
    Usage: date [-u] [+field descriptors]
    
    ...presumably this is something to do with my account setup, but what?
    I was not aware of having to do anything to my account to accommodate
    scheduler.
    
    I log in using ksh, my .profile looks like this
    
    PATH=$HOME/bin:${PATH:-/usr/bin:.}
    export PATH
    stty dec
    tset -I -Q
    PS1="`hostname`> "
    MAIL=/usr/spool/mail/$USER
    
    What have I failed to do?
    
    Appologies if this should have gone in the OSF conference, if it should
    have, let me know and I will repost this.
    
    Thanks
    
    Guy
       

    
    When using the ksh or sh shell there are some restrictions
    on the types of commands which can be used or better stated 
    how they should be used. This is actually in the README (UNIX 
    equivalent of release notes). I suggest you review the specifics
    about the shell of your choice, it may require a minor workaround, 
    as an example:
    
     o  In Chapter 1 of the POLYCENTER Scheduler Guide for
        System Managers and Operators, in both Scenario
        sections (graphical interface and command line interface), 
    	the main step "date >> test1-runtimes" will produce the
        following error when using the Bourne or Korn shell:
    
           date: bad conversion
           Usage:  date [-u] [+field descriptors]
                   date [-nu] [mmddHHMM[yy]]
                   date [-nu] [mmddHHMM[.SS[yy]]]
                   date [-nu] [yymmddHHMM[.SS]]
    
       If you include that command within a shell script,
       and execute the shell script as a step command, the
       command will work properly. For example, you could put
       the command "date >> dir_list" within the shell script
       date.sh and execute date.sh as the main step.
    

    Thanks,
    
    Changing to shell scripts in the Main Step field, got tasks running. 
    
    Guy

also guy the README will mention you will always get:
    stty:tcgetattr: Not a typewriter
    Not a terminal
  
in the .err most off the time.  This can be ignored.

bob