Upgrading Program

Following procedure could be used if you are upgrading the control from Rel 10 to latest. These instruction are taken during the upgrade at BRAUN company, they were are Rel10 and we update to the latest. If you are jumping the upgrade from older than Rel10 to latest, please ask and refer to other manual and use this as a refrence.

1. Check the disk space to see if they have enough to do update.
2. Organize the time and date with the client to upgrade. Don't pick friday or day before holiday because if something goes wrong you can still fix it on next day.
3. Tell the customer that nobody should be using CONTROL when we do the update.
4. When you are ready to copy the program to customer server, talk to the customer if everything are compiled and if they have done any recent changes.

5. Backup Steps

   1. Backup the company directory with permission,owner and date intact ( #cp -r --preserve COMPANY COMPANY.bak)

   2. Backup any othe branch folder or anything seems to be crucial.

6. Copying program accross using tar command but before that create a unique folder at customer site (eg : cc.10 under /u)

   1. # tar cvz u/ccdev/std/{binl,binx11,utbinl,utbinx11} | ssh ccc@braun "cd /u/cc.10/; tar xvz"
   2. On our server compile any custom work that was done for them and copy accross
   3. # cd /u/cc/BRAUNSWAGER/mods/work
   4. #make (compile)
   5. #gol ( In linux mode)
   6. #cd /u/cc/BRAUNSWAGER/mods/ ; tar cvj bin{l,x11} | ssh ccc@braun "cd mods ; tar xjv" ( mods is new folder you have to create before sending thses mods)

7. Get ready to update the program now

   1. Comment out all cronjobs of root and ccc.
   2. Kill all the processes of control and any other things that will effect upgrade. ( eg: ilstr,salstr etc)
   3. Under std folder there will folder just like you copied over. Go inside the each one of them. You will see program like aleat and so on, if there is previous version there will be backup like aleat.bak or very oldest version aleat.old. You can also check the date by using #ll command. You need to used mv command to change .bak to .old and new to .bak. ( Eg : aleat.bak to aleat.old and aleat to aleat.bak). After that move all .bak command to different folder as backup, in anycase we need to revert back next day or so.
   4. After everything is moved, it's time to move our newest program from cc.10 directory to specific folder inside std.
   5. Check the permission of programs under those folder ( binl, binx11,utbinl, utbinx11). It should be atleast 666.
      1. # chmod 666 *
8. After program is update you have to check the program to see if it is actually the updated one.
   1. #what cd /u/cc/std/utbinl/trurep ( make sure the date are updated)
9. Any other modification update should be done this way.
   1. On our SAM, open #less /u/ccdev/std/upda10/upgra10 for your reference to update on client server
   2. Run the update just like the instruction on upgra10 script
   3. scp /u/ccdev/standard/pro* /u/ccdev/stanadard/op* ccc@braun:/u/cc/BRAUN
   4. chmod 666 *.idx
10. Remove the .bak folder in DEMO company if any ( for f in * ; do mv $f $f.bak; done )
11. Renable cronjobs on root and ccc

12. Test

    1. Open vnc or text mode session to see if new program work. Open several programs to see if all work. Try different logins.
    2. Notify customer after job done and let them try it as well.