RE: TWS migration

{\rtf1\ansi\ansicpg1252\fromtext \deff0{\fonttbl
{\f0\fswiss Arial;}
{\f1\fmodern Courier New;}
{\f2\fnil\fcharset2 Symbol;}
{\f3\fmodern\fcharset0 Courier New;}}
{\colortbl\red0\green0\blue0;\red0\green0\blue255;}
\uc1\pard\plain\deftab360 \f0\fs20 Iann-\par
\par
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.  \par
\par
So, yes, it would be an important step to make sure that current scheduling 
does not get impacted.\par
\par
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).\par
\par
Michael Elleby 3.0\par
Tivoli Administration\par
Unilever GIO-NA\par
Service Delivery - Utilities\par
Office 203-381-3049\par
Cell 203-906-6744\par
\par
\par
-----Original Message-----\par
From: Iann Lennox [mailto:Iann.Lennox@xxxxxxxxxxxxxx]\par
Sent: Monday, March 21, 2005 9:45 AM\par
To: tme10@xxxxxxxxxxxxxxxx\par
Subject: RE: [tme10] TWS migration\par
\par
\par
Hi Michael,\par
\par
c.. And lastly, since you are going to a new machine, perform a review\par
of your current 7.0 environment for any Carried Forward scheduling, as\par
this may or may not be a big admin issue to you, but you sure will get a\par
lot of complaints, if schedules for your customers suddently seem to\par
'stop' or don't complete. \par
\par
Does this not get saved when migrating the Schedules db? \par
\par
-----Original Message-----\par
From: owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx]\par
On Behalf Of Michael Elleby\par
Sent: Monday, March 21, 2005 9:38 AM\par
To: tme10@xxxxxxxxxxxxxxxx\par
Subject: RE: [tme10] TWS migration\par
\par
\par
Mario-\par
\par
As Iann gave you the documentation for doing such a migration, I only\par
humbly\par
suggest:\par
  a.. In step 3, use the composer 'validate' command on each file to\par
confirm it's integrity.\par
  b.. In step 9, do a 'makesec' on the security file before you\par
'composer add' the text files, you have the proper rights.\par
  c.. And lastly, since you are going to a new machine, perform a review\par
of your current 7.0 environment for any Carried Forward scheduling, as\par
this may or may not be a big admin issue to you, but you sure will get a\par
lot of complaints, if schedules for your customers suddently seem to\par
'stop' or don't complete. Michael Elleby 3.0 \par
Tivoli Administration \par
Unilever GIO-NA \par
Service Delivery - Utilities \par
Office 203-381-3049 \par
Cell 203-906-6744 \par
\par
  -----Original Message-----\par
  From: Mario Behring [mailto:mariobehring@xxxxxxxxx]\par
  Sent: Monday, March 21, 2005 8:15 AM\par
  To: tme10@xxxxxxxxxxxxxxxx\par
  Subject: [tme10] TWS migration\par
\par
\par
  Hi list,\par
\par
  I have a TWS 7.0 environment up and running ok. I want to migrate\par
everything to 8.2 version. However, the MDM will not be upgraded as the\par
version 8.2 will be installed on a new machine (a more powerful one). \par
\par
  My question is; after installing the Framework and TWS 8.2 MDM at the\par
new box (AIX 5.2.0.0), what files should I copy from the old TWS server\par
so I can have the entire environment (JOBs, Schedules, Configuration\par
files, Users, permissions, etc.) running on this new box ? The entire\par
mozart directory ... anything else ?\par
\par
  Please advise.\par
\par
  Thank you.\par
\par
  Mario\par
  __________________________________________________\par
  Do You Yahoo!?\par
  Tired of spam? Yahoo! Mail has the best spam protection around \par
  http://mail.yahoo.com \par
\par
}