Suggest you confirm what application generates this "file extension" type with your requestor - then do a search on the SAS support website http://support.sas.com/ for additional information, as well as checking the SAS Discussion Forums archives. Scott Barry SBBWorks, Inc. ... View more

Recommend searching the SAS support website at http://support.sas.com/ for your keywords - several DOC and tech SUGI/SGF paper references show up. Scott Barry SBBWorks, Inc. ... View more

Investigate using the UPDATEMODE=MISSINGCHECK|NOMISSINGCHECK parameter on the MODIFY statement to influence the missing-value handling behavior. Scott Barry SBBWorks, Inc. ... View more

The SAS PROC COPY procedure is used for this purpose -- specifically to make a back of the entire SAS data library, typically to be used for recovery purposes, as needed. Other approaches, such as using a DATA step to "duplicate" your production SAS database table(s) is somewhat short-sighted and may not satisfy a complete and effective recovery scenario. Also, consider that your D/R (backup and recovery) approach is going to be influenced by the availability of technical (data storage, scheduling, staffing) resources, as well as your operating environment (platform). This topic must be considered from a data management level, rather than at the lowest (SAS data table/index) level, frankly, if it is to be considered seriously for an enterprise data warehouse / repository initiative. Scott Barry SBBWorks, Inc. SAS.COM support site http://support.sas.com - technical paper references on this topic: http://support.sas.com/resources/papers/sgf2008/recovery.pdf http://support.sas.com/rnd/papers/sgf07/sgf2007-iosubsystem.pdf http://support.sas.com/documentation/onlinedoc/spds/admin443.pdf ... View more

SAS can be used to generate reports and other outputs in many formats (HTML, PDF, RTF, text-format, XML), so I would say that your SAS reports can be integrated with Visual Composer. Suggest you inquire directly with the SAP forums' discussion on Netweaver and Visual Composer, at https://www.sdn.sap.com/irj/sdn/forums Scott Barry SBBWorks, Inc. ... View more

A more general-purpose code logic would be to use IF FIRST.usubjid THEN DO; END; logic to test initialize a "temporary" SAS variable to the desired no-match condition, and use a RETAIN to keep track of this variable, and if the desired "match" condition is encountered for the "test" variable, set the "temporary" variable to a given value. The, use the IF LAST.usubjid THEN DO; END; logic to reset RESULT to the temporary variable and do an OUTPUT. This logic flow does not require a particular sort-sequence or "match" value order condition to work properly. The key here is using the RETAIN statement to track a temporary variable in the DATA step (remember to either DROP this var or specify a KEEP statement). Scott Barry SBBWorks, Inc. ... View more

The SAS macro code is using a technique to force a TRUE condition test result. A value of 1 is TRUE and a value of 0 is false. You can see this processing decision during SAS code compilation if you turn on: options source source2 macrogen symbolgen mlogic; Scott Barry SBBWorks, Inc. ... View more

Read the DOC on the COMPRESS function and you will see that you can supply the specific character(s) to be compressed. Scott Barry SBBWorks, Inc. ... View more

I believe this topic is discussed on the SAS support website http://support.sas.com/ - a link to the white paper is provide as well as the SAS DOC reference. Case Study in Synchronizing Identities in the SAS®9 Metadata Server with an Enterprise Security Provider This case study highlights the advantage of importing user and group information from an enterprise security provider, such as the Microsoft Active Directory. SAS provides macros that can be integrated with scheduling and other tools to synchronize SAS metadata repository identities with the enterprise Lightweight Directory Access Protocol (LDAP) environment. http://support.sas.com/rnd/papers/sgf07/sgf2007-syncmetadata.pdf Referenc within paper: RESOURCES SAS Institute Inc. 2006. "Appendix 2. Bulk Load Processes for Identity Management". SAS® 9.1.3 Intelligence Platform: Security Administration Guide, Second Edition. Cary, NC: SAS Institute Inc. Available support.sas.com/documentation/configuration/bisecag.pdf Scott Barry SBBWorks, Inc. http://support.sas.com/rnd/papers/ - tech papers ... View more

In your "not working" process, you are attempting to concatenate a data string to the end of a SAS variable. The concatenation operation does not trim trailing blanks, so your resulting SAS variable (after the array processing) has been truncated. For what you are trying to accomplish, you must use a function to accomplish the trim, such as CATT (new with SAS 9, or TRIM -- there are others as well). Also, if you were to add a PUT _ALL_ to your DO/END processing after the assignment, you might have some additional diagnostic information to see the execution as it is processing. Scott Barry SBBWorks, Inc. ... View more

Use the COMPRESS function in a SAS DATA step. Scott Barry SBBWorks, Inc. ... View more

Have a look at the PROC GBARLINE and search for "Bar-Line Chart" information resources on the SAS support website http://support.sas.com/ to find useful information and examples. Scott Barry SBBWorks, Inc. http://support.sas.com/documentation/cdl/en/graphref/59607/HTML/default/a002258324.htm ... View more

This is yet another anomaly with the "date" related INFORMAT handling. The fact that there is mixed INPUT processing is a contributing factor. My recommendation is to open a SAS support track, to let SAS Institute know that this unexpected input handling occurs when there is a date input field, and where the delimiter DOES NOT occur in the input record. For illustration purposes, the two different input record types are processed, one containing a date field within the record and a second type without a date. SAS seems to handle the record not containing the date with no problem. See the code below: data _null_; infile datalines dlm='\'; format numdtvar1 date9.; input type $ @; if type ne ' ' then do; if type = '1' then input charvar1 $ numdtvar1 anydtdte. numvar1 4.2 charvar2 $; else if type = '2' then input charvar1 $ numvar1 4.2 charvar2 $; putlog _all_; end; datalines; 1\aaaa\01jan2008\2222\bbbb 2\aaaa\2222\bbbb run; Like I suggested, open a support track and stand your ground. Good luck. Scott Barry SBBWorks, Inc. ... View more

A search of the SAS support website http://support.sas.com/ revealed these references, which may prove useful in your quest: http://www.sas.com/technologies/dw/etl/access/sol_adapter.html http://support.sas.com/documentation/onlinedoc/91pdf/sasdoc_91/access_sapbw_7297.pdf Scott Barry SBBWorks, Inc. ... View more

From what I understand, you want to "count" (do you mean combine together as one DEPT (DEPT='*DUPS*'; )??? Regardless, I believe you will need to pre-process your data file with a DATA step, as follows: 1) sort SAS member input by DEPT, creating a temp file. 2) use DATA step to input/output the temp file, and use FIRST.DEPT and LAST.DEPT to determine where there are multiples, and do something -- either combine these into a single DEPT value or establish a new "count" variable). 3) sort your temp file in DEPT sequence. 4) Use PROC MEANS, as you have shown in your code. Scott Barry SBBWorks, Inc. ... View more