Hello Allan,
DEFINE DUMPCLASS(MIGDMP /* FOR CLASS MIGDMP */ -
UNIT(ATL90) /* USE ATL90 DEVICES */ -
RETPD(16) /* KEEP DUMP COPIES FOR 16 DAYS */ -
AUTOREUSE /* MAKE VOLUMES AVAIL FOR REUSE */ -
NORESET /* DO NOT RESET CHANGE BIT */ -
STACK(10) /* 10 DUMP COPIES PER TAPE */ -
NODSRESTORE /* NO SINGLE DATASET RESTORES */ -
FREQUENCY(5) /* MIN DAYS FROM LAST VOL DUMP */ -
VTOCCOPIES(1)) /* KEEP 1 VTOC COPY DATASET */
/* THIS DUMP CLASS IS FOR */
/* THE WEEKLY DUMPING OF ML1 */
/* VOLUMES */
/*
*/
SETSYS -
AUTODUMPSTART(0300 0400)
/* PROVIDE TIME TO START AUTO */
/* DUMP, LATE START TIME, */
/* AND QUIESCE TIME. AUTO DUMP *
Jake
On Fri, May 24, 2013 at 6:29 PM, Staller, Allan <[email protected]>wrote:
> Please post the dump class definitions for MIGDMP.
>
> DEFINE DUMPCLASS (MIGDMP ...........
>
>
> Al Staller | Z Systems Programmer | KBM Group | (Tel) 972 664-3565 |
> [email protected]
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Jake anderson
> Sent: Friday, May 24, 2013 12:28 AM
> To: [email protected]
> Subject: Re: HSM option
>
> Hello,
>
> 1) HSM request for scratch tape, when performing a full volume dump of the
> volumes associated with some dump class. We have setup like below
>
> ADDVOL MIGL00
> UNIT(3390)
> MIGRATION
> (MIGRATIONLEVEL1
> AUTODUMP(MIGDMP)
> NOSMALLDATASETPACKING)
> THRESHOLD(85)
> ADDVOL MIGL01
> UNIT(3390)
> MIGRATION
> (MIGRATIONLEVEL1
> AUTODUMP(MIGDMP)
> NOSMALLDATASETPACKING)
> THRESHOLD(85)
>
>
> As per above code, we have two migration volumes (MIGL00 and MIGL01)
> defined under MIGDMP dump class.
>
>
> 2) There are only two DASD volume associated with this dump class.
>
> 3) In my previous email, I have wrongly put the dump time 0500 to 0600. It
> is actually dumping MIGL00 and MIGL01 volume on every Wednesday between
> 0300 to 0400.
>
>
> In our case, when every Wednesday dump starts at 0300, it ask for scratch
> tape volume, but I actually want dump of MIGL00 and MIGL01 volumes going
> into the used tape rather then scratch tape.
>
> I want to do this because, we are planning to migrate from ATL3494 to
> TS3400 tape library, which has very minimum number of I/O slots where we
> can keep data cartridge as compare to ATL 3494.
>
> if HSM ask for scratch tape volume everytime , then I will shortly run of
> the tapes and dump will fail. So, I want HSM to use the tape volume which
> has valid data and fill it to maximum before it ask for new scratch tape.
>
>
> Hope this is more clear now.
>
> Jake
>
>
> On Thu, May 23, 2013 at 11:36 PM, retired mainframer <
> [email protected]> wrote:
>
> > Your inconsistent use of terminology makes it difficult to fully
> > understand the problem.
> >
> > Is the new scratch tape requested when performing the backup of
> > datasets that happen to be on a volume associated with some dump
> > class? Or does the situation occur when performing a full volume dump
> > of the volumes associated with some dump class?
> >
> > A dump volume is a tape volume. Since you retain each dump
> > volume for
> > 16 days and perform your dumps every 7 days, you must have more than two.
> > Did you mean there are only two DASD volumes associated with the dump
> > class?
> >
> > Why do you think the dumps are performed between 0500 and 0600
> > when your AUTODUMPSTART operand specifies 0300 to 0400?
> >
> > Reading between the lines, I will take a stab and assume you are
> > addressing the issue of stacking (DASD) volume dumps on a single tape
> > volume. I think you are misinterpreting the purpose of the STACK(10)
> > operand. It allows you to place the dumps of up to ten DIFFERENT DASD
> > volumes on a single tape during a single dump operation. It does NOT
> > allow you to place ten different dumps of the SAME volume on a tape.
> >
> > If you look at the description of the STACK operand in the HSM Storage
> > Administration manual (Chapter 36 in my 1.11 copy), you will find:
> >
> > "DFSMShsm selects empty dump volumes as targets for auto or command
> dump."
> >
> > and
> >
> > "A given dump volume:
> > ...
> > Never contains more than one dump copy of the same source volume.
> > ..."
> >
> >
> >
> > :>: -----Original Message-----
> > :>: From: IBM Mainframe Discussion List
> > [mailto:[email protected]] On
> > :>: Behalf Of Jake anderson
> > :>: Sent: Thursday, May 23, 2013 2:47 AM
> > :>: To: [email protected]
> > :>: Subject: HSM option
> > :>:
> > :>: Hello All,
> > :>:
> > :>: In HSM, when we are taking backup of dump class volume, it
> > :>: always
> > :>: using scratch tape. But we want to change this configuration, so
> > that I
> > :>: should use existing tape which has data rather then new scratch tape.
> > :>:
> > :>:
> > :>: We are doing this because we are planning to migrate our 3494 ATL
> > to
> > :>: TS3400
> > :>: tape library . TS3400 Tape library has only 17 data cartridge slot
> > in
> > :>: compare to ATL 3494 has many. So that whenever HSM takes backup
> > in tape
> > :>: it
> > :>: should use only exsiting data cartridge until it becomes full.
> > Once it
> > :>: becomes full then it should look for new scratch tape.
> > :>:
> > :>:
> > :>: For doing this configuration, I have made below changes in HSM
> > parmlib
> > :>: member. IN parmlib definition as below for taking dump. Every
> > Wednesday
> > :>: it
> > :>: takes dump between 5 to 6 AM.We have two dump volume in our
> > systems,
> > :>:
> > :>:
> > :>: DEFINE -
> > :>: DUMPCYCLE(NNNYNNN /* 7-DAY DUMP CYCLE WITH DUMP */ -
> > :>: CYCLESTARTDATE(1992/05/17)) /* DONE ONLY WEDNESDAY */
> > :>: /* */
> > :>:
> > :>: DEFINE DUMPCLASS(MIGDMP /* FOR CLASS MIGDMP */ -
> > :>: UNIT(ATL90) /* USE ATL90 DEVICES */ -
> > :>: RETPD(16) /* KEEP DUMP COPIES FOR 16 DAYS */ -
> > :>: AUTOREUSE /* MAKE VOLUMES AVAIL FOR REUSE */ -
> > :>: NORESET /* DO NOT RESET CHANGE BIT */ -
> > :>: STACK(10) /* 10 DUMP COPIES PER TAPE */ -
> > :>: NODSRESTORE /* NO SINGLE DATASET RESTORES */ -
> > :>: FREQUENCY(5) /* MIN DAYS FROM LAST VOL DUMP */ -
> > :>: VTOCCOPIES(1)) /* KEEP 1 VTOC COPY DATASET */
> > :>: /* THIS DUMP CLASS IS FOR */
> > :>: /* THE WEEKLY DUMPING OF ML1 */
> > :>: /* VOLUMES */
> > :>: /* */
> > :>: SETSYS -
> > :>: AUTODUMPSTART(0300 0400)
> > :>: /* PROVIDE TIME TO START AUTO */
> > :>: /* DUMP, LATE START TIME, */
> > :>: /* AND QUIESCE TIME. AUTO DUMP */
> > :>:
> > :>: SETSYS -
> > :>: SELECTVOLUME(
> > :>: BACKUP(SCRATCH)
> > :>: MIGRATION(SCRATCH)
> > :>: DUMP(SCRATCH))
> > :>:
> > :>:
> > :>: Now I have changed this SCRATCH to SPECFIC using below commands.
> > :>:
> > :>:
> > :>: HSENDCMD SETSYS SELECTVOLUME (MIGRATION(SPECIFIC))
> > :>: HSENDCMD SETSYS SELECTVOLUME (BACKUP(SPECIFIC))
> > :>: HSENDCMD SETSYS SELECTVOLUME (DUMP(SPECIFIC))
> > :>:
> > :>:
> > :>: But still I noticed that while taking dump, HSM using scratch tape .
> > :>: Please provide your pointers.
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> > email to [email protected] with the message: INFO IBM-MAIN
> >
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
