The '0a'x only occur as line-end characters - never as data I hesitate to use the SAS filename ftp engine while it is still described as "experimental" see http://ftp.sas.com/techsup/download/technote/ts556.htm

A work around in the re-blocking approach delivered what we needed - and it worked quite quickly. It just took hours to find! Had a bit of trouble processing in the 200byte lrecl when two '0a'x occurred in one 200byte line. SAS produced an error message NOTE: DATA STEP stopped due to looping (it isn't host dependant, because the program and data generate the same message in SAS on WinNT)

All that went away by overriding the lrecl to 25 ( valid because it is an eighth of the stored lrecl) then that combination of more than one delimiter on one line won't arise

Datum: 20.07.99 21:41 An: Peter Crawford/Zentrale/DeuBaExt

Betreff: Re: Antwort: Re: os/390(mvs) reading a file after binary FTP from os/2 Nachrichtentext:

No - I didn't see your later spec that SAS wasn't available at the source until later. see later missle about using FTP as part of file access method... let mainframe read remote file directly without moving it with FTP. I think that will work.

If not - there are other methods... such as using Samba to share files across NT/UNIX machines... OS/390 has a UNIX flavor to it... if your at that level.

At 09:27 PM 7/20/99 +0100, you wrote: > > >Can cport handle external files ? > > > ---------------------------------------------------------------------- Michael S Hines, CISA,CIA,CFE,cDP | Phone 765.494.5338 Coordinator of Data Systems / Programming | fax 765.496.1466 Schools of Engineering | e-mail: mshines@purdue.edu 1280 Engineering Administration | West Lafayette, IN 47907-1280 | ----------------------------------------------------------------------