Path: utzoo!attcan!uunet!ncrlnk!ncrcae!ece-csc!ncsuvx!gatech!uflorida!haven!rutgers!njin!princeton!phoenix!pucc!EGNILGES
From: EGNILGES@pucc.Princeton.EDU (Ed Nilges)
Newsgroups: comp.lang.misc
Subject: Re: CICS what is it?
Message-ID: <6150@pucc.Princeton.EDU>
Date: 22 Sep 88 00:49:00 GMT
References: <3923@okstate.UUCP> <8943@srcsip.UUCP> <5740@utah-cs.UUCP>
Reply-To: EGNILGES@pucc.Princeton.EDU
Organization: Princeton University, NJ
Lines: 28
Disclaimer: Author bears full responsibility for contents of this article

In article <5740@utah-cs.UUCP>, u-dmfloy%sunset.utah.edu@utah-cs.UUCP (Daniel M Floyd) writes:
 
>CICS.
>
>Since I don't know what it is, I don't know where to post;
>however, I think it's some sort of language.
>
>Could anyone tell me?
>
>Thanks.
 
Customer Information Control System was developed in the late Sixties
for IBM for medium to large scale business customers.  It runs under
the operating system to provide telecommunications and real time
response where the main operating system is a dinosaur batch-oriented
monster like MVS or DOS which runs preplanned "jobs" only; in other
words, it provides an online responsiveness in an environment that
is anything but.
 
CICS is controlled typically be user or vendor written programs
that issue calls on CICS functions such as "get storage for
this transaction" or "write data about this transaction".  Programmers
conversant with CICS calls and especially those conversant with
CICS internal control blocks make big bucks.
 
The last time you were in the hospital, bleeding copiously onto the
reception desk while the clerk banged away at an enormous IBM
terminal, the system was probably CICS.