Possibly the ERRORABEND / NOERRORABEND condition may be the cause for different behavior? It would be best to share SAS log output with source code revealed for a proper diagnosis, after you have determined that the SAS behavior is different based on the two instances - check your PROC OPTIONS; settings for differences, possibly. Scott Barry SBBWorks, Inc. ... View more

Did you consider the ORDER=FREQ parameter on the PROC FREQ statement? Scott Barry SBBWorks, Inc. ... View more

Please post the SAS log information with the exact error message and SAS program code revealed. If you are using macro or macro variable logic, you will want to have an OPTIONS, such as: OPTIONS SOURCE SOURCE2 MACROGEN SYMBOLGEN MLOGIC; It's quite possible that with the above SAS statement, you may see the error cause with your own problem diagnosis, by the way. One possibility to verify is the DCB attributes for your PDSE, ensuring that it is being allocated as you expect? And obviously a member name can only be up to 8 characters. Scott Barry SBBWorks, Inc. ... View more

One approach is to use a DATA step and a SET statement with the two files specified on the SET. Scott Barry SBBWorks, Inc. ... View more

After visiting the SAS support website http://support.sas.com/ I did a search using the argument "proc export label column" and one of the search results is the link below: http://support.sas.com/kb/12/754.html Scott Barry SBBWorks, Inc. ... View more

Yes. One approach is to create a SAS file (and sort it) from your tblStates and then using the DATA step technique, merge the sorted file with your other tblAddress file, using a BY statement. Scott Barry SBBWorks, Inc. ... View more

Absolute column pointer is an offset in your input data/record buffer, relative to @1 being column 1. Relative column pointer is an increment (either plus or minus) from the current pointer position in the input data/record buffer, that being +10 in the INPUT statement below is at pointer location 25, for example: INPUT @5 myvar1 $char10. +10 myvar2 $char5. ; Scott Barry SBBWorks, Inc. Some SAS DOC links on this topic from SAS support website http://support.sas.com/ listed below: http://support.sas.com/documentation/cdl/en/basess/58133/HTML/default/a002645710.htm http://support.sas.com/documentation/cdl/en/lrdict/61724/HTML/default/a000146292.htm ... View more

I recommend not limiting yourself to the DATA step use of the BY statement, but also explore using the BY statement with SAS PROCs, as well, to generate separate analysis output based on the list of variables. Scott Barry SBBWorks, Inc. ... View more

Explore using the SAS DATA step and particularly the REVERSE function. And for the SAS numeric variable, use the SAS function PUT to convert the number to a character string first, then use the REVERSE function against the character variable representation of your number. Scott Barry SBBWorks, Inc. ... View more

[So I am breaking it up into two parts] The SAS support website http://support.sas.com/ has SAS product documentation and supplemental technical papers - the site's SEARCH facility can be used or consider the Google advanced search argument below which yields matching search results on the site using your topic (note that the site parameter must be in lowercase characters or it is ignored by Google): proc sql data set options site:sas.com Scott Barry SBBWorks, Inc. ... View more

[Sorry - SAS website server hangs with a more detailed post] With PROC SQL (similar to other SAS dataset option/parameter specifications), explore using the (KEEP=_NUMERIC_) parameter to select all SAS variables of a particular type. Scott Barry SBBWorks, Inc. ... View more

test reply - ignore. ... View more

When launching SAS, it is possible to pass a SYSPARM= parameter -- I suggest you explore how you can introduce this parameter into your vbs script as a command invocation parameter, then your SAS program can reference either the automatic macro variable named &SYSPARM, or you can retrieve the SYSPARM= character string using the SYSPARM() function. The SAS DOC has information about SYSPARM. Scott Barry SBBWorks, Inc. ... View more

Suggest you reply to the group with SASLOG output revealing your SAS DATA and PROC step execution adjacent to the failing DATA step, also showing the error message you receive. The critical contributing factor here is the location of your KEY= parameter on the SET statement - something the DOC can help convey. Scott Barry SBBWorks, Inc. ... View more

Possibly SAS/Stat is not a licensed SAS component on your system? Use PROC SETINIT to display what components are licensed: proc setinit; run; Scott Barry SBBWorks, Inc. ... View more