Our normal QDATFMT is *MDY. (Arrrgh!!!)
I am running an SQLRPGLE that does this:
**----Set Option must be first code in program.----------------* /free EXEC SQL SET OPTION DatFmt = *ISO, Commit = *NONE, CloSqlCsr = *ENDMOD; /end-free
The SQLRPGLE builds a file which is copied in the clp to the IFS as a CSV (excel) file and then the CSV is emailed (using our MFG software package commands).
This program/application runs fine interactively. I am trying to submit it with a self submitting clp. The job is submitted, the file is built, I have data on the IFS. The CSV is not emailed due to a message from the canned software (which we do not have source for this program).
From what I see in the joblog.
CPF3C17 Message . . . . : Error occurred with input data parameter. Cause . . . . . : An error occurred while copying information from the input data parameter. Recovery . . . : Do one of the following and try the request again: -- Verify that the input data parameter is correctly specified. -- Verify that the value for the length of data parameter is valid.
I do not see this message if I run the program interactively. I am wondering if the SQL set option for the date format stays with the job when the program ends. But that does not make sense either. If it was a case of the date being in a different format than the software expects, I would get that message when I run interactively.