Using the NQNMODE merge tables

In Table 1, choose the resources that are being merged (one input resource and one existing resource) by looking at the resource types and the NQNMODE status, and then choosing the corresponding resource type numbers.
Using the two numbers (one for the input resource and one for the existing resource), look at Table 2 for input resources 1–5, or Table 3 for input resources 6–10, and find where the column for the input resource intersects the row for the existing resource.
Note: Only existing resources can be dynamic, in session, applications, or LUs. So, all resource types in Table 1 are valid for the existing resource, but only resource types 1–10 are valid for the input resource.
The intersection has a letter followed by numbers in parentheses. These letters and numbers correspond to notes about the merge. These notes are listed in Table 4.

Table 1. Resource types for NQNMODE merges. This table shows the resource types that are involved in the merge. Information includes whether the resource has sessions, and the current value of NQNMODE. NQNMODE must be either NAME or NQNAME.
Resource type	NQNMODE	Defined with NETID	Sessions
1 - Predefined CDRSC	NQNAME defaulted	Yes	No
2 - Predefined CDRSC	NQNAME defined	Yes	No
3 - Predefined CDRSC	NAME defaulted	Yes	No
4 - Predefined CDRSC	NAME defined	Yes	No
5 - Predefined CDRSC	n/a	No	No
6 - Predefined Independent LU	NQNAME defaulted	Yes	No
7 - Predefined Independent LU	NQNAME defined	Yes	No
8 - Predefined Independent LU	NAME defaulted	Yes	No
9 - Predefined Independent LU	NAME defined	Yes	No
10 - Predefined Independent LU	n/a	No	No
11 - Predefined CDRSC	NQNAME defaulted	Yes	Yes
12 - Predefined CDRSC	NQNAME defined	Yes	Yes
13 - Predefined CDRSC	NAME defaulted	Yes	Yes
14 - Predefined CDRSC	NAME defined	Yes	Yes
15 - Predefined CDRSC	n/a	No	Yes
16 - Predefined Independent LU	NQNAME defaulted	Yes	Yes
17 - Predefined Independent LU	NQNAME defined	Yes	Yes
18 - Predefined Independent LU	NAME defaulted	Yes	Yes
19 - Predefined Independent LU	NAME defined	Yes	Yes
20 - Predefined Independent LU	n/a	No	Yes
21 - Dynamic CDRSC	NAME	n/a	No
22 - Dynamic CDRSC	NQNAME	n/a	No
23 - Dynamic CDRSC	NAME	n/a	Yes
24 - Dynamic CDRSC	NQNAME	n/a	Yes
25 - Application	n/a	n/a	No
26 - Application	n/a	n/a	Yes
27 - LU	n/a	n/a	No
28 - LU	n/a	n/a	Yes

Table 2. Matrix for NQNMODE merges, part 1. In this table, input resources 1–5 are read left to right across the top of the five columns. The existing resources are read top to bottom, in the far left column. Letters and numbers at the intersection of a particular input resource with an existing resource are explained in Table 4.
Exist. res.	Input resource 1	Input resource 2	Input resource 3	Input resource 4	Input resource 5
1	F(8)	F(8)	F(8)	F(8)	F(8)
2	F(8)	F(8)	F(8)	F(8)	F(8)
3	F(8)	F(8)	F(8)	F(8)	F(8)
4	F(8)	F(8)	F(8)	F(8)	F(8)
5	F(8)	F(8)	F(8)	F(8)	F(8)
6	M(2 5 12 18)	M(2 5 12 14 18)	M(1 3 12 18)	M(1 3 12 18 14)	M(11 15 18 16)
7	M(2 5 12 18 14)	M(2 5 12 18)	M(2 5 12 18 6)	M(1 3 12 18)	M(11 15 18 16)
8	M(2 4 18)	M(2 4 18 14)	M(1 5 18) F(20)	M(1 5 18 14) F(20)	M(11 18 16)
9	M(1 5 18 14 6)	M(2 4 18 14)	M(1 5 18) F(20)	M(1 5 18 14) F(20)	M(11 18 16)
10	M(2 4 23 22)	M(2 4 23 22)	M(1 5 22)	M(1 5 22)	M(11 16 5)
11	F(8)	F(8)	F(8)	F(8)	F(8)
12	F(8)	F(8)	F(8)	F(8)	F(8)
13	F(8)	F(8)	F(8)	F(8)	F(8)
14	F(8)	F(8)	F(8)	F(8)	F(8)
15	F(8)	F(8)	F(8)	F(8)	F(8)
16	M(2 5 12 18)	M(2 5 12 14 18)	M(1 3 12 18)	M(1 3 12 14 18)	M(11 15 16 18)
17	M(2 5 12 13)	M(2 5 12 18)	M(2 5 6 12 13)	F(6 9)	M(11 15 16 18)
18	M(2 4 12 18)	M(2 4 12 18 14)	M(1 5 18) F(20)	M(1 5 18 14) F(20)	M(11 16 18)
19	M(1 5 6 12 13)	F(6 9)	M(1 5 18 14) F(20)	M(1 5 18 14) F(20)	M(11 16 18)
20	M(2 4 17 18)	M(2 4 17 18 14)	M(2 4 17 18)	M(2 4 17 18 14)	M(11 18)
21	M(2 4 7 12 18 21)	M(2 4 7 12 18 21,14)	M(5 18 21) F(20)	M(5 18 21) F(20)	M(7 11 15 16 18 21)
22	M(5 18 21)	M(5 18 21)	M(1 3 7 12 18 21)	M(1 3 7 12 18 21,14)	M(7 11 15 16 18 21)
23	M(2 4 7 12 18 21)	M(2 4 7 12 18 21,14)	M(5 18 21) F(20)	M(5 18 21) F(20)	M(7 11 15 16 18 21)
24	M(5 18 21)	M(5 18 21)	M(1 3 7 12 18 21)	M(1 3 7 12 18 21,14)	M(7 11 15 16 18 21)
25	S	S	S	S	S
26	S	S	S	S	S
27	S	S	S	S	S
28	S	S	S	S	S

