THE PS/2 DUMP PROCESS

A utility exists in OS/2 to dump all of physical memory to diskette.
The dump is helpful in "some" situations to identify a failing
component in an OS/2 system.  Development has asked that the TRACE
utility be running for ALL dumps.  Note that the TRACE utility is
a separate function from the DUMP utility.

There are two types of dumps.

  A) AUTOMATIC DUMP (Only useful for Ring 3 Traps)
  B) MANUAL DUMP (To be used for hangs, and traps that are not Ring 3)

Different situations determine which type of dump is needed.  IBM
OS/2 Support will help to determine which process is correct for
your situation.


1.  STARTING THE TRACE **

For OS/2 prior to OS/2 2.1, add the following lines in config.sys:

TRACE=ON
TRACEBUF=63
TRACE=OFF 4,24,47,50,97,98

and then reboot the machine.

The above starts TRACE function and turns off major codes 4, 24, 47,
50, 97, and 98.  The default for TRACE=ON is to trace all system events.
These major codes are for some housekeeping functions that are not
normally used by development.
.............
For OS/2 2.1, add the following lines to the config.sys (exactly):

  TRACEBUF=63
  TRACE=ON

then you must reboot the machine.

For OS/2 2.1, enter the following commands from a command prompt after
the reboot noted just above:

  TRACE ON KERNEL
  TRACE ON DOSCALL1


** THE DUMP PROCESS **

2.  THE DUMP DISKETTE (Preparing for the memory dump to diskettes)

The first thing you will need is a "Dump Diskette".  This must be
created on a working machine BEFORE a failure.  The diskette is
then saved until needed.  The diskette sizes must be the same (i.e.,
all 1.44 diskettes or all 2.88 diskettes).

To create a DUMP Diskette enter the following from a command prompt:

    CREATEDD A:

This creates a DUMP diskette.  When the machine requests the dump
diskette, use this one as the first diskette.  Additional formatted
diskettes will be needed to hold the rest of the dump.  The number
of diskettes needed depends on the amount of memory in your system.

3.  TWO WAYS OF RECORDING THE DUMP (Automatic or Manual)

A.  AUTOMATIC DUMP PROCESS (Only to be used for Ring 3 Traps)

    In CONFIG.SYS enter the following:

      TRAPDUMP=ON

This will cause an automatic DUMP if the failing CS:EIP is in Ring 3
code (the CS value will end in either 3, 7, B or F).  It will not
DUMP on Ring 0 code traps.  (Applications run at Ring 3 while the OS/2
Kernel runs at Ring 0.)

OR***

B.  MANUAL DUMP PROCESS

It is also possible to start a MANUAL DUMP of the system.  If
the trap information is displayed on the screen, record ALL
of the information.  Press and hold "Ctrl+Alt" and then press
"Num Lock" twice.  This start the dump process.  This assumes
the keyboard is not locked.

4.  TAKING THE DUMP

When the dump is started, either automatic or manual, the screen
goes blank and the user is instructed to insert the DUMP diskette.
This is the diskette created with the CREATDD command.  The user
is prompted for additional diskettes as needed and then instructed
to insert the DUMP diskette a second time.  When this is finished,
the system can be re-booted to return to normal operation.

Note that no register information is displayed when an automatic
dump is taken.  The register information is contained in the
dump information.


5.  MAILING THE DUMP TO IBM

DO NOT send dump diskettes unless instructed by Level 2 Support.
Diskettes MUST be clearly labeled with the PMR# or APAR# and your
name.  Please ensure diskettes are numbered as well.

DUMP diskettes should be sent to:

IBM Corp.
1000 NW 51st Street
Boca Raton, FL 33432
ATTN: Sharon Cofar, Bldg 001-3  (Or whoever your analyst may be)
Internal Zip 1024

OR

Disk images (for ibm customers) may be created using OS2IMAGE.EXE
(pctools) or other disk image utility and send them to the appropriate
vm id.  The dumpformatter requires diskimages (as opposed to just
the contents of each diskette).  Please notify the analyst working
your pmr that you have forwarded the diskimages so that we may go
get them to analyze.