[H390-VM] VM/370 installation & startup

[[e-mail] [H390-VM]]

Background: We have recently brought up a 4361 running VM/370 at Living Computers: Museum + Labs, the culmination of several acquisitions over the last 6 years, with the help of the fine folks at Fundamental Software and their FLEXCUB(TM) peripheral emulator. This is a vanilla VM/370 installation.


I last played with Hercules in 2011, when we thought that we were going to restore a 360/40 and bring it up under DOS. (The hardware turned out to be much further gone that we had hoped.) I would like very much to use Hercules to play around with configurations for the 4361 before making changes to the current system. The ultimate plan is to open the system to public access.


The issue: I have installed Hercules 3.12 on a Linux box, along with the 4-pack VM/370 system which I had lying about since 2011. I commented out the DOS portion of the provided hercules.cnf and fired it up in a MobaXterm window. It starts off well, putting up 4 x3270 windows on my Windows 7 desktop and IPLing VM. At this point, the first window should, I believe, be the system console, but I get nothing after the Hercules logo. Modifying the hercules.rc file to start only a single x3270 session does not change this behavior, nor does eliminating the .rc file altogether and connecting with Vista tn3270 or ZOC.


I'm clearly missing something, so I'm soliciting advice from the group.


Thanks,
Rich Alderson


Rich Alderson, Sr. Systems Engineer
Living Computers: Museum + Labs
2245 1st Avenue S
Seattle, WA 98134


http://www.livingcomputers.org/

[[e-mail] [H390-VM]]

---In H390-***@yahoogroups.com, <***@...> wrote :

(snip)

Post by ***@yahoo.com [H390-VM]
I last played with Hercules in 2011, when we thought that we were going to restore
a 360/40 and bring it up under DOS. (The hardware turned out to be much further
gone that we had hoped.) I would like very much to use Hercules to play around
with configurations for the 4361 before making changes to the current system.
The ultimate plan is to open the system to public access.

(snip)

Post by ***@yahoo.com [H390-VM]
At this point, the first window should, I believe, be the system console, but I get
nothing after the Hercules logo.

Last I had VM/370 running, on a P/370 and not Hercules, I had

a 3215 configured as the console and not a 3270.



As far as I know, it can work either way, partly depending
on the I/O configuration.

['Dave Wade' [e-mail] [H390-VM]]

It may be a timing error. When you say it IPLS vm do you see any VM responses in the Hercules window? When you press “escape” what does the devices screen look like?



Dave



From: H390-***@yahoogroups.com [mailto:H390-***@yahoogroups.com]
Sent: 22 June 2017 02:28
To: H390-***@yahoogroups.com
Subject: [H390-VM] VM/370 installation & startup








Background: We have recently brought up a 4361 running VM/370 at Living Computers: Museum + Labs, the culmination of several acquisitions over the last 6 years, with the help of the fine folks at Fundamental Software and their FLEXCUB(TM) peripheral emulator. This is a vanilla VM/370 installation.



I last played with Hercules in 2011, when we thought that we were going to restore a 360/40 and bring it up under DOS. (The hardware turned out to be much further gone that we had hoped.) I would like very much to use Hercules to play around with configurations for the 4361 before making changes to the current system. The ultimate plan is to open the system to public access.



The issue: I have installed Hercules 3.12 on a Linux box, along with the 4-pack VM/370 system which I had lying about since 2011. I commented out the DOS portion of the provided hercules.cnf and fired it up in a MobaXterm window. It starts off well, putting up 4 x3270 windows on my Windows 7 desktop and IPLing VM. At this point, the first window should, I believe, be the system console, but I get nothing after the Hercules logo. Modifying the hercules.rc file to start only a single x3270 session does not change this behavior, nor does eliminating the .rc file altogether and connecting with Vista tn3270 or ZOC.



I'm clearly missing something, so I'm soliciting advice from the group.



Thanks,

Rich Alderson



Rich Alderson, Sr. Systems Engineer

Living Computers: Museum + Labs

2245 1st Avenue S

Seattle, WA 98134



http://www.livingcomputers.org/

[[e-mail] [H390-VM]]

Post by 'Dave Wade' ***@gmail.com [H390-VM]
It may be a timing error. When you say it IPLS vm do you see any VM responses in the Hercules window?
When you press “escape” what does the devices screen look like?

The CPU is stopped. The devices are all assigned as expected.
<pause>
Tried an experiment: Fired up an xterm from the Hercules command> prompt and from there telnetted to
localhost:3270, which got me attached to one of the 3215s configured. No apparent change in the state of
the emulated system.
<pause>
Went thru the user manual again, looking for possible things I might have missed, trying START and G and
a few status commands along the way. No apparent changes.


This is not going to be as useful as I had hoped, apparently.


thanks,
Rich

[Harold Grovesteen [e-mail] [H390-VM]]

Before you give up, why not share with the list your Hercules
configuration file and other files (.rc, bat file, etc.) associated
with your start up process.

This will give everyone the details they need to find the issue.

Typically a 3215 would be accessed via a standard telnet client.  Such
a client will not work with a device configured in Hercules as a 3270.
 You need a TN3270 client for that.

Your Hercules configuration must match the way the VM owned devices are
configured within VM.

It will certainly not be useful if you "throw the baby out with the
bath water" as the expression goes.  After all many Hercules users have
successfully run VM/370 with Hercules.

Harold Grovesteen

Post by 'Dave Wade' ***@gmail.com [H390-VM]

Post by 'Dave Wade' ***@gmail.com [H390-VM]
It may be a timing error. When you say it IPLS vm do you see any VM

responses in the Hercules window?

Post by 'Dave Wade' ***@gmail.com [H390-VM]
When you press “escape” what does the devices screen look like?

The CPU is stopped.  The devices are all assigned as expected.
<pause>
Tried an experiment:  Fired up an xterm from the Hercules command>
prompt and from there telnetted to
localhost:3270, which got me attached to one of the 3215s
configured. 

This on its face makes no sense.  The additional information you could
supply may clarify this statement.

Post by 'Dave Wade' ***@gmail.com [H390-VM]
No apparent change in the state of
the emulated system.
<pause>
Went thru the user manual again, looking for possible things I might
have missed, trying START and G and
a few status commands along the way.  No apparent changes.
This is not going to be as useful as I had hoped, apparently.
thanks,
Rich
 

[Ivan Warren [e-mail] [H390-VM]]

Post by ***@yahoo.com [H390-VM]
The CPU is stopped. The devices are all assigned as expected.

Try...

ipl 123 (at the hercules console)

--Ivan

['Dave Wade' [e-mail] [H390-VM]]

And so what does “IPL 141” do




From: H390-***@yahoogroups.com [mailto:H390-***@yahoogroups.com]
Sent: 22 June 2017 20:44
To: H390-***@yahoogroups.com
Subject: RE: [H390-VM] VM/370 installation & startup

Post by 'Dave Wade' ***@gmail.com [H390-VM]
It may be a timing error. When you say it IPLS vm do you see any VM responses in the Hercules window?
When you press “escape” what does the devices screen look like?

The CPU is stopped. The devices are all assigned as expected.

<pause>

Tried an experiment: Fired up an xterm from the Hercules command> prompt and from there telnetted to

localhost:3270, which got me attached to one of the 3215s configured. No apparent change in the state of

the emulated system.

<pause>

Went thru the user manual again, looking for possible things I might have missed, trying START and G and

a few status commands along the way. No apparent changes.



This is not going to be as useful as I had hoped, apparently.



thanks,

Rich

[[e-mail] [H390-VM]]

Post by ***@yahoo.com [H390-VM]

Post by ***@yahoo.com [H390-VM]
The issue: I have installed Hercules 3.12
on a Linux box, along with the 4-pack
VM/370 system which I had lying about
since 2011

This is not going to be as useful as I had
hoped, apparently.

Any reason you're not using the
VM/370 sixpack?

That's what most people use, and
thus easier to debug.

In addition, if that doesn't work out
of the box in 15 minutes then I
would think it needs to be fixed.

I run the sixpack under Windows
and I only use it for batch operations,
so I personally probably can't
solve the problem.

BFN. Paul.

[Jason Kirby [e-mail] [H390-VM]]

unsubscribe


________________________________
From: H390-***@yahoogroups.com <H390-***@yahoogroups.com> on behalf of ***@yahoo.com.au [H390-VM] <H390-***@yahoogroups.com>
Sent: Friday, June 23, 2017 3:36 AM
To: H390-***@yahoogroups.com
Subject: RE: [H390-VM] VM/370 installation & startup

Post by ***@yahoo.com [H390-VM]

Post by ***@yahoo.com [H390-VM]
The issue: I have installed Hercules 3.12
on a Linux box, along with the 4-pack
VM/370 system which I had lying about
since 2011

This is not going to be as useful as I had
hoped, apparently.

Any reason you're not using the
VM/370 sixpack?

That's what most people use, and
thus easier to debug.

In addition, if that doesn't work out
of the box in 15 minutes then I
would think it needs to be fixed.

I run the sixpack under Windows
and I only use it for batch operations,
so I personally probably can't
solve the problem.

BFN. Paul.

[Guy Sotomayor Jr [e-mail] [H390-VM]]

I believe the issue is that he’s trying to replicate an environment that can be transferred over to the real HW.

I’m in a similar boat in that I’ve just acquired a 4331 with all of the peripherals (3340’s, 1403, 2540, 3420s + control units). Since it has 4 3340’s, I want to use Hercules to gen (or at least practice gen’ing) VM/370 for it as the standard “packs” aren’t going to be usable since they assume a lot more disk space (and different disks).

TTFN - Guy

Post by ***@yahoo.com.au [H390-VM]

Post by ***@yahoo.com [H390-VM]

Post by ***@yahoo.com [H390-VM]
The issue: I have installed Hercules 3.12
on a Linux box, along with the 4-pack
VM/370 system which I had lying about
since 2011

This is not going to be as useful as I had
hoped, apparently.

Any reason you're not using the
VM/370 sixpack?
That's what most people use, and
thus easier to debug.
In addition, if that doesn't work out
of the box in 15 minutes then I
would think it needs to be fixed.
I run the sixpack under Windows
and I only use it for batch operations,
so I personally probably can't
solve the problem.
BFN. Paul.

[Harold Grovesteen [e-mail] [H390-VM]]

The first step in that process is to get a working VM system running.
 Then one can work at building a different environment that matches the
real hardware from the working base.

It does not appear the original poster has gotten that far.

Harold Grovesteen

Post by Guy Sotomayor Jr ***@shiresoft.com [H390-VM]
I believe the issue is that he’s trying to replicate an environment
that can be transferred over to the real HW.
I’m in a similar boat in that I’ve just acquired a 4331 with all of
the peripherals (3340’s, 1403, 2540, 3420s + control units).  Since
it has 4 3340’s, I want to use Hercules to gen (or at least practice
gen’ing) VM/370 for it as the standard “packs” aren’t going to be
usable since they assume a lot more disk space (and different disks).
TTFN - Guy

Post by ***@yahoo.com.au [H390-VM]

Post by ***@yahoo.com [H390-VM]

Post by ***@yahoo.com [H390-VM]
The issue: I have installed Hercules 3.12
on a Linux box, along with the 4-pack
VM/370 system which I had lying about
since 2011

This is not going to be as useful as I had
hoped, apparently.

Any reason you're not using the
VM/370 sixpack?
That's what most people use, and
thus easier to debug.
In addition, if that doesn't work out
of the box in 15 minutes then I
would think it needs to be fixed.
I run the sixpack under Windows
and I only use it for batch operations,
so I personally probably can't
solve the problem.
BFN. Paul.

[Rich Alderson [e-mail] [H390-VM]]

Any reason you're not using the VM/370 sixpack?

No awareness that it existed when I started? I had the 4-pack lying around from when I started playing with Hercules in 2011 (v 3.07 was new), so I started there.
Thanks,Rich

Post by ***@yahoo.com [H390-VM]
The issue: I have installed Hercules 3.12
on a Linux box, along with the 4-pack
VM/370 system which I had lying about
since 2011

This is not going to be as useful as I had
hoped, apparently.

Any reason you're not using the
VM/370 sixpack?

That's what most people use, and
thus easier to debug.

In addition, if that doesn't work out
of the box in 15 minutes then I
would think it needs to be fixed.

I run the sixpack under Windows
and I only use it for batch operations,
so I personally probably can't
solve the problem.

BFN. Paul.
#yiv0650244692 #yiv0650244692 -- #yiv0650244692ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv0650244692 #yiv0650244692ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv0650244692 #yiv0650244692ygrp-mkp #yiv0650244692hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv0650244692 #yiv0650244692ygrp-mkp #yiv0650244692ads {margin-bottom:10px;}#yiv0650244692 #yiv0650244692ygrp-mkp .yiv0650244692ad {padding:0 0;}#yiv0650244692 #yiv0650244692ygrp-mkp .yiv0650244692ad p {margin:0;}#yiv0650244692 #yiv0650244692ygrp-mkp .yiv0650244692ad a {color:#0000ff;text-decoration:none;}#yiv0650244692 #yiv0650244692ygrp-sponsor #yiv0650244692ygrp-lc {font-family:Arial;}#yiv0650244692 #yiv0650244692ygrp-sponsor #yiv0650244692ygrp-lc #yiv0650244692hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv0650244692 #yiv0650244692ygrp-sponsor #yiv0650244692ygrp-lc .yiv0650244692ad {margin-bottom:10px;padding:0 0;}#yiv0650244692 #yiv0650244692actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv0650244692 #yiv0650244692activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv0650244692 #yiv0650244692activity span {font-weight:700;}#yiv0650244692 #yiv0650244692activity span:first-child {text-transform:uppercase;}#yiv0650244692 #yiv0650244692activity span a {color:#5085b6;text-decoration:none;}#yiv0650244692 #yiv0650244692activity span span {color:#ff7900;}#yiv0650244692 #yiv0650244692activity span .yiv0650244692underline {text-decoration:underline;}#yiv0650244692 .yiv0650244692attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv0650244692 .yiv0650244692attach div a {text-decoration:none;}#yiv0650244692 .yiv0650244692attach img {border:none;padding-right:5px;}#yiv0650244692 .yiv0650244692attach label {display:block;margin-bottom:5px;}#yiv0650244692 .yiv0650244692attach label a {text-decoration:none;}#yiv0650244692 blockquote {margin:0 0 0 4px;}#yiv0650244692 .yiv0650244692bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv0650244692 .yiv0650244692bold a {text-decoration:none;}#yiv0650244692 dd.yiv0650244692last p a {font-family:Verdana;font-weight:700;}#yiv0650244692 dd.yiv0650244692last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv0650244692 dd.yiv0650244692last p span.yiv0650244692yshortcuts {margin-right:0;}#yiv0650244692 div.yiv0650244692attach-table div div a {text-decoration:none;}#yiv0650244692 div.yiv0650244692attach-table {width:400px;}#yiv0650244692 div.yiv0650244692file-title a, #yiv0650244692 div.yiv0650244692file-title a:active, #yiv0650244692 div.yiv0650244692file-title a:hover, #yiv0650244692 div.yiv0650244692file-title a:visited {text-decoration:none;}#yiv0650244692 div.yiv0650244692photo-title a, #yiv0650244692 div.yiv0650244692photo-title a:active, #yiv0650244692 div.yiv0650244692photo-title a:hover, #yiv0650244692 div.yiv0650244692photo-title a:visited {text-decoration:none;}#yiv0650244692 div#yiv0650244692ygrp-mlmsg #yiv0650244692ygrp-msg p a span.yiv0650244692yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv0650244692 .yiv0650244692green {color:#628c2a;}#yiv0650244692 .yiv0650244692MsoNormal {margin:0 0 0 0;}#yiv0650244692 o {font-size:0;}#yiv0650244692 #yiv0650244692photos div {float:left;width:72px;}#yiv0650244692 #yiv0650244692photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv0650244692 #yiv0650244692photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv0650244692 #yiv0650244692reco-category {font-size:77%;}#yiv0650244692 #yiv0650244692reco-desc {font-size:77%;}#yiv0650244692 .yiv0650244692replbq {margin:4px;}#yiv0650244692 #yiv0650244692ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv0650244692 #yiv0650244692ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv0650244692 #yiv0650244692ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv0650244692 #yiv0650244692ygrp-mlmsg select, #yiv0650244692 input, #yiv0650244692 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv0650244692 #yiv0650244692ygrp-mlmsg pre, #yiv0650244692 code {font:115% monospace;}#yiv0650244692 #yiv0650244692ygrp-mlmsg * {line-height:1.22em;}#yiv0650244692 #yiv0650244692ygrp-mlmsg #yiv0650244692logo {padding-bottom:10px;}#yiv0650244692 #yiv0650244692ygrp-msg p a {font-family:Verdana;}#yiv0650244692 #yiv0650244692ygrp-msg p#yiv0650244692attach-count span {color:#1E66AE;font-weight:700;}#yiv0650244692 #yiv0650244692ygrp-reco #yiv0650244692reco-head {color:#ff7900;font-weight:700;}#yiv0650244692 #yiv0650244692ygrp-reco {margin-bottom:20px;padding:0px;}#yiv0650244692 #yiv0650244692ygrp-sponsor #yiv0650244692ov li a {font-size:130%;text-decoration:none;}#yiv0650244692 #yiv0650244692ygrp-sponsor #yiv0650244692ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv0650244692 #yiv0650244692ygrp-sponsor #yiv0650244692ov ul {margin:0;padding:0 0 0 8px;}#yiv0650244692 #yiv0650244692ygrp-text {font-family:Georgia;}#yiv0650244692 #yiv0650244692ygrp-text p {margin:0 0 1em 0;}#yiv0650244692 #yiv0650244692ygrp-text tt {font-size:120%;}#yiv0650244692 #yiv0650244692ygrp-vital ul li:last-child {border-right:none !important;}#yiv0650244692

