You are developing a COBOL application that handles a large inventory database accessed by multiple users. What type of file locking strategy would you recommend to ensure data integrity while allowing concurrent reads?
- File-level locking
- No locking is needed for concurrent reads
- Record-level locking
- Table-based locking
For ensuring data integrity while allowing concurrent reads in a large inventory database, file-level locking is recommended. File-level locking ensures that the entire file is locked for write operations, preventing conflicts during updates.
Loading...
Related Quiz
- When using the "USE AFTER EXCEPTION" phrase with the READ statement in COBOL, what happens if the exception condition is not encountered?
- In a COBOL program, you need to store a date of birth. Which data type should you use to ensure compatibility with international date formats?
- Explain the concept of "caching" in the context of file handling performance optimization.
- In a multi-user COBOL application, two users are attempting to update the same record in a file simultaneously. How can you prevent conflicts and ensure that only one user can update the record at a time?
- What is the purpose of the COBOL REDEFINES clause?