If you create a PROFILE EXEC on 191 that checks who's running and invokes another exec if it's a dumper machine, e.g.: if userid() /= 'DMPADMIN' then do 'CP SP CON DMPADMIN' 'EXEC' userid() 'CP LOGOFF' end
and create "<userid> EXEC" for every dumper machine that you are actually going to use and that contains something simple (you are going to maintain this), e.g.: ' EXEC DDRCOPY $VOLS$ <source_addr> $VOLS$ <target_addr>' then you only need to write a DDRCOPY EXEC that will link source and target minidisks and invoke DDR program. >From here you only need to maintain <userid> EXEC's from dump maintenance machine and autolog dumper machines to do the work. On 08/02/2008, Ivica Brodaric <[EMAIL PROTECTED]> wrote: > > And if you move 191 minidisk from dumper machines to maintenance userid, > and add a link to that minidisk as 191 RR to SYSDMPPR profile, you can > define a pool of dumper machines, e.g.: > USER DMP password 5M 25M G > POOL LOW 0 HIGH 99 PROFILE SYSDMPPR > > On 08/02/2008, RPN01 <[EMAIL PROTECTED]> wrote: > > > > If you can get them to use a common profile, and possibly run a script > > or > > control file that matches the userid, then there'd really be no need for > > the > > writable 191 in each dumper virtual machine. You could place the 191 > > under > > either $VOLS$ or some other "maintenance" user, and have the profile > > just > > link it rr as well. > > > > We do this with all our Linux guests; they share a single 191 minidisk, > > and > > the profile accounts for any differences that may be required. > > > > -- > > .~. Robert P. Nix Mayo Foundation > > /V\ RO-OE-5-55 200 First Street SW > > /( )\ 507-284-0844 Rochester, MN 55905 > > ^^-^^ ----- > > "In theory, theory and practice are the same, but > > in practice, theory and practice are different." > > > > > > > > > > On 2/6/08 3:25 PM, "Aria Bamdad" <[EMAIL PROTECTED]> wrote: > > > > > On Wed, 6 Feb 2008 12:44:02 -0500 Hilliard, Chris said: > > >> > > >> I need a short lesson on backing up DASD volumes using DDR. > > >> > > > snip > > > > > > Chris, > > > > > > Others have made good suggestions. Over time, you may have more DASD > > > that you want to dump or use multiple virtual machines that you want > > to > > > use simultaniously to dump from. Here is one way to address that: > > > > > > Define one dummy user that owns a full pack minidisk on each volume: > > > > > > USER $VOLS$ NOLOG > > > ACCOUNT SYSTEM SYSTEM > > > MDISK A00 3390 0000 3339 VOLA00 RR > > > MDISK A01 3390 0000 3339 VOLA01 RR > > > MDISK A02 3390 0000 3339 VOLA02 RR > > > MDISK A03 3390 0000 3339 VOLA03 RR > > > MDISK A04 3390 0000 3339 VOLA04 RR > > > > > > > > > Now define multiple dump users that do the dumping to tape. These > > users > > > will have access to the dummy account disks above. To make it > > simpler, > > > just define a user profile first then use that in each dump account: > > > > > > > > > PROFILE SYSDMPPR > > > * Profile for SYSDUMP users > > > ACCOUNT SYSUTIL SYSTEM > > > MACHINE XC > > > IPL CMS PARM AUTOCR > > > CONSOLE 009 3215 > > > SPOOL 00C 2540 READER * > > > SPOOL 00D 2540 PUNCH A > > > SPOOL 00E 1403 A > > > LINK MAINT 190 190 RR > > > LINK MAINT 19E 19E RR > > > LINK $VOLS$ A00 A00 RR > > > LINK $VOLS$ A01 A01 RR > > > LINK $VOLS$ A02 A02 RR > > > LINK $VOLS$ A03 A03 RR > > > LINK $VOLS$ A04 A04 RR > > > > > > Now each new dump account can be define using: > > > > > > USER SYSDUMP PASSWORD 5M 25M G > > > INCLUDE SYSDMPPR > > > MDISK 191 3390 xxxx yyyy zzzzzz W > > > * > > > USER SYSDUMP2 PASSWORD 5M 25M G > > > INCLUDE SYSDMPPR > > > MDISK 191 3390 xxxx yyyy zzzzzz W > > > > > > > > > Now each dump account has a virtual address that matches the real > > > address of a real DASD. You can then do a DDR with input statements > > > that point to the virtual address. > > > > > > Remember to never make this LINK or MDISK statements in write mode. > > > Everything > > > should be in read only mode. > > > > > > Aria > > > > >
