INFO-VAX Sun, 20 Jul 2008 Volume 2008 : Issue 403 Contents: Curious problem with a dynamic rights identifier Re: F$CVTIME inconsistency after all those years Re: F$CVTIME inconsistency after all those years ---------------------------------------------------------------------- Date: Sun, 20 Jul 2008 16:32:39 GMT From: gerry77@no.spam.mail.com Subject: Curious problem with a dynamic rights identifier Message-ID: <62o6841dtur8pl8laupcsiq8godjrtmh0m@4ax.com> Hello everyone, Let's see... $ MCR AUTHORIZE SHOW/ID/FULL IP_ALLOW Name Value Attributes IP_ALLOW %X80010003 DYNAMIC Holder Attributes SYSTEM DYNAMIC (Notice that both the identifier and the holder have Dynamic attribute) $ MCR AUTHORIZE SHOW SYSTEM (...) Identifier Value Attributes IP_ALLOW %X80010003 DYNAMIC (Here too there is Dynamic attribute, just in case) $ SHOW PROC/RIGHTS (...) Process rights: SYSTEM resource INTERACTIVE REMOTE IP_ALLOW dynamic (Again, here too there is Dynamic attribute) $ SET RIGHTS/DISABLE IP_ALLOW $ (No error message, so I assume everything went fine) $ SHOW PROC/RIGHTS (...) Process rights: SYSTEM resource INTERACTIVE REMOTE IP_ALLOW dynamic (But the identifier is STILL THERE!) What am I doing wrong? I even tried SET RIGHTS/DISA/ATTR=DYN IP_ALLOW to no avail, as the idenfier is always there. Obviously the user SYSTEM has every possible privilege and the relevant process too (but notice that dynamic attribute should allow identifier management to unprivileged holders). I'm stuck. This is a Hobbyist system running OpenVMS Alpha V7.2 with every patch available on ftp.itrc.hp.com and I do not know what else I could try. Is that a known problem of this version? Do you have any suggestions? Note also that the same thing on a VAX with V7.2 (and every patch) does work! Thank you very much, G. (not english native, sorry for any mistake) ------------------------------ Date: Sun, 20 Jul 2008 02:07:47 -0400 From: JF Mezei Subject: Re: F$CVTIME inconsistency after all those years Message-ID: <4882d670$0$1812$c3e8da3@news.astraweb.com> OK, found an instance where F$CVTIME doesn't work :-) $ a = f$time() $ wait some time $ b = f$cvtime("''f$time()'-''a'","DELTA") %DCL-W-IVDTIME, invalid delta time - use DDDD-HH:MM:SS.CC format \20-JUL-2008 01:52:09.48-20-JUL-2008 01:47:44.91\ $ I tried to manually enter $ b = f$cvtime("20-jul-2008:01:48:37.62-20-JUL-2008:01:47:44.91","DELTA") %DCL-W-IVDTIME, invalid delta time - use DDDD-HH:MM:SS.CC format \20-JUL-2008:01:48:37.62-20-JUL-2008:01:47:44.91\ 20-JUL-2008:01:52:09.48-20-JUL-2008:01:47:44.91 (aka: adding a colon between date and time to make it a single "token" didn't help) Reading the HELP, it appears that F$CVTIME is unable to compute a delta time from two absolute times. Or is it ? ------------------------------ Date: Sun, 20 Jul 2008 09:04:11 +0200 From: "Martin Vorlaender" Subject: Re: F$CVTIME inconsistency after all those years Message-ID: JF Mezei wrote: > Reading the HELP, it appears that F$CVTIME is unable to compute a delta > time from two absolute times. Or is it ? Correct. That's why they added F$DELTA_TIME. The first argument to F$CVTIME can be an absolute, a delta, or a combination time, or TODAY, TOMORROW, or YESTERDAY. A combination time is a string of the form "[absolute time][+/-delta time]" (see $ HELP DCL Date_Time). cu, Martin -- One OS to rule them all | Martin Vorlaender | OpenVMS rules! One OS to find them | work: mv@pdv-systeme.de One OS to bring them all | http://vms.pdv-systeme.de/users/martinv/ And in the Darkness bind them.| home: martin.vorlaender@t-online.de ------------------------------ End of INFO-VAX 2008.403 ************************