Re: [U2] Remote (qfile) restrictions - (UV)
It sounds like an example of using a program to simulate TCL access. In that way, you can select who can do what via programming. In our menued business system, access to TCL is granted to anyone who knows to type OUT at a menu prompt. I wrote a line of code to change what happens when 'OUT' is typed depending on the user doing the typing. After that, I have limited commands granted to each user. This method doesn't affect program control of remote files. HTH, or at least gives some ideas. Karl quote who=John Rodgers On UniVerse version 9.6.1.6 HP-UX We can create q-pointers to any directory path on the system such that writes to a q-pointed file will write to the specified directory. Is there any way to restrict that mechanism to prevent accidental access. Our Production account is mirrored from the Production box onto the backup (DEV) box as a (disaster recovery) account. As such we need to be able to restore /activate it at short notice. BUT We do not want any inadvertent updates to that account via these q-pointers. Ideally I would like UniVerse to tell me that I cannot create a q-pointer to a 'restricted' area. I don't think it will do that. I do not want to change the unix permissions because that could interfere with the DR copying processes and would probably need to be undone if we need to switch over. Any ideas would be welcome. Cheers John Rodgers --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- karl _/ _/ _/ _/_/_/ __o _/ _/ _/ _/_/ _-\._ _/_/_/ _/_/_/ (_)/ (_) _/ _/ _/ _/ .. _/ _/ arl _/_/_/ _/ earson[EMAIL PROTECTED] -- IT Director, ATS Industrial Supply, Inc. http://www.atsindustrial.com Toll-free: 800-789-9300 x29 Direct2Desk: 801-978-4429 Facsimile: 801-972-3888 -- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Remote (qfile) restrictions - (UV)
Couldn't you put a user subroutine on the SET.FILE verb that deals with this? We do that for all kinds of uv verbs to deal with access. -Dianne John Rodgers wrote: On UniVerse version 9.6.1.6 HP-UX We can create q-pointers to any directory path on the system such that writes to a q-pointed file will write to the specified directory. Is there any way to restrict that mechanism to prevent accidental access. Our Production account is mirrored from the Production box onto the backup (DEV) box as a (disaster recovery) account. As such we need to be able to restore /activate it at short notice. BUT We do not want any inadvertent updates to that account via these q-pointers. Ideally I would like UniVerse to tell me that I cannot create a q-pointer to a 'restricted' area. I don't think it will do that. I do not want to change the unix permissions because that could interfere with the DR copying processes and would probably need to be undone if we need to switch over. Any ideas would be welcome. Cheers John Rodgers --- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Remote (qfile) restrictions - (UV)
John, One way of accomplishing this is to: (this varies base on what flavor you are running (UniVerse IDEAL/PICK/REALITY/PRIME...) This example is UniVerse/Pick flavor 1- Copy the SET-FILE VOC entry to SET-FILEB 2- Write a program that will prompt you for the account name and file name, **BETTER YET,**DON'T prompt SENT = TRIM(@SENTENCE) ANAME = FIELD(SENT, ,2) FNAME = FIELD(SENT, ,3) IF ANAME = OR FNAME = THEN PRINT Usage: SET-FILE account_name file_name STOP END *This way, if your PRODUCTION app's is using the SET-FILE then your new program handles it. 3- PERFORM the SET-FILEB with account name and file name ONLY if it passes your EDIT (restricted area) or create an ARRAY and write to the VOC file. 4- DELETE VOC SET-FILE 5- AE or ED VOC SET-FILE 6- 001 PA 7- 002 YOUR PROGRAM NAME or CATALOG your new program 8- PS. TEST and DEBUG..hope it helps. 2 1/2 cents please... Cheers, Angelo On UniVerse version 9.6.1.6 HP-UX We can create q-pointers to any directory path on the system such that writes to a q-pointed file will write to the specified directory. Is there any way to restrict that mechanism to prevent accidental access. Our Production account is mirrored from the Production box onto the backup (DEV) box as a (disaster recovery) account. As such we need to be able to restore /activate it at short notice. BUT We do not want any inadvertent updates to that account via these q-pointers. Ideally I would like UniVerse to tell me that I cannot create a q-pointer to a 'restricted' area. I don't think it will do that. I do not want to change the unix permissions because that could interfere with the DR copying processes and would probably need to be undone if we need to switch over. Any ideas would be welcome. Cheers John Rodgers --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Remote (qfile) restrictions - (UV)
Assuming UniVerse version 10, why not add an INSERT OR UPDATE trigger on VOC? --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
