Change communication entries
You can change the attributes of an existing communications entry
in an existing subsystem description by using the character-based interface.
- When the Job description (JOBD) or Default user profile
(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.
- If the value of the Maximum active jobs (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.
Command: Change Communications Entry (CHGCMNE)
Example: This example changes the communications entry (in
the subsystem description QGPL/BAKER) for the device A12 and mode *ANY. 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 might
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 can 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.
CHGCMNE SBSD(QGPL/BAKER) DEV(A12) MAXACT(*NOMAX)