DFS3101I MAXIMUM SESSIONS REACHED - NODE nodename


or

MAXIMUM SESSIONS REACHED

Explanation

The first form of the message is issued by the /OPNDST command processor. The second form of the message is issued by the LOGON or SCIP exit. Either all available parallel sessions are in use or a single session device is still active. This condition can occur if the half-session is allocated, stopped, or not idle. If a /OPN command was entered, this condition can also occur if OPTION=NOPNDST was specified on the TERMINAL macro.

System action

The command is not run, or a LOGON/REQSESS is denied.

Operator response

Wait until a session becomes available, and reenter the command.

If the problem persists for a single session device, the terminal might be hung in IMS as a result of an internal session cleanup problem. If the terminal remains hung after a VTAM VARY INACT and /CLSDST NODE FORCE, create a console memory dump and report the problem to IBM® Software Support. The receipt of this message for many terminals often indicates a more serious system wait, hang, or loop problem. If so, take a console memory dump before bringing the system down.