About sbb

sbb · ‎08-02-2011

To translate a numeric character into a represented month-name, use the MONNAME format in an assignment statement, along with a static 'day' and 'year' argument with the MDY function. data _null_; your_month = 2; Month = put(mdy(your_month,1,year(today())),monname.); putlog _all_; run; For the various INFORMATs to translate your date-time string, have a look at the SAS DOC - here is a reasonable Google advanced search argument to search the SAS-hosted documentation on its support website: mm/dd/yyyy datetime informat site:sas.com Scott Barry SBBWorks, Inc.

sbb · ‎07-07-2011

Some self-diagnosis output can be generated by adding this statement to a DATA step, so you can see in your SASLOG the SAS-generated temporary variables for FIRST.<byvar_> and/or LAST.<byvar_>. This information will help diagnose the program's execution more visually. Basically, you are only going to "OUTPUT" the last-occurrence condition of both of your BY statement variables. So, then, if you have a requirement to generate observations for other "OR" conditions, you will need to code them in your IF (<expression1>) OR (<expression2) THEN <action>; statement. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: by group processing site:sas.com

sbb · ‎07-01-2011

Diagnostic techniques to consider: 1) turn on the macro-generated source code: OPTIONS SOURCE SOURCE2 MACROGEN SYMBOLGEN MPRINT /* MLOGIC */; 2) add this line at various points in your DATA step to print-out on the SAS log the SAS variable contents as you perform one DATA step pass (change each "nn" value to be unique for identification in the log): PUTLOG '>DIAG-nn>' / _ALL_; 3) perform testing with a smaller subset of unique-characteristic input (data / observations) for exercising various code path scenarios. Scott Barry SBBWorks, Inc.

sbb · ‎06-28-2011

To simplify the edit activity, use a SAS macro variable to resolve the <libref> portion of your LIBNAME statement. You can use a %INCLUDE statement to include / execute a SAS code member that contains the %LET statements needed to resolve the current-value of the <libref> portion. And with that the actual LIBNAME statement and other code remains static. Scott Barry SBBWorks, Inc.

sbb · ‎06-24-2011

Recommend the OP review this topic in the SAS DOC related to global and local macro variable scope. Which by the way is influenced by the use of a RUN; statement with a DATA step. Also, it is most informative to COPY/PASTE an actual SAS log with all related diagnostic messages along with the SAS code execution (entire program, preferably). Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: symput macro variable scope site:sas.com

sbb · ‎06-22-2011

Suggested Google search argument might be: ascii code +"minus sign" Scott Barry SBBWorks, Inc.

sbb · ‎06-20-2011

Please clarify "the problem still didn’t go away" - share your actual SAS log output for a run where you had firstobs=2. Also, consider adding either or both of these SAS debugging statements for some self-initiated desk-checking: LIST; PUTLOG _ALL_; Scott Barry SBBWorks, Inc.

sbb · ‎06-17-2011

Use a DATA step approach and the PUT statement to generate the data-lines. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: data step put statement external file site:sas.com

sbb · ‎06-17-2011

Use a DO / END loop and use COUNTW function to count the words (in your part of the DO). You will have a LENGTH/ATTRIB, a SAS assignment where SCAN is used to parse the data-string, and an OUTPUT statement (minimum) in the DO/END code paragraph. Scott Barry SBBWorks, Inc.

sbb · ‎06-16-2011

Your INCLUDE file needs to provide all CHANGE statement parameters as shown in the prior thread - repeated here: CHANGE %INCLUDE ; ; Your input file must have syntactically valid CHANGE statement parameters for the members you wish to rename, supplying (to be generated by your DATA step logic): = = = So, you will have two files, one for the PROC PDSCOPY if you need a SELECT statement to copy a subset list of PDS members. And then another input file which contains the CHANGE statement parameters. Scott Barry SBBWorks, Inc.

sbb · ‎06-16-2011

Slight coding simplification, if you have FIRST.ID, then you can assign directly the DATE and SALES variables to capture it without using MIN function. Also eliminates need to set high values and/or MISSING value. Honestly, you can accomplish this processing with PROC SUMMARY/MEANS -- have a look at the DOC. Scott Barry SBBWorks, Inc.

sbb · ‎06-16-2011

Okay - so it's a similar situation as your other post / thread at this link: http://support.sas.com/forums/thread.jspa?threadID=14667 Use a SAS DATA step to generate your "PROC PDS" procedure CHANGE statement parameters out to a FILENAME-allocated temporary file, and then %INCLUDE the "fileref". Note, the PROC PDS would execute after you execute the PROC PDSCOPY, since PDSCOPY does not support a similar CHANGE statement. Scott Barry SBBWorks, Inc.

sbb · ‎06-16-2011

Share what SAS code you have created thus far to solve the problem/objective. You should be using a RETAIN statement to capture / retain a "temporary date variable" and then on LAST. you will want to output. Otherwise why not use PROC SUMMARY/MEANS with the MIN function instead? Scott Barry SBBWorks, Inc.

sbb · ‎06-16-2011

What is meant by "automatically" -- you have a list of and member names in your post -- is that not what is available to your SAS application? If not and you want to "automate" (using SAS programming logic and your own naming methodology) the member names, then you can use the DATA step to create the value using SAS IF THEN ; statements, as required. Then with these values, you can generate the CHANGE statement parameters and output the information either to a SAS macro (mind the length limitation), or create a temporary sequential file and then use %INCLUDE (after a suitable FILENAME invocation for your file). Scott Barry SBBWorks, Inc.

sbb · ‎06-16-2011

Yes you can. To pass the selection criteria via a file, you would need to use %INCLUDE to reference an input file and code the statement between a SELECT statement and a trailing statement with a semi-colon, as in: FILENAME input "_your_input_selection_list" ; PROC PDSCOPY ....; SELECT %INCLUDE input; ; run; Scott Barry SBBWorks, Inc.

Online Status	Offline
Date Last Visited	‎12-27-2023 10:40 AM

Re: ODS to multiple destinations

Re: IF then statement

Re: SAS import file with text qualifier

Re: Create SAS users through Base SAS Program

Re: Create SAS users through Base SAS Program

Re: Create SAS users through Base SAS Program

Re: using %scan (maybe) to extract date from macro variable

Re: %include sas program in the same folder

Re: %include sas program in the same folder

Re: Using Task Scheduler to Run SAS

Create function %countw

Re: Z/OS SMS Compression with Zedc

Add other=_error_ for PROC FORMAT

Dataset Option: ReversedOrder

Set &SYSRC from FILENAME PIPE

Re: Changing the Column positions in SAS

Re: What does =: do?

SAS z/OS support for IBM z15 INTEGRATED ACCELERATOR FOR Z SORT

Re: Export data from dataset without formats?

Re: why cards statement inside a macro program generating error messag...

Converting Non-SAS Dates to SAS Dates

first.[variable], last.[variable] question

What is my macro missing?

SAS Script to edit sas programs in a library

Re: CALL SYMPUT not resolved

Re: Minus sign hex code?

Re: How to read in from an external data file

Re: Date conversion and trim function

Re: Splitting variable into multiple rows

Re: To rename the PDS members

Re: Max/Min date function on a variable

Re: To rename the PDS members

Re: Max/Min date function on a variable

Re: To rename the PDS members

Re: Help needed in PROC PDSCOPY