Thank you so much. This what I was looking for. You can't believe how much you helped me by doing this. Thanks again ... View more

the A B C D E F are the some names   which do not correspond in any way to your input data, so we can't possibly help you produce such a table from this input data. Also we don't know what the numbers in the cells are. A better explanation is needed.   If you want zeros, you can add zeros for the missing months into your input data. ... View more

Hi Can you suggest what all modification needs to be done. if we have duplicate(that will form another hierarchy/tree) node. currently I am working on some similar project where I need to create a parent child grandchildren ....so on. relation table. Your code seems to be perfect but only thing is that I have duplicate also in the input file. ... View more

Hi , For now minimum lines of code and less execution time would be good for me. Thanks a lot ... View more

thanks ... View more

Thanks JuanS_OCS for the link ... View more

What is the question?  You are using a simple data step to write all variables to delimited file. Other than the strange code to add the carriage control character it should work fine.   But why are you manually adding a CR to the end of the line?  Why not just use the TERMSTR= option on the FILE statement to tell SAS what end of line characters to use?     DATA _NULL_; SET TEMP; FILE OUTFIL DSD DLM='|' LRECL=32767 TERMSTR=CRLF; PUT (_ALL_) (+0) ; RUN; Are you really on an IBM mainframe?  Wouldn't the way that the records are written to the file be controlled by the DD specifications in the JCL?  What type of file ends up on your target Windows or Unix system when you download it depends on how you perform the download. If you download it using FTP protocol as an text file instead of a binary file then it will write the file using the appropriate end of line characters for your target system.   Note that when you write using the DSD option then it will put nothing between the delimiters when the value is missing ( or blank for character variables).  That is why you will see two "pipes" next to each other some times. This is how delimited files are normally created.  Reading it will the DSD option on the INFILE statement will tell SAS to properly recognize the missing value.      Is the question about the leading spaces?   If you are reading your 'PIC -9.9(5)' field as a NUMBER then there are no "spaces" in a number. The space is just in your fixed length file to make the field take up the full width allocated in the fixed format layout.   When SAS writes using list mode (what you are doing essentially) then any leading and trailing spaces are removed.  So even a character variable that was created with leading space (or any character variable that has a value that is shorter then the variable's length) will not have leading or trailing spaces written to the output file.  Example:  2354 data _null_; 2355 file log dsd dlm='|' ; 2356 x=1; y=2 ; c=' string '; 2357 put x c y ; 2358 run; 1|string|2  If you really need to preserve leading spaces in the output then here is one way using $VARYING format so that the character variable is written using formatted style instead of list style.  Because of not using list mode for that variable you need to manually add the delimiter if another variable follows.   2394 data _null_; 2395 file log dsd dlm='|' ; 2396 x=1; y=2 ; c=' string '; 2397 n=lengthn(c); 2398 put x c $varying1000. n '|' y ; 2399 run; 1| string|2 To do that for a general dataset you would need to use some code generation and not just a simple variable list. ... View more