Major printng problem

[dennisw]

When you print from profound programs I understad print jobs go to QPRTJOB. I need to print a form to certain outq. In the program I am sending an OVRPRTF to direct the form to the right outq.

When I run the program directly it works. When I run from Atrium it doesn't. The command is being sent from the program that prints the file.

What gives?

[Alex]

I believe this may have something to do with the OVRSCOPE (Override Scope) parameter on the OVRPRTF (Override Printer File) command. The default value for this is *ACTGRPDFN. You can try changing this value to *JOB on the command. The original program may have ran using DFTACTGRP(*YES) and it was probably changed to DFTACTGRP(*NO) for Rich Display File programs.

[David]

I can't think of any obvious reason why it would/should work any differently when run inside/outside of Atrium.

As far as I'm aware, there is really nothing different about the job when running in Atrium or outside. Atrium just calls the Profound UI session as normal, which then does a security check (i.e. can the user run this program, according to Atrium) before running the program. Other than that, the application's job should be identical.

Obviously something is different, though, if it's not working for you. I just can't think what it would be. The behavior with QPRTJOB and all that should be the same. By 'not working' can you explain a bit more on what is happening? What is the result? Any error messages or anything in the application job log when running in Atrium?

[dennisw]

What I do in the program is call a prototype that determines where the form should print and calls an OVRPRTF. After the protype call about 5 lines later the print file is opened. When I call the program directlly, that is by starting from profoundui/start this works fine. The form prints where I want it. Whe I call the program from Atium it's as if the OVRPRTF was never called. Instead of printing to my desired outq it prints to PRT01 which is the default outq.

[David]

Maybe it's a silly question, but have you debugged the application to see if the OVRPRTF command is actually being run in this case? I'm not sure if it's conditional or not, but you do mention calling something else to determine how the override command should run, so maybe there is something to it.

I'm guessing something along these lines, as I don't really see any differences between running the session inside/outside of Atrium that should affect this.

If that's not it, could you provide a simplified example (like bare-bones RPG program that produces output from a system printer file) that demonstrates the problem so that we can test here?

[dennisw]

I debugged it and the command was sent. I changed to OVRSCOPE(*JOB) and that seems to have solved the problem. It works in Atrium and when calling directly.