Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Open Log, Close Log : Dinosaurs?

0 views
Skip to first unread message

emo...@my-dejanews.com

unread,
Apr 20, 1999, 3:00:00 AM4/20/99
to
Hi,

We're in the process of converting some old DOS procomm plus scripts into
the Windows version 4.7 scripts.

A lot of older commands like "Open Log" and "Close Log" have been
dropped.

The connection log shows very little about what transpires in a file upload
or download etc, communication errors.

Is it still possible to write to a log file from a script so that more
information shows up in the Connection Log file?

Your help would be much appreciated!

Dominique Emond
Royal Bank of Canada
Toronto, Ontario
(416) 348-5924

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

John Schultz

unread,
Apr 21, 1999, 3:00:00 AM4/21/99
to
In article <7fim18$atk$1...@nnrp1.dejanews.com>,

emo...@my-dejanews.com wrote:
> The connection log shows very little about what transpires in a file upload
> or download etc, communication errors.
>
> Is it still possible to write to a log file from a script so that more
> information shows up in the Connection Log file?

One thing you can do is enable the "Write status line messages to Connection
Log" checkbox in the System | System Options portion of setup. You must have
connection logging turned on to be able to access this checkbox. Any messages
that are displayed on the status line, such as connection made, file uploaded,
etc. will be displayed in the connection log. Also, any messages your script
displays on the status line (using the STATMSG command) will appear as well.

0 new messages