We pipe the results of a jhist command to a file then parse the results into a SAS table.  Like Greg mentioned, there are commands to get just jobs or flow info.  jhist will return historical information about Process Manager Server, calendars, flow definitions, flows, and jobs.  We leverage -C to filter the results to just 'job,flow' then using a -t we can get results just for the time window from our last processing time.  Then using SAS Visual Analytics we provide insight into the processes running through the scheduler.   - Brandon Kirk | Sr Manager, IT Software Development   ... View more

EDIT:  Just read you were using a different scheduler.  Well this is the syntax we use for the LSF Platform scheduler.  During our initialization of the LASR servers we evaluate if the servers started and if they did we kick of a .ksh which includes this info: #!/bin/ksh # Will source a batch version of PM profile # and kick off the main flow for LASR table reload . /<insert your path>/pm/conf/profile.js jtrigger _LASR_LOAD_ALL Also sounds like we have similar methodology so here are a couple of our published papers. http://support.sas.com/resources/papers/proceedings15/SAS1952-2015.pdf http://support.sas.com/resources/papers/proceedings15/SAS1890-2015.pdf http://support.sas.com/resources/papers/proceedings16/SAS6660-2016.pdf Hope that helps. ... View more

Ricky,   I work at SAS in IT supporting the VA environment we run internally.  Welcome to the SAS community.  The path you are headed is exactly like the setup we have employed.  We have seperated Hadoop loads and LASR loads then combined them into scheduled flows for regularly refreshing data.  The trick we crated is to take all the LASR flows/jobs and include them into one large flow "ie. Load all to LASR".  That flow is triggered via command on restart.  If this sounds like an option for you I can share the syntax we are using to trigger a flow in LSF Platform Scheduler.  Probably could be adapted for any scheduler.   Brandon    ... View more