Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IPL failure with Hyperion v4.2 #258

Closed
dfortier2346 opened this issue Sep 27, 2019 · 56 comments
Closed

IPL failure with Hyperion v4.2 #258

dfortier2346 opened this issue Sep 27, 2019 · 56 comments
Assignees
@Fish-Git
Labels
BUG The issue describes likely incorrect product functionality that likely needs corrected.

Comments

@dfortier2346
Copy link

dfortier2346 commented Sep 27, 2019 •
edited by Fish-Git
Loading

Previously ran licensed version of z/OS under Hercules 3.13 as distributed in LINUX Mint repository.

Recently installed Hyperion 4.2.1 and am experiencing an issue I can't exactly match in any reported SDL issues.

During the IPL process, I see the following on the system console:

IEA247I USING IEASYSCS FOR z/OS vv.rr.mm HBB7760
ISG313I SYSTEM IS INITIALIZING IN GRS NONE MODE.  RING OR STAR CONFIGURATION
 KEYWORDS IN GRSCNF00 ARE IGNORED.
IEA304W SYSTEM WAIT STATE CODE 80009064 DURING **IEAVNPF5** INITIALIZATION

You will notice the affected program is IEAVNPF5 -- this is the match I can't seem to locate in your reports. Additionally, the Hercules Studio log contains the message "HHC00809I Processor CP00: disabled wait state 0002000080000000 0000000000009064" and the Messages and Codes Manual HEMC040000-00 states this message is not yet documented.

I reviewed earlier recommendations to review and modify the configuration file to conform to the new parameters of Hyperion V4 and the system still fails to IPL.

I am happy to provide whatever additional documentation you may require, but there isn't much.

Regards, Dennis
@dfortier2346 dfortier2346 reopened this Sep 27, 2019
@dfortier2346
Copy link
Author

