Functionality Provided by

Both eventACTION and ussACTION, or

Component Feature

eventACTION only

ussACTION only

Change Tracker

• Tracks changes to PDS, PDSE, PS, VSAM Datasets and USS Files and Directories
• Tracks changes in the Dynamic LPA
• Quick and easy definition of resources
• Holds statistics on who made the change, when, with which program, DDNAME etc.
• Can take Backups of all changes if desired
• Able to Restore elements to any stored version
• Very low overhead and very low usage of CSA and ECSA
• Multiple systems can share one or more databases, but ussACTION data must be on the primary database.
• Full set of standard reports and maintenance jobs
• Excludes function to allow such products as IMS, DB2, SMP/E or Endevour to do their changes without hindrance
• Health Checker for various eventACTION functions
• Tracking of changes continues even when the eventACTION STC has been stopped
• Provides a complete and secure audit trail
• COMPARE - A powerful horizontal side-by-side compare utility for both normal and eventACTION data. You can even compare a VSAM with a PS dataset
• Low administrative overhead once the systems has been fully defined and tuned. This process usually last about 3 to 6 months

• Ability to restore a complete dataset back to the point of loss or damage (no loss of changes)
• Can be defined down to the Member level
• SCAN Function to quickly determine what was changed in a selected area and time-frame
• Own Scheduler for both eventACTION and non-eventACTION jobs/reports

• Tracks Permission-Bit changes

Change Manager (includes Change Tracker)

• Allows the user to prevent changes to datasets unless the pre-requisites have been met:
  • Change Request, and optionally
  • Change Authorisation on one or more levels, and optionally
  • Change Scheduling to ensure that the change is made at a specific point in time.
• Change Requests can be chained with pre-requisite changes
• Changes can no longer bypass the system

• Has special IPL volume protection
• Has a Blackout function to prevent changes from being made to certain resources during a particular interval
• Company specific fields and panels can be added to eventACTION

Reference Tracker

• RT - Allows the user to clean up internal datasets such as production LOAD libraries, REXX, JCL, CLIST, PANELS, uss Files and Directories etc. Over the space of one year elements that have not been referenced can be identified.

• RTDS - Allows the user to identify datasets (such as older versions of products) that are either no longer in use or are being used by one or two persons who have not migrated to the latest version. This can also track Tape Datasets since V7.08.
• RTM – Allows tracking of a particular program showing from which dataset the program was executed
• PXC – Product Execution Control – requires RT. PXC can enforce the usage of products, allowing them only to run on licensed LPARs

• RTF – Allows tracking of a particular file.

Command Manager

• Tracks all MVS and JES2 Commands
• Allows a particular command to be located quickly
• Through controls can prevent users, STCs or Jobs from issuing commands from specific locations such as TSO, or a batch job or from a non-authorised console
• Saves time wasted in searching through SYSLOG

Communications Manager

• Is the vehicle used to propagate or distribute Change Requests and/or changes from one eventACTION Changeplex to others
• Allows the user to compare datasets or volumes between Changeplexes (E.g. Compare SYS1.PARMLIB between Hannover and New York)

testACTION

• Permits faster and more transparent testing of new versions of Program or OEM Products
• Shortens the implementation cycle of new versions of products