开云体育

Thanks Bob, I will probably do so - especially because I ran into another trouble: DMKLNK117E USERID VSAMIO NOT LINKED; VOLID 191 CONFLICT what happened? created disk image using dasdinit of type 3350

VMCE supplies two preconfigured empty disk packs, labelled VM50U0 and VM50U1 that are to be used only for information put there by the end user. If you use those disk packs for installation specific

Hi Dave, thanks for the pointer. Using a dedicated new pack is definitely a good point here, not meddling with the distribution packs. kind regards Michael

Michael, Try “DISKMAP”. Its on MAINT’s B disk but there is a help file. I would say though if you want more minidisks add a pack for yourself. Makes upgrades simpler. Dave Sent: 14 March 2022

Dear Group, is there a way to figure out if there is place for? a (new) minidisk allocation on a volume? kind regards Michael

Found in the "extended sixpack" direct. :-) Now transferring to my VM/370 installation.. kind regards Michael

Dear René, downloaded your 6pack, ipl'ed VM and searched the sixpack direct up and down for that virtual machine, to no avail. kind regards Michael

Michael, Be aware, again, that in Moshix video M94, VSAMIO usage is illustrated on a cloud extended Sixpack 1.2, which is different from VM/370 CE. In particular, the VSAMIO minidisk containing the

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