an Integrated z/OS Event Management


PDF Manual

Normally computer systems need human intervention when certain cases occur. For example, a message occurs telling that a certain running job is waiting for reply to finish. Operator then reads the message and check the condition to decide what to reply. Such effort sometime takes quite awhile. No guarantee operator is watching console seriously when that message is occurred. Operator needs some amount of times to interpret and evaluate the message and make a decision what to reply. Moreover, there is no guarantee the reply is correct nor correctly keyed in. In the mission-critical situation, a simple mistake can potentially generate multiple serious and expensive problems.

System-events manager is the only solution for such above case. Decision is made by technical supports or system administrator, instead of operators, expressed as a list of parameters values, table entries or even script codes called action(s) and stored in the database. System-events manager then takes over this ordinary manual effort so operator could ignore it forever. System-events manager catches message internally before it’s displayed, even capable to suppress it, and fires appropriate defined action(s) to reply the message without any delay. No more incorrect reply is possible.

zJOS/Sekar© is one of system-events managers, It is a solution to establish automated action(s) execution in respond to the occurrences of several types of system events on z/OS operating environment. System can be a single or multiple networked z/OS hosts.


The above figure illustrate how zJOS/Sekar works. It softly cooperates with operating system (z/OS) to immediately responds to every occurrence of any event type and find appropriate users defined action(s) in the database table. All matched entries are then fired.

zJOS/Sekar was designed to answer some difficulties of other similar products which normally require users to code rules in Rexx or other scripting language. Although zJOS/Sekar also provides some rexx functions for users who love scripting, most of automation mechanism can be implemented just by fill up the events and actions tables. Neither specific skill nor scripting is required to establish system-wide automation.

zJOS/Sekar main functions are:

  • Facilitates users to define set of actions against each selected event
  • Automates firing all user’s defined action-sets based on event occurrences
  • In networked z/OS hosts, event-actions relationship can be one-to-one or one-to-many among hosts in the network


Integrated Events Management System




  • Supports message (WTO and WTOR), command, timing (TOD), end-of-job (EOJ) and end-of-job-step (EOS) types of events
  • Supports command, reply (to WTOR) and rule types of actions
  • Supports networking agent (TCP/IP) for:
    • Inter-hosts event intercepting
    • Inter-hosts actions propagation
  • Supports timeframe filter to control action execution based on user’s specified date-range, time-range, day-of-week and national holiday calendar



  • System is very critical box
  • System needs human intervention
  • Most of that needs are unsolicited or uncertained, or even intermittant
  • Human need think time delay
  • Sometime human can make mistakes
  • Mistake can causing fatal and expensive



  • Certain cases can be totally handled
    • Cases which can be handled by soft actions
  • Notifies the right person for cases that can not be totally handled
    • By message
    • By email
    • By cellular SMS
    • Or others



  • Execute predefined actions based on occurrence of known events without any single second delay
  • Knowledge Base support would be the best



Sekar is an event-driven automation tool for z/OS. It fires users’ defined actions exactly at the time the system event is occurred. On users’ choice, it can even suppress the event while the actions are fired.

  • zJOS/Sekar recognizes the following events:
    • Message (MSG)
    • Command (CMD)
    • Time-of-day (TOD)
    • End-of-task (EOT) – under construction
    • End-of-step (EOS)
    • End-of-job (EOJ)
  • zJOS/Sekar provides 3 action types against each event:
    • Command
    • Reply (to WTOR MSG event only)
    • Rule (user’s rexx exec program)