Did not intend to close this issue or create a second comment. Please excuse the newbie :(

@Fish-Git Fish-Git added (Unknown) Unresolved. It might be a bug. It might not. We don't know. We couldn't reproduce it. Researching... The issue is being looked into or additional information is being gathered/located. labels Sep 29, 2019
@SDL-Hercules-390 SDL-Hercules-390 deleted a comment from dfortier2346 Sep 29, 2019
@Fish-Git
Copy link
Member

Fish-Git commented Sep 29, 2019 •
edited
Loading

Previously ran licensed version of z/OS under Hercules ...

What version?   1.10?   1.13?   2.1?   2.3?

... disabled wait state 0002000080000000 0000000000009064" and the Messages and Codes Manual HEMC040000-00 states this message is not yet documented.

Look here:

064

Explanation

During nucleus initialization program (NIP) processing, NIP detected a software or hardware error. An attempt was made to enter the recovery termination manager (RTM). This was trapped by NIP because the system is in a variable state of initialization and, in particular, RTM is not fully initialized.

  • 009
    A program check occurred. Accompanying message IEA304W further explains this wait state and entry code.

 
Bottom line: SDL Hyperion 4.x is very different from Hercules 3.x. Please closely review all of SDL Hyperion 4.2.1's configuration file statements against yours. You are probably missing one or more important ones, such as, perhaps, (depending on which version of z/OS you are using), a FACILITY DISABLE 006_ASN_LX_REUSE or something similar.

SDL Hyperion 4.x has the ASN and LX Reuse Facility enabled by default, whereas Hercules 3.x has it disabled by default. SDL Hyperion also has the PFPO Facility enabled by default too, whereas, again, Hercules 3.x does not, etc.

Enter the command FACILITY QUERY ALL to display a list of all facilities. Enter help facility for more info regarding the facility command/statement itself. Enter help for a list of supported commands. Enter help help for help with the help command itself.

Or... you might need to specify the cu=3990-6 parameter on all of your dasd statements (again, depending on which version of z/OS you are using). cu=3990-3 is the default I believe. Maybe you need to specify cu=3990-6 instead?

FINALLY... it would be helpful to see your Hercules logfile output too. So many people forget to include that in their problem report. There might well be some error or warning message(s) logged there that points to exactly what your problem is (or at least provide a clue). Have you reviewed your Hercules logfile? Are there any unexpected errors or warnings in it? Please attach it to your reply the same way you attached your configuration file so we can look at it.

@Fish-Git Fish-Git added the QUESTION... A question was asked but has not been answered yet, -OR- additional feedback is requested. label Sep 29, 2019
@dfortier2346
Copy link
Author

dfortier2346 commented Oct 1, 2019 via email •
edited by Fish-Git
Loading

@Fish-Git
Copy link
Member

Fish-Git commented Oct 7, 2019 •
edited
Loading

@dfortier2346

Dennis,

Please let me know whether the information I sent you helped to resolve your issue or not.

Thanks!

@Fish-Git Fish-Git added Waiting to close... Waiting for user to report back whether problem still exists or not before closing as resolved. (Invalid/PEBKAC) Likely user error. The described problem does not exist or was otherwise determined to be bogus. and removed Researching... The issue is being looked into or additional information is being gathered/located. (Unknown) Unresolved. It might be a bug. It might not. We don't know. We couldn't reproduce it. labels Oct 7, 2019
@dfortier2346
Copy link
Author

dfortier2346 commented Oct 7, 2019 via email •
edited by Fish-Git
Loading

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 7, 2019 •
edited by Fish-Git
Loading

Fish:

I have made the changes you recommended and scoured the Hyperion Configuration Documentation to insure all the parameters are set correctly. After several step-wise tries, I am still getting the same error message:

15:27:05 HHC00809I Processor CP00: disabled wait state 0002000080000000 0000000000009064

I am also enclosing my Hyperion.conf file and the System Log message file from "power on" to "power off". You will notice the disabled wait state message is the third-to-the-last in the log.

@Fish-Git Fish-Git added (Unknown) Unresolved. It might be a bug. It might not. We don't know. We couldn't reproduce it. Researching... The issue is being looked into or additional information is being gathered/located. and removed (Invalid/PEBKAC) Likely user error. The described problem does not exist or was otherwise determined to be bogus. Waiting to close... Waiting for user to report back whether problem still exists or not before closing as resolved. labels Oct 7, 2019
@Fish-Git
Copy link
Member

Fish-Git commented Oct 7, 2019 •
edited
Loading

@dfortier2346

Dennis,

I found this old thread on Nabble.com:

Start reading about 9/10 of the way down, near the very end of the thread, starting with the reply from Cliff McNeill, dated Mar 18, 2019; 8:03am.

He mentions what I previously mentioned: the IBM MVS System Codes manual documenting Wait State 064 (which Cliff also mentions in his reply):

Operator response

Do one of the following:
...

  • For table entry code X'009', try restarting the system, specifying CLPA in the reply to accompanying message IEA101A. Table entry code X'009' may occur on a warm or quick start if the previous cold start failed before or during master scheduler initialization.

 

Is perhaps the answer to your problem Adding a CLPA to your IEASYSxx parmlib member?? (*)

(*) (I am not a z/OS person! I know very little (next to nothing!) about z/OS!)

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 8, 2019 •
edited by Fish-Git
Loading

Fish: I have reviewed your recommendations and the post from Cliff McNeill. I am not receiving the IEA101A message. I am, however, specifying "Cold Start" in my IPL Parms (0A82CS..) through Hercules. I have also downloaded and browsed the MVS Initialization and Tuning Guide and Reference manuals.

With that said, I am attaching a copy of the IEASYSCS member showing that "CLPA" is specified, and System Log showing the Wait State message.

Additionally, I am receiving the wait state code for module IEAVNPF5 not IEAVNP10, not sure if that makes a difference. I previously searched IEAVNPF5 and did not come up with much relevant information.

Any suggestions on where to go from here? Is anyone running z/OS 1.11 under Hyperion? Is there any way I can connect with him/her to discuss configuration settings?

Dennis

@Fish-Git Fish-Git removed QUESTION... A question was asked but has not been answered yet, -OR- additional feedback is requested. Researching... The issue is being looked into or additional information is being gathered/located. labels Oct 9, 2019
@Fish-Git
Copy link
Member

Fish-Git commented Oct 9, 2019

With that said, I am attaching a copy of the IEASYSCS member showing that "CLPA" is specified, and System Log showing the Wait State message.

Hopefully someone with z/OS knowledge will know what all that gobbledygook means because I sure as heck don't!   (Hint: I'm not a z/OS person)

