DFS3643I USER xxxxxxxx HAS EXCEEDED DLQT VALUE. LAST ACCESSED ON yyyyddd.
Explanation
User xxxxxxxx has queued messages or outstanding status and has not been accessed since yyddd, which exceeds the time period specified on the DLQT JCL parameter. User xxxxxxxx was last accessed when it was created, signed on, or signed off. Other possibilities are when messages were dequeued, or queues were assigned away. User xxxxxxxx has been marked as having a status of DEADQ.
System programmer response
Verify that the time period specified on the DLQT JCL parameter is not unreasonably short.
For ISC users, determine why the ISC user was not allocated to a node for the DLQT time period.
For dynamic users, if the user name is defined to enhanced security such as RACF®, verify that user xxxxxxxx can access the queue by signing on. If the dynamic user name is not defined to enhanced security such as RACF, and thus cannot be signed on, determine why messages were queued or status applied to that user.
To aid the investigation of why messages were queued and to remove the status of DEADQ, use the /ASSIGN command to reassign queues and retrieve the data for evaluation.
To purge the data and to remove the DEADQ status, use the /DEQUEUE command. If status no longer applies to the user, remove the status using a command or by signing the user on and taking the necessary actions to reset the undesired status.
Delete dynamic users who were created inadvertently. To cause the user structure to be deleted, all the messages must be dequeued or the queues assigned away, and the status must be removed. Then, the user structure will be deleted at the next simple checkpoint.