AshimSreedhar
New User
Joined: 18 Apr 2008 Posts: 10 Location: Canada
|
|
|
|
Hi,
This is regarding the keyword SEGNO in IMS TRANSACT macro. As per IBM manual SEGNO Specifies the maximum number of application program output segments that are allowed into the message queues per Get Unique (GU) call from the application program.
We have a transaction which contains SEGNO as 2000, but keeps on abending with a U0499 abend code. When I ran a Performance report using the IMS log, I found that the transaction reached the 2000 segno insert limit for DC Call ISRT.
So my doubt here is
1. Is SEGNO limit applicable for ISRT call??? (IBM manual says only about GU call)
2. If I increase the SEGNO of the transaction to say 4000, will there be any risk? Will it affect the performance.
My transaction has the following properties
Code: |
TRAN CLS ENQCT QCT LCT PLCT CP NP LP SEGSZ SEGNO PARLM RC
TRANSNM 14 741 0 2 3 8 8 9 0 2000 NONE 0
|
Any info on this will be really helpfull...
Thanks,
Ash! |
|
dominickim
New User
Joined: 28 Feb 2007 Posts: 65 Location: NS, CA
|
|
|
|
My opinion is that your transaction can be handled upto 2000 segs no matter what kind of call and I don't think it cause any big issue if you change that to 4000. Many report transactions are using multi-seg option as well, why don't you use PURG before it reaches 2000? |
|