Brad,
  The symptom of page ejects for each DISPLAY is usually caused by the FOPEN of
$STDLIST. I think to only way to avoid this from separate process (or fopens)
is to redirect these to a file (with an append option), then print the file.
You may have to use ;NOCCTL on the file...

Now that I think about it, you might try setting a file equation with ;NOCCTL
and redirecting this to $STDLIST & see if the formfeeds go away...(it's been
way too long since I had to solve this problem...)

Rich "shooting from the hip after a long weekend!"
_______________________________________________________________________
 Rich Trapp "RAT"
 Managed Business Solutions   [log in to unmask]   http://www.mbsnav.com
 Assigned to: TMO Design Automation Support at HP Loveland, CO
 (Telnet) or (970) 679-2221   [log in to unmask]
_______________________________________________________________________


-----Original Message-----
From: [log in to unmask] [mailto:[log in to unmask]]
Sent: Tuesday, June 01, 1999 8:38 AM
To: [log in to unmask]
Cc: [log in to unmask]
Subject: Avoiding page ejects with Cobol/Transact DISPLAY statements


I've got a Cobol programming running in a job that does a DISPLAY statement
just before it creates a Transact process. The created Transact process also
does a DISPLAY statement before it quits. This goes on throughout the day as
users request information from their browsers.

The problem is that at the end of the day, I'd like to print out the job
listing and review the activity but each display statement causes a page
eject resulting in a very long print out.

Is their something I can do in the programs to avoid the page eject? I've
tried various DISPLAY statement options in Cobol and Transact to no avail.
Maybe something can be done in the job stream? File equation?

--
Brad Feazell