IBM Tivoli Storage Manager, Version 7.1

The manifest file for the data extraction to media

During the data extraction to media, the DSMUPGRD utility creates a manifest file. The manifest file contains information about the volumes and device classes that are used for storing the extracted data.

The manifest file is required by the data insertion process when you are using media to move the database to the V7.1 server. You specify the name of the manifest file when you run the DSMSERV INSERTDB utility.

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Windows operating systems In the manifest file, the device configuration section contains information about the configuration settings of the source server device. You might need to edit settings, such as device names and drive element numbers, before you use the manifest file with the DSMSERV INSERTDB utility, especially if the utility is run on a different system.

A manifest file has content that is similar to the following example:

* Version 2 manifest file for EXTRACTDB
DEVCLASS=3584L2
STREAMS=1
VOLUMENAMES000=L12345
* Device Configuration Information
DEFINE DEVCLASS 3584L2 DEVTYPE=LTO FORMAT=DRIVE MOUNTLIMIT=DRIVES MOUNTWAIT=60
MOUNTRETENTION=60 PREFIX=ADSM LIBRARY=3584L2 WORM=NO DRIVEENCRYPTION=ALLOW
SET SERVERNAME MOKSHA
DEFINE LIBRARY 3584L2 LIBTYPE=SCSI SERIAL="00000002267304AB" SHARED=YES
AUTOLABEL=YES RESETDRIVE=YES
DEFINE DRIVE 3584L2 3584L2_DRV1 ELEMENT=265 ONLINE=Yes WWN="500507630F18BA09"
SERIAL="0007859130"
DEFINE PATH MOKSHA 3584L2 SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=/dev/IBMchanger5 ONLINE=YES
DEFINE PATH MOKSHA 3584L2_DRV1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=3584L2 DEVICE=/dev/IBMtape20 ONLINE=YES

z/OS operating systems The device configuration section contains device configuration information for the source server. Device configuration statements are based on definitions from the source server, but the statements are transformed into the format required by a server running on AIX® or Linux on System z®. The device configuration section is set up to use a z/OS® media server for media access.

A manifest file for an upgrade to an AIX or a Linux on System z system has content similar to the following example:

* Version 2 manifest file for EXTRACTDB
DEVCLASS=TAPE3592
STREAMS=1
VOLUMENAMES000=JJY010,JJY011,JJY012
/* Device Configuration */
DEFINE LIBRARY 3592LIB LIBTYPE=ZOSMEDIA
DEFINE DEVCLASS 3592CLASS DEVTYPE=3592 ESTCAPACITY=314572800K PREFIX=ADSM
MOUNTLIMIT=2 MOUNTRETENTION=60 MOUNTWAIT=60 COMPRESSION=Yes UNIT=C06M5N03 WORM=No
PROTECTION=No FORMAT=Drive LIBRARY=3592LIB
DEFINE PATH MVSTS 3592LIB SRCTYPE=SERVER DESTTYPE=LIBRARY
ZOSMEDIASERVER=TUCMVSTS ONLINE=YES
DEFINE DEVCLASS FILE DEVTYPE=File MAXCAPACITY=2097152K PREFIX=SVTSMS1
MOUNTLIMIT=20
DEFINE DEVCLASS FROM-MVSTT DEVTYPE=File MAXCAPACITY=2097152K PREFIX=SVTSMS1
MOUNTLIMIT=100
DEFINE DEVCLASS TO-MVSTT DEVTYPE=Server SERVERNAME=TUCMVSTT
MAXCAPACITY=2097152K PREFIX=ADSM MOUNTLIMIT=50 RETRYPERIOD=10 RETRYINTERVAL=30
DEFINE SERVER TUCMVSTT COMMMETHOD=TCPIP HLADDRESS=tucmvstt.storage.tucson.ibm.com
LLADDRESS=2533 NODENAME=MVSTS SERVERPASSWORD=18bf4d36c185
DEFINE SERVER PURGE COMMMETHOD=TCPIP HLADDRESS=purge.storage.tucson.ibm.com
LLADDRESS=1500 SERVERPASSWORD=180fb66e028d
DEFINE SERVER STA_PURGE COMMMETHOD=TCPIP HLADDRESS=purge.storage.tucson.ibm.com
LLADDRESS=1502 SERVERPASSWORD=18909a64694f303df677
DEFINE SERVER TUCMVSTS COMMMETHOD=TCPIP HLADDRESS=9.11.92.48 LLADDRESS=2556
SERVERPASSWORD=184feb8740bb139271
SET SERVERNAME MVSTS
SET SERVERPASSWORD 1891a1cefdcaf489d86c66af54

Feedback