ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

OPSMVS - Getting OPSLOG event data into a sequential file.

book

Article ID: 53359

calendar_today

Updated On:

Products

SOLVE:Operations Automation SOLVE:Access Session Management SOLVE:FTS OPS/MVS Event Management & Automation SOLVE

Issue/Introduction

Some clients may feel the need to place various OPSLOG event data into a sequential file. The most effecient way to do this is by using a combination of an AOF event rule, an OPS/REXX program and an RDF table that will store the event data that can be written to a pre-allocated sequential file.

A sample AOF MSG rule is documented in.............OPS.SAMPLE.RULES(ABENDLOG).
A sample OPS/REXX program is documented in.....OPS.SAMPLES(ABENDLOG).

Outline of the logic flow of this sample application:

  1. Sample ABENDLOG AOF rule processes the triggering event (IEF450I) and inserts desired event data into a RDF table. (table is created by logic in rule)
  2. A dynamic TOD rule created within the ABENDLOG AOF rule will trigger this OPS/REXX program.
  3. Logic in this program will simply read the data stored in the RDF table, and write to some preallocated sequential data set. The logic should of course be modified to meet the specific requirements of the application being created.

Environment

Release:
Component: SOPMVS