¿ªÔÆÌåÓý

  1. H390-Vm
  2. Messages
Expanded Topics Messages Polls
Date
Re: No VM IPL with V1.R1.1 #VMCE

 

On Fri, Dec 31, 2021 at 04:30 PM, Fish Fish wrote:
Eh? Since when are official releases of Hercules v4 only beta releases? What constitutes an "official" release?
Fish,

It probably has something to do with the flow, or the lack thereof, of SDL Hercules V4 into various Linux distributions, such as Arch, or Fedora, or even Ubuntu. I'm not saying a person can not acquire and install it on these distros. I have, and so have others, but you can't just issue the distribution's install command, and get V4.? For instance, for Fedora, this is what I see available, for all hercules.

[xmas@reindeer ~]$ dnf list *hercules*
Last metadata expiration check: 0:00:06 ago on Fri 31 Dec 2021 04:49:05 PM CST.
Installed Packages
hercules.x86_64?????????????????????? 3.13-8.fc34??????????????????????? @fedora
[xmas@reindeer ~]$ cat /etc/fedora-release
Fedora release 34 (Thirty Four)
[xmas@reindeer ~]$ dnf info hercules
Last metadata expiration check: 0:02:21 ago on Fri 31 Dec 2021 04:43:48 PM CST.
Installed Packages
Name???????? : hercules
Version????? : 3.13
Release????? : 8.fc34
Architecture : x86_64
Size???????? : 6.8 M
Source?????? : hercules-3.13-8.fc34.src.rpm
Repository?? : @System
From repo??? : fedora
Summary????? : Hercules S/370, ESA/390, and z/Architecture emulator
URL????????? : http://www.hercules-390.eu/
License????? : QPL
Description? : Hercules is an emulator for the IBM System/370, ESA/390, and
???????????? : z/Architecture series of mainframe computers. It is capable of
???????????? : running any IBM operating system and applications that a real
???????????? : system will run, as long as the hardware needed is emulated.
???????????? : Hercules can emulate FBA and CKD DASD, tape, printer, card
???????????? : reader, card punch, channel-to-channel adapter, LCS Ethernet, and
???????????? : printer-keyboard, 3270 terminal, and 3287 printer devices.

[xmas@reindeer ~]$

?... Mark S.
Re: No VM IPL with V1.R1.1 #VMCE

 

Joe Monk wrote:
Olaf wrote:
I don't know why maintainers of packages are so bad at
updating Hercules to version 4.
Because OFFICIALLY, there is no released version of Hercules
version 4. ALL versions of hercules version 4 are beta only.
The package maintainers are correct not to update until there
is an OFFICIAL release of hercules v4.
Eh? Since when are official releases of Hercules v4 only beta releases? What constitutes an "official" release?

--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...
Re: No VM IPL with V1.R1.1 #VMCE

 

"I don't know why maintainers of packages are so bad at updating Hercules
to version 4."

Because OFFICIALLY, there is no released version of Hercules version 4.? ALL ?versions of hercules version 4 are beta only. The package maintainers are correct not to update until there is an OFFICIAL release of hercules v4.

Joe

On Fri, Dec 31, 2021 at 11:41 AM Rhialto <rhialto@...> wrote:
On Fri 31 Dec 2021 at 11:31:46 -0500, gdblodgett wrote:
> Ant,I'm not sure how many of the maintainers are using version 4, but
> many maintainers and users are still using version 3 for the same
> reason as you are, it is easy to install.Due to my current lack of
> time, I've been waiting for a concise and nearly bullet proof set of
> installation docs/procedures for Linux before I attempt an install of
> version 4.Gary

I don't know why maintainers of packages are so bad at updating Hercules
to version 4.

For macports, I added a comment, urging to do an update, to
. Maybe a separate ticket is
required to get some attention there.

