convert long length dataset from wpd to sas7bdat

[backstreets]

Hi there,

I am very new to linux. And now I am using wps to convert wpd data to sas data. I got a very wide wpd dataset.

Here is the code I tried to execute:

libname out sas7bdat '/u01/mylocation';

libname in '/u01/hislocation';

data out.A;

set in.A;

run;

Here is the command I used to execute this sas code in putty:

sas convert_wpd_tosas.sas&

But the thing is, I got this error:     Floating point exception(core dumped) sas  convert_wpd_tosas.sas

I can fix this by shorting the length of the variable in the dataset. But I wonder if there is any ways to execute the command without changing the dataset.

Just an update, my log is empty. I have seen people make it work. But not really sure what command they used.

Any suggestion is appreciated!!!

[LinusH]

New to SAS as well? The first libname statement is not valid.

If you got the same error after fixing the syntax, seeing the whole log would help.

[Tom]

You should have just gotten a new file named convert_wpd_tosas.log that would show your program and the notes and error messages from SAS.

If you got a core dump with that simple (but buggy) program then perhaps SAS is not installed right on your machine?

[backstreets]

Thank you, my log is empty. My libname is correct. I am just not typing the location. But please assume the libname is correct.

[LinusH]

It's not correct, sas7bdat is not a ´valid libname engine.

[backstreets]

Thank you. It is actually. I use this command and code on any short length variable dataset. And they all work. Sorry I am new to linux but not really new to sas

[jakarman]

Back streets the first Libname is having sas7bdat after out.

That is the location for the engine. V9 v8 but not sas7bdat.

The location folder name being correct should be no issue.

Sample data is nice real data not necessary.

Just follow your data policy guidelines with the cia rating

[backstreets]

I guess I am not understanding sir. Are you saying I should not put SAS7BDAT? I have done this for many other dataset and they all work

[Tom]

sas7bdat is a valid extension for SAS datasets.  Since it is 8 characters long and starts with a letter is could even be used a a LIBREF, but it is not a valid ENGINE to include in a LIBNAME statement.

890  libname a '.';

NOTE: Libref A was successfully assigned as follows:

      Engine:        V9

      Physical Name: C:\Users\xxxx

891  libname b sas7bdat '.';

ERROR: The SAS7BDAT engine cannot be found.

ERROR: Error in the LIBNAME statement.

[backstreets]

Sorry Tom. I use this all the time in wps system. Maybe the environment you have is different than mine

[Tom]

Sounds like you are using WPS instead of SAS. That value for an libname engine might be valid in WPS.  If you are trying to convert from some WPS specific format for data to a valid SAS format for data then I think you will need to use WPS and not SAS.  SAS will not know how to read file formats that WPS has created.

[jakarman]

Tom ok it shows the error that is done.
SAS(R) 9.3 Statements: Reference (libname statement documentation) and SAS(R) 9.3 Companion for UNIX Environments (valid engines Unix). and the same in SAS(R) 9.4 Companion for UNIX Environments, Fourth Edition.

What other me as knowing  there are some enhancements made in 9.4 (2gb records 32bit counteren enhanced to 64bit), there must be a difference somewhere that could be important with migrations. 

[jakarman]

Yep other supplier http://www.teamwpc.co.uk/docs/WPS-Reference-for-Language-Elements.pdf  World Programming  and a different syntax,

They reverse engineered the SAS library. If there is in error in that you should contact WPS TS support. World Programming (contact)