开云体育

Yes, but how do they help? Dave Sent: 28 February 2025 09:59 To: [email protected] Subject: Re: [h390-vm] BCPL request I see. So far these posts are not CMS specific: 1978

I see. So far these posts are not CMS specific: 1978 ( https://cds.cern.ch/record/1292450/files/n-137.pdf ) and 1984 ( https://groups.google.com/g/net.lang.c/c/ht4q3DU6nDM/m/HKI_UCOsJRIJ ). -- VM/370

Ahh, yes.. people not playing nicely with other people's stuff.. that's why in the mid-70s my 2nd or 3rd CP mod was to force disconnect idle VMs after 10 minutes cheers, William

Never seen BCPL on VM/CMS. Can't find any downloads. Martin Richards still has a web page but no VM/CMS version on there... I think you might be on

https://www.softwarepreservation.org/projects/BCPL/index.html#IBM says -- VM/370 CE V1R1.2, Hercules on macOS

The VMREAD is there for the SAVESYS CMS as well as for an ACCESS (NOPROF. I remember the early days at IBM's VM test center in Belgium: people that left their 3270 logged on often suffered from

You're missing a crucial detail for an absolutely safe RENAME * CP LINK sharedDisk xxxx 111 M * ACCESS 111 N * COPYFILE ABC EXEC A ABC NEWEXEC N (OLDDATE * RENAME ABC EXEC N = OLDEXEC N (NOUPDIRT *

While is in some ways a silly analogy it might help to think of *CP* (Control Program in VM/CMS environments) as *BIOS* (in traditional PCs) - hit the wrong key during a reboot and, ...the results are

Thanks, it worked perfectly. I honestly never imagined that one <enter> too many could cause such a problem. Thanks again, I'm going to stop playing with teddy bears and go back to turkeys. Marco

I think so. Thats why it pauses after IPL so you can save the CMS segment Dave

[email protected]> wrote: Yes. That's specifically because CMS keeps a copy of the file directory of the S and Y disks in the saved system, so if you don't do this, the CMS users won't see the

The SAVESYS command *MUST* be *ONLY* entered at the 1st VM READ after the IPL command. If you wait until after the 1st ready message, then it won't work. The problem is that DMSINS has some additional

A useful way to avoid having to resave CMS all the time is to have an additional program disk to hold locally installed stuff that's not part of the base CMS installation. We used a minidisk that was

Yes I press enter. Is this the mistake I made? Marco

You didn't press enter at this point did you? On checking it needs to be straight after the IPL

typing error 2) copyfile myprogram a == z2 sorry Marco

Ok, I tryed ... 2) copyfile my program a = = z ... 3.4) access (noprof 3.5) savesys cms .... Now I get: DMSFRE161T INVALID DMSFRET CALL FROM F87AE8, ERROR NUMBER 5. DMSFRE164T LOW-CORE NUCLEUS STORAGE

Well it needs to mode 2 so the copy has to be = = z2... .. I then think you need "access (noprof" after the IPL and before the savesyd but on my phone so can't check manuals Dave [email protected]>

Here I am again to ask one last thing (I hope). From what I understand, when you want to move a program to minidisk MNT19E 19E Y/S to make it available to all other users, you have to (re)save the CMS

rexxtry REXX interpreter running (CMS bREXX 1.0.1 Jul ?5 2022) Enter any valid REXX instruction... type EXIT to quit. Rexxtry; '' DMSITP143T PROTECTION EXCEPTION OCCURRED AT F20A02 IN SYSTEM ROUTINE