Hi:
I agree with Scott -- knowing what is meant by "drop it into the Mainframe" is critical here.
If, for example, you have SAS on a local machine and you have SAS on the Mainframe and you have SAS/Connect, then you could read the Excel file, with the new columns on your local machine and then create a SAS dataset on the Mainframe which contained the new information. (This is similar, but not entirely similar to what would happen if you had EG on a local machine and were communicating with SAS on the Mainframe.)
If you only have SAS on a local machine, then you have different options. This is where the "drop it into the Mainframe" becomes critical. Mainframe files are not like PC files. They can live in proprietary database formats, like Oracle or DB2 or Adabas. A Mainframe file can be sequential -- it can be read with any program on the mainframe or a Mainframe file can be a a file that lives in a Partitioned Data Set; or a Mainframe file could be an older file type like VSAM or ISAM or BSAM format. PC files are in ASCII form in internal storage; Mainframe files are in EBCDIC form in internal storage. Last, but certainly not least, Excel does not live on the Mainframe. So what type of file would you create that would be "dropped" into the Mainframe??? A SAS dataset? A flat file to be read with some other type of program? A database file? What database?
What you want to do is possible. SAS on a local machine could create a sequential file that could be FTP'd to a Mainframe, and usually the FTP process will automatically do the translation from ASCII to EBCDIC. However, once on the Mainframe, what happens to the file? What program will read the file? Where does the file go? Where is the file stored? Generally speaking, SAS would not be able to create a file for a proprietary file format (like Oracle, DB2, VSAM, etc) without having SAS on the Mainframe -and- the appropriate SAS/ACCESS product. Just as you need SAS/ACCESS for PC Files to read Excel files on the Windows platform, you would need SAS/ACCESS for the appropriate file type or DBMS in order to WRITE files in a proprietary format.
Conceptually, what you want to do is possible. Your best resource, at this point, would be to contact Tech Support with this question and they could look at the current suite of SAS products that you have on various Platforms and they might be able to narrow down your options for making this concept a reality. For example, if you do have SAS and SAS/Connect on your Mainframe, then they can point you to examples of programs that use SAS/Connect. If you do not have SAS on the Mainframe, then they can point you to examples of programs that create "flat files" suitable for FTP'ing.
cynthia
... View more