CDA: The crash dump analyzer program has been modified to create and read from disk rather that tape. The program will run identically to the original version and will still respond to all of the original command lines described in the DECs IAS System Management Guide. However, if a comma is placed after the output file specification, CDA will now create a binary copy of the crash tape. The file will have a default name of SY:BINARY.CDA. The file can be used as an input file by placing it after the equal sign in the command line. For example: PDS> MC CDA DR0:,=/ATL will create the files DR0:ANALYSIS.LST and BINARY.CDA. Here the equal sign is optional. The binary file can be copied or transferred via DECNET, if desired. To use the binary file: PDS> MC CDA =BINARY.CDA/SRQ This command will open BINARY.CDA, analyze it, and spool the output file [1,4]ANALYSIS.LST. The files on this tape on [302,204] are intended to be applied to the IAS 3.1 (autopatch E) crash dump analyzer CDA. If you have DECnet source, the NDAXFR, NDADIO, and NDAFIO sliper files can be run on your source code. All modified object files have also been included. This implementation contains IAS Software dispatch seq # 2.1.8.1 . To implement the sliper files on your source code, issue the following command: PDS> SUB [302,204]SLIPER If you have DECnet source, then: PDS> SUB [302,204]SLIPERNDA Else: PDS> @NDACOPY If you don't have IAS source, the object files will have to be manually copied to [11,103]. No command files are provided. Also, the sliper files for CDAODL, and CDATKB will have to be executed manually. Build the program using the new command file and ODL file on [11,103]. file and odl file on [11,103]: PDS> MC TKB @TKB103 Please refer all questions, comments and/or gratuities to: Fred A. Lien C/O The Boeing Company, M.S. 6F-21 P. O. Box 3707 Seattle, Washington 98124