LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (June 2000, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 8 Jun 2000 22:03:54 -0400
Reply-To:     "Michael A. Raithel" <maraithel@EROLS.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Michael A. Raithel" <maraithel@EROLS.COM>
Subject:      Re: MVS - truncated SAS library after a backup
Comments: To: "L. Bertolini" <bertolini.1@OSU.EDU>
Content-Type: text/plain; charset="iso-8859-1"

L. Bertolini wrote an interesting addition to Thomas J Hanan's sad tale of a SAS Data Library's mistreatment at the hands of HSM:

>"Hanan, Thomas J" wrote: >> >> Hello SAS-Lers, >> >> >> I've never found a way to fix a SAS dataset when this happens > >Well, I've never had this happen, so I've never had to try to >fix it. I *think* that MVS access methods "see" SAS datalibraries >as plain, old, vanilla, RECFM=FBS datasets. If that's true, then >it *might* be possible to copy the SAS data library, which had been >split by HSM recall onto two volumes, back onto one volume, using >IEBGENER. > >e.g. > >if YOUR.SAS.DLIB used to be 600 CYL on one volume, and it's >been "split" by HSM recall onto two volumes, (400 CYL and 200 CYL), >try to copy YOUR.SAS.DLIB to YOUR.NEW.DLIB, specifying a single >VOLSER and SPACE=(CYL,600). Then try using YOUR.NEW.DLIB. > >Larry >

Larry, hey, good thought! I had another thought that might work. (The operant word is "might"). Hey, Tom has nothing to lose at this point!

In the SAS Companion for the MVS Environment, First Edition, pages 532 -533 are given over to a section titled: Allocating a SAS Data Library on Multiple DASD Volumes. I have done this in the dim and distant past for new SAS Data Libraries, but this could be the ticket. Uncatalog the SAS Data Library after first noting the two volumes that it is on. Then run JCL that looks something like this:

//VOL1 DD DSN=TOMS.FRAGED.SASLIB, // UNIT=3390, // DISP=(MOD,KEEP,KEEP), // VOL=SER=TOM01 //VOL2 DD DSN=TOMS.FRAGED.SASLIB, // UNIT=3390, // DISP=(MOD,KEEP,KEEP), // VOL=SER=TOM02 //CATL DD DSN=TOMS.FRAGED.SASLIB, // UNIT=3390, // DISP=(OLD,CATLG,KEEP), // VOL=SER=(TOM01,TOM02)

In the example, above, the JCL could be a part of an IEFBR14 or a simple SAS program JCL. The first two DD statements identify the existing portions of the SAS Data Library. The final DD statement catalogs the two portions together as one big happy SAS Data Library.

Larry and Tom, it would be interesting to see if this is the antidote to HSM's harmful meddling. Best of luck to you as you continue to work on that most fascinating of processing platforms: OS/390 (MVS)!

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Michael A. Raithel "The man who wrote the book on performance." Raithel Consulting Services E-mail: maraithel@erols.com Author: Tuning SAS Applications in the MVS Environment +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Welcome my son, welcome to the machine... -- Pink Floyd +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Back to: Top of message | Previous page | Main SAS-L page