Segmentaion Violation while running as an agent

[rahul vk]

Hi all,

 

I am seeking your help in my program which is causing a segmentation violation when run as an agent (TSA). If I run the same program in mainline it is working fine. Actually the program is for deleting records in one File. Normally the selection contains more than 6000 records. Any one has an idea why this segmentation violation is happening when run as an agent.

 

Details: jBASE release (4.1.5.18) running on AIX

 

Thanks in advance

Rahul

 

[ramanna]

Hai Rahul,

Which release of T24 are you in? Have you checked if there is any
'journal update' call in your program?

Cheers,
Ramanna.

[rahul vk]

Hi Ramana,

 

T24 Release is R06.005 . There is no Journal update in the program.

 

 

Regards

Rahul

[guru...@gmail.com]

Hi Rahul,

I think the problem is happening in EB.TRANS routine. Earlier we have
faced this same problem and found the cause later. This problem will
happen when T24 system trying to commit the transaction but the buffer
is unable to hold the data. As you mentioned 6000 records are selected
for processing the possibility is very high. Please try the following
to solve the problem.

1. Change the field 3(ADDITIONAL.INFO) in PGM.FILE to .NTX
2. Optimize your select statement, so that minimum number of records
will be selected for processing.
3. Check and change the " ulimit " settings in necessary.

Cheers

[rahul vk]

Hi ,

 

Thank u very much for your help. It is running fine after changing additional.info to .NTX .

also i changed SSELECT to  simple SELECT.

 

Any idea  what .NTX stands for ( previously it was R - rerunnable job)

 

Thanks

 

Rahul

 

[guru...@gmail.com]

Hi,

.NTX means no transaction management. Batch routines will not call
EB.TRANS if the PGM.FILE is set to " .NTX ".

Cheers

[Andrew Trusov]

Hi Rahul!
I think instead of using .NTX in PGM.FILE (which is quite good idea) you can slightly change *.SELECT part of your program adding e.g. "SAMPLE 1000" to a SELECT or SSELECT statement. But in this case you'll need to run your service several times or set in TSA.SERVICE 5.SERVICE.CONTROL to "AUTO", but such solution may not fit your business requirements.

2007/12/21, rahul vk <rahul...@gmail.com >:

--
А писал все это Барисыч - Google'оид со стажем.

[Pawel (privately)]

Hello,

Do not forget to raise bugreport via HD ;)

".NTX" was explained by well by gurujmani. Core will not start database
transaction for you. Always set it for reporting jobs (reading data) to
get performance boost.

Kind regards
Pawel

----------------------------------------------------
Jak zrobić to na 7 sposobów?
http://klik.wp.pl/?adr=http%3A%2F%2Fwww.swieta.wp.pl%2Fmagiazyczen%2F&sid=146

[Arindkar]

can you ensure your ULIMIT set to UNLIMITED?
Arindam