If another job works with that jobcard, then the problem is with the JCL not the JOBCARD, if the job works with the JCL but not that jobcard, then the issue is with the JOBCARD.
You should see the JCL error identified fairly clearly in the JESYSMSG DD under SDSF or IOF (that's the part that says what datasets were allocated and the condition codes, etc., but also shows the JCL error(s)). If there is nothing listed, and it is the JOBCARD that still seems to be the issue, then it's a issue with the IEFUJV exit that they are using. If you don't see any messags that identify the error, and it is the JOBCARD, then the only solution is to figure out what the IEFUJV exit wants. I suppose it could be a JES2 exit as well, but typically the exits would/should put something out to denote the error that it sees. I support DOD sites as well, and you can post the output to get the error fixed, just blank out any secret stuff, like the actual Account and actual user and even the dataset names if you think it's necessary. There is no DOS or Federal rule about not being able to pass on generic information to get a solution to any problem. Someone has led you astray to make you think otherwise. Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
