Resource3000.com

So Your HP 3000 Crashed ... Now What?

By: Stan Sieler, Allegro Consultants, Inc.

If your HP 3000 system has merely hung, then you want the System Hang web page.

Please follow this checklist, to help the support people to better understand the system crash.

What are the last few console messages? (If possible cut/paste the console memory and email it to support.)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

What were the last few things you remember the system doing? (e.g., jobs run, program run)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Take a mamory dump. If this is the first crash you've had a very long time, and if you have a large memory system, you might just decide to reboot instead.
1. Boot your system to the "ISL>" prompt:
  1. N-Class and A-Class systems:
    1. Press control-B, then TC, then press <return> Do not enter RS!
    2. Watch the console, and wait for output. If you see:
```
   To discontinue search, press any key
```
      ...then press a key (e.g., space bar) to stop the search. Note that termination may not be immediate.
    3. Enter: BOOT PRI and when asked:
```
   Interact with IPL (Y, N, or Cancel)?>
```
      answer: Y
  2. Older systems:
    1. Press control-B, then TC, then press <return> Do not enter RS!
    2. Watch the console, and wait for output. If you see:
```
   To discontinue, press any key within 10 seconds.
```
      ...then press a key (e.g., space bar) to stop the search.
    3. If asked:
```
   Boot from primary boot path (Y or N)?>
```
      answer: Y
    4. When asked:
```
   Interact with IPL (Y or N)?>
```
      answer: Y
2. Put a write-enabled tape into tape drive that is configure for Alternate Boot. On most systems, this is ldev 7. The Main Menu command – PA ALT – will display the hardware path.
3. At the ISL prompt, enter: DUMP
4. Enter a one line description of the dump, and press <return>. The dump should now start writing to the tape, and will print periods on the console while it is writing. The dump will take between 5 minutes and 2 hours, depending upon how much memory your computer has and how busy the computer was at the time if the crash.
5. When the dump is done, eject the tape, write-protect it, and make sure it is labeled with the date and word "DUMP".
Restart the system as normal (e.g.: START NORECOVERY)

The following is optional, but useful and speeds up dump analysis on your system.
If you skip it, then please send the dump tape you just created to Allegro.
Load the memory dump onto your HP 3000 from the tape:
1. Logon as MGR.TELESUP,DUMPS or MANAGER.SYS,DUMPS, or wherever you want to put the memory dump. If you've never restored a memory dump before, we suggest:
```
      :hello MANAGER.SYS
      :newgroup DUMPS
      :chgroup DUMPS
```
  Note: you might want to NEWGROUP/HOMEVS the DUMPS groups to a user volume set that has a lot of available free space. Assuming a volumeset called BIG, you could do:
```
      :hello MANAGER.SYS
      :newgroup DUMPS
      :newgroup DUMPS; onvs=BIG
      :altgroup DUMPS; homevs=BIG
      :chgroup DUMPS
```
2. Run the DAT (Dump Analysis Tool) program to load the dump onto the system:
```
      : DAT.DAT.TELESUP
```
3. Tell DAT to load the dump into a file named something like "SA1". There is a five character limit to the dump name. The first character must be a letter, and may be followed by any combination of letters and digits. Enter the getdump command. The following example creates a dump file called SA1
```
      getdump SA1
```
  DAT will request the tape (you may need to =REPLY to the tape request) and will allocate disk space to hold the dump. It then reads the tape onto disk, and displays a progress bar during loading.
4. Load the DAT macros: (SA1 is the name from the prior step)
```
      macstart "SA1", "1"
```
  Note: if DAT says it found errors while loading the dump, and asks if it should continue, enter YES.
5. Pre-process the dump, saving time for support:
```
      process_wait; ui_showjob; io_dev_list
```
  These commands search the dump and build a list of all processes, all jobs/sessions, and all IO LDEVs, and saves the list in a disk file associated with the dump, called SA1MEM.
6. Exit DAT:
```
      exit
```
STORE the dump to tape:
```
    :FILE TAPE;DEV=TAPE
    :STORE SA1@ ;*TAPE; show; progress
```
You may STORE the dump onto the original tape, if you wish. The original dump tape is no longer needed, because the STORE tape version is more useful.
Send (mail, Fed-Ex, UPS, etc.) the STORE tape to Allegro. If you stored the dump files onto a different tape you may wish to save the original dump tape for a few days just in case it's needed again.
Alternatively, you can FTP the dump to Allegro. Please note you need logon information to do this. Please contact Allegro before beginning.
```
    :LISTFILE SA1@,2
    :FILE DUMPSTD;DEV=DISC
    :STORE SA1@;*DUMPSTD;SHOW;PROGRESS
    :LISTFILE ./DUMPSTD@,2
```
The LISTFILE may show multiple DUMPSTD files (especially on big N-class systems). If so, each DUMPSTD file needs to be sent to Allegro during the FTP step. For example:
```
    >binary
    >put ./DUMPSTD
    >put ./DUMPSTD.2
    >put ./DUMPSTD.3
```
When the FTP completes, please let Allegro know that all the files have transferred. Also, send us the results of the two listfiles.

All content copyright Resource3000 | Privacy Policy | www.Resource3000.com