As shown in Figure 1, a program
that issues container commands can be used, without change, as part of a channel
application or as part of a BTS activity.
For a program to be used in both a channel and a BTS context, the container
commands that it issues must not specify any options that identify them as
either channel or BTS commands. The options to be avoided on each of the container
commands are:
- DELETE CONTAINER
-
- ACQACTIVITY (BTS-specific)
- ACQPROCESS (BTS-specific)
- ACTIVITY (BTS-specific)
- CHANNEL (channel-specific)
- PROCESS (BTS-specific)
- GET CONTAINER
-
- ACQACTIVITY (BTS-specific)
- ACQPROCESS (BTS-specific)
- ACTIVITY (BTS-specific)
- CHANNEL (channel-specific)
- INTOCCSID (channel-specific)
- PROCESS (BTS-specific)
- MOVE CONTAINER
-
- FROMACTIVITY (BTS-specific)
- CHANNEL (channel-specific)
- FROMPROCESS (BTS-specific)
- TOACTIVITY (BTS-specific)
- TOCHANNEL (channel-specific)
- TOPROCESS (BTS-specific)
- PUT CONTAINER
-
- ACQACTIVITY (BTS-specific)
- ACQPROCESS (BTS-specific)
- ACTIVITY (BTS-specific)
- CHANNEL (channel-specific)
- DATATYPE (channel-specific)
- FROMCCSID (channel-specific)
- PROCESS (BTS-specific)
When a container command is executed, CICS® analyzes the context (channel, BTS,
or neither) in which it occurs, in order to determine how to process the command.
To determine the context, CICS uses the following sequence of tests:
- Channel: does the program have a current channel?
- BTS: is the program part of a BTS activity?
- None: the program has no current channel and is not part of a BTS activity.
It therefore has no context in which to execute container commands. The command
is rejected with an INVREQ condition and a RESP2 value of 4.