Re: Slightly off-topic: development machine for z/OS wanted

"[email protected] [H390-MVS]" <[email protected]> 12 Oct 2019 19:46:22 +0000
Newsgroups gmane.comp.emulators.hercules390.mvs
Message-ID <[email protected]>
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 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.