DFS4451I LOGON REJECTED, NODE xxxxxxxx, RC=yy

Explanation

In an IMSplex environment, a VTAM® terminal (xxxxxxxx) attempted to log on to IMS and IMS attempted to register the terminal to Resource Manager (RM). However, IMS rejected the logon attempt. Most logon failures are the result of the node already being registered to RM due to a previous logon or a command issued and state data verification failed.

In the message text:
xxxxxxxx
The VTAM terminal IMS attempted to register onto RM.
yy
The reason code for the failure. The following list provides the reason codes and their meanings.
Reason
Meaning
01
The node was stopped.
02
A mismatch occurred between the local and RM definition: a static terminal as opposed to a dynamic terminal.
04
A mismatch occurred between the local and RM definition: a single session as opposed to a parallel-session.
05
A mismatch occurred between the local and RM definition: node device type.
06
A mismatch occurred between the local and RM definition: output-only (CTB4OUTP).
07
A mismatch occurred between the local and RM definition: output-only (CTBCPRT1).
08
A mismatch occurred between the local and RM definition: MFS use (CTT2DIT).
09
The node is already logged on to another active IMS system.
0A
The node is already logged on to another IMS system, but this IMS cannot determine the state of the owning system.
0B
The data in the static-node-user resource DATA2 is invalid.
0C
The data in the static-node-user resource is invalid.
0D
The data in the static-node-user resource is invalid.
0E
A mismatch occurred between the local and RM definition: the number of assigned LTERMS. Static terminal and LTERM definitions must be consistent, and the /ASSIGN command must be used consistently in each IMS system.
0F
A mismatch occurred between the local and RM definition: node device type.
10
A mismatch occurred between the local and RM definition: the order of assigned LTERMs. Static terminal and LTERM definitions must be consistent, and the /ASSIGN command must be used consistently in each IMS system.
11
The node with LOCAL status recovery mode is owned by another system in the IMSplex. The IMS that owns the node failed, but the user logon exit, DFSLGNX0, has not indicated that the logon can continue in this situation.
12
The node is already logged on to another IMS system, but this IMS cannot determine the state of the owning system.
13
The node is already logged on to another active IMS system.
14
A mismatch occurred between the local and RM definition: an assigned LTERM in RM is not found in the local system. Static terminal and LTERM definitions must be consistent, and the /ASSIGN command must be used consistently in each IMS system.
15
A mismatch occurred between the local and RM definition: static/dynamic LTERM.
16
A mismatch occurred between the local and RM definition: an assigned LTERM in the local system exists in RM but is assigned to a different node. Static terminal and LTERM definitions must be consistent, and the /ASSIGN command must be used consistently in each IMS system.
17
A system error occurred. The DFSPOOL GET storage request failed.
18
An RM system error occurred. RM did not return output on a CSLRMUPD request.
19
An RM system error occurred. Output that was returned on a CSLRMUPD request contained invalid data.
1A
IMS attempted to register a node or LTERM but it was already registered to RM as a different resource type within the same name type group. Message DFS4446E is also be issued.
1B
An unrecognized condition code was returned on a CSLRMUPD output list entry.
1C
An unrecognized return or reason code was returned on a CSLRMUPD request. Message DFS3308E should also be issued.
1D
IMS attempted to register the node and LTERMs but failed after certain recoverable errors occurred. IMS retried the registrations but reached the retry limit.
1E
The node had user information in RM, but the user resource could not be found in RM. This is a temporary condition. Retry the terminal logon.
1F
The STSN node with LOCAL status recovery mode is owned by another system in the IMSplex. The owning IMS failed but the user logon exit, DFSLGNX0, did not indicate that the logon can continue in this situation.
20
A user in Fast Path response mode attempted to log on to an IMS system that is not Fast Path capable or is not using an EMHQ structure.
21
The Resource Manager is unavailable.
22
The resource structure is unavailable.
23
A dynamic SLUP or FINANCE terminal attempted a warm session initiation, but there was an error in processing the information from RM. Retry the terminal logon.
24
An ISC terminal attempted a warm session initiation, but there was an error in processing the information from RM. Retry the terminal logon.
25
IMS has received an error return code from the Resource Manager, but the error is considered temporary. Try logging on again.

System action

The logon attempt is rejected.

Operator response

Attempt to correct the problem that is preventing logon indicated by the return code, then retry the logon. Use the /DISPLAY commands to determine the status of each terminal on each system in the IMSplex.

Module

DFSSLON0