General SAM Version Cutting

This general version cutting technique can be used for many of the SAM products. However, for some products you may use the same instructions below for part of the cutting, but they may have their own instructions prior to and after these commands. Or, they may have their own specific instructions altogether.

Products with their Own Instructions

Cutting sam_doc, sam_talks & sam_data_browsing: use the follow techniques for cutting sam_doc. They are very similar to those below, but have enough variations that a separate document was written.
Cutting sam_db_server & sam_db_server_idl: these two products are cut in concert with each other and both described in the sam set of instructions.

Steps for Cutting a Version - Up to CVS Tagging

The product version below should be replaced by the product name and version number you are cutting, e.g. sam_db v2_7.

logon to d0ora3
Make sure all your source has been checked into CVS.
cd <your_devel_dir> ; cvs ci -m "make sure all is checked in"
MAKE SURE YOUR ID IS IN THE PRODUCTS GROUP, AND YOUR UMASK IS 002.
This is very important - if you do not do this, then other SAM Team members will have trouble when trying to cut the next version. To check your group and umask use the following commands.
id ; umask
cd /fnal/ups/prd/product
cvs checkout product
If cutting sam_doc, you will want to cvs co -P sam_doc, to avoid getting all the empty directories that are still in the CVS archives from the earlier inclusion of sam_talks and sam_data_browsing. But, see the SAM Documentation Release Procedures for the complete instructions for cutting sam_doc, sam_talks, and sam_data_browsing.
Your directory will now be product/product
mv product version
Your directory will now be product/version
cd /fnal/ups/prd/product/version
cvs tag -F version

Review these remaining steps

To cut sam_db_admin to development, no need to cut sam_db into dev

See the sam_admin_db make command

Currently, for sam_db and sam_db_admin, you can do your make now, from d0ora3, instead of doing it on dbora2. You will point to the d0ora1 database.

See the sam_db_make_int command

See the sam_admin_db make command

then on d0ora1

logon as products
cd /fnal/ups/prd
upd install product version -f SunOS+5
declare the integration version
for sam_db ups declare -r /fnal/ups/prd/product/version/SunOS+5 -f flavor -m sam_db.table -M /fnal/ups/prd/sam_db/version/flavor/ups product version -q int -t
for sam_db_admin ups declare -r /fnal/ups/prd/product/version/SunOS+5 -f flavor -M /fnal/ups/prd/sam_db_admin/versionSunOS+5/ups -m sam_db_admin.table product version -q int -t
logon as a test user
setup -t product -q int
test the product
To run the production make for sam_db or sam_db_admin:
- See the sam_db_make_prd command
- See the sam_db_admin_make_prd command
finish with version cutting by defining ups products
for sam_db ups declare -r /fnal/ups/prd/product/version/flavor -f flavor -m sam_db.table -M /fnal/ups/prd/sam_db/version/flavor/ups product version -q prd -c
for sam_db_admin ups declare -r /fnal/ups/prd/product/version/flavor -f flavor -m sam_db_admin.table -M /fnal/ups/prd/sam_db/version/ups product version -q prd -c
review ups (ups list -val product)
setup product
check and test the product.
back to d0ora1 after the make runs successfully, and to continue with sam_doc
- cd /fnal/ups/prd/product. Make sure the current link is pointing to the newest version. If not:
  - rm current
  - ln -s version current
  - logon to d0ora3 as products, d0ora1 does not support a modproduct command. You cannot - su to products on d0ora3 either. Start a new session and logon d0ora3 as products.
  - Make the upd version current: upd modproduct product version -f flavor-c
  - upd list -val product, to insure the correct product is current
For sam_db_admin, you must stop and start the forms deamon for the web on both d0ora3 and d0ora1, else the deamon is still pointing at the old version. Ports 9002 on d0ora3 and d0ora1 point to dev and prd respectively. Port 9003 on d0ora1 is int.
- ps -ef |grep f60
- logon as the person who started the f60 jobs
- setup oracle_2000
- setup orasid_remote
- f60ctl stop port=9002 (or whatever port# shows in the ps -ef)
- cd /etc/init.d
- more OraFormsCtl
- /oracle/ora1/oracle_2000/v6_i/forms60_server start

Maintained by: sam-design@fnal.gov
Last modified: Fri Apr 15 14:17:21 CDT 2005