236 Getting Started with IBM Tivoli Workload Scheduler V8.3
The dump data of Tivoli Workload Scheduler V8.2 consists of the following
files:
topology_filename is the name of the file that contains the topology data of
the Tivoli Workload Scheduler you are upgrading, where “from cpu=@”
indicates all workstations, workstation classes, and domains.
prompts_filename is the name of the file that contains the prompts of the
Tivoli Workload Scheduler you are upgrading, where “from prompts”
indicates all prompts.
calendar_filename is the name of the file that contains the calendars of the
Tivoli Workload Scheduler you are upgrading, where “from calendars”
indicates all calendars.
parms_filename is the name of the file that contains the parameters of the
Tivoli Workload Scheduler you are upgrading, where “from parms”
indicates all parameters.
resources_filename is the name of the file that contains the resources of
the Tivoli Workload Scheduler you are upgrading, where “from resources”
indicates all resources.
users_filename is the name of the file that contains the users of the Tivoli
Workload Scheduler you are upgrading, where “from users=@#@”
indicates all users.
jobs_filename is the name of the file that contains the jobs of the Tivoli
Workload Scheduler you are upgrading, where “from jobs=@#@”
indicates all jobs.
scheds_filename is the name of the file that contains the job streams of
the Tivoli Workload Scheduler you are upgrading, where “from
scheds=@#@indicates all schedules.
Use these files to import the data into the relational database.
4.6.2 Extracting Tivoli Framework user data from the security file
To extract the Tivoli Management Framework users, perform the following steps:
1. As tws820 user, ensure that the Tivoli Management Framework environment
is set.
# su - tws820
$ . /etc/Tivoli/setup_env.sh
2. Stop the Tivoli Workload Scheduler V8.2 processes.
$ conman stop
$ conman shutdown
Chapter 4. Tivoli Workload Scheduler V8.3: Migration 237
3. Copy the migrtool.tar file to a directory on the Tivoli Workload Scheduler V8.2
environment, as shown in Example 4-84.
Example 4-84 Copying the migrtool.tar file to TWShome directory
$ cp /cdrom/LINUX_I386/utilities/migrtool.tar /usr/local/tws820
4. Make a backup of the files listed in the migrtool.tar file, if they already exist on
the Tivoli Workload Scheduler V8.2 environment, as shown in Example 4-85.
Example 4-85 List of files in the migrtool.tar file and backups in TWShome
$ tar -tvf /usr/local/tws820/migrtool.tar
-rw-r--r-- 0/0 16109 2006-03-27 17:22:19 catalog/C/unison.cat
-rw-r--r-- 0/0 57395 2006-03-27 17:22:27 catalog/C/unison_trace.cat
-rw-r--r-- 0/0 244563 2006-03-27 17:22:58 catalog/C/maestro.cat
-rw-r--r-- 0/0 48859 2006-03-27 17:23:15 catalog/C/maestro_trace.cat
-rwxr-xr-x 0/0 615964 2006-03-27 18:18:19 bin/getfwkusr
-rwxr-xr-x 0/0 791872 2006-03-27 19:04:39 bin/migrutility
-rwxr-xr-x 0/0 1368 2006-03-27 18:18:19 migrfwkusr
-rw-r--r-- 0/0 1441 2006-03-27 18:18:19 set_env
-rwxr-xr-x 0/0 32932 2006-03-27 19:04:24 bin/libatrc.so
-rwxr-xr-x 0/0 1432 2006-03-27 19:04:25 bin/libicudata.so.34
-rwxr-xr-x 0/0 958600 2006-03-27 19:04:27 bin/libicui18n.so.34
-rwxr-xr-x 0/0 83880 2006-03-27 19:04:27 bin/libicutu.so.34
-rwxr-xr-x 0/0 1132876 2006-03-27 19:04:28 bin/libicuuc.so.34
5. As root user, extract the files from the migrtool.tar file into the Tivoli Workload
Scheduler V8.2 environment, as shown in Example 4-86.
Example 4-86 Extracting files from migrtool.tar into TWShome
# cd /usr/local/tws820
# tar -xvf /usr/local/tws820/migrtool.tar
catalog/C/unison.cat
catalog/C/unison_trace.cat
catalog/C/maestro.cat
catalog/C/maestro_trace.cat
bin/getfwkusr
bin/migrutility
migrfwkusr
set_env
bin/libatrc.so
bin/libicudata.so.34
238 Getting Started with IBM Tivoli Workload Scheduler V8.3
bin/libicui18n.so.34
bin/libicutu.so.34
bin/libicuuc.so.34
6. Set permissions, owner, and group of the files extracted from the migrtool.tar
file into Tivoli Workload Scheduler V8.2 environment, as shown in
Example 4-87.
Example 4-87 Setting permissions, owner, and group of the files into TWShome
chmod 755 /usr/local/tws820/bin/getfwkusr
chmod 755 /usr/local/tws820/bin/bin/migrutility
chmod 755 /usr/local/tws820/bin/migrfwkusr
chmod 755 /usr/local/tws820/bin/set_env
chmod tws820.unison /usr/local/tws820/bin/getfwkusr
chmod tws820.unison /usr/local/tws820/bin/bin/migrutility
chmod tws820.unison /usr/local/tws820/bin/migrfwkusr
chmod tws820.unison /usr/local/tws820/bin/set_env
chmod tws820.unison /usr/local/tws820/bin/libatrc.so
chmod tws820.unison /usr/local/tws820/bin/libicudata.so.34
chmod tws820.unison /usr/local/tws820/bin/libicui18n.so.34
chmod tws820.unison /usr/local/tws820/bin/libicutu.so.34
chmod tws820.unison /usr/local/tws820/bin/libicuuc.so.34
7. As tws820 user, set the Tivoli Workload Scheduler V8.2 variables using the
set_env command, and run the dumpsec command to create the input security
file, as shown in Example 4-88.
Example 4-88 Setting Tivoli Workload Scheduler variables and running dumpsec command
# su - tws820
$ /usr/local/tws820/set_env
Environment Successfully Set !!!
$ dumpsec > /usr/local/tws820/dumpsec.users
USER MAESTRO
CPU=@+LOGON=tws820,root
BEGIN
USEROBJ CPU=@ ACCESS=ADD,DELETE,DISPLAY,MODIFY,ALTPASS
JOB CPU=@
ACCESS=ADD,ADDDEP,ALTPRI,CANCEL,CONFIRM,DELDEP,DELETE,DISPLAY,KILL,MODIFY,RELEASE,REP
LY,RERUN,SUBMIT,USE,LIST
SCHEDULE CPU=@
ACCESS=ADD,ADDDEP,ALTPRI,CANCEL,DELDEP,DELETE,DISPLAY,LIMIT,MODIFY,RELEASE,REPLY,SUBM
IT,LIST
RESOURCE CPU=@ ACCESS=ADD,DELETE,DISPLAY,MODIFY,RESOURCE,USE,LIST
PROMPT ACCESS=ADD,DELETE,DISPLAY,MODIFY,REPLY,USE,LIST

Get Getting Started with IBM Tivoli Workload Scheduler V8.3 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.