Table 3. Matrix for NQNMODE merges, part 2. In this table, input resources are read left to right 6–10 across the top of the five columns. The existing resources are read top to bottom, in the far left column. Letters and numbers at the intersection of a particular input resource with an existing resource are explained in Table 4.
Exist. res.	Input resource 6	Input resource 7	Input resource 8	Input resource 9	Input resource 10
1	M(2 5 12 13)	F(19)	M(1 3 12 13)	F(19)	M(22 15 13 17 2)
2	M(2 5 12 13 14)	F(19)	M(2 5 12 13 6)	F(19)	M(2 6 15 13 17 22)
3	M(2 4 13)	F(19)	M(1 5 13) F(20)	F(19) F(20)	M(1 22 13 6 17)
4	M(1 5 13 14 6)	F(19)	M(1 5 13) F(20)	F(19)	M(1 22 13 6 17)
5	M(2 4 13 17)	F(19)	M(1 5 13 17)	F(19)	M(11 5 13 16)
6	F(8)	F(19)	F(8)	F(19)	F(8)
7	F(8)	F(19)	F(8)	F(19)	F(8)
8	F(8)	F(19)	F(8)	F(19)	F(8)
9	F(8)	F(19)	F(8)	F(19)	F(8)
10	F(8)	F(19)	F(8)	F(19)	F(8)
11	M(2 5 12 13)	F(19)	M(1 3 12 13)	F(19)	M(22 15 13 17 2)
12	M(2 5 12 13)	F(19)	M(2 5 6 12 13)	F(19)	M(2 6 15 13 17 22)
13	M(2 4 12 13)	F(19)	M(1 5 13) F(20)	F(19)	M(1 22 13 6 17)
14	M(1 5 6 12 13)	F(19)	M(1 5 13) F(20)	F(19)	M(1 22 13 6 17)
15	M(2 4 12 13 17)	F(19)	M(1 5 13) F(20)	F(19)	M(11 5 13 16)
16	F(8)	F(19)	F(8)	F(19)	F(8)
17	F(8)	F(19)	F(8)	F(19)	F(8)
18	F(8)	F(19)	F(8)	F(19)	F(8)
19	F(8)	F(19)	F(8)	F(19)	F(8)
20	F(8)	F(19)	F(8)	F(19)	F(8)
21	M(2 4 7 12 13 21)	F(19)	M(5 13 21) F(20)	F(19)	M(7 11 15 16 13 21)
22	M(5 13 21)	F(19)	M(1 3 7 12 13 21)	F(19)	M(7 11 15 16 13 21)
23	M(2 4 7 12 13 21)	F(19)	M(5 13 21) F(20)	F(19)	M(7 11 15 16 13 21)
24	M(5 13 21)	F(19)	M(1 3 7 12 13 21)	F(19)	M(7 11 15 16 13 21)
25	F(24)	F(19)	F(24)	F(19)	F(24)
26	F(24)	F(19)	F(24)	F(19)	F(24)
27	S	F(19)	S	F(19)	S
28	S	F(19)	S	F(19)	S

