Transaction name for a CICS program.

Customer Information Control System. Middleware and MQ Series.
Previous topicNext topic

Topic Author
Kapil Sharma
Registered Member
Posts: 43
Joined: Sun Sep 29, 2013 1:46 am
Location: India

Transaction name for a CICS program.

Post by Kapil Sharma » Thu Jan 25, 2018 10:31 am

Hi,

I used to believe that a CICS program will always have an associated transaction name but at this new company I have been told there are some CICS programs which are never invoked directly on terminal and don't require a transaction name. These programs are called by the other application (not on mainframes) and provide them back with a response.

Now, in such a situation how would I know that which CICS program is a called by some third party application and which one is not?


Thanks,
Kapil

User avatar

Robert Sample
Global Moderator
Global Moderator
Posts: 1379
Joined: Fri Jun 28, 2013 1:22 am
Location: Dubuque Iowa
Zodiac: Virgo

Re: Transaction name for a CICS program.

Post by Robert Sample » Thu Jan 25, 2018 6:06 pm

Extract the CSD into a data set. Check that data set for transactions with the program name. If you find no transactions associated with the program, then it is not invoked from a terminal.




Topic Author
Kapil Sharma
Registered Member
Posts: 43
Joined: Sun Sep 29, 2013 1:46 am
Location: India

Re: Transaction name for a CICS program.

Post by Kapil Sharma » Sun Jan 28, 2018 6:30 pm

Thanks Robert.

I tried using this command and this gives result -

Code: Select all

CEMT I TRAN(*) PROGRAM(*) 
but I can not copy that information automatically to a notepad for future reference.

Is there a way I can run CEMT in batch?


Thanks,
Kapil

User avatar

Robert Sample
Global Moderator
Global Moderator
Posts: 1379
Joined: Fri Jun 28, 2013 1:22 am
Location: Dubuque Iowa
Zodiac: Virgo

Re: Transaction name for a CICS program.

Post by Robert Sample » Sun Jan 28, 2018 8:57 pm

There probably is a way to run CEMT in batch, but why bother? Extracting the CSD uses JCL that is available in the manual, provides what you want at a small cost of having to scan the output, and does not require experimenting to get CEMT running in batch.



Previous topicNext topic

Return to “CICS, Middleware and MQ Series.”