 |
 |
|
zCBT Automation Rexx Functions to Manage System Events |
||
|
|
|
zCBT Automation Rexx Functions to Manage System Events |
||
| Modern IT is indicated by how complete, how secure and how easy it serves people. Automation is one of most major factors. Never say that your system is a modern IT unless it has already been automated. Major things which required to be automated are event management system (EMS) and jobs or workloads scheduling. |
| Automation, however is an expensive solution. It becomes the most expensive stuff when you utilize them less than 50% of its capabilities. Normally, people can optimally use workload scheduler. Nevertheless, for EMS, in fact, people use less than 50% of its capabilities. Even in some places around south east Asia, they use less than 10%. Just to respond to some messages during system startup period. For such environment, zCBT is the best choice. This toy is quite capable to provide such solution, even more. |
|
zCBT is a miniature of zJOS. zCBT is the simplest solution for z/OS system event management at no cost. You don’t need special skill to automate your system using zCBT. Once zCBT is properly setup, you will very able to manage your system events using very simple rexx scripting. All you need is rexx skill. zCBT is a combined of subsystem functions and resource manager which run on z/OS as a subsystem, instead of an address space. zCBT subsystem supports 5 types of events: 1. Messages (MSG) events for both WTO and WTOR. Message is trapped before sent to console, hence you can optionally suppress it. By trapping substring of message text, you can do several actions. For WTOR message, you can reply it. 2. Command (CMD) events. Command is trapped before sent console, hence you can optionally suppress it. This is an opportunity for you to have your own console commands. By preparing rexx routine to trap certain command verbs (regardless they are valid commands) and their associated actions, you will have your own commands. 3. End-of-jobstep (EOS) events for both jobs and STCs. EOS event is trapped at almost the time of its occurrence and reporting condition codes. If you are a smart programmer, by using zCBT you can develop your own scheduler in rexx language. 4. End-of-job (EOJ) events for jobs and STCs. EOJ event is simulated from all related EOS previously occurred. Hence, there is a short time delay (less than 1 sec). 5. Time-of-day (TOD) events. TOD is very common event people can trap. Internally it just STIMER or STIMERM macro which doesn’t need authorization as privileged routine. Since rexx able to obtain date and time, zCBT only support TOD time event for both clock and interval time. The way zCBT subsystem supports system automation is by providing some rexx functions. Request regarding which event you want to trap is sent to zCBT subsystem as function arguments. Trapped event information is then returned to you as result value of the function. Although rexx is executed synchronously, you can however, trap multiple events within a single rexx program. |
 |
 |
Product Summary | |
| Name | zCBT Automation | |
| Type | Subsystem | |
| Environment | z/OS (with JES2) | |
| Special | Sensitive, APF authorized | |
| Coding | Assembly | |
| Author | Deru Sudibyo | |
| License | Freeware | |
| Note | This product will also be available in CBTTAPE very soon. | |
| Download The complete package is bundled in TSO XMIT format. Follow installation instructions in zCBT guide provided in ZIP file. |
