COMS Input Protection provides a mechanism to ensure that your transactions are not lost because of a Halt/Load. However, you might consider that the overheads of this function outweigh any real benefits you receive.
You can disable COMS Input Protection for a Specification by unsetting an environmental option in Builder.
Recommendation
It is generally recommended that you disable COMS Input Protection for your applications for the following reasons:
Input File Overhead
COMS Input Protection requires your input transactions to be stored in an Input file. This overhead can be removed if COMS Input Protection is disabled.
Duplicate Transaction Processing
Where External Automatic Entries (Hub communications) take place, COMS Input Protection might result in duplicate processing of these transactions. Applications using HUB communications should thus disable COMS Input Protection.
Limited Benefits
As COMS Input Protection is only involved with recovering transactions that have been received but not completed, real benefits are limited.
If COMS Input Protection is disabled, users who send a transaction but do not receive a reply (for example, SUCCESSFUL ENTRY), will have to reenter the transaction. This is the only additional activity required.
Disabling COMS Input Protection
To disable COMS Input Protection, perform the following:
Set the Protected Input Segment configuration property to False (this is the default setting).
Generate your application.