SOFTWARE SERVICE KIT DOCUMENTATION     HP 1000     24999-90001     REVISION CODE 1938     SEPTEMBER 17,1979     MATERIAL LIST     NAME REL BINARY SOURCE REVISION     PART # PART # CODE        JSAVE 24999-16048 24999-18065 1932 *    JRSTR 24999-16049 24999-18066 1932 *    SDLS4 24999-16050 24999-18067 1938 *    RXREF 24999-16051 24999-18068 1902 *    CMM3 24999-16052 24999-18069 1752    FGETR 24999-16053 24999-18070 1902 *    CLASS 24999-16055 24999-18083 1902 *    JVRFY 24999-16163 24999-18163 1902 *    SAMSZ 24999-16178 24999-18178 1814    CDA4 24999-16197 24999-18197 1938 *    SNPSH 24999-16198 24999-18198 1839    CDMP 24999-16199 24999-18199 1839    PATCH 24999-16200 24999-18200 1839    CMMM 24999-16201 24999-18201 1839    CMM4 24999-16202 24999-18202 1938 *    DSINF 24999-16215 24999-18215 1902 *    SLCIN 24999-16214 24999-18214 1902 *    NDTDU 24999-16213 24999-18213 1902 *    TDMP 24999-16218 24999-18218 1902 *    TRC65 24999-16225 24999-18225 1902 *    PSMON 24999-16224 24999-18224 1902 *    DVT65 24999-18226 1902 *    SAM 24999-16227 24999-18227 1902 *    MAPIO 24999-16222 24999-18222 1902 *    SCB 24999-16247 24999-18247 1938 *    DLB 24999-16244 24999-18244 1935 *    DLA 24999-16245 24999-18245 1932 *    VERIF 24999-16248 24999-18248 1938 *    DXREF 24999-16246 24999-18246 1938 *    "UTIL 24999-18071 1938 *    NOTE: asterisks (*) denote new or updated tools - FOR HP INTERNAL USE ONLY - HP 1000 SOFTWARE SERVICE KIT SUMMARY OF PARTS    +------------------------------------------------------+------------------+   | | |   | SUMMARY OF PARTS | CHAPTER 1 |   | | |    +------------------------------------------------------+------------------+    NAME PAGE DESCRIPTION        SYSTEM DEBUGGING AIDS:        CMM3 Permits modification of memory or disc, gives listing of     system tables, etc for RTE-II and RTE-III    CMM4 Permits modification of memory or disc, gives listing of     system tables, etc for RTE-IV    CMMM Permits modification of memory or floppy, gives listing of     system tables, etc for RTE-M    PATCH Patches system from a file containing binary absolute code        DATA COMMUNICATIONS DEBUGGING AIDS:        DSINF Gives listings of DS/1000 tables, etc.    NDTDU Dumps DS/1000 Network Description Table    TRC65 Trace program for DS/1000 communication line    DVT65 Modified DVA65 needed for TRC65    PSMON Passive monitor program for DS/1000 communication line    SLCIN Long term statistic and event trace for DS/1000-3000        CRASH DUMP ANALYSIS:        CDA4 Gives listings of system tables, etc from the memory under     the system map of a crashed system. Output and use is     similar to    CMM4    CDMP Dumps the memory under the system map to cassette for use     by CDA4    TDMP Dumps the memory under the system map to mag tape for use     by CDA4    SNPSH Saves system snapshot on cassette for use be CDA4 - FOR HP INTERNAL USE ONLY - 1 HP 1000 SOFTWARE SERVICE KIT SUMMARY OF PARTS        FILE RELATED UTILITIES:        VERIF Provides a means to verify a FMGR disc file    RXREF Generates cross refrence map of a program    DXREF Allows selective searching of modules, entry points,     and external refrences. (See RXREF)    DL Gives directory information about purged and open files     and gives enhanced filtering options to the 'DL' command.    SDLS4 Read CUPERTINO distribution tape into FMP files    JSAVE Save disc cartridge on mag tape    JRSTR Restores disc cartridge from JSAVE mag tape    JVRFY Verify disc cartridge and JSAVE tape    FGETR Access a file and directory on JSAVE mag tape        PERFORMANCE AND TABLE ANALYSIS UTILITIES:        CLASS Displays status of class table, list contents or     clear pending buffers    SCB Dumps and breaks out a Session Control Block (SCB)    SAM Identifies each buffer in System Available Memory,     who asked for it and what its contents are    SAMSZ Determines the amount of SAM dynamically    MAPIO Displays LU/EQT/SC relationships (LUPRN)            APPENDIX A CUPERTINO DISTRIBUTION TAPE FORMAT    APPENDIX B JSAVE/JRSTR TAPE FORMAT - FOR HP INTERNAL USE ONLY - 2 DEBUGGING AIDS CMM3, CMM4 and CMMM    +------------------------------------------------------+------------------+   | | |   | DEBUGGING AIDS | CHAPTER 2 |   | | |    +------------------------------------------------------+------------------+    2.1 CMM3, CMM4 AND CMMM    PROCEDURE NAMES:    CMM3, CMM4 AND CMMM    PART NUMBER:        24999-16052, 24999-16202 AND 24999-16201    DESCRIPTION:     CMM3, CMM4 and CMMM can be used as a debugging aid for program     development or as tools for trouble shooting.      They allow the user to examine or modify memory cells, to list, system     tables and peripheral information, to trace program linkage lists, and     to modify the disc.  CMM3 should be used for RTE II and RTE III, CMM4     for RTE-IV and CMMM for RTE M    USAGE:     CMM3 can be called by a command RU,CMM3 CMM4 can be called by a command     RU,CMM4 CMMM can be called by a command RU,CMMM CMM4 cannot be run from     multipoint terminals.      When the CMM program is ready, a prompting character "-" is displayed     and it waits for the following commands to be entered.     DESCRIPTION OF CMM COMMANDS:     Numbers used for parameters may be entered in decimal(nn) or octal(nnb)     form.      The standard output is produced in one word per line in decimal, octal,     and ASCII along with the location.  In addition, CMM4 prints symbolic     output (inverse asemble).      Any commands which produces more than one word of output may be     appended with PK (e.g.  INPK,6,10).  It causes the output to be     produced in 8 words of octal and ASCII per line instead of one word per     line.  - FOR HP INTERNAL USE ONLY - 3 DEBUGGING AIDS CMM3, CMM4 and CMMM    COMMAND DESCRIPTION        ?? Displays all available CMM commands with     description.        ??,xx Displays syntax format for the command xx.     ??,LI        /E, EN, or EX Exits from CMM        ID,xxxx Displays ID segments of the program xxxx.     If the program is a segment, 9 words are     displayed; otherwise, 28 words are displayed.                ID,n Displays all ID segments. n=any number.     ID,FMGR     ID,1        EQ,n1 Displays the contents of equipment table    EQ,n1,n2 entries n1 through n2.     EQ,4     EQ,1,9        DR,n1 Displays the contents of device reference    DR,n1,n2 table entries n1 through n2. Each entry     is displayed in two parts.     DR,1     DR,1,5        IN,n1 Displays the contents of interrupt table    IN,n1,n2 entries n1 through n2.     IN,6     IN,6,13        LM,n1 List n2 memory locations starting at n1    LM,n1,n2 address.     LM,2000B     LM,2000B,300        TA Displays complete track assignment table    TA,lu# if the logical unit is not specified;    TA,lu  ,trk  ,  of trks otherwise, the track assignment for the     system disc(lu=2) or auxillary disc(lu=3)     as many tracks specified from the specified     track.     TA,2        PM,n1,n2 Patch memory address n1 with the value n2.     The contents of n1 followed by the message - FOR HP INTERNAL USE ONLY - 4 DEBUGGING AIDS CMM3, CMM4 and CMMM     "YES" or "NO" are displayed. Type "YES" to     patch it; otherwise, type "NO" to quit.     PN,2000B,100B        F/,xx,n1,n2 Find all occurrence of value xx in next n2     locations starting at address n1.     F/,77B,2000B,200        LI,xxxx,# of words List the address of the entry point name     xxxx.     LI,CMM3,5        DI,xxxx List the disc address of the 4 word     dictionary that describes the entry point     xxxx.     DI,CMM3        LE List all entry points in the system        LL,lu # Change the list device to lu  . It is     initially set to the terminal where the     RU,CMM3 command was entered.     LL,6        TR,n1 Traces a threaded list starting at the    TR,n1,n2 address n1 until the address contains the     value n2. If n2 is omitted, the value of     0 or negative number terminates the trace.     TR,1711B        XT,n1 It is the same as TR except that it traces    XT,n1,n2 the system map.        DP,n Displays the value n in octal, decimal,     and ASCII format.     DP,3479        DL,lu,trk,sctr,# of sctrs Disc listing of any number of sectors     starting at the specified sector.        DM Disc modification in interactive mode     as follows:     MODIFY OP SYSTEM ?     YES OR NO ?     LU,TRK,SECTR,WORD,VALUE     type lu #, track #, sector #, word # to     specify the address and the value to be     entered.         The contents of the specified address is     displayed. If it is the cell to be changed - FOR HP INTERNAL USE ONLY - 5 DEBUGGING AIDS CMM3, CMM4 and CMMM     type "YES"; otherwise, type "NO".         /D terminates DM mode.        DS,lu #,trk #,value Scans the disc and displays all occurrences     of the value found on the track. Use this     information with DM to unpurge files.        XL,n1 List the contents of n2 locations in the    XL,n1,n2 system map starting with the address n1.     XL,46000B     XL,46000B,100    XF,n1,n2,n3 Scans for the value n1 in next n3 locations     in the system map strating at n2 address.     XF,111B,46000B,1000        XP,n1,n2 Patch the system map at the address n1     with the value n2.        LP,xxxx,n List the absolute program xxxx on disc.     The sector number corresponding to the     relocatable address n is listed.        PG,pg #,# of words,offset List any number of words starting at the     first word of the page plus offset        PP,pg #,offset,value Patch a word in physical memory at offset     in page. physical memory starts at     page 0.        NS,# of sectors Set number of sectors per track. If two    NS,# of sectors,# of sectors values are entered, the second value     will be used as the number of sectors     per track in the new track of the     MS command.        MS,lu1,track1,sector1,lu2,track2,sector2,# of sectors     Move disc sectors from one track and     sector to another. Use the NS command     if the source and destination LU's     have a different number of tracks     per sectors.        FP Footprint command. Displays the last     190 past disc modifications.    The following commands are not available in CMM3:         PP NS MS FP - FOR HP INTERNAL USE ONLY - 6 DEBUGGING AIDS CMM3, CMM4 and CMMM    The following commands are not available in CMMM:         TA LI DI LE LP PG PP NS MS FP        A more complete description of CMM commands, and a "How To" primer are    included as appendix C. - FOR HP INTERNAL USE ONLY - 7 DEBUGGING AIDS PATCH    2.2 PATCH    PROCEDURE NAME:     PATCH    PART NUMBER:        24999-16100    DESCRIPTION:     Patch is a program which can be used to put patches into the operating     system after it has been booted up.  Patch is normally run from the     WELCOM file.     USAGE:     Patch can be scheduled with:     RU,PATCH,terminal lu,file name     where terminal lu is used to log error messages and file name is a     binary absolute file (type 7) containing the patches to be made.     EXAMPLE:     Change program LOADR name to XXADR upon bootup.      1.  Using CMM3, find word 13 of the ID segment of LOADR (23435B).      2.  Assemble the following program into file PATCH1::-2     ASMB,A,L     ORG 23435B     ASC 1,XX     END     3.  Put the following statement into the WELCOM file:     :RU,PATCH,1,PATCH1::-2    ERRORS:    2 - First parameter not integer    3 - Second parameter not a namr    4 - File is not Binary Absolute (type 7)    6 - Checksum does not compute    7 - Record too large - FOR HP INTERNAL USE ONLY - 8 DATA COMMUNICATIONS DEBUGGING UTILITIES DSINF    +------------------------------------------------------+------------------+   | | |   | DATA COMMUNICATIONS DEBUGGING UTILITIES | CHAPTER 3 |   | | |    +------------------------------------------------------+------------------+    3.1 DSINF    PROCEDURE NAME:     DSINF    PART NUMBER:        24999-16215    DESCRIPTION:     DSINF is a program to printout DS/1000 internal information.  It allows     the user to examine EQT's, information stored in SAM and information     The source code is written with the following assembly options:     "N" 1000-1000 and 1000-3000 version     "Z" 1000-3000 only (no DEXEC or NRV)     The relocatable code for the "N" option is %DSINF, and for the "Z"     option is %DSIN2.  Only %DSINF is included on the software service kit.     %DSIN2 should be used when no other 1000's are connected to a node or     when program size is a critical factor (%DSIN2 is about a page shorter     than %DSINF).  Both cannot be generated into the same system because     they have the same program name.      DSINF is a type 19 program: background disc resident with access to     Subsystem Global Area.  The default priority is 65.  It does not use     the end of its partition, so there is no advantage to assinging extra     pages.  The 1000-1000-3000 version requires six pages while the     1000-3000 version requires five.      DSINF will not work in a non-DMS system (RTE-M II)    USAGE:     Run DSINF from RTE with:     RU,DSINF,,,,,     The run-time parameters have these meanings: - FOR HP INTERNAL USE ONLY - 9 DATA COMMUNICATIONS DEBUGGING UTILITIES DSINF        The logical unit number of the input device.  The default is     the number of the scheduling terminal passed by MTM or 1.      If the input device is interactive (uses DVR00, DVR07 or     DVR05 and subchannel 0), a prompt is printed on the device     before each read.        The logical unit number of the device where information is     printed.  The default is the input LU (if interactive) or 6.       A control word which specifies DSINF will be run     noninteractively.  The functions which take place are     determined by the bits set:     DECIMAL     VALUE PRINT THIS INFORMATION     ------- ------------------------------     1 available memory suspend list     2 I/O classes     4 DS/1000 values     8 dump of SAM block     16 DS/1000 lists     32 Nodal Routing Vector     64 DS/1000 EQT entries         For example, to print the I/O class and DS/1000 values     on your terminal, type RU,DSINF,,,6. To get all the     functions, type RU,DSINF,,,177B.     When DSINF runs non-interactively, it prints the time and node number     as a heading.         The node number where I/O is to occur.  Default is local     node (-1).         Set to a non-zero value when the node number is 0 (to     distinguish it from the default).      If DSINF is scheduled with wait from REMAT ( RW,DSINF), the     and parameters are not needed.  DSINF will run     in the remote node but will perform its I/O operations at     the local node.      The 1000-3000 version (%DSIN2) will not run remotely.      DSINF reuses its scheduling parameters if new ones are not provided     This allows DSINF to run non-interactively in the time list.  For     example, suppose you want the I/O class and DS/1000 lists information     printed on LU 6 every hour.  You would enter the RTE commands     *IT,DSINF,4,1 - FOR HP INTERNAL USE ONLY - 10 DATA COMMUNICATIONS DEBUGGING UTILITIES DSINF     *ON,DSINF,NOW,,6,18     Because of this feature, you should provide your terminal's LU if you     run DSINF from a non-MTM terminal.  Otherwise it will use its previous     parameters.      DSINF will not execute unless the node has been initialized by LSTEN.      If the node hasn't been initialized, DSINF prints "RUN LSTEN FIRST!"    COMMANDS     In interactive mode, DSINF recognizes the following commands:     AV available memory suspend list     CL I/O classes     VA DS/1000 values     DU dump of SAM block     LI DS/1000 lists     NR Nodal Routing Vector     EQ DS/1000 EQT entries     EQ,N print information on EQT N     /E OR EX terminate DSINF     All other characters cause the functions to be listed on the output     device.      NOTE: If the relocatable %DSIN2 is used, the NR command is not     recognized and the EQ command prints DVG67 information only.     SAMPLE OUTPUT FOR EACH COMMAND     1.  The available memory suspend list     AVAILABLE MEMORY SUSPEND LIST         PT SZ PRGRM T PRIOR AMT.MEM RN FATHER     ----------------------------------------------------------------------     5 5 SON 3 99 3608 F GF     5 5 DAVEM 3 99B 3708 RN DAVEE GYLRD LENDR WILAM JASON     FMGR     ----------------------------------------------------------------------     In this example, two programs are in the available memory suspend list.     "SON" is in partition 5, requires 5 PAGES, is a type 3 program, has     priority 99, has requested 3608 words of system available memory, and     was scheduled by "F".  "F" was scheduled by "GF".  "DAVEM" has the same     information with the following exceptions: the "B" following the     priority indicates it is being run in batch mode, the amount of memory     is 3708 words, the "RN" indicates a resource number has been locked,     and his "ancester" programs are as follows: FMGR scheduled JASON, who     scheduled WILAM, who scheduled LENDR, who scheduled GYLRD, who - FOR HP INTERNAL USE ONLY - 11 DATA COMMUNICATIONS DEBUGGING UTILITIES DSINF     scheduled     DAVEE, who scheduled DAVEM.      if no programs are waiting for memory, DSINF prints     AVAILABLE MEMORY SUSPEND LIST IS EMPTY     2. I/O CLASSES     DSINF prints the following:     I/O CLASS INFORMATION     40 CLASSES IN SYSTEM         CLASSES IN USE:     CLASS STATE GET POSSIBLE OWNER     27 GT PROGL ASMB LSTEN     28 GT OPERM ASMB LSTEN     29 GT RFAM ASMB LSTEN     30 GT EXECM ASMB LSTEN     31 GT PTOPM ASMB LSTEN     32 GT EXECW ASMB LSTEN     33 GT CNSLM ASMB LSTEN     34 GT DLIST ASMB LSTEN     35 GT QCLM ASMB LSTEN     36 GT RTRY ASMB LSTEN     37 GT GRPM ASMB LSTEN     38 GT RPCNV ASMB LSTEN     39 GT RQCNV ASMB LSTEN     40 AL ASMB LSTEN         26 CLASSES AVAILABLE     Each of the classes in use can be in one of the following three states:     AL -- the class has been allocated but no program is waiting to     receive data from it.      GT -- the class has been allocated and the program named in the "GET"     column iswaiting on it for data via a class I/O "GET" call.      BU -- the calss has been allocated and data is currently waiting.      The number of buffers and their total size is printed on one     line and the allocation information is printed on a second     line.         The possible owner field lists the programs which may have allocated        the class.  For slave monitors, this would be LSTEN (unless LSTEN was - FOR HP INTERNAL USE ONLY - 12 DATA COMMUNICATIONS DEBUGGING UTILITIES DSINF        removed from the system after initialization).  Because of the way RTE        maintains its I/O class table, it is impossible to determine exactly        which program originally allocated a class.  If the program which        allocated the class has been removed from the system, or removed and        later restored to a different ID segment address, it will not appear as        a possible owner.  If a program is aborted while waiting with a get,        the get program name will be .     3. DS/1000 VALUES     DSINF prints the following information in response to the VA command:     DS/1000 VALUES:     RESOURCE NUMBERS: OWNER LOCKER     TABLE ACCESS 40 LSTEN     QUIESCENT 39     QUEZ "LISTEN" 38         TIMEOUT VALUES (SEC):     MASTER T/O 45     SLAVE T/O 30     REMOTE BUSY WAIT 3     REMOTE QUIET WAIT 0         21 RFA FILES MAY BE OPEN         HP3000 IS ON LU 12      If an HP 3000 is not connected to the node, the QUEZ "LSTEN" resource      number and HP 3000 LU are not printed.       For the resource numbers, the name of the owner program should be      because all DS/1000 RN'S are allocated globally.  Under normal      conditions, the table access and quiescent RN'S are not locked (      is the locker) and the QUEZ RN is locked globally.  in the above      example, LSTEN has not completed initialization and has the table      access RN locked locally.  The quiescent RN is locked globally when the      system is quiesced.  4. DUMP OF SYSTEM AVAILABLE MEMORY BLOCK      DSINF dumps the locations used for transaction control blocks and the      HP 3000 transaction status table.       [See material in the DS/1000 lists section for information on TCB'S.]      DUMP OF TCB BLOCK      LOC OCTAL CONTENTS OF LOC THROUGH LOC+4 - FOR HP INTERNAL USE ONLY - 13 DATA COMMUNICATIONS DEBUGGING UTILITIES DSINF      55610 55615 42123 27461 30060 30040      55615 55622 32057 33467 20122 52105      55622 55627 44511 20055 30462 31464      55627 55634 33470 34460 24450 23446      55634 55641 21442 20500 25452 54417      55641 55646 57062 20044 42516 42040      55646 55653 46501 52040 0 36516      55653 55660 0 55725 372 1221      55660 55665 1 55655 367 1216      55665 55672 36122 55701 100035 613      55672 0 2 55732 367 1222           DUMP OF HP3000 TRANSACTION STATUS TABLE      LOC OCTAL CONTENTS OF LOC THROUGH LOC+7      55677 0 0 0 0 0 0 0      55706 0 0 0 0 0 0 0      55715 0 0 0 0 0 0 0      55724 0 0 0 0 0 0 0      55733 0 0 0 0 0 0 0      55742 0 0 0 0 0 0 0      Every time an HP 3000 user makes a master request to the HP 1000, an      entry is made in the transaction status table (TST).  If there is no HP      3000 connected to the node, the TST table is not printed.  Each entry      in the TST consists of 14 words (two lines of the dump):      WORD 1 - DS/1000 stream (0 if the table entry is not in use)      WORD 2 - local sequence number      WORD 3 - holding class number      WORD 4 - monitor class number      WORD 5 - call type code      WORD 6 - mask word (POPEN)      (the rest of the words are from the DS/3000 fixed format header)      WORD 7 - BITS 8-15: length of DS/3000 request (words)      BITS 0- 7: DS/3000 message class      WORD 8 - reserved for future use      WORD 9 - DS/3000 stream      WORD 10 - reserved for future use      WORD 11 - BITS 8-15: from process number      BITS 0- 7: to process number      WORD 12 - local sequence number      WORD 13 - MPE sequence number      WORD 14 - number of bytes in parameters and data 5. DS/1000 LISTS      DSINF prints the number of entries in each of the DS/1000 lists.  If a      list has entries, DSINF prints the address of the first TCB in the      list.  After the LI or DU command has been completed, the same list      information will be printed for the lists until a new dump of SAM is      taken.  The lists always reflect the state of the TCB's in the previous      dump.  - FOR HP INTERNAL USE ONLY - 14 DATA COMMUNICATIONS DEBUGGING UTILITIES DSINF      There are three types of active transaction control blocks:      PROCESS NUMBER LIST ENTRIES.      An entry is made in this list each time an HP 1000 user issues a      successful HELLO to an HP 3000. The entry is deleted after a BYE.           The words in the TCB have these meanings:           WORD 1 - address of next entry in list (0 indicates end)      WORD 2 - reserved for future use      WORD 3 - MPE session main process number      WORD 4 - logging device LU number      WORD 5 - BIT 15: when set, indicates a bad entry      BITS 0-14: logon program's ID segment address           MASTER LIST ENTRIES.      The master list contains an entry for each master request currently      outstanding. The words in the TCB have these meanings:           WORD 1 - address of next entry in list (0 indicates end)      WORD 2 - BIT 15: UPLIN may set this bit      BIT 14: set for requests to HP 3000      BITS 8-13: reserved for future use      BITS 0- 7: timeout counter. Timeout occurs when the      counter reaches octal 377.      WORD 3 - local sequence number      WORD 4 - BIT 15: when set, indicates long master timeout (about      twenty minutes)      BITS 0-14: master class number      WORD 5 - BIT 15: when set, indicates a bad entry      BITS 0-14: master program's ID segment address           SLAVE LISTS ENTRIES.      The slave lists contain an entry for each outstanding slave request.      There can be a slave list for each enabled slave monitor. The words      in the TCB have these meanings:           WORD 1 - address of next entry in list (0 indicates end)      WORD 2 - same as master list entry      WORD 3 - local sequence number      WORD 4 - origin sequence number      WORD 5 - origin nodal address      Any TCBs which are not in these three active lists are not currently      being used and are in the null list.  - FOR HP INTERNAL USE ONLY - 15 DATA COMMUNICATIONS DEBUGGING UTILITIES DSINF      DS/1000 LISTS           0 ENTRIES IN MASTER REQUEST LIST           ACTIVE SLAVE MONITORS: 1ST TCB      STREAM CLASS MONITOR ENTRIES LOCATION      1 34 DLIST 0      2 33 CNSLM 0      3 32 EXECW 0      4 31 PTOPM 0      5 30 EXECM 0      6 29 RFAM 0      7 28 OPERM 0      9 27 PROGL 0      0 ENTRIES IN SLAVE LISTS           11 ENTRIES IN NULL LIST, STARTING AT 55610      0 ENTRIES IN HP3000 PROCESS LIST      The HP3000 process list is not printed if no HP 3000 is connected.       Slave monitor stream lists are not printed if the associated slave      monitor has not been enabled by LSTEN.  6. NODAL ROUTING VECTOR      DSINF prints the same NRV information as LSTEN:      NRV SPECIFICATIONS:      LOCAL NODE : 3, NO. OF NODES= 8           1: NODE= 1, LU= 7, TO= 90(SEC.)           2: NODE= 2, LU= 7, TO= 45(SEC.)           3: NODE= 3, LU= 0, TO= 0(SEC.)           4: NODE= 4, LU= 7, TO= 90(SEC.)           5: NODE= 5, LU= 7, TO= 90(SEC.)           6: NODE= 0, LU= 7, TO= 90(SEC.)           7: NODE= 33, LU= 7, TO= 90(SEC.)           8: NODE= 11, LU= 7, TO= 90(SEC.)           LAST LOAD-NODE= 2      The last APLDR load-node (the last node from which a program was      downloaded) is printed for RTE-M systems only.  - FOR HP INTERNAL USE ONLY - 16 DATA COMMUNICATIONS DEBUGGING UTILITIES DSINF 7. DS/1000 EQUIPMENT TABLE INFORMATION     DSINF prints the following for each EQT with driver type 65:     DVA65 EQT INFORMATION           EQT   7, LU   7:      WORD VALUE MEANING WORD VALUE MEANING      1 0 I/O LIST ADDRESS 2 30702 INITIALIZATION ADDRESS      3 31443 CONTINUATION ADDR 4 10125 STATUS/UNIT/SUBCHNL*      5 32401 AV/TYPE/STATUS* 6 107 CONWD      7 0 DATA BUFFER ADDR 8 14 DATA BUFFER LEN      9 0 REQUEST BUFFER ADDR 10 0 REQUEST BUFFER LEN      11 31467 COROUTINE ADDRESS 12 2000 CURRENT STATUS*      13 34145 EQT EXTENSION ADDR 14 177775 NOMINAL TIMEOUT      15 0 MICROCODE TIMEOUT 16 1 DATA TRANSFER COUNT      17 0 LAST WORD RECEIVED 18 0 VPW/REPLY REQ LENGTH      19 0 DPW/REPLY DATA LEN 20 0 TOTAL BLOCK TRANSFER      21 0 TOTAL   RETRIES 22 34530 NEW REQ ID SEQ ADDR           *BIT BREAKDOWN 15 12 9 6 3 0      WORD 4 0 0 0 1 0 0 0 0 0 1 0 1 0 1 0 1      WORD 5 0 0 1 1 0 1 0 1 0 0 0 0 0 0 0 1      WORD 12 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0      Note that EQT words 16 through 22 are in the EQT extension.       If an HP 3000 is connected, the following is printed:      DVG67 EQT INFORMATION           EQT   12, LU   12:      WORD VALUE MEANING WORD VALUE MEANING      1 0 I/O LIST ADDRESS 2 32033 INITIATION ADDRESS      3 32001 CONTINUATION ADDR 4 100014 STATUS/UNIT/SUBCHNL*      5 33400 AV/TYPE/STATUS* 6 0 CONWD           *BIT BREAKDOWN 15 12 9 6 3 0      WORD 4 1 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0      WORD 5 0 0 1 1 0 1 1 1 0 0 0 0 0 0 0 0           SLC LONG TERM STATISTICS      0 READ REQUESTS 0 WRITE REQUESTS      0 MESSAGES TRANSMITTED 0 ERROR-FREE MSGS RECV      0 LINE ERRORS 0 NAKS RECEIVED      0 BCC/PARITY ERRORS 0 LONG TIMEOUTS      0 RESPONSE ERRORS 0 RESPONSE REJ      0 WACK/TTD RECEIVED      - FOR HP INTERNAL USE ONLY - 17 DATA COMMUNICATIONS DEBUGGING UTILITIES DSINF      For both drivers, words 4 and 5 have the standard RTE meanings:           WORD 4--      BIT 15: 1 if DMA required      BIT 14: 1 if automatic buffering is used      BIT 13: 1 if driver is to process power fail      BIT 12: 1 if driver is to process time-out      BIT 11: 1 if device timed out      BITS 6-10: last subchannel addressed      BITS 0-5: select code for I/O controller           WORD 5--      BITS 14-15: 0 if I/O controller is available, 1 if disabled (down),      2 if busy, 3 if waiting for DMA      BITS 9-13: driver type (65 for DVA65, 67 for DVG67)      BITS 0- 8: status      DVA65 maintains status bits in words 5 and 12           WORD 5--      BIT 7: write flag for GRPM      BIT 6: parity or protocol error      BIT 5: remote busy      BIT 4: stop received      BIT 3: time-out      BIT 2: simultaneous request reject      BIT 1: request pending on a write, or not pending on a read      BIT 0: request completed with no errors           WORD 12--      BIT 14: microcode read/write flag      BIT 13: flag for write retry in progress      BIT 12: last successful operation (1 = write)      BIT 10: listen mode enabled      BIT 9: request pending      BIT 6: broken line      BITS 0-5: retry counter or broken line counter      - FOR HP INTERNAL USE ONLY - 18 DATA COMMUNICATIONS DEBUGGING UTILITIES DSINF      DVG67 maintains status in bits 0-7 of word 5:           OCTAL      CODE ABORT? MEANING           0 NO the request completed normally      1 YES invalid request      2 YES request incompatible with line state      4 YES local hardware failure      5 NO end-of-transmission (EOT) received      6 NO disconnect (DLE EOT) received      7 YES long timeout occurred      10 YES ENQ received in response to EOT      11 YES data overrun      12 YES maximum number of NAKS received      13 YES maximum number of ENQS sent      14 YES reverse interrupt (RVI) received      15 NO ENQ received in response to ENQ sent      16 YES NAK received in response to write inquiry      17 YES maximum number of ENQX received in write      conversational situation      20 YES incorrect response (not NAK) to TTD      21 YES impossible situation      22 YES text error           Bits 5-7 are the block specification bits:           BIT 5 = 0 for no heading      1 for heading           BIT 6 = 0 for nontransparent mode      = 1 for transparent mode           BIT 7 = 0 for ETX ending block      1 for ETB ending block - FOR HP INTERNAL USE ONLY - 19 DATA COMMUNICATIONS DEBUGGING UTILITIES NDTDU     3.2 NDTDU     PROCEDURE NAME:     NDTDU     PART NUMBER:        24999-16213     DESCRIPTION:      This program formats and prints the information stored in a DS/1000      NTD (network description table) file created by NTDGN.  Because it      does not use RFA or DEXEC calls, it can be run either before or after      a node has been initialized by LSTEN.       NDTDU uses the area at the end of its partition to read the NTD file      records.  Tests that have been run in RTE-III indicate a network file      defining 180 nodes should fit without adding extra pages.  For each      additional page given to NDTDU, it will be able to add 341 nodes.       NDTDU is designed to run as a background partition-resident program.      It is not designed to run in RTE-M II systems.       When loaded on-line, NDTDU must be given access to subsystem global      area.  It's default priority is 89.      USAGE:      Run from RTE with: *RU,NDTDU,,,      The scheduling parameters have the following meanings:           the first parameter is either the namr for the NTD file (in the      format name:security:cartridge) or the lu of an interactive device      where the namr can be read. default is 1 or the mtm lu number.                the lu of an output device where information can be printed.      Default is same as .                the number of columns on the print page. default is 80. minimum is      50. maximum is 128.      If the command *BR,NDTDU is entered, NDTDU stops printing, closes the      NTD file, and terminates.  - FOR HP INTERNAL USE ONLY - 20 DATA COMMUNICATIONS DEBUGGING UTILITIES NDTDU  ERRORS      NDTDU detects several errors and reports them to the user.           " *** FMP ERROR - NNNNN ***"      The indicated FILE MANAGER error occured when NTDGN tried to access      the NTD file.  See batch-spool monitor manual for further      information.           " *** BAD DATA IN FILE ***"      The specified file does not conform to the NTD format in one of the      following areas: type is not 9, first word of record >= 0, or the      timeout/lu word is negative.           " *** TOO MANY NODES.  MAX = NNNNN ***"      The NTD file contains more nodes than NDTDU can handle.  (NDTDU      prints the maximum number of nodes that it can process.) Reload      NDTDU and assign it another page.   OUTPUT      NDTDU prints a header of three lines:      1.  The namr given it for the NTD file      2.  The local node number (or a blank line if the node isn't      initialized)      3.  The number of nodes in the network      The "to" node numbers are printed across the page and the "from" node      numbers are printed down the left side.  At the intersection in the      resulting matrix two numbers are printed.  the top number is the LU      number used to communicate between the "from" and "to" nodes.  The      lower number is the timeout value for the link.  When the "from" and      "to" numbers are the same, both values are zero.  If it is impossible      to communicate between the nodes, the numbers are left blank.       NDTDU prints as many "to" node numbers as will fit in the given width.      If they do not all fit, NDTDU will make as many passes as are needed      through the file (after all the "from" numbers are printed) to handle      the remaining "to" node numbers.  - FOR HP INTERNAL USE ONLY - 21 DATA COMMUNICATIONS DEBUGGING UTILITIES TRC65,DRT65     3.3 TRC65,DRT65     PROCEDURE NAME:     TRC65,DRT65     PART NUMBER:        24999-16225,24999-18226     DESCRIPTION:          1)  Displays line protocol sent and received (data words sent are          not displayed).  Effectively turns any terminal into a logic          analyzer for the link.           2)  Displays driver state with each word.  A legend is printed          which provides state-code description.           3)  Allows tracing all lines, or allows you to focus attention on          only one.           4)  Displays TBG 'tick' count, providing time between event          information.           5)  Displays pass number and time-of-sample, flagged in inverse          video if the printout program has gotten behind the driver.           6)  Displays the class number allocated and resource number          allocated.  You may need this information if you have to bring          it out of its resource number lock suspension, e.g., if you          asked for a trace of the wrong line.           7)  Can save 'trace' buffer information in a disc file for          high-speed and/or continuous usage purposes.  When the last          record of the file has been written, the program will either          terminate, or rewind the file, causing new data to be written          over old.  The message "/TRC65: REWINDING FILE" is printed the          first time to tell you that the data in the circular file is          all valid (if you examined the data in the file prior to          printout of this message, an indeterminate number of records          at the end of the file would contain garbage).           Since the file is opened non-exclusively, you may examine the          circular file while it is being logged by using another copy          of this program.  You should be aware that you may          occasionally see very strange-looking printouts, as there is          no synchronization between the two copies of this program.           However, you may find this a useful feature.  for example,          since the driver provides synchronization with the program via          a resource number, the program will "hang up" if the line is - FOR HP INTERNAL USE ONLY - 22 DATA COMMUNICATIONS DEBUGGING UTILITIES TRC65,DRT65          inactive.  You can look at what's in the file with another          copy of the same program, while still leaving the first copy          "armed",i.e., ready to log new data records into the file as          soon as they become available.           8)  You can get a printout of the data stored in the circular data          file (see   7 above).  when taking data from a data file, the          program waits two seconds before printing each "screen".  This          is to give you a chance to examine the previous screen.  If          you need more time, two seconds is more than enough time to          obtain system attention (the device should be unbuffered,          though).  Hold its attention as long as you need to examine          the screen, then type a carriage return or space carriage          return.           9)  Usable with terminals from ASR-33 to the latest HP 264x          termianl.  The display will be enhanced, however, if output is          to a DV.05 or DV.07 type of terminal, enhancements include:          Inverse video for pass number when not sequential(i.e.,          display does not show consecutive trace records)          Inverse video for all protocol words received black video          for transmissions          All abnormal protocol words ('RLM', 'RLW', 'STOP') are          flashed          10)  Keeps counts of the number of "RC", "RLM", "RLW" and "STOP"          protocol words seen, thus providing an indication of line          quality somewhat more exact than the statistics maintained by          the driver.           11)  Can optionally print or log either all 'trace' buffers or only          those containing 'RLW', 'RLM' or 'STOP' (i.e., only those in          which an error occurred).  Data source may be either "live" or          from disc file.           12)  Prints the number of abnormal protocol words seen in each          record, and summary of the total number of protocol words seen          when the program terminates.           13)  A rough estimate of the line quality may be obtained by          counting the number of 'RLM' words observed and comparing to          the number of messages sent during the observation interval.           The accuracy of this method improves as the observation period          increases.           14)  Works with hardwired and modem links.          This program operates with the cooperation of the driver (a version of         DVA65 supporting 'trace' must be used), but without special microcode. - FOR HP INTERNAL USE ONLY - 23 DATA COMMUNICATIONS DEBUGGING UTILITIES TRC65,DRT65         It displays only the protocol words which the software driver itself         sent at the end of the transfer, nor the 'TNW' which separates them.          A 'trace' may be set up on either or both sides of the line.      USAGE:      *ON,TRC65,[lutty[,luprin[,mode]]]      lutty = LU of operator console.  Used for dialog and error messages.       Default is your terminal (MTM environment), else 1.       luprin= LU for printing trace table (specify only when trace table      printout is desired to a unit other than .  Default is      lutty.       Note: if luprin = 2, then all trace buffers will be recorded      in their "raw" form on a disc file, whose name & size are then      asked for by the program.  The file will normally be circular,      but you can specify that the program quit as soon as the last      record is written (actually, on the attempt to write the next      one after that).  If the default (circular) option is taken,      trace information is maintained in a circular fashion: old      information is overwritten by new, the number of "fresh" trace      buffers being determined by the size of the file.  When the      file is rewound for the first time, a message is printed to      inform you that the data in the file is now valid (prior to      this, data records towards the end of the file would contain      garbage).       Syntax is: filnam : sc : cr : :   records for file      Note that the parameter specifying   of records for file is in      the same position as file size when specifying a with      "FMGR" syntax, and hence should be easy to remember.       To obtain a formatted printout of this information, simply set      the 'break' flag so the program will close the file.  Wait for      the program to print its termination message:: this will      include the number of complete buffers logged.  Then re-run      it, specifying the file name in response to the question,      "LINE LU?"      Note: you will have to use the pass number to determine the      oldest and newest entries.  The program simply formats records      starting from the first one in the file.       : bit mask      bit 0 = 0 causes program to wait until whole buffer is filled before      printing.  # 0 then program will print contents of trace      buffer, continuously, without waiting for synchronization from - FOR HP INTERNAL USE ONLY - 24 DATA COMMUNICATIONS DEBUGGING UTILITIES TRC65,DRT65      the driver.       bit 1 = 0 causes program to print driver state legend.       # 0 inhibits printout of driver state legend.       bit 2 used only when 'trace' data is being logged to a disc file.       =0 causes program to automatically rewind file when last      record has been written & begin writing new data over oldest      data records.  The message "/TRC65:rewinding file" is printed      after the file is rewound the first time, thus notifying the      user that the data in the file is completely valid.       #0 causes program to terminate as soon as the last record has      been written into the file (actually, when on the attempt to      write the next record after that).  The file is closed and the      termination message is printed.       bit 3 used to include or ignore 'trace' records containing no      abnormal protocol words.       =0: include all 'trace' records      =1: include only those 'trace' records containing abnormal      protocol errors.       Note: this feature may be used either to log only those records      containing errors, or to print only those records which contain      errors.  It will probably be found most useful to log all records      into very large logging files, then print only those records in      which errors occurred.  It will still be possible to use the      record number selection option on printout if it is necessary to      determine the context of the "bad" records.  However, by logging      only exception conditions, over a long period of time, one might      then go back later and print these records, using the summary      printed at the end as a "figure of merit" for the particular      communication line.       "LINK LU, -LU TO TRACE ALL, OR ?"      You are asked to specify the communication link LU to be traced.  To      "trace" activity on all links, enter the negative of any link LU.       Enter zero to terminate completely, release all resources, and disable      trace mode.       The program checks the response.  The only allowable responses are:      - A file [,first record  [,last record  ]] first record      number and last record number may optionally be specified,      separated by commas.  The defaults allow the whole file to be      printed.  You may use this to quickly scan through a large trace      file in order to locate a particular area of concern, and then      print that.  If the last record number specified is less than the      first, then only one record will be printed.  - FOR HP INTERNAL USE ONLY - 25 DATA COMMUNICATIONS DEBUGGING UTILITIES TRC65,DRT65      Illegal if output to a file has already been specified.  if an      error occurs on the attempt to open the file, the error number      will be printed:      FMP ERR - nnn      (where nnn = open error code) and the program terminates.       - Zero      - A valid link LU, or the negative of one (must be connected to a      device of type 65)      If none of the above, the message "illegal response" will be printed      and the question will be repeated.       To change the print LUs or trace mode, set the 'break' flag for this      program, and re-schedule it.       NOTE! NOTE! NOTE!           1)  This program semi-permanently allocates a block of system      available memory to be used as the trace buffer.  This is a potential      hazard if you leave it allocated for long periods of time (i.e., hours      or days) because it may be located in 'SAM' such that it prevents      large buffers from being allocated, thus producing a 'deadly embrace'.      2)  This program allocates a class number and a resource number when      it runs.  They are stored in 'RES', so they can't be lost.  If you      must abort the program, ALWAYS re-run it again, specifying a trace LU      of 0.  This will release the class buffer, class number, and resource      number.       3)  The program locks itself in its partition when it is logging data      (except when the data source is a file).       4)  "Escape sequences" are used when the print device is a terminal.       When used on multipoint terminals, you MUST have the update which      supports transparency mode.       5)  Some protocol words will not show up in the 'trace' because they      are handled completely within the microcode.  This includes the two      parity words and the intervening 'TNW'.  Also, there is an asymney      between what one observes on the receiving side, and what one sees on      the transmitting side.       6)  When comparing 'trace' printouts between two nodes ( should be      logging into disc files), note that the TNWs sent by microcode will      show up on the receiving side by not on the transmitting side.  This      means you should make allowances for the "lack" of two TNWs when      comparing word-for-word between sides.  - FOR HP INTERNAL USE ONLY - 26 DATA COMMUNICATIONS DEBUGGING UTILITIES TRC65,DRT65      The program must be loaded with access to SSGA.  Program type may be      either 2 or 3.       The protocol words are printed two to a line, in the order:     

