The performance of Dynamic SQL INSERT statement against NETWORK schema is reduced because there is a lot of processing to generate an access plan for the Insert.
Other statements are Cacheable: SELECT, UPDATE, and DELETE SQL statements and the CALL statement.
I would like to see the INSERT Statement syntax cached in a similar way
Our large IDMS Network schema with over 1,000 records and 1,500 sets the act of reading the Schema from the dictionary to establish the access plan and create a temporary subschema is a lot larger than the eventual process to INSERT (STORE) the record. With the large quantity of update transaction, including INSERT statements this is a considerable overhead in terms of CPU, IO and consequent elapsed time for the transaction to complete.
If the Dictionary access and reading the schema was not required for INSERT then we could use SQL INSERT successfully with our Dynamic SQL and java application.
As an IDMS DBA I would like the Dynamic INSERT SQL statement to be cached for NETWORK schema so that transactions including INSERT SQL statements execute efficiently in a short time without unnecessary CPU and IO overheads.