BookmarkSubscribeRSS Feed
sathya66
Barite | Level 11

All,
we have removed the flow(AP_000_test) from flow manager but flow instance still exists. We have unscheduled and deleted the flow from SMC too
Ex:
-rw-r--r--. 1 lsf Domain Users 46K Feb 10 12:20 lsfuser:AP_000_test%%%%%2045.dat
-rw-r--r--. 1 lsf Domain Users 46K Feb 10 12:20 lsfuser:AP_000_test%%%%%2085.dat

/<home>/pm/work/storage/flow_storage

Every time we re-schedule/schedule same flow , it is creating multiple instances of the same flow with diffrent ID on the server . how can we keep only one latest version of the flow instance in the flow storage folder?

Ex: from
-rw-r--r--. 1 lsf Domain Users 3.2K Jul 29 2021 lsfuser:CUST_TEST_day%%%%%2361.dat
-rw-r--r--. 1 lsf Domain Users 3.7K Jul 29 2021 lsfuser:CUST_TEST_day%%%%%2363.dat
-rw-r--r--. 1 lsf Domain Users 4.0K Oct 27 16:10 lsfuser:CUST_TEST_day%%%%%2359.dat
-rw-r--r--. 1 lsf Domain Users 4.0K Oct 27 17:10 lsfuser:CUST_TEST_day%%%%%2362.dat
-rw-r--r--. 1 lsf Domain Users 4.5K Nov 2 09:06 lsfuser:CUST_TEST_day%%%%%2364.dat
-rw-r--r--. 1 lsf Domain Users 3.3K Nov 3 21:09 lsfuser:CUST_TEST_day%%%%%2389.dat
-rw-r--r--. 1 lsf Domain Users 3.3K Nov 11 17:44 lsfuser:CUST_TEST_day%%%%%2398.dat
-rw-r--r--. 1 lsf Domain Users 3.3K Nov 16 09:26 lsfuser:CUST_TEST_day%%%%%2427.dat
-rw-r--r--. 1 lsf Domain Users 3.3K Nov 16 11:26 lsfuser:CUST_TEST_day%%%%%2439.dat
-rw-r--r--. 1 lsf Domain Users 46K Feb 10 12:20 lsfuser:CUST_TEST_day%%%%%2441.dat

 

 

to
-rw-r--r--. 1 lsf Domain Users 46K Feb 10 12:20 lsfuser:CUST_TEST_day%%%%%2441.dat

 

 

Thanks

SS

5 REPLIES 5
gwootton
SAS Super FREQ
You may want to look at the JS_IM_ACTIVEPOLICY setting and it's associated options in js.conf if you want these to be cleared out based on time (JF_IM_TPolicy) instead of number of instances (JF_IM_IPolicy, the default).

js.conf
https://www.ibm.com/docs/en/slpm/10.2.0?topic=files-jsconf

Process Manager stores these files for historical record purposes. These are related to files in work/storage/flow_instance_storage. So the flow definition info is in storage/flow_storage and then the info on each run is in storage/flow_instance_storage/finished, but the detail in those files references back to flow_storage names. The note below from IBM describes how to remove these files for a given user. If you wanted to remove this history manually you would similarly need to stop process manager, identify the files you want to remove in flow_storage and their associated files in flow_instance_storage/finished and backup then remove them, backup and remove the cache file and then start Process Manager again.

How to clean flow instances from Flow Manager
https://www.ibm.com/support/pages/how-clean-flow-instances-flow-manager

File Structure
https://www.ibm.com/docs/en/slpm/10.2.0?topic=files-file-structure#concept_xww_hdx_h4
--
Greg Wootton | Principal Systems Technical Support Engineer
sathya66
Barite | Level 11
Thanks ,
and also we deleted two calendar but we are getting below errors when we resart jfd. is there a way we can tidy up these.


2022 Feb 14 11:40:14 93953 93953 4 JFCalendarCache::addCalendar: Parse error -- calendar invalid/non-exist <CM_CAL_____71@Sys>.
2022 Feb 14 11:40:14 93953 93953 4 JFCalendarCache::buildCache: Failed to find the calendar CM_CAL@lsfuser.
2022 Feb 14 11:40:14 93953 93953 4 JFCalendarCache::addCalendar: Parse error -- calendar invalid/non-exist <CM_programme_____49@Sys>.
2022 Feb 14 11:40:14 93953 93953 4 JFCalendarCache::buildCache: Failed to find the calendar CM_programme@lsfuser.
2022 Feb 14 11:40:14 93953 93953 5 Starting Recovery (10 Steps in Total).


gwootton
SAS Super FREQ
Did you use the Calendar Editor to delete the calendars?
--
Greg Wootton | Principal Systems Technical Support Engineer
sathya66
Barite | Level 11

yes, for some reason, we are getting this.

gwootton
SAS Super FREQ
It sounds like they are still in use, maybe you have other calendars based on these? If you grep the files in work/calendar and work/storage/flow_instance for those calendar names do you see any results?
--
Greg Wootton | Principal Systems Technical Support Engineer

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 5 replies
  • 940 views
  • 2 likes
  • 2 in conversation