EVENT SERVICES START Command Format
The EVENT SERVICES START command enables you to start a specific notification request for event data. This command provides parameters where you can define what data (date, time, and sequence) is sent to your application.
The EVENT SERVICES START command uses the following format and parameters.
| Command | Parameters |
| EVENT [SERVICES] START | ID=event-request-name |
| WHERE=(STARTT | LASTSEQ | KEEPRREC | ( for CICS only)TRACE) (CICS only) |
Required Parameter
The EVENT SERVICES START command has one required parameter.
- ID=event-request-name
- specifies the logical name of the event services request to start. Specify this name in a CREATE EVENT SERVICES command.
Optional Parameters
The following parameter is optional for the EVENT SERVICES START command.
- WHERE(STARTT | LASTSEQ | KEEPRREC | TRACE)
- sets restriction on event records meeting the following selection criteria.
- STARTT=([date|day][,hh:mm:ssXM])
specifies selection by designated starting date and time. STARTT must be a date and time prior to the current time. If you specify this parameter, the event records retrieved from the statistics file begins with the date and time you specified, and continues until the current time is reached. At that point, event records are processed as they occur.
For a complete explanation of the subparameters, refer to EVENT SERVICES CREATE Command Format.
- LASTSEQ=n
- specifies the last sequence number (for Restart capability) associated with the date/time stamp. Use this parameter with the STARTT parameter. This information is provided by CICS when you issue a CREATE EVENT SERVICES REQUEST command for an event services request that finished abnormally.
- KEEPRREC (CICS-only)
- specifies that the restart record created by IBM® Connect:Direct® is kept, regardless of whether the event request completed abnormally or not. If KEEPRREC is not specified, the restart record created by IBM Connect:Direct is deleted if the event request completes normally.
- TRACE (CICS-only)
- specifies that every event record placed on the CICS TDQ is also written to the NDMTRACE temporary storage (TS) queue. You can use the NDMTRACE temporary storage queue to verify that EVENT records are flowing to the transient data queue.
Sample Command
Following is an example of the EVENT SERVICES START command.
|