Homebrew (which I don't use) is no better apparently.

Pkgsrc on MacOS does carry Hercules 4 (SDL) (thanks to yours truely).
See .
For version 4.3, I personally verified that it builds and runs on my
MacBook, but since it is for $WORK, I can't really use it to keep
checking.

Building Hercules from pkgsrc is easy (just follow the pkgsrc bootstrap
procedure at and do "make install" in
pkgsrc/emulators/hercules4sdl). But it does take a while, since it will
build all dependencies from source in pkgsrc context, even those you
might have already. And if you just want Hercules, that will also take
relatively much space for just the one package.

-Olaf.
--
___ "Buying carbon credits is a bit like a serial killer paying someone else to
\X/? have kids to make his activity cost neutral." -The BOFH? ? falu.nl@rhialto
Re: No VM IPL with V1.R1.1 #VMCE

 

On Fri 31 Dec 2021 at 11:31:46 -0500, gdblodgett wrote:
Ant,I'm not sure how many of the maintainers are using version 4, but
many maintainers and users are still using version 3 for the same
reason as you are, it is easy to install.Due to my current lack of
time, I've been waiting for a concise and nearly bullet proof set of
installation docs/procedures for Linux before I attempt an install of
version 4.Gary
I don't know why maintainers of packages are so bad at updating Hercules
to version 4.

For macports, I added a comment, urging to do an update, to
. Maybe a separate ticket is
required to get some attention there.

Homebrew (which I don't use) is no better apparently.

Pkgsrc on MacOS does carry Hercules 4 (SDL) (thanks to yours truely).
See .
For version 4.3, I personally verified that it builds and runs on my
MacBook, but since it is for $WORK, I can't really use it to keep
checking.

Building Hercules from pkgsrc is easy (just follow the pkgsrc bootstrap
procedure at and do "make install" in
pkgsrc/emulators/hercules4sdl). But it does take a while, since it will
build all dependencies from source in pkgsrc context, even those you
might have already. And if you just want Hercules, that will also take
relatively much space for just the one package.

-Olaf.
--
___ "Buying carbon credits is a bit like a serial killer paying someone else to
\X/ have kids to make his activity cost neutral." -The BOFH falu.nl@rhialto
Re: No VM IPL with V1.R1.1 #VMCE

 

¿ªÔÆÌåÓý

Ant,

I'm not sure how many of the maintainers are using version 4, but many maintainers and users are still using version 3 for the same reason as you are, it is easy to install.

Due to my current lack of time, I've been waiting for a concise and nearly bullet proof set of installation docs/procedures for Linux before I attempt an install of version 4.

Gary



Sent from whatever device I am using.


-------- Original message --------
From: Anthony Smith <anthony@...>
Date: 12/31/21 11:19 AM (GMT-05:00)
Subject: Re: [h390-vm] No VM IPL with V1.R1.1 #VMCE

I am always keen to improve things through feedback, but am I to take it that R1.V1.1 is only aimed at, and tested with Hercules 4.x ?
On Mac installing Hercules 3.x is super easy, so that is the route I tooken.

Re: No VM IPL with V1.R1.1 #VMCE

 

I am always keen to improve things through feedback, but am I to take it that R1.V1.1 is only aimed at, and tested with Hercules 4.x ?
On Mac installing Hercules 3.x is super easy, so that is the route I tooken.
Re: No VM IPL with V1.R1.1 #VMCE

 

¿ªÔÆÌåÓý

Correct.? The configuration name changed during the transition from Hercules 3.x and the newer SDL Hercules 4.x version.

I use the Meld diff utility to see the changes from one release of VM to another. For windows, try Winmerge instead.

Gary



Sent from whatever device I am using.


-------- Original message --------
From: Anthony Smith <anthony@...>
Date: 12/31/21 10:52 AM (GMT-05:00)
Subject: Re: [h390-vm] No VM IPL with V1.R1.1 #VMCE

Excellent. All appears to be resolved. I will better understand these options now. I take it this is a known issue which I didn't stumble across?

A 'game' written in REXX in 1983

 

Since I discovered Hercules two months ago I've been working on making a game I wrote in REXX for VM/CMS in 1983 working again. 'Game' is maybe the wrong term - it's more of a puzzle that you solve by writing software for a 'virtual computer'.?

If you're at all interested see??where there's a history of the game as well as a downloadable VMARC file so you can run it yourself.

Happy New Year and thanks to all who helped me get it off the ground - it's not easy understanding a large program you wrote 40 years ago!
Re: No VM IPL with V1.R1.1 #VMCE

 

Excellent. All appears to be resolved. I will better understand these options now. I take it this is a known issue which I didn't stumble across?
Re: No VM IPL with V1.R1.1 #VMCE

 

¿ªÔÆÌåÓý

Or install a supported Hercules. Version 3.xx now appears to be unsupported.

?

Dave

G4UGM

?

From: [email protected] <[email protected]> On Behalf Of Bob Bolch
Sent: 31 December 2021 14:24
To: [email protected]
Subject: Re: [h390-vm] No VM IPL with V1.R1.1 #VMCE

?

I reproduced the symptoms. Change ARCHLVL in the configuration file (vm370ce.conf)

to ARCHMODE.

?

Bob Bolch

?

On Fri, Dec 31, 2021 at 8:45 AM Anthony Smith <anthony@...> wrote:

I can post a log of a successful run as well if useful for comparison, but it basically contains VM IPL, Operator login, autolog1 login etc.

Re: No VM IPL with V1.R1.1 #VMCE

 

I reproduced the symptoms. Change ARCHLVL in the configuration file (vm370ce.conf)
to ARCHMODE.

Bob Bolch

On Fri, Dec 31, 2021 at 8:45 AM Anthony Smith <anthony@...> wrote:
I can post a log of a successful run as well if useful for comparison, but it basically contains VM IPL, Operator login, autolog1 login etc.

Re: No VM IPL with V1.R1.1 #VMCE

 

I can post a log of a successful run as well if useful for comparison, but it basically contains VM IPL, Operator login, autolog1 login etc.
Re: No VM IPL with V1.R1.1 #VMCE

  

13:40:18 Hercules Version 3.13
13:40:18 (c)Copyright 1999-2015 by Roger Bowler, Jan Jaeger, and others
13:40:18 Built on Dec 28 2021 at 23:35:26
13:40:18 Build information:
13:40:18   Modes: S/370 ESA/390 z/Arch
13:40:18   Max CPU Engines: 8
13:40:18   Using setreuid() for setting privileges
13:40:18   Dynamic loading support
13:40:18   Using shared libraries
13:40:18   HTTP Server support
13:40:18   Regular Expressions support
13:40:18   Automatic Operator support
13:40:18   Machine dependent assists: cmpxchg1 cmpxchg4 cmpxchg8
13:40:18 Running on AnthonyithsiMac Darwin-17.7.0.Darwin Kernel Version 17.7.0: Fri Oct 30 13:34:27 x86_64 MP=2
13:40:18 HHCHD018I Loadable module directory is /usr/local/Cellar/hercules/3.13/lib/hercules
13:40:18 Crypto module loaded (c) Copyright Bernard van der Helm, 2003-2010
13:40:18   Active: Message Security Assist
13:40:18           Message Security Assist Extension 1
13:40:18           Message Security Assist Extension 2
13:40:18           Message Security Assist Extension 3
13:40:18           Message Security Assist Extension 4
13:40:18 HHCCF008E Error in vm370ce.conf line 19: Syntax error: ARCHLVL
13:40:18 HHCCF051W Error in vm370ce.conf line 37: Invalid ECPSVM keyword : DISABLE. NO Assumed
13:40:18 HHCCF065I Hercules: tid=7FFF94848380, pid=46352, pgid=46344, priority=8
13:40:18 HHCTE001I Console connection thread started: tid=70000F8B8000, pid=46352
13:40:18 HHCTE003I Waiting for console connection on port 3270
13:40:18 HHCDA020I disks/gccbrx.cckd cyls=555 heads=30 tracks=16650 trklen=19456
13:40:18 HHCDA004I opening disks/vm50-1.cckd readonly
13:40:18 HHCDA020I disks/vm50-1.cckd cyls=555 heads=30 tracks=16650 trklen=19456
13:40:18 HHCDA004I opening disks/vm50-2.cckd readonly
13:40:18 HHCDA020I disks/vm50-2.cckd cyls=555 heads=30 tracks=16650 trklen=19456
13:40:18 HHCDA004I opening disks/vm50-3.cckd readonly
13:40:18 HHCDA020I disks/vm50-3.cckd cyls=555 heads=30 tracks=16650 trklen=19456
13:40:18 HHCDA004I opening disks/vm50-4.cckd readonly
13:40:18 HHCDA020I disks/vm50-4.cckd cyls=555 heads=30 tracks=16650 trklen=19456
13:40:18 HHCDA004I opening disks/vm50-5.cckd readonly
13:40:18 HHCDA020I disks/vm50-5.cckd cyls=555 heads=30 tracks=16650 trklen=19456
13:40:18 HHCDA004I opening disks/vm50-6.cckd readonly
13:40:18 HHCDA020I disks/vm50-6.cckd cyls=555 heads=30 tracks=16650 trklen=19456
13:40:18 HHCDA004I opening disks/vm50-7.cckd readonly
13:40:18 HHCDA020I disks/vm50-7.cckd cyls=555 heads=30 tracks=16650 trklen=19456
13:40:18 HHCDA004I opening disks/vm50-8.cckd readonly
13:40:18 HHCDA020I disks/vm50-8.cckd cyls=555 heads=30 tracks=16650 trklen=19456
13:40:18 HHCDA004I opening disks/vm50u0.cckd readonly
13:40:18 HHCDA020I disks/vm50u0.cckd cyls=555 heads=30 tracks=16650 trklen=19456
13:40:18 HHCDA004I opening disks/vm50u1.cckd readonly
13:40:18 HHCDA020I disks/vm50u1.cckd cyls=555 heads=30 tracks=16650 trklen=19456
13:40:18 HHCDA004I opening disks/vm14-0.cckd readonly
13:40:18 HHCDA020I disks/vm14-0.cckd cyls=203 heads=20 tracks=4060 trklen=7680
13:40:18 HHCDA004I opening disks/vm14-1.cckd readonly
13:40:18 HHCDA020I disks/vm14-1.cckd cyls=203 heads=20 tracks=4060 trklen=7680
13:40:18 HHCDA004I opening disks/vm14-2.cckd readonly
13:40:18 HHCDA020I disks/vm14-2.cckd cyls=203 heads=20 tracks=4060 trklen=7680
13:40:18 HHCDA004I opening disks/vm14-3.cckd readonly
13:40:18 HHCDA020I disks/vm14-3.cckd cyls=203 heads=20 tracks=4060 trklen=7680
13:40:18 HHCTT001W Timer thread set priority -20 failed: Permission denied
13:40:18 HHCTT002I Timer thread started: tid=70000FABE000, pid=46352, priority=8
13:40:18 HHCCP001W CPU0000 thread set priority 0 failed: Permission denied
13:40:18 HHCCP002I CPU0000 thread started: tid=70000F9BB000, pid=46352, priority=8
13:40:18 HHCCP003I CPU0000 architecture mode ESA/390
13:40:18 HHCPN001I Control panel thread started: tid=7FFF94848380, pid=46352
13:40:18 HHCAO001I Hercules Automatic Operator thread started;
13:40:18           tid=70000FDC7000, pri=8, pid=46352
13:40:18 HHCPN008I Script file processing started using file "hercules.rc"
13:40:18 * Hercules runs the commands in this file upon startup.
13:40:18 * IPL VM/370, which resides on device 6A1.
13:40:18 HHCPN011I Pausing SCRIPT file processing for 2 seconds...
13:40:20 HHCPN012I Resuming SCRIPT file processing...
13:40:20 ipl 6A1
13:40:20 * Enable any attached devices.
13:40:20 HHCPN011I Pausing SCRIPT file processing for 4 seconds...
13:40:20 HHCCP011I CPU0000: Disabled wait state
13:40:20           PSW=000A0000 00000017
13:40:24 HHCPN012I Resuming SCRIPT file processing...
13:40:24 /(0009) enable all
13:40:24 HHCPN013I EOF reached on SCRIPT file. Processing complete.
13:40:48 suspend
13:40:48 HHCIN900I Begin Hercules shutdown
13:40:48 HHCIN901I Releasing configuration
13:40:48 HHCAO002I Hercules Automatic Operator thread ended
13:40:48 HHCCP008I CPU0000 thread ended: tid=70000F9BB000, pid=46352
13:40:48 HHCTT003I Timer thread ended
13:40:48 HHCCF047I Subchannel 0:0000 detached
13:40:48 HHCCF047I Subchannel 0:0001 detached
13:40:48 HHCCF047I Subchannel 0:0002 detached
13:40:48 HHCCF047I Subchannel 0:0003 detached
13:40:48 HHCCF047I Subchannel 0:0004 detached
13:40:48 HHCCF047I Subchannel 0:0005 detached
13:40:48 HHCCF047I Subchannel 0:0006 detached
13:40:48 HHCCF047I Subchannel 0:0007 detached
13:40:48 HHCCF047I Subchannel 0:0008 detached
13:40:48 HHCCF047I Subchannel 0:0009 detached
13:40:48 HHCCF047I Subchannel 0:000A detached
13:40:48 HHCCF047I Subchannel 0:000B detached
13:40:48 HHCCF047I Subchannel 0:000C detached
13:40:48 HHCCF047I Subchannel 0:000D detached
13:40:48 HHCCF047I Subchannel 0:000E detached
13:40:48 HHCCF047I Subchannel 0:000F detached
13:40:48 HHCCF047I Subchannel 0:0010 detached
13:40:48 HHCCF047I Subchannel 0:0011 detached
13:40:48 HHCCF047I Subchannel 0:0012 detached
13:40:48 HHCCF047I Subchannel 0:0013 detached
13:40:48 HHCCF047I Subchannel 0:0014 detached
13:40:48 HHCCF047I Subchannel 0:0015 detached
13:40:48 HHCCF047I Subchannel 0:0016 detached
13:40:48 HHCCF047I Subchannel 0:0017 detached
13:40:48 HHCCF047I Subchannel 0:0018 detached
13:40:48 HHCCF047I Subchannel 0:0019 detached
13:40:48 HHCCF047I Subchannel 0:001A detached
13:40:48 HHCCF047I Subchannel 0:001B detached
13:40:48 HHCCF047I Subchannel 0:001C detached
13:40:48 HHCCF047I Subchannel 0:001D detached
13:40:48 HHCCF047I Subchannel 0:001E detached
13:40:48 HHCCF047I Subchannel 0:001F detached
13:40:48 HHCCF047I Subchannel 0:0020 detached
13:40:48 HHCCF047I Subchannel 0:0021 detached
13:40:48 HHCCF047I Subchannel 0:0022 detached
13:40:48 HHCCF047I Subchannel 0:0023 detached
13:40:48 HHCCF047I Subchannel 0:0024 detached
13:40:48 HHCCF047I Subchannel 0:0025 detached
13:40:48 HHCCF047I Subchannel 0:0026 detached
13:40:48 HHCCF047I Subchannel 0:0027 detached
13:40:48 HHCCF047I Subchannel 0:0028 detached
13:40:48 HHCCF047I Subchannel 0:0029 detached
13:40:48 HHCCF047I Subchannel 0:002A detached
13:40:48 HHCCF047I Subchannel 0:002B detached
13:40:48 HHCCF047I Subchannel 0:002C detached
13:40:48 HHCCF047I Subchannel 0:002D detached
13:40:48 HHCCF047I Subchannel 0:002E detached
13:40:48 HHCCF047I Subchannel 0:002F detached
13:40:48 HHCCF047I Subchannel 0:0030 detached
13:40:48 HHCCF047I Subchannel 0:0031 detached
13:40:48 HHCCF047I Subchannel 0:0032 detached
13:40:48 HHCCF047I Subchannel 0:0033 detached
13:40:48 HHCCF047I Subchannel 0:0034 detached
13:40:48 HHCCF047I Subchannel 0:0035 detached
13:40:48 HHCCF047I Subchannel 0:0036 detached
13:40:48 HHCCF047I Subchannel 0:0037 detached
13:40:48 HHCCF047I Subchannel 0:0038 detached
13:40:48 HHCCF047I Subchannel 0:0039 detached
13:40:48 HHCCF047I Subchannel 0:003A detached
13:40:48 HHCCF047I Subchannel 0:003B detached
13:40:48 HHCCF047I Subchannel 0:003C detached
13:40:48 HHCCF047I Subchannel 0:003D detached
13:40:48 HHCCF047I Subchannel 0:003E detached
13:40:48 HHCCF047I Subchannel 0:003F detached
13:40:48 HHCCF047I Subchannel 0:0040 detached
13:40:48 HHCCF047I Subchannel 0:0041 detached
13:40:48 HHCCF047I Subchannel 0:0042 detached
13:40:48 HHCCF047I Subchannel 0:0043 detached
13:40:48 HHCCF047I Subchannel 0:0044 detached
13:40:48 HHCCF047I Subchannel 0:0045 detached
13:40:48 HHCCF047I Subchannel 0:0046 detached
13:40:48 HHCCF047I Subchannel 0:0047 detached
13:40:48 HHCCF047I Subchannel 0:0048 detached
13:40:48 HHCCF047I Subchannel 0:0049 detached
13:40:48 HHCCF047I Subchannel 0:004A detached
13:40:48 HHCCF047I Subchannel 0:004B detached
13:40:48 HHCCF047I Subchannel 0:004C detached
13:40:48 HHCCF047I Subchannel 0:004D detached
13:40:48 HHCCF047I Subchannel 0:004E detached
13:40:48 HHCTE004I Console connection thread terminated
13:40:48 HHCCF047I Subchannel 0:004F detached
13:40:48 HHCCF047I Subchannel 0:0050 detached
13:40:48 HHCCF047I Subchannel 0:0051 detached
13:40:48 HHCCF047I Subchannel 0:0052 detached
13:40:48 HHCCF047I Subchannel 0:0053 detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]   12572324   0%    0          0       0       0       0        0
13:40:48 HHCCD215I disks/gccbrx.cckd
13:40:48 HHCCD216I [0]   12572324   0%    0 rw       0       0       0
13:40:48 HHCCF047I Subchannel 0:0054 detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]   25227318   3%   55          1       0       1       0        1
13:40:48 HHCCD215I disks/vm50-1.cckd
13:40:48 HHCCD216I [0]   25226030   3%   55 ro       1       0       1
13:40:48 HHCCD217I disks/shadows/vm50-1_*.shadow
13:40:48 HHCCD218I [1]       1288   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:0055 detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]   19515205   5%    7          0       0       0       0        0
13:40:48 HHCCD215I disks/vm50-2.cckd
13:40:48 HHCCD216I [0]   19513917   5%    7 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm50-2_*.shadow
13:40:48 HHCCD218I [1]       1288   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:0056 detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]   14897992  10%   15          0       0       0       0        0
13:40:48 HHCCD215I disks/vm50-3.cckd
13:40:48 HHCCD216I [0]   14896704  10%   15 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm50-3_*.shadow
13:40:48 HHCCD218I [1]       1288   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:0057 detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]   26835237   4%  116          0       0       0       0        0
13:40:48 HHCCD215I disks/vm50-4.cckd
13:40:48 HHCCD216I [0]   26833949   4%  116 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm50-4_*.shadow
13:40:48 HHCCD218I [1]       1288   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:0058 detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]   31601486   0%    0          0       0       0       0        0
13:40:48 HHCCD215I disks/vm50-5.cckd
13:40:48 HHCCD216I [0]   31600198   0%    0 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm50-5_*.shadow
13:40:48 HHCCD218I [1]       1288   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:0059 detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]    6913943   0%    0          0       0       0       0        0
13:40:48 HHCCD215I disks/vm50-6.cckd
13:40:48 HHCCD216I [0]    6912655   0%    0 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm50-6_*.shadow
13:40:48 HHCCD218I [1]       1288   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:005A detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]   25447630   0%    0          0       0       0       0        0
13:40:48 HHCCD215I disks/vm50-7.cckd
13:40:48 HHCCD216I [0]   25446342   0%    0 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm50-7_*.shadow
13:40:48 HHCCD218I [1]       1288   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:005B detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]   21611671   0%    0          0       0       0       0        0
13:40:48 HHCCD215I disks/vm50-8.cckd
13:40:48 HHCCD216I [0]   21610383   0%    0 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm50-8_*.shadow
13:40:48 HHCCD218I [1]       1288   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:005C detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]    8042777   0%    1          0       0       0       0        0
13:40:48 HHCCD215I disks/vm50u0.cckd
13:40:48 HHCCD216I [0]    8041489   0%    1 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm50u0_*.shadow
13:40:48 HHCCD218I [1]       1288   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:005D detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]       8431   0%    0          0       0       0       0        0
13:40:48 HHCCD215I disks/vm50u1.cckd
13:40:48 HHCCD216I [0]       7143   0%    0 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm50u1_*.shadow
13:40:48 HHCCD218I [1]       1288   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:005E detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]     262525   0%    2          0       0       0       0        0
13:40:48 HHCCD215I disks/vm14-0.cckd
13:40:48 HHCCD216I [0]     261437   0%    2 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm14-0_*.shadow
13:40:48 HHCCD218I [1]       1088   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:005F detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]    3005590   0%    0          0       0       0       0        0
13:40:48 HHCCD215I disks/vm14-1.cckd
13:40:48 HHCCD216I [0]    3004502   0%    0 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm14-1_*.shadow
13:40:48 HHCCD218I [1]       1088   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:0060 detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]    7312383   0%    1          0       0       0       0        0
13:40:48 HHCCD215I disks/vm14-2.cckd
13:40:48 HHCCD216I [0]    7311295   0%    1 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm14-2_*.shadow
13:40:48 HHCCD218I [1]       1088   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:0061 detached
13:40:48 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
13:40:48 HHCCD212I --------------------------------------------------------------------
13:40:48 HHCCD213I [*]       4566   0%    0          0       0       0       0        0
13:40:48 HHCCD215I disks/vm14-3.cckd
13:40:48 HHCCD216I [0]       3478   0%    0 ro       0       0       0
13:40:48 HHCCD217I disks/shadows/vm14-3_*.shadow
13:40:48 HHCCD218I [1]       1088   0%    0          0       0       0
13:40:48 HHCCF047I Subchannel 0:0062 detached
13:40:48 HHCIN902I Configuration release complete
13:40:48 HHCIN903I Calling termination routines
13:40:48 HHCHD900I Begin shutdown sequence
13:40:48 HHCHD901I Calling panel_cleanup
13:40:48 HHCHD902I panel_cleanup complete
13:40:48 HHCHD901I Calling console_shutdown
13:40:48 HHCHD902I console_shutdown complete
13:40:48 HHCHD901I Calling hdl_term
13:40:48 HHCHD950I Begin HDL termination sequence
13:40:48 HHCHD951I Calling module *Hercules cleanup routine
13:40:48 HHCHD952I Module *Hercules cleanup complete
13:40:48 HHCHD959I HDL Termination sequence complete
13:40:48 HHCHD902I hdl_term complete
13:40:48 HHCHD901I Calling logger_term
13:40:48 HHCLG014I logger thread terminating
13:40:48 HHCLG014I logger thread terminating

