For sequence to install RAA pre-reqs I think the only recommendation is DB2 before WAS. You could do:
1) REXX 3.2 (must be REXX 3.2 and 32 bit)
2) DB2 9.5+
3) WAS 6.1 +
Pinned topic The sequence to install: DB2, WAS, REXX, RAA
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-13T21:14:06Z at 2013-02-13T21:14:06Z by jcdelmo
Re: The sequence to install: DB2, WAS, REXX, RAA2012-08-27T16:35:55ZThis is the accepted answer. This is the accepted answer.DB2 and WAS with fix packs.
DB2 and WAS on same bit mode, 32 or 64, with 64 preferred.
There are no dependencies between OOrexx, WAS and DB2. As far as I know install sequence does not matter.
jcdelmo 0600012HN8347 Posts
Re: The sequence to install: DB2, WAS, REXX, RAA2013-02-13T21:14:06ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
1) Have a copy of the product data sets under a separate HLQ
2) Have a copy of the product HFS directory under a different path. By "product HFS directory", I mean a path in the USS. It doesn't have to be a specific one. When the product is installed, one might use /usr/lpp/dmh. However, after it's SMP/E installed someplace, you can copy that directory to /usr/lpp/dmh600sys1, for example. Similarly, you might copy the DMH.V6R0M0.** data sets to DMH.V6R0M0.SYS1.**. When you execute DMH.V6R0M0.SYS1.SDMHREXX(DMHINSTL) option 0, you'd indicate that the HFS base directory to be /usr/lpp/dmh600sys1.
3) In DMHINSTL, define separate DB2 settings for things like schema names, database names, etc. To separate the database on z/OS, you'd just specify unique settings in DMHINSTL option 0 for the storage group, database name, DB2 table space prefix, high-level qualifier for the tables, and DB2 plan prefix. Then, when you save the settings and use option 1 to create the database objects, the ones that need to be separate will be.
4) Create the separate DB2 databases (though it can be in the same DB2 subsystem)
5) Use a separate WAS server
6) Optionally, use a separate HTTP server for the remote request server. I say "optionally" because you can use the same HTTP server if you use a different web path. For example, dmhsys1-cgi and dmhsys2-cgi, each mapped to a different bin directory. Yes, it's easier to just use the same HTTP server. Just remember that, if you're going to change the web path from dmh-cgi to dmhsys1-cgi, you need to specify dmhsys1-cgi in the DMHINSTL option 0 settings as well.
NOTE-1: DMHINSTL does help to separate things. Ideally, we'd like to use the USS directory and HLQ so you have 1 set of data sets and files, but we're not there yet.
NOTE-2: The separate WAS will give separate ear files, but the real reason is because there can be only one wsaaConfig custom JVM property to tell WAS where to find Common.cfg file, so each WAS will its own setting for that.