But thanks for posting it?

Additionally, I am receiving the wait state code for module IEAVNPF5 not IEAVNP10, not sure if that makes a difference. I previously searched IEAVNPF5 and did not come up with much relevant information.

For what it's worth I just did a search for "IEAVNPF5" and "80009064" and found this:

Does that make any sense to you?

Any suggestions on where to go from here?

None. :(

As I've been saying, I'm not a z/OS person. :(

Is anyone running z/OS 1.11 under Hyperion? Is there any way I can connect with him/her to discuss configuration settings?

I have no idea. You might want to ask that question on the main list or in the H390-MVS group?

All I do know is that I myself happen have an old z/OS 1.10 system, and it IPLs and runs just fine with the latest SDL Hyperion (and all previous SDL Hyperion versions for that matter).

Now I know that 1.10 isn't the same as 1.11, but then neither is 2.1 or 2.3 or z/VM 6.3 either, and they all IPL and run just fine under Hercules too. So I don't quite understand why z/OS 1.11 wouldn't. <shrug>

I don't know if you're using CKD/CCKD/32/64 dasd but maybe it wouldn't hurt to check them for damage? Or if you still have the original installation media (dasds), you might try starting over again? (Where did you get your dasds from anyway?) Maybe something you tried in the past went wrong and left some part of the system in a bad state (bad setting?) that's causing your current problem? Or maybe it's not quite configured the way you think it is if you got them from somewhere else?

I'll keep this issue open for another few days but after that I'm afraid I'm going to have to close it. It honestly does not look like a Hercules problem.

Maybe play around with those ASN and LX Reuse settings? Maybe 1.11 was the first z/OS that cared about that setting (facility)? Maybe you need to disable it? And/or PFPO? Or maybe some other facility? As I said for the thousandth time, I'm not a z/OS person! Sorry! :(

@Fish-Git Fish-Git added the HELP! Help is needed from someone more experienced or I'm simply overloaded with too much work right now! label Oct 9, 2019
@Fish-Git
Copy link
Member

Fish-Git commented Oct 9, 2019

@dfortier2346

Dennis!

I just now noticed!   (Sorry for not looking sooner)

Maybe you shouldn't do a startall before IPLing!!!   (I've never seen anyone do that before!!)

I never do a startall before IPLing! If that's the way you've been trying to IPL your z/OS system, then maybe that's been your problem this whole time!!

Just start Hercules, attach a 3270 as your master console, and do ipl 0A80!!

Maybe your problem this whole time was that you simply weren't IPLing z/OS correctly??

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 9, 2019 •
edited by Fish-Git
Loading

Fish: I'm afraid going directly to ipl without the startall command didn't make any difference. I have attached the Operator Screen image after the failure and the Hercules log.

Per your suggestion, I'm going to troll this site to see if anyone else is running z/OS v1 and ask them to provide me with their setup. Since you stated you do have a z/OS 1.10 system you run, are you willing to share your configuration file? Please feel free to cut out any site-specific entries (Disks, etc) you don't want to share.

Dennis

@Fish-Git
Copy link
Member

Since you stated you do have a z/OS 1.10 system you run, are you willing to share your configuration file?

Sure:

@Fish-Git Fish-Git added the Waiting to close... Waiting for user to report back whether problem still exists or not before closing as resolved. label Oct 11, 2019
@Fish-Git
Copy link
Member

Fish-Git commented Oct 2, 2020

Is 4.3 ready for release?

Not yet, but hopefully it will be soon.

If I find time (HA!) I'll try building you a version you can try

OR... you can of course try building one for yourself. It's not hard!

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 2, 2020 via email •
edited by Fish-Git
Loading

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 2, 2020 via email

@Fish-Git
Copy link
Member

Fish-Git commented Oct 2, 2020

FYI: I would prefer that you reply via the GitHub Issues web page, NOT via email.

I can’t seem to find a web page to download Hyperion 4.3, all the links I go to say “Page not found”.

What URL are you using?

@wrljet
Copy link
Member

wrljet commented Oct 2, 2020

Dennis,
Instructions for building the latest from source can be found here:

https://sdl-hercules-390.github.io/html/hercinst.html

Scroll down a ways to the Linux section.

@Fish-Git
Copy link
Member

Fish-Git commented Oct 2, 2020 •
edited
Loading

Bill Lewis wrote:

Instructions for building the latest from source can be found here:

https://sdl-hercules-390.github.io/html/hercinst.html

Scroll down a ways to the Linux section.

Correct.

And I would like to emphasize the fact that building from a git clone of the repository is much preferred over building from the downloadable .zip file. Doing so ensures a 100% accurate version number. (Building from the downloadable .zip file only gives you a generic version number that doesn't tell us whether you're using the absolutely most current version of 4.3 or a much older 4.3. Building from the git clone of the repository however, tells us exactly what code you're running.)

@dfortier2346
Copy link
Author

I am on the https://github.com/SDL-Hercules-390/hyperion and the latest release available is 4.2.1, not 4.3. I've already tried 4.2.1 and that's where the original failure occurred.

Do you want me to wait for 4.3 or retry 4.2.1?

@Fish-Git
Copy link
Member

Fish-Git commented Oct 3, 2020 •
edited
Loading

(sigh)

Do you have git installed on your Linux system? Yes or no?

If you do not, then please install it.

After it is installed, then "git clone" the current SDL repository, and build from THAT.

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 3, 2020 •
edited by Fish-Git
Loading

Gentlemen:

I installed git on my computer, then went to https://github.com/SDL-Hercules-390/hyperion and followed the git documentation to do a clone to my hard drive. I then read and followed the install instructions outlined in https://sdl-hercules-390.github.io/html/hercinst.html and encountered a configuration failure. Here is the configuration log, look for the word "error".

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure 

## --------- ##
## Platform. ##
## --------- ##

hostname = Hercules
uname -m = x86_64
uname -r = 5.4.0-48-generic
uname -s = Linux
uname -v = #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
PATH: /usr/local/games
PATH: /snap/bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:3187: checking for a BSD-compatible install
configure:3255: result: /usr/bin/install -c
configure:3266: checking whether build environment is sane
configure:3321: result: yes
configure:3470: checking for a thread-safe mkdir -p
configure:3509: result: /bin/mkdir -p
configure:3516: checking for gawk
configure:3532: found /usr/bin/gawk
configure:3543: result: gawk
configure:3554: checking whether make sets $(MAKE)
configure:3576: result: yes
configure:3605: checking whether make supports nested variables
configure:3622: result: yes
configure:3760: checking whether make supports nested variables
configure:3777: result: yes
configure:3794: checking whether to enable maintainer-specific portions of Makefiles
configure:3803: result: no
configure:3820: checking build system type
configure:3834: result: x86_64-pc-linux-gnu
configure:3854: checking host system type
configure:3867: result: x86_64-pc-linux-gnu
configure:3887: checking target system type
configure:3900: result: x86_64-pc-linux-gnu
configure:3935: checking whether make supports the include directive
configure:3950: make -f confmf.GNU && cat confinc.out
this is the am__doit target
configure:3953: $? = 0
configure:3972: result: yes (GNU style)
configure:4042: checking for gcc
configure:4058: found /usr/bin/gcc
configure:4069: result: gcc
configure:4298: checking for C compiler version
configure:4307: gcc --version >&5
gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:4318: $? = 0
configure:4307: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.3.0-10ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) 
configure:4318: $? = 0
configure:4307: gcc -V >&5
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:4318: $? = 1
configure:4307: gcc -qversion >&5
gcc: error: unrecognized command line option '-qversion'; did you mean '--version'?
gcc: fatal error: no input files
compilation terminated.
configure:4318: $? = 1
configure:4338: checking whether the C compiler works
configure:4360: gcc    conftest.c  >&5
/usr/bin/ld: cannot find Scrt1.o: No such file or directory
/usr/bin/ld: cannot find crti.o: No such file or directory
collect2: error: ld returned 1 exit status
configure:4364: $? = 1
configure:4402: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define PACKAGE "hercules"
| #define VERSION "4.3.9999"
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| 
|   ;
|   return 0;
| }
configure:4407: error: in `/home/dollar/Locker/Hyperion/hyperion':
configure:4409: error: C compiler cannot create executables
See `config.log' for more details

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_build=x86_64-pc-linux-gnu
ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_F77_set=
ac_cv_env_F77_value=
ac_cv_env_FFLAGS_set=
ac_cv_env_FFLAGS_value=
ac_cv_env_HQA_DIR_set=
ac_cv_env_HQA_DIR_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=x86_64-pc-linux-gnu
ac_cv_path_install='/usr/bin/install -c'
ac_cv_path_mkdir=/bin/mkdir
ac_cv_prog_AWK=gawk
ac_cv_prog_ac_ct_CC=gcc
ac_cv_prog_make_make_set=yes
ac_cv_target=x86_64-pc-linux-gnu
am_cv_make_support_nested_variables=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ACLOCAL='${SHELL} /home/dollar/Locker/Hyperion/hyperion/autoconf/missing aclocal-1.16'
AMDEPBACKSLASH='\'
AMDEP_FALSE='#'
AMDEP_TRUE=''
AMTAR='$${TAR-tar}'
AM_BACKSLASH='\'
AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
AM_DEFAULT_VERBOSITY='0'
AM_V='$(V)'
AR=''
AS=''
AUTOCONF='${SHELL} /home/dollar/Locker/Hyperion/hyperion/autoconf/missing autoconf'
AUTOHEADER='${SHELL} /home/dollar/Locker/Hyperion/hyperion/autoconf/missing autoheader'
AUTOMAKE='${SHELL} /home/dollar/Locker/Hyperion/hyperion/autoconf/missing automake-1.16'
AWK='gawk'
BUILD_FTHREADS_FALSE=''
BUILD_FTHREADS_TRUE=''
BUILD_HERCIFC_FALSE=''
BUILD_HERCIFC_TRUE=''
CC='gcc'
CCDEPMODE=''
CFLAGS=''
CONVENIENCE_LTDL_FALSE=''
CONVENIENCE_LTDL_TRUE=''
CPP=''
CPPFLAGS=''
CXX=''
CXXCPP=''
CXXDEPMODE=''
CXXFLAGS=''
CYGPATH_W='echo'
DEFS=''
DEPDIR='.deps'
DLLTOOL=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
EXTPKG_HEADERS=''
EXTPKG_INCDIRS=''
EXTPKG_LDADD=''
F77=''
FFLAGS=''
GREP=''
HERCIFC_GROUPNAME=''
HERCIFC_GROUPSET_FALSE=''
HERCIFC_GROUPSET_TRUE=''
HQA_DIR=''
HQA_INC=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_LTDL_FALSE=''
INSTALL_LTDL_TRUE=''
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
LDFLAGS=''
LIBADD_DL=''
LIBOBJS=''
LIBS=''
LIBTOOL=''
LIBTOOL_DEPS=''
LN_S=''
LTLIBOBJS=''
MAINT='#'
MAINTAINER_MODE_FALSE=''
MAINTAINER_MODE_TRUE='#'
MAKEINFO='${SHELL} /home/dollar/Locker/Hyperion/hyperion/autoconf/missing makeinfo'
MKDIR_P='/bin/mkdir -p'
OBJDUMP=''
OBJEXT=''
OPTION_CAPABILITIES_FALSE=''
OPTION_CAPABILITIES_TRUE=''
PACKAGE='hercules'
PACKAGE_BUGREPORT=''
PACKAGE_NAME=''
PACKAGE_STRING=''
PACKAGE_TARNAME=''
PACKAGE_URL=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
RANLIB=''
SETUID_HERCIFC_FALSE=''
SETUID_HERCIFC_TRUE=''
SET_MAKE=''
SHELL='/bin/bash'
STRIP=''
VERSION='4.3.9999'
ac_ct_CC='gcc'
ac_ct_CXX=''
ac_ct_F77=''
am__EXEEXT_FALSE=''
am__EXEEXT_TRUE=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__fastdepCXX_FALSE=''
am__fastdepCXX_TRUE=''
am__include='include'
am__isrc=''
am__leading_dot='.'
am__nodep='_no'
am__quote=''
am__tar='$${TAR-tar} chof - "$$tardir"'
am__untar='$${TAR-tar} xf -'
bindir='${exec_prefix}/bin'
build='x86_64-pc-linux-gnu'
build_alias=''
build_cpu='x86_64'
build_os='linux-gnu'
build_vendor='pc'
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE}'
dvidir='${docdir}'
exec_prefix='NONE'
host='x86_64-pc-linux-gnu'
host_alias=''
host_cpu='x86_64'
host_os='linux-gnu'
host_vendor='pc'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
install_sh='${SHELL} /home/dollar/Locker/Hyperion/hyperion/autoconf/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
mandir='${datarootdir}/man'
mkdir_p='$(MKDIR_P)'
modexecdir=''
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='NONE'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='${localstatedir}/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target='x86_64-pc-linux-gnu'
target_alias=''
target_cpu='x86_64'
target_os='linux-gnu'
target_vendor='pc'

