Hi all,

        I'd like to get some ideas/info on how others solved the 'access
to the spool file' SOX issue.  My current aggravation with the auditors
is as follows: We have a snag in our production data, and I have to run
JCL jobs in production to try to find the hosed data.  To run these
research JCL's, I have to use my logon with BA access in the job card of
the JCL so that if I try to change the production data using these JCL's
while doing research, my user will be tracked in the log files for the
changes...geeez .  However, I, myself, can't log onto production as an
online user (IA access), I can only log onto develop with IA access, so
I can't view the STDLIST created by the JCL I've run.  I don't want to
have the operators copy the spool files to my private account every time
the job is run, and the auditors won't let me view production spool
files (the word ridicules should come in here somewhere, but...).  Also,
I can't run GOD (the auditors nixed that long ago), or do a CHGLOGON.

        So, any help with this would be great. 

	
TIA (and have a great week!),

Ray Shahan

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *