开云体育

Fish - please don't apologize. You are doing fantastic work, thank's for that! I asked on this group, because I it was unexpected for me, because all books and materials I read, didnt notice such

Is there some material you can share on how to use DITTO for those tasks? I'm conversant with MVT and it's progeny, but I'm a total DOS neo.

Piotr Kolasinski wrote: You could be right. I apologize. I was going from memory. It might be because the files is declared "SD" and not "DA"? Maybe wit

I agree that once you have a fairly static I/O config it makes sense to build a supervisor that matches, but you always did need the function when building a DOS or DOS/VS system from a distribution

Hi, Harold and Piotr, From what I recall, from the last century, it was probably the 1980s the last time I actually worked with DOS/VSE at all "for real"... and it was a long time ago. The way

@Steen I use DITTO very often - to check VTOC, labels, read BSAM file etc. I like it very much and show my students how to use it. But in this case I need to understand the sysem's behaviore. It seems

Fish thanks for explanation but ... it is different than results of my test. I have access to z/VSE 6.1 and wrote the program in cobol, which inloop wruet 80 bytes records with increnebted counter

Eddy Balem wrote: I was going to mention that too, BUT... It's a lot easier to simply add the new devices to the supervisor (and then shutdown and re-ipl the new supervisor) than it is to have to

Just one minor point,you don't need to rebuild the DOS or DOS/VS supervisor to add devices. You can use Add and Del statements at ipl time, subject to the limit specified in the original build .

Harold Grovesteen wrote: I would to add to that, that due to this need for manually maintaining the location of all datasets (files) on the system, many shops wrote their own (or used someone else's)

Hi, A utility like DITTO might be useful in this case as it can perform a lot of file manipulations on different media, e.g: dasd and tape. Regard, Steen

I worked on DOS/VS systems back in the mid- to late 1970's. While DOS/VS has some extent protections as mentioned, actual management of space on volumes is manually performed.? This was usually

Hi, Rene, FYI, OS/360, OS/VS1, and OS/VS2 (SVS and MVS) also had "expiration date protection" of datasets available.? It was mainly used for tape datasets, but it could also be used for DASD

Fish, Mark, Thanks a lot for this information! I always love to learn something new, specially from people who work on DOS/VS in the past. Cheers, Rene FERLAND, Montreal

Hi, Rene and Piotr, From what I recall, from the last century, it was probably the 1980s the last time I actually worked with DOS/VSE at all "for real"... and it was a long time ago. The way DOS/360

Piotr Kolasinski wrote: There are no stupid questions if they are asked. It is only when you don't ask your question that it becomes stupid. ;-) No. If the file is never OPENED, it will never be

Me neither, before I asked the same question as you in this group. :-) I can't say for sure, but I would not be surprised if DISP=DELETE on MVS just delete the entries in the catalog and VTOC, not

Thanks Rene! I never heard about this tool . It's really strange that for manage space on dasd volume we have to use "diagnostic" tool (as it is defined in last z/VSE documentation). In real that is

I can't answer for your questions 2 and 3 (Fish, can you?). But for 1 above, I use a program called IKQVDU. It can be run in a batch job or interactively on the console. I used the latter. It goes on