On Feb 1, 2008, at 7:39 AM, Gary Green wrote:
I just glanced at this before I head off for something else, and I
may not
understand fully what you're saying...
Why would you need to "own the programs"? The possible solution I
offered
up should work without any vendor programs being touched.
Basically, the SMF records are intercepted by YOUR IFASMFDP exits
before
they are dumped , and modified ever so slightly. The vendors
programs have
nothing to do with this. By the time the records are intercepted, the
vendor's code has already forgotten about them.
If the processing of the SMF data in question is all in-house, this
should
work just fine. Even if the SMF data dose go out of house, code
another
couple of exits for IFASMSFDP to reverse the modifications and then
dump the
data to, say, tape for sending the data out.
Does this make sense?
-----------------Yes/no....
The auditors were vocal about any change to raw smf data. We looked
into doing a transformation ourselves and presented it to the
auditors and they said "NO" well... if we did we had to maintain
unedited copy and we were back to square one with the number of tapes
issue.
Ed
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
