Re: VOLSER issue with DASDCOPY
| Newsgroups | gmane.comp.emulators.hercules390.general |
|---|---|
| Message-ID | <CAJTOO58=uwGqPGZnDqVTy2ZL9kAqGzmM=brbBu2aZcgOa7Y4KQ@mail.gmail.com> |
On a real system you usually have a member called CLIP or RENAME to rename the offline volume with ICKDSF. Of course, the difficulties of Hercules attaching the file are an additional layer that may not let you do this. Here is IBM's Example. https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ickug00/initex.htm On Fri, May 31, 2019 at 9:08 AM rahimazizarab-/[email protected] [hercules-390] < [email protected]> wrote: > > > When using DASDCOPY to create a new volume it retains the original dasd > identity (volser). This makes the new dasd unusable in an existing system > due to having two identical DASDs vtoc information; and in some other > system it would result in a DASD that has a different filename and volser.. > It seems to me that it should use the new dasd name as the volser or give > an option to change it. I could not find a work around to change the dasd > name. > > > > Rahim > > > > > > -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all?