[Rocky Martin [e-mail] [H390-VM]]

Pretty sure that before you get a system console you are going to have to
IPL something.
Suggest you read the instructions for your version of VM 370 . The IPL
device.

Post by ***@yahoo.com [H390-VM]
Background: We have recently brought up a 4361 running VM/370 at Living
Computers: Museum + Labs, the culmination of several acquisitions over the
last 6 years, with the help of the fine folks at Fundamental Software and
their FLEXCUB(TM) peripheral emulator. This is a vanilla VM/370
installation.
I last played with Hercules in 2011, when we thought that we were going to
restore a 360/40 and bring it up under DOS. (The hardware turned out to be
much further gone that we had hoped.) I would like very much to use
Hercules to play around with configurations for the 4361 before making
changes to the current system. The ultimate plan is to open the system to
public access.
The issue: I have installed Hercules 3.12 on a Linux box, along with the
4-pack VM/370 system which I had lying about since 2011. I commented out
the DOS portion of the provided hercules.cnf and fired it up in a MobaXterm
window. It starts off well, putting up 4 x3270 windows on my Windows 7
desktop and IPLing VM. At this point, the first window should, I believe,
be the system console, but I get nothing after the Hercules logo.
Modifying the hercules.rc file to start only a single x3270 session does
not change this behavior, nor does eliminating the .rc file altogether and
connecting with Vista tn3270 or ZOC.
I'm clearly missing something, so I'm soliciting advice from the group.
Thanks,
Rich Alderson
Rich Alderson, Sr. Systems Engineer
Living Computers: Museum + Labs
2245 1st Avenue S
Seattle, WA 98134
http://www.livingcomputers.org/

['Dave Wade' [e-mail] [H390-VM]]

The .RC file IPL’s VM on the 4-pack




Dave



From: H390-***@yahoogroups.com [mailto:H390-***@yahoogroups.com]
Sent: 22 June 2017 10:48
To: H390-***@yahoogroups.com
Subject: Re: [H390-VM] VM/370 installation & startup








Pretty sure that before you get a system console you are going to have to IPL something.

Suggest you read the instructions for your version of VM 370 . The IPL device.





On Jun 22, 2017 4:32 AM, "***@yahoo.com <mailto:***@yahoo.com> [H390-VM]" <H390-***@yahoogroups.com <mailto:H390-***@yahoogroups.com> > wrote:



Background: We have recently brought up a 4361 running VM/370 at Living Computers: Museum + Labs, the culmination of several acquisitions over the last 6 years, with the help of the fine folks at Fundamental Software and their FLEXCUB(TM) peripheral emulator. This is a vanilla VM/370 installation.



I last played with Hercules in 2011, when we thought that we were going to restore a 360/40 and bring it up under DOS. (The hardware turned out to be much further gone that we had hoped.) I would like very much to use Hercules to play around with configurations for the 4361 before making changes to the current system. The ultimate plan is to open the system to public access.



The issue: I have installed Hercules 3.12 on a Linux box, along with the 4-pack VM/370 system which I had lying about since 2011. I commented out the DOS portion of the provided hercules.cnf and fired it up in a MobaXterm window. It starts off well, putting up 4 x3270 windows on my Windows 7 desktop and IPLing VM. At this point, the first window should, I believe, be the system console, but I get nothing after the Hercules logo. Modifying the hercules.rc file to start only a single x3270 session does not change this behavior, nor does eliminating the .rc file altogether and connecting with Vista tn3270 or ZOC.



I'm clearly missing something, so I'm soliciting advice from the group.



Thanks,

Rich Alderson



Rich Alderson, Sr. Systems Engineer

Living Computers: Museum + Labs

2245 1st Avenue S

Seattle, WA 98134



http://www.livingcomputers.org/

['\'Fish\' (David B. Trout)' [e-mail] [H390-VM]]

Rich Alderson wrote:

[...]

Post by ***@yahoo.com [H390-VM]
It starts off well, putting up 4 x3270 windows on my Windows
7 desktop and IPLing VM. At this point, the first window
should, I believe, be the system console, but I get nothing
after the Hercules logo. Modifying the hercules.rc file to
start only a single x3270 session does not change this behavior,
nor does eliminating the .rc file altogether and connecting
with Vista tn3270 or ZOC.
I'm clearly missing something, so I'm soliciting advice from
the group.

We need to see both your Hercules configuration file and your .rc file as well.

I don't have the 4-pack VM/370 system but I do have the 6-pack VM/370 system, which I believe is just a later version of the same thing. Looking at its Hercules configuration file I see:


[...]
# You can access the operator's console through the Hercules
# window, or you can launch a 3270 emulator and have the
# operator use it. For the former, ensure the next line is
# not commented.
0009 3215-C NOPROMPT
# For the latter, comment the above line and un-comment this
# line:
# 0010 3270 MOD4
[...]


Presuming your Hercules configuration is the same, the main Hercules panel (HMC = Hardware Maintenance Console, i.e. the screen where you see Hercules issue messages to) is your VM/370 system's master console, not any of your x3270 windows.

Presuming I'm correct (which is required until we can see your Hercules configuration file and .rc file), you might just need to enable your VM terminals:

On your VM/370 master operator console (which, as explained, is likely your main HERCULES window), enter the command:


/ena all


The '/' (slash) is the Hercules prompt character that indicates what follows is NOT a Hercules command but is rather a reply for that guest device (see: "http://www.hercules-390.eu/hercconf.html#consysc"). What the above command is doing is asking VM/370 to "enable all of its terminals.

Once you enter the above command, the VM/370 terminal logo should then appear on ALL of your x3270 terminals, and you should then be able to logon to VM/370 and use your system.

If you want to use an x3270 terminal for your VM/370 master console, then follow the comments in the Hercules configuration file snippet I've posted further above: comment out the 3215 statement and Uncomment the 3270 statement:


[...]
# 0009 3215-C NOPROMPT <-- comment out (prepend with '#')
0010 3270 MOD4 <-- Uncomment (remove '#')
[...]


Then when you IPL, your first x3270 terminal (the one identified as device 0010) *should* then be your VM/370 master operator console where you should see your VM/370 IPL messages appear.

I hope that helps.


