Home > Data Services > Catalog . Restricted Data . Census . ACS

Search Data Services

Meta Search
search across all the following databases:

Data Catalog
Data and documentation

KnowledgeBase
Common questions and answers.

Resources
Entire collection of data resources.


Latest Data News

RSS Feed icon

Lessons from North of the Border

Nerd Alert: Dictionary of Numbers

International Migration Statistics for the US

Open Data Executive Order

Measuring Marriage & Divorce among Same-Sex Couples

Terminal I/O attempted with no controlling terminal

If a user gets the following message in a SAS log file:

ERROR:  Terminal I/O attempted with no controlling terminal.

Most likely, this means that /usr/tmp is full on the workstation where the job was running. Users can go in and delete their own files from /usr/tmp. Typically, /usr/tmp looks like this:

drwx------   2 hono     audit        203 Jan 19 00:15 SAS_worka00001CE6
drwx------   2 hono     audit        250 Jan 19 01:23 SAS_worka00001EE2
drwx------   2 hono     audit        474 Jan 19 04:05 SAS_worka000023F1
drwx------   2 hono     audit        156 Jan 19 04:14 SAS_worka0000242A
drwx------   2 hono     audit        156 Jan 19 04:14 SAS_worka00002430
drwx------   2 hono     audit        156 Jan 19 04:15 SAS_worka00002438
drwx------   2 hono     audit        156 Jan 19 04:15 SAS_worka0000243D
drwx------   2 steffick audit        203 Jan 12 09:20 SAS_worka00003D46
drwx------   2 hono     audit        203 Jan  4 12:55 SAS_worka00006810
drwx------   2 hono     audit        156 Jan  4 15:18 SAS_worka00006A25

To clean your own work area:

cd   SAS_worka00003D46   [if you are steffick]
rm *.*

However, if another user has filled /usr/tmp, someone with root authority and familiarity with statistical packages has to go in and clean up /usr/tmp.

See Neidert or Rodriguiz for help.