Upgrading from Version 11.0 to Version 12.0 Questions
Article ID: 190205
Updated On:
Products
Mainframe Application Tuner
Issue/Introduction
We currently have a quadplex where CA-MF APTUNER is running on 3 of the 4. These complexes share a SYSRES set so as one IPLs on the new SYSRES set it will get the 12.0 version of the product.
Environment - Of the systems in the quadplex - only 3 of them are running the Started Task.
Each of these 3 systems is using it's own system specific GIF file.
Questions....
1) Can LPAR1 be upgraded to 12.0 without impacting LPAR2 & LPAR3?
2) Since there are separate GIF file on each LPAR used by each Started Task - this would imply that they LPARS are not communicating with each other for this product. Is that correct?
3) It is documented in the installation guide that a new GIF must be allocated when installing a new version. If for any reason, V12.0 would have to be backed off to V11.0 - can the old GIF file be reinstated?
Environment - Of the systems in the quadplex - only 3 of them are running the Started Task.
Each of these 3 systems is using it's own system specific GIF file.
Questions....
1) Can LPAR1 be upgraded to 12.0 without impacting LPAR2 & LPAR3?
2) Since there are separate GIF file on each LPAR used by each Started Task - this would imply that they LPARS are not communicating with each other for this product. Is that correct?
3) It is documented in the installation guide that a new GIF must be allocated when installing a new version. If for any reason, V12.0 would have to be backed off to V11.0 - can the old GIF file be reinstated?
Environment
Release : 12.0
Component : CA MAINFRAME APPLICATION TUNER
Resolution
1) Can LPAR1 be upgraded to 12.0 without impacting LPAR2 & LPAR3?
Yes. You can have many instances of MAT running on the same LPAR in fact...driven by the fact they have their own HLQ, and GRPNAME. The CA MAT 12.0 and CA MAT 11.0 will not know the other exists!
2) Since there are separate GIF file on each LPAR used by each Started Task - this would imply that they LPARS are not communicating with each other for this product. Is that correct?
That is correct...the SYSPLEX=NO means each CA MAT on each LPAR is using it's own GIF and doesn't know of the other MAT instances running on the other LPARs in the plex...
3) It is documented in the installation guide that a new GIF must be allocated when installing a new version. If for any reason, V12.0 would have to be backed off to V11.0 - can the old GIF file be reinstated?
Yes, that would be what would need to happen. You can not use the CA MAT 12.0 GIF on CA MAT 11.0...and visa versa...
You've probable seen this page...when migrating to a new release of CA MAT you are mostly concerned with TUNSSPxx parameters and the UIF/GIF datasets...
http://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/devops/ca-mainframe-application-tuner/12-0/installing/migration-considerations.html
Yes. You can have many instances of MAT running on the same LPAR in fact...driven by the fact they have their own HLQ, and GRPNAME. The CA MAT 12.0 and CA MAT 11.0 will not know the other exists!
2) Since there are separate GIF file on each LPAR used by each Started Task - this would imply that they LPARS are not communicating with each other for this product. Is that correct?
That is correct...the SYSPLEX=NO means each CA MAT on each LPAR is using it's own GIF and doesn't know of the other MAT instances running on the other LPARs in the plex...
3) It is documented in the installation guide that a new GIF must be allocated when installing a new version. If for any reason, V12.0 would have to be backed off to V11.0 - can the old GIF file be reinstated?
Yes, that would be what would need to happen. You can not use the CA MAT 12.0 GIF on CA MAT 11.0...and visa versa...
You've probable seen this page...when migrating to a new release of CA MAT you are mostly concerned with TUNSSPxx parameters and the UIF/GIF datasets...
http://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/devops/ca-mainframe-application-tuner/12-0/installing/migration-considerations.html
Feedback
Yes
No
Powered by
