Starting a Process Flow from a batch job

How about a custom 4GL process to take care of step#2 ? Read the CSV file, exclude specified pay codes, write a new CSV file that is then input to PR530 in step #3

What version of process flow are you using? If you're using Process Flow Integrator, or Infor/Lawson Process Automation, you should be able to do all 3 steps in a single process flow.

1. Use a WebRun node to kick off an HS535 program. Use the WAIT=TRUE parameter on it so it doesn't move to the next step until it is done.
2. Use a Data Iterator to iterate through the HS535 output. For the records you want, write them to a new file, skip the records you don't.
3. Put your new file in the PR530 input location
4. Use a WebRun node to kick off the PR530 program, using the WAIT=TRUE parameter again.

That way you can just schedule 1 flow via the Process Flow scheduler and not worry about any batch jobs.

Writing the Process Flow to create the CSV is easy (step 2). Even creating a flow to kick off the jobs for step 1 and 2 is easy. But I need just the opposite - how to execute a flow, from a Windows Server command - which can then be part of a multi-step batch job. These are jobs that the payroll supervisor will run "on demand" so they can't be scheduled. I was hoping to just have one job that would do all three things for him.

You should be able to use the FileClient utility to trigger the flow from the command line. This will trigger a specific flow on demand. A data file is required, but it can be empty if you wish.

What is the FileClient Utility? Never heard of that before. Is it Lawson supplied?

Yes, FileClient is supplied by Lawson. If you go to a Lawson command line and type "FileClient" you should see the help text. I think the minimum information required is the DataFile and the ProcessName.

There is a similar command named "ScanFileClient" which is a filewatcher version of this utility that will trigger a flow when a file with a specified name appears in a specified location.

Additional information is available in the "Processflow Administration Guide".

FileClient and ScanFileClient are only part of "Process Flow Integrator" and aren't included if you just have "Process Flow Professional". They are installed as part of the "BCI" (used to be "Business Component Integrator"). If BCI is installed on your server, you will have FileClient (Unix) or FileClient.exe (Windows) in your GENDIR/bin directory/folder. If they are not there, than BCI is not installed on your server, and (if you are licensed for "Integrator") you would need to download BCI and install it on your server.

Thanks for catching that, John.

My apologies for misleading you, Terry.

I tried the "fileclient" from a LID command line - no joy. We do have PFI, but we're a Managed Services customer so guess they would need to install it.

The command is case-sensitive; try "FileClient" on the command line.