Lizette - don't make the upgrade more complicated than it needs to be.
By the way, one of the biggest issues we see with upgrades is that the userid performing the upgrade had all the permissions needed when upgrading a test instance but not when upgrading production.
Anyway, looking at the 10.1 readme:
1. Stop all Content Manager OnDemand activity on databases being upgraded to V10.1.0.
Okay, that makes sense. Bring down arssockd and everyone else.
2. Backup the Content Manager OnDemand database or make sure a current backup is available.
This is tougher because so many tables point to other tables which point to other tables.
But I have good news. Unless something really improbable happens you should never have to back out your tables because starting at the 9.5 level of CMOD, V9.5 executables (SARSLOAD and HFS) will work just fine with V10.1 tables. In other words if you bring up 10.1 and immediately hit an issue don't back out your tables, just revert back to V9.5 code. This is tested and thus far I've seen no reports of any issues in this area.
* where does the zFS file get mounted? Anywhere you want as long as every //ARSBIN DD points to it. But the easiest would be to just unmount the old CMOD product HFS and mount the new one.
* are any of the files in the filesystem mounted or just the main file? Just the product HFS.
3. Run the following commands ... (arsdb). If you're running them from your userid you should export the following, this is what I have in my dot-profile.
STEPLIB=$STEPLIB:ARS.ARSV1010.USERLOAD:ARS.ARSV1010.SARSLOAD:DB2.V12R1M0.SDSNEXIT:DB2.V12R1M0.SDSNLOAD:DB2.V12R1M0.SDSNLOD2
DSNAOINI=/etc/ars/V1010/cli.ini
PATH=/bin:/usr/lpp/ars/V10R1M0/bin:/usr/lpp/java/J8.0_64/bin:$HOME:.
export STEPLIB
export DSNAOINI
export PATH
Admittedly perhaps this should be part of the readme.
There is no magic in the drop indexes, create indexes, and maintenance and runstat steps. If you want to do that with your own tools, go right ahead.
______________
* Do we need to run ARSDB prior to starting up CMOD?
Yes! If you try to run Version 9.5 database defs with Version 10 code you get all sorts of ugly errors.
You can run a V10 database with V9.5 code, but not the other way around.
___________
Then change arssockd and other jobs and procs to point to the V10.1 code and bring it all up.
What's the single biggest issue with this upgrade? Exits because of the change to 64 bit arssockd.
I welcome comments from others.
Ed