06-02-2011 10:50 PM
06-03-2011 02:04 AM
May be you could explain in pseudo-code what this script should do, as sed, syslog, armdsp, model or trace event do not have strict equivalence in OpenVMS (even if sed has been ported).
06-03-2011 04:00 AM
".rtf"? Did this script begin on a Windows
system, or was that your idea?
> [...] sed, syslog, armdsp, model or trace
> event do not have strict equivalence in
> OpenVMS [...]
At least. Also "/usr/sbin/ioscan",
"/usr/sbin/cmviewcl", and a host of others.
Define "translate to OpenVMS". What are you
actually trying to do?
> [...] is there a tool available [...]
06-03-2011 06:48 AM
This script provides a primitive web-based front end for an application that processes the network configuration and the hardware configuration, as well as looking at the server logs in some detail.
From what I see of it, it'll be a complete rewrite.
Most everything that this script is doing is specific to Unix, and a whole lot of what I see here is specific to HP-UX on PA-RISC and Integrity servers.
You'll need a programmer here that's somewhat familiar with bash HP-UX and very familiar with OpenVMS I/O and device configuration, and this "port" will be a complete rewrite of this script. As part of this "port", I'd look to move to a scripting language supported on all of the target platforms, and toward (somewhat) common source code.
All of the VMS scripting languages are either down-revision, or unsupported. Perl, php, Python, Lua, etc. And a DCL port would be full-parallel maintenance of two scripts.
As for the GNV bash implementation, that's a headache. Often a large one. All headaches and bash problems and limitations and omissions aside, this target task and involving tools such as ioscan, sasmgr, sautil and other HP-UX tools, will find GNV and its bash entirely inadequate. These tools are all platform-specific.
I'd likely also look at integrating this work with SNMP, but there may well be other scripts around that provide this path into the server.
06-03-2011 11:49 AM
ps: the target OpenVMS box here will also either need to have a web server configured and running (usually Apache or WASD) or the converted shell script will need to embed a web server.
(And yes, there are scripting languages around with libraries for easily embedding http services without requiring a web server. This approach is particularly useful if you can't load or can't assume or can't tie into a "traditional" web server on the target OpenVMS systems, and for whatever reason.
06-05-2011 04:36 AM
For starters, forget the Unix commands.
Just look at the output generated and see how you might generate similar, or the same, data for OpenVMS.
Some things will not map, many will.
This is not going to be a '5 minutes' job though!
Get ready for some tedious interpretationa and re-formatting.
06-05-2011 03:13 PM
Kind Regards, Andre