M204.0582 Access to file token prevented by: jobname
A shared DASD enqueuing conflict occurred for the specified file. Another Model 204 run processing on a different CPU has established an enqueue against this file. This conflicts with the enqueue level you are attempting to establish. That is, if you want a share enqueue, another run has an exclusive enqueue on the file; if you want an exclusive enqueue, another run already has either a share or an exclusive enqueue. If this message occurs in a batch Model 204 run, Model 204 waits for five minutes and retries the enqueue. It continues to wait and retry until the enqueue succeeds.
Model 204 maintains a Shared DASD Enqueue List for each file on the File Parameter List page, that is, on the first page of the file. Refer to Shared DASD and Global Resource Serialization for more details about file enqueueing between multiple copies of Model 204.
Response: Retry the request or command later or notify your system manager if you suspect that the job holding the enqueue has crashed.
System manager response: There may be either a real enqueueing conflict or an obsolete shared DASD enqueue list due to a system crash. The job name specified in the message will assist you in determining the cause. Use the ENQCTL command to correct obsolete shared DASD enqueue lists. This command should be used with extreme caution as its abuse can cause file integrity problems.
Operator response: Notify the Model 204 system manager if there are multiple occurrences of this message.
|RETCODEO=0||Sets online return code|
|RETCODEB=0||Sets batch (single user) return code|
|CLASS=I||Information class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter|
|AUDITMS||Writes the message with line type MS to the audit trail|
|NOCOUNT||Does not increment the error count (ERCNT) parameter|
|OPR||Writes the message to the (operator) console|