IBM MAINFRAME HELP FORUMS for COBOL, JCL, CICS, DB2, IMS etc...
Help & Support Forums for IBM Mainframe computers Applications like COBOL, JCL, CICS, DB2, FileAid, DFSORT, Endevor, Xpediter, CoolGen, CA-7, CA-11, AbendAid, IMS, IDMS, PL/I, MqSeries, SyncSort, Assembler, VSAM, ISPF, ChangeMan, Easytrieve, InterTest, REXX, CLIST etc...
 

Disadvantages of increasing the SEGNO?

THIS IS AN ARCHIVE FORUM: CLICK HERE TO GO TO THE ORIGINAL TOPIC

 
       IBMMAINFRAMES.com - IBM Mainframe Support Forums Index -> IMS DB/DC
View previous topic :: View next topic  
Author Message
AshimSreedhar



Joined: 18 Apr 2008
Posts: 6
Location: Canada
Posted: Sat Jul 12, 2008 1:46 am    Post subject: Disadvantages of increasing the SEGNO?  
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!
Back to top  
 
       IBMMAINFRAMES.com - IBM Mainframe Support Forums Index -> IMS DB/DC
Page 1 of 1
THIS IS AN ARCIVE FORUM IN READ ONLY MODE. IF YOU WANT TO ASK YOUR DOUBTS USE THE ACTUAL FORUM
Related Links