开云体育

Hi Greg, You are missing the vm370r6-essentials archive.? It contains the following files: ??? dmkddr.aws??? ??? ??? (to restore the starter tapes) ??? dmkrio.assemble??? (supplied

It probably been would have been a SSD.? A RAM disk would have been volatile? memory (and fact in various VM download pages include code to do such a thing.) Full screen CMS was/is a awful hack --

Hello! I said I knew it was out there, I did not miss one. If nothing I might have definitely did so, it is because I did not download it before.now. I just did. Can you describe completely the steps

Gregg, You missed one! http://www.smrcc.org.uk/members/g4ugm/VM370.htm and there is an additional optional tape http://www.smrcc.org.uk/members/g4ugm/vm-370/waterloo.aws.bz2 You need to BUNZIP it ad

Hello! So its been added to the basic system regarding the 6 Pack series? I know there's a Waterloo tape some place for the basic system and of course the dreaded additional pack tape that we know how

Folks, Sorry I misread the question. In VM370R6 minidisks are always CKD blocked 800 bytes. In later releases minidisks can be blocked 512/1024/2048/4096. These can be on CKD or FBA but as George says

"The disks are formatted into 800-byte physical records, called blocks. Logical records, which may be fixed-length or variable-length, are imposed on constant physical blocks. Space required for files

Steven, If you are referring to VM minidisks (such as those available to a cms user), I believe that the device type is always the same as what the VM operating system thinks they are. So if VM thinks

Steven, I haven’t looked at the code, but VM/370R6 only uses 800byte blocks so CKD for minidisks. I don’t know how this is mapped to clusters on windows or linux, but its possible it overlaps two

> > Related to this discussion of performance is the virtual device associated > with a minidisc always the same type of device (CKD or FBA) as the > underlying device or can it be different. If it

Thanks for posting that link to the homerow site. The precompiled vma and vmagui utilities work excellently on my Win10 system. I contributed code changes many years ago to the assembler

Our university (second half of the 1980s) used some Japanese clone called NAS I think, and they were proud of their "solid state paging device". I think that is what we would call a RAM disk these

To that end - I have renamed it to SPLCON to YATA "Yet Another Text Archive", and will never mention it again! (probably)

Good - and it certainly seems to meets all needs For me it is a bit heavy weight - I just want something as a text file transport: ASCII/EBCDIC can be done by Hercules/IND$FILE, I don't care about

And there is the fantastic VMAGUI that runs on various platforms.? I use it very frequently on Windows 10 to look at the contents of my VM stuff that I save on my laptop as VMARC files. I even allows

Thanks to René for e-mailing me a link to a video that describes searching for the source with "vma utility homerow" which leads to https://homerow.net/zvm/vma/ I did try searching before to find a

I don't know. It probably is. I've never found any need to delve into the format any more than knowing that it is in 80 column card image format which can readily be sent through a punch / card reader

This is the hack I produced to do that ... https://github.com/adesutherland/spltcon Given no alternatives I will clean it up and make it produce an archive with 80 char lines ...

wrote: Is the format of the archive used by vmarc documented anywhere? if one were to use the pack function to put a number of CMS files into an archive file and then transfer this to another system,

What are you trying actually to do?? Load files onto VM?? Get files off?