## ----------- ##
## confdefs.h. ##
## ----------- ##

/* confdefs.h */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""
#define PACKAGE "hercules"
#define VERSION "4.3.9999"

configure: exit 77

@wrljet
Copy link
Member

wrljet commented Oct 3, 2020

Dennis,

gcc -V is an ancient obsolete switch, which means something before the configure isn't correct.

Try running ./autogen.sh before ./configure

And, what is the exact version of Ubuntu you're using, just so we know?

Bill

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 3, 2020 via email •
edited by Fish-Git
Loading

@wrljet
Copy link
Member

wrljet commented Oct 3, 2020

Is Mint based on Ubuntu? (I've never dabbled with Mint)

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 3, 2020 via email •
edited by Fish-Git
Loading

@wrljet
Copy link
Member

wrljet commented Oct 3, 2020

OK. That's what I figured.
If the autogen doesn't do the trick, I will set up a Mint VM and give it a try myself.

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 3, 2020 via email •
edited by Fish-Git
Loading

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 3, 2020 via email •
edited by Fish-Git
Loading

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 3, 2020 via email •
edited by Fish-Git
Loading

@wrljet
Copy link
Member

wrljet commented Oct 3, 2020

OK Can you point me to the exact thing you used to install Mint? URL to ISO, etc?
I'll set it up and see if I can figure it out.

Bill

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 3, 2020 via email •
edited by Fish-Git
Loading

@wrljet
Copy link
Member

wrljet commented Oct 3, 2020

I have installed Mint 20 in a VMware VM. Mint looks like a pretty nice distribution!

First off the autogen.sh suggestion was a red herring.

Here's what I did, and it "works for me":

    sudo apt update
    sudo apt list --upgradable

    sudo apt install --yes build-essential
    sudo apt install --yes cmake git autoconf flex gawk

    which gcc
    gcc --version

    mkdir sdl42
    mkdir herc42
    mkdir extpkgs

    cd extpkgs
    git clone https://github.com/SDL-Hercules-390/gists.git

    cp gists/extpkgs.sh .
    cp gists/extpkgs.sh.ini .

    ./extpkgs.sh CLONE c d s t

    cd ../sdl42
    git clone https://github.com/SDL-Hercules-390/hyperion.git

    cd hyperion/

    util/bldlvlck 
    ./autogen.sh

    ./configure --prefix=/home/bill/hercules/herc42 --enable-extpkgs=/home/bill/hercules/extpkgs
    ./config.status --config

    make -j

    # quickie test
    # sudo ./hercules

Things in your config.log and mine diverged here:

Mine:
configure:4338: checking whether the C compiler works
configure:4360: gcc conftest.c >&5
configure:4364: $? = 0
configure:4412: result: yes

Yours:
configure:4338: checking whether the C compiler works
configure:4360: gcc conftest.c >&5
/usr/bin/ld: cannot find Scrt1.o: No such file or directory
/usr/bin/ld: cannot find crti.o: No such file or directory
collect2: error: ld returned 1 exit status

So... I guess we have to take that at face value. For some reason your gcc "doesn't work".
Try:

sudo apt install --yes build-essential

And then run configure again.

Bill

@dfortier2346
Copy link
Author

dfortier2346 commented Oct 3, 2020 via email •
edited by Fish-Git
Loading

@wrljet
Copy link
Member

wrljet commented Oct 3, 2020 •
edited by Fish-Git
Loading

Dennis,

Generally the full C development tools are not really all there out of the box.
Seems like distros these days are more interested in playing Netflix and stuff like that. :-)

