Hi John, Didn't mean to imply that we would be doing development on the Z box, we won't. Currently, we run XML code development under Eclipse on the PC and then port the code up to the Z.
Kevin -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Saturday, November 17, 2007 1:39 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: GUI development tools Evans, Kevin R wrote: > I would like some feedback on development tools, let me describe the > environment first > > > > Our existing CICS system uses what we call "dot delimited messages". > These all arrive over point to point encrypted communications lines into > what we call CORs (kinda sorta like TORs but without terminals). The COR > code either does some routing or passes the messages to the AORs. The > AORs process the message and send the result to the COR who then send it > back to the original requester. > > > > The XML system runs under zVM as a Linux guest (software here is written > in C) which we refer to as an XOR (XML owning region). Its job is to > translate the inbound XML message back to "dot-delimited" format and > push the message into the COR. The existing system runs as normal > (message into the AOR and get the response etc). The COR then sends the > response to the XOR who translates the "dot delimited" response back to > XML and sends the response to the originating end user. > > > > The GUI software I am talking about developing is to control the Linux > guest where we have configuration files written in XML that we want to > change from the outside world while the guest software is running. We > also log all messages in and out and want to write some GUI software to > search these logs etc. The custom GUI software can then be used for > those searches/configuration changes etc. I'm not sure I'm keen on developing/running GUI software actually on your very expensive Zed. An idea I like is to run the GUI on one system (eg your Intellish desktop/laptop) and the commands on the server (Zed in this case).. This kind of implementation would be well-suited to developing on the peecee, you would only need to compile on the Zed for final testing. The final choice as to where to run the actual GUI need not be made until implementation, and would be easily changed when you find running GUIs on the Zed's not that good an idea. Apple (OS X xserv) has a fairy sold set of commandline tools that can set and interrogate settings. While they can be used from the standard shell, I suspect their purpose is to separate the GUI from the configuration so the GUI can be run on one machine (my laptop) and the commands on the server, I don't know what communications protocol it uses, but shell commands piped through ssh would do. If you use qt libraries, then you have the option of also building the GUI part for Windows. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
