T24: R07.004 T24 Service Error

[Ahmed Ali Nisar]

Dear All,

I am facing a problem with a service with following error

=================================================================================================

Agent 44 started 20 SEP 11 18:23:43

Agent's Process id 17833

Running on server JSBPRD01 PortNumber 7

_PK.OFFBAL_PK.OFFBAL_44_20 SEP 2011_18:23:43_Standard multi-thread job

_PK.OFFBAL_PK.OFFBAL_44_20 SEP 2011_18:23:43_Calling load routine

_PK.OFFBAL_PK.OFFBAL_44_20 SEP 2011_18:23:43_Updating the Locking with PK.OFFBAL-PK.OFFBAL-1 and F.JOB.LIST.3

_PK.OFFBAL_PK.OFFBAL_44_20 SEP 2011_18:23:43_Session not doing SELECT  processing 608 75542

_PK.OFFBAL_PK.OFFBAL_44_20 SEP 2011_18:23:43_Processing...11 Offset...484 Number of sessions...54

_PK.OFFBAL_PK.OFFBAL_44_20 SEP 2011_18:23:43_Processing...4 Offset...181 Number of sessions...54

_PK.OFFBAL_PK.OFFBAL_44_20 SEP 2011_18:23:43_Processing...1 Offset...70 Number of sessions...54

_PK.OFFBAL_PK.OFFBAL_44_20 SEP 2011_18:23:43_Processing...36 Offset...28 Number of sessions...54

 ** Error [ EXIT_TRANS_ABORT ] **

TRANSACTION ABORT forced as transaction open when program terminated

jsh sep19ac ~ -->

=======================================================================================================================

The F.LOCKING application contains the record PK.OFFBAL-PK.OFFBAL-1 and doesn't clear, I am convince that the  service is abnormally terminated and re started and as

a result the Select routine of the service is not thrown by the system where some file variable has been assigned for sequential writing in the main routine.......

looking forward for your views and solutions.....

--
Ahmed Ali Nisar          

Temenos T24 Consultant

Sapphire Consulting Service

+92 345 330 6585

[VK]

Hi,

Stop all services and tSM, clear file F.TSA.STATUS and all
F.JOB.LIST.n, where n = 1...x (when you get "no file" error you can
stop); then restart all anew. If the error still there:

looks like PK.OFFBAL is a local service? Might be that some
programming error leads to CALL FATAL.ERROR. Try to DEBUG it.

If it's core - write to Temenos helpdesk.

VK

> *Ahmed Ali Nisar          *

[Ahmed Ali Nisar]

Hi VK,

    thank you so much we have able to fix that error by clearing the Job(s) list .... how ever there was no programming error as i debug

the service quite a few time and the same error reproduce once i break the session manually.....

--
Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines

IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24

To post, send email to jB...@googlegroups.com
To unsubscribe, send email to jBASE-un...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en

--
Ahmed Ali Nisar