Re: No VM IPL with V1.R1.1 #VMCE

 

Could you show us what you do get in the?log? The complete log, please. We can afford the space. :-)


On Fri, Dec 31, 2021 at 6:07 AM Anthony Smith <anthony@...> wrote:
I have Hercules 3.13
Running VM 6 pack vm370sixpack1_3 - All is good

Running V1.R1.1 using the included vm370ce.sh - I see the IPL 6A1 but none of the other VM messages. It appears VM does not IPL. The log doesn't offer any clues.
I would appreciate any pointers.

Ant



--
Jay Maynard
No VM IPL with V1.R1.1 #VMCE

 

I have Hercules 3.13
Running VM 6 pack vm370sixpack1_3 - All is good

Running V1.R1.1 using the included vm370ce.sh - I see the IPL 6A1 but none of the other VM messages. It appears VM does not IPL. The log doesn't offer any clues.
I would appreciate any pointers.

Ant
ASM3705

 

Has anyone found a working copy of the assembler for 3705 running CMS? I used to do 3705 programming using VM/CMS and might still have a tape of source code kicking around.

Currently, I¡¯m running VM Sixpack V3.

Michael
Re: IFOX00/ASSEMBLER Question #VMCE

 

On Tue, Dec 28, 2021 at 10:35:32PM -0000, Dave Wade wrote:
-----Original Message-----