(But seriously, when asking for help, you REALLY need to get into the habit of PROVIDING ENOUGH INFORMATION FOR PEOPLE TO HELP YOU! Please see: https://github.com/Fish-Git/AskForHelp)

[Rich Alderson [e-mail] [H390-VM]]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
But seriously, when asking for help, you REALLY need to get into the habit of PROVIDING ENOUGH INFORMATION FOR PEOPLE TO HELP YOU!

Yes, thank you, I was an ass for thinking that in saying "the 4-pack VM system" people might have an idea of what might be in there. Mea maxima culpa.(And here I sit, former customer service manager for a computer manufacturer. I really am embarassed about having made that assumption.)

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
We need to see both your Hercules configuration file and your .rc file as well.

I modified the default hercules.cnf to remove (comment out) the DOS stuff, substitute "4361" for "3081," and "hercules" for "herc370." Here's what I am using:

#
#  NOTE - All entries for MVS and VS1 are commented out
#         but should be compatable with MVS Turnkey system 3
#
#
# VMSYS and basic system VM Config file.
#
#
# This is in several sections
# First is the  CPU setup
#          then  VM Stuff
#          then MVS Stuff
#          then VS1 Stuff
#          eventually DOS/VS stuff if you can wait long enough
#
# All except CPU and VM is commented out but I hope later
# to have the system set up to run MVS and VS1 as turnkey systems
# under VM and perhaps even DOS/VS
#
CPUSERIAL 550042        # CPU serial number
CPUMODEL  4361          # CPU model number
MAINSIZE  2             # Main storage size in megabytes
XPNDSIZE  0             # Expanded storage size in megabytes
CNSLPORT  3270          # TCP port number to which consoles connect
NUMCPU    1             # Number of CPUs
LOADPARM  0120....      # IPL parameter
OSTAILOR  VM            # OS tailoring
PANRATE   100           # Panel refresh rate
#SYSEPOCH  1960          # Needed to suit VS/1
ARCHMODE  S/370
HTTPPORT  8081
TZOFFSET  +0000
#
#
# .-----------------------Device number
# |     .-----------------Device type
# |     |       .---------File name and parameters
# |     |       |
# V     V       V
#---    ----    --------------------
# This is Basic VM Stuff
*
000C    3505    /hercules/vm/dummy eof
000D    3525    /hercules/vm/pun/punch00d.txt ascii
000E    1403    /hercules/vm/prt/print00e.txt
000F    1403    /hercules/vm/prt/print00f.txt
0010    3270
0008    3215
001F    3215
0040    3270
0041    3270
0042    3270
0043    3270
0044    3270
0045    3270
0046    3270
0047    3270
00C0    3270
00C1    3270
00C2    3270
*
*
0480    3420 *
0481    3420 *
*
0580    3420 *
0581    3420 *
# System pack on Chan 7#0731    3330    /hercules/vm/vmsys1-3330-11-ckd
# Temp/Page 1 on Chan 8#0831    3330    /hercules/vm/vmsys2-3330-11-ckd
# Temp/Page 2 on chan 9#0931    3330    /hercules/vm/vmsys3-3330-11-ckd
# Lots of extra MDISK space#0A31    3330    /hercules/vm/vmsys4-3330-11-ckd
#
# Packs on different channels for performance, as in the old days on real iron.
249     3350    /hercules/vm/vm3350-1-cckd
24a     3350    /hercules/vm/vm3350-2-cckd
24b     3350    /hercules/vm/vm3350-3-cckd
24c     3350    /hercules/vm/vm3350-4-cckd
#750     3350    /hercules/vm/vm50-a
#751     3350    /hercules/vm/vm50-b
#752     3350    /hercules/vm/vm50-c
#753     3350    /hercules/vm/vm50-d


## Next is MVS stuff
#
## .-----------------------------Device number
## |    .------------------------Device type
## |    |   .--------------------File name
## |    |   |
## V    V   V
##--- ---- --------------------
#010C 3505 /hercules/dummy eof
#020c 3505 /hercules/dummy eof
##020c 3505 localhost:3505 sockdev ascii trunc eof
#030c 3505 /hercules/dummy eof
#
#010d 3525 /hercules/mvs/pch/pun10d.txt
#020d 3525 /hercules/mvs/pch/pun20d.txt
#030d 3525 /hercules/mvs/pch/pun30d.txt
#
#010e 1403 /hercules/mvs/prt/prt10e.txt
#010f 1403 /hercules/mvs/prt/prt10f.txt
#
#020e 1403 /hercules/mvs/prt/prt20e.txt
#020f 1403 /hercules/mvs/prt/prt20f.txt
#
#030e 1403 /hercules/mvs/prt/prt30e.txt
#030f 1403 /hercules/mvs/prt/prt30f.txt
#
#0131 2314 /hercules/mvs/dasd/sort01.131 ro  sf=/hercules/mvs/shadow/sort01_1.131
#0132 2314 /hercules/mvs/dasd/sort02.132 ro  sf=/hercules/mvs/shadow/sort02_1.132
#0133 2314 /hercules/mvs/dasd/sort03.133 ro  sf=/hercules/mvs/shadow/sort03_1.133
#0134 2314 /hercules/mvs/dasd/sort04.134 ro  sf=/hercules/mvs/shadow/sort04_1.134
#0135 2314 /hercules/mvs/dasd/sort05.135 ro  sf=/hercules/mvs/shadow/sort05_1.135
#0136 2314 /hercules/mvs/dasd/sort06.136 ro  sf=/hercules/mvs/shadow/sort06_1.136
#
#0140 3350 /hercules/mvs/dasd/work00.140 ro  sf=/hercules/mvs/shadow/work00_1.140
#0148 3350 /hercules/mvs/dasd/mvsres.148 ro  sf=/hercules/mvs/shadow/mvsres_1.148
#0149 3350 /hercules/mvs/dasd/smp001.149 ro  sf=/hercules/mvs/shadow/smp001_1.149
#014a 3350 /hercules/mvs/dasd/smp002.14a ro  sf=/hercules/mvs/shadow/smp002_1.14a
#014b 3350 /hercules/mvs/dasd/smp003.14b ro  sf=/hercules/mvs/shadow/smp003_1.14b
#014c 3350 /hercules/mvs/dasd/smp004.14c ro  sf=/hercules/mvs/shadow/smp004_1.14c
#
#
#0150 3330 /hercules/mvs/dasd/start1.150 ro  sf=/hercules/mvs/shadow/start1_1.150
#0151 3330 /hercules/mvs/dasd/spool0.151 ro  sf=/hercules/mvs/shadow/spool0_1.151
#0152 3330 /hercules/mvs/dasd/hasp00.152 ro  sf=/hercules/mvs/shadow/hasp00_1.152
#
#0160 3340 /hercules/mvs/dasd/page00.160 ro  sf=/hercules/mvs/shadow/page00_1.160
#0161 3340 /hercules/mvs/dasd/page01.161 ro  sf=/hercules/mvs/shadow/page01_1.161
#0162 3340 /hercules/mvs/dasd/page02.162 ro  sf=/hercules/mvs/shadow/page02_1.162
#
#0170 3375 /hercules/mvs/dasd/work01.170 ro  sf=/hercules/mvs/shadow/work01_1.170
#
#0180 3380 /hercules/mvs/dasd/work02.180 ro  sf=/hercules/mvs/shadow/work02_1.180
#
#0190 3390 /hercules/mvs/dasd/work03.190 ro  sf=/hercules/mvs/shadow/work03_1.190
#0191 3390 /hercules/mvs/dasd/mvscat.191 ro  sf=/hercules/mvs/shadow/mvscat_1.191
#
#0240 3350 /hercules/mvs/dasd/pub000.240 ro  sf=/hercules/mvs/shadow/pub000_1.240
#0248 3350 /hercules/mvs/dasd/mvsdlb.248 ro  sf=/hercules/mvs/shadow/mvsdlb_1.248
#
#0280 3380 /hercules/mvs/dasd/pub002.280 ro  sf=/hercules/mvs/shadow/pub002_1.280
#
#0340 3350 /hercules/mvs/dasd/cbt000.340 ro  sf=/hercules/mvs/shadow/cbt000_1.340
#0341 3350 /hercules/mvs/dasd/cbt001.341 ro  sf=/hercules/mvs/shadow/cbt001_1.341
#0342 3350 /hercules/mvs/dasd/cbt002.342 ro  sf=/hercules/mvs/shadow/cbt002_1.342
#0343 3350 /hercules/mvs/dasd/cbtcat.343 ro  sf=/hercules/mvs/shadow/cbtcat_1.343
#
#0348 3350 /hercules/mvs/dasd/src000.348 ro  sf=/hercules/mvs/shadow/src000_1.348
#0349 3350 /hercules/mvs/dasd/src001.349 ro  sf=/hercules/mvs/shadow/src001_1.349
#034a 3350 /hercules/mvs/dasd/src002.34a ro  sf=/hercules/mvs/shadow/src002_1.34a
#034b 3350 /hercules/mvs/dasd/srccat.34b ro  sf=/hercules/mvs/shadow/srccat_1.34b
#
#0500 3088 ctct 30880 192.100.100.223 30880 2048
#0501 3088 ctct 30881 192.100.100.223 30881 2048
#
#0600 3088 ctct 30882 192.100.100.223 30882 2048
#0601 3088 ctct 30883 192.100.100.223 30883 2048
#
#
#
#
## Next is VS1 stuff
#
#
## .-----------------------------Device number
## |    .------------------------Device type
## |    |   .--------------------File name
## |    |   |
## V    V   V
##--- ---- --------------------
##0488 3420 *
##014E 3350 /hercules/vs1/vsxres.14A ro sf=/hercules/vs1/shadow/vsxres.14A_1
##014F 3350 /hercules/vs1/vsxspl.14B ro sf=/hercules/vs1/shadow/vsxspl.14A_1
#
#
## Dos system volume
#
#024d 3350 /hercules/vm/sysres.3350
#024e 3350 /hercules/vm/mcat01.3350
#
#
#
#
#
#
The hercules.rc file is untouched:
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 5
*ipl 731
ipl 249
For completeness, here is the entirety of the configuration as shown by Hercules in response to an escape key at the command prompt after the .rc has executed:

    Hercules  CPU0000:   0%     S/370   |                                                                                     Peripherals
                                      | U Addr Modl Type Assignment
  000A0000 00000007        24M.W..... | A 000C 3505 RDR  /hercules/vm/dummy eof
         PSW                          | B 000D 3525 PCH  /hercules/vm/pun/punch00d.txt ascii
                                      | C 000E 1403 PRT  /hercules/vm/prt/print00e.txt print fcbck
  00000C10 00000000 00000249 00000C60 | D 000F 1403 PRT  /hercules/vm/prt/print00f.txt print fcbck
         0        1        2        3 | E 0010 3270 DSP  127.0.0.1
  00000000 00000000 00000000 00000000 | F 0008 3215 CON
         4        5        6        7 | G 001F 3215 CON
  00000000 00000000 00000000 00000000 | H 0040 3270 DSP  127.0.0.1
         8        9       10       11 | I 0041 3270 DSP  127.0.0.1
  00000800 00001800 00000000 00000000 | J 0042 3270 DSP  127.0.0.1
        12       13       14       15 | K 0043 3270 DSP
     GPR     CR      AR      FPR      | L 0044 3270 DSP
                                      | M 0045 3270 DSP
 ADDRESS:  00000000  DATA:   00000000 | N 0046 3270 DSP
                                      | O 0047 3270 DSP
--------------------------------------| P 00C0 3270 DSP
  0.00      0   STO     DIS     RST   | Q 00C1 3270 DSP
  MIPS  SIO/s                         | R 00C2 3270 DSP
                                      | S 0480 3420 TAPE *
  STR    STP    EXT     IPL     PWR   | T 0481 3420 TAPE *
                                      | U 0580 3420 TAPE *
--------------------------------------| V 0581 3420 TAPE *
CPU                                   | W 0249 3350 DASD /hercules/vm/vm3350-1-cckd [555 cyls]
00 STOPPED                            | X 024A 3350 DASD /hercules/vm/vm3350-2-cckd [555 cyls]
                                      | Y 024B 3350 DASD /hercules/vm/vm3350-3-cckd [555 cyls]
                                      | Z 024C 3350 DASD /hercules/vm/vm3350-4-cckd [555 cyls]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
Presuming your Hercules configuration is the same, the main Hercules panel (HMC = Hardware Maintenance Console, i.e. the screen where you see Hercules issue messages to)> is your VM/370 system's master console, not any of your x3270 windows.

From the Installation instructions included on the page http://www.hercules-390.eu/hercinst.html



To start Hercules enter this command at the Unix or Windows command prompt:
hercules [ -f filename ]
[ -d ]
[ -p dyndir ] [[-l dynmod ] ... ]
[ > logfile ]
        ...Next connect a tn3270 client to the console port (normally port 3270). The client will be connected to the first 3270 device address specified in the configuration file (this should be the master console address). If your master console is a 1052 or 3215, connect a telnet client instead of a tn3270 client. Now you can enter an ipl command from the control panel.

so color me confused by your statement that the HMC is the VM master console, as if that ought to be obvious to a blind horse.  Moving on

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
/ena all
The '/' (slash) is the Hercules prompt character that indicates what follows is NOT a Hercules command but is rather a reply for that guest device (see: "http://www.hercules-390.eu/hercconf.html#consysc").>  What the above command is doing is asking VM/370 to "enable all of its terminals.

Having some experience with VM, and a great deal more with SVS and MVS, 35 years ago when I was a systems programmer in the IBM world, as well as more recently in getting the 4361 up and running, I'm familiar with the CP ENABLE command, but you have no way of knowing that.  The result, however, is not encouraging.  I'm including only the last few lines following the execution of the "ipl 249" command in the .rc file:
...HHCCP048I 0249:CCW=06862000 60001000
HHCCP075I 0249:Stat=0C20 Count=0000
HHCCP048I 0249:CCW=06862000 60001000
HHCCP075I 0249:Stat=0C20 Count=0000
HHCCP011I CPU0000: Disabled wait state
          PSW=000A0000 00000007
/ena all
HHCPN139E Command "/ena" not found; enter '?' for list.
/cp ena all
HHCPN139E Command "/cp" not found; enter '?' for list.
Command ==>
So I'll ask again, with complete documentation, what is it that I am missing? Thank you for your assistance.
Rich
Rich Alderson
Vintage Computing Sr. Systems Engineer
Living Computers: Museum + Labs
2245 1st Avenue S
Seattle, WA 98134mailto:***@LivingComputers.orghttp://www.LivingComputers.org/



On Thursday, June 22, 2017 3:11 PM, "''Fish' (David B. Trout)' ***@gmail.com [H390-VM]" <H390-***@yahoogroups.com> wrote:


  Rich Alderson wrote:

[...]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
It starts off well, putting up 4 x3270 windows on my Windows
7 desktop and IPLing VM. At this point, the first window
should, I believe, be the system console, but I get nothing
after the Hercules logo. Modifying the hercules.rc file to
start only a single x3270 session does not change this behavior,
nor does eliminating the .rc file altogether and connecting
with Vista tn3270 or ZOC.
I'm clearly missing something, so I'm soliciting advice from
the group.

We need to see both your Hercules configuration file and your .rc file as well.

I don't have the 4-pack VM/370 system but I do have the 6-pack VM/370 system, which I believe is just a later version of the same thing. Looking at its Hercules configuration file I see:

[...]
# You can access the operator's console through the Hercules
# window, or you can launch a 3270 emulator and have the
# operator use it. For the former, ensure the next line is
# not commented.
0009 3215-C NOPROMPT
# For the latter, comment the above line and un-comment this
# line:
# 0010 3270 MOD4
[...]

Presuming your Hercules configuration is the same, the main Hercules panel (HMC = Hardware Maintenance Console, i.e. the screen where you see Hercules issue messages to) is your VM/370 system's master console, not any of your x3270 windows.

Presuming I'm correct (which is required until we can see your Hercules configuration file and .rc file), you might just need to enable your VM terminals:

On your VM/370 master operator console (which, as explained, is likely your main HERCULES window), enter the command:

/ena all

The '/' (slash) is the Hercules prompt character that indicates what follows is NOT a Hercules command but is rather a reply for that guest device (see: "http://www.hercules-390.eu/hercconf.html#consysc"). What the above command is doing is asking VM/370 to "enable all of its terminals.

Once you enter the above command, the VM/370 terminal logo should then appear on ALL of your x3270 terminals, and you should then be able to logon to VM/370 and use your system.

If you want to use an x3270 terminal for your VM/370 master console, then follow the comments in the Hercules configuration file snippet I've posted further above: comment out the 3215 statement and Uncomment the 3270 statement:

[...]
# 0009 3215-C NOPROMPT <-- comment out (prepend with '#')
0010 3270 MOD4 <-- Uncomment (remove '#')
[...]

Then when you IPL, your first x3270 terminal (the one identified as device 0010) *should* then be your VM/370 master operator console where you should see your VM/370 IPL messages appear.

I hope that helps.

(But seriously, when asking for help, you REALLY need to get into the habit of PROVIDING ENOUGH INFORMATION FOR PEOPLE TO HELP YOU! Please see: https://github.com/Fish-Git/AskForHelp)

['Dave G4UGM' [e-mail] [H390-VM]]

Rich,

I think the first thing to say is that Hercules is rather complex. It will emulate anything from a 370 forwards. There are many options that can pull the rug from under your feet.,



With the config you sent the HERCULES console is the “HMC” console but the “/ENA ALL” doesn’t work because Hercules is not the system console. Your config pretty closely matches a 43xx box with a 3278-2A console, except it has a 3278-2 console with the full 24 lines. This is mapped to X3270 session connected to channel 010. Those instructions assume you have a line-mode console/printer and Hercules is emulating that as well as the HMC on the same screen. Hercules can emulate a line mode console/printer as either an “Integrated console” or via a line-mode telnet connection.



I feel sometimes you can have too much automation and the Hercules.rc and the script used to start up Hercules are hiding something!.



The stuff you sent all looks good. What we can’t see is the response to the IPL which will be on the other Hercules screen. If you press “esc” from the device config what does that say. I think there are three possible problems here:-



1. The IPL is failing. => there should be a herclog.txt somewhere with this info in. Are you typing “vmdist” to run a shell script to start things up? If so it probably has a re-direct for the log.
2. The IPL works and VM can’t find a console => The VM DIST I have has the primary console on 010 and you have a 3270 on 010 connected. Can you confirm that the 3270 connected to 010 is blank.

a. Perhaps edit the Hercules.rc so it only starts one 3270 then we are sure it’s the console?

3. The IPL works and VM is hung at the WARM/COLD/CKPT dialog => this should be on the screen on 010. At this point the other screens will still have the Hercules logo.



Let me know if this helps




Dave







From: H390-***@yahoogroups.com [mailto:H390-***@yahoogroups.com]
Sent: 23 June 2017 19:54
To: H390-***@yahoogroups.com
Subject: Re: [H390-VM] VM/370 installation & startup

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
But seriously, when asking for help, you REALLY need to get into the habit of PROVIDING ENOUGH INFORMATION FOR PEOPLE TO HELP YOU!

Yes, thank you, I was an ass for thinking that in saying "the 4-pack VM system" people might have an idea of what might be in there. Mea maxima culpa.

(And here I sit, former customer service manager for a computer manufacturer. I really am embarassed about having made that assumption.)

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
We need to see both your Hercules configuration file and your .rc file as well.

I modified the default hercules.cnf to remove (comment out) the DOS stuff, substitute "4361" for "3081," and "hercules" for "herc370." Here's what I am using:



#
# NOTE - All entries for MVS and VS1 are commented out
# but should be compatable with MVS Turnkey system 3
#
#
# VMSYS and basic system VM Config file.
#
#
# This is in several sections
# First is the CPU setup
# then VM Stuff
# then MVS Stuff
# then VS1 Stuff
# eventually DOS/VS stuff if you can wait long enough
#
# All except CPU and VM is commented out but I hope later
# to have the system set up to run MVS and VS1 as turnkey systems
# under VM and perhaps even DOS/VS
#
CPUSERIAL 550042 # CPU serial number
CPUMODEL 4361 # CPU model number
MAINSIZE 2 # Main storage size in megabytes
XPNDSIZE 0 # Expanded storage size in megabytes
CNSLPORT 3270 # TCP port number to which consoles connect
NUMCPU 1 # Number of CPUs
LOADPARM 0120.... # IPL parameter
OSTAILOR VM # OS tailoring
PANRATE 100 # Panel refresh rate
#SYSEPOCH 1960 # Needed to suit VS/1
ARCHMODE S/370
HTTPPORT 8081
TZOFFSET +0000
#
#
# .-----------------------Device number
# | .-----------------Device type
# | | .---------File name and parameters
# | | |
# V V V
#--- ---- --------------------
# This is Basic VM Stuff
*
000C 3505 /hercules/vm/dummy eof
000D 3525 /hercules/vm/pun/punch00d.txt ascii
000E 1403 /hercules/vm/prt/print00e.txt
000F 1403 /hercules/vm/prt/print00f.txt
0010 3270
0008 3215
001F 3215
0040 3270
0041 3270
0042 3270
0043 3270
0044 3270
0045 3270
0046 3270
0047 3270
00C0 3270
00C1 3270
00C2 3270
*
*
0480 3420 *
0481 3420 *


*
0580 3420 *
0581 3420 *


# System pack on Chan 7

#0731 3330 /hercules/vm/vmsys1-3330-11-ckd
# Temp/Page 1 on Chan 8

#0831 3330 /hercules/vm/vmsys2-3330-11-ckd
# Temp/Page 2 on chan 9

#0931 3330 /hercules/vm/vmsys3-3330-11-ckd
# Lots of extra MDISK space

#0A31 3330 /hercules/vm/vmsys4-3330-11-ckd
#
# Packs on different channels for performance, as in the old days on real iron.


249 3350 /hercules/vm/vm3350-1-cckd
24a 3350 /hercules/vm/vm3350-2-cckd
24b 3350 /hercules/vm/vm3350-3-cckd
24c 3350 /hercules/vm/vm3350-4-cckd


#750 3350 /hercules/vm/vm50-a
#751 3350 /hercules/vm/vm50-b
#752 3350 /hercules/vm/vm50-c
#753 3350 /hercules/vm/vm50-d







## Next is MVS stuff
#
## .-----------------------------Device number
## | .------------------------Device type
## | | .--------------------File name
## | | |
## V V V
##--- ---- --------------------
#010C 3505 /hercules/dummy eof
#020c 3505 /hercules/dummy eof
##020c 3505 localhost:3505 sockdev ascii trunc eof
#030c 3505 /hercules/dummy eof
#
#010d 3525 /hercules/mvs/pch/pun10d.txt
#020d 3525 /hercules/mvs/pch/pun20d.txt
#030d 3525 /hercules/mvs/pch/pun30d.txt
#
#010e 1403 /hercules/mvs/prt/prt10e.txt
#010f 1403 /hercules/mvs/prt/prt10f.txt
#
#020e 1403 /hercules/mvs/prt/prt20e.txt
#020f 1403 /hercules/mvs/prt/prt20f.txt
#
#030e 1403 /hercules/mvs/prt/prt30e.txt
#030f 1403 /hercules/mvs/prt/prt30f.txt
#
#0131 2314 /hercules/mvs/dasd/sort01.131 ro sf=/hercules/mvs/shadow/sort01_1.131
#0132 2314 /hercules/mvs/dasd/sort02.132 ro sf=/hercules/mvs/shadow/sort02_1.132
#0133 2314 /hercules/mvs/dasd/sort03.133 ro sf=/hercules/mvs/shadow/sort03_1.133
#0134 2314 /hercules/mvs/dasd/sort04.134 ro sf=/hercules/mvs/shadow/sort04_1.134
#0135 2314 /hercules/mvs/dasd/sort05.135 ro sf=/hercules/mvs/shadow/sort05_1.135
#0136 2314 /hercules/mvs/dasd/sort06.136 ro sf=/hercules/mvs/shadow/sort06_1.136
#
#0140 3350 /hercules/mvs/dasd/work00.140 ro sf=/hercules/mvs/shadow/work00_1.140
#0148 3350 /hercules/mvs/dasd/mvsres.148 ro sf=/hercules/mvs/shadow/mvsres_1.148
#0149 3350 /hercules/mvs/dasd/smp001.149 ro sf=/hercules/mvs/shadow/smp001_1.149
#014a 3350 /hercules/mvs/dasd/smp002.14a ro sf=/hercules/mvs/shadow/smp002_1.14a
#014b 3350 /hercules/mvs/dasd/smp003.14b ro sf=/hercules/mvs/shadow/smp003_1.14b
#014c 3350 /hercules/mvs/dasd/smp004.14c ro sf=/hercules/mvs/shadow/smp004_1.14c
#
#
#0150 3330 /hercules/mvs/dasd/start1.150 ro sf=/hercules/mvs/shadow/start1_1.150
#0151 3330 /hercules/mvs/dasd/spool0.151 ro sf=/hercules/mvs/shadow/spool0_1.151
#0152 3330 /hercules/mvs/dasd/hasp00.152 ro sf=/hercules/mvs/shadow/hasp00_1.152
#
#0160 3340 /hercules/mvs/dasd/page00.160 ro sf=/hercules/mvs/shadow/page00_1.160
#0161 3340 /hercules/mvs/dasd/page01.161 ro sf=/hercules/mvs/shadow/page01_1.161
#0162 3340 /hercules/mvs/dasd/page02.162 ro sf=/hercules/mvs/shadow/page02_1.162
#
#0170 3375 /hercules/mvs/dasd/work01.170 ro sf=/hercules/mvs/shadow/work01_1.170
#
#0180 3380 /hercules/mvs/dasd/work02.180 ro sf=/hercules/mvs/shadow/work02_1.180
#
#0190 3390 /hercules/mvs/dasd/work03.190 ro sf=/hercules/mvs/shadow/work03_1.190
#0191 3390 /hercules/mvs/dasd/mvscat.191 ro sf=/hercules/mvs/shadow/mvscat_1.191
#
#0240 3350 /hercules/mvs/dasd/pub000.240 ro sf=/hercules/mvs/shadow/pub000_1.240
#0248 3350 /hercules/mvs/dasd/mvsdlb.248 ro sf=/hercules/mvs/shadow/mvsdlb_1.248
#
#0280 3380 /hercules/mvs/dasd/pub002.280 ro sf=/hercules/mvs/shadow/pub002_1.280
#
#0340 3350 /hercules/mvs/dasd/cbt000.340 ro sf=/hercules/mvs/shadow/cbt000_1.340
#0341 3350 /hercules/mvs/dasd/cbt001.341 ro sf=/hercules/mvs/shadow/cbt001_1.341
#0342 3350 /hercules/mvs/dasd/cbt002.342 ro sf=/hercules/mvs/shadow/cbt002_1.342
#0343 3350 /hercules/mvs/dasd/cbtcat.343 ro sf=/hercules/mvs/shadow/cbtcat_1.343
#
#0348 3350 /hercules/mvs/dasd/src000.348 ro sf=/hercules/mvs/shadow/src000_1.348
#0349 3350 /hercules/mvs/dasd/src001.349 ro sf=/hercules/mvs/shadow/src001_1.349
#034a 3350 /hercules/mvs/dasd/src002.34a ro sf=/hercules/mvs/shadow/src002_1.34a
#034b 3350 /hercules/mvs/dasd/srccat.34b ro sf=/hercules/mvs/shadow/srccat_1.34b
#
#0500 3088 ctct 30880 192.100.100.223 30880 2048
#0501 3088 ctct 30881 192.100.100.223 30881 2048
#
#0600 3088 ctct 30882 192.100.100.223 30882 2048
#0601 3088 ctct 30883 192.100.100.223 30883 2048
#
#
#
#
## Next is VS1 stuff
#
#
## .-----------------------------Device number
## | .------------------------Device type
## | | .--------------------File name
## | | |
## V V V
##--- ---- --------------------
##0488 3420 *
##014E 3350 /hercules/vs1/vsxres.14A ro sf=/hercules/vs1/shadow/vsxres.14A_1
##014F 3350 /hercules/vs1/vsxspl.14B ro sf=/hercules/vs1/shadow/vsxspl.14A_1
#
#
## Dos system volume
#
#024d 3350 /hercules/vm/sysres.3350
#024e 3350 /hercules/vm/mcat01.3350
#
#
#
#
#
#

The hercules.rc file is untouched:

pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 5
*ipl 731
ipl 249

For completeness, here is the entirety of the configuration as shown by Hercules in response to an escape key at the command prompt after the .rc has executed:

Hercules CPU0000: 0% S/370 | Peripherals
| U Addr Modl Type Assignment
000A0000 00000007 24M.W..... | A 000C 3505 RDR /hercules/vm/dummy eof
PSW | B 000D 3525 PCH /hercules/vm/pun/punch00d.txt ascii
| C 000E 1403 PRT /hercules/vm/prt/print00e.txt print fcbck
00000C10 00000000 00000249 00000C60 | D 000F 1403 PRT /hercules/vm/prt/print00f.txt print fcbck
0 1 2 3 | E 0010 3270 DSP 127.0.0.1
00000000 00000000 00000000 00000000 | F 0008 3215 CON
4 5 6 7 | G 001F 3215 CON
00000000 00000000 00000000 00000000 | H 0040 3270 DSP 127.0.0.1
8 9 10 11 | I 0041 3270 DSP 127.0.0.1
00000800 00001800 00000000 00000000 | J 0042 3270 DSP 127.0.0.1
12 13 14 15 | K 0043 3270 DSP
GPR CR AR FPR | L 0044 3270 DSP
| M 0045 3270 DSP
ADDRESS: 00000000 DATA: 00000000 | N 0046 3270 DSP
| O 0047 3270 DSP
--------------------------------------| P 00C0 3270 DSP
0.00 0 STO DIS RST | Q 00C1 3270 DSP
MIPS SIO/s | R 00C2 3270 DSP
| S 0480 3420 TAPE *
STR STP EXT IPL PWR | T 0481 3420 TAPE *
| U 0580 3420 TAPE *
--------------------------------------| V 0581 3420 TAPE *
CPU | W 0249 3350 DASD /hercules/vm/vm3350-1-cckd [555 cyls]
00 STOPPED | X 024A 3350 DASD /hercules/vm/vm3350-2-cckd [555 cyls]
| Y 024B 3350 DASD /hercules/vm/vm3350-3-cckd [555 cyls]
| Z 024C 3350 DASD /hercules/vm/vm3350-4-cckd [555 cyls]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
Presuming your Hercules configuration is the same, the main Hercules panel (HMC = Hardware Maintenance Console, i.e. the screen where you see Hercules issue messages to)
is your VM/370 system's master console, not any of your x3270 windows.

From the Installation instructions included on the page http://www.hercules-390.eu/hercinst.html




To start Hercules enter this command at the Unix or Windows command prompt:

hercules [ -f filename ]
[ -d ]
[ -p dyndir ] [[-l dynmod ] ... ]
[ > logfile ]

...

Next connect a tn3270 client to the console port (normally port 3270). The client will be connected to the first 3270 device address specified in the configuration file (this should be the master console address). If your master console is a 1052 or 3215, connect a telnet client instead of a tn3270 client.

Now you can enter an ipl command from the control panel.

so color me confused by your statement that the HMC is the VM master console, as if that ought to be obvious to a blind horse. Moving on

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
/ena all
The '/' (slash) is the Hercules prompt character that indicates what follows is NOT a Hercules command but is rather a reply for that guest device (see: "http://www.hercules-390.eu/hercconf.html#consysc").
What the above command is doing is asking VM/370 to "enable all of its terminals.

Having some experience with VM, and a great deal more with SVS and MVS, 35 years ago when I was a systems programmer in the IBM world, as well as more recently in getting the 4361 up and running, I'm familiar with the CP ENABLE command, but you have no way of knowing that. The result, however, is not encouraging. I'm including only the last few lines following the execution of the "ipl 249" command in the .rc file:

...

HHCCP048I 0249:CCW=06862000 60001000
HHCCP075I 0249:Stat=0C20 Count=0000
HHCCP048I 0249:CCW=06862000 60001000
HHCCP075I 0249:Stat=0C20 Count=0000
HHCCP011I CPU0000: Disabled wait state
PSW=000A0000 00000007
/ena all
HHCPN139E Command "/ena" not found; enter '?' for list.
/cp ena all
HHCPN139E Command "/cp" not found; enter '?' for list.
Command ==>

So I'll ask again, with complete documentation, what is it that I am missing? Thank you for your assistance.



Rich



Rich Alderson
Vintage Computing Sr. Systems Engineer
Living Computers: Museum + Labs
2245 1st Avenue S
Seattle, WA 98134

mailto:***@LivingComputers.org

http://www.LivingComputers.org/





On Thursday, June 22, 2017 3:11 PM, "''Fish' (David B. Trout)' ***@gmail.com <mailto:***@gmail.com> [H390-VM]" <H390-***@yahoogroups.com <mailto:H390-***@yahoogroups.com> > wrote:





Rich Alderson wrote:

[...]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
It starts off well, putting up 4 x3270 windows on my Windows
7 desktop and IPLing VM. At this point, the first window
should, I believe, be the system console, but I get nothing
after the Hercules logo. Modifying the hercules.rc file to
start only a single x3270 session does not change this behavior,
nor does eliminating the .rc file altogether and connecting
with Vista tn3270 or ZOC.
I'm clearly missing something, so I'm soliciting advice from
the group.

We need to see both your Hercules configuration file and your .rc file as well.

I don't have the 4-pack VM/370 system but I do have the 6-pack VM/370 system, which I believe is just a later version of the same thing. Looking at its Hercules configuration file I see:

[...]
# You can access the operator's console through the Hercules
# window, or you can launch a 3270 emulator and have the
# operator use it. For the former, ensure the next line is
# not commented.
0009 3215-C NOPROMPT
# For the latter, comment the above line and un-comment this
# line:
# 0010 3270 MOD4
[...]

Presuming your Hercules configuration is the same, the main Hercules panel (HMC = Hardware Maintenance Console, i.e. the screen where you see Hercules issue messages to) is your VM/370 system's master console, not any of your x3270 windows.

Presuming I'm correct (which is required until we can see your Hercules configuration file and .rc file), you might just need to enable your VM terminals:

On your VM/370 master operator console (which, as explained, is likely your main HERCULES window), enter the command:

/ena all

The '/' (slash) is the Hercules prompt character that indicates what follows is NOT a Hercules command but is rather a reply for that guest device (see: "http://www.hercules-390.eu/hercconf.html#consysc"). What the above command is doing is asking VM/370 to "enable all of its terminals.

Once you enter the above command, the VM/370 terminal logo should then appear on ALL of your x3270 terminals, and you should then be able to logon to VM/370 and use your system.

If you want to use an x3270 terminal for your VM/370 master console, then follow the comments in the Hercules configuration file snippet I've posted further above: comment out the 3215 statement and Uncomment the 3270 statement:

[...]
# 0009 3215-C NOPROMPT <-- comment out (prepend with '#')
0010 3270 MOD4 <-- Uncomment (remove '#')
[...]

Then when you IPL, your first x3270 terminal (the one identified as device 0010) *should* then be your VM/370 master operator console where you should see your VM/370 IPL messages appear.

I hope that helps.

(But seriously, when asking for help, you REALLY need to get into the habit of PROVIDING ENOUGH INFORMATION FOR PEOPLE TO HELP YOU! Please see: https://github.com/Fish-Git/AskForHelp)

[Rich Alderson [e-mail] [H390-VM]]

Hi, Dave,

Post by 'Dave G4UGM' ***@gmail.com [H390-VM]
What we can’t see is the response to the IPL which will be on the other Hercules screen.

I modified the startup script I set up to log the Hercules console.  It's very simple:

    #!/bin/sh
    cd /hercules/vm/
    exec /usr/local/bin/hercules -f 4361.cnf > /tmp/Hercules.$$.log

The results:

17:25:03 Hercules Version 3.12
17:25:03 (c)Copyright 1999-2015 by Roger Bowler, Jan Jaeger, and others
17:25:03 Built on Jun 15 2017 at 15:49:17
17:25:03 Build information:
17:25:03   Modes: S/370 ESA/390 z/Arch
17:25:03   Max CPU Engines: 8
17:25:03   Using setresuid() for setting privileges
17:25:03   Dynamic loading support
17:25:03   Using shared libraries
17:25:03   HTTP Server support
17:25:03   Regular Expressions support
17:25:03   Automatic Operator support
17:25:03   Machine dependent assists: cmpxchg1 cmpxchg4 cmpxchg8 fetch_dw store_dw multi_byte
17:25:03 Running on LCMlinux Linux-3.2.29-smp.#2 SMP Mon Sep 17 13:16:43 CDT 2012 i686 UP
17:25:03 HHCHD018I Loadable module directory is /usr/local/lib/hercules
17:25:03 Crypto module loaded (c) Copyright Bernard van der Helm, 2003-2010
17:25:03   Active: Message Security Assist
17:25:03           Message Security Assist Extension 1
17:25:03           Message Security Assist Extension 2
17:25:03           Message Security Assist Extension 3
17:25:03           Message Security Assist Extension 4
17:25:03 HHCCF065I Hercules: tid=B70E5700, pid=19117, pgid=19117, priority=0
17:25:03 HHCDA020I /hercules/vm/vm3350-1-cckd cyls=555 heads=30 tracks=16650 trklen=19456
17:25:03 HHCHT001I HTTP listener thread started: tid=B6DFFB40, pid=19117
17:25:03 HHCHT013I Using HTTPROOT directory "/usr/local/share/hercules/"
17:25:03 HHCHT006I Waiting for HTTP requests on port 8081
17:25:03 HHCTE001I Console connection thread started: tid=B6CFFB40, pid=19117
17:25:03 HHCTE003I Waiting for console connection on port 3270
17:25:03 HHCDA020I /hercules/vm/vm3350-2-cckd cyls=555 heads=30 tracks=16650 trklen=19456
17:25:03 HHCDA020I /hercules/vm/vm3350-3-cckd cyls=555 heads=30 tracks=16650 trklen=19456
17:25:03 HHCDA020I /hercules/vm/vm3350-4-cckd cyls=555 heads=30 tracks=16650 trklen=19456
17:25:03 HHCCP002I CPU0000 thread started: tid=B67FCB40, pid=19117, priority=15
17:25:03 HHCTT002I Timer thread started: tid=B66FCB40, pid=19117, priority=0
17:25:03 HHCCP003I CPU0000 architecture mode S/370
17:25:03 HHCPN001I Control panel thread started: tid=B70E5700, pid=19117
17:25:03 HHCAO001I Hercules Automatic Operator thread started;
17:25:03           tid=B6BFFB40, pri=0, pid=19117
17:25:17 sh x3270 localhost 3270 &
17:25:18 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:0010
17:25:30 ipl 249
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP011I CPU0000: Disabled wait state
17:25:30           PSW=000A0000 00000007
17:25:46 exit
17:25:46 HHCIN900I Begin Hercules shutdown
17:25:46 HHCIN901I Releasing configuration
17:25:46 HHCCP008I CPU0000 thread ended: tid=B67FCB40, pid=19117
17:25:46 HHCAO002I Hercules Automatic Operator thread ended
17:25:46 HHCCF047I Subchannel 0:0000 detached
17:25:46 HHCCF047I Subchannel 0:0001 detached
17:25:46 HHCCF047I Subchannel 0:0002 detached
17:25:46 HHCCF047I Subchannel 0:0003 detached
17:25:46 HHCCF047I Subchannel 0:0004 detached
17:25:46 HHCCF047I Subchannel 0:0005 detached
17:25:46 HHCCF047I Subchannel 0:0006 detached
17:25:46 HHCCF047I Subchannel 0:0007 detached
17:25:46 HHCCF047I Subchannel 0:0008 detached
17:25:46 HHCCF047I Subchannel 0:0009 detached
17:25:46 HHCCF047I Subchannel 0:000A detached
17:25:46 HHCCF047I Subchannel 0:000B detached
17:25:46 HHCCF047I Subchannel 0:000C detached
17:25:46 HHCCF047I Subchannel 0:000D detached
17:25:46 HHCCF047I Subchannel 0:000E detached
17:25:46 HHCCF047I Subchannel 0:000F detached
17:25:46 HHCCF047I Subchannel 0:0010 detached
17:25:46 HHCCF047I Subchannel 0:0011 detached
17:25:46 HHCCF047I Subchannel 0:0012 detached
17:25:46 HHCCF047I Subchannel 0:0013 detached
17:25:46 HHCCF047I Subchannel 0:0014 detached
17:25:46 HHCCF047I Subchannel 0:0015 detached
17:25:46 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
17:25:46 HHCCD212I --------------------------------------------------------------------
17:25:46 HHCCD213I [*]   20726045   2%    9          3       0       2       0        3
17:25:46 HHCCD215I /hercules/vm/vm3350-1-cckd
17:25:46 HHCCD216I [0]   20726045   2%    9 rw       3       0       2
17:25:46 HHCCF047I Subchannel 0:0016 detached
17:25:46 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
17:25:46 HHCCD212I --------------------------------------------------------------------
17:25:46 HHCCD213I [*]   23614905   1%    1          0       0       0       0        0
17:25:46 HHCCD215I /hercules/vm/vm3350-2-cckd
17:25:46 HHCCD216I [0]   23614905   1%    1 rw       0       0       0
17:25:46 HHCCF047I Subchannel 0:0017 detached
17:25:46 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
17:25:46 HHCCD212I --------------------------------------------------------------------
17:25:46 HHCCD213I [*]   10074447   3%    2          0       0       0       0        0
17:25:46 HHCCD215I /hercules/vm/vm3350-3-cckd
17:25:46 HHCCD216I [0]   10074447   3%    2 rw       0       0       0
17:25:46 HHCCF047I Subchannel 0:0018 detached
17:25:46 HHCCD210I           size free  nbr st   reads  writes l2reads    hits switches
17:25:46 HHCCD212I --------------------------------------------------------------------
17:25:46 HHCCD213I [*]    9570062   7%    3          0       0       0       0        0
17:25:46 HHCCD215I /hercules/vm/vm3350-4-cckd
17:25:46 HHCCD216I [0]    9570062   7%    3 rw       0       0       0
17:25:46 HHCCF047I Subchannel 0:0019 detached
17:25:46 HHCIN902I Configuration release complete
17:25:46 HHCIN903I Calling termination routines
17:25:46 HHCHD900I Begin shutdown sequence
17:25:46 HHCHD901I Calling panel_cleanup
17:25:46 HHCTE004I Console connection thread terminated
17:25:46 HHCHD902I panel_cleanup complete
17:25:46 HHCHD901I Calling console_shutdown
17:25:46 HHCHD902I console_shutdown complete
17:25:46 HHCHD901I Calling hdl_term
17:25:46 HHCHD950I Begin HDL termination sequence
17:25:46 HHCHD951I Calling module *Hercules cleanup routine
17:25:46 HHCHD952I Module *Hercules cleanup complete
17:25:46 HHCHD959I HDL Termination sequence complete
17:25:46 HHCHD902I hdl_term complete
17:25:46 HHCHD901I Calling logger_term
17:25:46 HHCLG014I logger thread terminating
17:25:46 HHCLG014I logger thread terminating

No manipulation of the x3270 window (either via the emulated keypad or attempting to use the keyboard shortcuts offered made any difference, other than to turn on the "X Wait" in the bottom row of the 3270 screen.
It looks to me as though the IPL is succeeding, but ...
Thanks,Rich

['Dave Wade' [e-mail] [H390-VM]]

So the IPL fails or rather VM Initialization fails and VM loads a disabled wait:-



17:25:30 HHCCP011I CPU0000: Disabled wait state
17:25:30 PSW=000A0000 00000007



For with the system messages and codes say:-



007 Explanation; A program check, a machine check, a permanent I/O error, invalid warm start data, an invalid warm start cylinder, or a full warm start cylinder was encountered by the checkpoint program. Issued by module DKKCK



Which seems reasonable, given the list of io errors (I assume they are errors) shown in the console log for device 249 the IPL device. So it appears VM can’t find access checkpoint data BUT we still don’t seem to have a console where we should see an error message.



As I don’t recognise the config file, its not the one from the normal 4-pack download I would next, as Mark suggests remove all the 3215 devices and see what happens. I can only think VM is trying to use one of those as a console.



If that fails, then it looks like you need a new download. I would grab a copy of the Six Pack 1.2. I know there is a copy here:-



http://www.smrcc.org.uk/members/g4ugm/VM370.htm



Dave

['\'Fish\' (David B. Trout)' [e-mail] [H390-VM]]

Rich Alderson wrote:

[...]

Post by Rich Alderson ***@yahoo.com [H390-VM]
17:25:30 ipl 249
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000

<snip a zillion more lines just like the above>

Post by Rich Alderson ***@yahoo.com [H390-VM]
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP048I 0249:CCW=06862000 60001000
17:25:30 HHCCP075I 0249:Stat=0C20 Count=0000
17:25:30 HHCCP011I CPU0000: Disabled wait state
17:25:30 PSW=000A0000 00000007

Wow. Channel Program Checks right off the bat! Something is very wrong with your dasd.

Given that they're compressed I have to ask whether or not you have BZIP2 and/or ZLIB installed on your system.

From the beginning of your log it looks like you did correctly build your Hercules with both BZIP and ZLIB support (this being 3.12, I didn't see any "No CCKD BZIP2 support" or "No ZLIB support" error message which should otherwise appear if you hadn't, which is good), so unless you somehow built your Hercules *with* such support even though your system doesn't *have* such support, I'm at a complete loss as to why you're getting Channel Program Check I/O errors on your dasd. It's obvious however, that *something* is "wrong" with your dasd. The VM/370 4-pack *should* IPL just fine. The fact that is doesn't on your system would seem to imply your system is missing something Hercules is expecting.

Try this (in addition to the CCW trace ("t+249") I requested in my earlier reply):

cckddiag -c /hercules/vm/vm3350-1-cckd


That will display the CCKD header and tell us, at offset 45 (hex 2d) which compression algorithm the device is using: 00 = none, 01 = zlib, 02 = bzip2.

Then all we need to know is whether or not your system actually *has* such compression support. If it does, then the problem is something else, so it wouldn't hurt to then try doing a "check disk" (cdsk) on all of your dasd (especially 249 = /hercules/vm/vm3350-1-cckd of course!):

cckdcdsk -3 /hercules/vm/vm3350-1-cckd


FINALLY, if *that* doesn't work (if it doesn't spit out any messages indicating it found and corrected some errors), then you *might* want to try doing a cckdcopy to convert your dasd to regular CKD dasd (and not compressed CKD (CCKD) dasd as they are today):

dasdcopy -lfs -o ckd /hercules/vm/vm3350-1-cckd /hercules/vm/vm3350-1.CKD


(and then update your Hercules configuration file as appropriate of course)

If THAT'S not it, then I give up!

That's all I can think of for now.

Good luck!

I hope the above helps.

['\'Fish\' (David B. Trout)' [e-mail] [H390-VM]]

Fish wrote:

[...]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
If THAT'S not it, then I give up!
That's all I can think of for now.

Just thought of one more possibility since you're using compressed dasd: you could be out of room. (It's unlikely but still a possibility.)

CCKD (compressed CKD) dasd files are limited to 4G maximum file size (since the original design/code foolishly used/uses only 32-bit file offsets in its structures), so if you, for example, created a bunch of large files on your sysres dasd, it might not have any room left to write whatever log files or spool files that get created (are there any?) whenever you IPL the system.

As I said, I find this particular possibility quite unlikely, but until we eliminate it, we must entertain it.

What does a 'ls -al /hercules/vm/*' show for each file's size?

[[e-mail] [H390-VM]]

The reason that the channel program checks are occurring is because there is insufficient main storage available in order to IPL this system. This is evidenced by the CCWs shown in Rich's log that he provided. The address in the CCW is x'862000', and that address does not exist in a 2 MB machine.


I realize that the goal is to mimic the 4361, but for now, I'd increase the MAINSIZE specification in the Hercules configuration file to 16.


These high addresses contained in the CCWs strongly imply that the CP nucleus generated on the 249 volume was generated Virtual=Real. Otherwise, CP would IPL in a 2 MB machine with ease.


I agree with Gary's earlier post that your best bet would be to start fresh with the Sixpack 1.2 system. Then that can be reconfigured to match your 4361 arrangement, or even better, use it to generate an entirely new VM system in second level and then bring it over to your 4361 when you have it just so.


Regards,
Bob

['\'Fish\' (David B. Trout)' [e-mail] [H390-VM]]

Post by ***@sbcglobal.net [H390-VM]
The reason that the channel program checks are occurring
is because there is insufficient main storage available
in order to IPL this system. This is evidenced by the CCWs
shown in Rich's log that he provided. The address in the
CCW is x'862000', and that address does not exist in a 2 MB
machine.

<snip>

(DOH!) <me: smacks self in forehead>

Good catch, Bob! I'm embarrassed to admit I completely missed that. I usually catch such things but for some reason I looked right past it this time.

You are of course completely correct. He just needs to increase his MAINSIZE value to, probably, 16 (MB) and try again. I'm sure it'll work a LOT better then.

Thanks for keeping me on my toes. :)

(and my apologies for missing the obvious!)

[Rich Alderson [e-mail] [H390-VM]]

 OK, that's embarassing. Set it back to 16MB and it runs beautifully.
Thank you all for your help and your patience.
Onward and upward!
Rich

Post by ***@sbcglobal.net [H390-VM]
The reason that the channel program checks are occurring
is because there is insufficient main storage available
in order to IPL this system. This is evidenced by the CCWs
shown in Rich's log that he provided. The address in the
CCW is x'862000', and that address does not exist in a 2 MB
machine.

<snip>

(DOH!) <me: smacks self in forehead>

Good catch, Bob! I'm embarrassed to admit I completely missed that. I usually catch such things but for some reason I looked right past it this time.

You are of course completely correct. He just needs to increase his MAINSIZE value to, probably, 16 (MB) and try again. I'm sure it'll work a LOT better then.

Thanks for keeping me on my toes. :)

