开云体育

Thanks :-) didn't know about that ... much easier than my MOVEFILE approach with FILEDEFs Am 13.03.2022 um 12:44 schrieb Dave Wade:

WHy? COPYFILE (REPL is fine. It creates a new file and then renames the source at the end. Dave Sent: 13 March 2022 09:20 To: [email protected] Subject: Re: [h390-vm] COBOL compile error Hello

Michael, Yes it needs FB80 so :- copy mycob cobol a = = = (repl recfm f lrecl 80 or before you save in EE do RECFM F LRECL 80 You can customize it with a PROFILE EE file to set COBOL to be FB80

Hello Michael, my guess is that the source file needs to be FIXED 80. I wrote a small EXEC to convert such LRECL V files to LRECL F. Don't have access to my VM machine at the moment, but it goes like

Dear Group, I was watching moshix' M94 video (Part 2 on how to use VSAM on VM/370 from COBOL + PL/I using VSAMIO) and thought I give COBOL a try, first, without the VSAM example. So I prepped a very

Thanks, Dave. In VMCE 1.1.1, I added the VM50U0 and VM50U1 as user pack volume serial numbers. Those packs are empty in the distribution, and those names (or anything of that name pattern - VM50Ux)

René, There isn’t a “command” as such. You can use the standalone Format Allocate program. Its available as IPL FMT on the “S” disk. Make sure the disk you want to label is detached from

Well … skip that. I varied the wrong address online. (Still interested in the answer tho). René.

Hi Bob, to prepare for the release of VM370CE 1.1.2 I am getting rid of some sixpack version I am running, and one has a dasd that I allocated for a user; unfortunately it is called VM50-7, which the

Hi Gary, Ooops :-) I have 1.1.2 on the brain, since we are trying to get it out as soon as we can. The current release is 1.1.1. We want to get at least a few more of the bugs at

Bob and Rene, Thank you guys for helping me understand. I see now the reasoning for the readme's and the value they add to be included. I am the user that was a former computer operator in the 80s who

Hi Bob, Bob Bolch wrote: Is that a typo, or is 1.1.2 set to be released shortly? Regards, Gary

On Sat, Mar 12, 2022 at 02:17 AM, rvjansen@... wrote: Hi Jamie, Thanks to René for explaining the way the readme files build on the previous versions of VM/370. I believe the target VM/370 user

Hi Jaime, as these subsequent releases build on older work, you see different readme’s belonging to those older releases all in the same directory; this is not unusual for these efforts. Most of the

Hi Bob, I am a new user to the VM370CE world, so I was looking for the userids to logon. I looked in the readme files. The one with userids is readme-1_2.txt. This readme stated that there was a BREXX

Jaime, Well if its in the readme it should be there, and the link also needs the user to exist. I know Bob has moved stuff round so it may have gon. From his E-Mail looks like its now on MAINTC Dave

I am using VM/370 Community Edition V1R1.1 I am new so I did not know about linking to another disk. I was looking for the BREXX user. Thanks wrote:

Please elaborate on the "packaging issue for the readme files", so it can be fixed. The current source code for BREXX and GCC runtime library files for CMS, are on the MAINTC user ID in VMCE. Thanks!

J Which versión of CE? Its not usually useful to logon to BREXX, you can link the disk:- link brexx 191 199 rr Ready; T=0.01/0.01 11:43:05 access 199 x X (199) R/O Ready; T=0.01/0.01 11:43:10 Then

Gentlemen, I am grateful for the amazing work on VM370CE and also SDL yperion and Hercules.? I reached this forum because I am running a Raspberry Pi and Herc 3.13.? I also had the IPL issue and I