topic Re: File path error given using X Command in SAS Programming

File path error given using X Command

OGA13 — Mon, 25 Nov 2024 10:15:01 GMT

I'm trying to fetch files and put them in a single sas file using X Command.

The error is given because in the file path there is a space.

How can I fix it?

data helper;
    length Module $50 Function $100;
    set helper;
    Module = "HELPER";
	Path = "V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\"||strip(Module)|| "\" || strip(Function) || ".sas";
run;

proc print data=helper;
run;


%macro fetch_files(module=, output=);
	data _null_;
	    set &module end=last;
	    /* Construct the copy command */
	    if _n_ = 1 then call execute('X "copy ');

	    call execute('"', Path, '" + ');

	    /* Finalize the command when the last file is processed */
	    if last then call execute('"&output"');
	run;
%mend ; 


 %fetch_files(module=helper, output=helper.sas);

Re: File path error given using X Command

Patrick — Mon, 25 Nov 2024 11:04:30 GMT

Then wrap the path or at least the portion with the blank in it into double quotes.

data helper;
  length Module $50 Function $100;
  set helper;
  Module = "HELPER";
/*Path =          "V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\"||strip(Module)|| "\" || strip(Function) || ".sas";      */
  Path = cats('"',"V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\",       Module ,  "\",         Function,    ".sas",'"');
run;

Re: File path error given using X Command

PaigeMiller — Mon, 25 Nov 2024 11:04:38 GMT

@OGA13 wrote:

I'm trying to fetch files and put them in a single sas file using X Command.

The error is given because in the file path there is a space.

How can I fix it?

Show us the log.

Is the error because of the space after 05. ?? Or is the error somewhere else?

If you look in data set PATH, do you see an unnecessary space in variable PATH? If so, where is it?

Re: File path error given using X Command

OGA13 — Mon, 25 Nov 2024 11:27:47 GMT

It seems that your suggestion fix the issue. But still, when I run the macro I don't see the desired file generated.
I'm sharing the LOG.

MLOGIC(FETCH_FILES):  Beginning execution.
MLOGIC(FETCH_FILES):  Parameter MODULE has value helper
MLOGIC(FETCH_FILES):  Parameter OUTPUT has value helper.sas
MPRINT(FETCH_FILES):   data _null_;
MPRINT(FETCH_FILES):   set helper end=last;
MPRINT(FETCH_FILES):   if _n_ = 1 then call execute('X "copy ');
MPRINT(FETCH_FILES):   call execute(cats('"', Path, '" + '));
MPRINT(FETCH_FILES):   if last then call execute(cats('"', Path, '"','" &output"'));
MPRINT(FETCH_FILES):   run;

NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.
NOTE: There were 11 observations read from the data set WORK.HELPER.
NOTE: DATA statement used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds


NOTE: Line generated by the CALL EXECUTE routine.
2     + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\APPEND_GMAP.sas"" +
        --
        49
NOTE: Line generated by the CALL EXECUTE routine.
3     + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\APPLY_VAR_TYPE.sas"" +
        --
        49
NOTE: Line generated by the CALL EXECUTE routine.
4     + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\ASSIGN_RECORDID.sas"" +
        --
        49
NOTE: Line generated by the CALL EXECUTE routine.
5     + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\CREATE_HORIZON_TEMPLATE.sas"" +
        --
        49
NOTE: Line generated by the CALL EXECUTE routine.
6     + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\LOG_BACKUP.sas"" +
        --
        49
NOTE: Line generated by the CALL EXECUTE routine.
7     + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\LST_BACKUP.sas"" +
        --
        49
NOTE: Line generated by the CALL EXECUTE routine.
8     + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\MASTER_FORMOID.sas"" +
        --
        49
NOTE: Line generated by the CALL EXECUTE routine.
9     + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\POST_DOMAIN.sas"" +
        --
        49
NOTE: Line generated by the CALL EXECUTE routine.
10    + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\REFRESH_FROM_PILOT.sas"" +
        --
        49
NOTE: Line generated by the CALL EXECUTE routine.
11    + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\RENAME_SPEC.sas"" +
        --
        49
NOTE: Line generated by the CALL EXECUTE routine.
12    + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\REPORT_LOGMSG.sas"" +
        --
        49
NOTE: Line generated by the CALL EXECUTE routine.
13    + ""V:\Projects\BOE\_BI\Consulting\05. System\Macros\Horizon\HELPER\REPORT_LOGMSG.sas""" helper.sas"
        --
        49
MLOGIC(FETCH_FILES):  Ending execution.
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release.  Inserting white space between a quoted string
             and the succeeding identifier is recommended.

Re: File path error given using X Command

OGA13 — Mon, 25 Nov 2024 11:31:19 GMT

Yes, the error is gaven by the space after "05.". However, even with the correct path I still don't get any generated SAS file.

Re: File path error given using X Command

yabwon — Mon, 25 Nov 2024 11:33:01 GMT

1) do not use X for the job.

2) if you have multiple files you want to copy to a single .sas file and all of then are in one directory you can do it like this:

/* create some text files */
filename f "R:\test\";

data _null_;
file f(a.sas);
put "data _null_; run;";

file f(b.sas);
put "proc print data=sashelp.class; run;";

file f(c.sas);
put '%macro test(n); %do i = 1 to &n.; %put &=i.; %end; %mend;';

file f(d.sas);
put '%test(42)';
put "data _null_; run;";
run;

/* get them all into one file */
filename in_list "R:\test\*.sas";
filename out "R:\out\allInOne.sas";

data _null_;
  infile in_list;
    file out;
  input;
    put _infile_;
run;

Bart