[hercules-390] Starting VM/370

[Michael Short [e-mail] [hercules-390]]

I'm hitting a snag starting VM/370. I'm using
Hercules-4.00.0-git-8119-gca365ac-x64. The problem occurs in the
Hercules.rc file which has a /enable all and I get the follow error:

HHC01603I /enable all

HHC01600E Unknown command /enable, enter 'help' for a list of valid commands

The readme indicates that this should be passed to the Operator to be
acted upon.

Any ideas why the command is not being recognized.

[Mike Schwab [e-mail] [hercules-390]]

Need a period before the slash to send it to the operating system.

I'm hitting a snag starting VM/370. I'm using Hercules-4.00.0-git-8119-gca365ac-x64.
The problem occurs in the Hercules.rc file which has a /enable all and I
HHC01603I /enable all
HHC01600E Unknown command /enable, enter 'help' for a list of valid commands
The readme indicates that this should be passed to the Operator to be
acted upon.
Any ideas why the command is not being recognized.

[Gregg Levine [e-mail] [hercules-390]]

Hello!
Oh mynock muffins! I missed that one. Thank's Mike.
Michael Short, try that.

And are you a member of the two VM/370 groups?
-----
Gregg C Levine ***@gmail.com
"This signature fought the Time Wars, time and again."

Post by Mike Schwab ***@gmail.com [hercules-390]
Need a period before the slash to send it to the operating system.

Post by Michael Short ***@gmail.com [hercules-390]
I'm hitting a snag starting VM/370. I'm using
Hercules-4.00.0-git-8119-gca365ac-x64. The problem occurs in the Hercules.rc
HHC01603I /enable all
HHC01600E Unknown command /enable, enter 'help' for a list of valid commands
The readme indicates that this should be passed to the Operator to be
acted upon.
Any ideas why the command is not being recognized.

--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

[Gregg Levine [e-mail] [hercules-390]]

Hello!
Yes it should. I typically, for Hercules-3.13, send it to the console
that's opened by using telnet to the chosen port. You're trying this
out via the six pack series, correct? I'd say we've a problem
someplace.

And II'd be curious to find out what caused it.
-----
Strange? What's that big hairy something else doing in the rain in the
driveway of an individual who uses fins to communicate.?
-----
Gregg C Levine ***@gmail.com
"This signature fought the Time Wars, time and again."


On Thu, Dec 14, 2017 at 9:27 PM, Michael Short

Post by Michael Short ***@gmail.com [hercules-390]
I'm hitting a snag starting VM/370. I'm using
Hercules-4.00.0-git-8119-gca365ac-x64. The problem occurs in the Hercules.rc
HHC01603I /enable all
HHC01600E Unknown command /enable, enter 'help' for a list of valid commands
The readme indicates that this should be passed to the Operator to be acted
upon.
Any ideas why the command is not being recognized.
________________________________

['Dave Wade' [e-mail] [hercules-390]]

Possibly the default console escape character has changed, or you have changed the config to use a remote telnet console..

Dave

-----Original Message-----
Sent: 15 December 2017 02:44
Subject: Re: [hercules-390] Starting VM/370
Hello!
Yes it should. I typically, for Hercules-3.13, send it to the console that's
opened by using telnet to the chosen port. You're trying this out via the six
pack series, correct? I'd say we've a problem someplace.
And II'd be curious to find out what caused it.
-----
Strange? What's that big hairy something else doing in the rain in the
driveway of an individual who uses fins to communicate.?
-----
"This signature fought the Time Wars, time and again."

Post by Michael Short ***@gmail.com [hercules-390]
I'm hitting a snag starting VM/370. I'm using
Hercules-4.00.0-git-8119-gca365ac-x64. The problem occurs in the
HHC01603I /enable all
HHC01600E Unknown command /enable, enter 'help' for a list of valid commands
The readme indicates that this should be passed to the Operator to be
acted upon.
Any ideas why the command is not being recognized.
________________________________

------------------------------------
------------------------------------
http://groups.yahoo.com/group/hercules-390
http://www.hercules-390.org
------------------------------------
Yahoo Groups Links

