RE: TWS migration

Ahh..  Thanks.  I wasn't thinking about the 'cutover'..

Iann

-----Original Message-----
From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx 
[mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx]
On Behalf Of Michael Elleby
Sent: Monday, March 21, 2005 10:09 AM
To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Subject: RE: [tme10] TWS migration


Iann-

The 'carried forward' scheduling does not get saved as the data in the
Schedules database is 'static' info.  The 'carried forward' information
I am referring to are the schedules that are currently running when
Jnextday executes, thus marking them as CF schedules in the new days
Symphony file, which will not exist on the new machine since the new
machine is not yet a member in the environment.  

So, yes, it would be an important step to make sure that current
scheduling does not get impacted.

I think you are referring to the fact that a schedule is marked as carry
foward in its definition (correct me if I am wrong).

Michael Elleby 3.0
Tivoli Administration
Unilever GIO-NA
Service Delivery - Utilities
Office 203-381-3049
Cell 203-906-6744


-----Original Message-----
From: Iann Lennox [mailto:Iann.Lennox-w6+5gY1eu51YzD5mSbZInQ@xxxxxxxxxxxxxxxx]
Sent: Monday, March 21, 2005 9:45 AM
To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Subject: RE: [tme10] TWS migration


Hi Michael,

c.. And lastly, since you are going to a new machine, perform a review
of your current 7.0 environment for any Carried Forward scheduling, as
this may or may not be a big admin issue to you, but you sure will get a
lot of complaints, if schedules for your customers suddently seem to
'stop' or don't complete. 

Does this not get saved when migrating the Schedules db? 

-----Original Message-----
From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx 
[mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx]
On Behalf Of Michael Elleby
Sent: Monday, March 21, 2005 9:38 AM
To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Subject: RE: [tme10] TWS migration


Mario-

As Iann gave you the documentation for doing such a migration, I only
humbly
suggest:
  a.. In step 3, use the composer 'validate' command on each file to
confirm it's integrity.
  b.. In step 9, do a 'makesec' on the security file before you
'composer add' the text files, you have the proper rights.
  c.. And lastly, since you are going to a new machine, perform a review
of your current 7.0 environment for any Carried Forward scheduling, as
this may or may not be a big admin issue to you, but you sure will get a
lot of complaints, if schedules for your customers suddently seem to
'stop' or don't complete. Michael Elleby 3.0 
Tivoli Administration 
Unilever GIO-NA 
Service Delivery - Utilities 
Office 203-381-3049 
Cell 203-906-6744 

  -----Original Message-----
  From: Mario Behring 
[mailto:mariobehring-/E1597aS9LQAvxtiuMwx3w@xxxxxxxxxxxxxxxx]
  Sent: Monday, March 21, 2005 8:15 AM
  To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
  Subject: [tme10] TWS migration


  Hi list,

  I have a TWS 7.0 environment up and running ok. I want to migrate
everything to 8.2 version. However, the MDM will not be upgraded as the
version 8.2 will be installed on a new machine (a more powerful one). 

  My question is; after installing the Framework and TWS 8.2 MDM at the
new box (AIX 5.2.0.0), what files should I copy from the old TWS server
so I can have the entire environment (JOBs, Schedules, Configuration
files, Users, permissions, etc.) running on this new box ? The entire
mozart directory ... anything else ?

  Please advise.

  Thank you.

  Mario
  __________________________________________________
  Do You Yahoo!?
  Tired of spam? Yahoo! Mail has the best spam protection around 
  http://mail.yahoo.com