DFS189 TERMINAL OR USER NOT STOPPED AND IDLE, CANNOT PROCESS COMMAND
Explanation
The terminal or user must be stopped or idle, or both, before the command can be processed.
For /DEQUEUE LINE, LTERM, MSNAME, or NODE command, the line, MSC link, or node must be stopped and idle if the PURGE/PURGE1 keyword is specified.
For /DEQUEUE LTERM with the
PURGE/PURGE1 keyword specified, if the command is issued for a dynamic LTERM in a shared-queue
environment with the STM=YES option specified, the user must be stopped and idle.
For /DEQUEUE LUNAME, the LU 6.2 destination must be stopped.
For /DEQUEUE USER, the user must be stopped if the PURGE/PURGE1 keyword is specified.
For /EXIT command, the line or node must be stopped and idle to protect the conversational user from having the conversation terminated while entering a segment for it.
System action
The entered command is disregarded.
Operator response
(local/remote terminal) For /DEQUEUE LINE, /DEQUEUE LTERM, /DEQUEUE MSNAME, and /DEQUEUE NODE, stop and idle the line/node/link. For /DEQUEUE LUNAME, stop the LU 6.2 destination. For /DEQUEUE USER, stop the user.For /DEQUEUE LTERM with the
PURGE/PURGE1 keyword specified, complete the following steps:- Issue a /STOP USER command to set the user in the stopped status.
- Issue the /DEQUEUE LTERM command with the PURGE/PURGE1 keyword again.
- If the command fails again with a DFS189 message because an IMS checkpoint is triggered after the /STOP USER command but before the /DEQUEUE LTERM (PURGE/PURGE1) command is issued again, restart the user, and repeat Steps 1-2.