Search results for query: *

Steve, The messages can arrive frequently too. To your query, we have not used any SYNCPOINT as of now. MQ triggering the CICS transaction, I guess folks here are having some concern. will propose this design option anyway and try to understand why they are not interested, if so. Thank You...

Thanks Steve. Appreciate your quick response on this. The program (rather transaction) will be shut down in two scenarios - 1. when the program receives a "special message" saying 'STOP THE EXECUTION' or 2. the operator terminates it before bringing the CICS down at the day end. The program...

Dear all, Can I free the working storage space occupied by the CICS program when the transaction is in active state itself. The background is From CICS program I am reading messages from queue manager (in MQ server)and once all message r processed, the program goes to sleep state. again when...

Greg, Marc Thank you very much for your suggestions. It's a great start for me in this Forum.... Last couple of weeks it's of great help to me to get your help and opinions.. "at the very right time" Yes. You both are right. Index is the key which made the difference. The idexes are...

Hello Marc, You are right. The data is different. The input is NOT exactly same. However the total no. of records in each run is "almost" same. When the data is not much changed but the CPU time varying that much is what raise suprise to me. One observation is out of 4 test runs...

Marc, Thanks for your response. The total number of records in different runs are around 6 million records. That is absolutely right. But the data are surely bit different. However we could not understand the erratic nature of the Job behaviour or CPU time. The input files are not locked by...

Hi All, We have observed that a JOB with same input and load module takes different CPU time, when we submitted it for testing in different instances. The COBOL program is using DB2 and flat files as input. The time difference is in Hours, 1st run it took 2 Hrs. 2nd run it took 13 min...

Thanks Greg. The information was very useful. The performance of the job has improved. However still it's taking few hours. Let me explain what am specifically looking for.... We have 2 data bases containing around 7 million records. We are suppossed to process around 25 thousand of records...

Dear ALL, We want DB2 to stop searching the table once the first occurence of the predicate is satisfied.(i.e. Once the condition is met, DB2 should stop further processing the querry) Is this possible in DB2? - We are accessing a DB2 table with millions of records, so optimized querry...