> The thing that always cracks me up is that all one has to do in a U2/PICK > environment is to create q pointers to the main account from the test > account. You can look and even modify without having access to that account > unless it is locked down by logon at the OS level, which I have yet to find > and as a consultant I have worked on several 'sox compliant' boxes. > > You can even compile a program in the test account, and then copy that to > the main account via q pointers as long as you copy the voc pointer as well. > You have to be sure you get the right path for the object code, but that's a > piece of cake, and then the sox auditors would have absolutely no way of > finding out who did what if you just delete the q pointers when you're done. > > Not that I would do such a thing (because I get paid by the hour and the > more complicated the procedure the longer it takes), but it is possible. > > fwiw, > > Allen E. Elwood www.tortillafc.com
Well, there goes any new U2 install's in a SOX company. No decent auditor is going to stand for anything like that. Richard ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
