| Summary | Understanding the relationship between Orbix Mainframe 6.x license files and the underlying platform |
|---|---|
| Article Number | 13677 |
| Environment | Orbix Mainframe 6.x All supported platforms |
| Question/Problem Description | What is the relationship between Orbix Mainframe 6.x license files and the underlying platform? How is the Orbix Mainframe license member related to the platform? Is the Orbix Mainframe license connected to a specific machine? |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | The Orbix Mainframe 6.x license files are independent of the underlying platform. That is, changing the OS version, or hardware will not require a new license file. |
| Workaround | |
| Notes | Please note, an exception to the above statement relates to license files distributed in the AsaiaPac region. These files can be "node-locked". That is, the license file can be tied to a particular host machine. While the license files are generally independent of the underlying platform version, the License Agreement may differ. Please contact your sales account manager if upgrading the platform running Orbix. |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 23 June 2012 |
| First Published date: | 09 September 2011 |
#KnowledgeDocs
#Orbix
