| Newsgroups |
gmane.comp.emulators.hercules390.mvs |
| Message-ID |
<[email protected]> |
Joe,
I hope that what you mean is “S/370 is no longer produced or supported” , rather than “no longer exists” , if it no longer exists outside Hercules then my P/390 which can be IMLed in 370 mode must have fallen through some sort of black hole or there is rent in the space time continuum. It was there when I went to Spain a couple of weeks ago. I must admit I haven’t checked since I got back but I am pretty sure its still there. . I see that a couple of FPGA implementations of S/370 have also appeared…
… but yes I think you need access to a modern system to properly test and debug your code….
Dave
From: [email protected] <[email protected]>
Sent: 12 October 2019 22:59
To: [email protected]
Subject: Re: [H390-MVS] Re: Slightly off-topic: development machine for z/OS wanted
VB,
GCC (latest version) already has a z/os target (s390x) ...
https://gcc.gnu.org/install/specific.html
* <https://gcc.gnu.org/install/specific.html#s390-x-linux> s390-*-linux*
* <https://gcc.gnu.org/install/specific.html#s390x-x-linux> s390x-*-linux*
* <https://gcc.gnu.org/install/specific.html#s390x-ibm-tpf> s390x-ibm-tpf*
This targets z/os as well as TPF...
s390-*-linux*
S/390 system running GNU/Linux for S/390.
_____
s390x-*-linux*
zSeries system (64-bit) running GNU/Linux for zSeries.
_____
s390x-ibm-tpf*
zSeries system (64-bit) running TPF. This platform is supported as cross-compilation target only.
What Paul has is an S/370 target, an architecture that no longer exists (it is only available on Hercules). He has added limited 31-bit support in what he calls a "380" architecture.
Whatever you want to port, you should be able to using the s390x target on your PC, then using FTP to upload to the target z/series and run the binder to make it a load module.
Joe
On Sat, Oct 12, 2019 at 3:46 PM [email protected] <mailto:[email protected]> [H390-MVS] <[email protected] <mailto:[email protected]> > wrote:
Hi, Paul,
I'm aware of the fork(2) problem. There's still no fork in many POSIX implementations. And this function was not part of older POSIX versions (while it is in 2017).
Unfortunately, the C standard is not sufficient for implementing many programs even in C17. Usually, when it's coming to C then it will be “standard C with extensions adding POSIX functions”, even in 2019. We've this problem at pEp, and we found our way of dealing with it. If real world programs should be ported to MVS then such an API has to be provided or it will most likely not happen.
There's a POSIX path rule, which might be of interest to you: operating system special paths are starting with a double slash (//). IBM is using this as following:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxa500/mvsds.htm
On MVS/380 I'd have questions:
«For some reason with TK4- you can't use TSO while running a 31-bit batch job.» Does this mean I've to stop TSO before I can run a batch job, and I have to run it from console?
My problem is I'm not experienced in MVS. I know basic system programming there, that's it. Which way is the easiest to get MVS/380 running in Hercules? I'm depending on solutions like TK4- because they're turn key. I don't feel secure enough to get a system installed myself.
Yours,
VB.