I'm confused, and could use some clarification.
The VM Assembler is the Assembler XF and the load modules are identical to the MVS ones. However, CMS doesn't have any JCL so it¡¯s a pain typing in a load of FILEDEF commands for all the work files.
To avoid this IBM provides a CMS Interface, DMSASM which parses the CMS command line and sets up all the FILEDEFS and converts the CMS argument strings into an OS PAFRMLIST ready to run the ASSEMBLER.
So its part of CMS rather than the ASEMBLER and mark was having issues with it not working as documented. I suspect over the years no one has tried to do what Mark wants to do even though the docs imply its possible.
(it says you can issue a FILEDEF for the source file, but ASSEMBLE aka DMSASM always wants a file name making the FILEDEF pointless....)


I am not. I am using ASSEMBLER to refer to the Assembler XF and ASSIST to refer to ASSIST.
You need to use the normal ASSEMBLER to fix ASSIST so we need to talk about both.

In fact one of the things that¡¯s missing from ASSIST appears to be the equivalent CMS front end.
At present you have to issue a load of FILEDEFS and run it in batch mode.....
Thank you, Dave.

That joins all of the scraps that I have been reading ( skimming? )
here.


My experience with these was in the MTS environment at the University of
Alberta. Quite a different command line ( and user interface ).