(and my apologies for missing the obvious!)

['Dave Wade' [e-mail] [H390-VM]]

Rich,



If you build it without the V=R it should run in 2MB. The latest 1.2 6-pack IPL’s fine in 2MB of store..



Dave



From: H390-***@yahoogroups.com [mailto:H390-***@yahoogroups.com]
Sent: 25 June 2017 23:29
To: H390-***@yahoogroups.com
Subject: Re: [H390-VM] VM/370 installation & startup










OK, that's embarassing. Set it back to 16MB and it runs beautifully.



Thank you all for your help and your patience.



Onward and upward!



Rich

Post by ***@sbcglobal.net [H390-VM]
The reason that the channel program checks are occurring
is because there is insufficient main storage available
in order to IPL this system. This is evidenced by the CCWs
shown in Rich's log that he provided. The address in the
CCW is x'862000', and that address does not exist in a 2 MB
machine.

<snip>

(DOH!) <me: smacks self in forehead>

Good catch, Bob! I'm embarrassed to admit I completely missed that. I usually catch such things but for some reason I looked right past it this time.

You are of course completely correct. He just needs to increase his MAINSIZE value to, probably, 16 (MB) and try again. I'm sure it'll work a LOT better then.

Thanks for keeping me on my toes. :)

(and my apologies for missing the obvious!)

