Here we have a requirement such that a job should not get submitted when the job has production files ie those start with 'LS.' or 'LSV.'. Can we restrict this by any means. The important thing is even a PROC should not contain these files. Any solution to this..??
a job should not get submitted when the job has production files
Most installations are content with using security prodcuts to prevent execution of jobs based on combinations of, say, jobname, submitter, dataset access &c. Why would it matter whether the job can be submitted if it can't execute? If the security product logs violation attempts, follow-up disciplinary action will dissuade submitters from re-offending.