Brian
Re: IFOX00/ASSEMBLER Question #VMCE

 

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Brian
McCullough
Sent: 28 December 2021 21:42
To: [email protected]
Subject: Re: [h390-vm] IFOX00/ASSEMBLER Question #VMCE

On Tue, Dec 28, 2021 at 09:32:12PM -0000, Dave Wade wrote:
Mark,
Dave and all,


Looking at the source for DMSASM I don¡¯t think it will be hard to tweak.
The code is pretty clear, unlike the Assembler itself.

I'm confused, and could use some clarification.
The VM Assembler is the Assembler XF and the load modules are identical to the MVS ones. However, CMS doesn't have any JCL so it¡¯s a pain typing in a load of FILEDEF commands for all the work files.
To avoid this IBM provides a CMS Interface, DMSASM which parses the CMS command line and sets up all the FILEDEFS and converts the CMS argument strings into an OS PAFRMLIST ready to run the ASSEMBLER.
So its part of CMS rather than the ASEMBLER and mark was having issues with it not working as documented. I suspect over the years no one has tried to do what Mark wants to do even though the docs imply its possible.
(it says you can issue a FILEDEF for the source file, but ASSEMBLE aka DMSASM always wants a file name making the FILEDEF pointless....)


I am also looking forward to see ASSIST running properly. I feel its pretty
unusable as it is¡­..

