Hi SAS folks,   I am trying to create a catalog (sas7bcat file) named "vdt_test" which shell have a compiled macro in it called "get_info". When running the following code: %LET PGname_in = getinfomacro; %LET PGNname_in_cat = get_info ; %LET catname = vdt_test; %LET entrytype = MACRO; libname _catloc base "/sas/sources/catalogs/"; filename inputPG "/tmp/&PGname_in..sas" ; data _null_; file inputPG; infile datalines delimiter="," truncover; length line $1000.; input line $; put _infile_; datalines4; %MACRO get_info(p_Env= ,p_Uname= ,p_Macvarname=) / SECURE STORE ; /* set scope for user-given macro variablen */ %IF %SYMEXIST(&p_Macvarname.) = 0 %THEN %DO; %GLOBAL &p_Macvarname; %END; %ELSE %DO; %PUT ERROR: Makrovariablenname "&p_Macvarname" bereits vergeben.; %END; %IF %UPCASE(&p_Env.) eq E %THEN %DO; %IF %UPCASE(&p_Uname.) eq SASBATCH %THEN %LET &p_Macvarname. = Tokenstring1; %IF %UPCASE(&p_Uname.) eq SASTOKEN %THEN %LET &p_Macvarname. = Tokenstring2; %END; %IF %UPCASE(&p_Env.) eq T %THEN %DO; %IF %UPCASE(&p_Uname.) eq SASBATCH %THEN %LET &p_Macvarname. = Tokenstring3; %IF %UPCASE(&p_Uname.) eq SASTOKEN %THEN %LET &p_Macvarname. = Tokenstring4; %END; %IF %UPCASE(&p_Env.) eq P %THEN %DO; %IF %UPCASE(&p_Uname.) eq SASBATCH %THEN %LET &p_Macvarname. = Tokenstring5; %IF %UPCASE(&p_Uname.) eq SASTOKEN %THEN %LET &p_Macvarname. = Tokenstring6; %END; %IF %UPCASE(&p_Env.) eq AD %THEN %DO; %IF %UPCASE(&p_Uname.) eq %STR($SASBATCH) %THEN %LET &p_Macvarname. = Tokenstring7; %END; %MEND; ;;;; run; data _null_ ; filename mycat catalog "_catloc.&catname." lrecl= 256 ; file mycat("&PGNname_in_cat..&entrytype.") ; infile inputPG; input ; put _infile_ ; run ; proc catalog CATALOG= _catloc.&catname. ; contents ; run; quit ;   I get this ERROR message: ERROR: Output mode is only supported for catalog entry types of SOURCE, LOG, OUTPUT, HTML, JPEG, GIF, CSS, WML, XML, XSL, RTF, PDF, PS, CSV, JS, VBS, JAR, CATAMS, HPFPROJ, HPFDATA, HPFEVENT, HPFDIAG, HPFSPEC, HPFLIST, HPFSCORE, PNG, and HPF1-HPF10. Here is my question: why the heck is it not possible to name a catalog which contains a compiled macro other than "SASMACR", which is the name given automatically by the system when just running the "%MACRO" step with the options "store" and "secure"?   Any help would be highly appreaciated, FK21 ... View more

Hello, first of all: I know this might not be the best forum to place this question, but I did not find a more appropiate one. So, if one of the admins knows, where to post this question, feel free to move it. Now, having said, this my question is as follows: Is it possibl to set a sort of parameter in Data Integration Studio (4.906 under SAS 9.4M8) which forces users to check out an obect, before they are able to alter/modify it?   I stumbled upon the fact, that you can alter any given object (e.g. a Job) without having to check it out in the first place! This can lead to missing audit trails. In case of using the check-in/check-out facility, you would be able to view the the (modification)history of a Job (right click on the job, then choos "History"). For example: I created a job, "LS_KFZ_00_BESTAND_SCHADEN_REMOVE_CURRENT_MONTH".  Then, I DID NOT check it out and went on to chang the content of the job by adding several transformations and removing others in the job. After I saved it, I got the following result: I only see the "creation" of the job in the history:    So my qustion is: how can I prevent users from modifying jobs or other metadata objects, which are in the realm of DIS, if they are not properly checked out?     ... View more