home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
DBMTRC.FAX
< prev
next >
Wrap
Text File
|
1994-11-29
|
4KB
|
116 lines
Database Manager trace instuctions with OS 7/15/92
********PLEASE NOTE:****************************************************
These instructions are only for OS/2 Extended Edition. If you are
tracing Database Manager under Extended Services, use the new SQLTRC
function.
************************************************************************
OS/2 DATABASE MANAGER TRACE INSTRUCTIONS
________________________________________
If the problem you are tracing is reproducible at will, fol-
low steps 2 - 10. If it is not, you will need to follow in-
struction 1, skip steps 2 - 6 and continue through
instruction 10.
1. Edit the CONFIG.SYS file and add the following state-
ments:
'TRACEBUF=63'
'TRACE=ON 176,177,178,179,180,182,183,184'
Re-ipl the system to activate the changes.
NOTE: Running all the required trace events may impact
system performance. OS/2 Database Development has sug-
gested that users always run with system event 183 (er-
ror path trace) activated so that important information
will be readily available in case of an abend or system
error (trace records will only be written if an error
occurs so performance will not be impacted).
2. Edit the CONFIG.SYS file and add the following state-
ments if they do not exist.
'TRACEBUF=63'
'TRACE=OFF'
Re-ipl the system to activate the changes.
3. Begin the application and get as far into the process
before the problem occurs.
The objective is to get as close to the problem before
it occurs, turn 'TRACE ON' and then immediately issue
the 'TRACE OFF' command after the problem has occurred.
4. Start a new OS/2 session and type the following:
'TRACE ON 176, 177, 178, 179, 180, 182, 183, 184' Press 'Enter'.
5. The next command should only be used if requested by IBM
Support. 'SQLTRSET x x x' where x is a letter requested
by IBM Support.
6. Switch back to the session running the application and
continue until the problem occurs.
7. After the application has failed, copy or print the
'ABEND' screen (if any) and take special note of the
'CS' & 'IP' values.
8. Switch back to the session where the 'TRACE ON' command
was issued (or go to a new OS/2 command prompt if you
started the trace from CONFIG.SYS) and type the follow-
ing:
'TRACE OFF'
9. At the OS/2 command line type the following:
'TRACEFMT > FN' (FN is any user defined Filename)
This will copy the trace information from the trace
buffer to an OS/2 file.
10. You need only perform this step if an abend (or TRAP)
occurred on your system. Type the following at an OS/2
command prompt:
'SQLABEND FN CSV:IPV' (FN = Filename, any user defined name)
(CSV = CS value)
(IPV = IP value)
If the problem has occurred in database services then
the user will receive a message indicating the component
(i.e, SQLx where x is the component ID. The user should
record this message.
WHERE TO SEND THE FORMATTED TRACE
_________________________________
You can send the trace to IBM Level 2 Support in one of two
ways:
1. Have your local IBM Representative (SE or OSS) upload
the file in BINARY FORMAT (this is very important) and
send it electronically to DEFECT at AUSVM8 (userid and
nodeid on VM system). Make sure that he/she includes
the problem number in the filename, e.g. 1X123 TRACE1,
1X123 TRACE2, etc.
2. Copy the trace to diskette and mail it to the following
address:
IBM Corp.
Attn: <Level 2 Support person you are working with>
11400 Burnet Rd.
Zip 2900 Bldg. 042
Austin, TX 78758
12/31/99