ADDCFGLE (Add Configuration List Entries)

ADDCFGLE Command syntax diagram

 

Purpose

The Add Configuration List Entries (ADDCFGLE) command adds entries to a configuration list.

Note:

You can also use an option on the full screen entry display of the Work with Configuration Lists (WRKCFGL) command to add, change, or remove entries in an existing list except for the configuration lists of type *APPNDIR, *APPNSSN, and *SNAPASTHR.

 

Required Parameters

TYPE

Specifies the type of configuration list entry being added.

*APPNDIR: An advanced peer-to-peer networking* (APPN*) directory search filter configuration list is used.

*APPNLCL: An APPN local location list is used. Up to 476 APPN local location entries are allowed in the configuration list (using the CHGCFGL and CRTCFGL commands).

*APPNRMT: An APPN remote location list is used. Up to 1898 APPN remote location entries are allowed in the configuration list (using the CHGCFGL and CRTCFGL commands).

*APPNSSN: An APPN session end point filter configuration list is used.

*ASYNCADR: An asynchronous network address list is used. Up to 294 asynchronous network address entries are allowed in the configuration list.

*ASYNCLOC: An asynchronous remote location list is used. Up to 32000 asynchronous remote location entries are allowed in the configuration list.

*RTLPASTHR: A retail pass-through list is used. Up to 450 retail pass-through entries can be specified in the configuration list.

*SNAPASTHR: An SNA pass-through list is used. Up to 254 SNA pass-through entries can be specified in the configuration list.

CFGL

Specifies the name of the configuration list. This parameter is valid only when *ASYNCADR is specified on the TYPE parameter. Only one of the other configuration list types is allowed on a system. The list types have system-supplied names: QAPPNDIR, QAPPNLCL, QAPPNRMT, QAPPNSSN, QASYNCADR, QASYNCLOC, QRTLPASTHR, QSNAPASTHR.

 

Optional Parameters

APPNLCLE

Specifies the APPN local location entry. This value is required if *APPNLCL is specified for the TYPE parameter.

Up to 476 entries can be specified for this parameter, but only 50 entries can be specified at a time. An entry consists of a value from the local location name and the entry description.

Element 1: Local Location Name

local-location-name: Specify the location name of the local system. This name is used by APPN support to determine whether the request being received in is for this system or another system in the network. The local location name must be unique; it cannot already exist as a remote location name that is used by configuration list QAPPNRMT and it cannot be specified on another system as a local location in the same APPN network.

Element 2: Text Description

*BLANK: Text is not specified.

'entry-description': Specify a short description of 20 characters or less for each local entry.

APPNRMTE

Specifies the APPN remote location entry. This value is required if *APPNRMT is specified for the TYPE parameter. Up to 1898 entries can be specified for this parameter, but only 50 entries can be specified at a time. An entry consists of a value from each of the following elements. A value must be specified for each of the 11 elements for each entry.

Element 1: Remote Location Name

*ANY: The system potentially accepts all requests sent to it.

generic*-remote-location-name: Specify the generic name (part of a name followed by an asterisk) of the remote location(s) to be changed. The generic location name allows one directory entry to be defined for all locations, on a single control point, with a name that matches the characters preceding an *.

remote-location-name: Specify the full name of a remote location.

Element 2: Remote Network Identifier

*NETATR: The LCLNETID value specified in the system network attributes is used.

*NONE: The remote network identifier is not specified.

remote-network-identifier: Specify the network identifier of the network in which the remote location resides.

Element 3: Local Location Name

*NETATR: The LCLLOCNAME value specified in the system network attributes is used.

local-location-name: Specify the location name on the local system. This name is used by APPN support to match a local/remote location pair entry.

Element 4: Control Point Name

*NONE: There is no control point name.

control-point-name: Specify the name of the control point that provides network functions for the remote location. This field is required if the entry is either a generic name or *ANY.

Element 5: Control Point Network Identifier

*NETATR: The LCLNETID value specified in the system network attributes is used.

control-point-network-identifier: Specify the network identifier in which the control point resides.

Element 6: Location Password

*NONE: There is no location password.

location-password: Specify the password that is used when establishing sessions on the local location/remote location name pair. It must be an even number of hexadecimal characters.

Element 7: Location Security

Specifies how security information is handled for program start requests received from remote systems. The value is sent to the remote system when sessions are established. It is used in determining how allocate or evoke requests should be built. The value only applies to conversations started with the SECURITY(SAME) level of security.

*NO: The remote system is not a secure location. Security validation done by the remote system is not accepted. SECURITY(SAME) conversations are treated as SECURITY(NONE). No security information will be sent with allocate or evoke requests.

*YES: The remote system is a secure location and the local system will accept security validation done by remote systems. For SECURITY(SAME) conversations, the local system allows the remote system to verify user passwords. On the remote system, user IDs are retrieved from the operating system. The user IDs are then sent with an already verified indicator in the allocate or evoke requests.

