DM_DELAYCLOSE Keyword
9.5B
DM_DELAYCLOSE={ON | OFF}
When this keyword is enabled, the close operation is delayed for any AFILE, IFILE, or FILE file variables opened at a SUNDM server. This behavior of a PLB runtime can only be invoked by the DM_DELAYCLOSE keyword that can be defined in the SUNDM.CFG file. The intended use of this keyword is to improve the performance of a PLB program when managed files are closed with explicitly or implicitly.
Note:
The program closing action for managed AFILE, IFILE, or FILE variables are delayed until one of the following conditions occurs:
A maximum of fifty (50) files to a specific SUNDM is delayed.
All opened files to a specific SUNDM are closed.
Any PLB language instruction is encountered in a program that requires a log-on to a specific SUNDM. This includes OPEN, PREP, AAMDEX, INDEX, RENAME, SORT, COPYFILE, and any other instructions that logs onto a SUNDM server.
More than two (2) seconds elapses between the first close and a keepalive runtime check. This is to prevent any unnecessary wasted time to close files opened at a SUNDM server.
Any PLB language instruction that can suspend keepalive messages to a SUNDM server. As an example, an PLB instructions that would cause a Windows OS dialog to be presented or, an ALERT would cause the keepalive messages to a SUNDM to be suspended. This same instruction would cause any delayed/queues close operations to be sent to a SUNDM to be executed.
The Data Manager DM_DELAYCLOSE keyword helps improve the performance when non-common file variables are opened at the Data Manager and they are implicitly being closed by a CHAIN operation.
The DM_DELAYCLOSE keyword should not be used except in extreme scenarios where there are an excessive large number of users have files opened at a specific SUNDM server. It would be recommended that this keyword should not be used unless there are more than a one thousand (1,000) users logged on to a Data Manager.
Example:
DM_DELAYCLOSE=on
See Also: SUNDM Keywords
![]() |