Table 4. Notes for NQNMODE merges tables. This table explains the letters and numbers seen in Table 2 and Table 3.
Letter, number	Explanation
M	Merge the resources.
F	Fail the integration request. Do not merge the resources. Existing resource remains unchanged.
S	Input resource is put into shadow. If a shadow already exists, the shadow is treated as the existing resource, and is merged with the input resource.
1	Resulting NQNMODE value for this resource is NAME.
2	Resulting NQNMODE value for this resource is NQNAME.
3	An SRT entry is added for this resource using the netid of this host, if the existing resource is cross net.
4	The SRT entry is deleted for this resource.
5	No SRT entry addition or deletion is needed.
6	Do not override a defined NQNMODE value with a defaulted one. Do not change the NQNMODE value.
7	When the existing resource is a dynamic CDRSC, the resources will be merged regardless of conflicting NQNMODE values, whether or not the existing CDRSC has sessions. The NQNMODE value of the existing resource becomes the NQNMODE value of the input resource.
8	It is not valid to have duplicate predefined resource definitions of the same type (for example, two CDRSC definitions, or two ILU definitions).
9	NQNMODE conflict, and the existing resource is in session. Also, the existing resource has NQNMODE defined.
10	Conflict in two defined NQNMODE values.
11	NQNMODE cannot be defined for a predefined alias.
12	Because NQNMODE=NQNAME on one of the resources, the netids of the input and existing resource must be the same to have a collision.
13	Only ILU parameters for the existing resources are overridden by parameters from the input resources. The RDTE for the existing resources is moved (if not already there) to ISTPDILU.
14	NQNMODE is now considered a defined value for the resulting resource.
15	The existing resource must have a netid of this host's netid for there to have been a collision.
16	The resulting resource becomes a predefined alias (RCDPDALS in RCDRS is turned on).
17	RCDPDALS in RCDRS is turned off.
18	The definition parameters for the existing resources are overridden by parameters from the input resources.
19	Impossible scenario. NQNMODE cannot be defined on a predefined ILU when the ILU is the input resource. NQNMODE is defined for an ILU only when the ILU has merged with a CDRSC which has NQNMODE defined.
20	Fail this integration request if the netids of the existing and input resources are different.
21	Resource becomes a predefined resource.
22	Resulting resource takes the netid of the input resource.
23	The input resource must have a netid of this host's netid for there to have been a collision.
24	The definition should be failed because there might be the case where an appl and an ILU represent the same resource.

Table 5. Cross-Domain resource major node definition statements and operands
Name	Definition statement	Operands	Page	Req	Sift effect	Default	Restrictions, dependencies
name	VBUILD	TYPE=CDRSC	TYPE	R
		CONFGDS	CONFGDS
		CONFGPW	CONFGPW				CONFGDS

name	NETWORK	NETID	NETID

name	GROUP	See the CSRSC definition statement for operands.

cdrscname	CDRSC	ADJLIST	ADJLIST		G
		ALSLIST	ALSLIST		G		ALSREQ
		ALSREQ	ALSREQ		G	ALSREQ start option
		ASLENT	ASLENT		G		ASLTAB
		ASLTAB	ASLTAB		G
		CDRM	CDRM		G
		CPNAME	CPNAME		G		REGISTER=NO
		DELETE	DELETE				model CDRSC's only
		DLOGMOD	DLOGMOD		G		MODETAB
		EAS	EAS		G	256	Independent LUs
		ENCR	ENCR		G	OPT
		ENCRTYPE	ENCRTYPE		G	DES
		ISTATUS	ISTATUS		G	ACTIVE
		LOGAPPL	LOGAPPL		G		NetView® or TSO
		LUALIAS	LUALIAS		G
		MAXSESS¹	MAXSESS		G		NCP-attached ILUs
		MDLENT	MDLENT		G		MDLTAB
		MDLTAB	MDLTAB		G
		MODETAB	MODETAB		G	ISTINCLM
		NATIVE	NATIVE		G
		NETSRVR	NETSRVR		G		APPN only
		NQNMODE	NQNMODE		G	NAME	see description
		PACING	PACING		G	1
		REGISTER	REGISTER		G	NO	CPNAME; APPN only
		RESSCB	RESSCB		G	0	Type 2.1
		SIRFMSG	SIRFMSG		G		STARTOPT
		SPAN	SPAN		G		NetView
		SRCOUNT	SRCOUNT		G		SRCHRED start option
		SRTIMER	SRTIMER		G		SRCHRED start option
		SUBAREA	SUBAREA		G
		VFYOWNER	VFYOWNER		G	NO	Subarea sessions
		VPACING	VPACING		G	2
Legend: R Required operand. G Code this operand on the higher-level GROUP definition statement to take advantage of the sift effect, or code it on this definition statement.

¹You should not exceed the MAXSESS value coded on the NCP's BUILD macro. VTAM® does not check the value coded here against the value coded on the NCP's BUILD macro. Session setups will fail if the maximum number of sessions attempted exceeds the MAXSESS value coded on the NCP's BUILD macro.