I have been working with Fish to improve the Linux build process.
We worked some on NetBSD a while back. And recently for the Raspberry Pi 64-bit.

The instructions on the website need updating, and it is "on the list" to do.

If you want to know how to build and include the optional Rexx, let me know.

Bill

@dfortier2346
Copy link
Author

Bill, Fish

Installed newest release of Hyperion 4.2.1 from source by cloning from GIT rather than downloading the ZIP file. After a few minor blips with the environment, it was able to successfully MAKE the executable modules and they work.

Thanks for your guidance and assistance.

Dennis

@Fish-Git
Copy link
Member

Fish-Git commented Oct 4, 2020

Dennis,     (@dfortier2346)

Installed newest release of Hyperion 4.2.1 from source by cloning from GIT rather than downloading the ZIP file.

If you did a git clone of the repository and built from that (which IS what we wanted you to do! Thank you!), then the version you built should not have been 4.2.1, but rather version 4.3.9999.10257-SDL-g39beac46 instead. Please check the version that is reported whenever you start Hercules:

    HHC00100I Thread id 000008bc, prio 5, name 'impl_thread' started
    HHC00100I Thread id 00003350, prio 4, name 'logger_thread' started
    HHC01413I Hercules version 4.3.9999.10257-SDL-g39beac46 (4.3.9999.10257)
    HHC01414I (C) Copyright 1999-2020 by Roger Bowler, Jan Jaeger, and others
    HHC01417I ** The SoftDevLabs version of Hercules **
    HHC01415I Build date: Oct  2 2020 at 01:13:59
