Bill,

When I do these types of CAPTURING to gleam the output I also set my TERM
page width to 255,0 the 255 for the widest screen size and 0 causes the
pagination logic to be turned off.  Of course I read the TERM settings
before changing them so that I can restore them before exiting.

Example:

  CMD = "LIST ..."
  !
  MAX.ROW = @CRTHIGH
  MAX.COL = @CRTWIDE
  !
  PERFORM "TERM 255,0" CAPTURING BUFF  ;* Set term characteristics
  PERFORM CMD CAPTURING BUFF           ;* Execute command and capture output
  !
  PERFORM "TERM ":MAX.COL:",":MAX.ROW CAPTURING BUFF   ;* Reset term

Thanks,
David A. Green
DAG Consulting


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett
Sent: Thursday, January 19, 2006 5:15 PM
To: [email protected]
Subject: RE: [U2] [UD] list output when captured

David:

Thanks...because I need the heading.  :-)

A SCROLL program takes the results of a query and simply pages it so the
user can move around the report (up, down, all around, and search).  We need
the heading passed into the program (assuming one is).

Bill
 

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> David A. Green
> Sent: Thursday, January 19, 2006 6:01 AM
> To: [email protected]
> Subject: RE: [U2] [UD] list output when captured
> 
> Why not just suppress the heading? HDR.SUP
> 
> David A. Green
> DAG Consulting
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett
> Sent: Wednesday, January 18, 2006 5:20 PM
> To: [email protected]
> Subject: [U2] [UD] list output when captured
> 
> I've got a simple scroll routine that parses the output from 
> a LIST or SORT command's "CAPTURING" variable of an EXECUTE 
> statement.  The routine tests for the 2nd empty line to 
> determine when the column heading ends and the data begins, 
> as all output with a heading puts a blank line between the 
> column heading and the data.
> 
> So, typical captured output would look like:
> 
> SCRATCH(1)=Dictionary of File: PERIPHERALS                    
>   16:05:08 Jan
> 18
> 2006^Dict Name...... Typ # Col-Heading.... Field-Def... 
> Conversion.. Formt Assoc
> ...^^@               Phr                   LPTRNO DEV_N^
> .
> .
> 
> The total width of the heading is 78 characters, while the 
> TERM width is 79.
> If I were to change the TERM width to 78 then rerun the above 
> listing the extra line between the column heading and the 1st 
> row of data disappears (the first of two attribute marks 
> changes to a space).
> 
> SCRATCH(1)=Dictionary of File: PERIPHERALS                    
>   16:05:08 Jan
> 18
> 2006^Dict Name...... Typ # Col-Heading.... Field-Def... 
> Conversion.. Formt Assoc
> ... ^@               Phr                   LPTRNO DEV_N^
> .
> .
> 
> Is there a reason why this occurs (I've not seen this before) 
> or will I just have to be careful in the future?
> 
> As always, thanks.
> 
> Bill Haskett
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to