In response to #2 - We had a somewhat similar setup for a while because
we were warehousing goods for a customer.  Their data was unique to
their inventory, so they needed their own separate account, but they
needed to use the same applications as us with a few minor exceptions.
Our live account was FABRIC.PROD and our source code was in BP, so our
BP VOC looked like this:

F
BP
D_BP

and theirs looked like this:

Q
FABRIC.PROD
BP

The handful of exception programs were stored in a type 19 file in their
account with a VOC entry like this:

F
BP.PDTN
D_BP.PDTN

The exception programs were named the same as ours, but by locally
cataloging the BP.PDTN copy while logged into their account, their VOC
was re-pointed to their own copy.  The non-exception VOC entries pointed
to the BPs in our account.  This setup allowed us to maintain only 1 set
of code for the most part, so bug fixes and enhancements didn't have to
be ported over to an add'l account.

As Mark suggested, you could utilize the same setup for testing by
having an add'l local BP file in your SANDBOX account.  Catalog the
local version for testing, then copy it over to the SOFTWARE account
file and catalog that copy when it's ready to go live.  As a side
benefit, if you always delete the local testing copy when you copy it
back to the live file, you'll have a quick way to list every program
currently being worked on.

-John

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Bill Brutzman
Sent: Wednesday, October 20, 2010 8:28 AM
To: U2 Users List
Subject: [U2] Compiling 102

1. It works.  Thanks to Kat, Tom, Vance, and Drew.
2. I am wondering if others keep their source code in an UV account as
such.
3. Prior to this thread, I had two accounts
        /u2/METAL
        /u2/SANDBOX

4. The source code was not in a UV account in
        /u2/SOFTWARE

5. An advantage that I seem to have now is that I can compile code when
logged in to either METAL or SANDBOX and the compiled code works in both
METAL and SANDBOX.  In other words, I do not have to compile the same
source code for each account.  It is not clear to me how VOC and
Q-Pointers are setup to handle this scheme.

6. Comments would be welcome.

--Bill
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to