When Lawson batch jobs are not running, they return the following error:
User: lawson Job: C Queue: **********
BEGIN: Job Submitted: Wed Dec 6 11:30:01 2017
Step 1: CU201 Started. . . . . .: Wed Dec 6 11:30:01 2017
Token Command. . . . . .: D:\lsfprod\law\prod\obj\CU201.
Executable Command . . .: D:\COBOL\bin64\run.exe D:\lsfprod\law\prod\obj\CU201.
Running as Account . . .: \lawson
Load error : file ‘lacobrts.dll’
error code: 173, pc=0, call=1, seg=0
173 Called program file not found in drive/directory
Elapsed Time . . . . . .: 00:00:00
ERROR: Stopped On Exit 32. Elapsed Time: 00:00:01
END: Job Ended: Wed Dec 6 11:30:02 2017
The error message from the job log indicated a problem with lacobrts.dll. The actual problem was related to the local security policy. This error was resolved by reviewing the setup for the lawbatch id. The LSF system in this example had a secured ldapbind. The domain lawbatch id should be added to the Local Security Policy under User Rights Assignment for “Log on as a batch job” and “Allow log on locally.”