Inquiry commands

You can use a program to get details of a specific BTS object by issuing an INQUIRE command instead of browsing for the object. Note some limitations about using the INQUIRE command.

The objects that you can inquire about include:
  • Activities
  • Data-containers
  • Events
  • Processes
  • Process-types
  • Timers.

The object inquired upon might have been located by browsing. For example, a program can use a browse to locate an activity, then issue an INQUIRE ACTIVITYID command to find out the name of the program associated with the activity, the userid under whose authority it runs, or its current completion status.

Note: All INQUIRE commands try to locate a record on a BTS repository data set, and to read information from it if found. This operation does not obtain an exclusive control lock for the record; therefore the data in the record might change while the operation is taking place.

Be careful when issuing INQUIRE commands from within programs that execute as part of an activity, if the commands refer to records which might be modified by the same program. The INQUIRE command always goes to the repository for the record it needs, and might not see changes made by the program. This can lead to unexpected results. For example, a program might define a new activity and then issue a command to inquire upon it, only to be told that the activity does not exist (because the activity-record has not yet been committed to the repository).



dfhp9c00127.html | Timestamp icon Last updated: Monday, 5 June 2017