...

Another way to check what version you are running is to enter the Hercules version command (which simply re-displays the same startup messages):

    HHC01603I *
    HHC01603I *
    HHC01603I *
    HHC01603I *
    HHC01603I help version
    HHC01603I
    HHC01602I Command               Description
    HHC01602I ----------------      -------------------------------------------------------
    HHC01602I version               Display version information
    HHC01603I
    HHC01603I *
    HHC01603I *
    HHC01603I *
    HHC01603I *
    HHC01603I version
    HHC01413I Hercules version 4.3.9999.10257-SDL-g39beac46 (4.3.9999.10257)
    HHC01414I (C) Copyright 1999-2020 by Roger Bowler, Jan Jaeger, and others
    HHC01417I ** The SoftDevLabs version of Hercules **
    HHC01415I Build date: Oct  2 2020 at 01:13:59
    HHC01417I Built with: Microsoft Visual Studio 2008 (MSVC 150030729 1)
    HHC01417I Build type: Windows MSVC AMD64 host architecture build
    HHC01417I Modes: S/370 ESA/390 z/Arch
    HHC01417I Max CPU Engines: 64
    HHC01417I Using   shared libraries
    HHC01417I Using   Fish threads Threading Model
    HHC01417I Using   Error-Checking Mutex Locking Model
    HHC01417I With    Shared Devices support
    HHC01417I With    Dynamic loading support
    HHC01417I With    External GUI support
    HHC01417I With    Partial TCP keepalive support
    HHC01417I With    IPV6 support
    HHC01417I With    HTTP Server support
    HHC01417I With    sqrtl support
    HHC01417I With    Signal handling
    HHC01417I With    Watchdog monitoring
    HHC01417I With    CCKD BZIP2 support
    HHC01417I With    HET BZIP2 support
    HHC01417I With    ZLIB support
    HHC01417I With    Regular Expressions support
    HHC01417I With    Object REXX support
    HHC01417I Without Regina REXX support
    HHC01417I With    Automatic Operator support
    HHC01417I Without National Language Support
    HHC01417I With    CCKD64 Support
    HHC01417I With    Transactional-Execution Facility support
    HHC01417I With    "Optimized" instructions
    HHC01417I With    OPTION_DEPRECATE_AIM
    HHC01417I Without OPTION_TXF_SINGLE_THREAD
    HHC01417I Machine dependent assists: cmpxchg1 cmpxchg4 cmpxchg8 cmpxchg16 hatomics=msvcIntrinsics
    HHC01417I Running on: WIN7 (Windows-6.1.7601 Intel(R) x64) LP=8, Cores=8, CPUs=2
    HHC01417I Built with crypto external package version 1.0.0.31-gbf46d03
    HHC01417I Built with decNumber external package version 3.68.0.84-g94144c9
    HHC01417I Built with SoftFloat external package version 3.5.0.87-gb706677
    HHC01417I Built with telnet external package version 1.0.0.48-gb90a708
    HHC01603I *
    HHC01603I *
    HHC01603I *
    HHC01603I *

