topic Re: minor usage issue in SAS Programming

minor usage issue

me55 — Wed, 02 Dec 2020 18:30:41 GMT

i am trying to build a process that uses last months file to create this months file. for some reason my variable in proc copy is not working. the error i get is...

560 proc copy in=LIB03 out=WORK;
561 select FILE_&l2numshortdate.dbf;
_
22
200
WARNING: Apparent symbolic reference L2NUMSHORTDATE not resolved.
ERROR 22-322: Syntax error, expecting one of the following: a name, ;, (, -, /, :.
ERROR 200-322: The symbol is not recognized and will be ignored.
562 run;

i cannot figure it out. i am certain i have used very similar code before but it is not working here...code below...

data _null1_;
td00=today();
td01=intnx('month',today(),-5);
td02=intnx('month',today(),-6);
td03=intnx('month',today(),-7);
ytrd00=put(td00,YYMMN.);
ytrd01=put(td01,YYMMN.);
ytrd02=put(td02,YYMMN.);
ytrd03=put(td03,YYMMN.);
ytrd04=put(td04,YYMMN.);
call symput('l0numshortdate',ytrd00);
call symput('l1numshortdate',ytrd01);
call symput('l2numshortdate',ytrd02);
call symput('l3numshortdate',ytrd03);
run;

LIBNAME LIB01 '/sas/loc_01/files/';
LIBNAME LIB02 '/sas/loc_02/files/';

proc copy in=LIB01 out=WORK;
select ARCHIVE;
run;

proc copy in=LIB02 out=WORK;
select FILE_&l2numshortdate.dbf;
run;

the first proc copy is running but the second fails at the &...

Re: minor usage issue

PaigeMiller — Wed, 02 Dec 2020 18:45:20 GMT

Please do not show us portions of the log separated from the code. Please do show us the ENTIRE log for this sequence of code, with nothing chopped out, 100% of it, the CODE as it appears in the log, the NOTEs, the ERRORs, the WARNINGs, all of the log for this sequence of code.

Please copy the log as text and paste it into the window that appears when you click on the </> icon. DO NOT SKIP THIS STEP. This preserves the formatting and makes the log more readable and more usable.

Re: minor usage issue

AMSAS — Wed, 02 Dec 2020 19:02:15 GMT

Add the following at the top of the code, re-run, check the log and post the log to this thread

options mprint symbolgen mlogic;

Re: minor usage issue

r_behata — Wed, 02 Dec 2020 19:15:56 GMT

Looks like you are missing a '.' to separator.

proc copy in=LIB03 out=WORK;
    select FILE_&l2numshortdate..dbf;
 run;

Re: minor usage issue

ballardw — Wed, 02 Dec 2020 19:28:30 GMT

561 select FILE_&l2numshortdate.dbf;
_
22
200
WARNING: Apparent symbolic reference L2NUMSHORTDATE not resolved.

So, where do you define a macro variable named "l2numshortdate"? That error means that you have not created the macro variable, or attempted to and failed.

Also, the . is used as an end of macro variable marker. If the file that you expect to use needs a period after a macro variable you need to double them up. Please run the following code and read the log.

%let macrovar = Sometext;

%put Without two dots: &macrovar.dbf;
%put With two dots: &macrovar..dbf;

Please when posting copied text from the log paste it into a code box opened using the </> icon on the forum. That will preserve the formatting of the text making it easier to read and keep the locations of any diagnostic characters provided by SAS in the correct place relative to the code.

Re: minor usage issue

andreas_lds — Thu, 03 Dec 2020 06:21:10 GMT

@r_behata wrote:

Looks like you are missing a '.' to separator.
proc copy in=LIB03 out=WORK;
    select FILE_&l2numshortdate..dbf;
 run;

No, not in this case. With the extra dot an illegal dataset-name would be the result.

Re: minor usage issue

me55 — Thu, 03 Dec 2020 14:21:24 GMT

yeah, what they said below...

Re: minor usage issue

me55 — Thu, 03 Dec 2020 14:22:05 GMT

yeah, i tried it with and without the double dots and neither worked.

Re: minor usage issue

me55 — Thu, 03 Dec 2020 14:29:24 GMT

yeah, that changed nothing...

Re: minor usage issue

Kurt_Bremser — Thu, 03 Dec 2020 14:50:28 GMT

Combine your code that sets the macro variable with the PROC COPY code, and use the option

options mprint mlogic symbolgen;

%let .....

proc copy .....

and then post the complete log from that into a window opened with the </> button.

Re: minor usage issue

me55 — Thu, 03 Dec 2020 15:14:51 GMT

this is multiple issues...the first was, i had to change the program location of the variables. when i added the variables to the process flow in the correct spot in the project tree window, that did not change the order when they are run so when i added the new program, it added to the end of the process flow and so that is why it was not resolving.

so, i corrected that and now i am getting a new issue which i dont really understand. so...

variable definition...

data _null1_;
	options mprint symbolgen mlogic;
	td00=today();
  	td01=intnx('month',today(),-5);
  	td02=intnx('month',today(),-6);
	td03=intnx('month',today(),-7);
	ytrd00=put(td00,YYMMN.);
	ytrd01=put(td01,YYMMN.);
	ytrd02=put(td02,YYMMN.);
	ytrd03=put(td03,YYMMN.);
	ytrd04=put(td04,YYMMN.);
	call symput('l0numshortdate',ytrd00);
	call symput('l1numshortdate',ytrd01);
	call symput('l2numshortdate',ytrd02);
	call symput('l3numshortdate',ytrd03);
run;

code to run it...

LIBNAME LIB01 '/loc_01/';
LIBNAME LIB02 '/loc_02/';

proc copy in=LIB01 out=WORK;
	select FILE_ARCHIVE;
run;

%let FILEA_file=FILEA_&l2numshortdate..dbf;

proc copy in=LIB02 out=WORK;
	select &FILEA_file;
run;

resulting error...

25         GOPTIONS ACCESSIBLE;
SYMBOLGEN:  Macro variable L2NUMSHORTDATE resolves to 202006
26         
27         %let FILEA_file=FILEA_&l2numshortdate..dbf;
28         
29        


30         proc copy in=LIB02 out=WORK;
31         	
SYMBOLGEN:  Macro variable FILEA_FILE resolves to FILEA_202006.dbf
31       !  select &FILEA_file;
NOTE: Line generated by the macro variable "FILEA_FILE".
31          FILEA_202006.dbf
            _______________
            22
            201
ERROR 22-322: Expecting a name.  
ERROR 201-322: The option is not recognized and will be ignored.
32         run;

what am i missing here? i tried putting the variable inside the proc copy and as a macro and i keep getting the same error.

Re: minor usage issue

Tom — Thu, 03 Dec 2020 15:30:29 GMT

You are using PROC COPY. So the names you want to list in the SELECT statement are the names of MEMBERS of the LIBREF listed in the IN= option. Member names do NOT contain special characters like periods.

What are you trying to do?

Why are you sticking DBF extension onto the member name here?

What members exist in LIB02?

Run PROC CONTENTS to see what is there.

proc contents data=lib02._all_; run;

Re: minor usage issue

me55 — Thu, 03 Dec 2020 15:34:36 GMT

i am trying to copy a file that ends with a date. so it is FILE_YYYYMM from its home which is LIB02 to my work directory. i will not hard code the date and since this same format has worked in many other instances, i figured it would work here. the file is a dbf, that is why i am putting the dbf extension on there.

Re: minor usage issue

Kurt_Bremser — Thu, 03 Dec 2020 15:41:20 GMT

PROC COPY is for SAS files (datasets, views, catalogs); A .dbf (dBase) is NOT a SAS file, it is an external file.

Re: minor usage issue

me55 — Thu, 03 Dec 2020 16:17:46 GMT

well, i solved my own problem. i had to wo that issue...

Re: minor usage issue

PaigeMiller — Thu, 03 Dec 2020 16:25:57 GMT

@me55

Please tell us what the solution was.

Re: minor usage issue

me55 — Thu, 03 Dec 2020 19:40:13 GMT

i realized that copying the table would be the same essentially as importing the table so if copy couldnt handle it, import proabably would...so, i imported the table from another directory into the work directory.