[Rich Alderson [e-mail] [H390-VM]]

Post by 'Dave Wade' ***@gmail.com [H390-VM]
If you build it without the V=R it should run in 2MB. The latest 1.2 6-pack IPL’s fine in 2MB of store..

Thanks, Dave!  I'll do that.  Putting up the 1.2 6-pack today, now that I know that Hercules is working and I wasn't. :-)
Rich


On Sunday, June 25, 2017 4:02 PM, "'Dave Wade' ***@gmail.com [H390-VM]" <H390-***@yahoogroups.com> wrote:


  Rich,   If you build it without the V=R it should run in 2MB. The latest 1.2 6-pack IPL’s fine in 2MB of store..  Dave  From: H390-***@yahoogroups.com [mailto:H390-***@yahoogroups.com]
Sent: 25 June 2017 23:29
To: H390-***@yahoogroups.com
Subject: Re: [H390-VM] VM/370 installation & startup  

Post by 'Dave Wade' ***@gmail.com [H390-VM]
The reason that the channel program checks are occurring
is because there is insufficient main storage available
in order to IPL this system. This is evidenced by the CCWs
shown in Rich's log that he provided. The address in the
CCW is x'862000', and that address does not exist in a 2 MB
machine.

<snip>

(DOH!) <me: smacks self in forehead>

Good catch, Bob! I'm embarrassed to admit I completely missed that. I usually catch such things but for some reason I looked right past it this time.

You are of course completely correct. He just needs to increase his MAINSIZE value to, probably, 16 (MB) and try again. I'm sure it'll work a LOT better then.

Thanks for keeping me on my toes. :)

(and my apologies for missing the obvious!)

['Dave G4UGM' [e-mail] [H390-VM]]

Rich,

I am a VM sysprog from a long long time ago. I remember how confusing Hercules was when I first started and the cold shoulders I got because my questions were silly.

Think of it as having a 43xx box delivered when you are used to a 360/67
 and there was no training


Dave



From: H390-***@yahoogroups.com [mailto:H390-***@yahoogroups.com]
Sent: 26 June 2017 19:30
To: H390-***@yahoogroups.com
Subject: Re: [H390-VM] VM/370 installation & startup

Post by 'Dave Wade' ***@gmail.com [H390-VM]
If you build it without the V=R it should run in 2MB. The latest 1.2 6-pack IPL’s fine in 2MB of store..

Thanks, Dave! I'll do that. Putting up the 1.2 6-pack today, now that I know that Hercules is working and I wasn't. :-)



Rich



On Sunday, June 25, 2017 4:02 PM, "'Dave Wade' ***@gmail.com <mailto:***@gmail.com> [H390-VM]" <H390-***@yahoogroups.com <mailto:H390-***@yahoogroups.com> > wrote:





Rich,



If you build it without the V=R it should run in 2MB. The latest 1.2 6-pack IPL’s fine in 2MB of store..



Dave



