Release 7.09

March 29, 2010 For a printable version of Release 7.09 highlights select this pdf.

TCP/IP Session Manager

The eventACTION TCP/IP Session Manager provides the ability to communicate with eventACTION via TCP/IP. It provides an infrastructure for use by other eventACTION components. Clients can include instances of eventACTION running on different hosts as well as user-initiated functions.

It is Action Software International's intent to eventually replace all functions in the LULU component with equivalent functions using TCP/IP.

For this release, eventACTION includes a new utility that transmits eventACTION database options from one Changeplex to another using TCP/IP. A separate description of this application is available upon request.

NOTE: This feature is currently under Beta test and is subject to further change. Please contact Action Software International if you wish to test this feature, and provide feedback regarding the results of your testing.

Health Checker

Additional health checks have been added:

PXC definition check
This will check a PXC definition to ensure either the library name specified is defined to RT or the program name is defined to RTM.

BLDL hook status check
the eventACTION BLDL SVC hook is required for RT, RTM, PET and PXC. If the BLDL hook is no longer active or not being called (e.g., masked by other products), this check will issue a warning message.

eventACTION status check
A warning message will be issued if eventACTION has become inactive.

eventACTION monitor task status check
The eventACTION monitor task, MZ1ZMON, is required to monitor the status of various eventACTION internal control blocks. It will also monitor and/or expand various work queues. If this task is inactive, a warning message will be issued.

Health Checker UDP server

The eventACTION Health Checker UDP server is a new Beta feature and can be activated by adding the following statement to the eventACTION initialization parmlib member MZCPRMxx:

UDPSESSMGR=YES

The eventACTION TCP/IP Session Manager must also be activated. Please refer to the relevant parts of the TCP/IP Session Manager documentation for security setup, host definition and port reservation. When this new feature is activated, eventACTION alert messages will be propagated to all systems in the same Changeplex.

NOTE: This feature is currently under Beta test and is subject to further change. Please notify Action Software International if you wish to test this feature, and provide feedback regarding the results of your testing.

Change Tracking

Notification – Using the options at OID level only (DES line command on the list of OIDs), you can specify a user group to be notified when data sets under that OID are changed. Prior to this release, this option only sent a message indicating the data set and volume to avoid flooding users with messages for every individual member changed. An option has now been added to the panel so that you may specify a job-id of a scheduled but suspended global reporting job that is defined to report on all the changes to datasets under that OID. The report job must be defined by a global administrator as a GLOBAL job (group name must be GLOBAL) and should be set up to report on all changes under this same OID since the last time this scheduled job ran. It should be scheduled to run every hour of every day and then suspended. It should also have email options defined to send the report output to the same user group as the notification messages set under the OID options.

The notification messages will still be sent once in an hour any time a change is detected, just as before, but if a report job is specified, then that job will be unsuspended when the notify message is triggered and so the job will be run at the next scheduled hour with the intent to be automatically suspended again. This job will list all the member-level information for all members changed in that time period and then this information will be emailed to the notification recipients.

For further information on the steps to follow to implement this procedure, please refer to the help panel that describes the notification of changes within the OID-only options.

USS Change Requests from Batch

You can now create USS Change Requests from batch. To create USS Change Requests, specify PARM=USS on the EXEC statement for the job step.

Only ACTION=NEW is supported.

The following new SYSIN statements have been added:

DIR= directory name (case-sensitive)

FILE= file name (case-sensitive)

Change Requests from Batch (USS and non-USS)

A new SYSIN statement, DUR=nnn, has been added to specify “Number of days Change Request Info to be kept after it is closed”.

Note: Normally this number is specified on the SUMM panel. When you create a new Change Request, the value on the DUR= statement is used. If DUR= is not specified, then the value on panel 3/4 of “Options to be used at OID Level” is used.

Security Definitions

Any eventACTION security profiles that previously had to be defined in resource class $MZCA can now be defined in resource class FACILITY if class $MZCA is not active. This eliminates the need to create a new resource class just for eventACTION. Please note that if class $MZCA is active, class FACILITY will not be checked. If you are already using class $MZCA you can continue to do so.

DFSMSdss Interface

The eventACTION DFSMSdss interface can now track full and partial physical volume dumps. The changes are tracked under pseudo data set name “.VOLUME.DUMPED” and the volume ID of the volume that was dumped. To make use of this feature, define options for data set name .VOLUME.DUMPED (note the leading “.”) and volume *.

Reference Tracking

RT and RTM Activation

Prior to Version 7.09, eventACTION's RT and RTM functions were always automatically activated whether the installation used them or not. Starting with 7.09, these features can now be explicitly turned off when specified in the startup parameters. To turn off these features, include the following statements in the eventACTION initialization parmlib member MZCPRMxx:
RT=NO
RTM=NO

Dynamic LPA Tracking

A new beta feature has been added to allow RT, RTM and PXC to track and/or control the execution of modules that are loaded into the Dynamic LPA Area..
To activate this feature, add the following statement to the eventACTION initialization parmlib member MZCPRMxx: RTDLPA=YES

. . . . . . . . . . . . . . . .
The End.