Summary -
In this topic, we described about the 101 RECORDBUSY with detailed example.
If this error condition occurred, the task gets abended with AEX9.
| Command | RESP2, Description & Solution |
|---|---|
| DELETE | 107 - The NOSUSPEND keyword is specified for the deletion of a record that is locked by a VSAM active lock. Solution: - This might occur very rarely. Wait for some time and try again. If this occurring on regular basis, modify the application program to remove NOSUSPEND. |
|
READ READNEXT READPREV |
107 - The NOSUSPEND keyword is specified and the record is locked by an active lock. Solution: - This might occur very rarely. Wait for some time and try again. If this occurring on regular basis, modify the application program to remove NOSUSPEND. |
| REWRITE | 107 - NOSUSPEND is specified but VSAM holds an active lock against a unique alternate index key which would cause the request to wait. Solution: - This might occur very rarely. Wait for some time and try again. If this occurring on regular basis, modify the application program to remove NOSUSPEND. |
| WRITE | 107 - NOSUSPEND is specified on the request but VSAM holds an active lock against the record, which would cause the request to wait. Solution: - This might occur very rarely. Wait for some time and try again. If this occurring on regular basis, modify the application program to remove NOSUSPEND. |