HP 3000 Manuals HP 3000 Manuals
How to Get Started with the DAT Macros Utilizing the DAT macro package is the simplest way to analyze a dump. Additional documentation is required to make use of the macros. Contact your Response Center for further information. To use this package, log on to the TELESUP account in the USER group. The TELESUP account is where the DAT program, the macro files, and the symbolic data type files are located. The first step is to start the DAT program and invoke the DAT Macros startup macro.
NOTE Please note that these macros are dynamic. They will change and be improved. The output from these examples may differ from what future macros produce.
:DAT DAT XL A.00.00 Copyright Hewlett-Packard Co. 1987. All rights reserved. $1 ($0) nmdat > use macstart /* Invoke the startup macro Welcome to the DAT Macro facility. Enter the dump file name to process: examp /* Open this dump Last PIN: 2b On ICS stack Dump operating system vuf is: 8.60.55 Please choose from the following levels of macros available for use: 1) All macros (default, includes high level Macros). 2) Low level macros. 3) Expert level macros. 4) General level macros only. 5) Do not load any macros. Enter your selection: 1 /* Load ALL of the macros Reading in macro files (from os860.telesup)... General macros read in. File System expert level macros read in. Input/Output expert level macros read in. Process Management expert level macros read in. User Interface expert level macros read in. Transaction Management expert level macros read in. File System low level macros read in. Input/Output low level macros read in. Process Management low level macros read in. Resource Management low level macros read in. User Interface low level macros read in. Transaction Management low level macros read in. Configuration high level macros read in. Current State high level macros read in. Recent Event high level macros read in. Macro files loaded successfully. $21e ($2b) nmdat > At this point, the dump has been opened and all of the DAT macros have been loaded. The following examples show some of the more interesting high-level macros: $21e ($2b) nmdat > machine state MPE/XL VERSION: 8.60.55 CPU: PROCESS_RUNNING SYSTEM CONSOLE AT LDEV #20 CURRENT REGISTERS: R0 =00000000 00000e00 000a2150 c3ff668c R4 =c0000000 0088e640 0088e688 00000000 R8 =00000000 00000000 00000000 00000000 R12=00000000 00000000 00000000 00000000 R16=00000000 00000000 00000000 c3ff668c R20=c0000000 00000000 c3ff6680 402123c0 R24=00000000 0000000a c3ff668c c0200008 R28=00000001 00000000 40212468 000a2150 IPSW=0006ff0b=jthlnxbCVmrQpDI PRIV=0 SAR=0002 PCQF=a.a4838 a.a483c SR0=0000000a 0000000a 0000000a 0000000a SR4=0000000a 000005e4 0000000b 0000000a TR0=005eb200 0061b200 0063f000 000a4000 TR4=0004000e 0007c810 0063f05c 0088e688 PID1=03d6=01eb(W) PID2=0342=01a1(W) PID3=0314=018a(W) PID4=0000=0000(W) RCTR=00000000 ISR=0000000a IOR=000a2150 IIR=e840c002 IVA=00081000 ITMR=b9dc4649 EIEM=ffffffff EIRR=80000000 CCR=0080 $21f ($2b) nmdat > The above example shows the basic state of the machine at the time it was dumped. $21f ($2b) nmdat > process dispatcher PROCESSOR STATE --------------- PROCESS_ACTIVE === SCHEDULING INFORMATION === READY ACTIVE ACTIVE PENDING PENDING PENDING TIMESLICE COUNT PIN PRI PIN PRI COUNT INTERVAL ----- ------ ------ ------- ------- ------- --------- $0 $2b $1bff $7ffd $0 $0 $249f00 ES BACKRD DS BACKRD CS CS CS QUANTUM QUANTUM QUANTUM QUANTUM MAX QUANTUM MIN --------- --------- ------- ----------- ---------- $0 $f42400 $3d0900 $f42400 $3d0900 ES PRIORITY DS PRIORITY CS PRIORITY BASE LIM BASE LIM BASE LIM ---- --- ---- --- ---- --- $3e8 $1 $1bff $1bff $1bff $1bff === MISCELLANEOUS INFORMATION === DISP DISABLE DISP DISABLE ICS DISP ICS NESTED INT DISABLE COUNT PIN DSABL CNT INT CNT COUNT ------------ ------------ --------- ---------- ----------- $0 $37 $0 $1 $0 DISPATCH QUEUE INFO: PIN PRIORITY --- -------- HEAD ===> $20 $1bff $2b $1bff $37 $1bff DISPATCHER WORK QUEUE EMPTY $220 ($2b) nmdat > The above example shows the dispatcher's state and queues. $221 ($2b) nmdat > config device ldev LDEV# IO-PATH TYPE ID OUTDEV MODE SIZE CLASS ----- ------- ---- -- ------ ---- ---- ----- $1 8.0.0 IO_DISC HP7935 $320 $0 DISC SPOOL $2 8.0.1 IO_DISC HP7935 $0 $ffffff80 DISC $3 8.0.2 IO_DISC HP7935 $320 $0 DISC $4 8.0.3 IO_DISC HP7935 $0 $ffffff80 DISC Control-Y encountered $223 ($2b) nmdat > The above example shows all of the configured LDEVs on the system. This macro was terminated with a Control-Y before it completed. $223 ($2b) nmdat > job current JOB TIME USER INPUT DEVICE OUTPUT DEVICE CI PROCESS ----- ------- ---------------- ------------ ------------- ---------- #S95 15:16:49 LOGGER .SYS $15 $15 $1f #S4 13:16:34 LOGGER .SYS $16 $16 $32 #S2 13:14:04 MANAGER .SYS $14 $14 $35 #S381 22:55:30 MGR .VSTEST $1f $1f $18 #S659 09:17:36 MGR .VSTEST $17 $17 $1b #S371 22:46:51 MGR .VSTEST $20 $20 $29 Control-Y encountered $224 ($2b) nmdat > The above example shows all of the jobs and sessions on the system. This macro was terminated with a Control-Y before it completed. The above examples give a hint of the power and convenience of utilizing the DAT macros package for dump analysis. Many more macros exist that will format an operating system table, print process information, display resource allocation, help find deadlocks, and so forth.