The Audit System for IWS for z/OS (aka TWS for z/OS)

1

• TWS/Audit

• The Audit System for IWS for z/OS (aka TWS for
  z/OS)

2
What is TWS/Audit?

• TWS/Audit is a change documentation system for
  IWS z/OS

• TWS/Audit tracks and documents all user
  modifications made to
• The definition database
• (WS, Calendar, Period, AD, OI, Specres, ETT,
  JCLVAR, RunCycle)
• The LTP (long term plan)
• The CP (current plan)
• The JS file (JCL)
• TWS/Audit tracks and keep versions
• TWS/Audit allows to compare versions
• TWS/Audit allows to restore old versions

3
How does it work?

• TWS/Audit consists of
• VSAM database
• ISPF Dialog
• Set of Batch Jobs for reporting, housekeeping and
  maintenance.
• TWS/Audit is reading the TWS job tracking log
  files
• (JT-Files and/or the daily EQQTROUT file)
• TWS/Audit detects what happened and writes the
  change information to the VSAM file.
• TWS/Audit automatically creates (old) versions of
  all IWSz definition objects and keeps them as
  long as you want
• The ISPF Dialog enables you to search for these
  changes
• (see next slides)

4
TWS/Audit - Main Panel
This is the main panel of TWS/Audit. Select the
desired option.
5
TWS/Audit - Applications
Option 4 offers the search panel for application
descriptions, e.g. search for changes on
applications HOR
6
TWS/Audit - Applications
The result list shows the Application id, Type,
Status, Valid from/to
the Action (Insert, Update, Browse, Delete)
last update Date, Time, User
7
TWS/Audit - Applications
Use line commands to e.g. Browse or Compare
Versions, Select compares with the previous
version
8
TWS/Audit Applications, compare
The new version
The old version
9
TWS/Audit Applications, compare
F gt guides you to the changed values
10
TWS/Audit Applications, find changes
Here for example, operation 012 was changed WS
CPU to DMY and Duration to 000130
11
TWS/Audit Applications, restore to TWS
HOR1111 was deleted by Userid P390K. If you need
it again, you can Restore it to TWS by
TWS/BatchAD or Generate Batchloader statements
12
TWS/Audit Applications, restore to TWS
Submit the generated Job to load it back to TWS
13
TWS/Audit - Main Panel
Its basically the same for all these objects,
except JS and LTP, they have no restore function
and for CP there is an extra report to show all
details.
14
TWS/Audit - MCP
MCP allows to search for manual changes
(Modifications) in the CP, e.g. in a specific
time rage and done via Dialog, or PIF or other
special functions.
15
TWS/Audit - MCP
and the action, e.g. ADD-AD (add appl), MOD-OP
(modify oper), RER-OP (rerun/restart oper) etc.,
scroll right to see the timestamp, IA-Date/time
end more
The result list shows the Application id, Op no.,
Jobname
16
TWS/Audit - MCP
Linecommand T shows the TWS update record, in
case of Modify-JCL also the JCL, stored in the
JS (compare with S)
17
TWS/Audit CP Report
While TWS/Audit MCP keeps only key data, you
can use option CP to create a detailed report
18
TWS/Audit CP Report
Specify the tracklog to be read, JT-Files or
older EQQTROUT files (GDGs)
19
TWS/Audit CP Report
For example List all jobs that where changed
manually (Dialog) in the last hour
20
TWS/Audit CP Report
Generate and submit the job, the report will be
stored in a file
21
TWS/Audit CP Report
After the job ended, option 3 shows you the result
22
TWS/Audit CP Report
Somebody set the job to completed
23
TWS/Audit CP Report
Scroll down to see all details, the userid and
the timestamp of the MCP action
24
TWS/Audit - Summary

• A brief summary of TWS/Audit functions

• TWS/Audit documents all changes made to
  definition database of IWSz, to the LTP, the CP
  and to the JS file
• TWS/Audit tracks all versions
• TWS/Audit allows searching and comparing of all
  versions
• TWS/Audit allows to restore old versions of
  application description, workstations, special
  resources etc.

25

• TWS/Audit

• Many thanks for your attention