Those are PSF exits. If you reassembled and relinked they should work the same. A full external trace can show everything sent to the printer.
On Wed, Aug 10, 2022, 2:08 AM Tommy Tsui <[email protected]> wrote: > We didn’t change any printer definition and default line per page.we use > default separator exit only. Any change we need? > > 「Tommy Tsui <[email protected]>」在 2022年8月10日 週三，下午3:27 寫道： > > > Hi Brain > > Thanks for your information. After I checked, we already assembled all > new > > separator exit APSUX01 & 02. The new page inserted after a separator > page. > > We don’t know why. The data seems not problem. All new page break are > > correct. > > > > 「Brian Westerman <[email protected]>」在 2022年8月10日 週三，下午1:13 > > 寫道： > > > >> I am assuming that you are printing with JES2 and not VPS or some other > >> remote print product. > >> > >> This can happen if you didn't re-assemble your separator exit. Although > >> it can happen with VPS as well if you forget to assemble it, but VPS is > >> good about telling you if you forgot. JES can mess up if the exit > didn't > >> assemble cleanly, or > >> > >> Do you notice that the data your exit is putting out is not being > >> inserted into the separator? Also, this can happen if your printer > >> definitions have changed between the releases. > >> > >> Did you change your default lines per page for the printer. IF your > >> separator is larger than the page, it will cause an extra eject. > >> > >> IBM says "Some printers do not reposition to "top of forms" after the > >> trailer page. To avoid feeding blank pages through your printer, > include a > >> page eject statement in your exit routine following the trailer > separator > >> page." If your problem is a blank page after the last separator, then > this > >> is likely to be the reason. > >> > >> Otherwise, I need more information to help you debug this. > >> > >> Brian > >> > >> ---------------------------------------------------------------------- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected] with the message: INFO IBM-MAIN > >> > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
