Topics

1

MP Server / Re: CMOD upgardes : v8.4.1 to v10.1 on Windows

« on: September 15, 2017, 02:14:30 AM »

My suggestion would be the following (in the same line as Justin:

For the CMOD Server side:
- Install the new server with all the software
- Configure everything on the new server, so you could just start from scratch, in order to test that everything works as expected
- Export the DB2 V9.1 (with the command "db2move export")
- Export the db structure (with a db2look)
- Create a DB with the same codepage as the old one
- Play the new db structure created on with the db2look command (you can change some tablespace/add new ones/etc... but don't change the table structure at all or the indexes)
- Import the export from previous step with a "db2move load"
- Do the CMOD upgrade from V8.4.X to V9.5.X

For the TSM Server side:
- Install the new server with all the software
- Configure everything on the new server, so you could just start from scratch, in order to test that everything works as expected
- Upgrade to the latest level of TSM V5.5 -> V5.5.7 (this is a MUST, you cannot do the next step without being in V5.5 latest FP).
- do a server to server export procedure from V5.5.7 to V7.1.1.1+

And that should be it... there is really nothing special, I've done it countless of time, even going from DB2 V8.1 to V10.5 for a customer.

As Justin said, if the customer keeps current on the patch level, that would be much simpler :-)

Sorry for bringing up an old thread with a new post.

Thanks Alessandro for the steps, but I have some questions. I'm testing this approach right now.

Old machine:
Win2003, CMOD v8.4.0, DB2 v8.1.7

New machine:
Win2012R2, CMOD v10.1, DB2 v11.1.2

I installed latest DB2, and CMOD in the new server. I also exported both structure, and data from the old database.

Question:
1. Do I configure the new CMOD by creating a new instance? Creating a new instance will create a database.
2. If I don't create an instance in new CMOD but I create a new database with the same codepage/territory as the old database, how do I link a new CMOD instance with an existing database?

I also tried the steps below, and I couldn't start Library server with logon failure error:
1. Created new instance (which will create a database).
2. Dropped the database.
3. Created a new database with the same codepage/territory as the old database.
4. Created database structure using the result of db2look.
5. Loaded (db2move load) the data exported from old database.
6. Logon failure when starting CMOD Library server.
7. Changed CMOD instance credentials to follow the old CMOD's credentials but still login failure.


Thank you very much in advance!

2

Report Indexing / XML Indexing - How to start?

« on: September 13, 2017, 08:10:13 PM »

Greetings fellow CMOD gurus,

We received a requirement to archive XML files, that consist of information of their customers, from a potential customer. However, we don't know where to start. Knowledge Center isn't exactly very helpful.

The theory that we understand is that these XML files would need to be converted to another XML file that follows CMOD's structure (odxmlidx.xsd). The converter is either XSLT or XQuery. Let's say we want to use XSLT, do we build it based on odxmlidx.xsd?

I understand that we can use Generic indexer with an additional index file. Assuming the customer isn't willing to generate the index file from their end, we would probably need to build an application that reads the XML contents to generate the index file. That would be the last option as we would like to explore what CMOD's XML indexer can do first.

Also, how do we load the XMLs automatically using XML indexer? Just move the transformed XML file into the data load directory? What is the extension/format of the input file? XML or ARD? Or rename the XML file to .OUT, and ARD is just the trigger?

Really really appreciate the help. Thank you in advance.