CHGNETA (Change Network Attributes)

CHGNETA Command syntax diagram

 

Purpose

The Change Network Attributes (CHGNETA) command changes the network attributes of a system.

Network attributes are saved by the Save System (SAVSYS) command. Network attributes are optionally restored to the system when the operating system is installed. The following network attributes are not restored if they are saved from another system: system name, local network ID, local control point name, default local location name, default mode, node type, maximum number of intermediate sessions, route addition resistance, network node servers, alert primary focal point, and alert default focal point, allow virtual controllers, allow HPR transport tower support, APPC device limit, and the four HPR path switch timers.

When a new default local location name, control point name, or network ID is specified, a check is made against the remote location list to determine whether the new qualified local location name or control point name already exists on the list. If it does, an error occurs and no network attributes change.

If there are synchronous datalink control (SDLC), Frame Relay Direct, or IDLC line descriptions that are varied on and the (SDLC) line descriptions that are varied on and the short hold mode node type (SHMNODE) parameter has a value of *T21, the physical interface (INTERFACE) parameter has a value of *X21, and the connection type (CNN) parameter has a value of *SHM, an attempt to change the network ID and the control point name causes an error, and no network attributes change.

An attempt to change the network atributes for

• the local control point name,
• the network ID,
• HPR transport tower support or
• the node type

will fail if there are any APPC or HOST controllers active which have the APPN option set to *YES and a link type of anything other than *DLUR. If this failure occurs, no network attributes will change.

If a new default local location name or network ID is entered, devices are checked to ensure that descriptions are still valid. When a new default local location name is entered, the entry is checked against existing device descriptions with LCLLOCNAME(*NETATR) to ensure that the LCLLOCNAME/RMTLOCNAME pair has different values. If either the default local location or network ID is changed, all devices attached to the same controller with LCLLOCNAME(*NETATR) or RMTNETID(*NETATR) are checked to ensure that each device description remains unique. If an error occurs, no network attributes change.

When the option is selected to allow APPN traffic to use virtual controllers, APPC devices with APPN(*YES) attached to real controllers will no longer be allowed to be varied on. An equivalent device attached to a virtual controller will instead be created and/or used.

Restrictions: This command is shipped with public *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 *ALLOBJ and *IOSYSCFG authority to change the network attributes JOBACN, DDMACC, and PCSACC.

A user is required to have *IOSYSCFG authority to change the network attribute ALWADDCLU.

More information on this command is in the Work Management book or the Communications Management book.

 

Optional Parameters

SYSNAME

Specifies the name assigned to the system. The name can contain up to 8 alphanumeric characters. The characters that are allowed are uppercase letters A through Z, 0 through 9, or special characters @, #, $, and embedded blanks. Embedded blanks must be enclosed in single quotation marks (') in the same manner as other character strings. Leading blanks are not allowed.

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.

Note:

The use of the @, #, and $ characters is not recommended because they are not part of an invariant character set and are not available on all keyboards.

*SAME: The value does not change.

system-name: Specify the name that identifies the system. The pending system name is changed when a request to change the system name is issued. The pending system name becomes the current system name at the next IPL of the system. If the system name is changed during the IPL, the name specified becomes the current system name.

LCLNETID

Specifies the local network identifier (ID) assigned to the system. The name can contain up to 8 alphanumeric characters. The first character must be an uppercase letter A through Z, or special character $, #, or @ and cannot contain blanks, plus signs (+), periods (.), or underscores (_). More information on these requirements is in APPC, APPN, and HPR topic in the Information Center.

*SAME: The value does not change.

local-network-ID: Specify the ID of the local network. The network ID is changed if all APPC controllers with the APPN parameter set to *YES are varied off.

LCLCPNAME

Specifies the name of the local control point for the system. The name can contain up to 8 alphanumeric characters. The first character must be an uppercase letter A through Z, or special character $, #, or @ and cannot contain blanks, plus signs (+), periods (.), or underscores (_). More information on these requirements is in APPC, APPN, and HPR topic in the Information Center. If the local control point name is not set, it is defaulted at IPL to the machine serial number with the first character changed (if necessary) to an alphabetic character.

