| Newsgroups |
gmane.comp.emulators.hercules390.mvs |
| Message-ID |
<[email protected]> |
> And actually, it isn’t, it’s a z/OS artefact.
I don't understand what you are referring to here as a z/OS artifact.
> given that USS runs in z/OS (much like Windows can run in a Linux VM)
Avoid who ever told you this. Unix is part of the z/OS kernel and runs in every address space when needed. In theory, you could run unix process in any address space but for security reasons, IBM restricts most user's programs from many address spaces (e.g. TSO, CICS and IMS).
> I assume that z/OS and the preferences file (I’m not sure you understand what that is)
> have some kind of precedence.
Tony told you where etc.services precedence is documented. As for preference standards, the problem is with crossover products(z/OS and z/OS Unix) such as TCP. TCP must be able to exist without filesystems because they are only needed for z/OS Unix.
> I think I’ll have to figure this out on my own. Thanks for your opinions.
Unlike Unix systems, z/OS is a very complex OS to maintain for sysprogs but extremely simple for programmers. For instance, a good sysprog would never just change the system name. At this point, you still don't know what else that could have broken.
I doubt that changing the system name is causing this problem but I also suspect this is not a service name problem because this must have been a pre-built / configured z/OS. I'm guessing you changed something without considering the ramifications.
I wish you luck in solving the problem.
Jon.
On Tuesday, September 17, 2019, 01:45:44 PM PDT, John Murray [email protected] [H390-MVS] <[email protected]> wrote:
I think I’ll have to figure this out on my own. Thanks for your opinions.
And actually, it isn’t, it’s a z/OS artefact. And given that USS runs in z/OS (much like Windows can run in a Linux VM) I assume that z/OS and the preferences file (I’m not sure you understand what that is) have some kind of precedence. I will continue reading until I find out what the relationships are.
John Murray
Ottawa
On 17 Sep 2019, at 15:09, Jon Perryman jperryma-yBeKhBN/[email protected] [H390-MVS] <[email protected]> wrote:
I repeat, use your Unix skills to debug this problem. Do you actually think "1023 UDP OMVS ; OE TELNET SERVER" is an etc/services entry? What could possibly be the service name? Take a look at your Linux /etc/services if you can't remember the format. I believe you meant xxx.etc.services.
I repeat, stop making wild guesses as to the problem. Change the inetd conf telnet entry from a service name to the port number 1023. If that works, change it to port 1024 and duplicate the line but place the service name back on the new line. At this point, you can telnet into port 1024 for debugging and debug the service.
The IBM-MAIN news group has more participants and more current about finding information. I can only recommend looking at the previously mentioned manual.
As for the netstat command, I find it easier to use from MVS Unix. You can use the TSO OMVS command to access Unix line mode from TSO.