All -
I am having problems specifying a storage set when updating application groups in CMOD after upgrading to version 8.5.0.4. Wonder if anyone else has experienced the same and how it was resolved.
Administrative client allows update to "Cache Only - Library Server" and click "OK" on the storage management tab. It reverts to blank when I go back in to review and confirm the update took place. Same happens when trying to update it to a storage set other than "Cache Only - Library Server."
Administrative PC client software and CMOD application are at version 8.5.0.4. DB2 9.7. TSM 5.5 level 3.0
Running CMOD MP on Linux x86
Update: I tried the same against production (DB2 9.7 -- TSM 5.5 level 3.0 -- administrative client 8.5.0.4) and got the same problem. Wondering if CMOD defaults to cache only now.
Found answer (and it's not ideal):
Configurations created in a prior version (in my case 8.4.1.3) cannot be exported to an instance of CMOD running at 8.5.0.4
This means I have to create configurations in each environment until they are all in synch (or the same version of CMOD)
>:( :( ???
Hello Brian,
Well not really... I've had the same problem on a old ondemand in Solaris, and there where some strange values in the databases... and by correcting them, the problem was solved.
Now it's quite a long time... and I don't remember the details...
Check the content of the arsnode/arsset table, arsag (sid field), and check that everything seems correctly setup...
Hope that helps a little bit...
Sincerely yours,
Alessandro
Can you use arsxml to export the data? (I can't remember if 8.4.1.3 has arsxml, and if it doesn't, can you use the version from 8.5.0.5 and use the -h <hostname> parameter to pull the data from the old server? I'm assuming here that there's an 'old' and a 'new' server, and that this isn't an in-place upgrade.
-JD.
Hello Justin,
For info, CMOD 8.4.X has already arsxml.
And unfortunately an arsxml from 8.5.X cannot access a server 8.4.X... I've tried and it doesn't work :-(
Sincerely yours,
Alessandro
All --
I can accept and deal with the issues between versions and won't have to deal with this long.
However, I opened a PMR with IBM today because creating a new application in 8.5.0.4 does the same thing. Can't load objects to an application group without the storage set identified. IBM Responder acknowledged this may have been a bug in a previous fixpack version, but I'm only one behind the latest 8.5.0.5. Waiting for feedback and will update this string once I get it.
Hi Brian...
8.5.0.6 was released on September 21st. So make sure you get the latest and greatest!
I've also seen a similar bug, I'll make sure that gets a PMR opened on it as well, in case it's related.
-JD.
CMOD 8.5.0.6 does have a fix related to this:
PM68005 - AG STORAGE MANAGEMENT changed after update in GENERAL tab