Re: Minidisk allocation planning
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 with label VSAMIO and attached it @ cuu = 06D5 in the config file
created user vsamio in the directory with minidisk 191 for vol VSAMIO
added attach 6d5 to system as VSAMIO in the profile exec of autolog1
?kind regards
Michael
|
Re: Minidisk allocation planning
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 minidisks, then when a new VM370CE release comes out, you can copy the user volumes to the new system release, and just add the new directory entries.
Bob
On Mon, Mar 14, 2022 at 6:21 AM Michael Grom < macbaer@...> wrote: 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
|
Re: Minidisk allocation planning
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
|
Re: Minidisk allocation planning
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 ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Michael Grom
Sent: 14 March 2022 09:14
To: [email protected]
Subject: [h390-vm] Minidisk allocation planning? Dear Group, is there a way to figure out if there is place for? a (new) minidisk allocation on a volume??
kind regards
Michael
|
Minidisk allocation planning
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 搁别苍é,
downloaded your 6pack, ipl'ed VM and searched the sixpack direct up and down for that virtual machine, to no avail.?
kind regards
Michael
|
On Sun, Mar 13, 2022 at 01:01 AM, Michael Grom wrote:
I was watching moshix' M94 video (Part 2 on how to use VSAM on VM/370 from COBOL + PL/I using VSAMIO)
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 MACLIBs, TXTLIB, and example programs used in the video is NOT available on VM/370 CE. Moreover, Jay Moseley has changed the way he distributes VSAMIO so the video instructions regarding its download and install (if there are any, I don't remember) are most probably obsolete now.
?
If you are ever interested by VSAMIO, one possible way to get it on VM/370 CE would be to transfer it from my old obsolete 6PExt. On that system, minidisk 191 of the NOLOG virtual machine VSAMIO contains all the stuff mentionned in the video.
?
Cheers,
?
Rene FERLAND, Montreal
|
Thanks :-) didn't know about that ... much easier than my
MOVEFILE approach with FILEDEFs
Am 13.03.2022 um 12:44 schrieb Dave
Wade:
toggle quoted message
Show quoted text
WHy? COPYFILE (REPL is fine. It creates a new
file and then renames the source at the end.
?
Dave
?
?
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 this:
two filedefs, INPUT with LRECL V, output with LRECL FIXED 80,
MOVEFILE INPUT OUTPUT
then rename to result to original
You could look at my Stanford Pascal Compiler sites, maybe
you find the EXEC there:
HTH
kind regards
Bernd
?
?
Am 13.03.2022 um 10:01 schrieb Michael
Grom:
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 small program and tried to compile. Before that, I
linked to COBOL 191 and accessed the mini disk as B.?
cobol mycob
SYSTEM/360 COBOL COMPILER? ? ? ? ? CB545 V2 LVL78
OPEN ERROR CODE '03' ON 'SYSIN '.
?
Ready; T=0.01/0.04 08:48:47
That was kind of unexpected to me. As René Ferland
explained, the Cobol compiler is significantly older than
the system itself and was lifted from a previous version of
MVS. Hence the use of VSAMIO which brings VSAM capability to
these old compilers. However, the problem seems to start
much earlier, at least with my?
VM/370 CE 1.1 installation.
query cplevel
SYSTEM 4381-A
VM/370 Community Edition Version? 1 Release? 1.1 03/10/22
08:54:40
?
Ready; T=0.01/0.01 08:56:28
update: I created the source file with "ee" without any
further specification, quite naively. A dir * cobol yields
Filename Filetype Fm? Format? ? Recs Blocks? ? Date? ?
?Time? ?Label
MYCOB? ? COBOL? ? A1? V? ? 32?
? ?10? ? ? 1? 03/12/22? ?16:29? CMS191
Could it be the old compiler chokes because of the file
attributes V and lrecl=32??
Is there a way to specify that beforehand or to change the
record attributes later??
kind regards
Michael
|
WHy? COPYFILE (REPL is fine. It creates a new file and then renames the source at the end. ? Dave ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Bernd Oppolzer via groups.io
Sent: 13 March 2022 09:20
To: [email protected]
Subject: Re: [h390-vm] COBOL compile error? 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 this: two filedefs, INPUT with LRECL V, output with LRECL FIXED 80,
MOVEFILE INPUT OUTPUT
then rename to result to original You could look at my Stanford Pascal Compiler sites, maybe you find the EXEC there:
HTH
kind regards Bernd ? ? Am 13.03.2022 um 10:01 schrieb Michael Grom: 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 small program and tried to compile. Before that, I linked to COBOL 191 and accessed the mini disk as B.? cobol mycob SYSTEM/360 COBOL COMPILER? ? ? ? ? CB545 V2 LVL78 OPEN ERROR CODE '03' ON 'SYSIN '. ? Ready; T=0.01/0.04 08:48:47
That was kind of unexpected to me. As René Ferland explained, the Cobol compiler is significantly older than the system itself and was lifted from a previous version of MVS. Hence the use of VSAMIO which brings VSAM capability to these old compilers. However, the problem seems to start much earlier, at least with my?
VM/370 CE 1.1 installation. query cplevel SYSTEM 4381-A VM/370 Community Edition Version? 1 Release? 1.1 03/10/22 08:54:40 ? Ready; T=0.01/0.01 08:56:28
update: I created the source file with "ee" without any further specification, quite naively. A dir * cobol yields Filename Filetype Fm? Format? ? Recs Blocks? ? Date? ? ?Time? ?Label MYCOB? ? COBOL? ? A1? V? ? 32? ? ?10? ? ? 1? 03/12/22? ?16:29? CMS191
Could it be the old compiler chokes because of the file attributes V and lrecl=32??
Is there a way to specify that beforehand or to change the record attributes later?? kind regards
Michael
|
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 ? FTDEFaults COBOL F 80 ? Take a look at “FSHELP EE” and the sections on profile and configuration. (If you use FSHELP you can move the cursor over the entry you want to view and hit PF1) ? Dave ? ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Michael Grom
Sent: 13 March 2022 09:01
To: [email protected]
Subject: [h390-vm] COBOL compile error? 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 small program and tried to compile. Before that, I linked to COBOL 191 and accessed the mini disk as B.? cobol mycob SYSTEM/360 COBOL COMPILER? ? ? ? ? CB545 V2 LVL78 OPEN ERROR CODE '03' ON 'SYSIN '. ? Ready; T=0.01/0.04 08:48:47
That was kind of unexpected to me. As René Ferland explained, the Cobol compiler is significantly older than the system itself and was lifted from a previous version of MVS. Hence the use of VSAMIO which brings VSAM capability to these old compilers. However, the problem seems to start much earlier, at least with my?
VM/370 CE 1.1 installation. query cplevel SYSTEM 4381-A VM/370 Community Edition Version? 1 Release? 1.1 03/10/22 08:54:40 ? Ready; T=0.01/0.01 08:56:28
update: I created the source file with "ee" without any further specification, quite naively. A dir * cobol yields Filename Filetype Fm? Format? ? Recs Blocks? ? Date? ? ?Time? ?Label MYCOB? ? COBOL? ? A1? V? ? 32? ? ?10? ? ? 1? 03/12/22? ?16:29? CMS191
Could it be the old compiler chokes because of the file attributes V and lrecl=32??
Is there a way to specify that beforehand or to change the record attributes later?? kind regards
Michael
|
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 this:
two filedefs, INPUT with LRECL V, output with LRECL FIXED 80,
MOVEFILE INPUT OUTPUT
then rename to result to original
You could look at my Stanford Pascal Compiler sites, maybe you
find the EXEC there:
HTH
kind regards
Bernd
Am 13.03.2022 um 10:01 schrieb Michael
Grom:
toggle quoted message
Show quoted text
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 small program and tried
to compile. Before that, I linked to COBOL 191 and accessed the
mini disk as B.?
cobol mycob
SYSTEM/360 COBOL COMPILER? ? ? ? ? CB545 V2 LVL78
OPEN ERROR CODE '03' ON 'SYSIN '.
?
Ready; T=0.01/0.04 08:48:47
That was kind of unexpected to me. As René Ferland explained,
the Cobol compiler is significantly older than the system itself
and was lifted from a previous version of MVS. Hence the use of
VSAMIO which brings VSAM capability to these old compilers.
However, the problem seems to start much earlier, at least with
my?
VM/370 CE 1.1 installation.
query cplevel
SYSTEM 4381-A
VM/370 Community Edition Version? 1 Release? 1.1 03/10/22
08:54:40
?
Ready; T=0.01/0.01 08:56:28
update: I created the source file with "ee" without any further
specification, quite naively. A dir * cobol yields
Filename Filetype Fm? Format? ? Recs Blocks? ? Date? ? ?Time?
?Label
MYCOB? ? COBOL? ? A1? V? ? 32? ? ?10? ? ? 1? 03/12/22? ?16:29?
CMS191
Could it be the old compiler chokes because of the file
attributes V and lrecl=32??
Is there a way to specify that beforehand or to change the
record attributes later??
kind regards
Michael
|
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 small program and tried to compile. Before that, I linked to COBOL 191 and accessed the mini disk as B.?
cobol mycob
SYSTEM/360 COBOL COMPILER? ? ? ? ? CB545 V2 LVL78
OPEN ERROR CODE '03' ON 'SYSIN '.
?
Ready; T=0.01/0.04 08:48:47
That was kind of unexpected to me. As René Ferland explained, the Cobol compiler is significantly older than the system itself and was lifted from a previous version of MVS. Hence the use of VSAMIO which brings VSAM capability to these old compilers. However, the problem seems to start much earlier, at least with my?
VM/370 CE 1.1 installation.
query cplevel
SYSTEM 4381-A
VM/370 Community Edition Version? 1 Release? 1.1 03/10/22 08:54:40
?
Ready; T=0.01/0.01 08:56:28
update: I created the source file with "ee" without any further specification, quite naively. A dir * cobol yields
Filename Filetype Fm? Format? ? Recs Blocks? ? Date? ? ?Time? ?Label
MYCOB? ? COBOL? ? A1? V? ? 32? ? ?10? ? ? 1? 03/12/22? ?16:29? CMS191
Could it be the old compiler chokes because of the file attributes V and lrecl=32??
Is there a way to specify that beforehand or to change the record attributes later??
kind regards
Michael
|
Re: Using Hercules version specific config file parameters with VM370CE
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) will never be used to distribute VMCE content.?搁别苍é, I suggest you use those names for your private?data minidisks. When a new VM release comes out, just copy those disk volumes to the new release, over top of the empty ones we supply and update the USER DIRECT file appropriately. Also copy any shadow files for those?User volumes.
Bob
|
Re: Using Hercules version specific config file parameters with VM370CE
搁别苍é, ? 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 SYSTEM attached to your VM. Punch IPL FMT it to your reader (NOH and IPL it, e.g. ? purge r????????????????????????????????????????????? ?NO? FILES PURGED??????????????????????????????????? Ready; T=0.01/0.01 14:47:34????????????????????????? spool pun *??????????????? ?????????????????????????? Ready; T=0.01/0.01 14:47:42????????????????????????? punch ipl fmt s (noh???????????????????????????????? PUN FILE 0617? TO? MAINT??? COPY 01 NOHOLD?????????? Ready; T=0.01/0.03 14:47:56????????????????????????? ipl c??????? ???????????????????????????????????????? VM/370 FORMAT/ALLOCATE PROGRAM RELEASE 6???????????? ENTER FORMAT OR ALLOCATE:??????????????????????????? format?????????????????????????????????????????????? FORMAT FUNCTION SELECTED???????????????????????????? ENTER DEVICE ADDRESS (CUU):????????????????????????? 131????????????????????????????????????????????????? ENTER DEVICE TYPE:????????????????????????????????? 3350??????????????????????????????????????????????? ENTER START CYLINDER (XXX OR XXXX) OR "LABEL":????? label????????????????????????? ????????????????????? ENTER DEVICE LABEL: TTEST ? ??????????????????????????????? ? ? Dave ? ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of rvjansen@...
Sent: 12 March 2022 14:23
To: [email protected]
Subject: Re: [h390-vm] Using Hercules version specific config file parameters with VM370CE? Well … skip that. I varied the wrong address online. (Still interested in the answer tho). 搁别苍é.
? 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 CE already has. I put it on another address, and when attaching it with: /attach 6a9 to system as vm51-7 (I thought to be clever and just attach it with another name and change it to that in the USER DIRECT) /13:53:19 DASD 6A9 VOLID VM50-7 DOES NOT MATCH So I am doubting now to vmarc the content of its minidisks and reformat, or to relabel it, which seems quicker. Is there a command to relabel it? ?
On 12 Mar 2022, at 14:04, Bob Bolch <Bob@...> wrote: ? Hi Gary, 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 fixed before release if we can. Everything?takes a lot longer to fix now, than it did in 1978! ? Hi Bob,
Bob Bolch wrote:
> Starting with the Community Edition Version 1 Release 1.2 (the current?
> release),
Is that a typo, or is 1.1.2 set to be released shortly?
Regards,
Gary
?
?
|
Re: Using Hercules version specific config file parameters with VM370CE
Well … skip that. I varied the wrong address online.
(Still interested in the answer tho).
toggle quoted message
Show quoted text
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 CE already has. I put it on another address, and when attaching it with:
/attach 6a9 to system as vm51-7
(I thought to be clever and just attach it with another name and change it to that in the USER DIRECT)
VM tells me that:
/13:53:19 DASD 6A9 VOLID VM50-7 DOES NOT MATCH
So I am doubting now to vmarc the content of its minidisks and reformat, or to relabel it, which seems quicker. Is there a command to relabel it?
Many thanks in advance,
Best regards,
搁别苍é.
On 12 Mar 2022, at 14:04, Bob Bolch < Bob@...> wrote:
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
fixed before release if we can. Everything?takes a lot longer to fix now, than it did in 1978! Bob? Hi Bob,
Bob Bolch wrote:
> Starting with the Community Edition Version 1 Release 1.2 (the current?
> release),
Is that a typo, or is 1.1.2 set to be released shortly?
Regards,
Gary
|
Re: Using Hercules version specific config file parameters with VM370CE
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 CE already has. I put it on another address, and when attaching it with:
/attach 6a9 to system as vm51-7
(I thought to be clever and just attach it with another name and change it to that in the USER DIRECT)
VM tells me that:
/13:53:19 DASD 6A9 VOLID VM50-7 DOES NOT MATCH
So I am doubting now to vmarc the content of its minidisks and reformat, or to relabel it, which seems quicker. Is there a command to relabel it?
Many thanks in advance,
Best regards,
搁别苍é.
toggle quoted message
Show quoted text
On 12 Mar 2022, at 14:04, Bob Bolch < Bob@...> wrote:
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
fixed before release if we can. Everything?takes a lot longer to fix now, than it did in 1978! Bob? Hi Bob,
Bob Bolch wrote:
> Starting with the Community Edition Version 1 Release 1.2 (the current?
> release),
Is that a typo, or is 1.1.2 set to be released shortly?
Regards,
Gary
|
Re: Using Hercules version specific config file parameters with VM370CE
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
fixed before release if we can. Everything?takes a lot longer to fix now, than it did in 1978! Bob?
Hi Bob,
Bob Bolch wrote:
> Starting with the Community Edition Version 1 Release 1.2 (the current
> release),
Is that a typo, or is 1.1.2 set to be released shortly?
Regards,
Gary
|
Re: Using Hercules version specific config file parameters with VM370CE
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 likes to "tinker" and learn. So my experience is more along the novice level and while I want to learn Rexx, the VM370 specifics like "nolog" are lost on me. I am guessing now that "nolog" means cannot log on. I will read more of the documentation to learn. I am grateful that you guys are taking your time to share your knowledge and experience so that others, like me can learn. Peace, Jaime On Sat, 12 Mar 2022 03:52:40 -0800, "Bob Bolch" <Bob@...> wrote: 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 for these distributions is either the
general user who wants
to learns about mainframe computing in the 1970s, or the system
programmer who
used VM/370 in that era, and really liked working on it. The new user can become familiar with
how things worked, using the CMSUSER uer ID. The primary documentation is here:
[1] and the
enhancements to the
system (like REXX or full screen editting) are mostly based on changes
that were incorporated
into later versions of VM by IBM. Some of the later IBM documentation can suplement the
HELP file documentation.
Starting with the Community Edition Version 1 Release 1.2 (the current
release), we
set up an issue reporting area at [2]
Most people just bring up issues on this mailing list and I enter the
issues,
so I can keep track.
In the old days, each IBM manual started with an explanation of changes
since the last release.
That is why the readme files have been retained for the Sixpack/VMCE
releases for the last
decade.
This is a completely volunteer effort, so there are always things that
can be improved.
Best regards,
Bob
Links:
------
[1]
[2]
[3] /g/h390-vm/message/4071
[4]
mailto: [email protected]?subject=Re:%20Re%3A%20%5Bh390-vm%5D%20Using%20Hercules%20version%20specific%20config%20file%20parameters%20with%20VM370CE [5]
mailto:Bob@...?subject=Private:%20Re:%20Re%3A%20%5Bh390-vm%5D%20Using%20Hercules%20version%20specific%20config%20file%20parameters%20with%20VM370CE [6] /mt/88093602/4526575
[7] /g/h390-vm/post
[8] /g/h390-vm/editsub/4526575
[9] mailto:[email protected]
[10] /g/h390-vm/leave/11166232/4526575/1317415517/xyzzy
|
Re: Using Hercules version specific config file parameters with VM370CE
Hi Bob, Bob Bolch wrote: Starting with the Community Edition Version 1 Release 1.2 (the current release), Is that a typo, or is 1.1.2 set to be released shortly? Regards, Gary
|
Michael Grom
René Ferland
