CICS *is* an application server... and a transaction monitor. And CICS
does *not* contain "a proprietary setof APIs to read and write data sets
on a record basis." CICS customers generally use VSAM, DB2, or Adabas
for file access.
Whatever made you think CICS wasn't an application server?
FWIW, when I first read the EJB spec... I knew I was looking at the next
CICS. CICS is ubiquitous... albeit proprietary. I doubt that you could
achieve ubiquity today without the type of "openness" that we see in the
EJB and J2EE specifications. (I also doubt that EJB could achieve
ubiquity
without the expertise and support of IBM... but EJB seems to have that
aplenty.)
-eric
"Kenneth D. Litwak" wrote:
>
> CICS stands ofr Customer Information and Control System, generally pronounced
> like "kicks". CICS is NOT an application server. It is a transaction manager.
> It has a proprietary setof APIs to read and write data sets on a record basis.
> Exactly what the transaction management part is I never knew, except that you
> could comit and rollback your work.
>
> Ken Litwak
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
