EASY/Exit is a powerful tool for installations that want to replace existing exits and take advantage of all the ‘hidden’ functionality available in z/OS subsystems such as DFSMShsm, FTP, MPF, TSO, JES2, and others without the need for assembler language code or complex recovery procedures.
EASY/Exit’s flexible, extensible architecture allows the use of simple IF-THEN-ELSE policy rules to get control at exit points to perform tasks like:
- Implement DFSMShsm calendar processing to avoid migration over holidays
- Manage FTP file transfers, including examining, altering, or rejecting commands, users, or IP addresses
- Allow emergency TSO ‘firecall’ logons and control other TSO logons
- Dynamically direct jobs to use specified JES2 classes, scheduling environments, or other attributes
- Peform rules-based recording, suppression, change, and processing of WTOs, WTORs and other messages
- And much more!
z/OS, OS/390, and many IBM program products provide exits which give installations the ability to extend the scope and functionality of the system. Many companies gain a strategic advantage over their competitors through the use of customized system and product exits to provide critical features and function unavailable elsewhere. However, the use of such exits has sometimes been problematic because exits:
- must be coded in assembler language
- often run in an APF-authorized environment in key 0
- sometimes required an IPL to activate or remove
- usually require system programming specialists to develop and maintain
- rarely have imbedded recovery and debugging facilities
Eliminating the Need for Programming – EASY/Exit contains code which interfaces with each supported exit point. This code performs the required initialization and termination for the exit as well as establishing a recovery environment in case of errors. Most importantly, though, the code provides access to all of the exit’s input and output parameters in the form of easy-to-use variables which can be examined, set, tested, and manipulated without the need for any programming. The code established by EASY/Exit has everything except the logic your installation wants to implement, which you provide with a set of simple, flexible, IF-THEN-ELSE rules.
The IF-THEN-ELSE Language – Your installation logic is implemented with the same IF-THEN-ELSE rules language used by all DTS Software products. EASY/Exit makes the input and output parameter information available as symbolic fields to the rules language, along with many other variables that may be useful in providing the required function.
For example, the following rule allows additional CPU time for critical jobs running over the weekend. In this example, jobs whose names begin with the characters ’PR’ (indicating, perhaps, an important production job) are allowed up to 5 minutes of additional CPU time, in one-minute increments, if the job is executing on a Saturday or Sunday. During the week, the normal CPU time limitations apply.
DEFRULE MORETIME IF &ENV = JOB_CPU &JOBNAME = PR* &JOBSDAY = (SATURDAY, SUNDAY) &JOB_CPU_EXT LT 4 THEN SET &ADDITIONAL_TIME = 60
DEFMSG USERMSG ’CPU TIME WAS EXTENDED BY 60 SECONDS’
The rules language can be changed at anytime, and updated with a simple DIF REFRESH command. The rules language has extensive debugging facilities, so you can run test jobs to watch the flow of logic through the rules.
Consolidated Rules Logic – The rules used by various exits can be consolidated into a single file, or grouped into different members based on exit type. Each exit runs the rules language with environment variables (&ENV, &ENVS) set to unique values. The rules can test the environment variables, and set the other necessary variables accordingly.
Exits that Communicate – The product provides many capabilities that are far beyond the scope of a typical exit. Most hand-coded exits are used to make simple yes or no decisions and pass a return code to the caller. In contrast, EASY/Exit allows installations to make much more detailed and sophisticated decisions in the rules logic. The rules can dynamically build messages and/or records, and write them:
- to the TSO or JOB that called the exit
- as SMF records
- directly to specified TSO users
- to log files allocated to the DIF started task (this can be done from environments that don’t allow I/O). The log files can be sequential or VSAM KSDS data sets.
- to MQSeries message queues
- to TCP/IP ports
Performance – Most of the products written by DTS Software execute in very performance sensitive areas of the operating system. The code used by EASY/Exit uses the same design methodologies and practices as the rest of the DTS products. Our developers are always concerned about performance, and we have been very successful at creating products with very low overhead. In the usual case, the overhead of EASY/Exit processing should be so low as to be unmeasurable.
EASY/Exit uses proven technology – The developers at DTS Software have been writing highly sophisticated and functional system software products for many years. EASY/Exit makes use of technologies written for the company’s system software products to eliminate the need for assembler-language coding and allow the use of exits in a way that is much easier to use and much more reliable. Logic implemented through EASY/Exit can be activated or removed instantly through the product’s Dynamic Install Facility (DIF). No IPL is ever required.
Currently, EASY/Exit supports approximately 30 exits.
- z/OS Exits
- DFSMShsm Exits
- ABARS Exits
- Recovers abilities lost with diminished Assembler skillets
- Replaces assembler exits with CLIST like language exits
- Prevents production job failures (S322, S522, tape mounts)
- Exploits functionality of z/OS, DFHSM and ABARS exits
Ease of Use
- Simple English-language rules
- Installs from a CD, tape or web download
- No SMP/E or IPL necessary
The marketing literature is available to all visitors. The product manuals are only available to registered customers and companies trialing DTS products – login is required. To request authorized access, please complete the Registration form. DTS customer support will review your request. Upon approval, you will receive access notification by E-mail within one business day.
|Oct 26 2017||65.81 MB||59 Minutes|
|Feb 09 2017||55.11 MB||50 Minutes|
|Jun 16 2016||76.89 MB||53 Minutes|
|Dec 18 2014||70.89 MB||46 Minutes|
|Jun 26 2014||63.28 MB||43 Minutes|
|Feb 26 2013||107.04 MB||55 Minutes|
|Dec 13 2012||79.79 MB||56 Minutes|
|Jun 07 2012||94.90 MB||55 Minutes|
|Managing Your z_OS Storage Environment More Efficiently||Oct 25 2011||99.80 MB||56 Minutes|
|EASY/Exit Product Sheet||Oct 26 2019||350 KB|
|EASY/Exit Questions||Feb 26 2011||96.27 KB|
|Policy-Based Control over System Resources||Feb 26 2011||146.37 KB|
|EASY/Exit for DFSMShsm||Feb 26 2011||104.96 KB|
|EASY/Exit Overview||Feb 26 2011||167.94 KB|
|EASY/EXIT User’s Guide||May 24 2018||1.42 MB|
|Product Installation Guide||Nov 01 2018||1.04 MB|
|Rule Language Programming Guide||May 24 2018||1.55 MB|
|SCC Messages Manual||Nov 15 2018||1.02 MB|
All DTS products rely on the Dynamic Install Facility (DIF). In fact, about 90% of the code in a DTS product is actually part of DIF – modules called “Common Service Routines”. Besides actually installing and removing products, DIF controls the rule compiler, console interface, memory management, record logging, and trace facilities.
Since DIF is capable of hooking almost anything in an operating system, the concept of creating a product that dynamically installs system exits was frequently discussed by our developers. The product would use small generic exits that handle everything except the exit logic required by an installation. The customer would simply code rules in a high-level IF-THEN-ELSE language that’s easy to change, and has far greater functionality and debugging capabilities than anyone would be willing to write using an in-house assembler exit.
The first version of the product was delivered in January 2003. Support for additional exits has been added over the years – usually at customer request.