(repeated twice)      = 'x' if word was transmitted = 'r' if word was received.       The line will be displayed in inverse video if the terminal      is driven by DV.05 or DV.07.  An up-arrow will be printed if      there was a time-out indication.  A right-arrow (->) will be      printed to the left of for the oldest entry.       Protocol word mnemonic: If data word does not match any of      these possibilities.  For example, the data lengths will not      match.       = protocol word in octal.       = driver state number.  A legend is printed when this      program first begins execution, giving a brief description of      each driver state.  For detailed information, it is helpful      to have a driver listing.       = eqt number (useful in separating activity among various      lines), printed in decimal.       = low 16 bits of $TIME word when entry was made,      converted to decimal.  This provides an elapsed time      indication between this entry and the previous one.  Each      tick represents ten milliseconds.          To change the size of the trace buffer, change '.SIZE'.  the size must         be a multiple of 4, plus 2 extra words.  It must not be less than 128         words if disc files are to be used.          This program requires the version of DVA65 which supports 'trace', and         the revision 1901 version of 'RES' or subsequent.  the 'trace' version         of the driver produces almost no increased overhead when trace mode is         disabled, and very little while it is enabled, since it is of most use         with high error-rate lines, which implies modems, and the existing         driver adds a very insignificant overhead to transmissions because         modems are so slow.          The trace buffer format is described in the source for DVA65.  The         format of the disc records is almost identical, except that the time         at which the record was obtained and the local node number are         contained in the three words immediately preceding the rest of the         record as described.  The format of the time of day is exactly the         form of the two "$TIME" words in RTE.  the record size is 128 words, - FOR HP INTERNAL USE ONLY - 27 DATA COMMUNICATIONS DEBUGGING UTILITIES TRC65,DRT65         the trace buffer size is 122 words (enough for 30 entries, or 15 lines         on the screen).      DVA65 PROTOCOL (as recorded in 'trace' buffers)         The parity word exchange and all data words are not recorded in the         'trace' buffer.  See the Network Manager's Manual for a complete         protocol description.          The description below shows both sides.  If you were observing from,         say, the "transmitting side", then arrows to the right would appear as         "x", arrows from the right would appear as "r" (received).  The         reverse would, of course, be true for observers at the "receiving         side".       TRANSMITTING SIDE RECEIVING SIDE      ----------------- ------------------      RC --------------------------------->      <-------------------------------- TNW      ----------------------->      <---------------------------------- (echo of length)      ------------------->      <-------------------------------- (echo of length)      note: bit 15 set if in      closed loop.      TNW ---------------------------->      <------------------------------(note:TNW sent by microcode,           and therefore not seen      by "TRACE" on this side)      Data transmission is handled by microcode.  No trace entries are made      for any data words, nor for the parity words nor intervening TNW.       When transmission is complete, the sending side will send a 'TNW' if      it was good, or 'RLM' if a retry is to be attempted, or 'STOP'      otherwise.       TNW ---------------------------->      or      RLM ---------------------------->      <-------------------------------- TNW      or      STOP --------------------------> - FOR HP INTERNAL USE ONLY - 28 DATA COMMUNICATIONS DEBUGGING UTILITIES TRC65,DRT65           DRIVER LEGEND:           STATE 0: Initiating read, sending TNW      STATE 1: Writing, sending RC      STATE 2: Writing, sent RC, expect TNW      STATE 3: Writing, sending data length      STATE 4: Writing, sent data lnth, expect echo      STATE 5: Writing, sending request length      STATE 6: Writing, sent req. lnth, expect echo      STATE 7: Write retry      STATE 8: Request preamble write failure--retry      STATE 9: Writing, simult.rqst, am backing down.      STATE 10: Writing, sending TNW, expect TNW      STATE 11: Performing write retry      STATE 12: First interrupt in LSTEN mode, exp.RC      STATE 13: Power failed!      STATE 14: Receiving, expecting data length      STATE 15: Echoing data length, expect req. lnth      STATE 16: Receiving, expecting req. lnth      STATE 17: QUEUE busy, sending 'STOP'      STATE 18: Request to send 'STOP'      STATE 19: Read rqst, echoing rqst lnth      STATE 20: Read rqst, checking response      STATE 21: Block has been read, waiting for TNW      STATE 22: Block read but last ctrl unrec      STATE 23: Checking response to RLW      STATE 24: 'STOP' received during xmit--abort      STATE 25: Parity error(read or write)      STATE 26: Protocol failure      STATE 27: Time-out occurred-end of rqst      STATE 28: Simultaneous request retry      STATE 29: LSTEN mode aborted with stop - FOR HP INTERNAL USE ONLY - 29 DATA COMMUNICATIONS DEBUGGING UTILITIES PSMON     PROCEDURE NAME:     PSMON     PART NUMBER:        24999-16224     DESCRIPTION:      Provides "passive monitor" capability for DS/1000 12665 hardwire      links.  Useful in those cases where 'TRC65' does not show enough (this      program displays all data on the communication link, not just certain      protocol words).      REQUIREMENTS:      1) Separate computer      2) Two HP 12665 interface cards (in addition to those used to      connect the computer to a DS/1000 network, if any)      3) Connecting cables modified for passive monitoring.       4) An RTE operating system (may be RTE-M) with DS/1000 software      generated in.      USAGE:      1) Install two interface cards in the computer and hook them up to      the line to be traced with a cable modified to provide passive      monitoring.       2) Edit the source for 'PSMON', specifying the select codes for the      two interface cards as the definitions for "XMTIF" and "RCVIF".       All data taken from the interface in the "XMTIF" select code will      be considered as "transmit" data.  All data from the "RCVIF"      select code will be considered as "receive" data.  Be sure to      write down which is which so you can determine data direction      from the printout.       3) Re-assemble the source and load the program in the computer to be      used for monitoring.       4) Schedule the program:      *ON,PSMON,[lutty[,luprin[,node [,mode[, points]]]]]      lutty = Lu of operator console(must be capable of input & output)      at local node.  Used for dialog and error messages.       Default is your terminal (MTM environment), else 1      NOTE : Special features are invoked if the terminal is driven      using DVR05 or DVR07:      1) Each line which is 'recieved (as opposed to      'transmitted') is displayed in inverse video.  - FOR HP INTERNAL USE ONLY - 30 DATA COMMUNICATIONS DEBUGGING UTILITIES PSMON      2) Abnormal protocol indications ('RLM', 'RLW', 'STOP') are      highlighted: 'RLM' & 'RLW' are underlined, 'STOP' is      shown blinking.  Requires optional modules supporting      these functions be installed in the 264X terminal used.       luprin= LU for printing trace table if not the same as at      remote or local node.  Useful when hardcopy log is      desired.  Default is lutty.       NOTE: If luprin = 2, then all trace records will be      recorded in their "raw" form, either on a disc file or a      remote device, such as a tape.  The program will ask for      the file parameters; enter the name of the file,      security code, etc., or the LU of the remote device.       When outputting raw data to a disc file, the file is      normally assumed to be circular: old information is      overwritten by new, the number of "fresh" trace records      being determined by the size of the file.  When      outputting to a remote device, such as a mag tape, all      data is recorded.       syntax is: filnam : sc : cr : :  records for file      or           To obtain a formatted printout of this information, simply set the      'break' flag so the program will close the file, then re-run it,      specifying the file name or device LU in response to the question,      "FILE OR DEVICE TO GET 'TRACE' DATA?"      NOTE: If disc files are not going to be used, you do not need to load      the program with the FMP routines (CREAT, OPEN, CLOSE, READF, etc.),      and may ignore these undefined symbols at load time.       = remote node number for printout (allows you to use a      computer without an output device of its own).  Default is      local node.  If luprin = 2 then data logging is done      locally, and this parameter has no effect.       bit mask bits 0 not used      bit 1 =0:(default) causes printout or logging of all data gathered.      =1: causes program to ignore all data buffers which contain      no abnormal protocol words.  ('STOP', 'RLM', 'RLW')      bit 2 used only when 'trace' data is being logged to a disc file.       =0 causes program to rewind file automatically when last      record has been written.  New data overlays old.  The      message "/PSMON:REWINDING FILE" is printed after the first      time to inform you that the data in the file is now valid. - FOR HP INTERNAL USE ONLY - 31 DATA COMMUNICATIONS DEBUGGING UTILITIES PSMON      = 1 causes program to terminate as soon as the last record      has been written (actually, when the attempt is made to      write the next one after that).  The file is closed and the      termination message is printed.       < points> = number of data points to log.  Maximum allowable value,      and also the default, is 2048 points.       5) The program will wait for activity on the communication link with      the interrupt system off.  Use 'REMAT' to create such activity.  It is      advisable to use a transfer file containing a large number of "TI"      commands for the simple reason that the data will be far too      voluminous otherwise.       At any time, you may bring it out of its "waiting for data" loop by      setting the sign bit in the switch register.  For your own      information, the program displays its internal "pseudo-clock" in bits      14 thru 0 of the switch register while it is waiting.       NOTE! NOTE! NOTE!      When gathering "live" data (i.e., not taking data from a disc file),      this program turns normal RTE interrupt processing off!!       This means that the system time-keeping and other real-time activities      cease during this period.  You must be sure that no other critical      activities exist before using this program, and you may wish to re-set      the system time-of-day afterwards.  (Be sure to re-schedule all      programs in the time list whose "time of next schedule" has been      passed over.  You can find out which ones these are from a 'WHZAT'      printout).       During the printout phase, normal RTE interrupt processing is restored      and the system becomes an RTE again.       You will be asked to specify the data source.  Acceptable responses      are:      1)   File ---the name of a data file in which data was      logged during some previous run.  The cartridge reference      number and security code may be specified in the usual way.      2)   The logical unit of some device, typically a mag tape or      mini-cartridge, on which data was logged during some      previous run.  The program will continue to read until an      EOF or EOT condition or some other mag tape-related error      condition is set.       3)   Blanks--the program will take data "live", i.e., directly      from the passive-monitor interface cards.  - FOR HP INTERNAL USE ONLY - 32 DATA COMMUNICATIONS DEBUGGING UTILITIES PSMON      To terminate this program while it is printing, set the "break" flag.      To terminate it while it is gathering data (non-privileged interrupts      are off), set the sign bit in the switch register.       The print format shown below is actually repeated twice per line:     

     = 'x' if word was transmitted = 'r' if word was received.     

