z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

A relative time specification may not use AM/PM format. The third form removes
item n from the event list:
> sched
1 Wed Apr 4 15:42 /usr/lib/uucp/uucico -r1 -sother
2 Wed Apr 4 17:00 set prompt=[%h] It’s after 5; go home: >
> sched -2
> sched
1 Wed Apr 4 15:42 /usr/lib/uucp/uucico -r1 -sother
A command in the scheduled-event list is executed just before the first prompt is
printed after the time when the command is scheduled. It is possible to miss the
exact time when the command is to be run, but an overdue command will execute
at the next prompt. A command which comes due while the shell is waiting for user
input is executed immediately. However, normal operation of an already-running
command will not be interrupted so that a scheduled-event list element may be run.
This mechanism is similar to, but not the same as, the at command on some UNIX
systems. Its major disadvantage is that it may not run a command at exactly the
specified time. Its major advantage is that because sched runs directly from the
shell, it has access to shell variables and other structures. This provides a
mechanism for changing one’s working environment based on the time of day.
Related information
tcsh
setenv built-in command for tcsh: Set environment variable name to
value
Format
setenv [name [value]]
Description
setenv without arguments, prints the names and values of all environment
variables. Given name, sets the environment variable name to value or, without
value, to the null string.
Related information
tcsh
settc built-in command for tcsh: Tell tcsh shell the terminal capability
cap value
Format
settc cap value
Description
settc tells the tcsh shell to believe that the terminal capability cap (as defined in
termcap) has the value value. No sanity checking is done. Concept terminal users
may have to settc xn no to get proper wrapping at the rightmost column.
Related information
tcsh
tcsh: sched
Chapter 2. Shell command descriptions 689