Comments on: Overlay Printing Issue http://itknowledgeexchange.techtarget.com/itanswers/overlay-printing-issue/ Tue, 21 May 2013 23:11:32 +0000 hourly 1 By: qtrmaster http://itknowledgeexchange.techtarget.com/itanswers/overlay-printing-issue/#comment-105239 qtrmaster Thu, 22 Mar 2012 11:48:38 +0000 #comment-105239 Thanks Tom for your response. The CL I’m using is very simple:

PGM
OVRDBF FILE(GBLCTL03T) TOFILE(MOWENS/GBLCTL03T)
/* CALL RB530 */
CALL RB530B
ENDPGM

The overlay works fine when call RB530 but doesn’t work when calling RB530B. I call the CL program from a command line so the LIBL shouldn’t be a factor.

Below is the F spec that’s in both programs:

FRB530ZZ O E PRINTER

Below is the overlay in the PRTF:

A OVERLAY(*LIBL/RB530OL 0.250 0.250)

Keep in mind there is only one RB530ZZ on the system.

Thanks

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/overlay-printing-issue/#comment-105217 tomliotta Thu, 22 Mar 2012 00:09:57 +0000 #comment-105217 Any ideas?

Sure.

First idea is that the two programs don’t use the same printer file definitions. Perhaps because they use two different printer files or because they apply different overrides.

Second idea is that it’s a library list problem. It doesn’t matter if they’re called from the “same” CL or not; in fact, they might require different CLs, and calling from the “same” CL is what’s introducing the problem.

Third idea is that the execution of one program makes some underlying change to the program environment. When the second program runs, it behaves different from what is expected.

There are probably many variations of those three ideas as well as other ideas. Without seeing the programming, it could be almost anything. Seeing the CL should be the minimum needed to know what to suggest to try.

Tom

]]>