The SAS LABEL will need to be resolved with a double-quoted macro variable reference.  And you can use PROC SQL to select the SAS variable's data-value(s) into a SAS macro variable (for example, call it macro variable PERIOD) in a step ahead of the DATA / PROC step that sets the SAS statement, for illustration: LABEL <myvar> = "Current Period (&period)"; Check the SAS PROC SQL DOC and SAS.COM resources for using INTO with SELECT <varname>  -- to create the SAS macro variable needed to resolve the various labels accurately. Note that this can also be done in a preceding DATA step that reads the input file, with SET <filename> ( KEEP=<myvar>) END=EOF;   and then upon IF EOF THEN DO;  * SAS code;  END;  to issue CALL SYMPUT with a formatted SAS date variable to resolve the SAS macro variable. ... View more

The final syntax must have double-quotes surrounding your EMAIL address, whether you generate that in the PROC SQL or hardcode it in the TO= ( .... ) parameter surround your macro variable resolved EMAIL address(es).  The error is due to the TO= lacking double-quotes surrounding each address and if you intend to code multiple addresses, the entire TO=(....)    must be surrounded with parentheses. ... View more

What is the exact SAS error received?  My attempt resolved the quote / double-quote correctly and the EMAIL was generated as expected.  Suggest you post the exact SAS code piece in its entirety and the SASLOG error diagnostics. ... View more

Suggest using a DATA step where SAS assignment statements use the ANYDIGIT along with a H_xxxx (hold variable) for your conditional assignment. What is unspecified here is whether your objective is on an SAS observation level basis or if only one occurrence is different, then switch all observations -- there you might consider a DATA step to test values, then a conditional PROC DATASETS to effect a change on the entire dataset. 35758 - New "ANY" functions in SAS® 9 and later releases can search for various types of characters in a string Scott Barry SBBWorks, Inc. ... View more

Suggest the task be broken down into smaller subtask objectives, and explore these SAS programming techniques to achieve your task's overall objective: 1) SAS SORT for ordering observations in advance of #2 below. 2) SAS DATA step with SET / BY processing to identify FIRST.<break_variable> and LAST.<break_variable> processing, where needed. 3) enhanced diagnostic SASLOG output by using PUTLOG _ALL_;  which helps by revealing the FIRST. and LAST. conditions based on the DATA step BY variable list. 4) possibly consider the DATA step LAG function for capturing prior observation SAS variable values; also RETAIN statement for retaining values across DATA step execution iterations. Scott Barry SBBWorks, Inc. ... View more

From your SAS code piece, file WORK.TABLERANGES is sourced from a DATA step that inputs with a SET dates_info ab;  specified.  Neither of those two files has a SAS variable with the name you are getting for the SAS ERROR. ... View more

Help clarify here please (best to reveal more of your SAS code, including the PROC PRINTTO statement(s) please) - you have a z/OS MVS TSO user running interactive SAS and when the SAS session is immediately started, a PROC PRINTTO PRINT FILE=xxxxx (where "xxxxx" is a pre-allocated SYSOUT= destination?)  is issued, followed by a DATA step that issues some PUT references against FILE PRINT, and eventually a RUN;  and a PROC PRINTTO to reset the output re-direct -- is that the case here?  Consider helping us help you will the encapsulated SAS program to start, along with some confirmation about observations / presumptions above? ... View more