This general macro is used to increment the count dynamically for a
count-type event after the event has been defined via the EVNTC macro.
(See EVNTC-Define Internal Event.) An EVNWC macro cannot have been issued for the
event.
Format
- label
- A symbolic name can be assigned to the macro statement.
- LEVEL=Dx
- A core block reference word and file address reference word (ranging from
D0 to DF). The file address reference word on the specified data level
must contain the 8-character name of the event.
- BLOCK=address
- The address of an area that contains the event block formatted as defined
by EV0BK. The name of the event must reside in EVNBKN. The
symbol you specify can be either an assembler label or a register enclosed in
parentheses.
- Note:
- LEVEL and BLOCK are mutually exclusive. One or the other is
required.
- NFOUND=label
- A label where processing resumes if the event does not exist. This
parameter is required.
Entry Requirements
- When EVINC is coded with the LEVEL parameter, the symbolic name of the
event to be waited for must be in CE1FAx (where x is the specified data
level).
- When EVINC is coded with the BLOCK parameter, the symbolic name of the
event must be in the field EVNBKN in the area pointed to by the BLOCK
parameter.
- R9 must contain the address of the ECB being processed.
Return Conditions
- Control will be returned to the next sequential instruction (NSI) with the
count for the event incremented by one. If the event has not been
defined via the EVNTC macro, the NFOUND branch will be taken.
- The contents of R14 and R15 are unknown. The contents of R0 --
R7 are preserved across this macro call.
Programming Considerations
- This macro may be executed on any I-stream.
- The specified event must be a count-type event. An EVNWC macro
cannot have been issued for the event. If either of these conditions is
violated, a system error is taken and the ECB exits.
- The maximum number of times the count for an event may be incremented is
32767.
- Defined events in MDBF systems are subsystem unique. The NFOUND
branch will be taken if a match on the event name is found but the data base
identifier (DBI) of the issuer is not the same as that of the subsystem that
defined the event.
Examples
None.