To all:

Odd issue. This program is kicked off by Lawson via the WH32 screen Special Actions button "Print".

Our users run this MANY times each day without issue. Every now and then one will abort with the message:

PrtDtlGrp: LINE.SkipCnt < 1 (Grp 12, Line 0)

I delete the job in recovery and they go back into WH32 and hit print again. It always works when the redo it.

Any idea what could be causing this?

Apps 8.0.3 MSP8
Env 8.0.3 ESP6
Unix
Oracle

Thanks in advance

Laura:

We happen to have a copy of that program, although we don't use it. So I looked at it. It is medium-sized, just over a thousand lines.

My interest is intrigued by the fact that it works when you re-run it. I notice that the code prints out comments, among other things. I believe that the error you're getting is when it fails to find anything to print -- even though there's something to print when you re-run it. That means that the data is really there, the program just can't get to it.

Due to the erratic nature of the problem, I conclude (best guess, worth 2-cents or less) that the records are locked or not yet written when the program attempts to grab them to print.

Solution: Make sure that the whatever-it-is that WH224 is printing is completely closed out and not 'in use'. If the problem persists, you may have to decrease the database write latency.

(We have a similar problem here when people open up reports and are looking at them when they submit the same job for another run. The program bombs out with a '9 065' error, meaning that the program couldn't delete the old report before creating the new report.)

I hope that this helps.

Following Milo's thoughts - if you believe that its because the program is already running, then I have an idea for you. If your users are all running this program often, it's possible that they may submit the program (nearly) simultaneously. Perhaps this is the cause? To prevent the programs from running simultaneously, change the program-setting to "non-concurrent execution". No recompile is needed and technicall it's not a "mod". The typical MSP should not over write this (but a new install would).

To update this flag go to:

pgmdef
- enter product line, "WH" in the system code
- use the arrow keys to find your program and when it's highlighted, choose "F6 (define), "A - Program"

- arrow down to "Execut" and change the setting to "Non-Concurrent" (hit 'N' or use your F4 key)

Save the change. After that multiple submissions of the program will then "wait in line" until the other one is done. If these programs are quick, then the end user will notice no difference other than a few seconds lag.

Keith