Zeev Atlas wrote:
!My questions are: !a) Is Perl-MVS compiled with native IBM MVS C or was the GNU gcc (or !whatever they call the current version) ported to MVS as well. Usually you have to compile perl with the Unix System Services c89 compiler. I am not sure if anyone has attempted to port perl to David Pitts' port of gcc to OS/390. It should not be too difficult, but as far as I know it has not been done. !b) If it is compiled with native IBM MVS C, how feasible would it be to !code a module to add the aforementioned functionality. I have seen it has !been done under Windows and would assume it should be possible. Considering that native MVS I/O already has been addressed by a module on CPAN (namely OS390::Stdio) it should be very feasible. See for example: http://search.cpan.org/search?dist=OS390-Stdio !c) Same question if I must use gcc (I would assume it should make it harder !to implement unless modules compiled with the two C compilers may !communicate... er... interface with each other) I do not know much about the port of gcc to OS/390 or z/OS unfortunately. I can tell you that the C run time library that IBM's c89 compiler has access to distinguishes between files that are open()'ed from C and files that are fopen()'ed from C. The latter can be made to fopen() //'TRADITIONAL.DATA.SETS' whereas the former cannot. It would seem that the distinction is a matter of interfacing well with MVS, and I cannot tell you much about how the port of gcc does in that regard. Peter Prymmer