*SAME: The value does not change.

local-control-point-name: Specify the local control point name for the system. The control point name is changed if all APPC controllers with the APPN parameter set to *YES are varied off.

LCLLOCNAME

Specifies the local location name.

Note:

The name may contain up to 8 alphanumeric characters. The first character must be an uppercase letter A through Z, or special character $, periods (.), or underscores (_). If the default local location name is not set, it is defaulted at IPL to the machine serial number (with the first character changed, if necessary, to an alphabetic character). More information is in APPC, APPN, and HPR topic in the Information Center.

*SAME: The value does not change.

default-local-location-name: Specify the default local location name for the system.

DFTMODE

Specifies the default mode name for the system. The name can contain up to 8 alphanumeric characters in length. The first character must be an uppercase letter A through Z, or special character $, #, or @ and cannot contain blanks, plus signs (+), periods (.), or underscores (_). More information is in APPC, APPN, and HPR topic in the Information Center.

*SAME: The value does not change.

default-mode-name: Specify the default mode name. Mode names SNASVCMG and CPSVCMG are not allowed. Specifying BLANK for the default mode name is the same as specifying a mode name of all blanks.

NODETYPE

Specifies the APPN node type. More information is in APPC, APPN, and HPR topic in the Information Center.

*SAME: The value does not change.

*ENDNODE: The node does not provide network services to other nodes, but it can participate in the APPN network by using the services of an attached network server or it can operate in a peer-to-peer environment similar to migration end nodes. NODETYPE(*ENDNODE) cannot be specified if either ALRPRIFP(*YES) or ALRDFTFP(*YES) is specified.

*NETNODE: The node provides intermediate routing and route selection services and distributed directory services for local users to end nodes and migration end 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.

DTACPR

Specifies the level of data compression used when the iSeries 400 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 changed to a lower compression level 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 requests are the configured levels. If data compression levels are changed by the remote system, they cannot 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 accept 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.

line-speed: Specify the maximum line speed 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 used for the session as if *REQUEST is specified. Otherwise, compression is used for the session as if *ALLOW is specified. Valid values range from 1 through 2147483647 in bits per second (bps).

DTACPRINM

Specifies the level of data compression to request when the iSeries 400 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 iSeries 400 is an SNA intermediate node.

*REQUEST: The remote systems are requested to compress data when the iSeries 400 is an SNA intermediate node.

line-speed: Specify a line speed. 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. Valid values range from 1 through 2147483647 bits per second (bps).

MAXINTSSN

Specifies the maximum number of APPN intermediate sessions. This parameter is used only if NODETYPE(*NETNODE) or NODETYPE(*BEXNODE) is specified. More information is in APPC, APPN, and HPR topic in the Information Center.

*SAME: The value does not change.

maximum-number-of-intermediate-sessions: Specify the maximum number of intermediate sessions. Valid values range from 0 through 9999.

RAR

Specifies the APPN route addition resistance (RAR). This parameter is used only if NODETYPE(*NETNODE) or NODETYPE(*BEXNODE) is specified. More information is in APPC, APPN, and HPR topic in the Information Center.

*SAME: The value does not change.

route-addition-resistance: Specify the RAR. Valid values range from 0 through 255.

NETSERVER

Specifies the APPN network node servers. This parameter is used only if *ENDNODE or *BEXNODE is specified on the NODETYPE parameter. More information is in APPC, APPN, and HPR topic in the Information Center.

A network node server is a network identifier (ID) qualified by a control point name. Up to five network node servers can be specified. A network node server must be specified by using two values (one value for each element): the network ID and the control point name. Name restrictions are the same as those for LCLNETID and LCLCPNAME.

*SAME: The value does not change.

*NONE: The list of network node servers is cleared. This value can be specified as the only value for NETSERVER.

Element 1: Server Network ID

*LCLNETID: The value used depends on the value of the network ID network attribute (LCLNETID) at the time the server is referenced.