From: H390-***@yahoogroups.com <mailto:H390-***@yahoogroups.com> [mailto:H390-***@yahoogroups.com]
Sent: 25 June 2017 23:29
To: H390-***@yahoogroups.com <mailto:H390-***@yahoogroups.com>
Subject: Re: [H390-VM] VM/370 installation & startup









OK, that's embarassing. Set it back to 16MB and it runs beautifully.



Thank you all for your help and your patience.



Onward and upward!



Rich

Post by 'Dave Wade' ***@gmail.com [H390-VM]
The reason that the channel program checks are occurring
is because there is insufficient main storage available
in order to IPL this system. This is evidenced by the CCWs
shown in Rich's log that he provided. The address in the
CCW is x'862000', and that address does not exist in a 2 MB
machine.

<snip>

(DOH!) <me: smacks self in forehead>

Good catch, Bob! I'm embarrassed to admit I completely missed that. I usually catch such things but for some reason I looked right past it this time.

You are of course completely correct. He just needs to increase his MAINSIZE value to, probably, 16 (MB) and try again. I'm sure it'll work a LOT better then.

Thanks for keeping me on my toes. :)

(and my apologies for missing the obvious!)

[[e-mail] [H390-VM]]

Rich,

Try commenting out the 3215 consoles. I was able to get it to IPL this way.




Mark Gutzwiller

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
But seriously, when asking for help, you REALLY need to get into the habit of PROVIDING ENOUGH INFORMATION FOR PEOPLE TO HELP YOU!

Yes, thank you, I was an ass for thinking that in saying "the 4-pack VM system" people might have an idea of what might be in there. Mea maxima culpa.
(And here I sit, former customer service manager for a computer manufacturer. I really am embarassed about having made that assumption.)

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
We need to see both your Hercules configuration file and your .rc file as well.

I modified the default hercules.cnf to remove (comment out) the DOS stuff, substitute "4361" for "3081," and "hercules" for "herc370." Here's what I am using:


#
# NOTE - All entries for MVS and VS1 are commented out
# but should be compatable with MVS Turnkey system 3
#
#
# VMSYS and basic system VM Config file.
#
#
# This is in several sections
# First is the CPU setup
# then VM Stuff
# then MVS Stuff
# then VS1 Stuff
# eventually DOS/VS stuff if you can wait long enough
#
# All except CPU and VM is commented out but I hope later
# to have the system set up to run MVS and VS1 as turnkey systems
# under VM and perhaps even DOS/VS
#
CPUSERIAL 550042 # CPU serial number
CPUMODEL 4361 # CPU model number
MAINSIZE 2 # Main storage size in megabytes
XPNDSIZE 0 # Expanded storage size in megabytes
CNSLPORT 3270 # TCP port number to which consoles connect
NUMCPU 1 # Number of CPUs
LOADPARM 0120.... # IPL parameter
OSTAILOR VM # OS tailoring
PANRATE 100 # Panel refresh rate
#SYSEPOCH 1960 # Needed to suit VS/1
ARCHMODE S/370
HTTPPORT 8081
TZOFFSET +0000
#
#
# .-----------------------Device number
# | .-----------------Device type
# | | .---------File name and parameters
# | | |
# V V V
#--- ---- --------------------
# This is Basic VM Stuff
*
000C 3505 /hercules/vm/dummy eof
000D 3525 /hercules/vm/pun/punch00d.txt ascii
000E 1403 /hercules/vm/prt/print00e.txt
000F 1403 /hercules/vm/prt/print00f.txt
0010 3270
0008 3215
001F 3215
0040 3270
0041 3270
0042 3270
0043 3270
0044 3270
0045 3270
0046 3270
0047 3270
00C0 3270
00C1 3270
00C2 3270
*
*
0480 3420 *
0481 3420 *

*
0580 3420 *
0581 3420 *

# System pack on Chan 7
#0731 3330 /hercules/vm/vmsys1-3330-11-ckd
# Temp/Page 1 on Chan 8
#0831 3330 /hercules/vm/vmsys2-3330-11-ckd
# Temp/Page 2 on chan 9
#0931 3330 /hercules/vm/vmsys3-3330-11-ckd
# Lots of extra MDISK space
#0A31 3330 /hercules/vm/vmsys4-3330-11-ckd
#
# Packs on different channels for performance, as in the old days on real iron.

249 3350 /hercules/vm/vm3350-1-cckd
24a 3350 /hercules/vm/vm3350-2-cckd
24b 3350 /hercules/vm/vm3350-3-cckd
24c 3350 /hercules/vm/vm3350-4-cckd

#750 3350 /hercules/vm/vm50-a
#751 3350 /hercules/vm/vm50-b
#752 3350 /hercules/vm/vm50-c
#753 3350 /hercules/vm/vm50-d






## Next is MVS stuff
#
## .-----------------------------Device number
## | .------------------------Device type
## | | .--------------------File name
## | | |
## V V V
##--- ---- --------------------
#010C 3505 /hercules/dummy eof
#020c 3505 /hercules/dummy eof
##020c 3505 localhost:3505 sockdev ascii trunc eof
#030c 3505 /hercules/dummy eof
#
#010d 3525 /hercules/mvs/pch/pun10d.txt
#020d 3525 /hercules/mvs/pch/pun20d.txt
#030d 3525 /hercules/mvs/pch/pun30d.txt
#
#010e 1403 /hercules/mvs/prt/prt10e.txt
#010f 1403 /hercules/mvs/prt/prt10f.txt
#
#020e 1403 /hercules/mvs/prt/prt20e.txt
#020f 1403 /hercules/mvs/prt/prt20f.txt
#
#030e 1403 /hercules/mvs/prt/prt30e.txt
#030f 1403 /hercules/mvs/prt/prt30f.txt
#
#0131 2314 /hercules/mvs/dasd/sort01.131 ro sf=/hercules/mvs/shadow/sort01_1.131
#0132 2314 /hercules/mvs/dasd/sort02.132 ro sf=/hercules/mvs/shadow/sort02_1.132
#0133 2314 /hercules/mvs/dasd/sort03.133 ro sf=/hercules/mvs/shadow/sort03_1.133
#0134 2314 /hercules/mvs/dasd/sort04.134 ro sf=/hercules/mvs/shadow/sort04_1.134
#0135 2314 /hercules/mvs/dasd/sort05.135 ro sf=/hercules/mvs/shadow/sort05_1.135
#0136 2314 /hercules/mvs/dasd/sort06.136 ro sf=/hercules/mvs/shadow/sort06_1.136
#
#0140 3350 /hercules/mvs/dasd/work00.140 ro sf=/hercules/mvs/shadow/work00_1.140
#0148 3350 /hercules/mvs/dasd/mvsres.148 ro sf=/hercules/mvs/shadow/mvsres_1.148
#0149 3350 /hercules/mvs/dasd/smp001.149 ro sf=/hercules/mvs/shadow/smp001_1.149
#014a 3350 /hercules/mvs/dasd/smp002.14a ro sf=/hercules/mvs/shadow/smp002_1.14a
#014b 3350 /hercules/mvs/dasd/smp003.14b ro sf=/hercules/mvs/shadow/smp003_1.14b
#014c 3350 /hercules/mvs/dasd/smp004.14c ro sf=/hercules/mvs/shadow/smp004_1.14c
#
#
#0150 3330 /hercules/mvs/dasd/start1.150 ro sf=/hercules/mvs/shadow/start1_1.150
#0151 3330 /hercules/mvs/dasd/spool0.151 ro sf=/hercules/mvs/shadow/spool0_1.151
#0152 3330 /hercules/mvs/dasd/hasp00.152 ro sf=/hercules/mvs/shadow/hasp00_1.152
#
#0160 3340 /hercules/mvs/dasd/page00.160 ro sf=/hercules/mvs/shadow/page00_1.160
#0161 3340 /hercules/mvs/dasd/page01.161 ro sf=/hercules/mvs/shadow/page01_1.161
#0162 3340 /hercules/mvs/dasd/page02.162 ro sf=/hercules/mvs/shadow/page02_1.162
#
#0170 3375 /hercules/mvs/dasd/work01.170 ro sf=/hercules/mvs/shadow/work01_1.170
#
#0180 3380 /hercules/mvs/dasd/work02.180 ro sf=/hercules/mvs/shadow/work02_1.180
#
#0190 3390 /hercules/mvs/dasd/work03.190 ro sf=/hercules/mvs/shadow/work03_1.190
#0191 3390 /hercules/mvs/dasd/mvscat.191 ro sf=/hercules/mvs/shadow/mvscat_1.191
#
#0240 3350 /hercules/mvs/dasd/pub000.240 ro sf=/hercules/mvs/shadow/pub000_1.240
#0248 3350 /hercules/mvs/dasd/mvsdlb.248 ro sf=/hercules/mvs/shadow/mvsdlb_1.248
#
#0280 3380 /hercules/mvs/dasd/pub002.280 ro sf=/hercules/mvs/shadow/pub002_1.280
#
#0340 3350 /hercules/mvs/dasd/cbt000.340 ro sf=/hercules/mvs/shadow/cbt000_1.340
#0341 3350 /hercules/mvs/dasd/cbt001.341 ro sf=/hercules/mvs/shadow/cbt001_1.341
#0342 3350 /hercules/mvs/dasd/cbt002.342 ro sf=/hercules/mvs/shadow/cbt002_1.342
#0343 3350 /hercules/mvs/dasd/cbtcat.343 ro sf=/hercules/mvs/shadow/cbtcat_1.343
#
#0348 3350 /hercules/mvs/dasd/src000.348 ro sf=/hercules/mvs/shadow/src000_1.348
#0349 3350 /hercules/mvs/dasd/src001.349 ro sf=/hercules/mvs/shadow/src001_1.349
#034a 3350 /hercules/mvs/dasd/src002.34a ro sf=/hercules/mvs/shadow/src002_1.34a
#034b 3350 /hercules/mvs/dasd/srccat.34b ro sf=/hercules/mvs/shadow/srccat_1.34b
#
#0500 3088 ctct 30880 192.100.100.223 30880 2048
#0501 3088 ctct 30881 192.100.100.223 30881 2048
#
#0600 3088 ctct 30882 192.100.100.223 30882 2048
#0601 3088 ctct 30883 192.100.100.223 30883 2048
#
#
#
#
## Next is VS1 stuff
#
#
## .-----------------------------Device number
## | .------------------------Device type
## | | .--------------------File name
## | | |
## V V V
##--- ---- --------------------
##0488 3420 *
##014E 3350 /hercules/vs1/vsxres.14A ro sf=/hercules/vs1/shadow/vsxres.14A_1
##014F 3350 /hercules/vs1/vsxspl.14B ro sf=/hercules/vs1/shadow/vsxspl.14A_1
#
#
## Dos system volume
#
#024d 3350 /hercules/vm/sysres.3350
#024e 3350 /hercules/vm/mcat01.3350
#
#
#
#
#
#
The hercules.rc file is untouched:
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 5
*ipl 731
ipl 249
For completeness, here is the entirety of the configuration as shown by Hercules in response to an escape key at the command prompt after the .rc has executed:
Hercules CPU0000: 0% S/370 | Peripherals
| U Addr Modl Type Assignment
000A0000 00000007 24M.W..... | A 000C 3505 RDR /hercules/vm/dummy eof
PSW | B 000D 3525 PCH /hercules/vm/pun/punch00d.txt ascii
| C 000E 1403 PRT /hercules/vm/prt/print00e.txt print fcbck
00000C10 00000000 00000249 00000C60 | D 000F 1403 PRT /hercules/vm/prt/print00f.txt print fcbck
0 1 2 3 | E 0010 3270 DSP 127.0.0.1
00000000 00000000 00000000 00000000 | F 0008 3215 CON
4 5 6 7 | G 001F 3215 CON
00000000 00000000 00000000 00000000 | H 0040 3270 DSP 127.0.0.1
8 9 10 11 | I 0041 3270 DSP 127.0.0.1
00000800 00001800 00000000 00000000 | J 0042 3270 DSP 127.0.0.1
12 13 14 15 | K 0043 3270 DSP
GPR CR AR FPR | L 0044 3270 DSP
| M 0045 3270 DSP
ADDRESS: 00000000 DATA: 00000000 | N 0046 3270 DSP
| O 0047 3270 DSP
--------------------------------------| P 00C0 3270 DSP
0.00 0 STO DIS RST | Q 00C1 3270 DSP
MIPS SIO/s | R 00C2 3270 DSP
| S 0480 3420 TAPE *
STR STP EXT IPL PWR | T 0481 3420 TAPE *
| U 0580 3420 TAPE *
--------------------------------------| V 0581 3420 TAPE *
CPU | W 0249 3350 DASD /hercules/vm/vm3350-1-cckd [555 cyls]
00 STOPPED | X 024A 3350 DASD /hercules/vm/vm3350-2-cckd [555 cyls]
| Y 024B 3350 DASD /hercules/vm/vm3350-3-cckd [555 cyls]
| Z 024C 3350 DASD /hercules/vm/vm3350-4-cckd [555 cyls]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
Presuming your Hercules configuration is the same, the main Hercules panel (HMC = Hardware Maintenance Console, i.e. the screen where you see Hercules issue messages to)
is your VM/370 system's master console, not any of your x3270 windows.

From the Installation instructions included on the page http://www.hercules-390.eu/hercinst.html http://www.hercules-390.eu/hercinst.html


To start Hercules enter this command at the Unix or Windows command prompt: hercules [ -f filename ]
[ -d ]
[ -p dyndir ] [[-l dynmod ] ... ]
[ > logfile ]
... Next connect a tn3270 client to the console port (normally port 3270). The client will be connected to the first 3270 device address specified in the configuration file (this should be the master console address). If your master console is a 1052 or 3215, connect a telnet client instead of a tn3270 client. Now you can enter an ipl command from the control panel.


so color me confused by your statement that the HMC is the VM master console, as if that ought to be obvious to a blind horse. Moving on

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
/ena all
The '/' (slash) is the Hercules prompt character that indicates what follows is NOT a Hercules command but is rather a reply for that guest device (see: "http://www.hercules-390.eu/hercconf.html#consysc").
What the above command is doing is asking VM/370 to "enable all of its terminals.

Having some experience with VM, and a great deal more with SVS and MVS, 35 years ago when I was a systems programmer in the IBM world, as well as more recently in getting the 4361 up and running, I'm familiar with the CP ENABLE command, but you have no way of knowing that. The result, however, is not encouraging. I'm including only the last few lines following the execution of the "ipl 249" command in the .rc file:
...
HHCCP048I 0249:CCW=06862000 60001000
HHCCP075I 0249:Stat=0C20 Count=0000
HHCCP048I 0249:CCW=06862000 60001000
HHCCP075I 0249:Stat=0C20 Count=0000
HHCCP011I CPU0000: Disabled wait state
PSW=000A0000 00000007
/ena all
HHCPN139E Command "/ena" not found; enter '?' for list.
/cp ena all
HHCPN139E Command "/cp" not found; enter '?' for list.
Command ==>
So I'll ask again, with complete documentation, what is it that I am missing? Thank you for your assistance.


Rich


Rich Alderson
Vintage Computing Sr. Systems Engineer
Living Computers: Museum + Labs
2245 1st Avenue S
Seattle, WA 98134
mailto:***@...
http://www.LivingComputers.org/





On Thursday, June 22, 2017 3:11 PM, "''Fish' (David B. Trout)' ***@... [H390-VM]" <H390-***@yahoogroups.com> wrote:



Rich Alderson wrote:

[...]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
It starts off well, putting up 4 x3270 windows on my Windows
7 desktop and IPLing VM. At this point, the first window
should, I believe, be the system console, but I get nothing
after the Hercules logo. Modifying the hercules.rc file to
start only a single x3270 session does not change this behavior,
nor does eliminating the .rc file altogether and connecting
with Vista tn3270 or ZOC.
I'm clearly missing something, so I'm soliciting advice from
the group.