The -g39beac46 portion of the reported version should correspond to the last commit that was made to the repository (the "g" means "git" and the "39beac46" is the first 8 digits of the commit hash):

The last commit was made 4 days ago on Sep 30, 2020, and the commit hash was 39beac4. Thus the reported version is "4.3.9999.10257-SDL-g39beac46".

This is the exact version that I was mentioning before, which tells us exactly what code you are using. If you had built from the ZIP file instead (which is NOT recommended), then the reported version would have only been "4.3.9999", which is not helpful.

Please check to make sure you are running "4.3.9999.10257-SDL-g39beac46". When you first opened this GitHub Issue, you reported the problem was with version 4.2.1, which hasn't changed and should not have worked. Thus I suspect you are indeed running the latest (unreleased) version 4.3 instead, which thankfully does work. Again, please check to confirm.

Thanks.

@Fish-Git
Copy link
Member

Dennis,   (@dfortier2346)

Latest 4.3 TXF pre-release build:

The version that Hercules should report is:   4.3.9999.10260-SDL-g14e36689   (current as/of Oct 10, 2020)

Again, a reminder that this is a PRE-release version. That is to say, it is not an official release. We're still working on 4.3. The Transactional-Execution Facility (TXF) is known to be incomplete and to still contain at least one (possible more!) bug(s), so please use at your own risk!

Thanks.

@Fish-Git Fish-Git mentioned this issue Oct 25, 2020
Closed
11 tasks
@Fish-Git
Copy link
Member

Fish-Git commented Dec 3, 2020

Dennis (@dfortier2346),

Since 4.3 was (finally!) just recently released, I'm curious as to whether or not you've had a chance to try it yet? Does it fix your problem? Yes? No?

@dfortier2346
Copy link
Author

dfortier2346 commented Dec 3, 2020 via email •
edited by Fish-Git
Loading

@Fish-Git Fish-Git removed the QUESTION... A question was asked but has not been answered yet, -OR- additional feedback is requested. label Dec 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Fish-Git Fish-Git

Labels
BUG The issue describes likely incorrect product functionality that likely needs corrected.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mcisho @Fish-Git @wrljet @dfortier2346