As I remember, back in the dim ages long past, the main IBM assembler is
very different from ASSIST, from Penn State, which is a teaching, load and go
assembler, unless my memory is very wrong.

Because of that, unless you are using ASSIST to refer to both, I don't see
trying to modify ASSIST to do all of the things that I would expect only from
the other assembler.
I am not. I am using ASSEMBLER to refer to the Assembler XF and ASSIST to refer to ASSIST.
You need to use the normal ASSEMBLER to fix ASSIST so we need to talk about both.

In fact one of the things that¡¯s missing from ASSIST appears to be the equivalent CMS front end.
At present you have to issue a load of FILEDEFS and run it in batch mode.....



Brian
Dave
Re: IFOX00/ASSEMBLER Question #VMCE

 

On Tue, Dec 28, 2021 at 09:32:12PM -0000, Dave Wade wrote:
Mark,
Dave and all,


Looking at the source for DMSASM I don¡¯t think it will be hard to tweak. The code is pretty clear, unlike the Assembler itself.
I'm confused, and could use some clarification.


I am also looking forward to see ASSIST running properly. I feel its pretty unusable as it is¡­..
As I remember, back in the dim ages long past, the main IBM assembler is
very different from ASSIST, from Penn State, which is a teaching, load
and go assembler, unless my memory is very wrong.

