That would be explained by the fact that I thought I had sent it to the Linux-S390 list server in the first place (and obviously clipped the wrong address) <g>.

Oh well, vacation next week….maybe things will improve when I get back!

K

---

From: CICS List [mailto:CICS-L@LISTSERV.UGA.EDU] On Behalf Of McKown, John
Sent: Friday, November 16, 2007 10:57 AM
To: CICS-L@LISTSERV.UGA.EDU
Subject: Re: Development tools for custom GUI applications

Ah! Thanks for the update. Sounds interesting. Also, doesn't seem to have much to do with CICS, which is possibly why I am, as usual, quite confused <GRIN>.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law.  If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited.

-----Original Message-----
From: CICS List [mailto:CICS-L@LISTSERV.UGA.EDU] On Behalf Of Evans, Kevin R
Sent: Friday, November 16, 2007 9:25 AM
To: CICS-L@LISTSERV.UGA.EDU
Subject: Re: Development tools for custom GUI applications

Thanks, John, I’ll try that list server.

As far as your summary, not really, but nice try <g>.

In this case, the 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 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 GUI software can then be used for those searches/configuration changes etc.

Hope this makes things a little clearer.

Thanks,

Kevin