DAEVENTS file

The DAEVENTS file, the output generated by CTMEVRT, lists the extracted DSNEVENTs. The DAEVENTS file is used as the input to the CTMEVEX utility, which executes the DSNEVENTs’ DO actions. However, first the user must review and edit, if necessary, the list of DSNEVENTs, making sure that the actions to be executed are still required and will not interfere with current CMEM/Control-O processing. Special attention must be given to duplicate actions (marked with *DUP*); for example, making sure that duplicate forced jobs are appropriate.

The user can use a regular editor, to review and edit the DAEVENTS file. The user can prevent DSNEVENTs from being executed by removing them from the file or, preferably, commenting them out by inserting an asterisk at the beginning of the line.

Since the report will include DSNEVENTs that occurred prior to the CMEM/Control-O outage, it is the user's responsibility to remove DSNEVENTs that had already been handled by CMEM or Control-O.

The DAEVENTS file

• is a sequential dataset in readable format that can be modified by the user
• is sorted in chronological order
• treats any line beginning with an * as a comment
• begins with a headline that has column headers which are described in the following table:

  Table 120b Column headers for the DAEVENTS file

  Column header	Description
  Date	Date displayed in the following format: yyyy/mm/dd
  Time	Time displayed in the following format: hh:mm:ss
  SID	The System ID where the event occurred
  Data Set Name	Name of dataset that triggered the event.
  C	Indicates catalog status. Valid values: Y - Cataloged N - Not Cataloged
  Jobname	The name of the job that triggered the event
  JobID	The Job ID of the job that triggered the event If the event was triggered by FTP, only the job number is displayed.
  UserID	The User ID of the job that triggered the event
  Disp	The data set disposition that triggered the event (for example, “C”, “D”)
  StepName	The name of the step that triggered the event
  ProcStep	The name of the procedure step that triggered the event
  StepRc	The return code of the step that triggered the event.
  RuleName	The name of the rule that caught the event. The format is xxxx-TableName:RuleName where the xxxx is the DACTMLST entry sequence number as listed in CTMR3DI.
  Action	DO action (for example, DO COND FILE-ARRIVED +/DO FORCEJOB JOB1). CMEM/Control-O AutoEdit variables, if any exist, are resolved. Note: If two (or more) DO actions are defined for an event, they will appear as two identical events, but with different DO actions.
  Dup-I	A duplicate indication is given when a DSNEVENT and its associated action appear more than once (with the same data set name and disposition and the same action) in DAEVENTS
  Comment	Comments: (*) Unsupported action - not executed – actions other than DO COND and DO FORCEJOB (!) Sched / IN conditions in the rule - actions for rules that have scheduling criteria and/or IN conditions (?) Conditional-IF/WHILE/TERM precedes - actions that have a preceding IF or TERMINAT statement