|
View previous topic :: View next topic
|
| Author |
Message |
lind sh
New User
Joined: 04 Feb 2015
Posts: 32
Location: Tajikestan
|
|
|
|
Dear friends
Because of improvement and increasing our disk's size we want to DUMP multi volume dataset (type is OSAM) and restore it to a single volume. How is it possible?!
Which control statements we must use in ADRDSSU?
Regards |
|
| Back to top |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
ADRDSSU is the way to go,
so maybe you only need a COPY rather than a Dump followed by a RESTORE. |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 592
Location: London
|
|
|
|
I don't think there is an OSAM format, do you mean QSAM?
The DFDSS control statements below will move it assuming you have the required access. DFDSS will try and create it in as few extents as possible on the target volume. The original volumes will probably have to be DISNEW'd in SMS first so the dataset doesn't go back on them.
COPY ALLE ALLD(*) OPT(4) SPHERE TGTA(SRC) DELETE CATALOG -
DS(INC(your.file.name))
If the target volume is an EAV type you may have to include a PATCH command first to turn the EATTR=OPT on so it can go into cylinder manged space. You'll need access to the STGADMIN profile to use this. However if the dataset has a Dataclas with EATTR=OPT specified you may not need the patch.
SET PATCH 5B = FF |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10891
Location: italy
|
|
|
|
| Quote: |
| I don't think there is an OSAM format, do you mean QSAM? |
it could be a typo but ...
| Quote: |
| OSAM is a special access method supplied with IMS™. |
|
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 592
Location: London
|
|
|
|
| enrico-sorichetti wrote: |
| Quote: |
| I don't think there is an OSAM format, do you mean QSAM? |
it could be a typo but ...
| Quote: |
| OSAM is a special access method supplied with IMS™. |
|
Yeah you're right Enrico, I vaguely remember those from about 25+ years ago, and they were a pain to deal with from what I recall, which isn't much!. I looked it up and couldn't see it as one of the access methods so assumed it's no longer supported, like ISAM. Further looking I see it is there. |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 592
Location: London
|
|
|
|
yawn..
start I/O access method (default method)
The start I/O access method reads OSAM, ESDS, and KSDS data sets at speeds approaching the physical capabilities of the input device, with a significant reduction in CPU time.
native access method (OSAM/VSAM)
The native access method reads the data set at the same speed as an optimally tuned IMS Database Image Copy utility, but you can still take advantage of other product features (such as asynchronous processing and data compression). If you select this method, you can also control the input data set buffer pool size. For more information, see Buffers.
When processing a VSAM KSDS, a HISAM overflow data set, or an overflow data set for a secondary index with duplicate keys, the utility uses control interval access to improve performance. |
|
| Back to top |
|
|
Willy Jensen
Active Member
Joined: 01 Sep 2015
Posts: 740
Location: Denmark
|
|
| Back to top |
|
|
|
|
