16.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

tcsh<br />

v The autologout shell variable can be set to log out of the shell after a given<br />

number of minutes of inactivity.<br />

v The mail shell variable can be set to check for new mail periodically.<br />

v The printexitvalue shell variable can be set to print the exit status of commands<br />

which exit with a status other than zero.<br />

v The rmstar shell variable can be set to ask the user, when rm * is typed, if that<br />

is really what was meant.<br />

v The time shell variable can be set to execute the time built-in command after the<br />

completion of any process that takes more than a given number of CPU<br />

seconds.<br />

v The watch and who shell variables can be set to report when selected users log<br />

in or out, and the log built-in command reports on those users at any time.<br />

National language system report<br />

When using the system’s NLS, the setlocale function is called to determine<br />

appropriate character classification and sorting. This function typically examines the<br />

LANG and LC_CTYPE environment variables; refer to the system documentation<br />

for further details.<br />

Unknown characters (those that are neither printable nor control characters) are<br />

printed in the format \nnn.<br />

The version shell variable indicates what options were chosen when the shell was<br />

compiled. Note also the newgrp built-in and echo_style shell variable and the<br />

locations of the shell’s input files (see “tcsh files” on page 671).<br />

The tcsh shell currently does not support 3 locales. They are IBM-1388 (Chinese),<br />

IBM-933 (Korean) and IBM-937 (Traditional Chinese).<br />

Signal handling<br />

Login shells ignore interrupts when reading the file ~/.logout.The shell ignores quit<br />

signals unless started with -q. Login shells catch the terminate signal, but non-login<br />

shells inherit the terminate behavior from their parents. Other signals have the<br />

values which the shell inherited from its parent.<br />

In shell scripts, the shell’s handling of interrupt and terminate signals can be<br />

controlled with onintr, and its handling of hangups can be controlled with hup and<br />

nohup.<br />

The shell exits on a hangup (see also the logout shell variable). By default, the<br />

shell’s children do too, but the shell does not send them a hangup when it exits.<br />

hup arranges for the shell to send a hangup to a child when it exits, and nohup<br />

sets a child to ignore hangups.<br />

Terminal management<br />

The shell uses three different sets of terminal (tty) modes: edit, used when editing,<br />

quote, used when quoting literal characters, and execute, used when executing<br />

commands. The shell holds some settings in each mode constant, so commands<br />

which leave the tty in a confused state do not interfere with the shell. The shell also<br />

matches changes in the speed and padding of the tty. The list of tty modes that are<br />

kept constant can be examined and modified with the setty built-in. Although the<br />

editor uses CBREAK mode (or its equivalent), it takes typed-ahead characters<br />

anyway.<br />

652 z/<strong>OS</strong> <strong>V1R9.0</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> <strong>Command</strong> Reference

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!