Trigger for archiving user print jobs

We moved from an Iseries platform to Windows in the cloud. When on the Iseries, we had all the .prt files that were created from user jobs getting moved to an archive folder because they get overwritten each time. We are being told that on the Windows platform, we are not able to do that for our user jobs (PR141). So all of the user jobs gets overwritten unless the user remembers to save them off somewhere. This impacts auditing when we can't see each report that is output historically. Our developer has been successful in recreating a flow for the scheduled jobs. His issue is setting up the trigger for the on demand jobs that are run. Can anyone provide any help with this?

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

unknown

We use a date stamp on those jobs we don't want to be overwritten e.g. PR141M0530

vlaniauskas

We are in the process of attacking this issue as well. I am exploring creating a multi-step job where Step 1 runs PR141, then Step 2 is a tokendef that executes a script to copy print files from that specific user's job print directory to an archive directory, appending a date and time stamp. The user simply runs the Multi-step job and the output is copied automatically .... in theory ... still a work in progress. However, a different twist is introduced if the archive destination is another server, a share perhaps, so then, I'm trying to execute a powershell script in Step 2 which logs into the share on server 2 and executes the copy. Shoot me an email at vlaniauskas@srhs.com and we can discuss as I architect this thing.

sweta-priyadarshini

You might want to consider using PowerShell. There's a IO.FileSystemWatcher class that you might find useful. Here's a link to a script example.

gallery.technet.microsoft.com/.../Powershell-FileSystemWatche-dfd7084b

russel-cornelson

Just remember, you would probably have to additionally cd to the LSF Directory, set your environment variables "enter.cmd", then execute loadrpts to load those archived jobs into print manager. If you are just archiving them and don't care about seeing them in print manager you could skip that step and just leverage FileSystemWatcher to archive them

P.S to dbowen, great suggestion

unknown

Thank you all for the reply. I will pass this along to our IPA guy.

vlaniauskas

yes, sweet utility ... thx!

unknown

The loadrpts utility throws this error when run using IPA:
java.io.IOException: Cannot run program "sh": CreateProcess error=2, The system cannot find the file specified.
That command is run using the syscommand node. Any suggestions please?

Copyright © 2025 Infor. All rights reserved.