Suggest reviewing the PROC GPLOT documentation and the AXIS statement parameter (ANGLE=). The SAS support http://support.sas.com/ website has SAS-hosted documentation and also supplemental technical / conference reference material. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: proc gplot rotate axis value site:sas.com ... View more

Suggest the OP identify a sample "input" and desired "output", with SAS variable names as a header -- then review the ID and also BY statements for PROC TRANSPOSE as as suggested approach -- also consider the SAS support http://support.sas.com/ website and the supplemental technical / conference reference material. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: proc transpose id by statement site:sas.com ... View more

Consider the possibilities: - Learning opportunity.... - Self-discovery... - Desk-checking SAS program code-path / logic... Amazing how much information one can learn from a PUT (to the SAS log) or with a PUTLOG statement. Scott Barry SBBWorks, Inc. ... View more

This sounds like an interview question I've seen many times before - interleave uses SET (with or without a BY) and match-merge uses MERGE statement (with a BY statement, to achieve the match). And, the results are very much different - suggest the OP try it with the SASHELP "sample" dataset members and use various self-diagnostic techniques, such as PROC PRINT and use a PUTLOG _ALL_; statement in the DATA step where using the SET/MERGE statements. Scott Barry SBBWorks, Inc. Suggested Google advanced search arguments, this topic / post (clearly optional and no doubt extra-credit -- notice no links were contributed, nor harmed with this post-reply): data step programming set merge site:sas.com data step programming by group processing site:sas.com Message was edited by: sbb ... View more

I would say that a SAS FORMAT look-up (using a PUT function, or sometimes when using a PROC with a FORMAT statement) can be a more efficient performer depending on the search size. And I also would agree that the idea of maintaining a SAS format (no moving parts, like SAS statements) can also be more effective / efficient from a support perspective, particularly when using CNTLIN= to generate the FORMAT itself. As well, consider that PROC FORMAT was enhanced with SAS version 6 to permit character-value range strings which afforded the opportunity for data-string prefix wildcarding, when coded correctly. Consider that SAS can be influenced in the search/match behavior, choosing either "most discrete match" or "first entry match" when using a particular user FORMAT, as well. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: proc format character value range site:sas.com ... View more

Suggest you add the statement below to help with self-diagnosis: PUTLOG _ALL_; This will help determine if you have input your data record correctly or not. Also, you can test your code with a data-sample (instream) by using the statement: DATALINES; RUN; Scott Barry SBBWorks, Inc. ... View more

Decoding a user-defined SAS format: check the PROC FORMAT documentation, you have either CNTLOUT= (then PROC PRINT) or more simply you can use FMTLIB to print the contents of a SAS format. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: proc format fmtlib site:sas.com ... View more

Good point, Ksharp. Yes, the SAS behavior differs with one- or two- question-marks specified, as documented here: http://support.sas.com/documentation/cdl/en/lrdict/63026/HTML/default/viewer.htm#a000180357.htm Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: input function informat question mark site:sas.com ... View more

Please explain how "observations which move from...to..." - is there a master file that is updated in-place or is there some type of cycle / version type of aging going on with different SAS files for a particular period or year/month? And, also, how does one observation expect to be identified for tracking purposes, with some type of "key variable" that does not change over time? You will need to explain more accurately just how the data/information is processed input/output, or whether it's being maintained as a master file. At a minimum, it would be possible to maintain a prior cycle/version "copy" and use PROC COMPARE, based on some "key variable" identification, in order to compare variable value changes over time. Scott Barry SBBWorks, Inc. ... View more

Look at using SAS/ACCESS. Suggest searching the SAS support website for SAS-hosted documentation and also supplemental technical reference / conference material. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: access database sql server site:sas.com ... View more

Also, with your INPUT statement (or with using the INPUT function), you can specify a "?" character ahead of the INFORMAT with some additional overhead. Scott Barry SBBWorks, Inc. ... View more

To the OP: what you are asking can be done with ODS and cell-highlighting. I would encourage you to abandon the "roll your own HTML" technique, where possible. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: conditional cell highlighting site:sas.com ... View more

In my experience with ODS-generated output, it's much easier to parse SAS-generated HTML for any required manipulation than having to maintain a SAS program to generate the HTML tag statements for whatever is being created. I can't imagine having to turn this type of code-piece over to someone else, expecting that individual to embrace the same technical approach, frankly. Scott Barry SBBWorks, Inc. ... View more

To the OP: have you explored a SAS ODS generated output rather than hand-coding a DATA/PROC/macro-generated solution? Can you explain what it is about the required format that is sufficiently unique to need to go about it this way? Scott Barry SBBWorks, Inc. ... View more

Yes, PROC CONTENTS (and CONTENTS of PROC DATASETS) can read a SAS data library (called direct-access bound), however only PROC CONTENTS can process/readd a "sequential format" SAS data library (typically residing on tape). Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: sequential format site:sas.com ... View more