I have been using Revision suffixes and VOC. In other words... >LOGTO SANDBOX
>ED VOC SAMPLE.PROGRAM >PA >RUN BP SAMPLE.PROGRAM.R1 --> R2 save > BASIC BP SAMPLE.PROGRAM.R2 After the program is found to be workable... >LOGTO METAL >ED VOC SAMPLE.PROGRAM >PA >RUN BP SAMPLE.PROGRAM.R1 --> R2 save I have only been using CATALOG to register global SUBs. --Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mark Eastwood Sent: Wednesday, October 20, 2010 11:44 AM To: U2 Users List Subject: Re: [U2] Compiling 102 You might want to consider having two "BP" files - Production and Test (Sandbox?) - e.g. BP and TEST.BP You then use the CATALOG command to control which version is running. Mark -----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 _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
