|
I changed the subject line to be more specific.
I caused the existing difficulty with ARCHLVL -vs- ARCHMODE because I thought that 3.13 supported both. That was an error on my part. However, there are more incompatibilities than just ARCHMODE/ARCHLVL.? The currently available VM370CE release exposed bugs in ECPSVM support for Hyperion only. That bug is reported as fixed, but I have found new bugs in the operation of the CP PER command modification, when ECPSVM YES is present in the configuration file and Hyperion 4.4.0 is used.
I think saying that you cannot use VM370CE with HERCGUI is not desirable, when the change needed to allow that package to work is trivial for the end user.?
Which of these is the most acceptable?for VM370CE to supply?
1. A config file for each release.? 2. One config file with tailoring instructions for other releases. 3. A small config file for each release. Each has an INCLUDE statement to pull in the common elements. Most statements are common between releases and would be in this common section. 4. One config file for the oldest supported Hercules release with instructions for modifying it for other Hercules releases.? 5. Same as 4, but we supply one config file for the newest release.
A separate question is can we ever drop support for a Hercules release??
Another question is what happens when an "old" configuration statement like ARCHMODE stops being accepted by a newer Hercules?
Your thoughts would be appreciated. Bob Bolch
|
Bob Bolch wrote: I changed the subject line to be more specific.
I caused the existing difficulty with ARCHLVL -vs- ARCHMODE
because I thought that 3.13 supported both. And I compounded the difficulty by coding my HercGUI to summarily reject ARCHMODE (even though Hercules v4.x still accepts it (albeit with a deprecation warning)). That was an error on my part. And on my part as well. However, there are more incompatibilities than just
ARCHMODE/ARCHLVL. Indeed. New statements have been added and old ones changed or dropped altogether. The currently available VM370CE release exposed bugs in ECPSVM
support for Hyperion only. That bug is reported as fixed, but I
have found new bugs in the operation of the CP PER command
modification, when ECPSVM YES is present in the configuration
file and Hyperion 4.4.0 is used. Uh oh! I hope you opened a new github issue for this so we (you?) can get it fixed! I think saying that you cannot use VM370CE with HERCGUI is not
desirable, when the change needed to allow that package to work
is trivial for the end user. True. But what we *really* need is a foolproof(?) way of detecting which version of Hercules the user intends to use, and then using the correct (compatible) configuration file for that version. Which of these is the most acceptable for VM370CE to supply?
1. A config file for each release. Yes. With each clearly marked as being for what version, and separate invoking scripts for each version (e.g. "hercv3 ..." and "hercv4 ..."). Each would be identical except for which configuration file it used. OR... perhaps some sophisticated batch file logic that determines ahead of time which version of Hercules the user has installed (is going to use) and then setting a flag telling it which config file to use. But I agree something needs to be done. 2. One config file with tailoring instructions for other releases.
3. A small config file for each release. Each has an INCLUDE statement to
pull in the common elements. Most statements are common between releases
and would be in this common section. That would work for Hercules since Hercules does indeed support INCLUDE statements. Unfortunately however, my HercGUI doesn't (yet). :( 4. One config file for the oldest supported Hercules release with
instructions for modifying it for other Hercules releases.
5. Same as 4, but we supply one config file for the newest release. Between 4 and 5, I prefer 5 of course, but then I'm biased too. A separate question is can we ever drop support for a Hercules release? A *damn* good question! Another question is what happens when an "old" configuration statement
like ARCHMODE stops being accepted by a newer Hercules? Another good question. Your thoughts would be appreciated. Done. -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@...
|
A very good new year to all of us, and thank you for this exemplary and very positive discussion.
A separate question is can we ever drop support for a Hercules release?
A *damn* good question!
My point of view is this: although our efforts are focused on preservation of our heritage, this is only part of it, it is not a museum(1), and recent releases of OS and VM from the community contain clear anachronisms - which I am very happy about!
I am not inclined to regard the simulator a part of this museum, and I would love it to move forward. In my view, when end of support for a specific application, like the VM/370CE set, is *clearly indicated*, well in advance, *and* a version that is compatible with older versions *is kept online* (with an optional, do-it-yourself upgrade path).
The version indication can be of the form ‘VM/370CE VxRyMz is tested with release X of Hercules, and issues can be filed for releases upwards of version Y only; lower versions are not supported by the maintainers’.
I deplore the forking that took place but let’s not open that wound. In my opinion, the introduction of an incompatibility, for instance in the Hercules parameters, must have a very good reason. This is why I am particularly happy with Fish’s and Bobs latest email exchange.
Let me finish with: we, the users and maybe only occasional developers are very thankful for all your work on this, and look at VM/370CE, how very nice it has become with the xedit and rexx compatible, well working contributions on it.
best regards,
搁别苍é.
(1) well maybe the ideal museum, in which you can play with everything, everything works, and keeps getting better.
|
Hi Bob, Fish and others,
Please note that I'm including information provided by Fish is a
newer post than this one...
To summarize the posts and include additional information to the
discussion.
??? Hercules 3.x knows nothing about the newer Hercules 4.x
ARCHLVL and other configuration parameters.
??? Hercules 4.x will accept the older Hercules 3.x configuration
parameters, but will issue a warning that are deprecated.
??? Fish's HercGUI (Windows only) currently rejects the Hercules
3.x configurations parameters (to be accepted in the next release)
and INCLUDE statements.
??? Jacob Dekel's HercStudio (Linux and Mac) only supports
Hercules 3.x only.? I'm not sure if it accepts INCLUDE
statements.?
??? ??? I'm not sure that Jacob is maintaining this as the Yahoo
group is no longer available.
??? None graphical interface users who are only affected by the
differences between Hercules 3.x and 4.x.
I had thought that Bob's option 3 was the best and easiest to
maintain, but given the above information, I would suggest a
single file with both Herc 3.x and Herc 4.x statements commented
out and include some sort of Installation/User document similar to
Jurgen Winkelmann's TK4- document.?
Fish has suggested an configuration/installation script to make
the necessary changes to the configuration file based on the
version of Hercules installed or failing that to prompt the user
for the Hercules version.?
I think that a good Installation/User manual would go a long way
to making new users to VM/370 CE more comfortable and at ease with
it no matter which Hercules version or direction is chosen by the
maintainers.
As far as dropping support for older versions of Hercules, I
would say not until there is a reliable way to get SDL Hercules
4.x installed on Linux and Mac either by the distro's Software
Manager utility, a DEB/RPM file or a reliable Build/Make file from
source option.? Otherwise, you will have done a disservice to the
community.
Thanks for listening.
Regards,
Gary?
On 1/2/22 10:58 AM, Bob Bolch wrote:
toggle quoted message
Show quoted text
I changed the subject line to be more specific.
I caused the existing difficulty with ARCHLVL -vs-
ARCHMODE because I thought that 3.13 supported both. That
was an error on my part. However, there are more
incompatibilities than just ARCHMODE/ARCHLVL.? The currently
available VM370CE release exposed bugs in ECPSVM support for
Hyperion only. That bug is reported as fixed, but I have
found new bugs in the operation of the CP PER command
modification, when ECPSVM YES is present in the
configuration file and Hyperion 4.4.0 is used.
I think saying that you cannot use VM370CE with HERCGUI
is not desirable, when the change needed to allow that
package to work is trivial for the end user.?
Which of these is the most acceptable?for VM370CE to
supply?
1. A config file for each release.?
2. One config file with tailoring instructions for other
releases.
3. A small config file for each release. Each has an
INCLUDE statement to pull in the common elements. Most
statements are common between releases and would be in this
common section.
4. One config file for the oldest supported Hercules
release with instructions for modifying it for other
Hercules releases.?
5. Same as 4, but we supply one config file for the
newest release.
A separate question is can we ever drop support for a
Hercules release??
Another question is what happens when an "old"
configuration statement like ARCHMODE stops being accepted
by a newer Hercules?
Your thoughts would be appreciated.
Bob Bolch
|
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 read through and understand about the CONF file and ARCHMODE.? I can now IPL.? I noticed that the read me files mention the BREXX user and when I try to logon, it says it is not in the CP Directory.? I mention this here because if it is not included, then it is also a packaging issue with the readme files. I use HercGUI on RPi along with Hercules 3.13 because those are the packages provided. I am a newby here, so if my comments are off topic, please let me know.? 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 ? FSLIST * * X ? Will show you the files. Not sure there is anything relevant to users on 迟丑别谤….?? ? Dave G4UGM ???????????????????????????????? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of j.carpenter@...
Sent: 11 March 2022 16:33
To: [email protected]
Subject: Re: [h390-vm] Using Hercules version specific config file parameters with VM370CE? 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 read through and understand about the CONF file and ARCHMODE.? I can now IPL.? I noticed that the read me files mention the BREXX user and when I try to logon, it says it is not in the CP Directory.? I mention this here because if it is not included, then it is also a packaging issue with the readme files. I use HercGUI on RPi along with Hercules 3.13 because those are the packages provided. I am a newby here, so if my comments are off topic, please let me know.? Thanks
|
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.?
|
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 On Fri, 11 Mar 2022 16:46:26 -0000, "Dave Wade" <dave.g4ugm@...> wrote: 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
FSLIST * * X
Will show you the files. Not sure there is anything relevant to users on
迟丑别谤….??
Dave
G4UGM
????????????????????????????????
FROM: [email protected] ON BEHALF OF j.carpenter@...
SENT: 11 March 2022 16:33
TO: [email protected]
SUBJECT: Re: [h390-vm] Using Hercules version specific config file
parameters with VM370CE
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 read through and understand
about the CONF file and ARCHMODE. I can now IPL. I noticed that the read
me files mention the BREXX user and when I try to logon, it says it is
not in the CP Directory. I mention this here because if it is not
included, then it is also a packaging issue with the readme files. I use
HercGUI on RPi along with Hercules 3.13 because those are the packages
provided. I am a newby here, so if my comments are off topic, please let
me know. Thanks
Links:
------
[1] /g/h390-vm/message/4065
[2]
mailto: [email protected]?subject=Re:%20Re%3A%20%5Bh390-vm%5D%20Using%20Hercules%20version%20specific%20config%20file%20parameters%20with%20VM370CE [3]
mailto:dave.g4ugm@...?subject=Private:%20Re:%20Re%3A%20%5Bh390-vm%5D%20Using%20Hercules%20version%20specific%20config%20file%20parameters%20with%20VM370CE [4] /mt/88093602/4526575
[5] /g/h390-vm/post
[6] /g/h390-vm/editsub/4526575
[7] mailto:[email protected]
[8] /g/h390-vm/leave/11166232/4526575/1317415517/xyzzy
|
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
toggle quoted message
Show quoted text
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Jaime
Carpenter
Sent: 11 March 2022 17:14
To: [email protected]
Subject: Re: [h390-vm] Using Hercules version specific config file parameters
with VM370CE
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
On Fri, 11 Mar 2022 16:46:26 -0000, "Dave Wade" <dave.g4ugm@...>
wrote:
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
FSLIST * * X
Will show you the files. Not sure there is anything relevant to users
on ther….
Dave
G4UGM
FROM: [email protected] ON BEHALF OF j.carpenter@...
SENT: 11 March 2022 16:33
TO: [email protected]
SUBJECT: Re: [h390-vm] Using Hercules version specific config file
parameters with VM370CE
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 read through and understand
about the CONF file and ARCHMODE. I can now IPL. I noticed that the
read me files mention the BREXX user and when I try to logon, it says
it is not in the CP Directory. I mention this here because if it is
not included, then it is also a packaging issue with the readme files.
I use HercGUI on RPi along with Hercules 3.13 because those are the
packages provided. I am a newby here, so if my comments are off topic,
please let me know. Thanks
Links:
------
[1] /g/h390-vm/message/4065
[2]
mailto:[email protected]?subject=Re:%20Re%3A%20%5Bh390-
vm%5D%20Using%20Hercules%20version%20specific%20config%20file%20pa
rameters%20with%20VM370CE
[3]
mailto:dave.g4ugm@...?subject=Private:%20Re:%20Re%3A%20%5B
h390-
vm%5D%20Using%20Hercules%20version%20specific%20config%20file%20pa
rameters%20with%20VM370CE
[4] /mt/88093602/4526575
[5] /g/h390-vm/post
[6] /g/h390-vm/editsub/4526575
[7] mailto:[email protected]
[8]
/g/h390-vm/leave/11166232/4526575/1317415517/xyzzy
|
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 userid, when I tried it that is where I got the not in CP Directory message. The multiple readme files, at first were confusing because they are a mix of Sixpack, TK4-, vm370ce and others. If this is not going to be called "Sixpack" then it seems to me that those readme files could be removed and some of the info put into the VM370CE readme. Also, those sixpack readmes mention "Please report any issues on the " [email protected]" mailing list." I think that is no longer valid. Thanks, Jaime Carpenter On Fri, 11 Mar 2022 12:45:56 -0500, "Bob Bolch" <Bob@...> 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!
Bob Bolch
Links:
------
[1] /g/h390-vm/message/4066
[2]
mailto: [email protected]?subject=Re:%20Re%3A%20%5Bh390-vm%5D%20Using%20Hercules%20version%20specific%20config%20file%20parameters%20with%20VM370CE [3]
mailto:Bob@...?subject=Private:%20Re:%20Re%3A%20%5Bh390-vm%5D%20Using%20Hercules%20version%20specific%20config%20file%20parameters%20with%20VM370CE [4] /mt/88093602/4526575
[5] /g/h390-vm/post
[6] /g/h390-vm/editsub/4526575
[7] mailto:[email protected]
[8] /g/h390-vm/leave/11166232/4526575/1317415517/xyzzy
|
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 time is spent working on technical improvements, and, for example, on the online help. The fact that the BREXX user is ’nolog’ is clearly indicated in bullet 14 of readme-vmce-1_1_1.txt.
It is imaginable to write a manual for this distribution, and I encourage you to do so. I admit that for new users to a particular system the basics are always a bit hard to find. I know, because I like playing with Multics, CDC NOS/BE, Music/SP and others in addition to MVS (z/OS) which I worked on most of my career. The trick is always to read all the readme’s in reverse chronological order.
Even if we have one big readme/manual, it needs to have all this older info. This is because when people use subsequent versions, they need to see what has changed, but also how it was, and why it became to be. Also, don’t forget to download the relevant product documentation from bitsavers.
Best regards,
搁别苍é.
toggle quoted message
Show quoted text
On 12 Mar 2022, at 05:38, Jaime Carpenter <j.carpenter@...> wrote:
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 userid, when I
tried it that is where I got the not in CP Directory message.
The multiple readme files, at first were confusing because they are a mix
of Sixpack, TK4-, vm370ce and others. If this is not going to be called
"Sixpack" then it seems to me that those readme files could be removed and
some of the info put into the VM370CE readme. Also, those sixpack readmes
mention "Please report any issues on the "[email protected]" mailing list."
I think that is no longer valid.
Thanks,
Jaime Carpenter
On Fri, 11 Mar 2022 12:45:56 -0500, "Bob Bolch" <Bob@...> 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!
Bob Bolch
Links:
------
[1] /g/h390-vm/message/4066
[2]
mailto:[email protected]?subject=Re:%20Re%3A%20%5Bh390-vm%5D%20Using%20Hercules%20version%20specific%20config%20file%20parameters%20with%20VM370CE
[3]
mailto:Bob@...?subject=Private:%20Re:%20Re%3A%20%5Bh390-vm%5D%20Using%20Hercules%20version%20specific%20config%20file%20parameters%20with%20VM370CE
[4] /mt/88093602/4526575
[5] /g/h390-vm/post
[6] /g/h390-vm/editsub/4526575
[7] mailto:[email protected]
[8] /g/h390-vm/leave/11166232/4526575/1317415517/xyzzy
|
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:
? 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???
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
|
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
|
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
|
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
|
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
|
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
|
搁别苍é, ? 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
?
?
|
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
|
