Re: [U2] Universe: IF statements in parargraphs don't work anymore
Jeff is right in theory though you would need to be careful whenever you run an upgrade account. If you really want to secure the VOC you would also need to lock out all other forms of access such as UniObjects: you can easily create a little VBScript to connect through with this and read/write/delete directly. And if anyone can ever get to shell, you have the UVread, UVwrite and UVdelete executables. And if you make the account a SQL schema, the VOC is not a SQL table so you can't use grant permissions. Brian -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff Porterfield Sent: 03 April 2012 23:04 To: u2-users@listserver.u2ug.org Subject: Re: [U2] Universe: IF statements in parargraphs don't work anymore Louie Bergsagel louiebergsagel at gmail.com writes: No, that works fine. You only need a label if you want to skip some lines. Turns out somebody had deleted the VOC equal sign record =. Which brings up a good security question, how do you prevent someone from deleting things? Put shell around ED and DELETE? It would be a bummer to have to make VOC read-only. On Thu, Jun 5, 2008 at 12:53 PM, Ron Hutchings ron_hutchings at hotmail.com wrote: On Line 6 don't you need to go to a label to execute a command instead of trying to directly execute it? --- u2-users mailing list u2-users at listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ Check into the Security Subroutines section of the Administrators Guide. 1) Make a temporary copy of ED in your VOC, call it ED.BAK. This is your backdoor in case of problems. I would also have a separate account with a pointer to the main account's VOC. This account you can lock with a simple paragraph that says if @LOGNAME isn't you, LOGOUT. 2) Write a security subroutine that conforms to the specs given in Chapter 8 of the Administrators guide. Catalog it in the global catalog. 2) Copy the verbs you want to secure, including ED, into your VOCLIB. 3) Change the verbs in the VOC to Remote pointers to your VOCLIB, and add the name of your security routine to line 4. (I might suggest testing the R pointers before applying the security routine.) 4) Once you're sure your security is working as planned, and that you can use the ED program you've secured, then remove your back door ED.BAK. Remember, you can still fix the VOC from your other account if you manage to lock yourself out. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Universe: IF statements in parargraphs don't work anymore
One way around the UPDATE.ACCOUNT problem that Brian mentions is to invent your own flavour (Your own sub-file under the Pick-style multi-level file under UV/NEWACC). Massage that once per UV upgrade, then apply it to all VOCs that need protecting or customizing. Personally, I wish it was much easier more practical to make a VOCs read-only. Same for DICTs, where next.available records and EVAL typically make read-only difficult. cds On 4/4/2012 5:21 AM, Brian Leach wrote: Jeff is right in theory though you would need to be careful whenever you run an upgrade account. If you really want to secure the VOC you would also need to lock out all other forms of access such as UniObjects: you can easily create a little VBScript to connect through with this and read/write/delete directly. And if anyone can ever get to shell, you have the UVread, UVwrite and UVdelete executables. And if you make the account a SQL schema, the VOC is not a SQL table so you can't use grant permissions. Brian -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff Porterfield Sent: 03 April 2012 23:04 To: u2-users@listserver.u2ug.org Subject: Re: [U2] Universe: IF statements in parargraphs don't work anymore Louie Bergsagellouiebergsagelat gmail.com writes: No, that works fine. You only need a label if you want to skip some lines. Turns out somebody had deleted the VOC equal sign record =. Which brings up a good security question, how do you prevent someone from deleting things? Put shell around ED and DELETE? It would be a bummer to have to make VOC read-only. On Thu, Jun 5, 2008 at 12:53 PM, Ron Hutchingsron_hutchingsat hotmail.com wrote: On Line 6 don't you need to go to a label to execute a command instead of trying to directly execute it? Check into the Security Subroutines section of the Administrators Guide. 1) Make a temporary copy of ED in your VOC, call it ED.BAK. This is your backdoor in case of problems. I would also have a separate account with a pointer to the main account's VOC. This account you can lock with a simple paragraph that says if @LOGNAME isn't you, LOGOUT. 2) Write a security subroutine that conforms to the specs given in Chapter 8 of the Administrators guide. Catalog it in the global catalog. 2) Copy the verbs you want to secure, including ED, into your VOCLIB. 3) Change the verbs in the VOC to Remote pointers to your VOCLIB, and add the name of your security routine to line 4. (I might suggest testing the R pointers before applying the security routine.) 4) Once you're sure your security is working as planned, and that you can use the ED program you've secured, then remove your back door ED.BAK. Remember, you can still fix the VOC from your other account if you manage to lock yourself out. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Universe: IF statements in parargraphs don't work anymore
Brian: Theoretically speaking, of course, couldn't you give an administrator write privileges and everyone else read and execute privileges to the VOC. If one assumes the application isn't writing anything to the VOC, which I know is unlikely, this is doable. But, you know, the U2 group hasn't done much to secure the dbms. You need to be a Windows user, the user (if it's not default) has to be loaded into the registry via UniAdmin, there's no reasonable way to restrict access within U2 at the file level. I remember the old Pick that had group permissions and user IDs within the dbms. That seemed to be the way. Anyway, implementing file security is difficult. :-( Bill - Original Message - *From:* br...@brianleach.co.uk *To:* 'U2 Users List' u2-users@listserver.u2ug.org *Date:* 4/4/2012 3:21 AM *Subject:* Re: [U2] Universe: IF statements in parargraphs don't work anymore Jeff is right in theory though you would need to be careful whenever you run an upgrade account. If you really want to secure the VOC you would also need to lock out all other forms of access such as UniObjects: you can easily create a little VBScript to connect through with this and read/write/delete directly. And if anyone can ever get to shell, you have the UVread, UVwrite and UVdelete executables. And if you make the account a SQL schema, the VOC is not a SQL table so you can't use grant permissions. Brian -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff Porterfield Sent: 03 April 2012 23:04 To: u2-users@listserver.u2ug.org Subject: Re: [U2] Universe: IF statements in parargraphs don't work anymore Louie Bergsagellouiebergsagelat gmail.com writes: No, that works fine. You only need a label if you want to skip some lines. Turns out somebody had deleted the VOC equal sign record =. Which brings up a good security question, how do you prevent someone from deleting things? Put shell around ED and DELETE? It would be a bummer to have to make VOC read-only. On Thu, Jun 5, 2008 at 12:53 PM, Ron Hutchingsron_hutchingsat hotmail.com wrote: On Line 6 don't you need to go to a label to execute a command instead of trying to directly execute it? --- u2-users mailing list u2-usersat listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ Check into the Security Subroutines section of the Administrators Guide. 1) Make a temporary copy of ED in your VOC, call it ED.BAK. This is your backdoor in case of problems. I would also have a separate account with a pointer to the main account's VOC. This account you can lock with a simple paragraph that says if @LOGNAME isn't you, LOGOUT. 2) Write a security subroutine that conforms to the specs given in Chapter 8 of the Administrators guide. Catalog it in the global catalog. 2) Copy the verbs you want to secure, including ED, into your VOCLIB. 3) Change the verbs in the VOC to Remote pointers to your VOCLIB, and add the name of your security routine to line 4. (I might suggest testing the R pointers before applying the security routine.) 4) Once you're sure your security is working as planned, and that you can use the ED program you've secured, then remove your back door ED.BAK. Remember, you can still fix the VOC from your other account if you manage to lock yourself out. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Universe: IF statements in parargraphs don't work anymore
I just noticed the OP posted his original message nearly 4 years ago, so I don't know if he's still listening, but thought I'd reply anyway for the benefit of anyone else who might have interest. I put a wrappers around ED and DELETE many, many years ago, and it hasn't been a problem. My solution to the custom version getting wiped out is to keep all of our customized VOC entries in a file named VOC.MOD. The only time our VOCs get updated is during a hardware upgrade, and I copy the contents of VOC.MOD back into VOC as part of the process. -John -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff Porterfield Sent: Tuesday, April 03, 2012 3:04 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Universe: IF statements in parargraphs don't work anymore Louie Bergsagel louiebergsagel at gmail.com writes: No, that works fine. You only need a label if you want to skip some lines. Turns out somebody had deleted the VOC equal sign record =. Which brings up a good security question, how do you prevent someone from deleting things? Put shell around ED and DELETE? It would be a bummer to have to make VOC read-only. On Thu, Jun 5, 2008 at 12:53 PM, Ron Hutchings ron_hutchings at hotmail.com wrote: On Line 6 don't you need to go to a label to execute a command instead of trying to directly execute it? --- u2-users mailing list u2-users at listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ Check into the Security Subroutines section of the Administrators Guide. 1) Make a temporary copy of ED in your VOC, call it ED.BAK. This is your backdoor in case of problems. I would also have a separate account with a pointer to the main account's VOC. This account you can lock with a simple paragraph that says if @LOGNAME isn't you, LOGOUT. 2) Write a security subroutine that conforms to the specs given in Chapter 8 of the Administrators guide. Catalog it in the global catalog. 2) Copy the verbs you want to secure, including ED, into your VOCLIB. 3) Change the verbs in the VOC to Remote pointers to your VOCLIB, and add the name of your security routine to line 4. (I might suggest testing the R pointers before applying the security routine.) 4) Once you're sure your security is working as planned, and that you can use the ED program you've secured, then remove your back door ED.BAK. Remember, you can still fix the VOC from your other account if you manage to lock yourself out. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Universe: IF statements in parargraphs don't work anymore
Louie Bergsagel louiebergsagel at gmail.com writes: No, that works fine. You only need a label if you want to skip some lines. Turns out somebody had deleted the VOC equal sign record =. Which brings up a good security question, how do you prevent someone from deleting things? Put shell around ED and DELETE? It would be a bummer to have to make VOC read-only. On Thu, Jun 5, 2008 at 12:53 PM, Ron Hutchings ron_hutchings at hotmail.com wrote: On Line 6 don't you need to go to a label to execute a command instead of trying to directly execute it? --- u2-users mailing list u2-users at listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ Check into the Security Subroutines section of the Administrators Guide. 1) Make a temporary copy of ED in your VOC, call it ED.BAK. This is your backdoor in case of problems. I would also have a separate account with a pointer to the main account's VOC. This account you can lock with a simple paragraph that says if @LOGNAME isn't you, LOGOUT. 2) Write a security subroutine that conforms to the specs given in Chapter 8 of the Administrators guide. Catalog it in the global catalog. 2) Copy the verbs you want to secure, including ED, into your VOCLIB. 3) Change the verbs in the VOC to Remote pointers to your VOCLIB, and add the name of your security routine to line 4. (I might suggest testing the R pointers before applying the security routine.) 4) Once you're sure your security is working as planned, and that you can use the ED program you've secured, then remove your back door ED.BAK. Remember, you can still fix the VOC from your other account if you manage to lock yourself out. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] Universe: IF statements in parargraphs don't work anymore
IF statements don't work in my paragraphs any more. They worked yesterday. No upgrades or changes that I know of. LOGIN.TEST Your 'VOC' has been modified to use long file names. Illegal IF statement. Illegal IF statement. CT VOC LOGIN.TEST LOGIN.TEST 0001 PA 0002 PTERM CASE NOINVERT 0003 LONGNAMES ON 0004 TERM ,8 0005 IF @TTY = phantom THEN GO END.PARAGRAPH 0006 IF @ACCOUNT = louie THEN LOUIEB 0007 END.PARAGRAPH: 0008 * CT VOC IF IF 0001 K 0002 215 0003 * UniVerse release.: 10.2.7 UniVerse syntax..: PICK AIX 5.2 Louie Bergsagel North Coast Electric --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Universe: IF statements in parargraphs don't work anymore
Louie - I noticed that you have included a LONGNAMES ON statement in this login test. LONGNAMES ON should only be run once in each account, not repeatedly. I don't know if that is your problem, but it might be. Ken At 09:59 AM 6/5/2008, you wrote: IF statements don't work in my paragraphs any more. They worked yesterday. No upgrades or changes that I know of. LOGIN.TEST Your 'VOC' has been modified to use long file names. Illegal IF statement. Illegal IF statement. CT VOC LOGIN.TEST LOGIN.TEST 0001 PA 0002 PTERM CASE NOINVERT 0003 LONGNAMES ON 0004 TERM ,8 0005 IF @TTY = phantom THEN GO END.PARAGRAPH 0006 IF @ACCOUNT = louie THEN LOUIEB 0007 END.PARAGRAPH: 0008 * CT VOC IF IF 0001 K 0002 215 0003 * UniVerse release.: 10.2.7 UniVerse syntax..: PICK AIX 5.2 Louie Bergsagel North Coast Electric --- 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] Universe: IF statements in parargraphs don't work anymore
I commented out that LOGNAMES line, logged out, and in, and ran LOGIN.TEST again, and it still gives me an Illegal IF statement. error message. I'm also finding dictionary I-TYPES not working today that worked yesterday: LIST REPORTS START.DATE UD.TODAY WITH START.DATE = UD.TODAY Bad data = for conversion D4/. Unconverted data used for selection. 0 records listed. .x7 07 LIST DICT REPORTS START.DATEUD.TODAY DICT REPORTS12:45:05pm 05 Jun 2008 Page1 Field. Type Field Conversion.. Column. Output Depth Name.. Field. Definition... Code Heading Format Assoc.. Number START.DATE D5 D4/ START.DATE 10RS UD.TODAY I @DATE D4/ UD.TODAY10RS 2 records listed. ED REPORTS SELECTed record name = 6765776. 62 lines long. : 5 0005: 14753 : Q --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Universe: IF statements in parargraphs don't work anymore
I found the problem. Somebody had deleted the = VOC record. ED = Unable to open =, not a file in VOC. I restored it from EQ. -- Louie CT VOC =EQ = 0001 K 0002 4 EQ 0001 K 0002 4 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Universe: IF statements in parargraphs don't work anymore
On Line 6 don't you need to go to a label to execute a command instead of trying to directly execute it? Date: Thu, 5 Jun 2008 09:59:00 -0700 From: [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Subject: [U2] Universe: IF statements in parargraphs don't work anymore IF statements don't work in my paragraphs any more. They worked yesterday. No upgrades or changes that I know of. LOGIN.TEST Your 'VOC' has been modified to use long file names. Illegal IF statement. Illegal IF statement. CT VOC LOGIN.TEST LOGIN.TEST 0001 PA 0002 PTERM CASE NOINVERT 0003 LONGNAMES ON 0004 TERM ,8 0005 IF @TTY = phantom THEN GO END.PARAGRAPH 0006 IF @ACCOUNT = louie THEN LOUIEB 0007 END.PARAGRAPH: 0008 * CT VOC IF IF 0001 K 0002 215 0003 * UniVerse release.: 10.2.7 UniVerse syntax..: PICK AIX 5.2 Louie Bergsagel North Coast Electric --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ _ Its easy to add contacts from Facebook and other social sites through Windows Live Messenger. Learn how. https://www.invite2messenger.net/im/?source=TXT_EML_WLH_LearnHow --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Universe: IF statements in parargraphs don't work anymore
We had something similar happen once - check if the VOC entery for TERM has been changed. -Dianne At 09:59 AM 6/5/2008, you wrote: IF statements don't work in my paragraphs any more. They worked yesterday. No upgrades or changes that I know of. LOGIN.TEST Your 'VOC' has been modified to use long file names. Illegal IF statement. Illegal IF statement. CT VOC LOGIN.TEST LOGIN.TEST 0001 PA 0002 PTERM CASE NOINVERT 0003 LONGNAMES ON 0004 TERM ,8 0005 IF @TTY = phantom THEN GO END.PARAGRAPH 0006 IF @ACCOUNT = louie THEN LOUIEB 0007 END.PARAGRAPH: 0008 * CT VOC IF IF 0001 K 0002 215 0003 * UniVerse release.: 10.2.7 UniVerse syntax..: PICK AIX 5.2 Louie Bergsagel North Coast Electric --- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Universe: IF statements in parargraphs don't work anymore
Thanks! Good to know. Nancy Fisher Peninsula Truck Lines, Inc Auburn, Washington 253/929-2040 Visit our Website www.peninsulatruck.com [EMAIL PROTECTED] - Original Message - From: Louie Bergsagel [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Thursday, June 05, 2008 12:56 PM Subject: Re: [U2] Universe: IF statements in parargraphs don't work anymore I found the problem. Somebody had deleted the = VOC record. ED = Unable to open =, not a file in VOC. I restored it from EQ. -- Louie CT VOC =EQ = 0001 K 0002 4 EQ 0001 K 0002 4 --- 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] Universe: IF statements in parargraphs don't work anymore
No, that works fine. You only need a label if you want to skip some lines. Turns out somebody had deleted the VOC equal sign record =. Which brings up a good security question, how do you prevent someone from deleting things? Put shell around ED and DELETE? It would be a bummer to have to make VOC read-only. On Thu, Jun 5, 2008 at 12:53 PM, Ron Hutchings [EMAIL PROTECTED] wrote: On Line 6 don't you need to go to a label to execute a command instead of trying to directly execute it? --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Universe: IF statements in parargraphs don't work anymore
Has anything happened that may have wreaked havoc with your Pick flavor? Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Louie Bergsagel Sent: Thursday, June 05, 2008 2:49 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Universe: IF statements in parargraphs don't work anymore I commented out that LOGNAMES line, logged out, and in, and ran LOGIN.TEST again, and it still gives me an Illegal IF statement. error message. I'm also finding dictionary I-TYPES not working today that worked yesterday: LIST REPORTS START.DATE UD.TODAY WITH START.DATE = UD.TODAY Bad data = for conversion D4/. Unconverted data used for selection. 0 records listed. .x7 07 LIST DICT REPORTS START.DATEUD.TODAY DICT REPORTS12:45:05pm 05 Jun 2008 Page1 Field. Type Field Conversion.. Column. Output Depth Name.. Field. Definition... Code Heading Format Assoc.. Number START.DATE D5 D4/ START.DATE 10R S UD.TODAY I @DATE D4/ UD.TODAY10R S 2 records listed. ED REPORTS SELECTed record name = 6765776. 62 lines long. : 5 0005: 14753 : Q --- 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/
