MVSFORUMS.com

What programming/application lanuguage will you be using?

Ha Ha - too funny! I need to read these more closely...

Welcome DaveTV.

Do you plan on staying in Boston? Hopefully there's work to be found in your area. I lived in Connecticut briefly - really enjoyed New England.

hmmm...RIF'ed - the letters als ...

Very nice shekar - I was not aware of this feature.

One additional note: You may have to scroll left or right in 3.4 to see the members.

A comma separated file is even easier. Just put a comma in between each field in your text file, FTP it to the win platform with a file extension of .csv, and it will open in Excel as though it were ...

PROC SQL should be much easier than data step (unless data step is required.) It looks like you're trying to process each record from the first table against each record from the second table...defi ...

It's not clear what you are trying to accomplish. Joining the tables is much simpler than what you are doing...perhaps you want more than to just join the two tables by ID? Pleas explain.

Ask the DBA.

I suggest you google for third party applications. I have never heard of such a product. However, there are thrid party products that will process SAS job logs (parse them into easy to read highligh ...

You could label them as moderator in bold red under their name. I've seen that on other boards and it's very effective.

A PROC PRINT might be what you're looking for. BEWARE that without a limit on the records, it will attempt to print ALL records. You can limit like this:

Remove the PROC SUMMARY because you are n ...

How about just adding the TITLE parameter with no text: It's working for me...

PROC REPORT DATA=X;
COLUMN A B C;
TITLE;
RUN;

Are you using the TITLE statement? If so, then TITLE1 should replace "The SAS System"

Pcik up a copy of "The Little SAS Book". Found in most major book store catalogs.

But of course you'll be checking the forum!