Use this command to activate one or more network addressable units
(NAUs).
Requirements and Restrictions
- To activate a remote Advanced Peer-to-Peer Networking (APPN) control point
(CP), the TPF system must be in NORM state and CP-CP sessions cannot already
exist with any processor in the TPF loosely coupled complex.
- To activate any other NAU, the TPF system must be in CRAS state or
higher.
Format
- Id
- specifies the NAU to be activated, which can be one of the
following:
- netid.nau
- activates the specified resource, where netid.nau is the
1- to 17-character symbolic name of the NAU to be activated. The
network ID and name of a resource must both begin with a letter (A-Z),
@, #, or $. The remaining characters can be
letters (A-Z), numbers (0-9), @, #, or
$.
- Note:
- To specify an SNA network ID or resource name that contains dollar signs
($), you must type two consecutive dollar signs ($$) for
each dollar sign in the network ID or resource name. For example, if
the SNA resource name is $SNANAME, you must type
$$SNANAME.
- CTCNODES
- activates all channel-to-channel (CTC) links.
- ALSNODES
- activates all PU 2.1 links.
- netid.cpname
- activates CP-CP sessions with a remote CP, where
netid.cpname is a 1- to 17-character symbolic name of the
remote CP to be activated. The network ID and name of a resource
must both begin with a letter (A-Z), @, #, or
$. The remaining characters can be letters (A-Z),
numbers (0-9), @, #, or $.
Notes:
- You cannot specify the name of a remote CP that resides in an APPN end
node (EN).
- To specify an SNA network ID or resource name that contains dollar
signs ($), you must type two consecutive dollar signs
($$) for each dollar sign in the network ID or resource
name. For example, if the SNA resource name is $SNANAME, you must type
$$SNANAME.
- CPCP
- activates CP-CP sessions with a remote CP that is selected by the TPF
system.
- Sda-addr
- activates a local NCP or CTC, where addr is the symbolic device
address of the 37x5 NCP or CTC.
- Note:
- This parameter is required for NCP but optional for CTC. When
activating a CTC link, the TPF system chooses an available CTC SDA if you omit
this parameter.
- Logon-appl
- activates cross-domain applications to local TPF application sessions,
where appl is the symbolic name of the local TPF application that is
placed in session for the cross-domain application specified on the ID
parameter.
- Cdrm-cdrmname
- starts FMMR-FMMR or application-application (APPL-APPL) sessions through a
gateway SNA network interconnection (SNI), where cdrmname is the 1-
to 8-character symbolic name of the gateway system services control point
(SSCP). The network ID and name of a resource must both begin with
a letter (A-Z), @, #, or $. The remaining
characters can be letters (A-Z), numbers (0-9), @,
#, or $.
Notes:
- For FMMR-FMMR sessions, the remote FMMR is placed in session with the
local FMMR through the specified CDRM.
- If you specify the CDRM parameter, you must also specify the LOGON
parameter.
- The ID parameter must specify the remote FMMR or the remote
application; the LOGON parameter must specify the local SSCP or the local
application.
- If you do not specify the CDRM parameter, how the TPF system starts the
session with the specified remote LU is determined by the following:
- Whether the TPF system is connected to the network as a PU 5 node, PU
2.1 node, or both.
- How sessions with the specified remote LU were activated
previously.
See TPF ACF/SNA Data Communications Reference for
more information about how the TPF system selects the path to use when
starting a new LU-LU session.
- Sessions across CTC links do not cross gateway boundaries. Specify
the name of the remote CDRM to start an application-application (APPL-APPL)
session across a CTC link to another TPF system or VTAM system.
- To specify an SNA network ID or resource name that contains dollar
signs ($), you must type two consecutive dollar signs
($$) for each dollar sign in the network ID or resource
name. For example, if the SNA resource name is $SNANAME, you must type
$$SNANAME.
- CNT-count
- specifies the number of secondary logical unit (SLU) threads to be
activated, where count is a number between 1 and 255.
- Note:
- If you do not specify the CNT parameter, all SLU threads that are not already
in session will be activated.
- LINK-alsname
- specifies the 1- to 8-character name of the adjacent link station (ALS)
through which the CP-CP sessions will be established. The network
ID and name of a resource must both begin with a letter (A-Z),
@, #, or $. The remaining characters can be
letters (A-Z), numbers (0-9), @, #, or
$.
Notes:
- If you do not specify the LINK parameter, the TPF system will search all
of the active APPN links that support CP-CP sessions to find a link connected
to the specified remote CP, and use the first link found to start the CP-CP
sessions.
- To specify an SNA network ID or resource name that contains dollar
signs ($), you must type two consecutive dollar signs
($$) for each dollar sign in the network ID or resource
name. For example, if the SNA resource name is $SNANAME, you must type
$$SNANAME.
Additional Information
Online help information is available for this command. To display
the help information, enter one of the following:
ZNETW HELP
ZNETW ?
Examples
A CTC link is activated in the following example.
+--------------------------------------------------------------------------------+
|User: ZNETW ACT ID-TBCTCL1 |
| |
|System: NETW0011I 08.37.29 CTC TBCTCL1 ACT PROCESSING BEGUN |
| XID20000I 08.37.29 SDA 03AF NODE NAME TBCTCL1 |
| SUCCESSFUL XID FORMAT 2 COMPLETED |
| NETW0033I 08.37.29 CTC TBCTCL1 ACT PROCESSING COMPLETE |
+--------------------------------------------------------------------------------+
An LU-LU session is started in the following example.
+--------------------------------------------------------------------------------+
|User: ZNETW ACT ID-RBS1B001,LOGON-RCS1 |
| |
|System: NETW0011I 08.43.43 LU RBS1B001 ACT PROCESSING BEGUN |
| NETW0033I 08.43.43 LU RBS1B001 ACT PROCESSING COMPLETE |
+--------------------------------------------------------------------------------+
In the following example, an LU-LU session is started through the specified
gateway SNI.
+--------------------------------------------------------------------------------+
|User: ZNETW ACT ID-RBS1B002,LOGON-RCS1,CDRM-TPFB |
| |
|System: NETW0011I 08.44.14 LU RBS1B002 ACT PROCESSING BEGUN |
| NETW0033I 08.44.15 LU RBS1B002 ACT PROCESSING COMPLETE |
+--------------------------------------------------------------------------------+
APPN CP-CP sessions are started in the following example. The TPF
system selects the remote CP to use.
+---------------------------------------------------------------------------------------------+
|User: ZNETW ACT ID-CPCP |
| |
|System: NETW0100I 17.19.04 CPCP ACT PROCESSING BEGUN |
| NETW0101I 17.19.14 CPCP ACT PROCESSING COMPLETE, CP VTAMNET.VTAM2 SELECTED |
+---------------------------------------------------------------------------------------------+
A specified number of SLU threads are activated in the following
example.
+--------------------------------------------------------------------------------+
|User: ZNETW ACT ID-RBS1 LOGON-RAS1 CNT-2 CDRM-TPFB |
| |
|System: NETW0011I 18.13.09 APPL RAS1 ACT PROCESSING BEGUN |
| NETW0067I 18.13.09 2 SLU SESSIONS REQUESTED, 2 INITIATED |
| NETW0033I 18.13.09 APPL RAS1 ACT PROCESSING COMPLETE |
+--------------------------------------------------------------------------------+
Related Information
See TPF ACF/SNA Data Communications Reference for
more information about SNA communications.