Dictionaly.Columns label gets trancated issue

[elena_ziemke_capblurcross_com]

We are running into issues with Dictionalry.Columns data for a file what we read in when the headings/labels on that file are over 64 characters long.    When we read the file in SAS process and then run 

proc sql;

select name, label

from  DICTIONARY.COLUMNS A

"label" colummn data is truncated to 64 characters so we don't see the entire value in this column. 

Anybody ran into this issue before, what can be done to resolve it?  Is there a setting or anything we can do to fix it?

We are on 9.4 M5.  

Thank you!

[Reeza]

What’s the format, informat and length of the variable?

You can get that from PROC CONTENTS on the output data set.

[elena_ziemke_capblurcross_com]

Format and Informat is $1

Lenght is 1

Lenght for this label column is 256 

LINESIZE=132

This is another message we get in Test 

NOTE: VARCHAR data type is not supported by the V9 engine. Variable Name has been converted to CHAR data type.

We believe this is all related but don't understand how to code around it OR why we get this error in Test but not Prod system.  Both systems are V9 engine. 

[Reeza]

Sounds like it's an issue for Tech Support then. 

V9 is a bit vague though, but the SASHELP libraries have been around a long time and there shouldn't be these types of issues.

---

@Elena_ziemke_capblurcross_com wrote:

We believe this is all related but don't understand how to code around it OR why we get this error in Test but not Prod system.  Both systems are V9 engine. 

---

[ballardw]

Where are you displaying the results? If you are using the listing destination (output window not Resuts) your line length may be too short to display everything on one line. Names may be 32 characters and if you are only seeing 64 characters in a label that may mean your linesize is 100 or less.

Create a table and examine the table properties. The label should have a length of 256.

I have no troubling labels from my data sets longer than 64 characters if sent to a table.

[Reeza]

D’oh, @ballardw answer is correct. I missed the fact that you’re not creating a table. 

Create a table and use PROC PRINT on it after and use ODS HTML it should be fine.