*VFYENCPWD: The remote system is not a secure location. For SECURITY(SAME) conversations, the remote system is not allowed to send the already verified indicator. On the remote system, user IDs and passwords are retrieved from the operating system. Passwords are then encrypted and sent with the user IDs in the allocate or evoke requests, to be verified by the local system. This value should only be used if the remote system is using OS/400 V3R2M0 or later. If the remote system does not support password protection then session establishment will not be allowed. For remote systems that support password protection, but do not support verification of encrypted passwords (VFYENCPWD), conversations will be treated as SECURITY(NONE).

Element 8: Single Session Location

This value specifies whether the connection between the local location and remote location is a single session connection.

*NO: A single session connection is not made between the local and the remote location.

*YES: A single session connection is made between the local location and the remote location.

Element 9: Locally Controlled Session

This value specifies whether the single session connection between the local location and remote location is locally controlled.

*NO: The single session connection does not have to be locally controlled.

*YES: The single session connection is locally controlled.

Element 10: Pre-established Session

This value specifies whether the single session is automatically bound when the mode is started between the local location and remote location.

*NO: The single session connection is not automatically made between the local and remote location.

*YES: The single session connection is automatically made between the local and remote location.

Element 11: Remote Entry Description

*BLANK: Text is not specified.

'entry-description': Specify a short description of 20 characters or less, enclosed in apostrophes, for each remote entry.

Element 12: Number of Single-Session Conversations

10: The number of single session conversations allowed for this device description is ten.

single-session-conversations: Specify the number of conversations allowed for a single session of this device description. Valid values range from 1 through 512.

Note:

The combination of remote location name, remote network identifier, and local location name must be unique. Also, the remote location name cannot already exist as a local location in configuration list QAPPNLCL, or as the current value for either the LCLLOCNAME or the CPNAME network attribute.

ASYNCADRE

Specifies the asynchronous network address entry. This value is required if *ASYNCADR is specified for the TYPE parameter. Up to 50 entries can be specified for this parameter.

The following values make up an asynchronous network address entry.

Element 1: Network Address

network-address: Specify the asynchronous remote network address.

Element 2: Dial Retries

2: The LZ algorithm with the 12-bit code for repeated substrings in the data stream is used. These codes refer to entries in a common dictionary, created as the data flows between the sender and receiver. The LZ algorithms require storage and extra processing time. The LZ12 requires the most storage and processing time of the LZ algorithms; however, it compresses the data stream the most.

dial-retry: Specify the number of times dialing is retried (because errors occur) before the next number on the list is dialed. Valid values range from 1 through 255.

Element 3: Text Description

*BLANK: Text is not specified.

'entry-description': Specify a short description of 20 characters or less for each network address entry.

ASYNCLOCE

Specifies the asynchronous remote location entry. This value is required if *ASYNCLOC is specified for the TYPE parameter. Up to 50 entries can be specified for this parameter.

The following values make up an asynchronous network address entry.

Element 1: Remote Location Name

remote-location-name: Specify the name of the remote location. This name, when combined with the remote location identifier, determines whether an incoming call is accepted. The specified name must be unique.

Element 2: Remote Location Identifier

remote-location-identifier: Specify the identifier of the remote location. When this identifier is combined with the remote location name, it determines whether an incoming call is accepted. This identifier must be the same as the remote system has for its local identifier.

Element 3: Description of Remote Location Entry

*BLANK: Text is not specified.

'entry-description': Specify a short description of 20 characters or less for each remote location entry.

RTLPASTHRE

Specifies the retail pass-through entry. This value is required if TYPE(*RTLPASTHR) is specified. Up to 50 entries can be specified for this parameter.

The following values make up a retail pass-through entry:

Element 1: Retail Device Name

retail-device-name: Specify the name of the retail device to use for the pass-through session. This must be a unique value.

Element 2: SNA Upline Facility Device Name

SNUF-device-name: Specify the name of the host device to use for the pass-through session. This must be a unique value.

Element 3: Default Host Program Name

default-host-program-name: Specify the name of the program to be started on the host if a program name was not specified by the retail controller.

Element 4: Text Description

*BLANK: Text is not specified.

'entry-description': Specify a short description of 20 characters or less for each retail pass-through entry.

FTRCPNAME

Specifies the control point name of the adjacent control point that is being filtered by the local system when a directory search request is made.

Note:

This parameter is valid only if TYPE(*APPNDIR) is specified.

*ANY: Any control point name is filtered.

generic*-filtered-CP-name: Specify the generic control point name (part of a name followed by an asterisk) of the adjacent control point(s) being filtered. The generic control point name allows one directory entry to be defined for all control points, in a single network, with a name that matches the characters preceding an *.

filtered-CP-name: Specify the control point name of the adjacent control point being filtered.

FTRCPNETID

Specifies the control point network identifier of the adjacent control point being filtered by the local system when a directory search request is made.

Note:

This parameter is valid only if TYPE(*APPNDIR) is specified.

*NETATR: The LCLNETID value specified in the system network attributes is used.

filtered-CP-network-ID: Specify the control point network identifier of the adjacent control point being filtered by the local system.

LCLLOCNAME

