RE: ITM - Standby HUB on different OS ?

The 32/64 bit makes no difference. All the communication is via remote SQL 
which is platform independent.

On Linux/Unix/Windows, the indexed sequential QA1* files do have a 
different form - big endian and small endian, but are bit size 
independent.

If you are making a transition from z/OS hub TEMS to Windows hub TEMS, hot 
standby works fine.

Regards, 
______________________________________________


John Alvord
Advisory Engineer
IBM Tivoli Monitoring 6 Platform
Customer Support 
Office: 1-720-396-2788 
Mobile: none 
jalvord-r/[email protected]

Cloud & Smarter Infrastructure
IBM Support Portal
Open a New Service Request
Update your PMR via Email
Escalate your PMR
My Blog: Wonderful World of Situations
Secure upload to ECUREP







From:   "PODGORSKI Pierre (ext SOGETI - SNCF)" 
<[email protected]>
To:     "Discussion list for Tivoli product and Tivoli Ready products." 
<[email protected]>, 
Date:   08/02/2013 02:11 AM
Subject:        RE: [TME10] ITM - Standby HUB on different OS ?
Sent by:        [email protected]



Hello,
 
Is the Hot backup works to move from 32 to 64 bits os ?
 
Regards,
 
Pierre PODGORSKI
 
 
De : [email protected] [mailto:[email protected]
] De la part de John Alvord
Envoyé : jeudi 1 août 2013 18:27
À : Discussion list for Tivoli product and Tivoli Ready products.
Objet : Re: [TME10] ITM - Standby HUB on different OS ?
 
You can use the Hot Backup setup to go from z/OS to Linux for a one-time 
conversion where the original hub TEMS is unaware of what is happening. 

It is the second backup solution here: 

Sitworld: Best Practice TEMS Database Backup and Recovery 
https://www.ibm.com/developerworks/community/blogs/jalvord/entry/sitworld_best_practice_tems_database_backup_and_recovery?lang=en 

 

Regards, 
______________________________________________ 

 


John Alvord
Advisory Engineer
IBM Tivoli Monitoring 6 Platform
Customer Support 
Office: 1-720-396-2788 
Mobile: none 
jalvord-r/[email protected]

Cloud & Smarter Infrastructure 
IBM Support Portal
Open a New Service Request
Update your PMR via Email
Escalate your PMR
My Blog: Wonderful World of Situations
Secure upload to ECUREP 







From:        Dave Mcneilly/Markham/IBM <[email protected]> 
To:        "Discussion list for Tivoli product and Tivoli Ready products." 
<[email protected]>, 
Date:        08/01/2013 09:14 AM 
Subject:        Re: [TME10] ITM - Standby HUB on different OS ? 
Sent by:        [email protected] 




I just went through this going from windows to zlinux and all is good so 
far.
-----------------
Sent from my BlackBerry Handheld. 

  From: John Alvord [jalvord-r/[email protected]]
 Sent: 08/01/2013 09:08 AM MST
 To: "Discussion list for Tivoli product and Tivoli Ready products." 
<[email protected]>
 Subject: Re: [TME10] ITM - Standby HUB on different OS ? 

Among the distributed platforms [WIndows/Linux/Unix] it works fine and QA 
tests it. 

The two FTO hub TEMS should be at the same maintenance level.

Regards, 
______________________________________________ 

 


John Alvord
Advisory Engineer
IBM Tivoli Monitoring 6 Platform
Customer Support 
Office: 1-720-396-2788 
Mobile: none 
jalvord-r/[email protected]

Cloud & Smarter Infrastructure 
IBM Support Portal
Open a New Service Request
Update your PMR via Email
Escalate your PMR
My Blog: Wonderful World of Situations
Secure upload to ECUREP 








From:        doan nguyen <[email protected]> 
To:        "Discussion list for Tivoli product and Tivoli Ready products." 
<[email protected]>, 
Date:        08/01/2013 09:00 AM 
Subject:        [TME10] ITM - Standby HUB on different OS ? 
Sent by:        [email protected] 




Not ideal, but we are looking into moving to a different OS for our TEMS 
HUB and Standby. So the first step is to build the new Standby on a 
different OS and connect this with the old HUB. Is having 2 different OS 
for the HUB and Standby supported ? and if so any gotcha's ?

-- 
Regards 

Doan Nguyen 
_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]
_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]
_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]
-------
Ce message et toutes les pièces jointes sont établis à l'intention 
exclusive de ses destinataires et sont confidentiels. L'intégrité de ce 
message n'étant pas assurée sur Internet, la SNCF ne peut être tenue 
responsable des altérations qui pourraient se produire sur son contenu. 
Toute publication, utilisation, reproduction, ou diffusion, même 
partielle, non autorisée préalablement par la SNCF, est strictement 
interdite. Si vous n'êtes pas le destinataire de ce message, merci d'en 
avertir immédiatement l'expéditeur et de le détruire.
-------
This message and any attachments are intended solely for the addressees 
and are confidential. SNCF may not be held responsible for their contents 
whose accuracy and completeness cannot be guaranteed over the Internet. 
Unauthorized use, disclosure, distribution, copying, or any part thereof 
is strictly prohibited. If you are not the intended recipient of this 
message, please notify the sender immediately and delete it. 
_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]