Because of that, unless you are using ASSIST to refer to both, I don't
see trying to modify ASSIST to do all of the things that I would expect
only from the other assembler.



Brian
Re: IFOX00/ASSEMBLER Question #VMCE

 

¿ªÔÆÌåÓý

Mark,

I am sorry to hear about your virus encounter. My wife and I both had a bout in the summer and we both hope you recover as well as we have.

?

Looking at the source for DMSASM I don¡¯t think it will be hard to tweak. The code is pretty clear, unlike the Assembler itself.

I am also looking forward to see ASSIST running properly.?? I feel its pretty unusable as it is¡­..

¡­ and while you are looking at it I can plod on with a few more help files.

?

Dave

?

?

From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via groups.io
Sent: 28 December 2021 02:54
To: [email protected]
Subject: Re: [h390-vm] IFOX00/ASSEMBLER Question #VMCE

?

On Wed, Dec 22, 2021 at 05:05 AM, Dave Wade wrote:

Did you get anywhere with fixing this, or create a work around?

Because the CMS interface routine, DMSASM, does not support this, per Bob Bolch, which I anticipated from the error I was getting; I took the 'futuristic VM/SP REXX EXEC' that I had used years ago, and modified it to pull each member in turn, assemble, and erase the pulled member) and go on to the next. This works just fine.

The nice thing about the MACLIB in this case, is it keeps related assembler routes together. Bad thing, you have to extract to assemble something. I have added a To-Do and see if I can wrangle DMSASM into accepting a member as input to ASSEMBLE.

I was on my way to having the ASSIST package deliverable in time for Christmas and then Monday last, with one COVID booster, and Tuesday 3 more antiviral vaccines, I spent time in the ER on Wednesday, and then I was unable to do much of anything until this evening, besides sleep, ache, sweat, etc. I've since patched and rebooted my server, starting KVMs, IPLing VMs, MVSs, processing e-mails, such as this one, with the hopes of getting ASSIST available by the end of 2021.

Merry Christmas, Amazing Epiphany, Happy Chanukah, Joyous Kwanzaa, Bodhi Day, Pancha Ganapati or one of the myriad other celebrations that take place this time of year ...

?... Mark S.

2721 - 2740 of 6534