network-ID: Specify the local network ID that becomes the network node server.

Element 2: Control Point Name

*ANY: The first network node that offers services becomes the network node server. Any network node with the same network ID as that specified on the LCLNETID parameter can be a network node server.

control-point-name: Specify the control point name of the network node server.

ALRSTS

Specifies whether local alerts are generated. When alert processing is active, alerts are generated when a permanent error is encountered with local devices or control units, network lines, devices, and control units, and when programming and operator errors occur. More information is in the Alerts Support book and APPC, APPN, and HPR topic in the Information Center.

*SAME: The value does not change.

*ON: Alert processing is started. The system generates alerts for all alert conditions except unattended conditions.

*UNATTEND: The system generates alerts for all alert conditions including those that have the alert indicator in the message description set *UNATTEND.

*OFF: No monitoring of errors occurs.

ALRLOGSTS

Specifies how alerts are logged by the iSeries 400. More information on the logging of system alerts is in the Alerts Support book.

*SAME: The value does not change.

*NONE: No alerts are logged.

*LOCAL: Only locally generated alerts are logged.

*RCV: Only alerts received from other systems are logged.

*ALL: Both locally generated alerts and alerts received from other systems are logged.

ALRPRIFP

Specifies whether the system is an alert primary focal point. If the system is defined as a primary focal point, alerts are received from all network nodes explicitly defined in the sphere of control. More information is in the Alerts Support book and APPC, APPN, and HPR topic in the Information Center.

*SAME: The value does not change.

*NO: The system is not an alert primary focal point. Information about when this parameter can be changed from *YES to *NO is in the Alerts Support book. Use the Display Sphere of Control Status (DSPSOCSTS) command to see the status for all systems in the sphere of control.

*YES: The system is defined as an alert primary focal point and it provides focal point services to all systems in the network that are explicitly defined in the sphere of control. If a system is defined as a focal point, ALRLOGSTS(*ALL) or ALRLOGSTS(*RCV) must be specified to ensure that alerts coming in from nodes in the sphere of control are logged.

ALRDFTFP

Specifies whether the system is a default alert focal point. If the system is defined as a default alert focal point, alerts are received from all network systems not explicitly defined in the sphere of control of some other focal point system within the network. More information is in the Alerts Support book.

*SAME: The value does not change.

*NO: The system is not a default alert focal point. Information about when this parameter can be changed from *YES to *NO is in the Alerts Support book. Use the Display Sphere of Control Status (DSPSOCSTS) command to show the status for all systems in the sphere of control.

*YES: The system is a default alert focal point and it provides focal point services to all network systems not being serviced by either a primary focal point or another default focal point. If a system is defined as a focal point, NODETYPE(*NETNODE) must be specified.

ALRBCKFP

Specifies the name of the system that provides alert focal point services if the primary focal point is unavailable.

*SAME: The 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.

network-ID: Specify the network ID of the system that provides backup focal point services for alerts.

Element 2: Control Point Name

control-point-name: Specify the control point name of the system that provides backup focal point services for alerts.

ALRRQSFP

Specifies the name of the system that is requested to provide alert focal point services.

*SAME: The value does not change.

*NONE: A focal point is not requested. 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.

network-ID: Specify the network ID of the system that is requested to provide focal point services for alerts.

Element 2: Control Point Name

control-point-name: Specify the control point name of the system that is requested to provide focal point services for alerts.

ALRCTLD

Specifies the name of the controller through which alerts are sent on the alert controller session. Only a 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. More information about the alert controller session is in the Alerts Support book.

*SAME: The value does not change.

*NONE: No alert controller is described.

