Dean:

This is interesting to know!

2 Dev (0)-> BPTEST OPEN '', 'ARTMASTER' TO ARTMASTER ELSE STOP 201, 'ARTMASTER' ; CRT FILEINFO(ARTMASTER, 25) ; CRT FILEINFO(ARTMASTER, 26) ; END

Compiling Unibasic: SAVEDLISTS\BpTest_487376561 in mode 'p'.
compilation finished
U2.MASTER.TRIGGER.U
U2.MASTER.TRIGGER.D

This isn't in my most recent UD BASIC Reference manual (although 27 & 28 are). Thanks,

Bill

------------------------------------------------------------------------
----- Original Message -----
*From:* <dean.armbrus...@ferguson.com
*To:* jbut...@hampshire.edu, u2-users@listserver.u2ug.org
*Date:* 10/10/2011 1:22 PM
*Subject:* Re: [U2] Finding Triggers on files
FILEINFO

25 - Returns update trigger
26 - Returns delete trigger


Dean Armbruster
Information Technology, System Analyst
Ferguson Enterprises, Inc.
12500 Jefferson Avenue * Newport News * VA * 23602-4314
T: +1 (757) 989 2839 * F: +1 (757) 989 2801
www.ferguson.com


-----Original Message-----
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeffrey
Butera
Sent: Monday, October 10, 2011 11:40 AM
To: U2 Users List
Subject: [U2] Finding Triggers on files


   Unidata 7.2.9 on RedHat

Is there a programmatic way to determine if a file has a trigger on it?

I've looked at FILEINFO and it doesn't indicate that any parameter would

return trigger information.  I know I can do something like:

EXECUTE "LIST.TRIGGER MY_FILE" CAPTURING X.RESULT

and parse X.RESULT, but was curious if there's a better way.

I've occasionally been bitten by converting a file from static to
dynamic hashing, losing an update trigger in the process so I want to
write some code to check these and let me know if something's awry.


_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to