Keyboard Shortcuts
Likes
- H390-Vm
- Messages
Search
This group is for all folks running the original IBM VM/370 Release 6 operating system (or later (e.g. VMTCE (Community Edition)) on Hercules. Like the other early IBM operating systems this version has always been in the public domain and so can be freely distributed. The base version as supplied by IBM is lacking in many facilities. IBM solved this by providing additional extension products which were licensed and so are not available. There are however many user enhancements available which can be installed. In addition, in order to get users up and running quickly updated "releases" of VM/370 included the most popular updates are available for download, so novices can start to learn VM without having to delve into the system internals. It is intended that this wiki will provide information on the base release and these updates.
The available versions are here :-
?
?
Re: Accessing the Hercules Console from a web Browser
Edward lott wrote:
OK adding the HTTPPORT 8081 line works. In reading theAFAIK, there is no default. The port number must be specified on the HTTPPORT configuration file statement itself. And as Dave pointed out, that particular statement was commented out. Thus, the Hercules HTTP Server was never started. It is the existence of the HTTPPORT statement in your configuration file that triggers the Hercules HTTP Server to start. Without it, the server will never start. and 2.) the HTTP PORT ${HTTPPORT:=8081} line wasThat's a Hercules v4.x Hyperion configuration file statement, *not* a Hercules v3.x configuration file statement. Originally, Hercules supported two "http" statements: HTTPPORT and HTTPROOT: * and, as just explained, it is the existence of the HTTPPORT statement which triggers the server to start. Starting with Hercules 4.0 however, both statements were deprecated and replaced with the "HTTP" statement instead: * Now, with Hercules 4.x, you specify all HTTP Server configuration values via the "HTTP" statement. One specifying the server's root directory ("HTTP ROOT directory") and the other specifying the port number the server should listen for connections on ("HTTP PORT nnnn ..."). But even then (even with *both* statements specified), with Hercules 4.x, the server will not automatically start. To start the Hercules HTTP Server, with Hercules 4.x, you have to *explicitly* specify that you *want* it to be started, via either the "HTTP START" configuration file statement, or the "http start" command: * So in summary, the "HTTPPORT" statement is a Hercules 3.x statement, whereas the "HTTP PORT" statement is a Hercules 4.x statement, which requires a separate "http start" command (or configuration file statement). Hope that helps! I learn something new every day.Indeed. The day I myself stop learning new things is the day I've died and gone to my grave. :) -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@... |
Re: Accessing the Hercules Console from a web Browser
开云体育Dave: ??? OK adding the HTTPPORT 8081 line works. In reading the configuration file I thought that 1.) port 8081 was the default and 2.) the HTTP PORT ${HTTPPORT:=8081} line was what enabled it. I learn something new every day. Regards: Ed. # HTTP Configuration for Hercules V4.x Ed.. ================================================ On 8/14/2022 2:02 PM, Dave Wade wrote:
|
Re: Accessing the Hercules Console from a web Browser
开云体育Ed, That’s disabled by default. You need to remove the “#” from the config line ? ? #HTTPPORT?????? 8081 ? Dave ? From: [email protected] <[email protected]> On Behalf Of Edward lott
Sent: 14 August 2022 19:15 To: [email protected] Subject: Re: [h390-vm] Accessing the Hercules Console from a web Browser ? I am running Hercules R3.13 and VMCE-V1.1.2 on a Windows 11 computer (i.p. address 192.168.15.61) and would like to access the Hercules Console from my Web Browser (firefox) on that machine. I enter in the browser and the connection simply times out. I have entered the netstat -a command (see below) and it does not appear that anything is listening on port 8081. Can anyone give me some insight into what is or isn't happening. Ed. C:\windows\system32>netstat -a |
Re: Accessing the Hercules Console from a web Browser
开云体育I am running Hercules R3.13 and VMCE-V1.1.2 on a Windows 11 computer (i.p. address 192.168.15.61) and would like to access the Hercules Console from my Web Browser (firefox) on that machine. I enter in the browser and the connection simply times out. I have entered the netstat -a command (see below) and it does not appear that anything is listening on port 8081. Can anyone give me some insight into what is or isn't happening. Ed. C:\windows\system32>netstat -a |
Today's the 50th anniversary of the announcement of VM/370 as a product.
The following was posted by Jay Maynard on the Discord Mainframe Enthusiasts channel.
I thought the folks here might enjoy it as well. Jay MaynardToday's the 50th anniversary of the announcement of VM/370 as a product. IBM has a few pages up for the occasion...and @Adam Thornton 's Linux on VM scalability articles are reproduced there, among lots of other good stuff.
Main page: Timeline: History and heritage: ?
?
...haw! The X in XEDIT is for the developer, Xavier de Lamberterie. |
Re: best practise on updates to USER DIRECT
#VMCE
开云体育Thank you Bob.Speedy response that gets me further. Bert Op 2022-07-26 om 13:42 schreef Bob
Bolch:
|
Re: best practise on updates to USER DIRECT
#VMCE
Hi Bert, To verify a USER DIRECT file, issue: DIRECT USER [ DIRECT [ A]] ( EDIT To activate?a USER DIRECT file, omit the EDIT parameter. Issue the DIRECT command from the MAINT ID, It has the correct? MDISK entry to allow disk where the object directory is written. The DIRECT command became DIRECTXA?in later VM versions after VM/370. Bob Bolch On Tue, Jul 26, 2022 at 7:27 AM Bert Lindeman <bert.lindeman@...> wrote:
|
best practise on updates to USER DIRECT
#VMCE
Getting started with VM/370 and would like some help. On a change to the USER DIRECT I used to do:
Step 3 I now use What is the correct command for step 4 and 6. Or is it simply acessing the correct MAINT minidisk? Maybe not, as I used to use directXA. Thank you, Bert |
VM/370 Community Edition Version 1 Release 1.2 is now available
The new release may be downloaded from ?now.
The new features and fixes are described in the readme-vmce-1_1_2.txt document in the downloaded folder. Also in that folder are readme files for the previous VMCE releases, and supplemental documents on how to integrate virtual DOSVS and TK4- MVS operating systems under VM.? I plan to close the fixed issues on the issue web pages at ? As usual, we can discuss new issues on this email forum, but it can be difficult to remember and find these discussions after a few weeks have gone by :-) Please open new issues, so that errors are corrected in future versions. I am proud of the way so many people contribute to our Community Edition.? Bob Bolch? |
Re: VM370CE Version 1 Release 1.2 Release Candidate
On Fri, Jul 15, 2022 at 10:07 PM, Mark A. Stevens wrote:
In the Release Candidate, after you log in to either CMSUSER or MAINT, when you enter:You can not select a CMS, CP, or others command. It does work for EE, EDIT, EXEC, and DEBUG commands. ?... Mark S. |
Re: VM370CE Version 1 Release 1.2 Release Candidate
Hi Mark, The new full screen HELP command functionally replaces the FSHELP command. I will remove the FSHELP command. It had many limitations and could not display all HELP files. Bob On Fri, Jul 15, 2022 at 11:07 PM Mark A. Stevens via <marXtevens=[email protected]> wrote: On Mon, Jul 11, 2022 at 04:24 PM, Bob Bolch wrote: |
Re: VM370CE Version 1 Release 1.2 Release Candidate
On Mon, Jul 11, 2022 at 04:24 PM, Bob Bolch wrote:
In the Release Candidate, after you log in to either CMSUSER or MAINT, when you enter: FSHELP It displays a list of commands, but none of them are found, when the cursor is on a word and you press F1. For instance, for ADSTOP, you get the message: No help found for 'ADSTOP' This does work properly in the current release. Not sure what is wrong, yet. ?... Mark S. |
Re: VM370CE Version 1 Release 1.2 Release Candidate
Hi Mark W.,
It's true that the VMSE MAINT procedures are slightly different than the process described by Melinda and the other document you named. Mark S. pointed out the MAINT MEMO file, where we want to describe this stuff. I made the VMSETUP EXEC to be similar to the VMFSETUP EXEC in the later VM releases which use the SES facility. In a typical customer site, in the 70s, you had IBM supplied base code, IBM fixes, and local customer modifications. In VMCE, you have IBM code, IBM fixes, VMCE modifications, and a 4th level is code modifications added by you. That is really the only difference. I build my own local modifications on the MAINT A work disk, and then copy them to the? 594 (for CP) or 593 (for CMS) when they are finished. To go to a new VMSE release, you can copy the 594 and 593 to the new system (using a virtual tape or VMARC file download and upload). Of course, you may have to rework any local modifications, if VMSE made changes to the same source files. Please send in any specific question that are not answered by MAINT MEMO, and we can update it. Thanks for testing/Bob ? ?? |
Re: VM370CE Version 1 Release 1.2 Release Candidate
On Tue, Jul 12, 2022 at 02:19 PM, Mark Waterbury wrote:
So far, what I do not see or cannot seem to find is a "How To" guide for how to make any local modifications to the VM/CE system, e.g. something along the lines of Linda Varian's "What mother never told you ..." or the WSC orange book "VM Maintenance Simplified" ...You can find information on the MAINT 5E5 mindisk accessed at B: XLIST: * MEMO B?????????????????????????????????????? Lines 1-2/2? XLIST V1.2.5 ? Filename Filetype Fm? Format??? Recs Blocks? Date?????? Time?? Label ? MAINT??? MEMO???? B1? V??? 80??? 490???? 24? 2021-03-03 09:06? MNT5E5 ? RSCS???? MEMO???? B1? F??? 80??? 308???? 31? 2021-11-30 12:56? MNT5E5 ... FSVIEW: MAINT MEMO B1?????????????????? Lines 1-39/490 V80[1-79]? FSVIEW V1.2.5 **** VM/370 Community Edition System Programming Notes Notes on generating the CMS nucleus, the CP nucleus, and the various saved systems and shared segments.? Thanks to Dave Wade, Kevin Leonard, Bob Bolch and Bob O'Hara. **** To establish a VM component service disk search order, issue one of these commands: Component???? Setup command ---------???? ------------- CP??????????? VMSETUP CP CMS?????????? VMSETUP CMS RSCS????????? VMSETUP RSCS ... I Hope This Helps. ... Mark S. |
Re: VM370CE Version 1 Release 1.2 Release Candidate
开云体育Mark, Its simply following IBM convention in version naming. Dave ? ? From: [email protected] <[email protected]> On Behalf Of Mark Waterbury
Sent: 12 July 2022 20:19 To: [email protected] Subject: Re: [h390-vm] VM370CE Version 1 Release 1.2 Release Candidate ? Bob, Dave, et al: |
Re: VM370CE Version 1 Release 1.2 Release Candidate
Bob, Dave, et al:
So far, what I do not see or cannot seem to find is a "How To" guide for how to make any local modifications to the VM/CE system, e.g. something along the lines of Linda Varian's "What mother never told you ..." or the WSC orange book "VM Maintenance Simplified" ... Also, how should I carry forward any local modifications that I have made to my copy of VM/CE V1.R1.1 into the new version? I would also prefer to see a more consistent naming standard or convention for the versions and releases of VM/CE, e.g. rather than "V1.R1.1" I would prefer either "1.1.1" or "V1R1M1" ... so for this new version, either "1.1.2" or "V1R1M2".? ? Thanks in advance. Mark S. Waterbury |
Re: VM370CE Version 1 Release 1.2 Release Candidate
开云体育Hi Bob, I downloaded the zip file for CE 1.2 RC with much eagerness.? I have only checked out the README and found in the Changes section that items 25 & 42 concerning the PASCAL compiler conflict... Looking forward to carving out some time to try it out. Thank you to all of the hard work to the maintainers and contributors. Regards, Gary On 7/11/22 17:24, Bob Bolch wrote:
|
Re: VM370CE Version 1 Release 1.2 Release Candidate
Sorry, the corrected link is: Bob On Mon, Jul 11, 2022 at 5:06 PM Bob Bolch via <Bob=[email protected]> wrote: Thanks to all contributors, I am pleased to post a test version of the third |