Dianne,
The length of time that the DUMP DB command will run depends on the
size of your database. As far as the command syntax goes, I don't have
a Version 1 manual anymore but you might want to check the appendix to
the Admin Reference - here's the JCL I used when upgrading from V1 to
V2....
//IS0EDUMP JOB (0289,O179),'DUMP ADSM DB',CLASS=A,
// MSGCLASS=V,REGION=128M,TIME=1440
//*
//********************************************************************
//* DUMP THE ADSM DATABASE *
//* *
//* *
//* DUMP DB DEVCLASS= *
//* CONSISTENT=<YES NO> *
//* SCRATCH=<YES NO> *
//* VOLUMENAMES=<VOLNAM1,VOLNAM2....> *
//********************************************************************
//SERVER EXEC PGM=DSMSERV,DYNAMNBR=300,TIME=1440,
// PARM='/DUMPDB DEV=CART3480'
//*
//OPT DD DISP=SHR,DSN=ADSM.ADSM.OPT
//DSMAMENG DD DISP=SHR,DSN=SYS1.ADSM.SANRMSG(ANRMENU)
//HLPAMENG DD DISP=SHR,DSN=SYS1.ADSM.SANRHLP(ANRHENU)
//DSK DD DISP=SHR,DSN=ADSM.ADSM.DISKLOG
//SYSPRINT DD SYSOUT=W
//SYSTERM DD SYSOUT=W
The Upgrade process itself is very fast - I think it just updates some
DB records to indicate it's now a Version 2 database. However, this is
irreversible, hence the reason for doing a database dump first.
Tim Pittson
tpittson AT himail.hcc DOT com
>----------
>From: Dianne Sharp[SMTP:DSHARP AT CLEAR.CO DOT NZ]
>Sent: Tuesday, May 27, 1997 11:48 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Migrating from MVS V1 to V2
>
>We are about to upgrade our ADSM MVS Server from V1 to V2. I'm reading
>the MVS V2 Installing Server and Admin Client manual and it says that
>one of the things we should do is use the DUMP DB command with the
>version 1 server to dump the contents of the server database to
>sequential media. However, I can't find anything in the V1 manuals to
>explain the syntax of this command.
>
>Can someone please supply me with the syntax of the command and/or any
>comments you might have after going through the migration yourselves.
>
>Also, does anyone have any idea of how long a DUMP DB or UPGRADE from V1
>to V2 takes?
>
|
