04-04-2017 12:38 PM
In Platform Process Manager I have a flow instance where all the jobs have completed, but the flow is still in running state. I think maybe jfd was being restarted when it completed (not certain about that).
I have tried the following to move it into exit or done state:
The .dat file is in .../work/storage/flow_instance_storage/finished, not in equivalent ‘active’ directory.
Here is the output from jflows <flowid> command, notice the end time is after the start time…
STATE START TIME END TIME
Running Mon Mar 27 10:06:26 GMT+01:00 2017 Fri Mar 24 20:38:58 GMT+01:00 2017
CURRENTLY-USED VERSION: 1.0
NAME TYPE STATE JOBID
<removed> Job Done 646059
<removed> Job Exit 684169
<removed> Job Done 645871
<removed> Job Done 645879
<removed> Job Done 645872
<removed> Job Done 645878
<removed> Job Done 645873
<removed> Job Done 645883
<removed> Job Done 646085
<removed> Job Done 648037
<removed> Job Done 645875
<removed> Job Done 645884
How can I remove this flow from running state?
04-10-2017 09:25 AM
Thank you for opening a track with SAS Technical Support. We will be continuing to work with you to debug and resolve this issue.
For those following this thread, a resolution will be posted once an answer is found.
04-13-2017 04:29 PM
In this situation with Platform Process Manager 8.1.239197, there are IBM patches that should resolve the issue. Before applying patches, issue the following command to double check that patches aren't already in place.
For this customer, Build106823 was recommended: \\sashq\root\dept\ftp\outgoing\build106823
Not unlike SAS hot fixes, it's always a good idea to ensure available patches for LSF and PPM are current.
04-18-2017 08:55 AM
Thanks all, yes we have a patch from SAS for PPM and we are just lining up the resource to test and implement. I will update this discussion when we have implemented.