-
Forum
-
T24 Technical Discussions
-
T24 Development & Customization
-
CLEAR-FILE F.LOCKING
CLEAR-FILE F.LOCKING
-
yap
-
Topic Author
-
Offline
-
New Member
-
Less
More
-
Posts: 2
-
Thank you received: 0
-
-
2 years 11 months ago #23761
by yap
Made a mistake using CLEAR-FILE F.LOCKING LIKE ...<job_name>... during a COB run
What will happen and is there a way to revert or fix this?
Please Log in or Create an account to join the conversation.
-
VK
-
-
Offline
-
Platinum Member
-
-
Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
Less
More
-
Posts: 1209
-
Thank you received: 158
-
-
-
2 years 11 months ago - 2 years 11 months ago #23763
by VK
Hi
no backups I suppose?
There are several records that are mandatory for working... minimum set is:
JOURNAL
001 0
MB.CLIENT
001 N
002 Non Model Bank Client
Check for the latter if it's your case...
Other quite necessary records - LIKE "...'.UNIQUE'"
e.g.
AA.ARRANGEMENT.UNIQUE
001
002 12
003 AA
DX.ORDER.UNIQUE
001 0123456789
002
003 DXORD
Similar to them are ones LIKE "'F'...".
If you lost them - try to imitate a change in AUTO.ID.START records and authorise them; records in F.LOCKING will be recreated.
Finally, create a record BATCH.START.DATE:
BATCH.START.DATE
001 >>> bank date when COB started, e.g. 20220728
002 >>>> your COMPANY @ID
Nearly forgot... for multi-threaded COB jobs there's info in F.LOCKING about which F.JOB.LIST.n file holds records selection...
Cheers
VK
Last edit: 2 years 11 months ago by VK.
The following user(s) said Thank You: yap
Please Log in or Create an account to join the conversation.
-
yap
-
Topic Author
-
Offline
-
New Member
-
Less
More
-
Posts: 2
-
Thank you received: 0
-
-
2 years 10 months ago #23770
by yap
Thank you VK, managed to resolve it and has completed fine
Please Log in or Create an account to join the conversation.
-
Forum
-
T24 Technical Discussions
-
T24 Development & Customization
-
CLEAR-FILE F.LOCKING
Time to create page: 0.038 seconds