EnterpriseOne SubSystem Jobs Not Starting

Read Time:1 Min, 17 Sec

For a while now we have had an issue where our subsystem Purchase Order Print job (R43500) will not run in JPD900 but it will in PD900. After going through the debug log I found a something:

--UBE--[0]-- SS0000009:Subsystem Limit is reached. 
--UBE--[0]-- SS:Cannot start new subsystem.

Above this notification I found an SQL was ran looking for subsystem jobs in the F986113:

SELECT COUNT(*) 
FROM SVM900/F986113 
WHERE ( SSPID = R43500 AND SSVERS = MOD0009 AND SSENHV = JPD900 
AND SSEXEHOST = MODENT AND SSJOBSTS = S )

The results of this SQL was 3. Which is the UBE Subsystem Limit specified in the Enterprise Servers JDE.INI [UBE] section (Configurations – Batch Processing from Oracle Server Manager). 3 is also the default value.
However, there is a problem with this SQL querie. It only finds the number of subsystem jobs that have been submitted. It doesnt check to see if they are running. If all subsystem jobs have been stopped properly, there would be zero records returned from this SQL. However, if you have had any issues with subsystem jobs or even if things dont get cleaned up correctly when bouncing services, you can end up with subsystem jobs in an error state.
The only way to clean up these records is to go into the database and remove them:

DELETE FROM SVM900/F986113 
WHERE (SSPID = R43500 AND SSVERS = MOD0009 AND SSENHV = JPD900 
AND SSEXEHOST = MODENT AND SSJOBSTS = S AND SSOPCR=E)

Do you have any tips for SubSystem jobs? If so, please leave them in the comments.

Author

Stewart Schatz

Career: Principal CNC Consultant for Syntax Systems Limited specializing Oracle JD Edwards EnterpriseOne and the technology that supports it. Side Hustle: Owner/Operator of E1Tips.com Location: Lancaster, PA USA What I like to do: Invest in Family, Explore Technology, Lead Teams, Share Knowledge/Experience, Hunt, Hike, etc.

stewart@9rains.com

http://stewartschatz.com