SAS data is read in by SAS Studio not by SAS EG

[shoin]

SAS dataset created on Solaris 9.3 SAS exported to Linux SAS 9.4 M8

simple sas dataset created on sas 9.3 solaris and exported to sas on linux 9.4 m8

The dataset is read in via sas studio and if run in batch, however in EG it shows obs=0 but correct # of vars

Proc content is almost identical encoding wise.

Any suggestions?

Thank you in advance,

S

[ballardw]

Show us the LOG from SAS at each step.

We have no way of telling if the first step had any observations much less what ever was done later. The LOG will show how many observations were "created" and likely how many were "exported", depending on method.

[ChrisHemedinger]

Is it just the data viewer in EG that won't show the data? Can you see the first observations in EG if you run PROC PRINT with an OBS= option? Is the data being accessed in EG via a libname statement or just directly from file system?

[Tom]

I don't understand what you mean by "exported to Linux SAS 9.4 M8".

Do you mean you copied the .sas7bdat file from old Unix system to the new Unix system?

Or did you actually run something to "export" it.  If so what type of file did you export it into? And how did you import it back into a sas7bdat file?

[BillSawyer]

Hi Shoin,

If the SAS dataset is on the EG client machine then from EG's Process Flow window use Tasks > Browse > Data > 'Upload Data Files to  Server' task which will copy the data to a SAS library on the SASAPP server (WORK library by default) to see if the data opens with expected  rows.

Or, if the SAS dataset is already on the SASAPP server (on the Linux box) then use a libname statement to point to the directory where the data resides then open the data from that library instead of the directly from the file system.

Ex.

libname mydata "in these quotes specify directory where the data resides on the linux box";

run;

After running the code then right-click on Libraries folder to refresh so that you see the new library then expand to then view and open the data.

If still an issue then feel free to open a new Case with SAS Technical Support and I will be glad to follow-up with you.  Be sure to include a proc contents of the dataset.

Regards,

Bill

[Quentin]

When you say "EG shows obs=0" what do you mean? Sometimes if you run PROC CONTENTS on a table in a database, it will show 0 obs, but that really means "I don't know how many obs there are because I can't find the information in the metadata".  But when you use the table in a DATA step, it reads all the data. So it's possible with transcoding or whatever, something like that is happening.

So you have a .sas7bdat file it a directory somewhere, lib.have.

Can you run:

proc contents data=lib.have;
run;

data want;
  set lib.have (obs=10);
run;

In both SAS studio and EG and post the results (log and PROC CONTENTS output)?

Are your SAS studio and EG pointed to the same SAS server?

If SAS thinks this file is corrupted, the log should provide helpful errors/warnings.