Bad File Status

We noticed our jobs are failing after refreshing our productline.  The job log is showing a bad file status error.   

This particular error was caused by windows permissions not being inherited.  Even though the owner of the applications directory was correct, it was not the owner of the files and folders underneath it.  This was resolved by setting the owner in the advanced security settings of the folder properties and running icacls to reset permissions on the files.

——————————————————————————–

User: domain\lawson                     Job: PR140           Queue: **********

——————————————————————————–

BEGIN:  Job Submitted:  Wed Feb 14 09:22:06 2018

Step  1:  PR140 Started. . . . . .:  Wed Feb 14 09:22:06 2018

Token Command. . . . . .:  C:\LSFDEV\law\dev\obj\PR140.gnt

Executable Command . . .:  C:\COBOL\bin64\run.exe C:\LSFDEV\law\dev\obj\PR140.gnt dev NT00000004 PR140 1

Process ID . . . . . . .:  4008

Running as Account . . .:  domain\lawson              

Program Messages:

** Creating .prt and .dtl files

Bad File Status 3 7 On File PRPAYRPTEN-FILE

Elapsed Time . . . . . .:  00:00:00

ERROR:    Stopped On Exit 1.

Elapsed Time:  00:00:01

END:    Job Ended:  Wed Feb 14 09:22:07 2018