Event code 20 — query/build feedback code event
Purpose
The Query/Build event handler is used to convert 12-byte character strings to condition tokens and condition tokens to 12-byte character strings.
Syntax
Call CEEEVnnn (20, function_code, additional_parms, ownership)
INT4 *function code;
INT2 *cond_name;
CHARn *cond_token;
INT4 *ownership;
- function_code (input)
- Defines if this event is a query or build function. The functions
are defined as follows:
- 1
- Fixed-binary(31) indicating query feedback token event
- 2
- Fixed-binary(31) indicating build feedback token event
- additional_parms (input/output)
- Parameters specific to a certain function code. The following
parameters are for each function code:
Figure 1. Syntax by function_code
Call CEEEVnnn (20, 1, cond_name, cond_token, ownership)
Call CEEEVnnn (20, 2, cond_token, cond_name, ownership)
- cond_name (input/output)
- A halfword-prefixed character string symbolic condition name.
- cond_token (input/output)
- A 12-byte condition token that is constructed from the symbolic name. The I_S_Info field is set to binary zero.
- ownership (input)
- Fixed-binary (31) set to contain
- 0
- This member does not recognize this cond_name
- 1
- For query, this member recognizes this cond_name and has filled in the cond_token. For build, this member recognizes this cond_token and has filled in the cond_name.
Usage notes
- If the condition token is unrecognized, the value of cond_token is undefined.
- Language Environment recognizes only those cond_names that start with cel; and have a corresponding message within the Language Environment message set. If Language Environment does not recognize the cond_name, then all of the active members are invoked by the event handlers polling each member until one claims the cond_name returning the cond_token. Each member can validate if the condition token exists within their message set by the CEEGETFB CWI. If the cond_name remains unclaimed, the appropriate feedback code is returned.