× Discuss on Template programming, jBASE programming, Enquiries, No-File enquiry, Enquiry routines, Version, Version routines, Menus, Abbriviations, Creating local reference fields, Fast path enquiries, Creating charts and graphs, Generating Reports, Deal slips, Straight through processing, Multi Company and Multi Book setup, Tabbed screens, Composite Screens, T24 API, etc...

Bypassing...

  • Comrade
  • Topic Author
  • Visitor
  • Visitor
16 years 11 months ago #1007 by Comrade
Bypassing... was created by Comrade
Hello,

What is the need of bypassing Batch jobs while running COB and how could we generate the missing reports after the COB process??


Thanks in Advance,

Please Log in or Create an account to join the conversation.

More
16 years 11 months ago #1008 by malai
Replied by malai on topic Check This
Which version of T24 you are running?



Normally in TSM, you need to do the following steps to bypass a particular job.

1. Mark the COB record in F.TSA.SERVICE to STOP.
2. Wait for sometime and check the tSA's are dead except tSA 1. If not kill the agents :-((
3. In jBASE prompt, SELECT F.BATCH WITH PROCESS.STATUS EQ 1.
4. Edit the selected batch record in jBASE prompt and set the JOB.STATUS for the running job to 2.
5. If the batch record contains only one job, then set the PROCESS.STATUS to 2.
6. In jBASE prompt, SELECT F.BATCH.STATUS WITH WITH F1 LIKE ...processing...
7. Change the value from processing to processed
8. In jBASE prompt SELECT F.TSA.STATUS WITH @ID GT 1
9. Inside the above select DELETE F.TSA.STATUS
10. Now again mark the COB record in F.TSA.SERVICE TO START.
11. Check whether the agents picked up the next job.


Which mismatch report you want to generate. For RE.STAT.MISMATCH verify the respective record in RE.STAT.MISMATCH.



___________

Thanks

Please Log in or Create an account to join the conversation.

Time to create page: 0.087 seconds