What are the terminate options for the "terminateABLSession" REST API or OEJMX query?

{"O":"PASOE:type=OEManager,name=AgentManager","M":["terminateABLSession","<agentID>",<agentSessionID>,<terminateOption>]}

DELETE /oemanager/applications/<abl-app-name>/agents/<agent-id|agent-pid>/sessions/<session-id>?terminateOpt=<terminate-opt>

A documentation defect has been submitted to update the documentation with the following information.

The terminate options for the terminateABLSession OEJMX query which can also be used in the DELETE API call are:

• 0 (Trappable stop):
  • ABL A Progress.Lang.StopError error is raised in the session. (soft/trappable stop), 
  • This can can caught by the application and dealt with appropriately. 
  • If not caught then a 500/Internal Server Error will be returned to the client.
• 1 (Hard stop):
  • An untrappable/uncatchable stop is raised since standard ABL stop behaviour applies ((ie transactions undo etc). 
  • A 500/Internal Server Error will be returned to the client, roughly equivalent to `kill -9` on the session,
• 2 (Complete request):
  • Any current request is allowed to finish and then the session is terminated.

Starting with OpenEdge 12.2.7 and 12.5, the following messages are written to the PASOE Agent log file when an ABL Session is terminated:

• For terminate option 0: Admin initiated termination of ABL Session AS-<number> with option: STOP
• For terminate option 1: Admin initiated termination of ABL Session AS-<number> with option: INTERRUPT
• For terminate option 2: Admin initiated termination of ABL Session AS-<number> with option: FINISH

Progress Articles:
How to recycle a PASOE agent with OEJMX? 
terminateABLSession requests are not logged    
ABL Session shutdown is never logged   
Cannot determine whether a StopError was raised from the terminateABLSession JMX query
terminateABLSession requests are not logged