We have noticed many orphaned subsystem jobs piling up in the F986113.
In tracking them down we found that the way we stop the subsystem jobs each night for things like backups, nightly processing, etc. may have been causing jobs to just sit there and not be processed. The process that was in place just deleted the subsystem processing job records from the F986113.
I did some research and found that an article on JDEList.com says to essentially use SQL to set the subsystem processing jobs to an “ERROR” state.
That didn’t seem quite right to me either. So, I set out to find out what the application does to end the subsystem jobs and found that it inserts a record into the F986113 that triggers the job to end.
Below is the that can be used to end the subsystem jobs gracefully:
insert into svm900.f986113 (SSPID,SSVERS,SSSBMDATE,SSSBMTIME,SSJOBSTS,SSOPCR,SSENHV,SSJOBNBR,SSUSER,SSORGHOST,SSJOBPTY,SSEXEHOST) select SSPID,SSVERS,SSSBMDATE,SSSBMTIME+1,'R','W',SSENHV,SSJOBNBR,'JDEPKG',SSORGHOST,'0',SSEXEHOST FROM SVM900.F986113 WHERE SSPID='R43500'