Define pipeline terminals with the following attributes:
- NETNAME
- The VTAM® session
that is used.
- POOL
- All the TERMINAL definitions having the same POOL name belong to the same
pipeline pool. The presence of a value for the POOL attribute distinguishes
these from ordinary TERMINAL definitions.
- SESSIONTYPE
- Use this attribute on the TYPETERM definition to identify the TYPETERM
as representing pipeline terminals. Specify PIPELINE as the value.
- TASKLIMIT
- Specify the maximum number of concurrent tasks that can be active for
the pool of terminals on at least one of the TERMINAL definitions.
One TYPETERM would normally suit all the definitions. The TYPETERM may
be in another group.
Pipeline transactions are associated with a PROFILE definition that has
the ONEWTE attribute. A program associated with these transactions is permitted
only one write or EXEC CICS SEND operation, or else it is terminated with
an ATCC abend code. This means that CICS tasks rapidly appear and disappear
across the pool of sessions.
There is an example of definitions for a pool of pipeline terminals in
the description of the POOL attribute in
Terminal definition attributes.
Note: - If you install a pipeline terminal naming a pipeline that already exists
in CICS, both the old pipeline and all its related terminals are deleted before
the new definitions are installed.
- If you discard the terminal that is defined as owning the existing pipeline,
the existing pipeline and all its related terminals are deleted.
- If you discard a terminal that is not the pipeline owner or change it
to a different pipeline, or to a nonpipeline terminal, the rest of the pipeline
definition is unchanged. (The owning terminal of a pipeline is the terminal
with the first name in alphanumeric sequence that is related to the pipeline
in the group from which the pipeline was installed.)
- You cannot change a terminal in an existing pipeline to a nonpipeline
terminal, or change it to a new pipeline, if the old pipeline is also being
reinstalled in the same group. To do this, you divide the installation into
two stages. If you are installing the group twice, remember to set the relevant
terminals out of service in the meantime.