It's been a while, but perhaps I can help. 

Unlike CICS, IMS is not normally conversational. You enter a transaction and 
IMS moves it from queue to queue until the unit of work is complete. If the 
transaction so chooses, a reply of some sort may be sent back to the entering 
terminal. 

It is reasonable to suspect that one or more resources are not available and 
the transaction is waiting in some queue. It's been too long for me to be able 
to suggest ways to identify what resources may be causing the issue. I seem to 
recall some sort of detailed report (DC Monitor?) that can be activated. 

But it is also reasonable to suspect that the transaction has simply not sent 
anything beck to the terminal. 

As I recall, the most basic form of a transaction was to clear the screen, then 
enter the transaction name. The transaction would then send a formatted reply 
to the terminal. 

You can pre format the screen with a /FOR command if you know the format 
(message output descriptor or MOD) name.    

I've never had occasion to use the /SET TRAN command. If you are finding that 
you have to use it, then perhaps the screen is being formatted without the 
transaction name as the first eight bytes of the input message. 

Having some experience with both CICS and IMS, I would not say that one is any 
easier to use than the other. IMS may be a bit more complicated, but it tends 
to scale well.        

HTH and good luck.    

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of 
David Logan
Sent: Wednesday, May 20, 2009 9:09 AM
To: IBM-MAIN@bama.ua.edu
Subject: "CEDF" type of ability in IMS??

Thanks all to those who helped me get through step one in IMS. It's pain in
the butt, a lot of stupid little pieces and parts and steps, but it's not
that hard once you know what the pieces and parts and steps are. I got one
of my two transactions working. However, the other one still isn't, and I
see no obvious reason. No messages or anything. So my question is this:

 

Is there some type of debug/log ability in IMS (perhaps similar to CEDF in
CICS)? Is there an easy way for me to tell that it may be trying to access a
DBD that doesn't have a file or something? I don't know why it just ignores
me when I type the transaction in.

 

As a secondary question, now that I'm thinking about it. My developers
appear to be used to logging onto IMS, signing in, then just typing the
transaction. Currently, I have to do a /SET TRANSACTION XXX" before I can
type in XXX. What is the magic to not have to do the /SET first?

 

Thanks!

 

David Logan


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to