Great ideas. Please open Marketing Requirements for the suggestions so that
they can be officially tracked and managed. Thanks, Glenn
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
How about adding a VSAM keyword that after reading the VTOC, looks up
the VSAM CLUSTER and migrates the entire VSAM SPHERE too? Yes, it is
slower, but doing each dataset is even slower.
Any way of doing something with 0 track or invalid datasets? I.E,
reallocating them on another volume then
Oh, and how about a RETRY(#minutes) that retries after a pause of
#minutes for datasets that don't migrate, and a SHUTDOWN option to
retry during SHUTDOWN and a STARTUP option to retry when the system is
restarted. This would help get DISABLED volume empty.
On Wed, Sep 25, 2013 at 11:17 AM, Mike
I would like to see similar option w/HRECOVER. Not for the parallelism (already
provided in z/OS 1.12), but to reduce the number of commands required.
i.e. RECOVER an entire storage group with one command. Rather than (in my case)
several hundred HRECOVER VOLUME(xx) commands per SG.
snip
Oh. If you want to recall a dataset, and the ML volume is busy, use
the last backup volume instead of taking away the ML volume from a
migrate task.
On Wed, Sep 25, 2013 at 11:49 AM, Staller, Allan allan.stal...@kbmg.com wrote:
I would like to see similar option w/HRECOVER. Not for the
the INTERVALMIGRATION tasks to four by specifying:
INTERVALMIGRATION(4)
Richard
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mike Schwab
Sent: Tuesday, September 24, 2013 6:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HMIGRATE in parallel
Hi, other customers with similar scenarios have requested multitasking support
for MIGRATE VOLUME and the addition of a MIGRATE STORAGEGROUP command. I am
currently 'Accepting' requirements for this type of functionality. Assuming
that we deliver this type of functionality in an upcoming
Hi everyone and thanks for your creative feedback!
(sorry for a late reply, I was AFK for a few days..)
So, a few more details about the environment and what problem we're trying to
solve here:
Data sets from several sources are produced in a PIT backup process (mostly
image copies from DB2) to
Configure your backup job to write to a non-GDG PS disk backup.
Once the backups are done, copy them to a GDG on tape.
The next day, overwrite the PS disk backup.
Our job using ADRDSSU:
//CPYADRDS PROC HLQ=VLT,VOL1=DUMMY,GENI='(00)',TYPEI=W,
//
A. Rosenberg hal9...@panix.com wrote:
At 21:40 +0100 on 09/18/2013, Graham Harris wrote about Re: HMIGRATE in
parallel:
I agree. What should not be hard for HSM to create multiple migration
subtasks (each with its own ML2 dataset) and have the master task pass one
dataset at a time to each
I suspect that the reason why this was originally implemented this way is that
the function was added back in the day when there were only reel tapes, tape
drives were at a premium and individual ds migrate commands were infrequest, so
individual command migrations were single threaded and
.
Lizette
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Glenn Wilcock
Sent: Tuesday, September 17, 2013 8:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HMIGRATE in parallel
Hi, are you using the WAIT or NOWAIT option? Even though
Hi,
Please provide more detail related to your environment so that we can better
help. Thanks, Glenn
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message:
snip
I agree. What should not be hard for HSM to create multiple migration
subtasks (each with its own ML2 dataset) and have the master task pass one
dataset at a time to each subtask (ie: The subtask does the same work as is
currently done for a migrate). As each subtask finishes it asks the
Hi, are you using the WAIT or NOWAIT option? Even though it is single tasked,
NOWAIT should just submit the request and then return control back so that the
job is not waiting for the migration to complete. Glenn
--
For
-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Glenn Wilcock
Sent: Tuesday, September 17, 2013 8:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HMIGRATE in parallel
Hi, are you using the WAIT or NOWAIT option? Even though it is single tasked,
NOWAIT
Interesting approach -
If the poster is actually trying to get an application PIT (point in time)
backup of his application using HSM, the only way I could get that to work
here would be to flashcopy the whole thing to new names then run HSM
backups against those new names. Then it would no
]
On Behalf Of Lizette Koehler
Sent: Tuesday, September 17, 2013 8:43 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HMIGRATE in parallel
Glenn
I think he wants to run wide on the migrates. So if he submits 10 migrates,
he
wants them to run concurrently. But the OP states it only mounts one
Yes, it would be but it is not what the OP asked for.
-Original Message-
From: Gibney, Dave [mailto:gib...@wsu.edu]
Sent: Tuesday, September 17, 2013 1:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HMIGRATE in parallel
Is this not called ABARS?
-Original Message-
From: IBM
Is this not called ABARS?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Darth Keller
Sent: Tuesday, September 17, 2013 8:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HMIGRATE in parallel
Interesting approach
1:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HMIGRATE in parallel
Is this not called ABARS?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Darth Keller
Sent: Tuesday, September 17, 2013 8:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
.
-Original Message-
From: Doug [mailto:dsh...@bellsouth.net]
Sent: Tuesday, September 17, 2013 1:43 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HMIGRATE in parallel
Since DB2 is headed to copypool as a back up, what the OP 'wants to do'
sounds great but..
As already stated, HSM migrate by command
Since DB2 is headed to copypool as a back up, what the OP 'wants to do'
sounds great but..
As already stated, HSM migrate by command is single threaded.
Maybe on of the HSM Guru's could jump in on this thread?
Sounds like a great requirement request.
Regards, Doug
Sent from my iPhone
On Sep
At 13:43 -0400 on 09/17/2013, Doug wrote about Re: HMIGRATE in parallel:
As already stated, HSM migrate by command is single threaded.
Maybe on of the HSM Guru's could jump in on this thread?
Sounds like a great requirement request.
I agree. What should not be hard for HSM to create multiple
Hi!
We've got a scenario where we should do a backup of some data to data sets and
after succesful backup send the previous copy to ML2 (so we've got only the
latest on DASD).
Since there are multiple backup jobs, we've tried to send a TSO command (via
IKJEFT01 in the jobs) to HMIGRATE the
, September 16, 2013 9:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: HMIGRATE in parallel
Hi!
We've got a scenario where we should do a backup of some data to data sets and
after succesful backup send the previous copy to ML2 (so we've got only the
latest on DASD).
Since there are multiple backup
ISTR reading in the fine manual that command activities (specifically migrate
and backup) are single threaded...IOW BAD
I believe command recall is an exception to the above.
HTH,
snip
We've got a scenario where we should do a backup of some data to data sets and
after succesful backup send
27 matches
Mail list logo
