Only a little "off-thread"....... As Randy Cartwright <rwcartwright@aaamichigan.com> writes >one of the big differences is that on the mainframe, SAS can >read files directly using the JCL DD name, rather than using filename >and libname (although both are still usable).

I often like to show how both winXX and unix platforms have their equivalent to the mainframe ddname . In Display Manager, issue command LIB or open the explorer on libraries. Usually you won't see libref TEMP Now issue command DIR TEMP or DIR SASROOT

A normal SAS Directory window opens ! but you haven't issued a libname statement nor created a libname with the dialogs. What happens is: an environment variable fills the same role as a ddname, and SASROOT is an environment variable that always seems available, and TEMP is normally defined in the operating system environment.

The environment variable name must be 8 or less characters wide conform to sas naming convention i.e. letter or underscore start and, on unix, it must be defined in upper case Of course, it should also point to a path.

Explore differences and find similarities !!!

Regards Peter Crawford Crawford Software Consultancy UK

Randy Cartwright <rwcartwright@aaamichigan.com> writes >Richard Thornton <richard@sun1.programming-analytics.org> wrote in message >news:<Pine.GSO.4.33.0310161959420.3422-100000@sun1>... >> Basically "mainframe" SAS is the same as any other SAS, except JCL >> is involved; Usually the SAS code is inline following a >> >> //JOBCARD >> //IN1 DD DSN = etc >> . >> . >> . >> >> //SYSIN DD * >> >> Options obs=max symbolgen; >> >> libname whatever; >> filename whatever; >> >> data test; >> run; >> >> proc means; >> run; >> >> >> /* >> //* >> >Actually, one of the big differences is that on the mainframe, SAS can >read files directly using the JCL DD name, rather than using filename >and libname (although both are still usable). E.g., > >//FILEONE DD DSN=FILENAME.NEXTNAME.WHATEVER,DISP=SHR >. >. >. >DATA FIRST; > INFILE FILEONE; >etc. > >As Richard pointed out, the rest of SAS operates pretty much as it >would on any other platform. SAS also publishes a very useful manual, >"SAS Companion for the MVS Environment", which covers things such as >how to set up JCL, how to allopcate work space, etc. >> >> >> On Thu, 16 Oct 2003, Zalek Bloom wrote: >> >> > Can someone publish here a sample of SAS mainframe program? I worked >> > with a maiframe SAS long time ago and want to prepare for an >> > interview. >> > >> > Thanks, >> > >> > Zalek >> >

-- Peter Crawford

Crawford Software Consultancy UK