This content has been marked as final. Show 5 replies
I don't know about changing the name after the file is created but the following is what I did.
When I first started testing with the software we were having a problem with the printer and a tech ended up deleting some of my test files before they printed because he didn't know what they were. I ended up specifying a default form in the JMD for the print task and then using the
parameter on the ^job line to skip the first page. Now all of our "FormsGen" print has a distinctive name that is recognizable by anyone.
So you now have a static name that appears for different types of prints is that it? What i need to do is to take a client number that exists in the pcl and use it as the printer job name.
Yes, it is a static name. I could have set up different tasks with different names but didn't feel the need to. Without specifying the form name in the task it appeared to just be random letters & numbers.
I've needed to extract field values from the DAT file for building the output PDF file name but not from the PCL file so that the print queue name reflects the information.
i see, ye it is turning out to be a bit tricky alright. If anyone else has any ideas please feel free to throw it out there!
The problem i can see now is that I am trying to replicate the step when the .tmp file which is also the same as the PCL file is processed from the collector directory.
When it is, it uses the value from the ics file \E%-12345X@PJL\x20RDYMSG\x20DISPLAY="default" the default is the mdf name which is static.
I use a Perl script and have a copy function to move the changed PCL file to the Printer spool queue, but the job name is now 'Remote DownLevel Document' in stead of the value in the PCL file.
Any body any idea as how to fix this?