If you mount volser A00001 and write 500GB that's fine, 1 TB is also fine or however much data you want. If it's 10 bytes that's fine too. The .AWS file representing the tape will be what ever size is written to it. It can be a single data set or stacked sets. We have very few customers that stack data sets on a tape because it's not necessary as there is no file size limit. Granted searching a vtl volume is faster than a real tape, but having one data set to a tape does not expand the footprint of your tapes as everything fits on the same small disk drive footprint. If you need a dataset mount the tape that has it, no need to search.
Ken Kenneth A. Bloom CEO Avenir Technologies Inc /d/b/a Visara International 203-984-2235 bl...@visara.com www.visara.com > On May 20, 2018, at 12:29 AM, R.S. <r.skoru...@bremultibank.com.pl> wrote: > > Ken, > What does it mean you don't limit the size of the volume? > I understand a job can write as much as it need to a single volume, that's > fine. > However tools like DFSMSHSM tend to fill the volume up. In that case some > limit has to be used, otherwise the volume wiil grow up indefinitely. > How do you address this issue? > > Regards > -- > Radoslaw Skorupka > Lodz, Poland > > > > > > > > W dniu 2018-05-18 o 20:05, Ken Bloom pisze: >> Hi Russell >> >> We don't limit the size of the VTL volume so size doesn't enter into it. >> >> Regards >> Ken >> >> Kenneth A. Bloom >> CEO >> Avenir Technologies Inc >> /d/b/a Visara International >> 203-984-2235 >> bl...@visara.com >> www.visara.com >> >> >>> On May 18, 2018, at 2:03 PM, Russell Witt <res09...@verizon.net> wrote: >>> >>> Tony, >>> >>> >>> Another item to throw into the mix is what size of virtual-volumes you >>> define them as. With 3490's, you can define the virtual-volumes in >>> Gigabytes of capacity. If you stack lots of very small files, you run into >>> a problem with the Block-ID not being large enough. With them defined as >>> 3590's, the block-id issue is non-existent because the Block-ID is a 4-byte >>> field on the 3590's. So, if you like to define your virtual-volumes as >>> large volumes; it might actually be better to define them as 3590's. >>> >>> >>> Russell Witt >>> res09...@verizon.net >>> >>> >>> >>> >>> -----Original Message----- >>> From: Tony Thigpen <t...@vse2pdf.com> >>> To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU> >>> Sent: Fri, May 18, 2018 12:52 pm >>> Subject: VTL as 3490 vs 3590 >>> >>> For a little fun on Friday afternoon. >>> >>> We will be replacing our current VTL. >>> >>> The new VTL can be configured to look like 3490s or 3590s. Our current >>> VTL is defined to z/OS as 3490s. >>> >>> Some of the staff are saying: "All VTLs should be defined as 3490s >>> because that is what everybody does." >>> >>> Others are saying: "Let's make them 3590s because then they match the >>> few remaining physical 3590s and if we have an issue with the VTL we can >>> just swap the fiber and continue running on real 3590s until the problem >>> is fixed." >>> >>> It was suggested I ask here to see what others are doing. >>> >>> Thoughts? >>> >>> -- >>> Tony Thigpen >>> > > > ====================================================================== > > > -- > TreœÌ tej wiadomoœci mo¿e zawieraÌ informacje prawnie chronione Banku > przeznaczone wy³¹cznie do u¿ytku s³u¿bowego adresata. Odbiorc¹ mo¿e > byÌ jedynie jej adresat z wy³¹czeniem dostêpu osób trzecich. Je¿eli nie > jesteœ adresatem niniejszej wiadomoœci lub pracownikiem upowa¿nionym do > jej przekazania adresatowi, informujemy, ¿e jej rozpowszechnianie, > kopiowanie, rozprowadzanie lub inne dzia³anie o podobnym charakterze jest > prawnie zabronione i mo¿e byÌ karalne. Je¿eli otrzyma³eœ tê wiadomoœÌ > omy³kowo, prosimy niezw³ocznie zawiadomiÌ nadawcê wysy³aj¹c odpowiedŸ > oraz trwale usun¹Ì tê wiadomoœÌ w³¹czaj¹c w to wszelkie jej kopie > wydrukowane lub zapisane na dysku. > > This e-mail may contain legally privileged information of the Bank and is > intended solely for business use of the addressee. This e-mail may only be > received by the addressee and may not be disclosed to any third parties. If > you are not the intended addressee of this e-mail or the employee authorized > to forward it to the addressee, be advised that any dissemination, copying, > distribution or any other similar activity is legally prohibited and may be > punishable. If you received this e-mail by mistake please advise the sender > immediately by using the reply facility in your e-mail software and delete > permanently this e-mail including any copies of it either printed or saved to > hard drive. > > mBank S.A. z siedzib¹ w Warszawie, ul. Senatorska 18, 00-950 Warszawa, > www.mBank.pl, e-mail: kont...@mbank.pls¹d Rejonowy dla m. st. Warszawy XII > Wydzia³ Gospodarczy Krajowego Rejestru S¹dowego, nr rejestru > przedsiêbiorców KRS 0000025237, NIP: 526-021-50-88. Wed³ug stanu na dzieù > 01.01.2018 r. kapita³ zak³adowy mBanku S.A. (w ca³oœci wp³acony) wynosi > 169.248.488 z³otych. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN