Re-configuring enterprise-specific traps

The IBM Workload Scheduler/NetView enterprise-specific traps are configured with default messages that will serve most users' needs. To re-configure the traps, choose Event Configuration from the Options menu. For instructions, refer to your NetView® documentation or online help. It might also be helpful to review the man page for trapd.conf(4).

The enterprise-specific traps and their positional variables are listed in Enterprise-specific traps. Trap descriptions are listed in IBM Workload Scheduler/NetView events.

Enterprise-specific traps lists enterprise-specific traps.
Table 1. Enterprise-specific traps
Trap Identifier Positional variables
1 * uTtrapReset
  1. Agent identifier number
  2. Software version
  3. HCL Workload Automation message string, if any

51  
52 *  
53 *

uTtrapProcessReset  
uTtrapProcessGone  
uTrapProcessAbend

  1. Process pid
  2. Program name
  3. HCL Workload Automation message string, if any
54 * uTrapXagentConnLost
  1. Program name
  2. HCL Workload Automation message string, if any

101 *  
102 *  
103  
104  
105 *  
204 *

uTtrapJobAbend  
uTtrapJobFailed  
uTtrapJobLaunch  
uTtrapJobDone  
uTtrapJobUntil  
uTtrapJobRerunPrompt

  1. workstation name of the schedule.
  2. Schedule name.
  3. Job name. For jobs submitted with at or batch , if the name supplied by the user is not unique, this is the HCL Workload Automation-generated name, and the name supplied by the user appears as variable 7.
  4. workstation name on which the job runs.
  5. Job number (pid).
  6. Job state, indicated by an integer: 1 (ready), 2 (hold), 3 (exec), 5 (abend), 6 (succ), 7 (cancl), 8 (done), 13 (fail), 16 (intro), 23 (abenp), 24 (succp), 25 (pend).
  7. Job's submitted (real) name. For jobs submitted with at or batch , this is the name supplied by the user if not unique. The unique name generated by Maestro appears as variable 3.
  8. User name under which the job runs.
  9. Name of the job's script file, or the command it executes. White space is replaced by the octal equivalent; for example, a space appears as 040.
  10. The rate at which an every job runs, expressed as hhmm . If every was not specified for the job, this is -32768.
  11. Job recovery step, indicated by an integer: 1 (stop), 2 (stop after recovery job), 3 (rerun), 4 (rerun after recovery job), 5 (continue), 6 (continue after recovery job), 10 (this is the rerun of the job), 20 (this is the run of the recovery job).
  12. An event timestamp, expressed as: yyyymmddhhmm0000 (that is, year, month, day, hour, minute, seconds always zeroes, hundredths always zeroes).
  13. The prompt number, or zero if there is no prompt.
  14. The prompt text, or HCL Workload Automation error message.

151 *  
152 *  
153  
154  
155 *

uTtrapSchedAbend  
uTtrapSchedStuck  
uTtrapSchedStart  
uTtrapSchedDone  
uTtrapSchedUntil

  1. Workstation name of the schedule.
  2. Schedule name.
  3. Schedule state, indicated by an integer: 1(ready), 2 (hold), 3 (exec), 4 (stuck), 5 (abend), 6 (succ), 7 (cancl).
  4. HCL Workload Automation error message, if any.
201 * uTtrapGlobalPrompt
  1. Prompt name.
  2. Prompt number.
  3. Prompt text.
202 * uTtrapSchedPrompt
  1. Workstation name of the schedule.
  2. Schedule name.
  3. Prompt number.
  4. Prompt text.
203 * uTtrapJobPrompt
  1. Workstation name of the schedule.
  2. Schedule name.
  3. Job name.
  4. Workstation name of the job.
  5. Prompt number.
  6. Prompt text.
251 * uTrapLinkDropped
  1. The to workstation name.
  2. Link state, indicated by an integer: 1 (unknown), 2 (down due to an unlink), 3 (down due to an error), 4 (up).
  3. HCL Workload Automation error message.

uTrapLinkDropped corresponds to link state 2) only.

252 * uTrapLinkBroken
  1. The to workstation name.
  2. Link state, indicated by an integer: 1 (unknown), 2 (down due to an unlink), 3 (down due to an error), 4 (up).
  3. HCL Workload Automation error message.

uTrapLinkBroken corresponds to link state 3) only.

* These traps are enabled by default.

Link states 1) unknown and 4) up are not used, as they are not relative to traps 251 and 252.