Change Network Attributes (CHGNETA)
Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Change Network Attributes (CHGNETA) command changes the network attributes of a system. A network attribute is control information about the communications environment. Network attributes contain specifications that can be used for networking and communications.
Restrictions:
- This command is shipped with public exclude (*EXCLUDE) authority. When this command is shipped, authority is issued only to the security officer. The security officer can grant the use of this command to other users.
- A user is required to have both all object (*ALLOBJ) and input/output system configuration (*IOSYSCFG) special authority to change the network attributes Network job action (JOBACN), DDM/DRDA request access (DDMACC), and Client request access (PCSACC).
- A user is required to have *IOSYSCFG special authority to change the network attribute Allow add to cluster (ALWADDCLU).
Notes:
- Information about specifying communications names is in the CL topic collection in the Programming category in the IBM i Information Center at http://www.ibm.com/systems/i/infocenter/.
- Information about advanced program-to-program communications (APPC), advanced peer-to-peer networking (APPN), and high-performance routing (HPR) is in the APPN information in the Networking category in the IBM i Information Center at http://www.ibm.com/systems/i/infocenter/.
- More information on this command is in the Work management topic collection in the IBM i Information Center at http://www.ibm.com/systems/i/infocenter/ or the Communcations Management book, SC41-5406.
Top |
Parameters
Keyword | Description | Choices | Notes |
---|---|---|---|
SYSNAME | System name | Character value, *SAME | Optional |
LCLNETID | Local network ID | Communications name, *SAME | Optional |
LCLCPNAME | Local control point name | Communications name, *SAME | Optional |
LCLLOCNAME | Default local location name | Communications name, *SAME | Optional |
DFTMODE | Default mode | Communications name, *SAME | Optional |
NODETYPE | Node type | *SAME, *ENDNODE, *NETNODE, *BEXNODE | Optional |
DTACPR | Data compression | 1-2147483647, *SAME, *NONE, *REQUEST, *ALLOW, *REQUIRE | Optional |
DTACPRINM | Intermediate data compression | 1-2147483647, *SAME, *NONE, *REQUEST | Optional |
MAXINTSSN | Maximum intermediate sessions | 0-9999, *SAME | Optional |
RAR | Route addition resistance | 0-255, *SAME | Optional |
NETSERVER | Network node servers | Single values: *SAME, *NONE Other values (up to 5 repetitions): Element list |
Optional |
Element 1: Server network ID | Communications name, *LCLNETID | ||
Element 2: Control point name | Communications name, *ANY | ||
ALRSTS | Alert status | *SAME, *ON, *OFF, *UNATTEND | Optional |
ALRLOGSTS | Alert logging status | *SAME, *NONE, *LOCAL, *RCV, *ALL | Optional |
ALRPRIFP | Alert primary focal point | *SAME, *NO, *YES | Optional |
ALRDFTFP | Alert default focal point | *SAME, *NO, *YES | Optional |
ALRBCKFP | Alert backup focal point | Single values: *SAME, *NONE Other values: Element list |
Optional |
Element 1: Network ID | Communications name, *LCLNETID | ||
Element 2: Control point name | Communications name | ||
ALRRQSFP | Alert focal point to request | Single values: *SAME, *NONE Other values: Element list |
Optional |
Element 1: Network ID | Communications name, *LCLNETID | ||
Element 2: Control point name | Communications name | ||
ALRCTLD | Alert controller description | Name, *SAME, *NONE | Optional |
ALRHLDCNT | Alert hold count | 0-32767, *SAME, *NOMAX | Optional |
ALRFTR | Alert filter | Single values: *SAME, *NONE Other values: Qualified object name |
Optional |
Qualifier 1: Alert filter | Name | ||
Qualifier 2: Library | Name, *LIBL, *CURLIB | ||
MSGQ | Message queue | Single values: *SAME Other values: Qualified object name |
Optional |
Qualifier 1: Message queue | Name | ||
Qualifier 2: Library | Name, *LIBL, *CURLIB | ||
OUTQ | Output queue | Single values: *SAME Other values: Qualified object name |
Optional |
Qualifier 1: Output queue | Name | ||
Qualifier 2: Library | Name, *LIBL, *CURLIB | ||
JOBACN | Network job action | *SAME, *REJECT, *FILE, *SEARCH | Optional |
MAXHOP | Maximum hop count | 1-255, *SAME | Optional |
DDMACC | DDM/DRDA request access | Single values: *SAME, *REJECT, *OBJAUT Other values: Qualified object name |
Optional |
Qualifier 1: DDM/DRDA request access | Name | ||
Qualifier 2: Library | Name, *LIBL, *CURLIB | ||
PCSACC | Client request access | Single values: *SAME, *REJECT, *OBJAUT, *REGFAC Other values: Qualified object name |
Optional |
Qualifier 1: Client request access | Name | ||
Qualifier 2: Library | Name, *LIBL, *CURLIB | ||
DFTNETTYPE | Default ISDN network type | Character value, *SAME, *ATT, *DBP1TR6, *ETSI, *JAPAN, *NISDN, *NORTEL, *NORTHAMT1 | Optional |
DFTCNNLST | Default ISDN connection list | Name, *SAME | Optional |
ALWANYNET | Allow AnyNet support | *SAME, *NO, *YES | Optional |
NWSDOMAIN | Network server domain | Character value, *SAME, *SYSNAME | Optional |
ALWVRTAPPN | Allow APPN virtual support | *SAME, *NO, *YES | Optional |
ALWHPRTWR | Allow HPR transport tower | *SAME, *NO, *YES | Optional |
VRTAUTODEV | Virtual ctl autocreate dev | 1-254, *SAME | Optional |
HPRPTHTMR | HPR path switch timers | Element list | Optional |
Element 1: Network priority | 1-10000, *SAME, *NONE | ||
Element 2: High priority | 1-10000, *SAME, *NONE | ||
Element 3: Medium priority | 1-10000, *SAME, *NONE | ||
Element 4: Low priority | 1-10000, *SAME, *NONE | ||
ALWADDCLU | Allow add to cluster | *SAME, *NONE, *ANY, *RQSAUT | Optional |
MDMCNTRYID | Modem country or region ID | Character value, *SAME | Optional |
Top |
System name (SYSNAME)
Specifies the name assigned to the system. The name can contain up to 8 alphanumeric characters. If the system name is not set, it is defaulted at initial program load (IPL) to the machine serial number (with the first character changed, if necessary, to an alphabetic character).
- *SAME
- The system name does not change.
- character-value
- Specify the name that identifies the system. The pending system name is changed when a request to change the system name is issued (except when entered during IPL). The pending system name becomes the current system name at the next IPL of the system.
Top |
Local network ID (LCLNETID)
Specifies the local network ID assigned to the system.
- *SAME
- The local network ID does not change.
- communications-name
- Specify the local network ID for the system.
Top |
Local control point name (LCLCPNAME)
Specifies the name of the local control point for the system. If the local control point name is not set, it is defaulted at initial program load (IPL) to the machine serial number with the first character changed (if necessary) to an alphabetic character.
- *SAME
- The local control point name does not change.
- communications-name
- Specify the name of the local control point for the system.
Top |
Default local location name (LCLLOCNAME)
Specifies the default local location name for the system. If the default local location name is not set, it is defaulted at initial program load (IPL) time to the machine serial number (with the first character changed, if necessary, to an alphabetic character).
- *SAME
- The local location name does not change.
- communications-name
- Specify the name of the default local location for the system.
Top |
Default mode (DFTMODE)
Specifies the default mode for APPC and APPN locations.
- *SAME
- The default mode does not change.
- communications-name
- Specify the default mode. Mode names SNASVCMG and CPSVCMG are not allowed. Specifying BLANK for the default mode is the same as specifying a mode of all blanks.
Top |
Node type (NODETYPE)
Specifies the APPN node type.
- *SAME
- The node type does not change.
- *ENDNODE
- The node does not provide network services to other nodes but can participate in the APPN network using the services of an attached network server, or can operate in a peer environment similar to low entry networking nodes. You cannot specify *ENDNODE if *YES is specified for either the Alert primary focal point (ALRPRIFP) parameter or the Alert default focal point (ALRDFTFP) parameter.
- *NETNODE
- The node provides intermediate routing, route selection services, and distributed directory services for local users, and to end nodes and low entry networking nodes that it is serving.
- *BEXNODE
- The node performs as a branch extender node. The node performs as an end node in the backbone APPN network, and performs as a network node server to end nodes within its local domain.
Top |
Data compression (DTACPR)
Specifies the level of data compression used when the system is an SNA end node.
- *SAME
- The value does not change.
- *NONE
- Data compression is not allowed on the session.
- *ALLOW
- Data compression is allowed on the session by the local system if requested by a remote system. The local system does not request compression.
If data compression is requested by the remote system, the data compression levels used by the session are the lower of the requested levels and the configured levels.
- *REQUEST
- Data compression is requested on the session by the local system. However, the request can be refused or negotiated to lower compression levels by the remote system. Data compression is allowed on the session if requested by the remote system.
The data compression levels that the local system will request are the configured levels. The negotiated data compression levels can never exceed the configured values.
If data compression is requested by the remote system, the data compression levels used by the session are the lower of the requested levels and the configured levels.
- *REQUIRE
- Data compression is required on the session. If the remote system does not negotiate to the local system's exact required levels of compression, the session is not established.
The data compression levels that the local system requires are the configured levels.
- 1-2147483647
- Specify the maximum line speed, in bits per second (bps), at which data is compressed. If the line speed of the link used by the session is less than or equal to this specified line speed, data compression is negotiated for the session as if *REQUEST is specified. Otherwise, compression is negotiated for the session as if *ALLOW is specified.
Top |
Intermediate data compression (DTACPRINM)
Specifies the level of data compression to request when the system is an SNA intermediate node.
- *SAME
- The value does not change.
- *NONE
- The remote systems are not notified of a need to compress data when the system is an SNA intermediate node.
- *REQUEST
- The remote systems are requested to compress data when the system is an SNA intermediate node.
- 1-2147483647
- Specify a line speed in bits per second (bps). If either the receiving or sending link has a line speed equal to or less than this specified line speed, data compression is requested from the remote systems. Otherwise, remote systems are not requested to compress the data.
Top |
Maximum intermediate sessions (MAXINTSSN)
Specifies the maximum number of APPN intermediate sessions. This parameter is used only when *NETNODE or *BEXNODE is specified for the Node type (NODETYPE) parameter.
- *SAME
- The maximum number of APPN intermediate sessions does not change.
- 0-9999
- Specify the maximum number of intermediate sessions.
Top |
Route addition resistance (RAR)
Specifies the APPN route addition resistance. This parameter is used only when *NETNODE or *BEXNODE is specified for the Node type (NODETYPE) parameter.
- *SAME
- The route addition resistance does not change.
- 0-255
- Specify the route addition resistance.
Top |
Network node servers (NETSERVER)
Specifies the APPN network node servers. This parameter is used only when *ENDNODE or *BEXNODE is specified for the Node type (NODETYPE) parameter.
A network node server is a network identifier (ID) qualified by a control point name.
Single values
- *SAME
- The value does not change.
- *NONE
- The current list of network node servers is cleared.
Other values (up to 5 repetitions)
Element 1: Server network ID
- *LCLNETID
- The value used is the current value of the Local network ID (LCLNETID) parameter at the time the node server is referred to.
- communications-name
- Specify the local network ID that will become the network node server.
Element 2: Control point name
- *ANY
- The first network node that offers services will become the network node server. Any network node with the same network ID as that specified for the Local network ID (LCLNETID) parameter can be a potential network node server.
- communications-name
- Specify the control point name of the network node server.
Top |
Alert status (ALRSTS)
Specifies whether local alerts are created. When alert status is active, alerts are created for all of the messages that have been defined as alertable and that report a permanent error with network lines, local devices or control units, or programming and operator errors.
- *SAME
- The value does not change.
- *ON
- Alerts are created by the system for all alert conditions, except unattended conditions.
- *OFF
- Alerts are not created by the system.
- *UNATTEND
- Alerts are created by the system for all alert conditions, including messages for which *UNATTEND is specified for the Alert options (ALROPT) parameter of the Add Message Description (ADDMSGD) or Change Message Description (CHGMSGD) command.
Top |
Alert logging status (ALRLOGSTS)
Specifies which alerts are logged.
- *SAME
- Alert logging does not change.
- *NONE
- No alerts are logged.
- *LOCAL
- Only locally created alerts are logged.
- *RCV
- Only alerts received from other nodes are logged.
- *ALL
- Both locally created alerts and alerts received from other nodes are logged.
Top |
Alert primary focal point (ALRPRIFP)
Specifies whether the system is an alert primary focal point. If the system is defined as a primary alert focal point, alerts are received from all network nodes explicitly defined in the sphere of control.
- *SAME
- The alert primary focal point does not change.
- *NO
- The system is not an alert primary focal point. This parameter cannot be changed from *YES to *NO if there is any node in the sphere of control that has a status of Active-in Sphere of Control or Add Pending-in Sphere of Control. Use the Display Sphere of Control Sts (DSPSOCSTS) command to see the status for all nodes in the sphere of control.
- *YES
- The system is defined as an alert primary focal point and provides focal point services to all nodes in the network that are explicitly defined in the sphere of control. If a system is defined as a focal point, *ALL or *RCV should be specified for the Alert logging status (ALRLOGSTS) parameter to ensure that alerts coming in from nodes in the sphere of control are logged.
Top |
Alert default focal point (ALRDFTFP)
Specifies whether the system is an alert default focal point. If the system is defined as a Default Focal Point, alerts are received from all nodes in the network which are not explicitly defined in the sphere of control of some other focal point node within the network.
- *SAME
- The alert default focal point does not change.
- *NO
- The system is not an alert default focal point. This parameter cannot be changed from *YES to *NO if there are any nodes in the sphere of control that have a status of Active-in Sphere of Control or Add Pending-in Sphere of Control. Use the Display Sphere of Control Sts (DSPSOCSTS) command to see the status for all nodes in the sphere of control.
- *YES
- The system is an alert default focal point, and provides focal point services to all nodes in the network which are not being serviced by an alert primary focal point or another alert default focal point. If a system is defined as a focal point, *ALL or *RCV should be specified for the Alert logging status (ALRLOGSTS) parameter to ensure that alerts coming in from nodes in the sphere of control are logged. If a system is defined as a focal point, the APPN node type must have the value *NETNODE.
Top |
Alert backup focal point (ALRBCKFP)
Specifies the name of the system that provides alert focal point services if the primary focal point is unavailable.
Single values
- *SAME
- This value does not change.
- *NONE
- The backup focal point is not defined.
Element 1: Network ID
- *LCLNETID
- The network ID of the backup focal point is same as that of the local system.
- communications-name
- Specify the network ID of the system that provides backup focal point services for alerts.
Element 2: Control point name
- communications-name
- Specify the control point name of the system that provides backup focal point services for alerts.
Top |
Alert focal point to request (ALRRQSFP)
Specifies the name of the system that is requested to provide alert focal point services.
Single values
- *SAME
- This value does not change.
- *NONE
- A focal point is not requested and the current focal point is revoked.
Element 1: Network ID
- *LCLNETID
- The network ID of the requested focal point is same as that of the local system.
- communications-name
- Specify the network ID of the system that is requested to provide focal point services for alerts.
Element 2: Control point name
- communications-name
- Specify the control point name of the system that is requested to provide focal point services for alerts.
Top |
Alert controller description (ALRCTLD)
Specifies the name of the controller through which alerts are sent on the alert controller session. Only a type HOST or APPC controller can be specified. The controller must be varied on for alert processing to be operational on the alert controller session, although it does not need to be varied on when this command is used.
- *SAME
- The value does not change.
- *NONE
- There is no alert controller description. Specifying *ON for the Alert status (ALRSTS) parameter and *YES for the Alert primary focal point (ALRPRIFP) parameter with *NONE for the controller description means that only local alerts are created and logged.
- name
- Specify the name of the controller that is used for alerts in an alert controller session. This controller is ignored if the system has a focal point (for example, if the node is in another system's sphere of control).
Top |
Alert hold count (ALRHLDCNT)
Specifies the maximum number of alerts that are created before the alerts are sent over the alert controller session (ALRCTLD network attribute). The alerts are held (queued) by the system until the specified number of alerts have been created. This parameter can be used to manage alerts that are sent over a limited resource by reducing the number of times alerts are sent.
Note: The ALRHLDCNT network attribute applies only when the ALRCTLD network attribute is used. When management services sessions, APPN, and sphere of control support are used, the ALRHLDCNT value is ignored.
- *SAME
- The hold alert count network attribute does not change.
- *NOMAX
- The alerts are held indefinitely. The current alert hold count is the maximum value. The alerts can be sent at a later time by changing the ALRHLDCNT value to a lower value.
- 0-32767
- Specify the maximum number of alerts that can be created before being sent. Alerts have a "held" status until the maximum is reached. If the value 0 is specified, alerts are sent as soon as they are created.
Top |
Alert filter (ALRFTR)
Specifies the qualified name of the alert filter used by the alert manager when processing alerts. The alert filter must exist in the system auxiliary storage pool (ASP) or in a basic user ASP.
Single values
- *SAME
- The value does not change.
- *NONE
- An alert filter is not used.
Qualifier 1: Alert filter
- name
- Specify the name of the alert filter.
Qualifier 2: Library
- *LIBL
- All libraries in the thread's library list are searched until a match is found.
- *CURLIB
- The current library for the thread is used to locate the object. If no library is specified as the current library for the thread, the QGPL library is used.
- name
- Specify the library where the alert filter is located.
Top |
Message queue (MSGQ)
Specifies the name and library of the message queue where messages received through the SNADS network are sent for users who have no message queue specified in their user profile, or whose message queue is not available. The message queue must exist in the system auxiliary storage pool (ASP) or in a basic user ASP.
Single values
- *SAME
- The message queue does not change.
Qualifier 1: Message queue
- name
- Specify the name of the message queue.
Qualifier 2: Library
- *LIBL
- All libraries in the thread's library list are searched until a match is found.
- *CURLIB
- The current library for the thread is used to locate the object. If no library is specified as the current library for the thread, the QGPL library is used.
- name
- Specify the library where the message queue is located.
Note: When *LIBL is used as the library name, the library list of the thread calling this command is searched to find a message queue with the object name specified. If the message queue is found, the name of the library in which it is found is used as the name stored. If the message queue is not found, an exception is signaled and no network attributes are changed. When the library name or *CURLIB is specified, this command attempts to find the message queue. If the message queue cannot be found in the library specified, a diagnostic message is sent. If all other parameters on the command were specified correctly, the MSGQ network attribute is changed to the qualified message queue name, whether or not this command is able to find the message queue in the library specified.
Top |
Output queue (OUTQ)
Specifies the name and library of the output queue to which spooled files received through the SNADS network are sent for users whose output queue is not available.
Single values
- *SAME
- The output queue does not change.
Qualifier 1: Output queue
- name
- Specify the name and library of the output queue.
Qualifier 2: Library
- *LIBL
- All libraries in the thread's library list are searched until a match is found.
- *CURLIB
- The current library for the thread is used to locate the object. If no library is specified as the current library for the thread, the QGPL library is used.
- name
- Specify the library where the output queue is located.
Note: When *LIBL is used as the library name, the library list of the thread calling this command is searched to find an output queue with the object name specified. If the output queue is found, the name of the library where it is found is used in the name stored. If the output queue is not found, an exception is signaled, and no network attributes are changed.
When the library name or *CURLIB is specified, this command attempts to find the output queue. If the output queue cannot be found in the specified library, a diagnostic message is sent. If all other parameters on the command were specified correctly, the OUTQ network attribute is changed to the output queue name, whether or not this command is able to find the output queue in the specified library.
Top |
Network job action (JOBACN)
Specifies the action taken for input streams received through the SNADS network by the system.
- *SAME
- The action taken for an input stream does not change.
- *REJECT
- The input stream is rejected by the system. This action allows you to secure your system from job streams received through the network.
- *FILE
- The input stream is filed in the queue of network files received by the user to whom it was sent. That user can then view, end, or receive the input stream, or submit the input stream to a job queue.
- *SEARCH
- The table of network job entries is searched to determine the action taken for the input stream.
Top |
Maximum hop count (MAXHOP)
Specifies the maximum number of times in a SNADS network that a distribution queue entry originating at this node can be received and routed on the path to its final destination. If this number is exceeded, the distribution queue entry is ended, and a feedback status is sent back to the sender.
- *SAME
- The maximum number of times that a distribution queue entry can be received and routed does not change.
- 1-255
- Specify the maximum number of times that a distribution queue entry can be received and routed before it is ended.
Top |
DDM/DRDA request access (DDMACC)
Specifies how the system processes distributed data management (DDM) and Distributed Relational Database Architecture (DRDA) requests from remote systems for access to the data resources of the system. The DDM or DRDA connections refer to APPC conversations or active TCP/IP or OptiConnect connections. Changes to this parameter are immediate and apply to DRDA, DDM, or DB2 Multisystem applications. However, jobs that are currently running on the system do not use the new value. The DDMACC value is accessed only when a job is first started.
If a program name is specified, the program must exist in the system auxiliary storage pool (ASP) or in a basic user ASP.
Single values
- *SAME
- The method for processing DDM requests from remote systems does not change.
- *REJECT
- This system does not allow DDM and DRDA requests from remote systems. However, this system can still use DDM or DRDA to access files or SQL tables on remote systems. Source (client) systems cannnot access files or SQL tables on any other system that specifies *REJECT.
- *OBJAUT
- If the user profile associated with the DDM or DRDA job is authorized to the files, all file or remote SQL requests are accepted. Object authorities such as read, write, or update must also exist for the files.
Qualifier 1: DDM/DRDA request access
- name
- Specify the name of the validation program.
Qualifier 2: Library
- *LIBL
- All libraries in the thread's library list are searched until a match is found.
- *CURLIB
- The current library for the thread is used to locate the object. If no library is specified as the current library for the thread, the QGPL library is used.
- name
- Specify the library where the validation program is located.
Note: When *LIBL is used as the library name, the library list of the thread calling the command is searched to find the program. If the program is found, the library containing it is used in the stored name. If the program is not found, an exception is signaled, and no network attributes are changed.
When the library name or *CURLIB is specified, the command attempts to find the program. If the program is found, the DDMACC network attribute changes to the qualified program if all other parameters on the command were specified correctly. If the program cannot be found, a diagnostic message is sent.
The program name identifies a customer validation program that can supplement system object level security. The user security exit program parameter list is also used by personal computer Support/38 applications. The user-exit program can restrict user access to public (*PUBLIC) and privately authorized files. The target distributed data manager support calls the user program each time a file is referred to. The user exit program indicates to DDM whether the request should proceed or end.
Top |
Client request access (PCSACC)
Specifies how IBM i Access for Windows requests are handled. You must specify a special value or program name which dictates how the requests are to be handled. This permits greater control over IBM i Access for Windows applications. Changes to this parameter are immediate. However, jobs that are currently running on the system do not use the new value. The PCSACC value is accessed only when a job is first started.
If a program name is specified, the program must exist in the system auxiliary storage pool (ASP) or in a basic user ASP.
Single values
- *SAME
- This value does not change.
- *REJECT
- The system rejects all requests from the client.
- *OBJAUT
- Normal object authorizations are checked for this client request (for example, authorization to retrieve data from a database file for a transfer facility request).
- *REGFAC
- The system uses the system's registration facility to determine which exit program (if any) to run. If no exit program is defined for an exit point and this value is specified, *OBJAUT is used.
Qualifier 1: Client request access
- name
- Specify the name of the program.
Qualifier 2: Library
- *LIBL
- All libraries in the thread's library list are searched until a match is found.
- *CURLIB
- The current library for the thread is used to locate the object. If no library is specified as the current library for the thread, the QGPL library is used.
- name
- Specify the library where the program is located.
Note: When *LIBL is used as the library name, the library list of the thread calling the command is searched to find the program. If the program is found, the library containing it is used in the stored name. If the program is not found, an exception is signaled, and no network attributes are changed.
When the library name or *CURLIB is specified, the command attempts to find the program. If the program is found, the PCSACC network attribute changes to the qualified program name if all other parameters on the command were specified correctly. If the program is not found, a diagnostic message is sent.
The program name is the name of the customer-supplied IBM i Access for Windows host system application exit program that can supplement system object level security. This user-exit program can restrict requests handled from the client. Each personal computer support application calls the exit program for requests from the client. Two parameters are passed to the user-exit program: the first describes the client request (which application and what kind of request). The second is used by the exit program to indicate to the client support application whether this client request must be handled.
Top |
Default ISDN network type (DFTNETTYPE)
Specifies the system default value for the Integrated Services Digital Network (ISDN) network type. The operating system no longer uses this network attribute. Changes made to this network attribute have no effect.
Top |
Default ISDN connection list (DFTCNNLST)
Specifies the system default value for the Integrated Services Digital Network (ISDN) connection list. The operating system no longer uses this network attribute. Changes made to this network attribute have no effect.
Top |
Allow AnyNet support (ALWANYNET)
Specifies the network attribute that allows the Communications APIs to use other communication transports that are not native for the API. Examples include ICF over TCP/IP or Sockets over SNA.
- *SAME
- The value does not change.
- *NO
- SNA transport is not used.
- *YES
- SNA transport is used.
Top |
Network server domain (NWSDOMAIN)
Specifies the LAN Server domain to which all Integrated PC Servers, also known as File Server Input/Output Processors (FSIOP) on the system belong.
- *SAME
- The value does not change.
- *SYSNAME
- The current system name is used.
- character-value
- Specify a 1 to 8 character system name.
Top |
Allow APPN virtual support (ALWVRTAPPN)
Specifies the network attribute that allows APPN sessions and devices to use virtual controllers.
Note: The setting of this parameter has nothing to do with sessions using HPR transport tower support--only APPN (non-HPR) session traffic is affected by this parameter setting; if sessions are using HPR transport tower support they will use virtual controllers, regardless of the setting of this network attribute.
- *SAME
- The value does not change. Allowing APPN sessions and devices to use virtual controllers is shipped with a value of *NO.
- *NO
- Virtual APPN controllers are not used.
- *YES
- Virtual APPN controllers are used.
Top |
Allow HPR transport tower (ALWHPRTWR)
Specifies the network attribute that allows the use of HPR transport tower support for APPN session traffic.
- *SAME
- The value does not change. The use of HPR transport tower support for APPN session traffic is shipped with a value of *NO.
- *NO
- HPR transport tower is not used.
- *YES
- HPR transport tower is used.
Top |
Virtual ctl autocreate dev (VRTAUTODEV)
Specifies the upper limit for number of automatically created APPC devices on virtual controllers.
- *SAME
- The value does not change. The limit for the number of automatically created APPC devices on virtual controllers is shipped with a value of 100.
- 1-254
- Specify the limit for the number of automatically created APPC devices on virtual controllers. If the number of devices attached to a virtual controller is equal or greater than the specified value, no additional APPC devices will be automatically created for that virtual controller. Additional devices beyond this limit may still be created manually.
Top |
HPR path switch timers (HPRPTHTMR)
Specifies the amount of time, in minutes, to allow for a path switch attempt of an RTP connection. Four positional values can be specified to control the time allowed based on the type of session traffic:
- Network Priority Traffic
- High Priority Traffic
- Medium Priority Traffic
- Low Priority Traffic
Element 1: Network priority
- *SAME
- The value does not change. The amount of time to allow for a path switch attempt of an RTP connection that has network transmission priority is shipped with a value of 1 minute.
- *NONE
- No path switch is allowed.
- 1-10000
- Specify the amount of time in minutes to allow for a path switch attempt of an RTP connection that has network transmission priority.
Element 2: High priority
- *SAME
- The value does not change. The amount of time to allow for a path switch attempt of an RTP connection that has high transmission priority is shipped with a value of 2 minutes.
- *NONE
- No path switch is allowed.
- 1-10000
- Specify the amount of time in minutes to allow for a path switch attempt of an RTP connection that has high transmission priority.
Element 3: Medium priority
- *SAME
- The value does not change. The amount of time to allow for a path switch attempt of an RTP connection that has medium transmission priority is shipped with a value of 4 minutes.
- *NONE
- No path switch is allowed.
- 1-10000
- Specify the amount of time in minutes to allow for a path switch attempt of an RTP connection that has medium transmission priority.
Element 4: Low priority
- *SAME
- The value does not change. The amount of time to allow for a path switch attempt of an RTP connection that has low transmission priority is shipped with a value of 8 minutes.
- *NONE
- No path switch is allowed.
- 1-10000
- Specify the amount of time in minutes to allow for a path switch attempt of an RTP connection that has low transmission priority.
Top |
Allow add to cluster (ALWADDCLU)
Specifies whether this system will allow another system to add it as a node in a cluster.
- *SAME
- The value does not change. The system is shipped with a value of *NONE.
- *NONE
- No other system can add this system as a node in a cluster.
- *ANY
- Any other system can add this system as a node in a cluster.
- *RQSAUT
- Any other system can add this system as a node in a cluster only after the cluster add request has been authenticated.
Top |
Modem country or region ID (MDMCNTRYID)
Specifies the country or region identifier associated with a modem. The list of valid modem country or region identifiers will be displayed when F4 is pressed while prompting for this parameter.
MDMCNTRYID defines the country-specific or region-specific default characteristics for modems which are internal to system I/O adapters. This value must be configured correctly to insure proper operation and, in some countries or regions, meet legal requirements. The adapter will fail the vary on of the line if modem country or region ID is not set.
- *SAME
- The value does not change. The system is shipped with blanks.
- character-value
- Specify the country or region identifier to be used by a modem.
Top |
Examples
Example 1: Changing the Pending System Name
CHGNETA SYSNAME(SYSTEST) ALRSTS(*ON) ALRPRIFP(*YES) ALRLOGSTS(*LOCAL)
This command changes the pending system name. The current system name is changed at the next IPL. Local alerts are generated and logged and the system is a primary focal point.
Example 2: Changing the Node Servers
CHGNETA LCLCPNAME(CPNAME) LCLNETID(NETNAME) NETSERVER((*LCLNETID BOSTON) (MINN ROCHEST) (MAINE BANGOR))
This command changes the name of the local control point, the network ID, and the list of network node servers. The servers are used only if the node type is *ENDNODE or *BEXNODE.
Example 3: Clearing the List of Node Servers
CHGNETA NETSERVER(*NONE) DDMACC(DDMLIB/DDMPGM)
This command clears the list of network node servers and sets the name of the DDM access program.
Example 4: Implementing the APPN Virtual Object Model
CHGNETA ALWVRTAPPN(*YES)
This command causes any future APPN devices and sessions to use virtual controllers.
Example 5: Allowing HPR Transport Tower for APPN Sessions
CHGNETA ALWHPRTWR(*YES) HPRPTHTMR(1 2 4 8)
This command enables APPN session traffic to use HPR transport tower support when possible. It also resets the HPR path switch timers to the default values.
Top |
Error messages
*ESCAPE Messages
- CPFE018
- Subsystem QSYSWRK not active or being ended.
- CPFE033
- IP over IPX not activated.
- CPFE034
- IP over IPX activated; however errors occurred.
- CPFE035
- IP over IPX deactivated; however errors occurred.
- CPF1001
- Wait time expired for system response.
- CPF1007
- Character is not valid for value &1.
- CPF1066
- Network attributes not changed.
- CPF1097
- No authority to change certain network attributes.
- CPF1844
- Cannot access network attribute &1.
- CPF91EB
- Filter type &3 not correct for this operation.
- CPF9801
- Object &2 in library &3 not found.
- CPF9807
- One or more libraries in library list deleted.
- CPF9808
- Cannot allocate one or more libraries on library list.
- CPF9899
- Error occurred during processing of command.
![Start of change](delta.gif)
![End of change](deltaend.gif)
Top |