[Michael Short [e-mail] [hercules-390]]

I'm using the 1,.3 Beta and have only edited the config file to change the
type of console. I got the system to come up once.

The . in front of the / solved the "invalid command" problem, but now I'm
getting
HHC00002E SCLP console not receiving operator commands. This seems to
indicate that possibly VM is not starting properly.

Since I haven't done anything with the system, it might appropriate to unzip
the components and try from a fresh copy.

Post by 'Dave Wade' ***@gmail.com [hercules-390]
Possibly the default console escape character has changed, or you have
changed the config to use a remote telnet console..
Dave

-----Original Message-----
Sent: 15 December 2017 02:44
Subject: Re: [hercules-390] Starting VM/370
Hello!
Yes it should. I typically, for Hercules-3.13, send it to the console

that's

opened by using telnet to the chosen port. You're trying this out via

the six

pack series, correct? I'd say we've a problem someplace.
And II'd be curious to find out what caused it.
-----
Strange? What's that big hairy something else doing in the rain in the
driveway of an individual who uses fins to communicate.?
-----
"This signature fought the Time Wars, time and again."
On Thu, Dec 14, 2017 at 9:27 PM, Michael Short

Post by Michael Short ***@gmail.com [hercules-390]
I'm hitting a snag starting VM/370. I'm using
Hercules-4.00.0-git-8119-gca365ac-x64. The problem occurs in the
HHC01603I /enable all
HHC01600E Unknown command /enable, enter 'help' for a list of valid commands
The readme indicates that this should be passed to the Operator to be
acted upon.
Any ideas why the command is not being recognized.
________________________________

------------------------------------
------------------------------------
http://groups.yahoo.com/group/hercules-390
http://www.hercules-390.org
------------------------------------
Yahoo Groups Links

[Ivan Warren [e-mail] [hercules-390]]

Post by Michael Short ***@gmail.com [hercules-390]
I'm using the 1,.3 Beta and have only edited the config file to change the
type of console. I got the system to come up once.
The . in front of the / solved the "invalid command" problem, but now
I'm getting
HHC00002E SCLP console not receiving operator commands. This seems to
indicate that possibly VM is not starting properly.
Since I haven't done anything with the system, it might appropriate to unzip
the components and try from a fresh copy.

Michael,

VM/370 never supported the SCLP console. It only supports a 3215 or 3270
console.

--Ivan


[Non-text portions of this message have been removed]

['Dave Wade' [e-mail] [hercules-390]]

So what is actually wrong! Well the “/” says send the command to the Hercules Integrated console (one with -C on its config line) that has “/” as its routing character, but you changed it to a telnet console, so there is nowhere to send it.



Adding the “.” Says send it to the “SCP SYSCONS” interface, but this is a concept that VM/370R6 does not understand, so there is nowhere to send it, so it didn’t solve the problem.



So if you put the console back to the “-C” console it will work, or if you comment out the “/enable all” (prefix with a “*”) in the hercules.rc file all will be well.



As someone else pointed out the “/enable all” is not needed the as AUTOLOG1 user issues an “enable all” command. I think it was changed a long time ago because with many 3270 devices defined it was slowing AUTOLOG1 processing.



Dave



From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: 15 December 2017 15:15
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Starting VM/370








I'm using the 1,.3 Beta and have only edited the config file to change the

type of console. I got the system to come up once.



The . in front of the / solved the "invalid command" problem, but now I'm getting

HHC00002E SCLP console not receiving operator commands. This seems to

indicate that possibly VM is not starting properly.



Since I haven't done anything with the system, it might appropriate to unzip

the components and try from a fresh copy.



On Fri, Dec 15, 2017 at 4:09 AM, 'Dave Wade' ***@gmail.com <mailto:***@gmail.com> [hercules-390] <hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> > wrote:



Possibly the default console escape character has changed, or you have changed the config to use a remote telnet console..

Dave