= mnemonic if data word matches one of the protocol words.       Note: since data is transmitted transparently over these      links, occasional "matches" to protocol words may appear.      You will have to study the activity surrounding the      "match" to determine if it is, indeed, valid.       Mnemonics:      RC TNW RLM RLW STOP      If not a match to above, then blanks are used.       = protocol word in octal.       = a pseudo-"clock" number which is      incremented after checking the two interface cards for      data.  This provides some indication of elapsed time.       Each tick represents about twenty microseconds or so,      depending on whether data was available in this "pass"      for the "receive" or "transmit" path or both.       NOTE: to analyze any particular sequence, one must be familiar with      the line protocol (see Network Manager's Manual for details).       To change the size of the trace buffer, change ".SIZE".  It must be a      power of two.       The "trace" buffer format is:      buffer: 1st data word observed      buffer+1:      buffer+2:2nd data word observed      " 3:      . .      etc.           = "transmit" line or "receive" line flag,      coded 0/1, and stored in bit 15.      = 15-bit unsigned integer pseudo-"clock" value      representing the time at which the data was available. - FOR HP INTERNAL USE ONLY - 33 DATA COMMUNICATIONS DEBUGGING UTILITIES PSMON      Default select codes for the passive monitor cards are (note: the      actual declaration in the source is shown to aid you in finding what      to change):      RCVIF EQU 16B "receive" line interface select code      XMTIF EQU 17B "transmit" line interface select code      WIRING DIAGRAM FOR MODIFIED CABLE - FOR HP INTERNAL USE ONLY - 34 DATA COMMUNICATIONS DEBUGGING UTILITIES SLCIN     3.4 SLCIN     PROCEDURE NAME:     SLCIN     PART NUMBER:        24999-16214     DESCRIPTION:      This program prints long term statistics and the event trace table      maintained by the synchronous line control (SLC) package for links      from DS/1000 to HP 3000 systems.  In DS/1000, the implementation of      SLC is handled by the module HSLC and the driver DVG67.       The long term statistics and event trace table are maintained in the      SSGA module D$EQT.  (when DSINF is loaded on line it must be given      access to SSGA.) In the currently released version, there are 100      words set aside for the trace table.  This number can be changed by      modifying the source code, re-assembling D$EQT, and re-generating the      system.       Each entry in the trace table contains two words plus one word for      each event and state that occurs during the given request.  Here is      the format:      +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+      bits !15!14!13!12!11!10! 9! 8! 7! 6! 5! 4! 3! 2! 1! 0!      +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+      word 1 ! address of next entry !      +-----------------------+-----+-----------------+      word 2 ! v ! w ! x !      +-----------------------+-----+-----------------+      word 3 ! y ! z !      +-----------------------+-----------------------+      ! y ! z !      +-----------------------+-----------------------+      (y and z word repeated as many times as needed)                     v = completion status of request (see below)      w = i/o request code (1=read, 2=write, 3=control)      x = function code used in request (see below)      y = SLC event number (see below)      z = SLC state number that is the result of the event (see below)      The trace buffer is circular; when the last word if filled, the next      entry goes to the first word of the table.  - FOR HP INTERNAL USE ONLY - 35 DATA COMMUNICATIONS DEBUGGING UTILITIES SLCIN      The "station states" are the states SLC is in after each request when      it is waiting for another request.       The SLC initialize control request resets the trace table (all      previous entries are destroyed).  As requests are received by SLC, it      uses the event and current state to address its state transition      table.  This tells it what action to perform and what state it will be      in next.  Thus, the trace table can show how the HP 1000 got out of      step with the HP 3000 if something goes wrong.      USAGE:      Run from RTE with:      RU,SLCIN,      Where is the LU where the information is to be printed.       Default is 1 or the multi-terminal-monitor LU.       If the node has not been initialized by LSTEN, SLCIN will not print      the SLC information.  Instead it will tell the user to "RUN LSTEN      FIRST!"      If the node has been initialized, but the HP 3000 was not enabled,      SLCIN prints "HP 3000 not enabled" and terminates.       If the node has been initialized, SLC starts printing information.       The SLC long term statistics are printed first, followed by the event      trace table.  The trace table includes the octal status, the function,      and the event(s) and state(s) associated with the function.      MEANING OF STATUS      OCTAL      CODE ABORT? MEANING           0 NO The request completed normally      1 YES Invalid request      2 YES Request incompatible with line state      4 YES Local hardware failure      5 NO End-of-transmission (EOT) received      6 NO Disconnect (DLE EOT) received      7 YES Long timeout occurred      10 YES ENQ received in response to EOT      11 YES Data overrun      12 YES Maximum number of NAKs received      13 YES Maximum number of ENQs sent      14 YES Reverse interrupt (RVI) received      15 NO ENQ received in response to ENQ sent      16 YES NAK received in response to write inquiry      17 YES Maximum number of ENQX received in write - FOR HP INTERNAL USE ONLY - 36 DATA COMMUNICATIONS DEBUGGING UTILITIES SLCIN      conversational situation      20 YES Incorrect response (not NAK) to TTD      21 YES Impossible situation      22 YES Text error          SLC FUNCTIONS      READ FUNCTIONS--      READ INQUIRY      Used to wait for the 3000 to bid for the line with an ENQ.       READ INITIAL      Used to receive text from the 3000 after an ENQ is received.       WRITE FUNCTIONS--      WRITE INQUIRY      Used to bid for the line.  send an ENQ, receive an ACK0.       WRITE CONVERSATIONAL      The normal way of sending and receiving text with the 3000: send a      block, receive a block of text.  Continues until EOT is received      from 3000 or 1000 performs write reset.       WRITE RESET      Send an EOT to relinquish use of the line.       WRITE DISCONNECT      Send DLE EOT to inform 3000 that there is to be no more      transmission of data.       CONTROL FUNCTIONS--      CLEAR      Disables the interface borad and severs the link between HSLC and      DVG67.  (inverse of initialize.)      INITIALIZE      Establishes the link between HSLC and DVG67.       LINE OPEN      Readies the line for read/write operations by initializing HSLC      values.       LINE CLOSE      Disconnects the line and disables it for further read/write      operations.  (inverse of line open.)      CHANGE THE ERROR RECOVERY PARAMETERS      Resets the number of retries to 7 and the long timeout to 60      seconds.       ZERO THE LONG TERM COMMUNICATIONS STATISTICS      Resets all the long term statistics to zero.  - FOR HP INTERNAL USE ONLY - 37 DATA COMMUNICATIONS DEBUGGING UTILITIES SLCIN     SLC EVENTS      These are the events reported by SLCIN.  Some of these events are not      possible under the current implementation.            SLCIN ABBREVIATION FULL MEANING (IF NECESSARY)      ------------------ ---------------------------      line open req line open request      line close req line close request      read inquiry req read inquiry request      read initial req read initial request      read continue RQ read continue request      read repeat req read repeat request      read/rev int req read with reverse interrupt request      delay read      write inqury req write inquiry request      write cntnue req write continue request      write conv req write conversational request      WRT reset(EOT)RQ write reset request (write EOT)      write discon req write disconnect request (write DLE EOT)      delay write req delay write request      ACK0 received      ACK1 received      WACK received      RVI recv/sent RVI received or being sent      ENQ received      NAK received      EOT received      DLE EOT received      TTD received      text received      bcc prty/fmt err bcc parity or format error detected      text overrun      garbage received      bad id sequence      short timeout      long timeout      low      high      mid           SLC STATES           SLCIN ABBREVIATION FULL MEANING (IF NECESSARY)      ------------------ ---------------------------      unopened      control      read ENQ      read ENQ error      check read req check read request type      read - FOR HP INTERNAL USE ONLY - 38 DATA COMMUNICATIONS DEBUGGING UTILITIES SLCIN      read text      read RVI      restricted read      write ENQ      write ENQ error      ENQ-ENQ contentn ENQ-ENQ contention      write      write text      write respns ENQ write previous response ENQ      check response      bad ACK received      write retry      ENQ rcv in write ENQ received in write or write conversational      mode      ENQ rcrd in writ second state: ENQ record in write or write      conversational mode      write converstnl write conversational      write EOT      read EOT rsponse read EOT response      disconnect hang up (a disconnect)      write TTD          LOW, HIGH, AND MID EVENTS      When low, high, or mid appears in a dump, the meaning is associated      with the state on the line above (the state SLC was in when the event      started) not the one on the same line (the state after the event      completed).       The low, high, and mid events have different meanings for different      states.  They are defined as follows:      Read ENQ error      low -- not defined      high-- no error counter overflow      mid -- error counter overflow: bad id      Check read request type      low -- read delay made in read state or read inquiry      high-- read initial      mid -- read delay made in restricted read state      Read RVI      low -- 2nd RVI request      high-- 1st RVI request      mid -- not defined      Write ENQ error      low -- error counter overflow, no bad id      high-- no error counter overflow      mid -- error counter overflow, bad id - FOR HP INTERNAL USE ONLY - 39 DATA COMMUNICATIONS DEBUGGING UTILITIES SLCIN      ENQ-ENQ contention      low -- retry counter overflow      high-- no retry counter overflow      mid -- not defined      Previous response ENQ      low -- retry counter overflow      high-- no overflow--write mode      mid -- no overflow--write conversational mode      Check response      low -- bad ACK received      high-- RVI received      mid -- good ACK received      Bad ACK received      low -- timeout flag not set or bad-response flag set      high-- timeout flag set and bad-response flag not set (write      conversational mode)      mid -- timeout flag set and bad-response flag not set (write      conversational mode)      Write retry      low -- retry counter overflow      high-- no overflow--write mode      mid -- no overflow--write conversational mode      ENQ received (write or write conversational mode)      low -- text not just received      high-- text just received and ENQ not just sent      mid -- ENQ just sent      Second state--ENQ received in write      low -- retry counter overflow      high-- no overflow--write mode      mid -- no overflow--write conversational mode      Write EOT      low -- line error      high-- no line error      mid -- not defined      All other states      low -- line error      high-- not defined      mid -- not defined - FOR HP INTERNAL USE ONLY - 40 CRASH DUMP ANALYSIS CDA4,SNPSH,CDMP,TDMP     +-----------------------------------------------------+------------------+   | | |   | CRASH DUMP ANALYSIS | CHAPTER 4 |   | | |     +-----------------------------------------------------+------------------+     4.1 CDA4,SNPSH,CDMP,TDMP     PROCEDURE NAME:     CDA4, SNPSH, CDMP, TDMP     PART NUMBER:        24999-16197, 24999-16198, 24999-16199, 24999-     DESCRIPTION AND USAGE:      The crash dump analyze package provides a means by which a copy of a      crashed system can be saved on a mini-cartridge and be examined and      analyzedat a later time.       The package consists of three parts:      1.  !CDMP - the dump program dumps the first 32k of physical memory,      the system map, the user map, and both port maps (ie the crashed      system)to a mini-cartridge.       2.  SNPSH - the snapshot program dumps a system's snapshot (ie      entrypoint information) to a mini-cartridge.       3.  CDA4 - the analyze program performs the actual examination and      analysis of the crashed system.      SNAPSHOT PROGRAM      SNPSH is designed to run on-line on an up and running system.  It will      dump a snapshot of the system onto a mini-cartridge.       RTE keeps a snapshot of the operating system on the disc.  This      snapshot contains all the entry point names, types and locations of      all the modules (except type 8) that were included at generation time.      SNPSH will read this snapshot from the disc and dump it to a      mini-cartridge in 128 word records.       To run SNPSH from a terminal:      RU,SNPSH,ctu lu - FOR HP INTERNAL USE ONLY - 41 CRASH DUMP ANALYSIS CDA4,SNPSH,CDMP,TDMP      where ctu lu is the logical unit number of the cartridge tape unit to      which SNPSH directs its output.  After successful completion the      message:      SNAPSHOT WRITTEN TO CASSETTE      appears on the terminal.       In order to operate correctly, CDA4 requires a type 1 file which      contains the snapshot generated by SNPSH.  This file should be      obtained from the mini-cartridge created above using the FMGR command:      :ST,ctu lu,name::crn:1:-1,BN      where ctu lu is the logical unit number of the cartridge tape unit      where the SNPSH output is located, name is the name of the file to      contain the snapshot and crn is an optional cartridge reference number      on which name is to becreated.       The snapshot program need only be run once for a given generation,      whereasthe dump program must be run once for every system crash.      DUMP PROGRAM      !CDMP is an absolute program which dumps a crashed system to a      mini-cartridge.  !TDMP operates similarly, but dumps the system to a      magnetic tape.  The first 32K of physical memory, the system map, the      user map, the port A map and the port B map will be dumped.       !CDMP or !TDMP must first be put on a paper tape or a mini-cartridge      so that it can be loaded into memory by either the paper tape or      mini-cartridge ROM boot in the event of a system crash.  This is done      by using the FMGR command:      :DU,!CDMP,lu  ,BA      or      :DU,!TDMP,lu  ,BA         where lu # is the logical unit number of either the paper tape punch         or a cartridge tape unit.          When this is done, and the system crashes, the program can be brought         into memory by using the appropriate ROM boot.  The program begins at         address 77463B and ends at address 77677B, ie it is located right         before the ROM boot in high memory.  Consequently, the original 140         words of memory which the program replaces are lost.          To run the program once it is in memory, select no parity for the         terminal and place the mini-cartridge in the left CTU or ready the - FOR HP INTERNAL USE ONLY - 42 CRASH DUMP ANALYSIS CDA4,SNPSH,CDMP,TDMP         tape drive, as appropriate.  The terminal must be one which is         normally driven by DVR05.  The tape drive must be one which is         normally driven by DVR23.  Set the P-register to 2 (the beginning of         the dump program) and then set the S-register to the select code of         the terminal.  Press RUN and the program should execute.          A HLT 77 indicates a normal completion.  A HLT 42 indicates that an         error occurred trying to write to the CTU.  By pressing RUN after a         HLT 42 the dump program will be retried.  !TDMP also uses HLT 41 and         HLT 43 which are not recoverable.          In order to operate correctly, CDA4 requires a type 1 file which         contains the         crashed system.  Such a file can be obtained from the mini-cartridge         created above by using the FMGR command:                 :ST,lu,name::crn:1:257,BN         where lu is the logical unit number of the tape unit where the dump         program output is located, name is the name of the file to be created         to contain the crashed system and crn is an optional cartridge         reference number on which name is to be created.          The dump program must be run once for every system crash whereas the         snapshot program need only be run once for a given generation.          ANALYZE PROGRAM         INTRODUCTION         CDA4 is a program designed to work with one type 1 file containing the         crashed system's snapshot and any number of type 1 files containing         crashed systems.          The CDA4 commands are entered interactively at a terminal.  The         commands perform the following functions:         * Control CDA4 operation         * Examine specified memory locations of the crashed system         * List various system tables of the crashed system         * List specified system information     CDA4 COMMANDS     All the CDA4 commands are summarized in the following table.  This table     presents the commands in the same functinal groups in which they are     described.  - FOR HP INTERNAL USE ONLY - 43 CRASH DUMP ANALYSIS CDA4,SNPSH,CDMP,TDMP     FUNCTIONAL      GROUP COMMAND FUNCTION          CDA4 FI Specify crashed system file     OPERATION LL Change list device      PK Packed listing      ?? Request command information      DP Display input in octal, decimal,      ASCII and symbolic      EP Eject page if line printer      /E, EN, EX Terminate CDA4          MEMORY LM List memory      EXAMINATION TR Trace list      F/ Find a value in memory          TABLE ID List ID segment      EXAMINATION EQ List EQT      DR List device reference table      IN List interrupt table      TA List track assignment table      LI List entry point          SYSTEM DU Dump system      INFORMATION AN Analysis of system      MA Dump all four maps          SPECIAL DB Invoke DBUGR      OPTIONS WH Run WHZAT on the crashed system     Please note that the command structure, syntax rules and many of the     commands are identical to those of CMM3 and CMM4.      CDA4 OPERATION     To use CDA4 you simply run the program from a terminal.  It responds with     a request for a snapshot file and a prompt.  Upon entering the snapshot     file name, it reminds you that the first thing you should do is to specify     the file containing a crashed system by using the FI command.  It then     issues an equal (=) prompt, at which time you may enter any command.      When you run CDA4 it assumes the terminal which initiated CDA4 as the     default device used for command input, to log errors and to list output.      You may change the list device during operation of CDA4 with the LL     command.      CDA4 operation is terminated with a /E, EN or EX command.  - FOR HP INTERNAL USE ONLY - 44 CRASH DUMP ANALYSIS CDA4,SNPSH,CDMP,TDMP     RUNNING PROGRAM CDA4     To request CDA4 from your terminal, simply run CDA4 as follows:                   RU,CDA4,device     where device is the logical unit number for input of CDA4 commands,     logging of errors and default for listing.  The default is the logical     unit number of the device where CDA4 was scheduled.      CDA4 will respond with the message:      CDA4! THE RTE IV CRASH DUMP ANALYZE PROGRAM!      INPUT SNAPSHOT FILE NAME      =     A type 1 file containing the system snapshot should be specified using the     format:          =name[:[security][:crn]]     where name is the name of the type 1 file created by SNPSH as described     above, security is its optional security code and crn is its optional     cartridge reference number.      In the event of an error, an error message will be printed followed by the     message:          ENTER /E TO EXIT     and another prompt to enter the snapshot file.  To exit CDA4, input /E,     otherwise try to input the snapshot file name again.      Note that the snapshot file name cannot be /E.      When a correct snapshot file name has been entered, CDA4 prints the     message:      SPECIFY FILE CONTAINING CRASHED SYSTEM WITH FI COMMAND      =     The equal prompt indicates that you may enter any command.  The message     indicates that the first command entered should be an FI command to     specify the file containing the crashed system.      After entering an FI command, CDA4 responds with another equal prompt.  - FOR HP INTERNAL USE ONLY - 45 CRASH DUMP ANALYSIS CDA4,SNPSH,CDMP,TDMP     EXPLANATION OF COMMANDS     EP Eject Page if line printer     The EP command will do a top of form if the output LU is a line printer     and will space one line if the output LU is a terminal.      Format: EP     FI Specify the file containing the crashed system     You may specify the file name you wish to use as the file containing the     crashed system with the FI commnad.      Format: FI,namr     DU DUmp the system to the list device     The DU command will list 32K words of the crashed system's memory to the     list device.  The format of the output is 64 word sections in packed     format.      Format: DU     AN ANalysis of system     The AN command will list several system entry points, base page locations     and     tables.  In addition, it will trace several system lists.      The following entry points are given:     $OP - The last operator command entered.     $LIST - IF $LIST is non-zero, a list change was made, but the crash      occurred before another program could be dispatched.     $UNPE - If $UNPE is zero, no parity error occurred.     $PVCN - If $PVCN is non-zero, the crash was due to a JSB $LIBR call.     $CIC - Contents of $CIC (central interrupt controller) when crash      occurred.     $POWR - Contents of $POWR (power up/down entry) when crash occurred.     $WORK - Address of last ID segment that $LIST processed.     $LSTM - Addres of last $LIST caller     $LSTM+1 - Old status of last program moved     $LSTM+2 - Last $LIST function code.     $PETB - Physical page number of parity error     $PETB+1 - Logical parity error address     $PETB+2 - Map containing parity error     $PETB+3 - ID segment address if program     $PETB+4 - Partition number(s) if program     $DMS - DMS status at interrupt - FOR HP INTERNAL USE ONLY - 46 CRASH DUMP ANALYSIS CDA4,SNPSH,CDMP,TDMP     $DMS+1 - Interrupt system on (0) or off (1)     $CIC0+13B The last CLF xx instruction configured          The following base page locations are listed:          1660B-1672B Addresses for     1771B-1774B current EQT entry     1673B CHAN - current DMA channel number     1700B RQPI - current EXEC request number     1717B XEQT - ID segment address of currently executing program.     1720B XLINK - ID segment address of last executing program     The following tables are printed.      All ID segments and extensions     All equipment table entries     Interrupt table     Device reference table     $CLASS table     $RNTB table     Memory allocation table ($MATA table)     The following lists are traced:     SKEDD The schedule list     SUSP2 The general wait list     SUSP3 The memory suspend list     SUSP4 The disc suspend list     The device suspend list for each EQT entry     $ZZZZ The abort list     Format: AN or ANPK (for a packed listing)     MA Dump the four maps to the list device     The system map, user map, port A map and port B map can be listed with the     MA command.  The 32 words of each map will be printed in packed format.      Format: MA - FOR HP INTERNAL USE ONLY - 47 CRASH DUMP ANALYSIS CDA4,SNPSH,CDMP,TDMP     The following commands perform identically as in CMM3 and CMM4:     LL PK ?? DP /E EN EX LM TR F/     ID EQ DR IN TA LI          DB Invokes the DBUGR which allows you to set labels to relative      addresses and use some of the nicer listing options of DBUGR.      To exit DBUGR just use ESC P.          WH This will cause a WHZAT print out of the crashed system. The      usefulness of this should be quite obvious.           NOTE! NOTE! NOTE!           DEPENDING ON THE SEVERITY OF THE CRASHED SYSTEM THE 'WH' OPTION      MAY GIVE UNPREDICTABLE RESULTS!!! - FOR HP INTERNAL USE ONLY - 48 FILE RELATED UTILITIES SDLS4     +-----------------------------------------------------+------------------+   | | |   | FILE RELATED UTILITIES | CHAPTER 5 |   | | |     +-----------------------------------------------------+------------------+     5.1 SDLS4     PROCEDURE NAME:     SDLS4     PART NUMBER:        24999-16050     DESCRIPTION:         SDLS4 is a routine which will read information from CUPERTINO         distribution tapes (SDLS or MTLS format, see Appendix A) directly into         RTE FMP files.  It accepts absolute, relocatable, or source files, but         it does not read "DATA" files from the MTLS tapes.  SDLS4 consists of         two parts, a main program written in FORTRAN-IV to interact with the         operator, and a subroutine "GETRC"(ASMB) which control and reads the         mag tape, passing infomation records back to the main program for         processing.  SDLS4 requies an 8K background area in order to operate.         SDLS4 checks the break flag (BR,SDLS4) at each mag tape record.  If a         LOAD is in progress, the load file is purged and the tape set back to         the beginning of that file.      USAGE:         SDLS4 can be called by RU,SDLS4.  It requests the LU   of the mag tape         locks it, and rewinds the tape.  When it is ready, a meassage "TASK:"         is displayed and waits for the following commands to be entered:     COMMAND      DESCRIPTION     LABEL         Reads the tape label and prints it on the terminal     ??            Displays available SDLS4 commands     DIRECTORY     Searches the tape for all program ID blocks and creates a                   file suitable for dumpping to line printer.  The result is a                   directory of the tape, giving part number, revision number,                   type, and the tape file position number.  The list file NAMR                   will be requested by "LIST FILE:".  The list file may be                   non-disc file (type 0) or a disc file.      REWIND        Rewinds the tape - FOR HP INTERNAL USE ONLY - 49 FILE RELATED UTILITIES SDLS4     N             Prints current file position number on tape     LL            Changes log device.  The log device is initially set up to                   be the                   terminal from which the RU,SDLS4 command was entered.      LOAD          Loads a specific file on tape to disc.  The destination FMP                   NAMR                   is requested by "LOAD INTO FILE:".  The tape file ID (part                   number) or file position number(available from the directory                   output) is requested by "ENTER STOCK   OR FILE  ".  If the                   file number is given, a random search of the file is                   applied.  If the part number is given, the tape will be                   searched forward only.  A revision code may be specified                   along with the part number.  If it does not match what is on                   tape, a message "REV DESCRIPANCY" will be displayed.  In any                   case, the file is still loaded.  When the tape file is                   found, the ID and the destination file are logged on the log                   device in order that a record of transaction can be kept.                    The old files are overwritten if existing names are given as                   destination files.  This is reported on the log device.  The                   destination files may be non-disc files(type 0).      BATCH         Gets LOAD commands from an FMP file.  The format of the                   command file is as follows:                   file NAMR                   part number rev or file number                   file NAMR                   .                    .                    file NAMR                   part number or file number                   E                   The part number and revision must be 16 characters long with                   no trailing blanks and in the format:                       XXXXX-XXXXX RRRR                   The /E causes a tape to rewind and return to interactive                   mode.      UPDATE        Just like BATCH mode, except that it requires part number                   rev and not file number.  In this mode, SDLS4 will only load                   those files whose rev codes are more recent than that                   specified in the command file.  It will update the command                   file rev parameter to reflect the current rev, so that next - FOR HP INTERNAL USE ONLY - 50 FILE RELATED UTILITIES SDLS4                   month the same command file can be used to update.                    To pick up a file of unknown revision, use a rev code of                   A000.      END OR EXIT Exit from SDLS4     The list of error codes output by SDLS4 and their meaning.      CODE MEANING          0 End of tape reached     1 Checksum error on mag tape physical record     2 Checksum error on data record     3 illegal logical record type on mag tape(wrong format)     4 break flag was set     5 internal error     6 tape logical record size greater than physical record     7 illegal record size (wrong format)     8 illegal logical record size     9 internal error (GETRC)     10 internal error(GETRC)     11 internal error(GETRC)     12 data record size> 255     13 illegal program type(DATA or cartridge image)     14 record out of sequence     129 internal error (wrong position in buffer from GETRC) - FOR HP INTERNAL USE ONLY - 51 FILE RELATED UTILITIES JSAVE     5.2 JSAVE     PROCEDURE NAME:     JSAVE     PART NUMBER:        24999-16048     DESCRIPTION:         JSAVE will save a disc cartridge on to a mag tape with a cartridge         header and directory of files in the cartridge.  the tape format that         JSAVE generates is shown in APPENDIX B.          JSAVE uses some of the extended instructions of the MX computer If you         need to run JSAVE on a 2100 or earlier machine a library of MX         instructions(simulated for the 2100) is provided in the source file.          JSAVE will work on the following discs:                7900 / 7905 / 7906 / 7920 / 7925         USAGE:           &dD &d@ &dD &d@      ! D&dDisk&d@ = x, !      ! F&dDile&d@ = x, ! Parameters may be in any      ! I&dDnhibit&d@, ! order seperated by      RU,JSAVE, ! L&dDast trk&d@ = x,! commas (,)      ! M&dDag Tape&d@ = x,!      ! R&dDepeat&d@ = x, !      ! V&dDerify&d@, !      &dD! &d@" . . . " &dD !&d@                   NOTE:     Only the first letter of each option is necessary except for          quote strings then both quotes are needed to delimit the          string.           Equals signs(=) can be replaced with colons(:) if desired.          'RU,JSAVE' with no parameters will cause JSAVE to prompt for all         answers.  (As it did)         'RU,JSAVE, .  .  .' with any parameters will cause JSAVE to use         defaults for unspecified parameters.  A list of JSAVE parameters and         their defaults(if any) are described below.  - FOR HP INTERNAL USE ONLY - 52 FILE RELATED UTILITIES JSAVE         D&dDisk&d@ = x       DEFAULT: Ask operator for +CRN or -LU.  i.e.  NO          default either specify in run string or let JSAVE ask          you for it.          F&dDile #&d@ = x     DEFAULT: x = 0 which tells JSAVE to start at current          position.  Do not rewind tape on entry to program.           (NOTE: This is only true for the 'batch' mode.)         I&dDnhibit RW&d@     DEFAULT: Rewind Mag Tape OFF-LINE when done.  Specifing          'I' in the run string will inhibit this function when          JSAVE terminates.          L&dDast track&d@ = x DEFAULT: last track of the subchannel for the given          disc LU.           (NOTE: This need only be specified if the cartridge          mounted was mounted with other than the last track for          that subchannel.  i.e.  'MC,lu,xx' was used.  In          addition if the cartridge is currently mounted and the          last track was not specified JSAVE will use the last          track as given in the cartridge list not the physical          last track defined by the subchannel.)         M&dDag Tape&d@ = x   DEFAULT: x = 8         R&dDepeat&d@ = x     DEFAULT: x = 1.  'x' specifies the number of times this          disc LU will be saved on consecutive files on the tape.         V&dDerify&d@         DEFAULT: Verify NOT performed.           header.  e.g.           CR    42  LUO42     10:39 AM  MON.,  9  APR., 1979          NOTE: The default is ALWAYS put on the tape.  Comments          will be appended to the default.  This is true for the          interactive mode also.  - FOR HP INTERNAL USE ONLY - 53 FILE RELATED UTILITIES JSAVE          Some examples are given below.          RU,JSAVE,D=47,F=1,V,"SSK DEVELOPMENT"          This would save Disc CRN 47, start at file 1, verify, add 'SSK          DEVELOPMENT' to the default header and rewind off-line when done.          or         RU,JSAVE,D:47,I          This would save Disc CRN 47, start at the current position of the          tape, not do a verify, use the default header, and leave the mag          tape positioned between the double EOF after the file just          created.          ADDITIONAL:          (1)       JSAVE now locks the MT LU #.           (2)       JVRFY is now a subroutine to JSAVE, hence the program          "JVRFY" will be obsoleted.  - FOR HP INTERNAL USE ONLY - 54 FILE RELATED UTILITIES JRSTR     5.3 JRSTR     PROCEDURE NAME:     JRSTR     PART NUMBER:        24999-16049     DESCRIPTION:         JRSTR restores a disc cartridge from a mag tape saved by JSAVE.      USAGE:         JRSTR can be called by RU,JRSTR.  When JRSTR is ready, the following         qestions will be requested interactively:         MAG TAPE LU:       Enter lu   of the mag tape drive         MAG TAPE FILE:     Enter the file position that contains the cartridge          data to be restored.           Entering the file number 0 terminates JRSTR          procedure.           Entering a negative value causes to display all of          the file headers on mag tape.           JRSTR positions the tape to the requested file and          displays the header.  If it is the desired file,          type "YES"; otherwise, type "NO".          DISC LU:           Enter disc cartrdige lu   to restore.          Note: JRSTR now updates the cartridge number for RTE-II,III and IVA         operating systems.  If the cartridge number on the JSAVE tape is         already mounted, you will be prompted for a new cartridge number.          The following error messages can be returned from the subroutine which         does the update:      DCMC ERR NF LU not found in cartridge table      OV Internal error      NG Negative response to CRN prompt      ZE Zero response to CRN prompt - FOR HP INTERNAL USE ONLY - 55 FILE RELATED UTILITIES JVRFY     5.4 JVRFY     PROCEDURE NAME:     JVRFY     PART NUMBER:        24999-16163     DESCRIPTION:      NOTE! NOTE! NOTE! NOTE!               JVRFY WILL BE OBSOLETED DURING THE NEXT UPDATE CYCLE.                JSAVE AND JRSTR NOW CALL A SUBROUTINE 'JVRFY' FOR THE               VERIFY OPERATION THUS ALLOWING A CONTINUAL LOCK ON THE               MAG TAPE.  THIS PROGRAM IS SUPPLIED ONLY FOR BACKWARD               COMPATABLITY AND IS NOT USED BY ANY OF THE SOFTWARE IN               THIS KIT.          JVRFY compares the contents of a mag tape file against the contents of         a disc cartridge.  The mag tape must be in the following format: n         consecutive records with 6145 words per record(the first word of a         record must be the associated disc track number).  It terminates on         EOF mark on tape.          Since a JSAVE tape file contains a header record of 100 characters as         the first record, this record must be by-passed by a command CN,mag         tape lu,FR if JVRFY is to be called from a command.      USAGE:         JVRFY can be called by a command:         CN,mag tape lu,FR         RU,JVRFY,list lu  ,disc lu  , mag tape lu           JVRFY can be called from a program( e.g.JSAVE, JRSTR):         CALL EXEC (icode,JVRFY, list lu  ,disc lu  , mag tape lu  )         where :   list lu   = device for the message to be displayed                   disc lu   = lu number of the disc cartridge                   mag tape lu   = lu number of the mag tape drive                   icode = 9,10,23, or 24.  9 or 23 allows to retrieve                   additional information upon return from JVRFY using CALL                   RAMPAR(IPBUF).  - FOR HP INTERNAL USE ONLY - 56 FILE RELATED UTILITIES VERIF     5.5 VERIF     PROCEDURE NAME:     VERIF     PART NUMBER:        24999-16248     DESCRIPTION:          'VERIF' provides a means to verify a FMGR disc file to LU or file to          file or LU to LU.  It also allows checking of one large file to many          smaller files in case the file has been split for some reason.  Also          an octal and ASCII dump can be obtained on records that do not          compare.           If 'VERIF' senses an EOF on one file (or device) and not the other          file (or device) it will ask the user if he wants to continue the          comparision.  If the user responds with 'YE', VERIF will ask him for          the new disc file (or LU) to continue the comparision on.  The new          file is then compared to the other file from the its current          position.           Zero length records are ignored by VERIF.                  NOTE! NOTE! NOTE! NOTE!          VERIF can only compare a MAXIMUM of 128 words per record!      USAGE:      RU,VERIF,P1,P2,P3,P4           WHERE P1 = INTERACTIVE DEVICE LU  (DEFAULT=1)           P2 = LIST DEVICE LU  (DEFAULT=P1)           P3 = RECORD DUMP FLAG (DEFAULT: REPORT ERROR ONLY)      IF 'P3' IS NON ZERO AND IF AN ERROR OCCURS      AN OCTAL AND ASCII DUMP OF BOTH RECORDS      IS GIVEN.           P4 = CONTINUE TO DEOF FLAG(DEFAULT: 1 FILE)      WHEN COMPARING TWO MAG TAPES YOU MAY      SET THIS PARAMETER TO NON ZERO AND      VERIF WILL CONTINUE UNTIL A DEOF IS      ENCOUNTERED ON THE FIRST DEVICE. - FOR HP INTERNAL USE ONLY - 57 FILE RELATED UTILITIES FGETR     5.6 FGETR     PROCEDURE NAME:     FGETR     PART NUMBER:        24999-16053     DESCRIPTION:         FGETR reads JSAVE tape and provides disc directory listing or allowes         to transfer files from the tape to disc one at a time.      USAGE:         It can be called by RU,FGETR.  When it is ready, it will request         information interactively.      DIRECTORY LIST REQUEST:     MAG TAPE LU:       Enter lu   of the mag tape drive     DO YOU WISH     A DIRECTORY ?      Enter Yes     WHAT LU ?          Enter lu   of the listing device     MAG TAPE FILE:     Enter JSAVE tape file position which contains the                        desired cartridge directory.  FGETR positions the tape                        and displays the file header created by JSAVE followed                        by a question mark(?).  Enter "YES" if this is the file                        which contains the desired directory.      ANY MORE ?         Enter "NO" to terminate FGETR or "YES" to continue to                        another file or directory listing.      MAG TAPE LU:       Enter lu   of the mage tape drive     DO YOU WISH     A DIRECTORY ?      Type "NO"     FILE NAMR,     :        Enter NANR of the desired file on tape.  If the new                        NAMR is supplied, the file will be stored on disc with                        the new NAMR.      MAG TAPE FILE:     Enter JSAVE mag tape file position which contains the                        desired file NAMR.  FGETR positions the tape and                        displays the file header created by JSAVE followed by a                        question mark(?).  Enter "YES" if it is the tape file. - FOR HP INTERNAL USE ONLY - 58 FILE RELATED UTILITIES FGETR     ANY MORE ?         Enter "NO" to terminate FGETR or "YES" to continue to                        another file.      /E entered for any inquiry terminates FGETR.  - FOR HP INTERNAL USE ONLY - 59 FILE RELATED UTILITIES RXREF     5.7 RXREF     PROCEDURE NAME:     RXREF     PART NUMBER:        24999-16051     DESCRIPTION:         RXREF provides cross references of modules used by a specific program.         The cross reference listing contains four parts.  The first part         provides the listing of used modules with each module description such         as the name, the size, the entry points, and external references.  The         second part provides the listing of modules with each module's level         and references where it is used.  The third part provides the list of         entry point names with references to where they are defined and used.         The last part provides the unresolved external names and references         where they are used.      USAGE:         RXREF can be called by RU,RXREF,input lu,log lu, where input lu is the         LU where input will come from (terminal) and log lu is where the RXREF         output will be printed.  When RXREF is ready, a prompting character     COMMAND       DESCRIPTION     NAMR          Request to produce cross reference list for the relocatable                   binary NAMR     lu #          Request to produce cross reference list of the relocatable                   binary which is on the device specified by the logical unit.     2 spaces      Request to produce cross reference list of the relocatable                   binary in load-and go area.      control-D     Signifies that the last file request has been specified and                   request to start processing         NOTE: "LEVEL" refers to the structured programming concept.  If RXREF         sees a module which is not called from any other module, then it         assigns that module LEVEL 0.  The modules to which this module calls         are assigned LEVEL 1, and so on.  Levels are assigned by the maximum         depth from which they are called.  For example, if a utility         subroutine is called from various levels, its level would then be one         larger than the largest level number of any subroutine which calls it.         Occaionally, it is necessary for software to refer to levels above it.         That is , a module at level n refers to another module with a lower         level number.  In this case, RXREF simply gives up and assigns level - FOR HP INTERNAL USE ONLY - 60 FILE RELATED UTILITIES RXREF         number 100.      ERROR MESSAGES:      OPEN ERROR         File named could not be opened.  Cause of error is not                         printed.                          BAD COMMAND        Command is not recognized.  Type it                         again correctly.       READ ERROR         File-read or parity error.  File may be corrupt.       CHECKSUM           Bad checksum, or file is not relocatable binary.       ILL RECORD         Record type read not defined in relocatable binary.       ILL RECORD SEQUENCE                         Legal record sequence is always NAM first.       DUP MODULE NAME    Module of the same name has been seen before.       SYMBOL TALBLE OVERFLOW      MODULE TABLE OVERFLOW      NOT ENOUGH SPACE TO COMPUTE LEVEL NUMBER      WARNING:CR  OF FILE DOES NOT MATCH CR  USED--                         possible that RXREF is using the wrong file.  Check                         for correctness.  This situation is caused by use of                         on- off-line disc restore utilty in order to change                         the file system on a peripheral disc, without first                         dismounting old cartridge, or removing a cartridge and                         inserting a new cartridge.  - FOR HP INTERNAL USE ONLY - 61 FILE RELATED UTILITIES RXREF      SAMPLE RXREF OUTPUT           MODULE MODULE SIZE (OCTAL)      NAME MODULE IDENT. BPAG MAIN COMM     -------------------------------------------------------     FILE NAME: %MXLIB:: 215: 5: 20: 000 IS ON LU 17           AVMEM 7 FEB 74 -TLD-      00000 00104 00000 ENT= GLWAM GFWAM      EXT= EXEC           IFCHR 14 JAN 74 -TLD-      00000 00033 00000 ENT= IFCHR      EXT= .ENTR           ISCHR 14 JAN 74 -TLD-      00000 00043 00000 ENT= ISCHR      EXT= .ENTR           CVTNP 25 JAN 74 -TLD-      00000 00153 00000 ENT= CVTNP      EXT= .ENTR IFCHR           NAMFM 25 JAN 74 -TLD- FMGR NAMR PARSE      00000 00512 00000 ENT= NAMFM      EXT= .ENTR IFCHR ISCHR CVTNP           RDDSK 1 FEB 74 -TLD-      00000 00126 00000 ENT= RDDSK      EXT= EXEC .ENTR           RREAD 1 FEB 74 -TLD-      00000 00117 00000 ENT= RREAD      EXT= DCB4 .ENTR READG           RBINY 15 FEB 74 -TLD-      00000 00402 00000 ENT= RBIN RBILU  DCB RBLU      EXT= .ENTR RREAD READF EXEC           .L.G. 1 FEB 74 -TLD-      00000 00467 00000 ENT= DCB DCB4 READG OPNLG      EXT= .ENTR RDDSK EXEC     FILE NAME: XRXREF:: 2: 5: 27: 000 IS ON LU 2           RXREF 23 FEB '77 -LAW- -TLD- -KH-      00000 03622 00000 EXT= RBIN RBILU  DCB RMPAR      EXT= .ENTR OPNLG OPEN NAMFM      EXT= CLOSE FSTAT LOCF GLWAM      EXT= EXEC GFWAM RBLU REIO      END= 00001      TOTAL 00000 06247 00000 - FOR HP INTERNAL USE ONLY - 62 FILE RELATED UTILITIES RXREF      MODULE LEVEL MODULES WHERE USED     -------------------------------------------------------      .L.G. 4 RREAD RXREF      AVMEM 2 RXREF      CVTNP 3 NAMFM      IFCHR 4 CVTNP NAMFM      ISCHR 3 NAMFM      RXREF 1      NAMFM 2 RXREF      RBINY 2 RXREF      RDDSK 5 .L.G.      RREAD 3 RBINY      ENTRY DEFN-MOD MODULES WHERE USED     -------------------------------------------------------       DCB RBINY RXREF      CVTNP CVTNP NAMFM      DCB .L.G.      DCB4 .L.G. RREAD      GFWAM AVMEM RXREF      GLWAM AVMEM RXREF      IFCHR IFCHR CVTNP NAMFM      ISCHR ISCHR NAMFM      NAMFM NAMFM RXREF      OPNLG .L.G. RXREF      RBILU RBINY RXREF      RBIN RBINY RXREF      RBLU RBINY RXREF      RDDSK RDDSK .L.G.      READG .L.G. RREAD      RREAD RREAD RBINY      UNRESOLVED EXT MODULES WHERE USED     -------------------------------------------------------      .ENTR IFCHR ISCHR CVTNP NAMFM RDDSK RREAD RBINY .L.G. RXREF      CLOSE RXREF      EXEC AVMEM RDDSK RBINY .L.G. RXREF      FSTAT RXREF      LOCF RXREF      OPEN RXREF      READF RBINY      REIO RXREF      RMPAR RXREF      END OF CROSS REF - FOR HP INTERNAL USE ONLY - 63 FILE RELATED UTILITIES RXREF      INTERNAL TABLE FORMATS:      SYMBOL TABLE -- GROWS DOWNWARD FROM LWAM      WORD 7 - ADDRESS OF DEFINING MODULE ENTRY      WORD 6 - ADDRESS OF FIRST ENTRY IN USER-MODULE LIST      WORD 5 - ADDRESS OF NEXT ALPHA. SYMBOL TABLE ENTRY      WORD 4 - ADDRESS OF NEXT ALPHA. ENTRY IN MODULE-ENT LIST      WORD 3 - CHARACTER 5 OF NAME; FLAGS      WORD 2 - CHARACTERS 3 AND 4 OF NAME      WORD 1 - CHARACTERS 1 AND 2 OF NAME           USER-MODULE LIST -- GROWS DOWNWARD WITH THE SYMBOL TABLE      WORD 2 - ADDRESS OF NEXT ENTRY IN USER-MODULE LIST      WORD 1 - ADDRESS OF MODULE ENTRY REFERENCING THIS SYMBOL           MODULE-TABLE -- GROWS UPWARD FROM FWAM; LENGTH VARIES AS      THE NUMBER OF EXT'S IN A MODULE VARY      WORD N - ADDRESS OF S.T. ENTRY FOR EXT  N      :      :      WORD 8 - ADDRESS OF S.T. ENTRY FOR EXT  1      WORD 7 - NUMBER OF EXT'S FOR THIS MODULE      WORD 6 - NOT USED      WORD 5 - ADDRESS OF FIRST S.T. ENTRY IN MODULE-ENT LIST      WORD 4 - ADDRESS OF NEXT ALPHA. MODULE TABLE ENTRY      WORD 3 - CHARACTER 5 OF NAME; FLAGS      WORD 2 - CHARACTERS 3 AND 4 OF NAME      WORD 1 - CHARACTERS 1 AND 2 OF NAME - FOR HP INTERNAL USE ONLY - 64 FILE RELATED UTILITIES DXREF     5.8 DXREF     PROCEDURE NAME:     DXREF     PART NUMBER:        24999-16246     DESCRIPTION:          'DXREF' has a similar function to 'RXREF' but allows for selective          searching of modules, entry points, and external referances.  It also          gives the module number, NAM record info, program size, base page and          common allocations if used.      USAGE:      RU,RXREF,P1,P2,P3,P4,P5           WHERE P1 = INTERACTIVE DEVICE LU# (DEFAULT=1)      P2 = LIST DEVICE LU# (DEFAULT=P1)      P3 = PROGRAM INPUT LU# (DEFAULT=ASK OPERATOR)      OR P3-P5 = FMGR FILE NAME           IF 'P3' = "1!" SPECIAL LIST & SEARCH OPTIONS ARE INVOKED.(*)     AND      IF 'P4' = "RE" THESE OPTIONS WILL BE CONTINUALLY ASKED AS SPECIFIED      IN 'P5'.           P5 = "AL" ASK FOR ALL OPTIONS AGAIN. ( DEFAULT )      "LO" ASK ONLY FOR CHANGE TO LIST OPTION      "MO" ASK ONLY FOR SEARCH BY MODULE NAME      "EN" ASK ONLY FOR SEARCH BY ENTRY POINTS      "EX" ASK ONLY FOR SEARCH BY EXTERNALS                (*) P3 = 1! AND P4 NOT EQUAL TO "RE". THIS IS USEFUL WHEN SEARCHING      FOR ONE PARTICULAR MODULE, ENTRY POINT, OR EXTERNAL REFRENCE.      ALL FILTERS AND LIST OPTION ARE SET INITIALLY AND ARE      NOT ASKED AGAIN. THEREBY ALLOWING EASY SEARCHES OF MANY FILES      FOR A SPECIFIC PIECE OF INFORMATION.           IF P4 = RE ANOTHER FEATURE IS ENABLED. THE SAME FILE CAN BE LOOKED      AT AGAIN BY ENTERING A SINGLE COLON (:) INSTEAD OF A FILE NAME.      THIS ALLOWS SEARCHES THROUGH ONE PARTICULAR FILE FOR MANY DIFFERINT      PIECES OF INFORMATION. A NOTE OF CAUTION HOWEVER: A DOUBLE COLON      (::) WILL TERMINATE RXREF.           TO TERMINATE DXREF ENTER '::' OR '0' OR ZERO LENGTH RECORD. - FOR HP INTERNAL USE ONLY - 65 FILE RELATED UTILITIES DL     5.9 DL     PROCEDURE NAME:     DL     PART NUMBER:        24999-16244, AND 24999-16245     DESCRIPTION:          'DL' is a program which allows enhanced capabilities over the 'DL'          command in FMGR.  It also can give you more information and thus be          an aid in certian trouble shooting tasks.           'DL' has all of the filtering capabilities of the 'DL' command except          for filtering on block size and record lengths.  In addition 'DL' has          string searching capabilities within the file name, and special          listing options to make finding the files of interest very easy and          fast.           'DL' is supplied in two versions one which runs on RTE-IVB          (24999-16244) and one which runs on RTE-IVA and RTE-III          (24999-16245).           'DL' uses the memory behind the program space for data arrays.  The          larger the listing the more space it will need.  Increasing the size          by about 4 or 5 pages is usually adequate.      USAGE:      TO RUN TYPE RU,DL,(P1)[,(P2),(P3),(P4),(P5),(P6)]           * (P1)= FILE NAMR FILTER MAY INCLUDE SECURITY,CART.,TYPE      (SEE BELOW FOR EXTENSIONS TO THIS FILTER)           (P2)= LIST UNIT (DEFAULT YOUR CONSOLE)           P3 IS USED TO INVOKE SPECIAL LISTING OPTIONS TO DL.           (P3)= 'OF' LIST OFF. DO NOT LIST FILES.      (P3)= 'EN' LIST END OF DIRECTORY   FILES GIVEN BY 'P4'      (P3)= 'OP' LIST ONLY FILES THAT ARE OPEN      (P3)= 'PU' LIST FILES THAT HAVE BEEN PURGED - FOR HP INTERNAL USE ONLY - 66 FILE RELATED UTILITIES DL      P4 IS PRIMARILY USED TO DETERMINE THE OUTPUT FORMAT      OF DL. IT ALSO INVOKES SOME SPECIAL OPTIONS.           (P4)= NUMBER OF FILES TO BE LISTED IF P3 IS 'EN'(DEFAULT ALL)      (P4)= 'HE' TO HAVE AN EXPANDED HEADING PRINTED.      (P4)= 'FC' TO HAVE NUMBER OF FILES PRINTED      (P4)= 'BO' TO HAVE HEADING AND FILE INFO PRINTED      (P4)= 'SC' TO SCAN ALL SECURITY CODES ON A GIVEN PLATTER      (P4)= 'PU' TO PURGE ALL FILES LISTED      (P4)= 'DI' GIVES DIRECTORY TRACK, SECTOR, AND WORD OF THE FILE      P5 REVERSE FILTER FLAGS. THIS PARAMETER IS USED TO LIST      'EVERYTHING BUT' WHAT THE FILTER WOULD NORMALLY ALLOW      TO BE LISTED. 'P5' CAN BE ANY COMBINATION OF UP TO 3      REVERSE FLAGS.           e.g. 'RTRS' WOULD REVERSE THE EFFECT OF THE FILE TYPE      FILTER AND THE SECURITY CODE FILTER. 'RTRSRF'      WOULD BE THE SAME AS 'RA'.           (P5)= 'RF' REVERSE FILE NAME FILTER      (P5)= 'RS' REVERSE SECURITY CODE FILTER      (P5)= 'RT' REVERSE FILE TYPE FILTER      (P5)= 'RA' REVERSE ALL FILTERS           (P6)= 'AL' CHECK ALL CARTRIDGES MOUNTED IN THE SYSTEM (RTE-IVB ONLY)           * THE FILE NAME FILTER GIVES MANY OPTIONS TO THE USER OF DL.      THE MOST COMMONLY USED FORM IS SPECIFYING CERTAIN CHARACTERS TO      BE 'DON'T CARE' CHARACTERS. E.G. '--AB' WOULD GIVE YOU ALL FILES      WITH THE 3RD AND 4TH CHARACTERS 'AB' (5TH & 6TH CHARACTERS ARE      IMPLICITLY DON'T CARES). IN ADDITION, DL ALLOWS SEARCHING FOR      A STRING OF CHARACTERS ANYWHERE IN THE FILE NAME. THIS FEATURE      ALLOWS THE USER TO USE JUST A FEW 'KEY' SYMBOLS WHICH HE BELIEVES      MIGHT BE IN THE NAME HE'S LOOKING FOR. FOR EXAMPLE, A USER WANTS      TO FIND A BINARY CODED DECIMAL TO FLOATING POINT CONVERSION ROUTINE      HE WOULD JUST ENTER, FOR A FILE NAME FILTER, '+BCD' AND ALL THE FILES      WITH THE CHARACTER STRING 'BCD' WOULD BE DISPLAYED FOR HIM. ONE      OTHER NOTE, MULTIPLE STRINGS ARE ALLOWED AND DASHES(-) ARE STILL      USED FOR 'DON'T CARE' PLACE HOLDERS. SOME EXAMPLES FOLLOW.           FILTER RESULT      +A+B WILL FIND ALL FILES THAT HAVE AN 'A' FOLLOWED BY A 'B'      ANYWHERE IN THE FILE NAME.           +--AB OR WILL FIND ALL FILES THAT HAVE THE STRING 'AB' ANY-      --+AB WHERE IN THE 3RD THROUGH 6TH CHARACTER POSITION.           +A-B WILL FIND THE CHARACTER STRING "A(DON'T CARE)B" ANY-      WHERE IN THE FILE. - FOR HP INTERNAL USE ONLY - 67 FILE RELATED UTILITIES DL      NOTE: When entering the filter if '??' or 'HE' is entered a brief      summary to the scheduling parameters are given to the user.      If you need a file beginning with these characters just      supply any additional characters.           e.g. '??-' or 'HE:' will cause 'DL' to find these files.                PURGE OPTION:           WHEN USING THE PURGE OPTION IN DL A 'VETO' OPTION IS ALSO AVAILABLE.      WHEN INVOKED DL WILL REQUIRE A RESPONSE TO EACH FILE AS IT IS LISTED.      YOU THEN HAVE THE OPTION OF PURGING OR NOT PURGING THE FILE OR ABORTING      THE PROGRAM.           NOTE: TYPE ZERO(0) FILES ARE NOT PURGED WITH THIS OPTION.           ----------------------------------------------------------------------      ADDITONAL PROBLEMS NOT TO BE RESOLVED           WHEN ASKING FOR OPEN FILES ONLY (P3 ='OP') THE NUMBER OF EXTENTS      WILL NOT BE SHOWN. ANY OTHER TYPE OF LISTING WILL SHOW THE EXTENTS,      HOWEVER. THIS IS BECAUSE FMGR DOES NOT KEEP OPEN FLAGS ON EXTENTS,      ONLY ON THE MAIN FILE.      ---------------------------------------------------------------------- - FOR HP INTERNAL USE ONLY - 68 PERFORMANCE UTILITIES CLASS     +-----------------------------------------------------+------------------+   | | |   | PERFORMANCE UTILITIES | CHAPTER 6 |   | | |     +-----------------------------------------------------+------------------+     6.1 CLASS     PROCEDURE NAME:     CLASS     PART NUMBER:        24999-16055     DESCRIPTION:         CLASS disaplays the status of the class table for the specified class         number, list the contents of the class table, or clear the pending         class buffers for the specified class number.      USAGE: It can be called by RU,CLASS.  CLASS displays the available         commands and their description and waits for the user to enter a         command after the TASK:.      CLASS AVAILABE COMMANDS:     DISPLAY,n1,n2,lu   Displays status of the class table for class numbers n1                        through n2 on logical unit lu.  CLASS outputs the class                        number, possible owners, class number sequrity code,                        the number of requests, the total block length of the                        entry in the class table, the track option word, and                        the sector option word.      LIST,lu            Lists the contents of the class table on lu.      CLEAR              Clears pending class buffers.  The class number is then                        requested to be entered.      END                Terminates CLASS procedure.  - FOR HP INTERNAL USE ONLY - 69 PERFORMANCE UTILITIES SAMSZ     6.2 SAMSZ     PROCEDURE NAME:     SAMSZ     PART NUMBER:        24999-16178     DESCRIPTION:         SAMSZ provides a means to determine dynamically the amount of system         available memory (SAM) size at any time which allows you to:         Determine whether lack of SAM is a bottleneck to your system         Determine whether SAM is being left allocated, due to software bugs.          Determining how much SAM may be required for planned expansion of a         system.          --etc.          This program totals the size of all blocks of memory in the free list         to get repeated samples.  It prints the time of day for each sample,         the total amount of SAM available, and the largest block found.  This         last feature allows you to spot severe SAM fragmentation problems, if         any.          You can use the printed time-of-day to correlate the printout with         other events the system may be doing.          It must be run at the highest priority in the system, or there is the         potential problem of the list being re-linked during SAMSZ's sample,         with the consequence that SAMSZ may "go off the deep end."     USAGE:         SAMSZ can be scheduled by a command, ON,SAMSZ,LU         where LU = LU you want the printout to come out on.  It may be a TTY,         CRT, cassette, mag tape, lineprinter, etc.  Default is 1 - FOR HP INTERNAL USE ONLY - 70 PERFORMANCE UTILITIES SAMSZ         Print format is one line per sample, as shown below:      TIME: 76: 12: 58, 3207 WORDS, MAX BLK = 3207      ^ ^ ^ ^ ^      ! ! ! ! +--- largest block      ! ! ! ! (size in decimal)      ! ! ! +-------- available SAM, in words (decimal)      ! ! +--------------- time-of-day (minutes)      ! +----------------------- time-of-day (seconds)      +------------------------------- time-of-day (centoseconds)         SAMSZ can be scheduled for repeated samplings by:         *IT,SAMSZ,2,2 (program is to run every two seconds)         *ON,SAMSZ,NOW,1      TIME: 76: 14: 58, 3207 WORDS, MAX BLK = 3207      TIME: 76: 16: 58, 3207 WORDS, MAX BLK = 3207         Note: This program uses $OPSY to determine which operating system it's         in.  It uses cross-map instructions for examining tables when in a         mapped-memory RTE.          The SAM free-list head is not an entry point, so SAMSZ must access it         via an offset value.  This technique is regrettable, because it         implies that various versions and revisions of RTE may, from time to         time, change the offset value required.  One means for determining the         proper value is to dump about 400 (octal) words from the entry point         of $ALC and following.  Look for 77777 and count back about 3         locations.  Subtract $ALC's address from this address, and that's your         offset.  As a check, the word immediately preceding the correct         location should be negative.  You should run SAMSZ when the system is         first booted up, and before any SAM has been allocated.  It should         print the same number your system generation listing shows as the size         of SAM.  If the number is far too large, or SAMSZ loops endlessly, you         should abort it and check the offset carefully.          Note that SAMSZ, in conjunction with LGTAT, can be used to determine         whether either of the two most likely bottlenecks are affecting you.          To determine whether the availablability of disc swapping tracks is a         bottleneck, simply put LGTAT in the time list, running every few         seconds, and pass it parameters to print out only the number of         available tracks and largest free block of tracks.  Determine the         swap-track requirements for the largest programs you have scheduled at         the time, and be sure there are no samples printed with less than this         number available.  - FOR HP INTERNAL USE ONLY - 71 PERFORMANCE UTILITIES SAMSZ         Note: it is possible that these sampler programs may only be runnable         at times when the resources they monitor are available.  For example,         if the printout device is buffered, RTE will delay them until         sufficient SAM is available for printing.  It may be that SAM will         periodically be almost entirely allocated, then quickly be released         (say, due to a single, very large class-I/O request).  SAMSZ would         never "see" this condition if the printout terminal was buffered.          Similarly, if the availability of swap tracks is a bottleneck, the         utility should be locked into a partition during the duration of its         sampling.          Check the time of day printed by SAMSZ to see how closely the sample         period is maintained.  If necessary, modify the code so it locks         itself in memory.  - FOR HP INTERNAL USE ONLY - 72 PERFORMANCE UTILITIES MAPIO     6.3 MAPIO     PROCEDURE NAME:       MAPIO     PART NUMBER:          24999,16222     DESCRIPTION:         'MAPIO' displays the system configuration which includes the         following; logical unit number,equipment number,equipmnt         status,driver,driver name, select code, and subchannel number.      USAGE:         The following command would be used;               RU,MAPIO[,LIST]         Where List = list output device LU, default = LU 1     SAMPLE OUTPUT:           RTE-IV SYSTEM CONFIGURATION      ON SEP 17,1979 AT 14:50: 1           CONFIGURED MEMORY SIZE IS 256 K WORDS      TIME BASE GENERATOR IS IN S.C. 12           LU EQT S.CHNL S.C. EQT STATUS DRIVER DEVICE NAME LU           1 2 1 14 B S DV.00 RS232 TERMINAL 1      2 1 0 13 D DV.32 7906/20 DISC 2      3 1 1 13 D DV.32 7906/20 DISC 3      4 4 0 22 B S DV.02 TAPE PUNCH 4      5 5 0 15 DV.01 TAPE READER 5     104 ********** LU UNASSIGNED ********** 104     105 ********** LU UNASSIGNED ********** 105     106 33 0 76 DV.12 LINE PRINTER 106     107 34 0 77 DV.12 LINE PRINTER 107           EQT STATUS LEGEND:           D= DMA REQUIRED      B= AUTOMATIC OUTPUT BUFFERING USED      P= DRIVER PROCESSES POWER FAIL      S= DRIVER PROCESSES TIME-OUT      T= DEVICE HAS TIMED OUT - FOR HP INTERNAL USE ONLY - 73 PERFORMANCE UTILITIES SCB     6.4 SCB     PROCEDURE NAME:    SCB          PART NUMBER:       24999-16247          DESCRIPTION:                   THIS PROGRAM DUMPS THE SESSION CONTROL BLOCK (SCB) CONTENTS          FOR A SPECIFIED SESSION TO THE SESSION CONSOLE OR OTHER          DESIGNATED LIST DEVICE.              INSTRUCTIONS           SCB IS SCHEDULED AS FOLLOWS:           RU,SCB[,LIST[,SESID]]           WHERE:           LIST = DESTINATION LOGICAL UNIT FOR SCB LISTING      (DEFAULT IS SESSION CONSOLE)           SESID = SESSION IDENTIFIER FOR DESIRED SCB      (DEFAULT IS CURRENT SESSION)               ENVIRONMENT AND RESOURE REQUIREMENTS:           SCB OPERATES ONLY IN THE RTE-IV SESSION MONITOR ENVIRONMENT      AND REQUIRES THE FOLLOWING EXTERNAL SUBROUTINES/FUNCTIONS:           NAME DESCRIPTION      ---- -----------           IGETB BYTE GET UTILITY      MOVCA BYTE MOVE UTILITY      BLANC FILLS WORDS W BLANKS      JASC BINARY TO ASCII      GTSAD GETS SCB ADDRESS - FOR HP INTERNAL USE ONLY - 74 PERFORMANCE UTILITIES SCB     SAMPLE OUTPUT:           USER: POTT GROUP: SESUP      CURRENTLY LOGGED ONTO SYSTEM LU  52           -SCB- -----DECIMAL------      INDEX OCTAL UPPER LOWER WORD ASCII DESCRIPTION      ----- ------- ----- ----- ------ ----- -------------------------      3 000064 0 52 52 4 SESSION IDENTIFIER      4 000134 0 92 92 \ ACCT. DIRECTORY ENTRY        5 000074 0 60 60 < CAPABILITY LEVEL      6 000000 0 0 0 ERROR MNEMONIC      7 000000 0 0 0 ERROR MNEMONIC      8 000000 0 0 0 ERROR MNEMONIC      9 000000 0 0 0 ERROR MNEMONIC      10 000000 0 0 0 CPU USAGE      11 015566 27 118 7030 v CPU USAGE      12 007670 15 184 4024 USER ID      13 000013 0 11 11 GROUP ID      14 000017 0 15 15 DISC LIMIT      15 177734 255 220 -36 - SST LENGTH      16 177777 255 255 -1 SST SPARE      . . . . . .      . . . . . .      27 177777 255 255 -1 SST SPARE      28 177777 255 255 -1 SST SPARE      29 064405 105 5 26885 i SYS LU 106 / SES LU  6      30 021042 34 34 8738 "" SYS LU  35 / SES LU  35      31 022044 36 36 9252 $$ SYS LU  37 / SES LU  37      32 006415 13 13 3341 SYS LU  14 / SES LU  14      33 031400 51 0 13056 3 SYS LU  52 / SES LU  1      34 000401 1 1 257 SYS LU  2 / SES LU  2      35 001002 2 2 514 SYS LU  3 / SES LU  3      36 013026 22 22 5654 SYS LU  23 / SES LU  23      37 002405 5 5 1285 SYS LU  6 / SES LU  6      . . . . . .      . . . . . .      51 010421 17 17 4369 SYS LU  18 / SES LU  18      52 177770 255 248 -8 - DISC CAPACITY      53 000027 0 23 23 EXIST/PRIV./ACTIVE/LU 23      54 100016 128 14 -32754 ADDED/PRIV./ACTIVE/LU 14      55 100045 128 37 -32731 % ADDED/PRIV./ACTIVE/LU 37      56 040013 64 11 16395 @ EXIST/GROUP/ACTIVE/LU 11      57 040034 64 28 16412 @ EXIST/GROUP/ACTIVE/LU 28      58 040041 64 33 16417 @! EXIST/GROUP/ACTIVE/LU 33      59 140043 192 35 -16349   ADDED/GROUP/ACTIVE/LU 35      60 000000 0 0 0 DISC SPARE      61 000000 0 0 0 DISC SPARE      62 000000 0 0 0 DISC SPARE      63 000000 0 0 0 DISC SPARE - FOR HP INTERNAL USE ONLY - 75 PERFORMANCE UTILITIES SAM     6.5 SAM     PROCEDURE NAME:     SAM     PART NUMBER:        24999-16227     DESCRIPTION:         THIS ROUTINE EXAMINES CONTENTS OF THE SYSTEM AVAILABLE MEMORY (SAM)         BUFFER FOR RTE 4.  IT DOES THIS BY TRACING OUT THE FOLLOWING LISTS:         1) FREE MEMORY  ORIGINAL LIST POINTER FOUND IN THE ENTRY POINT $PNTR          IN THE $ALC PROGRAM.          2) CLASS I/O.   LISTS MAY ORIGINATE FROM A POINTER IN ANY ONE OF THE          LOCATIONS IN THE CLASS I/O TABLE ($CLAS).          3) EQT LISTS.   AN EQT LIST BEGINS WITH A POINTER IN THE EQT LINK WORD          (WORD 1) OF ANY ENTRY IN THE EQT TABLE.          4) REENTRANT I/O          STARTING WITH A SINGLE POINTER (NEAR $REIO IN EXEC4) A          LIST OF RE-ENTRANT (AND SOME NONREENTRANT) I/O MAY BE          TRACED.          5) TURN-ON CHARACTER STRINGS          STARTING FROM LCOATION $STRG IS A LIST OF THE          CHARACTER STRINGS BEING PASSED AS TURN-ON PARAMETERS.         6) LU LISTS     AN LU LIST BEGINS WITH A BUFFER POINTER IN THE 2ND          HALF OF THE DEVICE REFERENCE TABLE.          7) DS TABLES    LOCATION #FWAM IN THE RES PROGRAM POINTS TO THE          DISTRIBUTED SYSTEMS TABLES AND VECTORS WHICH CONSIST          OF:          TRANSACTION CONTROL BLOCK(TCB)          TRANSACTION STATUS TABLE(TST)          NETWORK ROUTING VECTOR(NRV).           NOTE: IF YOU DO NOT HAVE DISTRIBUTED SYSTEMS THE LOADR MAY          GIVE YOU UNDEFINED EXTERNAL ERROR DUE TO #FWAM,#SAVM          DECLARED AS EXTERNALS BY THIS PROGRAM.  IF THIS OCCURS          YOU WILL NEED TO 'FORCE LOAD' SAM ALLOWING THE          UNDEFINED EXTERNALS NOT TO BE RESOLVED.          8) SCB          IF THE SESSION MONITOR IS IN YOUR SYSTEM IT ALSO          ALLOCATES SOME SAM.  - FOR HP INTERNAL USE ONLY - 76 PERFORMANCE UTILITIES SAM          NOTE: THIS TOO CAN CAUSE UNDEFINED EXTERNAL $SMEM UNLESS          RTE4B IS INSTALLED.  RESOLVE THIS PROBLEM AS GIVEN          ABOVE FOR DS TABLES.          9) CLASS TABLE  THOUGH ITS NOT PART OF THE BUFFER, THIS ROUTINE          RETURNS THE ENTIRE CLASS TABLE TO THE CALLER IN CASE          HE WANTS TO LIST IT.           NOTE: TO LOAD SAM YOU MUST SPECIFY ACCESS TO SSGA AREA.      USAGE:         NORMAL TURN-ON IS:          :RUN,SAM,LU,OPTION          WHERE:          LU =THE DESIRED LIST DEVICE.           (LIST DEVICE IS UNBUFFERED DURING SAM PRINTOUT.)          OPTION= "CL" TO GET A CLASS TABLE LISTING AFTER THE BUFFER LISTING.           OPTION= "IH" TO GET A SUMMARY OF SAM USAGE WITHOUT MAP PRINTOUT.           ON,SAM,6,CL DOES IT ALL ON THE LINE PRINTER.           HINT:  IF YOU SUSPECT SYSTEM AVAILABLE MEMORY IS CLOGGED.  DON'T          FORGET TO RUN SAM WITH THE 'IH' OPTION.  EG.  :RUIH,SAM.           THIS WILL INSURE THAT SAM WILL NOT USE A STRING BUFFER IN          SYSTEM AVAILABLE MEMORY WHICH MAY PREVENT 'SAM' FROM RUNNING. - FOR HP INTERNAL USE ONLY - 77 APPENDIX CUPERTINO DISTRIBUTION TAPE FORMAT     +-----------------------------------------------------+------------------+   | | |   | APPENDIX | CHAPTER 7 |   | | |     +-----------------------------------------------------+------------------+     7.1 CUPERTINO DISTRIBUTION TAPE FORMAT      REEL 1      I------------------I      I TAPE LABEL I --> contains the reel information: rev, date,      I I reel  , title, etc.      I------------------I      I TAPE MARK I      I------------------I      I DIRECTORY I --> only on the first reel: contains      I------------------I information for all files on library.      I TAPE MARK I (not currently supplied).      I------------------I      I PROGRAM 1 I --> the 1st record is the ID block      I------------------I      I TAPE MARK I      I------------------I      I . I      I . I      I------------------I      I PROGRAM n I      I------------------I      I TAPE MARK I      I------------------I      I TAPE MARK I --> End of logical tape      I------------------I      I - - - - I      I - - - - I      REEL 2 12 words<=all physical record<=1024 words                     I------------------I      I TAPE LABEL I 1st word of a record=character count of      I------------------I the record      I TAPE MARK I      I------------------I last word of a record = record checksum      I PROGRAM n+1 I      I------------------I - FOR HP INTERNAL USE ONLY - 78 APPENDIX CUPERTINO DISTRIBUTION TAPE FORMAT      I TAPE MARK I      I------------------I      I . I      I . I      I------------------I      I PROGRAM n+m I      I------------------I      I TAPE MARK I      I------------------I      I PN,REV=999...99 I --> Only on the last reel      I------------------I      I TAPE MARK I      I------------------I      I TAPE MARK I      I------------------I      I - - - I      I - - - - - I - FOR HP INTERNAL USE ONLY - 79 APPENDIX JSAVE/JRSTR TAPE FORMAT     7.2 JSAVE/JRSTR TAPE FORMAT      I-------------I      I I A TAPE FILE      I I      I FILE 1 I I---------------------I      I I I HEADER I      I I I 100 CHARACTERS I      I-------------I I---------------------I      I I I track   I I      I FILE 2 I I---------I I -->6145 OR      I I I DIRECTORY TRACK I 8193 WORDS      I I I---------------------I (1 TRACK)      I-------------I I track   I I      I . I I---------I I --> 6145 OR      I . I I FILE TRACK 1 I 8193 WORDS      I . I I---------------------I - FOR HP INTERNAL USE ONLY - 80                                 Table of Contents     1 SUMMARY OF PARTS . . . . . . . . . . . . . . . . . . . . . . . . . 1     2 DEBUGGING AIDS . . . . . . . . . . . . . . . . . . . . . . . . . . 3     2.1 CMM3, CMM4 AND CMMM . . . . . . . . . . . . . . . . . . . . . 3  2.2 PATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8  3 DATA COMMUNICATIONS DEBUGGING UTILITIES . . . . . . . . . . . . . . 9  3.1 DSINF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9  3.2 NDTDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20  3.3 TRC65,DRT65 . . . . . . . . . . . . . . . . . . . . . . . . . 22  3.4 SLCIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35  4 CRASH DUMP ANALYSIS . . . . . . . . . . . . . . . . . . . . . . . . 41  4.1 CDA4,SNPSH,CDMP,TDMP . . . . . . . . . . . . . . . . . . . . 41  5 FILE RELATED UTILITIES . . . . . . . . . . . . . . . . . . . . . . 49  5.1 SDLS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49  5.2 JSAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52  5.3 JRSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55  5.4 JVRFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56  5.5 VERIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57  5.6 FGETR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58  5.7 RXREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60  5.8 DXREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65  5.9 DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66  6 PERFORMANCE UTILITIES . . . . . . . . . . . . . . . . . . . . . . . 69  6.1 CLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69  6.2 SAMSZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70  6.3 MAPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73  6.4 SCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74  6.5 SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76  7 APPENDIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78  7.1 CUPERTINO DISTRIBUTION TAPE FORMAT . . . . . . . . . . . . . 78  7.2 JSAVE/JRSTR TAPE FORMAT . . . . . . . . . . . . . . . . . . . 80 - FOR HP INTERNAL USE ONLY - iii