We need to see both your Hercules configuration file and your .rc file as well.

I don't have the 4-pack VM/370 system but I do have the 6-pack VM/370 system, which I believe is just a later version of the same thing. Looking at its Hercules configuration file I see:

[...]
# You can access the operator's console through the Hercules
# window, or you can launch a 3270 emulator and have the
# operator use it. For the former, ensure the next line is
# not commented.
0009 3215-C NOPROMPT
# For the latter, comment the above line and un-comment this
# line:
# 0010 3270 MOD4
[...]

Presuming your Hercules configuration is the same, the main Hercules panel (HMC = Hardware Maintenance Console, i.e. the screen where you see Hercules issue messages to) is your VM/370 system's master console, not any of your x3270 windows.

Presuming I'm correct (which is required until we can see your Hercules configuration file and .rc file), you might just need to enable your VM terminals:

On your VM/370 master operator console (which, as explained, is likely your main HERCULES window), enter the command:

/ena all

The '/' (slash) is the Hercules prompt character that indicates what follows is NOT a Hercules command but is rather a reply for that guest device (see: "http://www.hercules-390.eu/hercconf.html#consysc"). What the above command is doing is asking VM/370 to "enable all of its terminals.

Once you enter the above command, the VM/370 terminal logo should then appear on ALL of your x3270 terminals, and you should then be able to logon to VM/370 and use your system.

If you want to use an x3270 terminal for your VM/370 master console, then follow the comments in the Hercules configuration file snippet I've posted further above: comment out the 3215 statement and Uncomment the 3270 statement:

[...]
# 0009 3215-C NOPROMPT <-- comment out (prepend with '#')
0010 3270 MOD4 <-- Uncomment (remove '#')
[...]

Then when you IPL, your first x3270 terminal (the one identified as device 0010) *should* then be your VM/370 master operator console where you should see your VM/370 IPL messages appear.

I hope that helps.

(But seriously, when asking for help, you REALLY need to get into the habit of PROVIDING ENOUGH INFORMATION FOR PEOPLE TO HELP YOU! Please see: https://github.com/Fish-Git/AskForHelp)

--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
mail: ***@...

['\'Fish\' (David B. Trout)' [e-mail] [H390-VM]]

[...]

Post by Rich Alderson ***@yahoo.com [H390-VM]
I modified the default hercules.cnf to remove (comment out)
the DOS stuff, substitute "4361" for "3081," and "hercules"

[...]

Post by Rich Alderson ***@yahoo.com [H390-VM]
0010 3270
0008 3215
001F 3215
0040 3270
0041 3270

[...]

Post by Rich Alderson ***@yahoo.com [H390-VM]
249 3350 /hercules/vm/vm3350-1-cckd
24a 3350 /hercules/vm/vm3350-2-cckd
24b 3350 /hercules/vm/vm3350-3-cckd
24c 3350 /hercules/vm/vm3350-4-cckd

[...]

Post by Rich Alderson ***@yahoo.com [H390-VM]
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 1
sh x3270 -model 3279-2 -keymap alt localhost 3270 &
pause 5
*ipl 731
ipl 249

[...]

Post by Rich Alderson ***@yahoo.com [H390-VM]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
Presuming your Hercules configuration is the same, the
main Hercules panel (HMC = Hardware Maintenance Console,
i.e. the screen where you see Hercules issue messages to)
is your VM/370 system's master console, not any of your
x3270 windows.

From the Installation instructions included on the page
http://www.hercules-390.eu/hercinst.html

[...]

Post by Rich Alderson ***@yahoo.com [H390-VM]
"Next connect a tn3270 client to the console port
(normally port 3270). The client will be connected
to the first 3270 device address specified in the
configuration file (this should be the master console
address). If your master console is a 1052 or 3215,
connect a telnet client instead of a tn3270 client.
Now you can enter an ipl command from the control panel."
so color me confused by your statement that the HMC is the VM master
console, as if that ought to be obvious to a blind horse. Moving on

Not having anything more to go on, I was guessing that maybe the VM/370 master console was defined as an integrated 3215 device (3215-C) and not a 3270 display terminal. It appears I guessed wrong. My apologies.


[...]

Post by Rich Alderson ***@yahoo.com [H390-VM]
Having some experience with VM, and a great deal more with
SVS and MVS, 35 years ago when I was a systems programmer
in the IBM world, as well as more recently in getting the
4361 up and running, I'm familiar with the CP ENABLE command,
but you have no way of knowing that.

(Ouch!) Not so hard. :)

