BP files only have to be type 1/19 if you want to compile / run from them.
Why not store your code in type {whatever else} files, then get the {revised
home-grown} ED
to copy source out to a GLOBALBP type 1 file
to compile, catalog program
then delete the source.
A trigger on the storage file will handle all auditing, SICA etc.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Clifton Oliver
Sent: 16 May 2008 03:52 AM
To: [email protected]
Subject: Re: [U2] locking code question
BP files have to be either type 1 or type 19 (directories). Not having a
file header, you can't have a SICA, can you? Same reason you can't have
indexes or transaction logging on them. At least that's my understanding.
I'd love to find out there is a way to do it.
Regards,
Clif
On May 15, 2008, at 4:14 PM, David Jordan wrote:
> You could look at SQLising the BP file. Having a SICA, you could
> restrict
> read and update to all users and have a BASIC program manager with the
> AUTHORIZATION command, handle check out, check in, compilation, etc.
> This means that programs could only be accessed through the program
> manager and not directly.
>
> This would only work on UniVerse as I believe UniData does not have
> the AUTHORIZATION Command.
> Regards
>
> David Jordan
> -------
> u2-users mailing list
> [email protected]
> To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
No virus found in this incoming message.
Checked by AVG.
Version: 8.0.100 / Virus Database: 269.23.2/1432 - Release Date: 5/14/2008
7:49 AM
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