-----Original Message-----
Sent: 15 December 2017 02:44
Subject: Re: [hercules-390] Starting VM/370
Hello!
Yes it should. I typically, for Hercules-3.13, send it to the console that's
opened by using telnet to the chosen port. You're trying this out via the six
pack series, correct? I'd say we've a problem someplace.
And II'd be curious to find out what caused it.
-----
Strange? What's that big hairy something else doing in the rain in the
driveway of an individual who uses fins to communicate.?
-----
"This signature fought the Time Wars, time and again."

Post by Michael Short ***@gmail.com [hercules-390]
I'm hitting a snag starting VM/370. I'm using
Hercules-4.00.0-git-8119-gca365ac-x64. The problem occurs in the
HHC01603I /enable all
HHC01600E Unknown command /enable, enter 'help' for a list of valid commands
The readme indicates that this should be passed to the Operator to be
acted upon.
Any ideas why the command is not being recognized.
________________________________

------------------------------------
------------------------------------
http://groups.yahoo.com/group/hercules-390
http://www.hercules-390.org
------------------------------------
Yahoo Groups Links

[[e-mail] [hercules-390]]

Post by Michael Short ***@gmail.com [hercules-390]
I'm hitting a snag starting VM/370. I'm using
Hercules-4.00.0-git-8119-gca365ac-x64. The
problem occurs in the Hercules.rc file which
HHC01603I /enable all
HHC01600E Unknown command /enable, enter 'help' for a list of valid commands

What do you have in your sixpack.conf here:


# 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





I think the default for Hercules 3.07 is "/"
and my system seems to work with "/".
You might want to try an older Hercules.


BFN. Paul.

[Mike Stramba [e-mail] [hercules-390]]

Hi Michael,

Which vm (sixpack ?) are you using?

AFAiK any "external" (to the guest) "enable" commands should not be
necessary, as there is an AUTOLOG1 user that will issue the enable at
IPL time.

You can edit AUTOLOG1's PROFILE EXEC if necessary.

Mike

Post by Michael Short ***@gmail.com [hercules-390]
I'm hitting a snag starting VM/370. I'm using
Hercules-4.00.0-git-8119-gca365ac-x64. The problem occurs in the
HHC01603I /enable all
HHC01600E Unknown command /enable, enter 'help' for a list of valid commands
The readme indicates that this should be passed to the Operator to be
acted upon.
Any ideas why the command is not being recognized.

[Peter Coghlan [e-mail] [hercules-390]]

As someone else pointed out the "/enable all" is not needed the as AUTOLOG1
user issues an "enable all" command. I think it was changed a long time ago
because with many 3270 devices defined it was slowing AUTOLOG1 processing.

There is another possible reason ENABLE ALL fell out of favour.

Some time ago, support for different sized 3270 screens was added to VM/370
by HRC101DK I think. This introduced a bug in ENABLE. If one terminal is
enabled, there is no problem. If more than one terminal of the same type
is enabled, there is no problem. If two or more terminals of differents sizes
are enabled by the same command, the same logo screen is sent to all the
terminals and is displayed properly on some and mangled on others because it
is the wrong size for them.

Therefore if different sized terminals are in use, ENABLE ALL should probably
be avoided except by those who are not paniced by the mangled logos.

Regards,
Peter Coghlan.

['Dave Wade' [e-mail] [hercules-390]]

-----Original Message-----
Sent: 15 December 2017 18:16
Subject: Re: [hercules-390] Starting VM/370

As someone else pointed out the "/enable all" is not needed the as
AUTOLOG1 user issues an "enable all" command. I think it was changed a
long time ago because with many 3270 devices defined it was slowing

AUTOLOG1 processing.
There is another possible reason ENABLE ALL fell out of favour.
Some time ago, support for different sized 3270 screens was added to
VM/370 by HRC101DK I think. This introduced a bug in ENABLE. If one
terminal is enabled, there is no problem. If more than one terminal of

the

same type is enabled, there is no problem. If two or more terminals of
differents sizes are enabled by the same command, the same logo screen is
sent to all the terminals and is displayed properly on some and mangled on
others because it is the wrong size for them.
Therefore if different sized terminals are in use, ENABLE ALL should probably
be avoided except by those who are not paniced by the mangled logos.

