Part of the "not much success" was based on our versions of our mainframe software
(DB2, OS/390, CICS, etc) and the resources workload on the mainframe side. I also
found it easier from a design standpoint to keep the servlets off the mainframe, where
the business logic is, especially since in the future we will be running SAP. This
way with MQ running as the middleware, "all" I will have to do is reconnect the
business logic from the mainframe to SAP.
>>> "Preston L. Bannister" <[EMAIL PROTECTED]> 05/04 9:26 AM >>>
Why "without much success"??
We're planning on developing a part of our product using servlets, and one
of our targets is OS/390.
> -----Original Message-----
> From: Alex P Deller
>
> We tried that approach of using Java Servlets on the OS/390
> mainframe without much success. What we did do is run IBM's MQ
> series as the middleware between CICS on the mainframe and the
> servlets on the webserver.
>
> >>> "Simonin, Bradley" <[EMAIL PROTECTED]> 05/03 2:39 PM >>>
> I am curious to know if anyone is writing Java Servlets on IBM's S/390
> mainframes?
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
