friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
ibm-information-center/dist/eclipse/plugins/i5OS.ic.cl_5.4.0.1/addcfgle.htm

810 lines
33 KiB
HTML
Raw Permalink Normal View History

Add readme and dist folders
2024-04-02 14:02:31 +00:00
<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Add Configuration List Entries (ADDCFGLE)</title>
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body bgcolor="white">
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<a name="ADDCFGLE.Top_Of_Page"></a>
<h2>Add Configuration List Entries (ADDCFGLE)</h2>
<table width="100%">
<tr>
<td valign="top" align="left"><b>Where allowed to run: </b>All environments (*ALL)<br>
<b>Threadsafe: </b>No
</td>
<td valign="top" align="right">
<a href="#ADDCFGLE.PARAMETERS.TABLE">Parameters</a><br>
<a href="#ADDCFGLE.COMMAND.EXAMPLES">Examples</a><br>
<a href="#ADDCFGLE.ERROR.MESSAGES">Error messages</a></td>
</tr>
</table>
<div> <a name="ADDCFGLE"></a>
<p>The Add Configuration List Entries (ADDCFGLE) command adds entries to a configuration list.
</p>
<p>
<b>Note: </b>You can also use an option on the full screen entry display of the Work With Configuration Lists (WRKCFGL) command to add, remove, or change entries in an existing list except for the configuration lists of type *APPNDIR, *APPNSSN, and *SNAPASTHR. TYPE(*SNAPASTHR).
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div>
<h3><a name="ADDCFGLE.PARAMETERS.TABLE">Parameters</a></h3>
<table border="1" cellpadding="4" cellspacing="0">
<!-- col1="10" col2="15" col3="30" col4="10" -->
<tr>
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
</tr>
<tr>
<td valign="top"><a href="#ADDCFGLE.TYPE"><b>TYPE</b></a></td>
<td valign="top">Configuration list type</td>
<td valign="top">*APPNDIR, *APPNLCL, *APPNRMT, *APPNSSN, *ASYNCADR, *ASYNCLOC, *RTLPASTHR, *SNAPASTHR</td>
<td valign="top">Required, Positional 1</td>
</tr>
<tr>
<td valign="top"><a href="#ADDCFGLE.CFGL"><b>CFGL</b></a></td>
<td valign="top">Configuration list</td>
<td valign="top"><i>Name</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#ADDCFGLE.APPNLCLE"><b>APPNLCLE</b></a></td>
<td valign="top">APPN local location entry</td>
<td valign="top">Values (up to 50 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Local location name</td>
<td valign="top">
<i>Communications name</i></td>
</tr>
<tr>
<td valign="top">Element 2: Entry 'description'</td>
<td valign="top">
<i>Character value</i>, <b><u>*BLANK</u></b></td>
</tr>
<tr>
<td valign="top" rowspan="13"><a href="#ADDCFGLE.APPNRMTE"><b>APPNRMTE</b></a></td>
<td valign="top">APPN remote location entry</td>
<td valign="top">Values (up to 50 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="13">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Remote location name</td>
<td valign="top">
<i>Generic name, name</i>, *ANY</td>
</tr>
<tr>
<td valign="top">Element 2: Remote network identifier</td>
<td valign="top">
<i>Communications name</i>, <b><u>*NETATR</u></b>, *NONE</td>
</tr>
<tr>
<td valign="top">Element 3: Local location name</td>
<td valign="top">
<i>Communications name</i>, <b><u>*NETATR</u></b></td>
</tr>
<tr>
<td valign="top">Element 4: Remote control point</td>
<td valign="top">
<i>Communications name</i>, <b><u>*NONE</u></b></td>
</tr>
<tr>
<td valign="top">Element 5: Control point net ID</td>
<td valign="top">
<i>Communications name</i>, <b><u>*NETATR</u></b>, *NONE</td>
</tr>
<tr>
<td valign="top">Element 6: Location password</td>
<td valign="top">
<i>Character value</i>, <b><u>*NONE</u></b></td>
</tr>
<tr>
<td valign="top">Element 7: Secure location</td>
<td valign="top">
*YES, <b><u>*NO</u></b>, *VFYENCPWD</td>
</tr>
<tr>
<td valign="top">Element 8: Single session</td>
<td valign="top">
*YES, <b><u>*NO</u></b></td>
</tr>
<tr>
<td valign="top">Element 9: Locally controlled session</td>
<td valign="top">
*YES, <b><u>*NO</u></b></td>
</tr>
<tr>
<td valign="top">Element 10: Pre-established session</td>
<td valign="top">
*YES, <b><u>*NO</u></b></td>
</tr>
<tr>
<td valign="top">Element 11: Entry 'description'</td>
<td valign="top">
<i>Character value</i>, <b><u>*BLANK</u></b></td>
</tr>
<tr>
<td valign="top">Element 12: Number of conversations</td>
<td valign="top">
1-512, <b><u>10</u></b></td>
</tr>
<tr>
<td valign="top" rowspan="4"><a href="#ADDCFGLE.ASYNCADRE"><b>ASYNCADRE</b></a></td>
<td valign="top">Async network address entry</td>
<td valign="top">Values (up to 50 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="4">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Network address</td>
<td valign="top">
<i>Character value</i></td>
</tr>
<tr>
<td valign="top">Element 2: Dial retry</td>
<td valign="top">
1-255, <b><u>2</u></b></td>
</tr>
<tr>
<td valign="top">Element 3: Entry 'description'</td>
<td valign="top">
<i>Character value</i>, <b><u>*BLANK</u></b></td>
</tr>
<tr>
<td valign="top" rowspan="4"><a href="#ADDCFGLE.ASYNCLOCE"><b>ASYNCLOCE</b></a></td>
<td valign="top">Async remote location entry</td>
<td valign="top">Values (up to 50 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="4">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Remote location name</td>
<td valign="top">
<i>Communications name</i></td>
</tr>
<tr>
<td valign="top">Element 2: Remote location identifier</td>
<td valign="top">
<i>Name</i></td>
</tr>
<tr>
<td valign="top">Element 3: Entry 'description'</td>
<td valign="top">
<i>Character value</i>, <b><u>*BLANK</u></b></td>
</tr>
<tr>
<td valign="top" rowspan="5"><a href="#ADDCFGLE.RTLPASTHRE"><b>RTLPASTHRE</b></a></td>
<td valign="top">Retail pass-through entry</td>
<td valign="top">Values (up to 50 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="5">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Retail device</td>
<td valign="top">
<i>Name</i></td>
</tr>
<tr>
<td valign="top">Element 2: SNUF device</td>
<td valign="top">
<i>Name</i></td>
</tr>
<tr>
<td valign="top">Element 3: Default host program</td>
<td valign="top">
<i>Name</i></td>
</tr>
<tr>
<td valign="top">Element 4: Entry 'description'</td>
<td valign="top">
<i>Character value</i>, <b><u>*BLANK</u></b></td>
</tr>
<tr>
<td valign="top"><a href="#ADDCFGLE.FTRCPNAME"><b>FTRCPNAME</b></a></td>
<td valign="top">Filtered control point name</td>
<td valign="top"><i>Generic name, name</i>, <b><u>*ANY</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDCFGLE.FTRCPNETID"><b>FTRCPNETID</b></a></td>
<td valign="top">Filtered CP network identifier</td>
<td valign="top"><i>Communications name</i>, <b><u>*NETATR</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDCFGLE.LCLLOCNAME"><b>LCLLOCNAME</b></a></td>
<td valign="top">Local location name</td>
<td valign="top"><i>Generic name, name</i>, <b><u>*ANY</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDCFGLE.FTRACN"><b>FTRACN</b></a></td>
<td valign="top">Filter action</td>
<td valign="top"><i>Character value</i>, <b><u>*ACCEPT</u></b>, *REJECT</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="6"><a href="#ADDCFGLE.APPNDIRE"><b>APPNDIRE</b></a></td>
<td valign="top">APPN directory search entries</td>
<td valign="top">Values (up to 300 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="6">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Filtered CP location name</td>
<td valign="top">
<i>Generic name, name</i>, <b><u>*ANY</u></b></td>
</tr>
<tr>
<td valign="top">Element 2: Filtered CP location NETID</td>
<td valign="top">
<i>Communications name</i>, <b><u>*NETATR</u></b></td>
</tr>
<tr>
<td valign="top">Element 3: Partner location name</td>
<td valign="top">
<i>Generic name, name</i>, <b><u>*ANY</u></b></td>
</tr>
<tr>
<td valign="top">Element 4: Partner location network ID</td>
<td valign="top">
<i>Communications name</i>, <b><u>*NETATR</u></b></td>
</tr>
<tr>
<td valign="top">Element 5: Entry 'description'</td>
<td valign="top">
<i>Character value</i>, <b><u>*BLANK</u></b></td>
</tr>
<tr>
<td valign="top" rowspan="4"><a href="#ADDCFGLE.APPNSSNE"><b>APPNSSNE</b></a></td>
<td valign="top">APPN session endpoint entries</td>
<td valign="top">Values (up to 300 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="4">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Remote location name</td>
<td valign="top">
<i>Generic name, name</i>, <b><u>*ANY</u></b></td>
</tr>
<tr>
<td valign="top">Element 2: Remote network identifier</td>
<td valign="top">
<i>Communications name</i>, <b><u>*NETATR</u></b></td>
</tr>
<tr>
<td valign="top">Element 3: Entry 'description'</td>
<td valign="top">
<i>Character value</i>, <b><u>*BLANK</u></b></td>
</tr>
<tr>
<td valign="top"><a href="#ADDCFGLE.GRPNAME"><b>GRPNAME</b></a></td>
<td valign="top">SNA pass-through group name</td>
<td valign="top"><i>Name</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDCFGLE.DEV"><b>DEV</b></a></td>
<td valign="top">SNA pass-through device desc</td>
<td valign="top">Values (up to 254 repetitions): <i>Name</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDCFGLE.TEXT"><b>TEXT</b></a></td>
<td valign="top">Entry 'description'</td>
<td valign="top"><i>Character value</i>, *BLANK</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="4"><a href="#ADDCFGLE.SNAPASTHRE"><b>SNAPASTHRE</b></a></td>
<td valign="top">SNA pass-through entry</td>
<td valign="top"><i>Element list</i></td>
<td valign="top" rowspan="4">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: SNA pass-through group name</td>
<td valign="top">
<i>Communications name</i></td>
</tr>
<tr>
<td valign="top">Element 2: SNA pass-through device desc</td>
<td valign="top">
Values (up to 254 repetitions): <i>Communications name</i></td>
</tr>
<tr>
<td valign="top">Element 3: Entry 'description'</td>
<td valign="top">
<i>Character value</i>, <b><u>*BLANK</u></b></td>
</tr>
</table>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
</div>
<div> <a name="ADDCFGLE.TYPE"></a>
<h3>Configuration list type (TYPE)</h3>
<p>Specifies the type of configuration list entry being added.
</p>
<dl>
<dt><b>*APPNDIR</b></dt>
<dd>An advanced peer-to-peer networking* (APPN*) directory search filter configuration list is used.
</dd>
<dt><b>*APPNLCL</b></dt>
<dd>An advanced peer-to-peer networking (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).
</dd>
<dt><b>*APPNRMT</b></dt>
<dd>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).
</dd>
<dt><b>*APPNSSN</b></dt>
<dd>An APPN session end point filter configuration list is used.
</dd>
<dt><b>*ASYNCADR</b></dt>
<dd>An asynchronous network address list is used. Up to 294 asynchronous network address entries are allowed in the configuration list.
</dd>
<dt><b>*ASYNCLOC</b></dt>
<dd>An asynchronous remote location list is used. Up to 32000 asynchronous remote location entries are allowed in the configuration list.
</dd>
<dt><b>*RTLPASTHR</b></dt>
<dd>A retail pass-through list is used. Up to 450 retail pass-through entries can be specified in the configuration list.
</dd>
<dt><b>*SNAPASTHR</b></dt>
<dd>An SNA pass-through list is used. Up to 254 SNA pass-through entries can be specified in the configuration list.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.CFGL"></a>
<h3>Configuration list (CFGL)</h3>
<p>Specifies the name of the configuration list. This value is required and valid only when the configuration list is an asynchronous network address list (*ASYNCADR is specified for the <b>Configuration list type (TYPE)</b> parameter). The list types have system-supplied names: QAPPNLCL, QAPPNRMT, QASYNCADR, QASYNCLOC, QRTLPASTHR, and QSNAPASSTHR.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.APPNLCLE"></a>
<h3>APPN local location entry (APPNLCLE)</h3>
<p>Specifies the APPN local location entry. This value is required if *APPNLCL is specified for the <b>Configuration list type</b> prompt (TYPE parameter).
</p>
<p>You can enter multiple values for this parameter.
</p>
<p>A maximum of 50 entries can be specified directly for this parameter. An entry consists of a value from each of the following elements.
</p>
<dl>
<dt><b><i>local-location-name</i></b></dt>
<dd>Specify the location name residing on the local system. This name is used by APPN to determine if the request coming in is for this system or another system in the network. The local location name must be unique and cannot already exist as a remote location name used by configuration list QAPPNRMT, or be specified on another system as a local location in the same APPN network.
</dd>
<dt><b><i>entry-description</i></b></dt>
<dd>Specify a short description of 20 characters or less for each local entry.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.APPNRMTE"></a>
<h3>APPN remote location entry (APPNRMTE)</h3>
<p>Specifies the APPN remote location entry. This value is required if *APPNRMT is specified for the <b>Configuration list type</b> prompt (TYPE parameter).
</p>
<p>You can enter multiple values for this parameter.
</p>
<p>A maximum of 50 entries can be specified directly for this parameter. An entry consists of a value from each of the following elements.
</p>
<dl>
<dt><b><i>remote-location-name</i></b></dt>
<dd>Specify the full name of a remote location or a generic name ending with an asterisk (*). The generic location name is used to allow one directory entry to be defined for all locations, on a single control point, whose name matches the characters preceding the asterisk. You can also specify *ANY so the system will accept all requests sent through it. Generic entries are only allowed from network nodes.
</dd>
<dt><b><i>remote-network-identifier</i></b></dt>
<dd>Specify the network identifier of the network in which the remote location resides. The default of *NETATR uses the LCLNETID value from the system network attributes.
</dd>
<dt><b><i>local-location-name</i></b></dt>
<dd>Specify the location name residing on the local system. This name is used by APPN to match a local/remote location pair entry. The default of *NETATR uses the LCLLOCNAME value from the system network attributes.
</dd>
<dt><b><i>control-point-name</i></b></dt>
<dd>Specify the control point providing network functions for the remote location. By using this control point name (directory entry for the remote location), the network is searched more efficiently to find the location. This field is required if the remote location name is generic. The default is *NONE.
</dd>
<dt><b><i>control-point-network-identifier</i></b></dt>
<dd>Specify the network identifier of the network in which the control point resides. The default of *NETATR uses the LCLNETID value from the system network attributes.
</dd>
<dt><b><i>location-password</i></b></dt>
<dd>Specify the password that is used when establishing sessions on the local location/remote location name pair. This value must contain an even number of hexadecimal characters. The default is *NONE.
</dd>
<dt><b><i>secure-location</i></b></dt>
<dd>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.
<dl>
<dt><b><u>*NO</u></b></dt>
<dd>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.
</dd>
<dt><b>*YES</b></dt>
<dd>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.
</dd>
<dt><b>*VFYENCPWD</b></dt>
<dd>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 i5/OS 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).
</dd>
</dl>
</dd>
<dt><b><i>number-of-conversations</i></b></dt>
<dd>Specify the number of conversations for a single session connection. The default number of conversations is 10. The default value must be used if single session is *NO. The valid range for the number of conversations is 1 through 512.
</dd>
<dt><b><i>locally-controlled-session</i></b></dt>
<dd>Specify YES or NO to indicate whether a locally controlled session is allowed for this local location/remote location name pair. The default is *NO.
</dd>
<dt><b><i>pre-established-session</i></b></dt>
<dd>Specify YES or NO to indicate whether the session is automatically bound when a connection is made between the local and remote location. The default is *NO.
</dd>
<dt><b><i>entry-description</i></b></dt>
<dd>Specify a short description for each remote entry. The default is *BLANK.
<p>
<b>Note: </b>The combination of remote location name, network identifier, and local location name must be unique. Also, the remote location name can not already exist as a local location in configuration list QAPPNLCL, or as the current value for LCLLOCNAME or LCLCPNAME network attribute.
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.ASYNCADRE"></a>
<h3>Async network address entry (ASYNCADRE)</h3>
<p>Specifies the asynchronous network address entry. This value is required if *ASYNCADR is specified for the <b>Configuration list type</b> prompt (TYPE parameter).
</p>
<p>You can enter multiple values for this parameter.
</p>
<p>A maximum of 50 entries can be specified directly for this parameter. An entry consists of a value from each of the following elements.
</p>
<dl>
<dt><b><i>network-address</i></b></dt>
<dd>Specify the X.25 network address. This value must contain only digits 0-9.
</dd>
<dt><b><i>dial-retry</i></b></dt>
<dd>Specify the number of times that dialing will be tried again when errors occur while dialing, before attempting to dial the next number on the list. The valid range of dial retries is 1-255.
</dd>
<dt><b><i>entry-description</i></b></dt>
<dd>Specify a short description for each network address entry.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.ASYNCLOCE"></a>
<h3>Async remote location entry (ASYNCLOCE)</h3>
<p>Specifies the asynchronous remote location entry. This value is required if *ASYNCLOC is specified for the <b>Configuration list type</b> prompt (TYPE parameter).
</p>
<p>You can enter multiple values for this parameter.
</p>
<p>A maximum of 50 entries can be specified directly for this parameter. An entry consists of a value from each of the following elements.
</p>
<dl>
<dt><b><i>remote-location-name</i></b></dt>
<dd>Specify the name that, when combined with the remote location identifier, determines whether to accept an incoming call. It is the same as the name used in the remote system as it's local name. This value must be unique.
</dd>
<dt><b><i>remote-location-identifier</i></b></dt>
<dd>Specify an identifier that, when combined with the remote location name, determines if an incoming call will be accepted. This identifier must be the same as the remote system has for its local identifier.
</dd>
<dt><b><i>entry-description</i></b></dt>
<dd>Specify a short description for each remote location entry. The default is *BLANK.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.RTLPASTHRE"></a>
<h3>Retail pass-through entry (RTLPASTHRE)</h3>
<p>Specifies the retail pass-through entry. This value is required if *RTLPASTHR is specified for the <b>Configuration list type</b> prompt (TYPE parameter).
</p>
<p>You can enter multiple values for this parameter.
</p>
<p>A maximum of 50 entries can be specified directly for this parameter. An entry consists of a value from each of the following elements.
</p>
<dl>
<dt><b><i>retail-device-name</i></b></dt>
<dd>Specify the name of the retail device that communicates with the host. This value must be unique.
</dd>
<dt><b><i>SNUF-device-name</i></b></dt>
<dd>Specify the name of the SNUF device through which the retail device communicates with the host. This value must be unique.
</dd>
<dt><b><i>Default-host-program-name</i></b></dt>
<dd>Specify the name of the program to be started on the host if the program name is not present in the SNA command (INIT-SELF) that requests a session to be started.
</dd>
<dt><b><i>entry-description</i></b></dt>
<dd>Specify a short description for each retail pass-through entry. The default is *BLANK.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.FTRCPNAME"></a>
<h3>Filtered control point name (FTRCPNAME)</h3>
<p>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.
</p>
<p>
<b>Note: </b>This parameter is valid only if TYPE(*APPNDIR) is specified.
</p>
<dl>
<dt><b><u>*ANY</u></b></dt>
<dd>Any control point name is filtered.
</dd>
<dt><b><i>generic*-filtered-CP-name</i></b></dt>
<dd>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 *.
</dd>
<dt><b><i>filtered-CP-name</i></b></dt>
<dd>Specify the control point name of the adjacent control point being filtered.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.FTRCPNETID"></a>
<h3>Filtered CP network identifier (FTRCPNETID)</h3>
<p>Specifies the control point network identifier of the adjacent control point being filtered by the local system when a directory search request is made.
</p>
<p>
<b>Note: </b>This parameter is valid only if TYPE(*APPNDIR) is specified.
</p>
<dl>
<dt><b><u>*NETATR</u></b></dt>
<dd>The LCLNETID value specified in the system network attributes is used.
</dd>
<dt><b><i>filtered-CP-network-ID</i></b></dt>
<dd>Specify the control point network identifier of the adjacent control point being filtered by the local system.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.LCLLOCNAME"></a>
<h3>Local location name (LCLLOCNAME)</h3>
<p>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.
</p>
<p>
<b>Note: </b>This parameter is valid only if TYPE(*APPNSSN) is specified.
</p>
<dl>
<dt><b><u>*ANY</u></b></dt>
<dd>Any local location name will be filtered by the local system.
</dd>
<dt><b><i>generic*-local-location-name</i></b></dt>
<dd>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 *.
</dd>
<dt><b><i>local-location-name</i></b></dt>
<dd>Specify the local location name that is being filtered by the local system.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.FTRACN"></a>
<h3>Filter action (FTRACN)</h3>
<p>Specifies the filter action for APPN requests being handled by the local system.
</p>
<p>
<b>Note: </b>This parameter is valid only if TYPE(*APPNDIR) or TYPE(*APPNSSN) is specified.
</p>
<dl>
<dt><b><u>*ACCEPT</u></b></dt>
<dd>The request is accepted.
</dd>
<dt><b>*REJECT</b></dt>
<dd>The request is rejected.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.APPNDIRE"></a>
<h3>APPN directory search entries (APPNDIRE)</h3>
<p>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.
</p>
<p>The possible Filtered Location Name values are:
</p>
<dl>
<dt><b>*ANY</b></dt>
<dd>Any control point location will be filtered.
</dd>
<dt><b><i>generic*-filtered-CP-loc-name</i></b></dt>
<dd>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 asterisk (*).
</dd>
<dt><b><i>filtered-CP-location-name</i></b></dt>
<dd>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).
</dd>
</dl>
<p>The possible Filtered CP Location Network ID values are:
</p>
<dl>
<dt><b><u>*NETATR</u></b></dt>
<dd>The LCLNETID value specified in the system network attributes is used.
</dd>
<dt><b><i>filtered-CP-location-network-ID</i></b></dt>
<dd>Specify the network identifier associated with the CP location name to be filtered.
</dd>
</dl>
<p>The possible Partner Location Name values are:
</p>
<dl>
<dt><b><u>*ANY</u></b></dt>
<dd>Any remote location will be filtered.
</dd>
<dt><b><i>generic*-partner-location-name</i></b></dt>
<dd>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 asterisk (*).
</dd>
<dt><b><i>partner-location-name</i></b></dt>
<dd>Specify the name of the partner location to be filtered.
</dd>
</dl>
<p>The possible Partner Network Identifier values are:
</p>
<dl>
<dt><b><u>*NETATR</u></b></dt>
<dd>The LCLNETID value specified in the system network attributes is used.
</dd>
<dt><b><i>partner-network-identifier</i></b></dt>
<dd>Specify the network identifier associated with the partner location to be filtered.
</dd>
</dl>
<p>The possible Entry Description values are:
</p>
<dl>
<dt><b><u>*BLANK</u></b></dt>
<dd>Text is not specified.
</dd>
<dt><b><i>'entry-description'</i></b></dt>
<dd>Specify a short description of 20 characters or less for each entry.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.APPNSSNE"></a>
<h3>APPN session endpoint entries (APPNSSNE)</h3>
<p>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.
</p>
<p>The possible Remote Location Name values are:
</p>
<dl>
<dt><b><u>*ANY</u></b></dt>
<dd>Any remote location will be filtered.
</dd>
<dt><b><i>generic*-remote-location-name</i></b></dt>
<dd>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 asterisk (*).
</dd>
</dl>
<p>The possible Remote Network Identifier values are:
</p>
<dl>
<dt><b><u>*NETATR</u></b></dt>
<dd>The LCLNETID value specified in the system network attributes is used.
</dd>
<dt><b><i>Remote-network-identifier</i></b></dt>
<dd>Specify the remote network identifier associated with the remote location to be filtered.
</dd>
</dl>
<p>The possible Text Description values are:
</p>
<dl>
<dt><b><u>*BLANK</u></b></dt>
<dd>Text is not specified.
</dd>
<dt><b><i>'entry-description'</i></b></dt>
<dd>Specify a short description of 20 characters or less for each entry.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.GRPNAME"></a>
<h3>SNA pass-through group name (GRPNAME)</h3>
<p>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.
</p>
<p>
<b>Note: </b>This parameter is valid only if TYPE(*SNAPASTHR) is specified.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.DEV"></a>
<h3>SNA pass-through device desc (DEV)</h3>
<p>Specifies the names of the upstream devices associated with the SNA pass-through group (GRPNAME parameter).
</p>
<p>
<b>Note: </b>This parameter is valid only if TYPE(*SNAPASTHR) is specified.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.TEXT"></a>
<h3>Entry 'description' (TEXT)</h3>
<p>Specifies the text that briefly describes the SNA pass-through group.
</p>
<p>
<b>Note: </b>This parameter is valid only if *APPNDIR, *APPNSSN, or *SNAPASTHR is specified for the TYPE parameter.
</p>
<dl>
<dt><b>*BLANK</b></dt>
<dd>Text is not specified.
</dd>
<dt><b><i>'entry-description'</i></b></dt>
<dd>Specify a description of up to 50 characters for the SNA pass-through entry being added.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDCFGLE.SNAPASTHRE"></a>
<h3>SNA pass-through entry (SNAPASTHRE)</h3>
<p>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.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="ADDCFGLE.COMMAND.EXAMPLES">Examples</a> </h3>
<p>
<pre>
ADDCFGLE TYPE(*APPNLCL)
APPNLCLE((LOC1 'location one') (LOC2 'location two'))
</pre>
</p>
<p>This command adds local locations LOC1 and LOC2 to configuration list QAPPNLCL.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="ADDCFGLE.ERROR.MESSAGES">Error messages</a> </h3>
<p><b><u>*ESCAPE Messages</u></b>
</p>
<dl>
<dt><b>CPF260F</b></dt>
<dd>Configuration list &amp;1 not found.
</dd>
<dt><b>CPF261C</b></dt>
<dd>Index for configuration list &amp;1 not changed.
</dd>
<dt><b>CPF261D</b></dt>
<dd>Index for configuration list &amp;1 not changed.
</dd>
<dt><b>CPF2613</b></dt>
<dd>Too many entries were added.
</dd>
<dt><b>CPF2625</b></dt>
<dd>Not able to allocate object &amp;1.
</dd>
<dt><b>CPF263A</b></dt>
<dd>CFGL type &amp;1 does not match existing type &amp;2.
</dd>
<dt><b>CPF2634</b></dt>
<dd>Not authorized to object &amp;1.
</dd>
<dt><b>CPF2663</b></dt>
<dd>Configuration list &amp;1 previously deleted.
</dd>
<dt><b>CPF9838</b></dt>
<dd>User profile storage limit exceeded.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDCFGLE.Top_Of_Page">Top</a></td></tr>
</table>
</body>
</html>
Reference in New Issue Copy Permalink