Any one knows how to turn on the trace in Micro Focus Cobol?
I googled it. I need to put READY TRACE statement, but in addition, it also said something about Compiler directive which I do not know.
My compiling statement is like
Hello guys,
I'm searching for a good COBOL compiler which runs on linux. In fact I have found one but I'm really lost with its installation!! I don't know how to install it and how it works. In fact I'm not so good in linux and I always have problems with installation, but this time it's... (1 Reply)
Hi,
I am working on a Mainframe to UNIX replatforming project.
we are facing problems with COBOL COMP-3 fields. We are using the Mainframe emulator software to download the data which has COMP-3 fields and using it as input to the same COBOL programs which were copied from Mainframe and did the... (1 Reply)
Does anyone use the following Cobol compiler:
RM/COBOL-85 Compiler - Version 5.15.00 for SCO Unix 386.
I am looking for a file that might be part of the distribution named "osmain.o"
Thanks. (0 Replies)
I have some compile programme .crn now I want to run .crn programme on express cobol which allow only *.gnt programme any solution to run *.crn programme (0 Replies)
Is there a way you can return a value from a script that is called from a rm cobol program...
01 WS-COMD-LINE-PGM X(39) value sh ./getUserId.sh 12345"
01 WS-RETURN-SYS-CODE PIC 9(8).
CALL "SYSTEM" USING WS-COMD-LINE-PGM
GIVING WS-RETURN-SYS-CODE.
... (1 Reply)
Dear All,
while installing mfcobol in sco open unix 5 in piv m/cs, when run
#sh ./install
this error massage is comming
load error file lmfnewdb
error code 198 pc=0 call=-1 seg=0
198 load failor
chmod warrning can not acess /opt/lib/mflmf/mflmfdb no such file or directory (error-2)... (0 Replies)
When running our UNIX job scripts we randomly get the following 198 error below. When we restart the job it works fine. I haven't been able to recreate the problem in test, so I'm wondering if it has something to do with Cron or possibly a memory error or memory leak. I don't see anything... (5 Replies)
Hello,
I have got a specific requirement of running a COBOL code on EL5. Not sure if GCC includes the compiler for COBOL.
Currently what I can think of installing openCOBOL in EL5 server and hand it over to developers.
From what I think need to do is, compile COBOL code using openCOBOL ... (5 Replies)
Hi all,
I am trying to virtualize a running SCO 5.0.6 system with microfocus cobol installed.
I have already managed (thanks to the people in this forum) to install the operating system.
I dont have the cobol installation media anymore. I have copied (using cpio) all directories from... (3 Replies)
Discussion started by: sopela123
3 Replies
LEARN ABOUT MOJAVE
_nc_tracebits
curs_trace(3X)curs_trace(3X)NAME
_tracef, _tracedump, _traceattr, _traceattr2, _nc_tracebits, _tracechar, _tracechtype, _tracechtype2, _tracemouse, trace - curses debugging
routines
SYNOPSIS
#include <curses.h>
void _tracef(const char *format, ...);
void _tracedump(const char *label, WINDOW *win);
char *_traceattr(attr_t attr);
char *_traceattr2(int buffer, chtype ch);
char *_nc_tracebits(void);
char *_tracechar(int);
char *_tracechtype(chtype ch);
char *_tracechtype2(int buffer, chtype ch);
char *_tracemouse(const MEVENT *event);
void trace(const unsigned int param);
DESCRIPTION
The trace routines are used for debugging the ncurses libraries, as well as applications which use the ncurses libraries. These functions
are normally available only with the debugging library libncurses_g.a, but may be compiled into any model (shared, static, profile) by
defining the symbol TRACE.
The principal parts of this interface are the trace routine which selectively enables different tracing features, and the _tracef routine
which writes formatted data to the trace file.
Calling trace with a nonzero parameter opens the file trace in the current directory for output. The parameter is formed by OR'ing values
from the list of TRACE_xxx definitions in <curses.h>. These include:
TRACE_DISABLE
turn off tracing.
TRACE_TIMES
trace user and system times of updates.
TRACE_TPUTS
trace tputs calls.
TRACE_UPDATE
trace update actions, old & new screens.
TRACE_MOVE
trace cursor movement and scrolling.
TRACE_CHARPUT
trace all character outputs.
TRACE_ORDINARY
trace all update actions. The old and new screen contents are written to the trace file for each refresh.
TRACE_CALLS
trace all curses calls. The parameters for each call are traced, as well as return values.
TRACE_VIRTPUT
trace virtual character puts, i.e., calls to addch.
TRACE_IEVENT
trace low-level input processing, including timeouts.
TRACE_BITS
trace state of TTY control bits.
TRACE_ICALLS
trace internal/nested calls.
TRACE_CCALLS
trace per-character calls.
TRACE_DATABASE
trace read/write of terminfo/termcap data.
TRACE_ATTRS
trace changes to video attributes and colors.
TRACE_MAXIMUM
maximum trace level, enables all of the separate trace features.
Some tracing features are enabled whenever the trace parameter is nonzero. Some features overlap. The specific names are used as a guide-
line.
RETURN VALUE
Routines which return a value are designed to be used as parameters to the _tracef routine.
PORTABILITY
These functions are not part of the XSI interface. Some other curses implementations are known to have similar, undocumented features, but
they are not compatible with ncurses.
SEE ALSO curses(3X).
curs_trace(3X)