DBI from PAS MSAgent keeps growing

PASOE agent DBI file is continuously growing causing disk space problems.
DBI from PAS MSAgent keeps growing beyond GB in size causing additional delays when terminating the MSA
The process using these files is the PAS Agent not to the PAS Agent Sessions. 
DBI files continue to grow when the load on the PAS appserver is low (only 1 or 2 calls per second) 
When there are no open transactions on the database the DBI file continues to grow around 5 minute intervals
What is causing the large DBI files from the MSA ?

Every transaction is finished within a few hundred milliseconds. 
There is nothing scheduled what every 5 minutes calls the appserver, it seems to be an internal pasoe process causing DBI growth
Agent startup parameters: -T /temp -t -Bt 20000 -tmpbsize 8 

When the MSAgent is stopped logs with logentrytype temp-tables:3 or -tttablerangesize / -ttindexrangesize with ttStats enabled shows the AS-ADMIN process deleting Temp-Tables and the DBI file is eventually removed: If on Unix like platform with -t enabled, the DBI files are visible. Without enabling 4GLTrace, the DBI files owner process can be determined by the file name. (Note: this format is a convention OpenEdge uses for now(as of version 12.8), it might be changed in the future.) The file name should be like:
DBIthreadid_sessionNumXXXXXX
Where:
           threadid is some number,
           sessionNumber is the ABL Session number (e.g., 4 for AS-4, 7 for AS-7). You can identify the AS-Admin temp-table db file name because its sessionNumber will always be 3. And,
XXXXXX gets replaced by the OS with something random when the file name is created (trying to guarantee a unique name).

This is functioning as currently designed and will require a feature enhancement otherwise.

The DBI file is the Admin Session's temp-table (it owns the _AgentRequest table)
Request metrics are stored in a temp-table and as the number of requests increases, so will the DBI file for the AS-Admin session.
There's no way to delete the _AgentRequest temp-table.

This is the Admin Session's temp-table (it owns the _AgentRequest table). 

1.  Trim the PASOE MSAgent

• How to stop a PASOE agent with OEJMX?
• How to trim and restart PASOE Agents using REST APIs.

2.  Periodically flush records from the Admin Session's temp-table by clearing the collected metrics (since 11.7.5)

• The JMX query will not reduce the current size of the DBI file, but it will prevent it from growing further until the space becomes filled again with request records. 

Alternatively use the REST API via OEMANAGER using a DELETE HTTP request against the OEMANAGER URL endpoint :

Progress Articles:
Is there a LOG-ENTRY-TYPE to log TEMP-TABLE statistics?    
Seeing a lot of DBI file growth and DBI file is not deleted