Please share your exact SAS code, pasted from your SAS log with all code lines revealed. Scott Barry SBBWorks, Inc. ... View more

To ArtC: From the SAS DOC (link below), there is indication that the SYSERR macro variable *IS* reset at the step-boundary. SAS 9.2 Macro Language: Automatic Macro Variables, SYSERR Automatic Macro Variable http://support.sas.com/documentation/cdl/en/mcrolref/61885/HTML/default/viewer.htm#a000208995.htm Scott Barry SBBWorks, Inc. ... View more

To the OP: you will need to share a bit more information than: "this does not work for me?" What code did you use to make the change? What HTML tag information was generated by SAS to the HTML document? Scott Barry SBBWorks, Inc. ... View more

The value of _ERROR_ is only maintained until it is reset by the user, influenced/assigned based on another INPUT function or use of an INPUT statement with a suitable INFORMAT. However, when you return to the top of a DATA step execution, the value is reset to _ERROR_=0 -- it's prior step-execution value is not maintained. This behavior is inherent to the SAS system architecture. Scott Barry SBBWorks, Inc. Message was edited by: sbb ... View more

It's most likely that you have defined an incorrect SAS LIBNAME location - I would doubt that you have SAS datasets/members in your root directory of the C:\ drive. Here is the key information from your SAS-generated log output: ERROR: The data set list (CDM.temp_:) does not contain any members. To start, find a suitable SAS data library folder, then do a PROC CONTENTS (shown below) to confirm you are where you expect to find your input SAS files, as coded in your SET statement: PROC CONTENTS DATA= ._ALL_ NODS; RUN; Scott Barry SBBWorks, Inc. Message was edited by: sbb ... View more

I agree with Reeza, and suggest the "input record buffer" be parsed using one of a few different DATA step functions, likely considering maybe SCAN, FIND, SUBSTR, INDEX, INDEXC, and possibly VVALUE or VVALUEX for assignment. Suggested DATA step structure approach demonstrated below: DATA ; KEEP ....; * RECOMMEND CODING SAS ATTRIB OR LENGTH STATEMENTS ; * HERE TO DECLARE EXPECTED SAS VARIABLES. ; INFILE ....; INPUT ; DO WHILE(1=1); * COME HERE FOR INFINITE LOOP TO PARSE CURRENT INPUT ; * RECORD AND DECODE ONE OR MORE SUB-FIELDS. ; LENGTH TEMPVAR $1000; I+1; TEMPVAR = SCAN(_INFILE_,I,'!'); * EXIT THE DO LOOP NOW WHEN NO MORE FIELDS TO PARSE. ; IF TEMPVAR = ' ' THEN LEAVE; * YOUR PARSING CODE FOR EACH RECORD SUBTYPE/FIELDS GOES HERE.; END; RUN; ... View more

I believe that your fundamental concern will be the underlying SAS software version, its supported operating environments and end-of-service time-frame. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: SAS end of service site:sas.com ... View more

As stated in my prior post, the use of a SAS dataset prefix in a SET statement is SAS version specific, it being a new feature available only with SAS 9.2. Scott Barry SBBWorks, Inc. Message was edited by: sbb ... View more

You cannot influence the exact location of a PROC PRINT column header label value, relative to the column-position of your detail report "body" contents. However, if you use a DATA step approach to generate your report/output, then, yes, you have full-control of the position of your column header label as it related to the report content, however you then must contend with variances in maximum data-width each execution, as compared to SAS PROC PRINT, when your SAS data variable values change in maximum length, from run to run. Also, you may have some additional flexibility with PROC REPORT. It would be most helpful to share your SAS code, fully expanded, in an embedded post-reply (COPY/PASTE from your SAS session log). Scott Barry SBBWorks, Inc. ... View more

I have to disagree with Ksharp, the behavior with _N_ is not consistent with _ERROR_ . And also to seek clarification from the OP, as I don't see where the value of _ERROR_ is actually "retained" across DATA step iterations, as its value is reset to zero. When a DATA step returns to the top, the _N_ is reset to the next data-value and does not "retain" the prior iteration value, not even before a SET is executed. And, in the case of _ERROR_, SAS also does not retain the prior DATA step iteration value. A code-snippet is listed below this post to demonstrate - for those who want to execute it on their own SAS system. Scott Barry SBBWorks, Inc. data x; do a=1 to 4; output; end; stop; run; DATA _null_; PUTLOG '>BEFORE-SET>' / _ALL_; set x; if a = 2 then x = input('a',best.); PUTLOG '>AFTER-SET>' / _ALL_; RUN; ... View more

Some pertinent reply info: 1. How can i get the by variable not printed out in between? REPLY: OPTIONS NOBYLINE; 2. Why are there spaces before Holdcode (tested with 2 different styles) REPLY: suggest self-diagnosis by reviewing the SAS-generated HTML code - nothing evident from JPEG image. 3. How does my link gets opened in a new window? REPLY: You must manipulate your generated URL string to include the HTML-standard tag behavior below: target="_blank" 4. Can i add formatting to my text in the compute before part? REPLY: suggested SAS support website search below. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: +"proc report" +"compute before" +formatting site:sas.com ... View more

Suggest SAS NLS function documentation review / reference, possibly KUPDATE or KTRANSLATE. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: replace characters nls function site:sas.com ... View more

Suggest starting with PROC CONTENTS output - also, refer to details in your particular OS environment's SAS "companion" documentation. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: proc contents estimate file size site:sas.com ... View more

Reading the INPUT statement DOC, it clearly states "...next non-blank column...". http://support.sas.com/documentation/cdl/en/lrdict/63026/HTML/default/viewer.htm#a000144370.htm If there is a chance you will have a blank value, then you will need to consider using the _INFILE_ automatic variable to parse your input record with the SCAN function (or possibly using FIND, INDEX/INDEXW/INDEXC). Scott Barry SBBWorks, Inc. Google advanced search argument, this topic / post: input list format modifier site:sas.com ... View more

Do your "100 outputs" reside in SAS database files? If so, what is the naming convention used and what SAS version are you using? For example, if all files are named with the same "prefix string", you can use a SET statement technique like below, for example to concatenate all files starting with "XXX" in libref : SET .XXX: ; If your files all reside outside of SAS in an external data source, you will need to consider a SAS macro language technique, possibly, which will also depend on the external file naming convention -- however it is possible to an INFILE with an external file prefix (or possibly use FILENAME with PIPES and get the directory/file information into SAS for processing each individual file. Scott Barry SBBWorks, Inc. ... View more