OVRPRTF

70 pts.
Tags:
AS/400
OVRPRTF
SPLF
HI, I need to print a back overlay only once per SPLF. The program does the OVRPRTF upon initialization, it prints the Front and Back overlay for the first page, But I don't need it for the subsequent pages, so I do a DLTOVR, OVRPRTF (BackOvl = *NONE), OPEN, but now it will create a new spool, which I don't want. I have also tried CHGPRTF, with same results. Any thoughts would be greatly appreciated. Thanks!

Software/Hardware used:
RPGLE

Answer Wiki

Thanks. We'll let you know when a new response is added.

 

Discuss This Question: 9  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    Is anything else printed on the backs of any pages? Or is all printing done only on one side of each page? . Tom
    125,585 pointsBadges:
    report
  • philpl1jb
    I don't believe this is possible.
    49,910 pointsBadges:
    report
  • TomLiotta
    It's almost certainly not possible using the BACKOVL() attribute of a PRTF. But it MIGHT be possible with the OVERLAY() and DUPLEX() record-level DDS keywords. Set it at the first end-of-page only. If a program writes the right record at the right time, it might work. Maybe. . Everyone I've seen in the past tried to use just BACKOVL() and had no success. That seems reasonable because it's an unconditioned file-level attribute. But doing it under program control at the record level should be different. (Otherwise why have the DDS keywords?) . I haven't tried, nor do I have a printer for it. . Tom
    125,585 pointsBadges:
    report
  • Rogueldr
    Thanks guys for your replies. I too believe that is not possible based on my experience, I just needed your backup so that I can inform the powers-that-be. Much appreciated !!!! MTFBWY...
    70 pointsBadges:
    report
  • BigKat
    I think Tom has it... if you use the AFPDS print file keywords, and you actually write the overlay into the spoolfile instead of trying to override it, you can do it. I haven't done a back overlay, but have done on the fly overlays on arbitrarily defined pages.
    8,200 pointsBadges:
    report
  • WoodEngineer
    Hello BigKat, I am very interested to know how your did overlays on the fly. That sounds like a useful technique.
    6,640 pointsBadges:
    report
  • TomLiotta

    I suspect that "on the fly" refers to supplying an OVERLAY() name at run-time, rather than creating a new overlay. It's just printing a record with OVERLAY(&fieldname). Put the overlay name in the field before writing the record. Change the variable value when you want a different overlay. That's a major reason the OVERLAY() keyword exists. (But if BigKat has more interesting methods...?)

    Later releases have more features than earlier. The various manuals and Printing* RedBooks tend to supersede parts of each other. In Printing VI, I see this piece:

    2.9.2  Adding a constant back to a subgroup

    It is common practice to print a “Terms and Conditions” page on the back of a document such as a company invoice or statement. With subgroup processing, we can do this using a function called constant back. This is a useful feature of form definition processing. Without this, the application would need to track what pages were to be printed in simplex and what pages in duplex, and insert a blank page at the appropriate points.

    I haven't seen examples anywhere, but that description implies that there are two general methods of printing back-overlays. One prints the same overlay on the back of every page, i.e., use BACKOVL(), and the other is under application control and prints selected overlays on the backs of selected pages.

    Necessary DDS keywords would seem to be OVERLAY(), DUPLEX() and perhaps ENDPAGE (if SPACEn and-or SKIPn aren't sufficient). It might also be necessary to have a record format that either skips a page or prints a 'blank' page. I'm not sure what happens if you simply write a new record with DUPLEX(*NO) and then don't print any more OVERLAY() records.

    If anyone can do some testing, it'd sure be nice to add info to this question thread.

    Tom

    125,585 pointsBadges:
    report
  • BigKat
    Tom is correct, OVERLAY(&fieldname) :)
    8,200 pointsBadges:
    report
  • Rogueldr
    HI guys, I'm going to give your suggestion a try. i will inform as soon as i have results.   Thanks !
    70 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following