(Seriously though, I don't know what I was thinking. For some reason I completely missed your background and who I was talking to. It's obvious now you DO know wtf you're doing. Please forgive me.)

Post by Rich Alderson ***@yahoo.com [H390-VM]
The result, however, is not encouraging. I'm including only
the last few lines following the execution of the "ipl 249"
...
HHCCP048I 0249:CCW=06862000 60001000
HHCCP075I 0249:Stat=0C20 Count=0000
HHCCP048I 0249:CCW=06862000 60001000
HHCCP075I 0249:Stat=0C20 Count=0000
HHCCP011I CPU0000: Disabled wait state
PSW=000A0000 00000007
/ena all
HHCPN139E Command "/ena" not found; enter '?' for list.
/cp ena all
HHCPN139E Command "/cp" not found; enter '?' for list.
Command ==>
So I'll ask again, with complete documentation, what is it that
I am missing? Thank you for your assistance.

I'm not sure. This is just another guess. But since it's obvious no operating system is actually running even after IPLing one (as evidenced by the disabled wait state message, and no doubt caused by the I/O errors (Channel Program Checks) on your system residence device (249) that you IPL'ed from), THAT would explain why the Hercules logo remains (and no VM/370 logo is appearing) on all of your x3270 terminals.

So we need to find out why you are experiencing I/O errors on device 249 during IPL. Use the "t+249" command to enable CCW tracing on device 249 before you issue the IPL command. That should provide us with some additional information as to what's going on.

It would also be helpful to see a complete Hercules log file too.

['\'Fish\' (David B. Trout)' [e-mail] [H390-VM]]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [H390-VM]
It would also be helpful to see a complete Hercules log file too.

Never mind. I see it now.

[Gary [e-mail] [H390-VM]]

Hi Rich,

I went back to an original VM/370 4 pack archive file and found the
following information that might be helpful to you. I found a number of
configuration files in several embedded archives. They are named
vmsys.conf/cnf and hercules.conf/cnf.

Here are the terminal configurations that they had in common:

0010 3270
0008 3215
001F 3215
0040 3270
0041 3270
0042 3270
0043 3270
0044 3270
0045 3270
0046 3270
0047 3270
00C0 3270
00C1 3270
00C2 3270

Two of the files had the following changes.

*0010 3270
0009 3215-C .

The main operator consoles, traditionally have been at addresses 009 & 01F.

In this version of VM/370 is generated with a 3215 at address 008 in
addition to 009 & 01F. To use a 3215, you will need to use a Telnet
emulator instead of a 3270 emulator. The 3215 at address 009 has an
"-C" which tell Hercules to route the input/output to the Hercules
console. If you are using the HercGUI by "Fish" or HercStudio by Jacob
Dekel, the input/output can be routed to them.

The remainder are 3270 terminals including address 010. If you are
using this address as the operator console, you may need to press the
Enter key to tell CP this is the main console.

It is also possible to name the terminal groupings. The name is placed
after the terminal type. For example for the console in my
configuration file I have.

0010 3270 vm370con

When I start my 3270 for the console with "vmcons" as a parameter along
with the port to be used. You will need to check your emulator
documentation on how to specify that. This method ensures that the
emulator window that I want to use as the console remains the same.

To access a standard user 3270, I have the following definition:

0040.7 3270 vm370m2

I used the x3270 emulator in the past and used the following BASH script
fragment to start the terminal sessions.

sleep 2
x3270 -model 2 ***@localhost:3270 &
sleep 2
x3270 -model 2 ***@localhost:3270 &
sleep 2

I currently use the Vista TN3270 emulator running under Play on
Linux/Wine. It is a little more labor intensive to start and get
connected, but the trade-off for more flexibility is worth it for me.

If you have any questions, don't hesitate to ask.

Regards,

Gary

[Gregg Levine [e-mail] [H390-VM]]

Hello!
Gary can you point me to your selected release? I have here the
original 2 pack from Bob Abeles, and several releases of the 6 pack.
Also several individual items....

Dave W? What is that really lost and bored Yeti doing where you are?
-----
Gregg C Levine ***@gmail.com
"This signature fought the Time Wars, time and again."

Post by Gary ***@comcast.net [H390-VM]
Hi Rich,
I went back to an original VM/370 4 pack archive file and found the
following information that might be helpful to you. I found a number of
configuration files in several embedded archives. They are named
vmsys.conf/cnf and hercules.conf/cnf.
0010 3270
0008 3215
001F 3215
0040 3270
0041 3270
0042 3270
0043 3270
0044 3270
0045 3270
0046 3270
0047 3270
00C0 3270
00C1 3270
00C2 3270
Two of the files had the following changes.
*0010 3270
0009 3215-C .
The main operator consoles, traditionally have been at addresses 009 & 01F.
In this version of VM/370 is generated with a 3215 at address 008 in
addition to 009 & 01F. To use a 3215, you will need to use a Telnet
emulator instead of a 3270 emulator. The 3215 at address 009 has an
"-C" which tell Hercules to route the input/output to the Hercules
console. If you are using the HercGUI by "Fish" or HercStudio by Jacob
Dekel, the input/output can be routed to them.
The remainder are 3270 terminals including address 010. If you are
using this address as the operator console, you may need to press the
Enter key to tell CP this is the main console.
It is also possible to name the terminal groupings. The name is placed
after the terminal type. For example for the console in my
configuration file I have.
0010 3270 vm370con
When I start my 3270 for the console with "vmcons" as a parameter along
with the port to be used. You will need to check your emulator
documentation on how to specify that. This method ensures that the
emulator window that I want to use as the console remains the same.
0040.7 3270 vm370m2
I used the x3270 emulator in the past and used the following BASH script
fragment to start the terminal sessions.
sleep 2
sleep 2
sleep 2
I currently use the Vista TN3270 emulator running under Play on
Linux/Wine. It is a little more labor intensive to start and get
connected, but the trade-off for more flexibility is worth it for me.
If you have any questions, don't hesitate to ask.
Regards,
Gary
------------------------------------
------------------------------------
------------------------------------
Yahoo Groups Links

[Gary [e-mail] [H390-VM]]

Hi Greg,

The 4-Pack is by Andy Norrie and I found it years ago here:

http://www.cbttape.org/vm6.htm

There are a number of other goodies to be had by poking around the links
on that page. While the site is mostly dedicated to the MVS family
there are some VM items, most would have to be back ported to VM/370.

Any idea of if or when there will be a newer release of the 6-pack system?

Gary

['Dave Wade' [e-mail] [H390-VM]]

Gary,
Most of the links on that page are broken. They refuse to fix them, I think because they get people to buy the CD. The Oxford links have not worked for a very long time. You can find all the VM "n-pack" downloads here:-

http://www.smrcc.org.uk/members/g4ugm/VM370.htm

I would have thought if you had a 43xx machine you could run VM/SP4 or SP5 on it. I assume it didn't come with tapes?

Dave

-----Original Message-----
Sent: 23 June 2017 11:19
Subject: [H390-VM] Re: VM/370 installation & startup
Hi Greg,
http://www.cbttape.org/vm6.htm
There are a number of other goodies to be had by poking around the links on
that page. While the site is mostly dedicated to the MVS family there are
some VM items, most would have to be back ported to VM/370.
Any idea of if or when there will be a newer release of the 6-pack system?
Gary
------------------------------------
------------------------------------
------------------------------------
Yahoo Groups Links

[Rich Alderson [e-mail] [H390-VM]]

Post by 'Dave Wade' ***@gmail.com [H390-VM]
I would have thought if you had a 43xx machine you could run VM/SP4 or SP5 on it. I assume it didn't come with tapes?

The 4361 can run VM/SP, which is a licensed product. That's for the future. Right now we're running what is available without a license.
You assume correctly that the system did not come with tapes. As it happens, it was running DOS/VSE when we acquired it from the original owner.
Rich


On Friday, June 23, 2017 3:57 AM, "'Dave Wade' ***@gmail.com [H390-VM]" <H390-***@yahoogroups.com> wrote:


  Gary,
Most of the links on that page are broken. They refuse to fix them, I think because they get people to buy the CD. The Oxford links have not worked for a very long time. You can find all the VM "n-pack" downloads here:-

http://www.smrcc.org.uk/members/g4ugm/VM370.htm

I would have thought if you had a 43xx machine you could run VM/SP4 or SP5 on it. I assume it didn't come with tapes?

Dave

Post by 'Dave Wade' ***@gmail.com [H390-VM]
-----Original Message-----
Sent: 23 June 2017 11:19
Subject: [H390-VM] Re: VM/370 installation & startup
Hi Greg,
http://www.cbttape.org/vm6.htm
There are a number of other goodies to be had by poking around the links on
that page. While the site is mostly dedicated to the MVS family there are
some VM items, most would have to be back ported to VM/370.
Any idea of if or when there will be a newer release of the 6-pack system?
Gary
------------------------------------
------------------------------------
------------------------------------
Yahoo Groups Links

#yiv9706672982 #yiv9706672982 -- #yiv9706672982ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv9706672982 #yiv9706672982ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv9706672982 #yiv9706672982ygrp-mkp #yiv9706672982hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv9706672982 #yiv9706672982ygrp-mkp #yiv9706672982ads {margin-bottom:10px;}#yiv9706672982 #yiv9706672982ygrp-mkp .yiv9706672982ad {padding:0 0;}#yiv9706672982 #yiv9706672982ygrp-mkp .yiv9706672982ad p {margin:0;}#yiv9706672982 #yiv9706672982ygrp-mkp .yiv9706672982ad a {color:#0000ff;text-decoration:none;}#yiv9706672982 #yiv9706672982ygrp-sponsor #yiv9706672982ygrp-lc {font-family:Arial;}#yiv9706672982 #yiv9706672982ygrp-sponsor #yiv9706672982ygrp-lc #yiv9706672982hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv9706672982 #yiv9706672982ygrp-sponsor #yiv9706672982ygrp-lc .yiv9706672982ad {margin-bottom:10px;padding:0 0;}#yiv9706672982 #yiv9706672982actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv9706672982 #yiv9706672982activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv9706672982 #yiv9706672982activity span {font-weight:700;}#yiv9706672982 #yiv9706672982activity span:first-child {text-transform:uppercase;}#yiv9706672982 #yiv9706672982activity span a {color:#5085b6;text-decoration:none;}#yiv9706672982 #yiv9706672982activity span span {color:#ff7900;}#yiv9706672982 #yiv9706672982activity span .yiv9706672982underline {text-decoration:underline;}#yiv9706672982 .yiv9706672982attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv9706672982 .yiv9706672982attach div a {text-decoration:none;}#yiv9706672982 .yiv9706672982attach img {border:none;padding-right:5px;}#yiv9706672982 .yiv9706672982attach label {display:block;margin-bottom:5px;}#yiv9706672982 .yiv9706672982attach label a {text-decoration:none;}#yiv9706672982 blockquote {margin:0 0 0 4px;}#yiv9706672982 .yiv9706672982bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv9706672982 .yiv9706672982bold a {text-decoration:none;}#yiv9706672982 dd.yiv9706672982last p a {font-family:Verdana;font-weight:700;}#yiv9706672982 dd.yiv9706672982last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv9706672982 dd.yiv9706672982last p span.yiv9706672982yshortcuts {margin-right:0;}#yiv9706672982 div.yiv9706672982attach-table div div a {text-decoration:none;}#yiv9706672982 div.yiv9706672982attach-table {width:400px;}#yiv9706672982 div.yiv9706672982file-title a, #yiv9706672982 div.yiv9706672982file-title a:active, #yiv9706672982 div.yiv9706672982file-title a:hover, #yiv9706672982 div.yiv9706672982file-title a:visited {text-decoration:none;}#yiv9706672982 div.yiv9706672982photo-title a, #yiv9706672982 div.yiv9706672982photo-title a:active, #yiv9706672982 div.yiv9706672982photo-title a:hover, #yiv9706672982 div.yiv9706672982photo-title a:visited {text-decoration:none;}#yiv9706672982 div#yiv9706672982ygrp-mlmsg #yiv9706672982ygrp-msg p a span.yiv9706672982yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv9706672982 .yiv9706672982green {color:#628c2a;}#yiv9706672982 .yiv9706672982MsoNormal {margin:0 0 0 0;}#yiv9706672982 o {font-size:0;}#yiv9706672982 #yiv9706672982photos div {float:left;width:72px;}#yiv9706672982 #yiv9706672982photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv9706672982 #yiv9706672982photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv9706672982 #yiv9706672982reco-category {font-size:77%;}#yiv9706672982 #yiv9706672982reco-desc {font-size:77%;}#yiv9706672982 .yiv9706672982replbq {margin:4px;}#yiv9706672982 #yiv9706672982ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv9706672982 #yiv9706672982ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv9706672982 #yiv9706672982ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv9706672982 #yiv9706672982ygrp-mlmsg select, #yiv9706672982 input, #yiv9706672982 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv9706672982 #yiv9706672982ygrp-mlmsg pre, #yiv9706672982 code {font:115% monospace;}#yiv9706672982 #yiv9706672982ygrp-mlmsg * {line-height:1.22em;}#yiv9706672982 #yiv9706672982ygrp-mlmsg #yiv9706672982logo {padding-bottom:10px;}#yiv9706672982 #yiv9706672982ygrp-msg p a {font-family:Verdana;}#yiv9706672982 #yiv9706672982ygrp-msg p#yiv9706672982attach-count span {color:#1E66AE;font-weight:700;}#yiv9706672982 #yiv9706672982ygrp-reco #yiv9706672982reco-head {color:#ff7900;font-weight:700;}#yiv9706672982 #yiv9706672982ygrp-reco {margin-bottom:20px;padding:0px;}#yiv9706672982 #yiv9706672982ygrp-sponsor #yiv9706672982ov li a {font-size:130%;text-decoration:none;}#yiv9706672982 #yiv9706672982ygrp-sponsor #yiv9706672982ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv9706672982 #yiv9706672982ygrp-sponsor #yiv9706672982ov ul {margin:0;padding:0 0 0 8px;}#yiv9706672982 #yiv9706672982ygrp-text {font-family:Georgia;}#yiv9706672982 #yiv9706672982ygrp-text p {margin:0 0 1em 0;}#yiv9706672982 #yiv9706672982ygrp-text tt {font-size:120%;}#yiv9706672982 #yiv9706672982ygrp-vital ul li:last-child {border-right:none !important;}#yiv9706672982

[[e-mail] [H390-VM]]

Dave,

You are correct. It was late and I didn't take the time to check the links. My bad Greg.


Rich,


Not knowing your background or what you mave have in the way of HW/SW I'm going to make some suggestions based on starting from scratch.


1. Go to Dave website and get the VM/370 Sixpack version 1.2 files.


2. Install the latest version of Hercules from your Distros Software Manager or go to the Hercules 390 website and install from source version 3.12.


3. Go to Bitsavers and get the VM/370 manuals and the DDR (Dasd Dump Restore) manual.


4. Go to the Files directory here in the group and snag the Diag58v200 file. It adds some additional software to enable full screen editing and other features.


5. Follow the following link to get the invalue "What Mother Never Told You About VM Service". While you most likely will not be doing VM maintenance, it does share some how's and why's for modifying a VM system. I learned a lot from this after my first attempt at applying service went miserably. I had to DDR the nucleus back because the IPL died.


6. The newest version of the Sixpack uses more automation than I like. I'm Ancient school and like to see blinking lights and push (click) buttons. I use the HercStudio emulator. You might find that in your Distros Software Manager.


You stated that all of this is in preparation for installing on real hardware. Once you get VM/370 up and running I would suggest that you create a second level VM guest to test your changes with. Working in that way is closer to what will be happening when you are on the real hardware. I did the upgrade from VM/SP 3 to SP 5 this way.


Another option is 2 separate Hercules configurations. One for the 3350 version and the other for the 3340 version. The 2 versions will need to share some common disks.


If you have any questions about working second level, just ask.


Gary

[[e-mail] [H390-VM]]

Disabled wait state is the way that system generate errors when the normal error systems don't work.

(Otherwise, the PSW should never be odd.)

The low bits of the PSW are the code to look up in a manual.

Interestingly, if you google for "000a0000-00000007"

you get the page:

https://docops.ca.com/ca-top-secret-for-z-vm/12-1/en/messages-and-return-codes/server-wait-state-codes/psw-x-000a0000-00000007/ https://docops.ca.com/ca-top-secret-for-z-vm/12-1/en/messages-and-return-codes/server-wait-state-codes/psw-x-000a0000-00000007/

which is a wait state code for z/VM.

with the explanation: "DASD 100 does not contain enough nucleus area"

I will make a wild guess here, that your emulated CPU
doesn't have enough memory for the system you are trying
to IPL.

Otherwise, devices that don't match the I/O configuration of the
system you are IPLing could also do it. At sysgen, you specify
which devices are at which channel addresses. The low ones
don't change much, such as the console, card reader, card punch,
and printer.

There is more variation for tape and disk drives, and getting the IPL
device right is pretty important. If your configuration says that
the IPL device is a different type of disk, then disk addressing won't
work right.

[[e-mail] [H390-VM]]

Wait state codes are in:

http://bitsavers.trailing-edge.com/pdf/ibm/370/VM_370/Release_3/GC20-1808-7_VM370_System_Messages_Rel_3_PLC_8_Oct76.pdf http://bitsavers.trailing-edge.com/pdf/ibm/370/VM_370/Release_3/GC20-1808-7_VM370_System_Messages_Rel_3_PLC_8_Oct76.pdf

but it isn't at all obvious to me what caused it.

[Rich Alderson [e-mail] [H390-VM]]

Thanks, Glen! Set MAINSIZE back to 16 and it works perfectly. Oh, well.


On Friday, June 23, 2017 10:27 PM, "***@ugcs.caltech.edu [H390-VM]" <H390-***@yahoogroups.com> wrote:


  Wait state codes are in:

http://bitsavers.trailing-edge.com/pdf/ibm/370/VM_370/Release_3/GC20-1808-7_VM370_System_Messages_Rel_3_PLC_8_Oct76.pdf

but it isn't at all obvious to me what caused it. #yiv3038890941 #yiv3038890941 -- #yiv3038890941ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv3038890941 #yiv3038890941ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv3038890941 #yiv3038890941ygrp-mkp #yiv3038890941hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv3038890941 #yiv3038890941ygrp-mkp #yiv3038890941ads {margin-bottom:10px;}#yiv3038890941 #yiv3038890941ygrp-mkp .yiv3038890941ad {padding:0 0;}#yiv3038890941 #yiv3038890941ygrp-mkp .yiv3038890941ad p {margin:0;}#yiv3038890941 #yiv3038890941ygrp-mkp .yiv3038890941ad a {color:#0000ff;text-decoration:none;}#yiv3038890941 #yiv3038890941ygrp-sponsor #yiv3038890941ygrp-lc {font-family:Arial;}#yiv3038890941 #yiv3038890941ygrp-sponsor #yiv3038890941ygrp-lc #yiv3038890941hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv3038890941 #yiv3038890941ygrp-sponsor #yiv3038890941ygrp-lc .yiv3038890941ad {margin-bottom:10px;padding:0 0;}#yiv3038890941 #yiv3038890941actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv3038890941 #yiv3038890941activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv3038890941 #yiv3038890941activity span {font-weight:700;}#yiv3038890941 #yiv3038890941activity span:first-child {text-transform:uppercase;}#yiv3038890941 #yiv3038890941activity span a {color:#5085b6;text-decoration:none;}#yiv3038890941 #yiv3038890941activity span span {color:#ff7900;}#yiv3038890941 #yiv3038890941activity span .yiv3038890941underline {text-decoration:underline;}#yiv3038890941 .yiv3038890941attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv3038890941 .yiv3038890941attach div a {text-decoration:none;}#yiv3038890941 .yiv3038890941attach img {border:none;padding-right:5px;}#yiv3038890941 .yiv3038890941attach label {display:block;margin-bottom:5px;}#yiv3038890941 .yiv3038890941attach label a {text-decoration:none;}#yiv3038890941 blockquote {margin:0 0 0 4px;}#yiv3038890941 .yiv3038890941bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv3038890941 .yiv3038890941bold a {text-decoration:none;}#yiv3038890941 dd.yiv3038890941last p a {font-family:Verdana;font-weight:700;}#yiv3038890941 dd.yiv3038890941last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv3038890941 dd.yiv3038890941last p span.yiv3038890941yshortcuts {margin-right:0;}#yiv3038890941 div.yiv3038890941attach-table div div a {text-decoration:none;}#yiv3038890941 div.yiv3038890941attach-table {width:400px;}#yiv3038890941 div.yiv3038890941file-title a, #yiv3038890941 div.yiv3038890941file-title a:active, #yiv3038890941 div.yiv3038890941file-title a:hover, #yiv3038890941 div.yiv3038890941file-title a:visited {text-decoration:none;}#yiv3038890941 div.yiv3038890941photo-title a, #yiv3038890941 div.yiv3038890941photo-title a:active, #yiv3038890941 div.yiv3038890941photo-title a:hover, #yiv3038890941 div.yiv3038890941photo-title a:visited {text-decoration:none;}#yiv3038890941 div#yiv3038890941ygrp-mlmsg #yiv3038890941ygrp-msg p a span.yiv3038890941yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv3038890941 .yiv3038890941green {color:#628c2a;}#yiv3038890941 .yiv3038890941MsoNormal {margin:0 0 0 0;}#yiv3038890941 o {font-size:0;}#yiv3038890941 #yiv3038890941photos div {float:left;width:72px;}#yiv3038890941 #yiv3038890941photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv3038890941 #yiv3038890941photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv3038890941 #yiv3038890941reco-category {font-size:77%;}#yiv3038890941 #yiv3038890941reco-desc {font-size:77%;}#yiv3038890941 .yiv3038890941replbq {margin:4px;}#yiv3038890941 #yiv3038890941ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv3038890941 #yiv3038890941ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv3038890941 #yiv3038890941ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv3038890941 #yiv3038890941ygrp-mlmsg select, #yiv3038890941 input, #yiv3038890941 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv3038890941 #yiv3038890941ygrp-mlmsg pre, #yiv3038890941 code {font:115% monospace;}#yiv3038890941 #yiv3038890941ygrp-mlmsg * {line-height:1.22em;}#yiv3038890941 #yiv3038890941ygrp-mlmsg #yiv3038890941logo {padding-bottom:10px;}#yiv3038890941 #yiv3038890941ygrp-msg p a {font-family:Verdana;}#yiv3038890941 #yiv3038890941ygrp-msg p#yiv3038890941attach-count span {color:#1E66AE;font-weight:700;}#yiv3038890941 #yiv3038890941ygrp-reco #yiv3038890941reco-head {color:#ff7900;font-weight:700;}#yiv3038890941 #yiv3038890941ygrp-reco {margin-bottom:20px;padding:0px;}#yiv3038890941 #yiv3038890941ygrp-sponsor #yiv3038890941ov li a {font-size:130%;text-decoration:none;}#yiv3038890941 #yiv3038890941ygrp-sponsor #yiv3038890941ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv3038890941 #yiv3038890941ygrp-sponsor #yiv3038890941ov ul {margin:0;padding:0 0 0 8px;}#yiv3038890941 #yiv3038890941ygrp-text {font-family:Georgia;}#yiv3038890941 #yiv3038890941ygrp-text p {margin:0 0 1em 0;}#yiv3038890941 #yiv3038890941ygrp-text tt {font-size:120%;}#yiv3038890941 #yiv3038890941ygrp-vital ul li:last-child {border-right:none !important;}#yiv3038890941

[Jason Kirby [e-mail] [H390-VM]]

________________________________
From: H390-***@yahoogroups.com <H390-***@yahoogroups.com> on behalf of Gary ***@comcast.net [H390-VM] <H390-***@yahoogroups.com>
Sent: Friday, June 23, 2017 6:18 AM
To: H390-***@yahoogroups.com
Subject: [H390-VM] Re: VM/370 installation & startup



Hi Greg,

The 4-Pack is by Andy Norrie and I found it years ago here:

http://www.cbttape.org/vm6.htm

There are a number of other goodies to be had by poking around the links
on that page. While the site is mostly dedicated to the MVS family
there are some VM items, most would have to be back ported to VM/370.

Any idea of if or when there will be a newer release of the 6-pack system?

Gary

[Joe Monk [e-mail] [H390-VM]]

Wrong address.

h390-vm-***@yahoo.com

Joe

Post by Gary ***@comcast.net [H390-VM]
------------------------------
*Sent:* Friday, June 23, 2017 6:18 AM
*Subject:* [H390-VM] Re: VM/370 installation & startup
Hi Greg,
http://www.cbttape.org/vm6.htm
There are a number of other goodies to be had by poking around the links
on that page. While the site is mostly dedicated to the MVS family
there are some VM items, most would have to be back ported to VM/370.
Any idea of if or when there will be a newer release of the 6-pack system?
Gary

['Dave Wade' [e-mail] [H390-VM]]

Use the links in the bottom of the e-mail.



From: H390-***@yahoogroups.com [mailto:H390-***@yahoogroups.com]
Sent: 23 June 2017 13:05
To: H390-***@yahoogroups.com
Subject: [H390-VM] unsubscribe












_____

From: H390-***@yahoogroups.com <mailto:H390-***@yahoogroups.com>
<H390-***@yahoogroups.com <mailto:H390-***@yahoogroups.com> > on behalf of
Gary ***@comcast.net <mailto:***@comcast.net> [H390-VM]
<H390-***@yahoogroups.com <mailto:H390-***@yahoogroups.com> >
Sent: Friday, June 23, 2017 6:18 AM
To: H390-***@yahoogroups.com <mailto:H390-***@yahoogroups.com>
Subject: [H390-VM] Re: VM/370 installation & startup





Hi Greg,

The 4-Pack is by Andy Norrie and I found it years ago here:

http://www.cbttape.org/vm6.htm

There are a number of other goodies to be had by poking around the links
on that page. While the site is mostly dedicated to the MVS family
there are some VM items, most would have to be back ported to VM/370.

Any idea of if or when there will be a newer release of the 6-pack system?

Gary

[Gregg Levine [e-mail] [H390-VM]]

Hello!
If you really want to do that, please that address in the footer, or
please go to the site,
-----
Gregg C Levine ***@gmail.com
"This signature fought the Time Wars, time and again."

Post by Jason Kirby ***@hotmail.com [H390-VM]
________________________________
Sent: Friday, June 23, 2017 6:18 AM
Subject: [H390-VM] Re: VM/370 installation & startup
Hi Greg,
http://www.cbttape.org/vm6.htm
There are a number of other goodies to be had by poking around the links
on that page. While the site is mostly dedicated to the MVS family
there are some VM items, most would have to be back ported to VM/370.
Any idea of if or when there will be a newer release of the 6-pack system?
Gary