This content has been marked as final. Show 4 replies
Is the path to your preamble file appropriate for the production machine?
Could you put the preamble script in the JFPREAMBLE inside the template?
Hello Mr. Jeffries,
yes the path is the same for the production .
Our main problem, as written, we may not change the datastream , because
it is used by many countries . Therefore for our location , I've tried
to modify JFPREAMBLE. I've inserted this statement
in the JFPREAMBLE
It worked by test, but not , after complitaion , in the production environment.
Mnay thanks for your help and hope you have a solution to resolve this
I don't have a solution for you but I can suggest some more troubleshooting.
I would like you to run the test in Designer and then production with a greater verbosity on the log files.
For the test, in the Designer go to menu item Tools/Options and select the Test Presentment tag. In the Print Options box enter -n0
Also on the Test Presentment tab be sure that you have an entry in the Log Files for Print, and I suggest that you check the box Empty First. This will give you a new log for only the latest test.
Select OK and run your test.
When you review the log file you will see that all the preamble script is listed. Ensure that your ^file text has been included.
For your test using Central you can add the -n0 to the job statement in the data file (I recommend this) OR add it to the merge task. If the merge task is used by other jobs do not make the change here.
After running the test review the log file and see if your ^file text was included.
If it is included then you can compare the log from your test presentment with the log from your Central run to see what happens when this data is processed.
If it is not included there should be an error message indicating why it couldn't include it.
Just a note regarding adding parameters like -n0 to the job statement...
reference needs to be included for the task in question or the parameter on the job statement won't accomplish much.