Internal Macro %MDSECDS ();

[dafata39]

Hi everyone

Thanks foy your suport, i tried run this code:

options    metaserver="server.com"
                metaport=8561
                metauser="sasadm@saspw"
                metapass="****************"
                metaprotocol=BRIDGE
                metarepository=Foundation;

libname  sasti '/tmp';
%mduextr(libref=sasti);
%mdsecds ();

Log:

ERROR: Physical file does not exist, /saswork10/SAS_workF9500000EE8D_server.com/#LN00048.
ERROR: Encountered during XMLInput parsing at or near line 1, column 1.
ERROR: The definition for the "FOLDERS" table is not well-formed or is corrupt

I attach an image of what space / saswork10 is if it exists

Thanks, I read them.

[Tom]

I haven't the foggiest idea what those macros are supposed to do, but that error messages makes it look like the macro is trying to read from a temporary fileref, but nothing was ever written to the temporary fileref.

When you use the syntax:

filename XXX temp;

SAS will define a fileref of XXX that points to a file in the WORK directory.  The name part of the file follows that #LN99999 pattern in your error message.

So whatever step earlier in the macro that was supposed to write something to the file didn't. So the step that then reads from the file generates the error message you quoted.

Search higher in your SAS log for the real issue.

[dafata39]

Thanks,

I tried change work to sasti in the code but the error continues.

libname  sasti '/sasdataTI/reportes/';
%mduextr(libref=sasti);

By the way, %MDSECDS Security Report Macro: Generates authorization data sets. This is the top-level macro (it calls the underlying macros and should be used on its own).

Documentation Link 

[dafata39]

Really the problem is being generated by the macro %mdsecds();

This is the code.

options      metaserver="server.com"
	metaport=8561
	metauser="sasadm@saspw"
	metapass="************"
	metaprotocol=BRIDGE
	metarepository=Foundation;

%mdsecds();

Thanks

[SASKiwi]

These macros are supplied by SAS so Tech Support is your best option for fixing these errors.