That would be good if the command in the HERCULES.RC file was different to
the one in the AUTOLOG1 PROFILE EXEC file.
But they are not, well not quite, the hercules.rc file says "ENABLE ALL" the
PROFILE EXEC says "CP ENA ALL"...
... which effectively are the same

Regards,
Peter Coghlan.

Dave

------------------------------------
------------------------------------
http://groups.yahoo.com/group/hercules-390
http://www.hercules-390.org
------------------------------------
Yahoo Groups Links

[Michael Short [e-mail] [hercules-390]]

Thanks for all of the input on start up. The solution for me was to use
0009 for the console which put VM's console on Hercules'
console. Did have to issue the ENABLE ALL since AUTOLOG1
doesn't do it.

Post by Peter Coghlan ***@beyondthepale.ie [hercules-390]

-----Original Message-----
Sent: 15 December 2017 18:16
Subject: Re: [hercules-390] Starting VM/370

As someone else pointed out the "/enable all" is not needed the as
AUTOLOG1 user issues an "enable all" command. I think it was changed a
long time ago because with many 3270 devices defined it was slowing

AUTOLOG1 processing.
There is another possible reason ENABLE ALL fell out of favour.
Some time ago, support for different sized 3270 screens was added to
VM/370 by HRC101DK I think. This introduced a bug in ENABLE. If one
terminal is enabled, there is no problem. If more than one terminal of

the

same type is enabled, there is no problem. If two or more terminals of
differents sizes are enabled by the same command, the same logo screen is
sent to all the terminals and is displayed properly on some and mangled

on

others because it is the wrong size for them.
Therefore if different sized terminals are in use, ENABLE ALL should

probably

be avoided except by those who are not paniced by the mangled logos.

That would be good if the command in the HERCULES.RC file was different to
the one in the AUTOLOG1 PROFILE EXEC file.
But they are not, well not quite, the hercules.rc file says "ENABLE ALL" the
PROFILE EXEC says "CP ENA ALL"...
... which effectively are the same

Regards,
Peter Coghlan.

Dave

------------------------------------
------------------------------------
http://groups.yahoo.com/group/hercules-390
http://www.hercules-390.org
------------------------------------
Yahoo Groups Links

['Dave Wade' [e-mail] [hercules-390]]

In that case the hercules.rc should be executed. Remove the “.” From the “./enable all” and it should work



Dave



From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: 17 December 2017 01:24
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Starting VM/370








Thanks for all of the input on start up. The solution for me was to use

0009 for the console which put VM's console on Hercules'

console. Did have to issue the ENABLE ALL since AUTOLOG1

doesn't do it.

-----Original Message-----
Sent: 15 December 2017 18:16
Subject: Re: [hercules-390] Starting VM/370

As someone else pointed out the "/enable all" is not needed the as
AUTOLOG1 user issues an "enable all" command. I think it was changed a
long time ago because with many 3270 devices defined it was slowing

AUTOLOG1 processing.
There is another possible reason ENABLE ALL fell out of favour.
Some time ago, support for different sized 3270 screens was added to
VM/370 by HRC101DK I think. This introduced a bug in ENABLE. If one
terminal is enabled, there is no problem. If more than one terminal of

the

same type is enabled, there is no problem. If two or more terminals of
differents sizes are enabled by the same command, the same logo screen is
sent to all the terminals and is displayed properly on some and mangled on
others because it is the wrong size for them.
Therefore if different sized terminals are in use, ENABLE ALL should probably
be avoided except by those who are not paniced by the mangled logos.

That would be good if the command in the HERCULES.RC file was different to
the one in the AUTOLOG1 PROFILE EXEC file.
But they are not, well not quite, the hercules.rc file says "ENABLE ALL" the
PROFILE EXEC says "CP ENA ALL"...
... which effectively are the same

Regards,
Peter Coghlan.

Dave

------------------------------------
------------------------------------
http://groups.yahoo.com/group/hercules-390
http://www.hercules-390.org
------------------------------------
Yahoo Groups Links