Re: Accessing TCPIP.DATA from Perl on os390

[Yaroslav Kuzmin]

Using module OS390:;Stdio (https://metacpan.org/pod/OS390::Stdio) to read 
datasets.


--

Regards,

Yaroslav Kuzmin
Developer C/C++ ,z/OS , Linux
3 Zhukovskiy Street · Miass, Chelyabinsk region 456318 · Russia
Tel:  +7.922.2.38.33.38
Email: ykuz...@rocketsoftware.com
Web: www.rocketsoftware.com



 Исходное сообщение 
От: M. Ray Mullins 
<m.ray.mull...@gmail.com<mailto:%22m.%20ray%20mullins%22%20%3cm.ray.mull...@gmail.com%3e>>
Кому: perl-mvs@perl.org<mailto:perl-mvs@perl.org>
Тема: Re: Accessing TCPIP.DATA from Perl on os390
Дата: Thu, 11 May 2017 19:01:51 -0700

I am well aware of what I wrote.

Maybe Yaroslav can assist you.

Good day.

On 2017-05-11 16:56, Dick Franks wrote:

On 11 May 2017 at 23:25, M. Ray Mullins 
<m.ray.mull...@gmail.com<mailto:m.ray.mull...@gmail.com>> wrote:
On 2017-05-10 13:12, Dick Franks wrote:
I've never tried open(FHAND, "http://data.set.name>'") or die 
"Not found: $!". I don't have perl installed on our system


If you have no skin in the game, the conversation is over
I don't have authority at my installation, otherwise it would be installed. 
However, I have used perl in the recent past under z/OS, and I've worked with 
z/OS USS for many years. I am a systems tools developer for over 20 years on 
the platform, almost 40 total. Assembler is my strength, but I have extensive 
experience with C in the systems context.


Yet you had no answer to the core question, and neither the kit to find out, 
nor the wit to remain silent.

If you think that unfair, go read your posts again.





--
M. Ray Mullins
Roseville, CA, USA

German is essentially a form of assembly language consisting entirely of far 
calls heavily accented with throaty guttural sounds. ---ilvi
French is essentially German with messed-up pronunciation and spelling.  
--Robert B Wilson
English is essentially French converted to 7-bit ASCII.  ---Christophe Pierret 
[for Alain LaBonté]


Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 877.328.2932
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

Re: Accessing TCPIP.DATA from Perl on os390

[M. Ray Mullins]

I am well aware of what I wrote.

Maybe Yaroslav can assist you.

Good day.

On 2017-05-11 16:56, Dick Franks wrote:


On 11 May 2017 at 23:25, M. Ray Mullins > wrote:


On 2017-05-10 13:12, Dick Franks wrote:


I've never tried open(FHAND, "http://data.set.name>'") or die "Not found: $!". I don't
have perl installed on our system


If you have no skin in the game, the conversation is over

I don't have authority at my installation, otherwise it would be
installed. However, I have used perl in the recent past under
z/OS, and I've worked with z/OS USS for many years. I am a systems
tools developer for over 20 years on the platform, almost 40
total. Assembler is my strength, but I have extensive experience
with C in the systems context.


Yet you had no answer to the core question, and neither the kit to 
find out, nor the wit to remain silent.


If you think that unfair, go read your posts again.





--
M. Ray Mullins
Roseville, CA, USA

German is essentially a form of assembly language consisting entirely of far 
calls heavily accented with throaty guttural sounds. ---ilvi
French is essentially German with messed-up pronunciation and spelling.  
--Robert B Wilson
English is essentially French converted to 7-bit ASCII.  ---Christophe Pierret 
[for Alain LaBonté]

Re: Accessing TCPIP.DATA from Perl on os390

[M. Ray Mullins]

(CC'd back to the mailing list.)

On 2017-05-04 20:22, Dick Franks wrote:


On 5 May 2017 at 01:08, M. Ray Mullins > wrote:


Hello Dick,

This appears to be a duplicate of an email you sent yesterday. Did
you receive my answer sent to the mailing list later that day?


Thanks

I was not subscribed to the list. No reply came, so I assumed that 
posting was restricted to subscribers, signed up and reposted


Makes sense. I was a bit surprised to see the same thing twice. :)



If not, here is what I sent:

-

Hi Dick,

As the UNIX® System Services component of z/OS is certified UNIX- and
POSIX-compliant, whatever method you use currently to interrogate the
UNIX and brethren OSes should work.

But does not because /etc/resolv.conf not the only place this could be 
found.


Having said that, of course, we are talking z/OS and EBCDIC, so, of
course, I'm sure it won't work out of the box and would require a tweak
or three.

EBCDIC issues fixed in Net::DNS 1.10

Yay! EBCDIC, the forgotten code set. :D


Tested, working, just no default nameserver config.


It is possible to read traditional data sets from the UNIX servers, 
however to be fair, I personally have not tried it.


In z/OS C, if you prefix a file specification with //, the C run-time 
knows that this data set resides in the traditional file system. If you 
don't prefix with single quotes, it prepends a high-level qualifier 
consisting of the userid. For example, in my environment (one of my 
userids is RMULLIN), "//MISC.ASM" would cause the C run-time to access 
data set RMULLIN.MISC.ASM. Likewise, to access TCPIP.DATA, you'd specify 
"//'TCPIP.DATA'".


I've never tried open(FHAND, "$!". I don't have perl installed on our system (I should talk to TPTB).


Also, be aware that although those are the default and most common data 
set names used for the TCP/IP server, they can be changed.


Having said all that…I believe the information you are looking for is 
available through calls to system routines. This might require dropping 
into C, though.


I've been a bit busy, but I'll look at the relevant z/OS C run-time 
library and TCP/IP manuals later this week.


Best regards,
Ray Mullins


Is there a specific issue you've encountered so far?


-

Best regards,
Ray Mullins


On 2017-05-04 16:24, Dick Franks wrote:

All,

Is it possible to access the content of TCPIP.DATA and
GLOBALTCPIPDATA from a Perl script?

Where do these files live? Are they readable and parseable?

Alternatively, is there some easy way of interrogating the OS to
find the value associated with an individual parameter name?

I am specifically interested in finding the local DNS nameserver
addresses, searchlist, etc. to provide the default values for
Net::DNS so that it works the same way on all supported platforms.

Any help you can provide would be much appreciated, an example,
even better.

P.S. I know next to nothing about MVS, so have a strong
preference for succinct and straightforward answers.


Dick Franks





-- 
M. Ray Mullins

Roseville, CA, USA

German is essentially a form of assembly language consisting entirely of 
far calls heavily accented with throaty guttural sounds. ---ilvi
French is essentially German with messed-up pronunciation and spelling.  
--Robert B Wilson
English is essentially French converted to 7-bit ASCII.  ---Christophe 
Pierret [for Alain LaBonté]





--
M. Ray Mullins
Roseville, CA, USA

German is essentially a form of assembly language consisting entirely of far 
calls heavily accented with throaty guttural sounds. ---ilvi
French is essentially German with messed-up pronunciation and spelling.  
--Robert B Wilson
English is essentially French converted to 7-bit ASCII.  ---Christophe Pierret 
[for Alain LaBonté]

Re: Accessing TCPIP.DATA from Perl on os390

[M. Ray Mullins]

Hi Dick,

As the UNIX® System Services component of z/OS is certified UNIX- and 
POSIX-compliant, whatever method you use currently to interrogate the 
UNIX and brethren OSes should work.


Having said that, of course, we are talking z/OS and EBCDIC, so, of 
course, I'm sure it won't work out of the box and would require a tweak 
or three.


Is there a specific issue you've encountered so far?

Best regards,
Ray Mullins

On 2017-05-03 10:33, Dick Franks wrote:

All,

Is it possible to access the content of TCPIP.DATA and GLOBALTCPIPDATA 
from a Perl script?


Where do these files live? Are they readable and parseable?

Alternatively, is there some easy way of interrogating the OS to find 
the value associated with an individual parameter name?


I am specifically interested in finding the local DNS nameserver 
addresses, searchlist, etc. to provide the default values for Net::DNS 
so that it works the same way on all supported platforms.


Any help you can provide would be much appreciated, an example, even 
better.


P.S. I know next to nothing about MVS, so have a strong preference for 
succinct and straightforward answers.



Dick Franks





--
M. Ray Mullins
Roseville, CA, USA

German is essentially a form of assembly language consisting entirely of far 
calls heavily accented with throaty guttural sounds. ---ilvi
French is essentially German with messed-up pronunciation and spelling.  
--Robert B Wilson
English is essentially French converted to 7-bit ASCII.  ---Christophe Pierret 
[for Alain LaBonté]