Mark,
I'm suitably impressed.
You can do this with some of the database reorg software, but they aren't
part of the base OS.
I can understand some of the OP's frustration now.
Ron
>
> If it was a file on a Linux system using LVM, I could move the physical
> extents that hold that file anywher
>>> On 4/12/2011 at 11:18 AM, Ron Hawkins
>>> wrote:
> I would like to
> know what other OS supports transparently moving an open file without
> disrupting the application that has it open.
If it was a file on a Linux system using LVM, I could move the physical extents
that hold that file any
If you take frequent checkpoints, you could cancel, back out to the
last check point, then restart on another system.
On Tue, Apr 12, 2011 at 10:47 AM, McKown, John
wrote:
> I guess zero downtime would require that all "server" type functionality be
> duplexed on multiple images and that said se
e-
> From: IBM Mainframe Discussion List
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL
> Sent: Tuesday, April 12, 2011 9:54 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: moving extends for allocated VSAM linear data set
>
> >The IBM rep should have said: "
ginal Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of
> Michael Klaeschen
> Sent: Monday, April 11, 2011 10:26 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: [IBM-MAIN] moving extends for allocated VSAM linear data set
>
> Ravi, thanks fo
>The IBM rep should have said: "The z means zero __unplanned__
downtime.". I am not aware of any OS on any platform which does not
require an occasional re-initialization (reboot, IPL, whatever
I think you've misunderstood IBM's intent.
With Parallel SYSPLEX, shared everything, IMSPLEX, and/or DB2
z/OS TCPIP will work just fine with only the "default root" (the root
that is mounted if there is an error in BPXPRM**).
It also supports a "altroot" file system.
This sounds to me like a planning/data placement failure, not a sysplex
design point failure.
I was told a "Softek" product may prov
Depending on the filesystem .. you should be able to at least minimize the
downtime... and not require an IPL. OMVS is restartable.
Just create a new filesystem/dataset, copy everything into it, stop the
application and swap the new one for the old one, restart app, copy any
missing files from old
On Tue, 2011-04-12 at 07:26 +0200, Michael Klaeschen wrote:
> Ravi, thanks for your reply. I was told a "Softek" product may provide
> this function as part of data migration support. But no, we just have z/OS
> and a couple of Redbooks, Whitepapers and the ringing sound of IBM sales
> represent
sendet von: IBM Mainframe Discussion List
2011-04-11 11:08
Bitte antworten an
IBM Mainframe Discussion List
An
IBM-MAIN@bama.ua.edu
Kopie
Thema
Re: moving extends for allocated VSAM linear data set
Do you have any t
Do you have any third party tool? to do so...
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/arch
Hi,
we have a VSAM linear data set which is allocated read/write to an ASID.
Now, the extents have to be moved to another VolSer without affecting the
ASID. How to do? IDCAMS ALTER ADD/REMOVEVOLUMES or REPRO do not
seem to work for VolSers with allocated extents that are opened.
Thank you, chee
12 matches
Mail list logo
