Hi @Yura2301    The problem is that you are using the wrong command. If the flow is submitted to Process Manager in SAS MC / Schedule Manager, the flow definition is stored in Process Manager's Flow Storage folder, and you can see it in the Flow Manager and run it from there. You can also run it from a command line using the Jtrigger command instead of Jrun, which requires an external flow definition file. https://www.ibm.com/docs/en/slpm/10.2.0?topic=commands-jtrigger   We use the Jtrigger command to run all flows (700+) in our daily batch, and all flows are scheduled with 'Manually to the scheduling server' as trigger, so they never run unless triggered by Jtrigger or mun manually from Flow manager. We have built a scheduler that establish flow order based om metadata registrations of jobs with input and output tables and trigger flows when all preceding flows in a chain have status Done.       ... View more

OK, I admit this is a pretty ancient thread but I've just had an issue with damaged datasets on a server that ran out of diskspace.  I've been trying to answer a very similar question - How can you test programmatically if a dataset is damaged and was surprised how little information there is out there.   My solution is to use the open() function and then check the sysmsg() for the word 'damaged'.   The open() function does not automatically put an error into the log (it puts a note), which meets the original requirement. Here's the macro I've knocked up.  I've chosen to output the sysmsg() so I get the error, but it could be done silently.  Not sure I want to attempt to repair everything so I've made that optional and I'll probably scan first to see what it finds.  Ideally it would record if a repair was successful - not sure if you can get the success of the repair from proc datasets, sysrc may be useful but the definition of 'successful' is open to interpretation - for instance most of the repairs I've seen indicate some data loss.   %macro checkAndRepair(dsn, repair=N); %local dsid msg; %if %sysfunc(exist(&dsn.)) = 0 %then %put WARNING: &dsn does not exist.; %else %do; %let dsid=%sysfunc(open(&dsn.,i,,D)); %if (&dsid=0) %then %do; %let msg=%sysfunc(sysmsg()); %put &msg.; %if %index(&msg.,damaged) gt 0 %then %do; %if &repair. = Y %then %do; %put Attempting to fix...; proc datasets nolist lib=%scan(&dsn,1,.); repair %scan(&dsn,2,.); quit; %end; %end; %end; %else %put NOTE: &dsn. opened succesfully.; %let dsid=%sysfunc(close(&dsid)); %end; %mend;     ... View more

You can compare all columns and all rows in one go if you hash all the fields as shown. And if you can easily sort the tables if needed on that one field. ... View more

Hi Quentin I'd like to look at your blog post but it looks like it's been taken down, can you link me to where it is currently please if it still exists? Thanks! ... View more

@Yura2301 - I also had this problem, but in fact - the command CAN be longer than 8191 characters, it's just that for some reason WINDOWS will remove a single character.    Weird - I know.   I created a workaround for this and posted it here:  https://stackoverflow.com/questions/30592523/sas-exportpackage-command-exceeds-8191-characters   Essentially you have to insert a dummy character at the 8191 position. ... View more

hi. the folder path is : sas\config\lev1\applications\sascustomerintelligence\campaignmanagement\data\matables   hope its helps. ... View more

Hi Patrik, Yes, but archiving process can fail for a some reasons, so just run 7z.exe with needed parameters probably a little bit unsecure. I used smth like: Set objectShell   = CreateObject("WScript.Shell") retVal = objectShell.Run(...) If retVal <> 0 Then ' write to log worning that archivation failed      Else ... ... View more

PROC SQL noprint ; select var into :macvar separated by '0A'x from that small.table is how I would collect the values Use it where-ever like    "&macvar" Perhaps as the label for the column ... View more

Small addition: Partly solved the issue by adding folders ,except root, to the command line,like that: ExportPackage -profile "profName" -package "c:\Documents and Settings\...\test.spk" -types Folder -excludeSubTypes -objects "/folder1(Folder)" -objects "/folder1/folder2(Folder)" ... "/sasproject/.../tablename2(Table)" -objects "/sasproject/.../tablename1(Table)" "/sasproject/.../tablename2(Table)" -types Table –excludeSubTypes -log "c:\Documents and Settings\...\test_log.log" Thats partly solved the issue but require from me to make additional code, that will parse fill path and put -object command for each folder connected to each job/table.Suppose should be some more clever solution, more quick and reliable. Maybe some option or smth. like that. Thanks! ... View more