Specifies the local location name being supplied by the caller that is being filtered by the local system. When the local system is initiating a session, this is the local location name being used. When a bind is received from another system, this is the Secondary Logical Unit (SLU) name being used.

Note:

This parameter is valid only if TYPE(*APPNSSN) is specified.

*ANY: Any local location name will be filtered by the local system.

generic*-local-location-name: Specify the generic local location name (part of a name followed by an asterisk) of the local location(s) being filtered. The generic local location name allows one entry to be defined for all local location names, on the system, with a name that matches the characters preceding an *.

local-location-name: Specify the local location name that is being filtered by the local system.

FTRACN

Specifies the filter action for APPN requests being handled by the local system.

Note:

This parameter is valid only if TYPE(*APPNDIR) or TYPE(*APPNSSN) is specified.

*ACCEPT: The request is accepted.

*REJECT: The request is rejected.

APPNDIRE

Specifies the APPN directory search entry being filtered by the local system. This parameter may be specified when *APPNDIR is specified for the TYPE parameter. Up to 300 entries may be specified at a time.

Element 1: Filtered Location Name

*ANY: Any control point location will be filtered.

generic*-filtered-CP-loc-name: Specify the generic name (part of a name followed by an asterisk) of the control point location(s) to be filtered. The generic name allows one name to be specified for all control point locations with a name that matches the characters preceding an *.

filtered-CP-location-name: Specify the control point location name to be filtered. This is the name of the location that is owned by the adjacent control point being filtered if the adjacent CP is an end node or LEN node. Or, the name of some location that accesses the local network via the adjacent control point (a non-native network node). This location name represents the name of the session partner attempting to establish a session with the remote location name (the location that exists in the local system's network).

Element 2: Filtered CP Location Network ID

*NETATR: The LCLNETID value specified in the system network attributes is used.

filtered-CP-location-network-ID: Specify the network identifier associated with the CP location name to be filtered.

Element 3: Partner Location Name

*ANY: Any remote location will be filtered.

generic*-partner-location-name: Specify the generic name (part of a name followed by an asterisk) of the partner location(s) to be filtered. The generic name allows one name to be specified for all partner locations with a name that matches the characters preceding an *.

partner-location-name: Specify the name of the partner location to be filtered.

Element 4: Partner Network Identifier

*NETATR: The LCLNETID value specified in the system network attributes is used.

partner-network-identifier: Specify the network identifier associated with the partner location to be filtered.

Element 5: Entry Description

*BLANK: Text is not specified.

'entry-description': Specify a short description of 20 characters or less for each entry.

APPNSSNE

Specifies the APPN session endpoint entry being filtered by the local system. This parameter may be specified when *APPNSSN is specified for the TYPE parameter. Up to 300 entries may be specified at a time.

Element 1: Remote Location Name

*ANY: Any remote location will be filtered.

generic*-remote-location-name: Specify the generic name (part of a name followed by an asterisk) of the remote location(s) to be filtered. The generic name allows one name to be specified for all remote locations with a name that matches the characters preceding an *.

Element 2: Remote Network Identifier

*NETATR: The LCLNETID value specified in the system network attributes is used.

Remote-network-identifier: Specify the remote network identifier associated with the remote location to be filtered.

Element 3: Text Description

*BLANK: Text is not specified.

'entry-description': Specify a short description of 20 characters or less for each entry.

GRPNAME

Specifies the SNA pass-through group name of the configuration list entry being added. The group name has upstream SNA pass-through device names associated with it (DEV parameter) and must exist in the configuration list.

Note:

This parameter is valid only if TYPE(*SNAPASTHR) is specified.

DEV

Specifies the names of the upstream devices associated with the SNA pass-through group (GRPNAME parameter).

Note:

This parameter is valid only if TYPE(*SNAPASTHR) is specified.

TEXT

Specifies the text that briefly describes the SNA pass-through group. More information is in Commonly used parameters.

Note:

This parameter is valid only if *APPNDIR, *APPNSSN, or *SNAPASTHR is specified for the TYPE parameter.

*BLANK: Text is not specified.

'entry-description': Specify a description of up to 50 characters for the SNA pass-through entry being added.

SNAPASTHRE

Specifies the SNA pass-through entry. This parameter can be specified if TYPE(*SNAPASTHR) is specified. However, because this parameter may be removed in a later release, whenever possible use GRPNAME, DEV, and TEXT parameters.

Example for ADDCFGLE

ADDCFGLE  TYPE(*APPNLCL)  APPNLCLE((LOC1 'location one')
  (LOC2 'location two'))

This command adds local locations LOC1 and LOC2 to configuration list QAPPNLCL.

Error messages for ADDCFGLE

*ESCAPE Messages

CPF260F

Configuration list &1 not found.

CPF261C

Index for configuration list &1 not changed.

CPF261D

Index for configuration list &1 not changed.

CPF2613

Too many entries were added.

CPF2625

Not able to allocate object &1.

CPF263A

CFGL type &1 does not match existing type &2.

CPF2634

Not authorized to object &1.

CPF2663

Configuration list &1 previously deleted.

CPF9838

User profile storage limit exceeded.