DELETE CONTAINER (BTS)
Delete a named BTS data-container.
Description
DELETE CONTAINER (BTS) deletes a BTS data-container and discards any data that it contains.
The
container is identified by name and by the process or activity for
which it is a container—the process or activity that “owns”
it. The activity that owns the container can be identified:
- Explicitly, by specifying one of the PROCESS- or ACTIVITY-related options.
- Implicitly, by omitting the PROCESS- and ACTIVITY-related options. If these are omitted, the current activity is implied.
Note: Process containers can be deleted only by the root activity
or by a program that has acquired the process.
Options
- ACQACTIVITY
- specifies either of the following:
- If the program that issues the command has acquired a process, that the container is owned by the root activity of that process.
- Otherwise, that the container is owned by the activity that the program has acquired by means of an ACQUIRE ACTIVITYID command.
- ACQPROCESS
- specifies that the container is owned by the process that the program that issues the command has acquired in the current unit of work.
- ACTIVITY(data-value)
- specifies the name (1–16 characters) of the activity that owns the container. This must be a child of the current activity.
- CONTAINER(data-value)
- specifies the name (1–16 characters) of the container to be deleted.
- PROCESS
- specifies that the container to be deleted is owned by the current process—that is, the process that the program that issues the command is executing on behalf of.
Conditions
- 109 ACTIVITYERR
- RESP2 values:
- 8
- The activity named on the ACTIVITY option could not be found.
- 110 CONTAINERERR
- RESP2 values:
- 10
- The container named on the CONTAINER option could not be found.
- 26
- The process container named on the CONTAINER option is read-only. (Process containers can be deleted only by the root activity or by a program that has acquired the process.)
- 16 INVREQ
- RESP2
values:
- 4
- The command was issued outside the scope of a currently-active activity.
- 15
- The ACQPROCESS option was used, but the unit of work that issued the request has not acquired a process.
- 24
- The ACQACTIVITY option was used, but the unit of work that issued the request has not acquired an activity.
- 25
- The PROCESS option was used, but the command was issued outside the scope of a currently-active process.
- 17 IOERR
- RESP2
values:
- 30
- An input/output error has occurred on the repository file.
- 31
- The record on the repository file is in use.
- 100 LOCKED
- The request cannot be performed because a retained lock exists against the relevant record on the repository file.
- 106 PROCESSBUSY
- RESP2 values:
- 13
- The request could not be satisfied because the process record is locked by another task.
