Date: Tue, 12 Oct 1999 13:05:09 -0700
Reply-To: "William W. Viergever" <wwvierg@IBM.NET>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "William W. Viergever" <wwvierg@IBM.NET>
Subject: Re: EBCDIC to Unix SAS
In-Reply-To: <38038DE7.B6742812@erols.com>
Content-Type: text/plain; charset="us-ascii"
I'm sure you'll get a few responses here.
Basically you want to get a binary image (or block) copy of the EBCDIC file, either via FTP or when copying from the EBCDIC tape to your unix box (your foreign tape reading software should have this option, basically it puts the data online in block format, not record).
If so, then you should be able to use the s370 informats to read the data.
Note: be this as it may, I personally have never been able to read VB/VL records, only FB/FL. My SAS jobs typically run fine but I don't get all the obs I expect; it appears the interblock gaps get screwed up inevitably.
HTH
At 03:37 PM 10/12/1999 -0400, jluke wrote:
>Are there any special considerations that should be made when bringing an EBCDIC SAS data file created on a mainframe MVS or CMS system to be used on a Unix system running SAS?
>
>Currently, when converting from PC SAS to our Unix SAS system I'm required to create a SAS transport file that I convert once it is moved to the Unix system. Is the same procedure nescessary with an EBCDIC file or can I avoid the transport file translation and read the EBCDIC file directly in to Unix SAS.
>
>Any help is appreciated.
----------------------------------------------------------------------------
William W. Viergever Voice : (916) 483-8398
Viergever & Associates Fax : (916) 486-1488
A SAS Institute Quality Partner (USA) E-mail : wwvierg@ibm.net
Sacramento, CA 95825
"Age is a question of mind over matter. If you don't mind, it don't matter."
- Satchel Paige -
"Reality is merely an illusion, albeit a very persistent one."
- Albert Einstein -
----------------------------------------------------------------------------
