Date:         Thu, 8 May 2003 16:28:58 +0100
Reply-To:     SAS User <sasuser@GUILDENSTERN.DYNDNS.ORG>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         SAS User <sasuser@GUILDENSTERN.DYNDNS.ORG>
Subject:      Re: SAS 6.12 / HP-UX
In-Reply-To:  <73FC8D4DCAD8D41190B300508B6980C202DFB80C@RARUSRAEXS13.prius.jnj.com>
Content-Type: text/plain; charset=us-ascii

on Thu, May 08, 2003 at 10:20:57AM -0400, Bosch, Jules [PRDUS Non J&J] (JBosch1@PRDUS.JNJ.COM) wrote:
> I have two SAS transport files sitting in a UNIX subdir.
>
> If I execute the UNIX command -
>
> "head -20 file_ONE"
>
> I get some text from the file on the terminal screen.
>
> If I execute the UNIX command -
>
> "head -20 file_TWO"
>
> the terminal screen freezes and I lose my UNIX session.
>
> Can someone suggest what may be the problem here.  Is file_TWO corrupted?

Maybe.  Maybe not.

You don't mention your terminal type, connection and several other
settings.  It's possible that you're getting a hangup or EOF from the
file that's terminating your shell or remote connection.  Various remote
access methods have various means of disabling magick character actions.

I'd suggest using a more meaningful tool to assess your dataset.  There
is the '-v' switch to 'cat' which generally presents nonprinting
characters in an encoded format while protecting your shell session.
The 'od' command can provide an octal or hex dump of your data.  SAS is
the best tool to assess the integrity of the transport library, though
other tools which can read a SAS transport dataset might also be used.

--
Charming man. I wish I had a daughter so I could forbid her to marry one...