controller-name: Specify the name of the controller being used for alerts in an alert controller session. This controller is ignored if the system has a primary or default alert focal point (if, for example, the node is in another system's sphere of control).

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 is valid only when the ALRCTLD parameter is specified. When management services sessions, APPN, and sphere of control support are used, the ALRHLDCNT parameter is ignored.

*SAME: The value 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.

alert-hold-count: 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. Valid values range from 0 through 32767.

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.>

*SAME: The value does not change.

*NONE: An alert filter is not used.

The name of the alert filter can be qualified by one of the following library values:

*LIBL: All libraries in the job's library list are searched until the first match is found.

*CURLIB: The current library for the job is searched. If no library is specified as the current library for the job, the QGPL library is used.

library-name: Specify the name of the library to be searched.

filter-name: Specify the name of the alert filter.

MSGQ

Specifies the qualified name of the message queue where messages received through the SNADS network are sent for users with no message queue specified in their user profile, or whose message queue is not available.

The message queue must exist in the system ASP or in a basic user ASP.>

*SAME: The value does not change.

The possible library values are:

*LIBL: The library list is used to locate the message queue.

When *LIBL is used as the library name, the library list of the job calling this command is searched to find a message queue with the specified object name. If the message queue is found, the name of the library in which it is found is used in the fully qualified name and it is stored. If the message queue is not found, an exception is signaled and no network attributes are changed.

*CURLIB: The current library for the job is used to locate the message queue. If no library is specified as the current library for the job, the QGPL library is used.

library-name: Specify the name of the library where the message queue is located.

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 specified library, a diagnostic message is sent. If all other parameters on the command are specified correctly, and whether or not this command is able to find the message queue in the library specified, the MSGQ network attribute is changed to the qualified message queue name.

message-queue-name: Specify the name of the message queue.

OUTQ

Specifies the qualified name of the output queue.

*SAME: The value does not change.

The possible library values are:

*LIBL: The library list is used to locate the output queue.

When *LIBL is used as the library name, the library list of the job calling this command is searched to find an output queue with the specified object name. If the output queue is found, the name of the library in which it is found is used in the qualified name and it is stored. If the output queue is not found, an exception is signaled, and no network attributes are changed.

*CURLIB: The current library for the job is used to locate the output queue. If no library is specified as the current library for the job, the QGPL library is used.

library-name: Specify the name of the library where the output queue is located.

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, and whether or not this command finds the output queue in the specified library, the OUTQ network attribute is changed to the output queue name.

output-queue-name: Specify the name of the output queue.

JOBACN

Specifies the action taken for job input streams received through the SNADS network by the system.

*SAME: The value does not change.

*REJECT: The input stream is rejected by the system. This action allows the user to secure the system from input streams received through the network.

*FILE: The input stream is filed in the queue of network files received for the user to which it was sent. That user can then look at, end, or receive the input stream, or submit it to a job queue.

*SEARCH: The table of network job entries is searched to determine the action taken for the input stream.

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 canceled, and a feedback status is sent to the sender.

*SAME: The value does not change.

maximum-hop-count: Specify the maximum number of times that a distribution queue entry can be received and routed before it is canceled. Valid values range from 1 through 255.

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 and 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. You must specify a special value or program name which dictates how the requests are to be handled.

If a program name is specified, the program must exist in the system ASP or in a basic user ASP.>

*SAME: The value 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 cannot access files or SQL tables on an iSeries 400 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.

The possible library values are:

*LIBL: The library list is used to locate the validation program.

If *LIBL is used as the library name, the library list of the job calling this command is searched to find the program name with the specified object name. If the program name is found, the name of the library in which it is found is used in the fully qualified name and it is stored. If the program name is not found, an error message is sent and no network attributes are changed.

*CURLIB: The current library for the job is used to locate the validation program. If no library is specified as the current library for the job, the QGPL library is used.

library-name: Specify the name of the library where the validation program is located.

When the library name or *CURLIB is specified, this command attempts to find the program name. If the program name cannot be found in the specified library, a diagnostic message is sent to the user. If this command is able to find the program name in the specified library, the DDMACC network attribute is changed to the qualified program name, if all other parameters on the command are specified correctly.

program-name: Specify the name of the validation program.

The program name is the name of the customer validation program that can supplement system object level security. This user-exit program can restrict user access to *PUBLIC and privately authorized files. The target DDM support calls the user program each time a file is read. The user exit program indicates to DDM whether the request must proceed or end. The iSeries 400 object level security still applies. More information about this program is in the File Management topic in the Information Center.

PCSACC

Specifies how Client Access/400 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 Client Access/400 applications. Changes to this parameter are immediate. However, jobs currently running on the system do not use the new value. The PCSACC value is used only when a job is first started.

If a program name is specified, the program must exist in the system ASP or in a basic user ASP.>

*SAME: The 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.

The possible library values are:

*LIBL: The library list is used to locate the program.

When *LIBL is used as the library name, the library list of the job calling this command is searched to find the program name with the specified object name. If the program name is found, the name of the library in which it is found is used in the fully qualified name and it is stored. If the program name is not found, an error message is sent and no network attributes are changed.

*CURLIB: The current library for the job is used to locate the program. If no library is specified as the current library for the job, the QGPL library is used.

library-name: Specify the name of the library where the program is located.

When the library name or *CURLIB is specified, this command attempts to find the program name. If the program name cannot be found in the specified library, a diagnostic message is sent to the user. If all other parameters on the command were specified correctly, and whether or not this command is able to find the program name in the specified library, the PCSACC network attribute is changed to the qualified program name.

program-name: Specify the name of the program.

The program name is the name of the customer-supplied Client Access/400 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.

DFTNETTYPE

Specifies the system default value for the integrated services digital network (ISDN) network type.

This parameter affects the creation of network interface and connection list objects on the system. The value specified here becomes the default network type (*NETTYPE) for connection lists and network interface descriptions created using the Create Connection List (CRTCNNL) command and the Create Network Interface description for ISDN (CRTNWIISDN) command.

*SAME: The value does not change.

*ATT: This value is used when attaching to an ISDN that uses an AT&T interface.

*DBP1TR6: This value is used when attaching to an ISDN controlled by Germany's Post Telephone and Telegraph Administration (PPT). (Deutsche Bundespost 1TR6).

*ETSI: This value is used when attaching to the ISDN that uses a European interface (ETSI, also known as EuroISDN standard).

*JAPAN: This value is used when attaching to an ISDN that uses a Japanese interface.

*NISDN: This value is used when attaching to an ISDN that uses a North American interface.

*NORTEL: This value is used when attaching to an ISDN that uses the Northern Telecom interface.

*NORTHAMT1: This value is used when attaching to a channelized North American T1 interface.

DFTCNNLST

Specifies the system default value for the ISDN connection list. The connection list contains information for identifying authorized incoming calls.

This parameter affects the creation of ISDN Data Link Control (IDLC) line description objects on the system. The value specified here becomes the default connection list for line descriptions created using the Create Line Description for IDLC (CRTLINIDLC) command.

*SAME: The value does not change.

connection-list-name: Specify the name of the default connection list.

ALWANYNET

Specifies the network attribute that allows iSeries 400 Communications APIs to use other communication transports that are not native for that 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.

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.

system-name: Specify a 1 to 8-character system name.

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.

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.

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.

autocreated-device-limit: 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. Valid values range from 1 through 254.

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.

network-priority: Specify the amount of time in minutes to allow for a path switch attempt of an RTP connection that has network transmission priority. Valid values range from 1 through 10000.

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.

high-priority: Specify the amount of time in minutes to allow for a path switch attempt of an RTP connection that has high tranmission priority. Valid values range from 1 through 10000.

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.

medium-priority: Specify the amount of time in minutes to allow for a path switch attempt of an RTP connection that has medium transmission priority. Valid values range from 1 through 10000.

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.

low-priority: Specify the amount of time in minutes to allow for a path switch attempt of an RTP connection that has low tranmission priority. Valid values range from 1 through 10000.

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.

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 iSeries 400 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.

modem-country-or-region-ID: Specify the country or region identifier to be used by a modem.

Examples for CHGNETA

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: 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 5: 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 6: Implementing the APPN Virtual Object Model

CHGNETA  ALWVRTAPPN(*YES)

This command causes any future APPN devices and sessions to use virtual controllers.

Example 7: 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.

Error messages for CHGNETA

*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.

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.