We have a main CICS Driver program which calls many DB2 programs.
One of the called program has ADD, DELETE and CHANGE functionality.
I have no issue with ADD but got an timeout error in web side when we hit the DELETE functionality. Mainframe side we are successful in doing the DELETE functionality and pasing back to web successfully.
Do you guys have similar kind of expereince in the past who can help me out.
Joined: 06 Jun 2008 Posts: 8280 Location: Dubuque, Iowa, USA
I suspect you won't get many answers without a lot more explanation. You say you have a main CICS driver program but the next paragraph you're talking about timeout error in the web side. What web side? CICS is a stand alone product -- you can interface it to the web but people who start out talking about CICS driver programs aren't generally connecting from a web site since the web site would usually be driving the process.
It sounds to me like this is a web server question being posed as if it were a CICS question. If the mainframe side is successfully doing the DELETE and going back to the web as you say, why on earth would you expect CICS people to have any clue what is going wrong with the web side? Especially since you don't bother mentioning the details -- like how does CICS connect to the web, what program(s) are used on the web side, how you know the mainframe is passing back to the web successfully, what type of communication link is being used, whether you've used a trace function or other facility to determine what's going on, if you have had your network people trace the data to see if there's a router issue, and so forth and so on.
I am really sorry for the confusion. I will try to explain in detail.
Ours is a web and Mainframe architecture connected through MQ.
On java side we have add, delete, update functionality on a single screen. In mainframe we have a main CICS cobol driver program which in turn calls many called DB2 programs. Like I said, One of the called program has the ADD, DELETE, UPDATE functionality.
Java screen will populate the request queue based on the functionality selected(A for ADD, D for Delete and U for update) and mainframe driver module picks up the information from request queue and pass that to the called module.
Called module will evaluate the function code (A or D or U) and do the processing accordingly.
Here is the problem.
The called module process ADD functionality and send the information back to main mainframe driver module and this main module will post this information to the response queue and Java code process the response correctly.
When web sends D or U function code, mainframe process send backs to MQ. but we get an error 'timeout error' at web side.
Does anybody experience this kind of error and I hope i drafted my problem clearly.
Thanks in Advance.
Reason for the Ban: Multiple IDs are not allowed in the Forum
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
Don't know if the will relate, but an INSERT shouldn't need to wait for some row(s) that are locked to be freed. An update or a delete may experience a wait because some row(s) are locked by some other process.
You might put some diagnostic code in the update/delete parts of the mainframe code to track what is happening.