NAME

aedjournal − display commands in a log file

SYNOPSIS

aedjournal file

DESCRIPTION

Although there is no debugging facility as such supplied with the C subroutine interface to the display, you can use VI_Login and VI_Logout (see log(3G)) with aedjournal to help follow your application program’s actions.  Aedjournal deciphers a file produced by VI_Login and reports to standard output all orders passed to the display.  Standard output may be redirected as usual.  You may inspect this output to discover unintended results. 

Beware of the length of logged files.  It is easy to generate thousands of display orders for a seemingly simple picture; thus, try to log the smallest group of orders likely to contain the bug.  The log routines may be called several times in one application to produce several files of orders, requiring only that each call to VI_Login provide a distinct file name. 

NOTE

Aedjournal applies only to the IBM Academic Information Systems experimental display. 

SEE ALSO

aedrunner(1), init(3G), log(3G), ibmaed(4)
 

PRPQs 5799-WZQ/5799-PFF: IBM/4.3  —  30 Sep 1985