Hi Team, Can you please help me how to start the Lasr servers like Lasr Analytical server and Public  Lasr Analytical server.   and also find the Last action log of Lasr public:   can you please help me how to resolve this issue. Let me know if you need any more details.   Thanks For advance.       ... View more

Hi All, We are able to extract user, flowname, trigger,etc from below code. We are looking to extract email notification (when flow exit or start, etc) with email address and options . see below screenshot . Found below info in .dat files but not sure how to extract them and also options. 17 FlowStateMailWhen 4 Exit 10 FlowStderr 0   15 MailDestination 24 email.com 10 OEMAppName 3 SAS 11 OutputFiles         options linesize=180; ods graphics off; ods html close; ods listing; %macro flowdef; %let JSHOME=/sas/common/pm; %PUT JSHOME = "%trim(&JSHOME)"; %if %length(%trim(&JSHOME)) = 0 %then %do; %put %str(); %put ERROR: JS_HOME environment variable not available, exiting; data _null_; abort return 16; run; %end; %if &sysscp = WIN %then %do; filename events "%trim(&JSHOME)\work\system\triggerevents.dat"; filename flowdefs "%trim(&JSHOME)\work\storage\flow_storage\*.dat"; %end; %else %do; filename events "/sas/common/pm/work/system/triggerevents.dat"; filename flowdefs "/sas/common/pm/work/storage/flow_storage/*.dat"; %end; %mend; %flowdef; data triggers; infile events; length owner $ 16 flowname $ 32; input; * version info; input; * number of events; nevents = input(_infile_||" ",5.); drop nevents; do i=1 to nevents; input; * length of flow name; input; * flow name; owner = scan(_infile_,1,":"); flowname = scan(_infile_,2,":"); output; do until(_infile_ = "</List>"); input; end; end; run; filename events; data scheduled adhoc; length owner $ 16 flowname $ 32 event $ 14 jobname details $ 64 specifics $ 32 runas $ 32 eventtype $ 4 flowpart instance $ 8 removed $ 1 calendar calowner $ 32 timepart $ 65 nextrun $ 17 flowID $ 6; retain owner flowname eventtype flowpart instance removed flowID; drop calowner ; infile flowdefs; input; if _infile_ = '<JFFlow>' then do; jobname = " "; runas = " "; nextrun = " "; EventType = " "; FlowPart = " "; flowID = " "; /* Job File Flow definition found. Get FlowName, Owner, and Instance */ input; /* eat next line -- length */ input; /* should be username:flowname */ owner = scan(_infile_,1,':'); flowname = scan(_infile_,2,':'); input; /* eat next line -- length */ input; /* should be same as above with %%%%%## instance */ instance = scan(_infile_,2,'%'); input; /* eat next line -- length */ input; /* eat next line -- <List> token */ input; /* this is the number of Flow IDs that have run already */ nflows = input(_infile_||" ",3.); do i=1 to nflows; input; end; /* we are at the last run flow ID or the same 0 if none */ if nflows then flowID = _infile_; else flowID = " "; input; /* eat next line -- length */ input; /* eat next line -- </List> token */ input; /* This line is questionable. Empirical observation had found that if the character is "F" then the flow has NOT */ /* been "removed," so is still scheduled. Otherwise, if it is "T" it HAS been "removed" and is an AdHoc flow. */ /* However, more recent complex flow instances have cast a shadow of doubt onto this notion. Stay tuned.... */ removed = _infile_; /* Between the previous flow list and the next <List> are some things we can ignore (flow security, flow version) */ /* so just scan for the next List header -- this should be the list of flow triggers, file and/or time. */ do until (_infile_ = '<List>'); input; /* eat everything until list of flow triggers */ end; input; FlowPart = "Events"; ntriggers = input(_infile_||' ',5.); * if ntriggers = 0 then output; do i = 1 to ntriggers; do until (_infile_ = "<JFCalendarEventDef>" or _infile_ = "<JFFileEventDef>"); input; end; if _infile_ = "<JFFileEventDef>" then EventType = "File"; else EventType = "Time"; do until (_infile_ = "</JFEventDef>"); input; end; input; input; /* eat the length of the next token and then get the next token */ if EventType = "File" then do; event = "File Trigger: "; details = _infile_; specifics = " "; end; else if _infile_ = '<JFTimeInstance>' then do; /* Job File Trigger instance found. Get Calendar name and time */ input; /* eat next line -- length */ input; /* should be calendar:hh:mm%dur */ calendar = scan(_infile_,1,':'); timepart = scan(_infile_,2,':')||':'||scan(_infile_,3,':%'); input; /* eat next line -- length */ input; /* eat calendar name repeat */ input; /* eat next line -- length */ input; /* calendar owner */ calowner = tranwrd(_infile_,'DT_BS_','.\'); calendar = trim(calendar)||'@'||trim(calowner); event = "Time Trigger: "; details = trim(calendar) || " at " || trim(timepart); end; else do; put "ERROR: Invalid Flow Event Trigger type: " _infile_; put _all_; abort return 5; end; do until (_infile_ = "</RuntimeClass>"); input; end; link out; /* output information on each flow's trigger */ end; end; else if _infile_ = '<SubFlowEvents>' then do; do until (_infile_ = '<JFFlow>'); input; end; /* Job File SUB Flow definition found. Get SubFlow Name */ input; /* eat next line -- length */ input; /* should be username:flowname:subflow */ details = scan(_infile_,3,':'); specifics = " "; flowpart = "SubFlows"; event = "SubFlow : "; link out; /* Just eat everything until end of sub flow */ do until (_infile_ = '</SubFlowEvents>'); input; end; end; else if _infile_ = '</JFFlow>' then do; jobname = " "; runas = " "; nextrun = " "; EventType = " "; /* We are either at the end of a flow or at the end of all */ end; else if _infile_ = '<JFJob>' then do; input; /* eat next line -- length */ input; /* eat next line -- "lsf" or "link" */ if _infile_ = "link" then do until (_infile_ = '</JFJob>'); input; end; else do; FlowPart = "Jobs"; /* "lsf" Job Flow Job definition found */ input; /* eat next line -- length */ input; /* should be username:flowname:jobname{metaid} */ jobname = scan(_infile_,3,':{'); runas = owner; do until (_infile_ = '</JFJob>'); input; if _infile_ = 'SubmissionCmd' then do; input; /* eat next line -- length */ input; /* eat next line -- "bsub" */ input; /* eat next line -- length */ input; /* eat next line -- "UserName" */ input; /* eat next line -- length */ input; /* should be RunAs username */ runas = _infile_; end; end; /* Write out every job within a flow */ event = "Job: "; details = jobname; specifics = " "; if "&sysscp" = "WIN" or index(owner,"\") then iffy = lowcase(runas) ^= lowcase(owner); else iffy = runas ^= owner; if iffy then specifics = "Run As: " || trim(runas); link out; end; end; return; out: if removed = "T" or ntriggers = 0 then output adhoc; else output scheduled; return; run; filename flowdefs; proc sort data=scheduled; by owner flowname descending instance flowpart; run; data schedules; set scheduled; length firstinst $ 8; retain firstinst; by owner flowname descending instance flowpart; if first.flowname then firstinst = instance; if instance = firstinst; drop firstinst; run; /* Now remove flows that are not REALLY "scheduled" -- not found in triggers file */ proc sort data=triggers; by owner flowname; run; data schedules nonsched; merge triggers(in=scheduled) schedules; by owner flowname; if scheduled then output schedules; else output nonsched; run; proc sort data=schedules; by owner flowname flowID; run; proc sql; create table schedule as select * from work.schedules where event in ('Time Trigger:', 'File Trigger:') ; quit; proc sql; create table active_schedule as select owner, flowname, details as trigger_event, eventtype as trigger_type, flowid from schedule ; quit; ... View more

A new update is available for SAS Fraud Management , version 6.2 : Hot Fix: M9S007 - Published 04DEC2025 , Download link for M9S007 Component name: SAS Fraud Management Related SAS release: SAS 9.4   Issues addressed in M9S007 KB0041744 Login attempts to SAS® Fraud Management are suspended with a spinning progress icon KB0043636 You cannot save a grid template that contains more than 500 fields in SAS® Fraud Management KB0043638 SAS® Fraud Management contains an Insecure Direct Object Reference (IDOR) vulnerability KB0043639 You cannot prioritize more than 256 strategies or queues in SAS® Fraud Management KB0043640 "Failed to perform cache operation (cache is stopped)..." occurs in SAS® OnDemand Decision Engine KB0043642 "java.lang.OutOfMemoryError: Direct buffer memory" occurs in SAS® Fraud Management KB0043643 Transactions are not inserted into to the TDR in SAS® OnDemand Decision Engine after a "No more data to read from socket..." message occurs This list of notes might be incomplete. For a complete list of issues addressed by this hot fix, visit the hot fix page for M9S007   Note: A comprehensive list of all SAS hot fixes is available from support.sas.com. You can use the SAS Hot Fix Analysis, Download, and Deployment (SASHFADD) tool to manage your SAS hot fixes. ... View more

I support local installations of SAS Enterprise Guide 8.6 running with SAS 9.4M7. While the Check for Updates option under Help is useful, our IT department restricts local user IDs from writing to Program Files. I suspect this policy is common across many organizations. I’m exploring alternatives and would appreciate your input: • Silent install via Microsoft Software Center – I suspect this may be a viable option. • Requesting write access – Since I have admin rights on my PC, I could potentially request access to specific Program Files folders. After running Check for Updates, I confirmed that multiple files in Program Files\SASHome\SASEnterpriseGuide were updated. Are there other approaches you would recommend for managing updates in this environment? Thank you in advance for any suggestions. ... View more

Hello I run code that create data sets in following order. Why the data sets appear in different order then order they were created?     %let h1=2508; /**YYMM structure**/ %let h2=2507; %let h3=2506; %let h4=2505; %let h5=2504; %let h6=2503; %macro Help_Macro_a; %do j=2 %to 6; proc sql; create table _L_CS_&&h&j. as select b.lakoach_y as lakoach_Y&h1.,a.* from L_CS_&&h&j.(Rename=(lakoach_y=lakoach_y_&&h&j.)) as a inner join L_CS_&h1. as b on a.lakoach=b.lakoach ; quit; %end; %mend Help_Macro_a; %Help_Macro_a ... View more