CHGCMNE (Change Communications Entry)

CHGCMNE Command syntax diagram

 

Purpose

The Change Communications Entry (CHGCMNE) command is used to change the attributes of a communications entry in an existing subsystem description.

 

Notes

  1. When the JOBD or DFTUSR parameters are changed, the communications entry also changes; however, the values of these parameters are not changed for any jobs that are active at the time.

  2. If the value of the MAXACT parameter is reduced to a number less than the total number of jobs that are active through the communications entry, no new program start requests are processed. Active jobs continue to run; but no additional program start requests are processed until the number of active jobs is less than the value specified for the MAXACT parameter.

 

Restrictions

  1. To use this command, the user must have object operational and object management authorities for the subsystem description and object operational authority for the job description.

  2. You cannot change the value of the MODE parameter while jobs are active through the communications entry.

 

Required Parameters

SBSD
Specifies the qualified name of the subsystem description that contains the communications entry to be 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 that contains the communications entry being changed.

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 Create Device Description for APPC (CRTDEVAPPC) command are used.

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

*BSCEL: All bisynchronous equivalency link communications devices can be used with this communications entry. The devices created with the CRTDEVBSC command are used. This value is valid only if MODE(*ANY) is specified.

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

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

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

*SNUF: All SNA upline facility communications devices can be used with this communications entry. The devices created with the CRTDEVSNUF command are used. 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 on the associated CRTDEVXXX command can be used here. The validity of the remote location name is not checked.

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 that are created as a result of receiving a program start request, and then are processed through this communications entry. If the job description does not exist when the entry is changed, a library qualifier must be specified because the qualified job description name is kept in the subsystem description.

*SAME: The value does not change.

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

*SBSD: The job description having the same qualified 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 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 (all blanks or a zero length password) and user profile name in the request. This user profile is not used for program start requests that have either a password or user profile specified (either valid or not valid).

*SAME: The value does not change.

*NONE: No user profile is specified as the 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 information.

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

MODE
Specifies the mode name of the communications device or remote location whose communications entry is being changed.

*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 associated with it, the communications device itself is allocated to the subsystem.

mode-name: Specify a mode name of the communications device or remote location name being changed.

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

*SAME: The value does not change.

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

CHGCMNE  SBSD(QGPL/BAKER)  DEV(A12)  MAXACT(*NOMAX)

This command changes the communications entry (in the subsystem description QGPL/BAKER) for the device A12. The maximum activity level is changed to *NOMAX which means that the communications entry puts no restrictions on the number of program start requests that may be active at the same time. However, the MAXJOBS value in the subsystem description BAKER limits the total number of jobs that can be active in the subsystem. This includes those created by program start requests. There is also a limit that the user can specify on the number of active jobs that can be routed through any particular routing entry (MAXACT). The limit specified in the routing entry may control the number of jobs using a particular pool or the recursion level of a particular program. In all cases, none of these limits can be exceeded as a result of processing a program start request.

Error messages for CHGCMNE

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