Re^2: Interact with mainframe screen

Hi, I am very interested in your solution of using OLE for perl access to the mainframe. I am trying to extend our (AIX/Windows based) environment for automated testing to the mainframe area. I have started work on a perl module that uses the Expect module on AIX to use the tn3270 emulator. But I think your approach is much better. I will try and see if I can use it with the 3270 emulator in our environment. The piece of code that you posted shows that it is a Host::PCOM module. Is it freely available? From your statement at the bottom I guess it is not. Is there a possibility for you to strip out the specific parts for your environment and publish the generic parts? I would be pleased to use it as a basis for further development and to help make this a general available perl module.

Comment on Re^2: Interact with mainframe screen

Replies are listed 'Best First'.
Re^3: Interact with mainframe screen by Corion (Patriarch) on Jun 30, 2007 at 13:25 UTC
No. Host::PCOM is a module I developed on the time and entirely for my employer. I don't feel it would be right to redistribute that code on my own, and I won't take it on me to involve the lawyers to get a release from my employer. That being said, it's not really hard to encapsulate the OLE API, as IBM provides plenty of good documentation.	[reply]
Re^4: Interact with mainframe screen by shmem (Chancellor) on Jun 30, 2007 at 14:09 UTC
I don't feel it would be right to redistribute that code on my own, and I won't take it on me to involve the lawyers to get a release from my employer. You might find "How to convince a client to release Perl code to CPAN?" helpful to get your employer to release the code... ;-) --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply]
Re^5: Interact with mainframe screen by Corion (Patriarch) on Jun 30, 2007 at 14:14 UTC
But that constitutes work on my part which far outweighs the effort needed to rewrite the module from the documentation.	[reply]