We have a flow that consists of multiple sub-flows. Today we were faced with an error situation in sub-flow 1 indicating a table was locked by a job from sub-flow 2. This sort of took us by surprise.   When we checked the SMC we noticed the following settings in the Attributes tab in the Properties: SMC Attributes 1               SMC Attributes 2 When we checked the Completion Attributes for the same flow in FlowManager we noticed the following settings: FlowManager Attributes 1                     FlowManager Attributes 2 What we understand from these settings and what we have seen today is the following: That the flow criteria completion was met when a warning occurred in the first job of sub-flow 1. The setting in FlowManager ("Change the flow state immediately and continue running the flow") The immediate change of the flow state resulted in sub-flow 2 to start running but at the same time also the second job in sub-flow 1 started. Both use the same file causing the entire flow to fail on a file lock. This is how we understand that the error was caused.   What we do not understand why in FlowManager the setting from SMC ("Complete any work in progress and stop running the flow") has not been taken over from the SMC.   Has anyone noticed this before and if so, any suggestions on how we can get FlowManager to have the same settings as SMC? NOTE: We have tried unscheduling and rescheduling the flow but that did not help.   ... View more

First a small disclaimer: I am asking this question as a statistical noob on behalf of a custormer of ours.  We are running SAS 9.4 M3 (SAS/ETS 14.1)   The customer runs various fit analysis using PROC MODEL and one of the graphs that is being generated is the Cook's D graph The question of the customer is: can I get the data that is being used to generate the Cook's D graph in an output dataset and link this back to my source data so I can filter outliers?   By using the ODS TRACE statement I have been able to derive - I think - the base data that is being used. The code I have used (hopefully as a representative example) is: ods trace on; proc model data=sashelp.citimon; lhur = 1/(a * ip + b) + c; fit lhur; id date; run; ods trace off; Attached a sample of part the output that is generated, specifically Panel 1 that contains the Cook's D graph. Comparing the output in the log against the output my assumption is that the base data for the graphs can be obtained by adding the following statement just before the PROC MODEL statement: ods output DiagnosticsPanel=work.panel; However, it seems as if the dataset contains all the data (the dataset contains 36 variables) that is needed to create the graphs in Panel 1 (and 2?) and I could find no way to relate the data back to the source data. I was hoping that adding the option PLOT(ONLY)=COOKSD would reduce the number of variables in the output dataset but it - as maybe could be expected - only reduced the number of graphs.   Hopefully someone can shed some light on this and help me help our customer. TIA       ... View more