ADDCMNE (Add Communications Entry)

ADDCMNE Command syntax diagram

 

Purpose

The Add Communications Entry (ADDCMNE) command adds a communications entry to an existing subsystem description.

Each entry specifies a communications device, device type, or remote location that can enter work into the subsystem. The subsystem can allocate a communications device, if the device is not currently allocated to another subsystem or job. A communications device that is currently allocated may eventually be de-allocated, making it available to other subsystems. For information regarding reallocation of communications devices to other subsystems, see the Work Management book.

 

Restrictions

1. The user must have object operational and object management authorities for the communications entry.
   
2. A subsystem cannot allocate a communications device that is currently allocated to another subsystem or job.

 

Required Parameters

SBSD

Specifies the qualified name of the subsystem description to which the communications entry is being added or in which it is being changed.

The name of the subsystem description 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.

subsystem-description-name: Specify the name of the subsystem description to which the communications entry is added.

DEV

Specifies the name of the device description or the type of the device being used with this communications entry.

Note:

A user must specify either this parameter or the RMTLOCNAME parameter, but not both.

*ALL: All communications devices can be used with this communications entry.

*APPC: All advanced program-to-program communications devices can be used with this communications entry. The devices created with the CRTDEVAPPC command are used by the iSeries 400 server APPN support.

*ASYNC: All asynchronous communications devices, including those created with the CRTDEVASC command, can be used with this communications entry. This value is valid only if MODE(*ANY) is specified.

*BSCEL: All binary synchronous equivalency link communications devices, including those created with the CRTDEVBSC command, can be used with this communications entry. This value is valid only if MODE(*ANY) is specified.

*FINANCE: All FINANCE communications devices, including those created with the CRTDEVFNC command, are used with this communications entry. This value is valid only if MODE(*ANY) is specified.

*INTRA: All INTRA communications devices, including those created with the CRTDEVINTR command, are used with this communications entry. This value is valid only if MODE(*ANY) is specified.

*RETAIL: All RETAIL communications devices, including those created with the CRTDEVRTL command, are used with this communications entry. This value is valid only if MODE(*ANY) is specified.

*SNUF: All SNA upline facility communications devices, including those created with the CRTDEVSNUF command, can be used with this communications entry. This value is valid only if MODE(*ANY) is specified.

device-name: Specify the device description name or the type of device to use with this communications device entry. The name specified on the CRTDEVxxx command associated with this device description name is used.

generic*-device-name: Specify the generic name of the device. A generic name is a character string of one or more characters followed by an asterisk (*); for example, ABC*. The asterisk substitutes for any valid characters. A generic name specifies all objects with names that begin with the generic prefix for which the user has authority. If an asterisk is not included with the generic (prefix) name, the system assumes it to be the complete object name. See generic names for additional information.

RMTLOCNAME

Specifies the name of the remote location that is used with this object.

Note:

The remote location name specified in the CRTDEVXXX command can be used here. No validity checking is done on the remote location name. The user must specify either this parameter or the DEV parameter, but not both.

 

Optional Parameters

JOBD

Specifies the qualified name of the job description used for jobs created as a result of program start requests and processed through this communications entry. If the job description does not exist when the communications entry is added, a library qualifier must be specified because the qualified job description name is kept in the subsystem description.

*USRPRF: The job description name specified in the user profile of the user that made the program start request is used for jobs that are processed through this communications entry.

*SBSD: The job description having the same name as the subsystem description (specified by the SBSD parameter) is used for jobs processed through this communications entry.

The name of the job description 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.

job-description-name: Specify the qualified name of the job description that is used for the jobs processed through this communications entry.

DFTUSR

Specifies the default user profile used for a program start request that contains no password (either all blanks or a zero length password) and user profile name. This user profile is not used for program start requests that contain a password or specify a user profile (either valid or not valid).

*NONE: No user profile is specified as a default.

*SYS: User program start requests are treated the same as DFTUSR(*NONE). For system-generated program start requests, the correct user profile is used.

user-profile-name: Specify the name of the user profile that is used for all program start requests that enter the system through this communications entry and that contain no password or user profile name.

Note:

The names QSECOFR, QSPL, QDOC, QDBSHR, QRJE, and QSYS are not valid entries on this parameter.

MODE

Specifies the mode name of the communications device or remote location name used with this communications entry.

*ANY: Any available modes defined to the communications device or remote location are allocated to the subsystem. If the communications device does not have defined modes, the communications device itself is allocated to the subsystem.

mode-name: Specify a mode name of the communications device or remote location used with this communications entry.

MAXACT

Specifies the maximum number of program start requests that can be active at the same time through this communications entry. More information is in Commonly used parameters.

*NOMAX: There is no maximum number of jobs that can be active at the same time.

maximum-active-jobs: Specify the maximum number of jobs that can be active at the same time through this communications entry.

Example for ADDCMNE

ADDCMNE   SBSD(ALIB/SBS1)  DEV(COMDEV)

This command adds a communications entry for the APPC device named COMDEV to the subsystem description SBS1, which resides in library ALIB. The DFTUSR parameter defaults to *NONE, which means that no jobs may enter the system through this entry unless valid security information is supplied on the program start request.

Error messages for ADDCMNE

*ESCAPE Messages

CPF1619

Subsystem description &1 in library &2 damaged.

CPF1691

Active subsystem description may or may not have changed.

CPF1697

Subsystem description &1 not changed.