SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Fri, 26 Nov 2004 15:43:55 PST8
From:	kfh777@earthlink.net
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: IBM Works export to Shared Drive

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Steven,

I think I followed the instructions of TraceRef.txt very literally but when I "start" by ENTER in the Trace Formatter, the start time remains at zero. When I finish executing the target app and ENTER to suspend the script, the finish time is recorded in the Formatter but it reports no data recovered.

Looking back at the script I can see this text:

[J:\os2\system\trace]trace /q
TRACE version = 2.7
TRACE ON /B:512 /M:W,NQ,NODTI /S
TRACE ON /P:ALL

[J:\os2\system\trace]trace /r
Tracing resumed, press enter to suspend...
Tracing suspended, press enter to restart...

[J:\os2\system\trace]trace on kernel(55,56,98,99,212,213,255,256,424,425)
SYS1409: The TRACE utility detected an incorrect opcode(s) in KERNEL.
This trace definition file is ignored.

The TRACE utility cannot accept any of the trace definition
file(s) that were entered. Trace status for the DLL libraries was not
updated.

[J:\os2\system\trace]trace /q
TRACE version = 2.7
TRACE ON /B:512 /M:W,NQ,NODTI /S
TRACE ON /P:ALL

[J:\os2\system\trace]trace /r
Tracing resumed, press enter to suspend...

How do I fix whatever I have left out?

Ken

MyTrc.cmd script, the In , on 11/26/04
at 11:48 AM, "Steven Levine" said:

>In <200411260907.2358400.8@scoug.com>, on 11/26/04
> at 09:07 AM, kfh777@earthlink.net said:

>>Sorry to bother you with the obvious. "Tracebuf" and "trace on /p:all"
>>in config.sys and several variants don't give me a log file of activity
>>which appears meaningful.

>It's not obvious. What is obvious is that you are working from the
>original Warp4 documetation. A lot has changed in the last decade.
>:-)

>Grab:

> <http://home.earthlink.net/~steve53/os2diags/TrcTools.zip>

>and use the attached configuration file.

>Since this configuration will trace all file I/O, it will be easier
>to interpret the results if you have only IBM Works running when
>you capture the trace data.

>If you know the name of the IBM Works executable, uncomment line 7
>and supply an executable name. This will limit the trace to just
>IBM Work file I/O.

>If the zipped formatted trace file is reasonably small, you can
>attach it here. Otherwise, e-mail it to me directly. Some of
>those on this list are still dial-up.

>HTH,

>Steven

--
-----------------------------------------------------------
K.F.Hammer Associates Ken Hammer
management consultations Barnet, VT 05821
-----------------------------------------------------------

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 26 | November | 2004 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.