Document revision date: 19 July 1999

**************************** ENTRY 82. **************************** ERROR SEQUENCE 1077. LOGGED ON SID 04FFFFFF MACHINE CHECK 30-MAR-1998 20:55:17.41 KA86 REV# 255. SERIAL# 4095. MFG PLANT 7. EHMSTS 40000802 VMS ERROR CODE = EBOX MICRO TRAP VECTOR = 08 (X) EHM ENTERED EVMQSAV 00000004 VIRTUAL ADDRESS FOR EBOX PORT _ REQUESTS EBCS 00000800 ECS PARITY ERROR EDPSR 00000000 CSLINT 04183D1F C BUS ADDRESS = 1F (X) C BUS DATA = 3D (X) INTERRUPT PRIORITY REQUEST = 8. INTERNAL SOURCE I/O ADAPTER = 0. INTERVAL TIMER IBESR 00004000 UOP SEL = IBOX REGISTER SELECT UTPR <2:0> = EBOX PORT ENABLE ETRAP EBXWD1 00000004 TOP OF "SP STACK" _ CONTENT IS ONE OF THE LAST _ LONGWORDS WRITTEN TO MBOX EBXWD2 7FF593D0 TOP OF "SP STACK" MINUS ONE _ CONTENT IS ONE OF THE LAST _ LONGWORDS WRITTEN TO MBOX VASAV 7FF593F8 VIRTUAL ADDRESS FOR OP FETCH _ PORT REQUEST ADDRESS _ CALCULATION FOR OPERAND _ PRE-FETCH AND RESULT DELIVERY VIBASAV 0000E7FF VIRTUAL ADDRESS OF NEXT IBUF _ PORT REQUEST TO FILL IBUFFER ESASAV 0000E7F2 PC OF INSTRUCTION DURING EBOX _ EXECUTION AND RESULT STORAGE ISASAV 0000E7F2 PC OF INSTRUCTION WHICH VA _ CALCULATION UNIT IS DOING ADDRESS _ CALCULATION OR OPERAND PRE-FETCH _ OR IS PASSING OPERAND DATA CPC 0000E7F4 PC OF INSTRUCTION IN _ DECODE UNIT MSTAT1 84006004 C0 TAG MISS BLOCK HIT ABUS ADAPTER = 0. WORD COUNT = 0. CYCLE TYPE = READ REGISTER DEST CP = EBOX MSTAT2 00004F00 DIAGNOSTIC STATUS FROM SBIA _ RD COM/MSK <3:0> = F (X) _ RD DAT L/S <1:0> = 0 (X) _ ABUS BAD DATA CODE PAMM DATA = ARRAY #0.,SLOT #1. MDECC 00066200 (* DATA NOT VALID *) MERG 04000100 MEMORY MANAGEMENT ENABLE CSHCTL 00000003 CACHE 0 ENABLE CACHE 1 ENABLE MEAR 0000007C PHYSICAL ADDRESS IN PA LATCH AT TIME OF ERROR = 0000007C MEDR 0000001F DATA WORD USED DURING ERROR FBXERR FFFFFFFF (* DATA NOT VALID *) CSES 1BD73E01 CS CODE = EBOX CONTROL STORE PARITY ERROR CS SYNDROME = 3E (X) CS ADDRESS = 1BD7 (X) ERROR PC 0000E7F2 ERROR PSL 03C00004 Z-BIT INTERRUPT PRIORITY LEVEL = 00. PREVIOUS MODE = USER CURRENT MODE = USER IOA ES 00000000 (* DATA NOT VALID *) AN/ER/INC=MACH ERR:ERRLOG.SYS_31MAR1998/ENT=S=82/OUT=DP.

Memory Error Entries Example

Memory error log entries consist of two types: fatal and nonfatal. A nonfatal memory error indicates that a single bit has failed within a memory location, and that the ECC (error code correctable) was able to compensate for the error and correct the data. A fatal error indicates that multiple bits were erroneous, and that the ECC could not correct the data.

Both the fatal and nonfatal memory entries are similar in their format. The memory error log reports can be divided into two logical areas of information. The first section of a memory error log report is the identification area. The second section contains memory controller-specific information. This data represents the information contained within the memory controller registers at the time of the memory error. Bit-to-text translation of the registers is performed and then listed on the right side of the report.

**************************** ENTRY 7. **************************** ERROR SEQUENCE 4. LOGGED ON SID 03003700 MEMORY ERROR, 6-MAR-1998 10:11:34.70 KA730 REV# 0. MIC# 55. CSR0 00166200 ERROR SYNDROME = 7F CORRECTED ERROR, BIT #31. ARRAY #1. IN ERROR CSR1 18000000 MEMORY MAPPING ENABLE ENABLE "CRD" REPORTING CSR2 8100000F MEMORY SIZE = 2048.K 64K RAMS PRESENT **************************** ENTRY 91. **************************** ERROR SEQUENCE 342. LOGGED ON SID 0138207A FATAL MEMORY ERROR, 4-MAR-98 08:16:45.20 KA780 REV# 7. SERIAL# 122. CONTROLLER AT TR #5. PRTCFNG 00000040 ADAPTER IS MULTI-PORT MEMORY PORT NUMBER = 0. PRTCR 00000003 MASTER INTERRUPT ENABLE PORT INTERFACE INTERRUPT ENABLE RAM COUNT 0. PCSR 07870003 ERROR INTERRUPT ENABLE IVDTCR 01870001 INVALIDATE CACHE DEVICE ID = 0. 8. ARRAY BOARD(S) PRESENT MEMORY BASE ADDRESS = 6144.K AER 16A70005 ERROR SYNDROME = 05 RDS ERROR ARRAY #6. IN ERROR ARRAY BANK #1. IN ERROR ERROR LOG REQUEST CSR0 0000C2C8 MEMORY CONTAINS VALID DATA PORT #2. POWERED DOWN PORT #3. POWERED DOWN ERROR INTERRUPT FROM PORT #1. PORT #2. OFFLINE PORT #3. OFFLINE CSR1 0000380A PORT #0. CONNECTED TO AN SBI PORT #1. CONNECTED TO AN SBI PORT #2. NOT PRESENT PORT #3. NOT PRESENT INVALIDATION MAP PRESENT PORT #0. INVALIDATION ACK RECEIVED PORT #1. INVALIDATION ACK RECEIVED MAT 0000C000

Nonfatal and User Bugchecks Entry Example

The following example shows a fatal bugcheck. Nonfatal and user bugcheck reports have the same format. These reports consist of three sections: identification, bugcheck reason and process information, and system register information.

Error Log Report Generator Version 7.1 ******************************* ENTRY 25. ******************************* ERROR SEQUENCE 15. LOGGED ON: CPU_TYPE 00000002 DATE/TIME 22-JUL-1998 13:43:48.96 SYS_TYPE 00000003 SYSTEM UPTIME: 90 DAYS 00:07:26 SCS NODE: LSR3 VAX/VMS V7.1 FATAL BUGCHECK SYS_TYPE = 03 OPERATOR, Operator requested system shutdown PROCESS NAME Aut PROCESS ID 00010004 ERROR PC 00000000 000304A0 Process Status = 08000000 00001F03, SW = 03, Previous Mode = USER System State = 00, Current Mode = KERNEL VMM = 00 IPL = 31, SP Alignment = 8 STACK POINTERS KSP 00000000 7FF95F08 ESP 00000000 7FF9A000 SSP 00000000 7FFA04C0 USP 00000000 7FE63B80 GENERAL REGISTERS R0 00000000 00000001 R1 00000000 00000000 R2 FFFFFFFF 805ED100 R3 00000000 00000001 R4 00000000 00000001 R5 00000000 00000001 R6 00000000 00000000 R7 00000000 00000000 R8 00000000 7FFA05F8 R9 00000000 7FFA0800 R10 00000000 00000000 R11 00000000 7FFBE3E0 R12 00000000 00000004 R13 00000000 00010100 R14 00000000 02080061 R15 FFFFFFFF 80403C30 R16 00000000 00000474 R17 00000000 00004000 R18 00000000 00000000 R19 00000000 00000000 R20 FFFFFFFF 805C04B6 R21 00000000 00800000 R22 FFFFFFFF 804308E8 R23 88000000 E4000003 R24 00000000 00000000 R25 00000000 00000001 R26 00000000 00000002 R27 00000000 00000002 R28 00000000 00030440 FP 00000000 7FF95F10 SP 00000000 7FF95F08 PC 00000000 000304A0 PS 08000000 00001F03 SYSTEM REGISTERS PTBR 00000000 000005D3 Page Table Base Register PCBB 00000000 00B98080 Privileged Context Block Base PRBR FFFFFFFF 805C0000 Processor Base Register SCBB 00000002 00000000 System Control Block Base SISR 00000000 0000017B Software Interrupt Summary Register ASN 00000000 00000000 Address Space Number ASTSR_ASTEN 00000000 0000003F AST Summary/AST Enable AT 00000000 0000000F Absolute Time

Unknown Entries Examples

The following examples are sample reports for error log entries of unknown type. Each report has an identification section and an error log record section. The error log record section contains two types of records: interpretable and noninterpretable. If ERROR LOG can interpret the fields of the record, the utility gives the name of the field, its contents, and interprets what the field is. If the utility cannot interpret the fields of a record, it gives the longword value of the field and its contents in hexadecimal format.

**************************** ENTRY 95. **************************** ERROR SEQUENCE 2. LOGGED ON SID 03003600 "UNKNOWN DEVICE" ENTRY, 4-MAR-98 10:12:12.44 KA730 REV# 0. MIC# 54. ERROR LOG RECORD ERF$L_SID 03003600 SYSTEM ID REGISTER ERL$W_ENTRY 0062 ERROR ENTRY TYPE EXE$GQ_SYSTIME C9764980 008C2F30 64 BIT TIME WHEN ERROR LOGGED ERL$GL_SEQUENCE 0002 UNIQUE ERROR SEQUENCE = 2. UCB$W_STS 0110 DEVICE STATUS UCB$B_DEVCLASS 42 DEVICE CLASS = 66. UCB$B_DEVTYPE 42 DEVICE TYPE = 66. UCB$W_UNIT 0000 PHYSICAL UNIT NUMBER = 0. UCB$W_ERRCNT 0001 UNIT ERROR COUNT = 1. UCB$L_OPCNT 00000001 UNIT OPERATION COUNT = 1. ORB$L_OWNER 00010004 OWNER UIC = [001,004] UCB$L_DEVCHAR 0C440007 DEVICE CHARACTERISTICS UCB$B_SLAVE 00 DEVICE SLAVE CONTROLLER = 0. DDB$T_NAME 41515403 00000000 00000000 00000000 /.TQA............/ LONGWORD 1. 00000008 LONGWORD 2. 00000007 LONGWORD 3. 00000502 LONGWORD 4. 04000000 LONGWORD 5. 00010000 LONGWORD 6. 00000000 LONGWORD 7. 00000080 LONGWORD 8. 00000000 LONGWORD 9. 00000000 **************************** ENTRY 161. **************************** ERROR SEQUENCE 213. LOGGED ON SID 070001FF "UNKNOWN ENTRY", 4-MAR-98 11:35:15.73 UVAX1 REV# 255. MIC# 1. ERROR LOG RECORD ERF$L_SID 070001FF SYSTEM ID REGISTER ERL$W_ENTRY 0008 ERROR ENTRY TYPE EXE$GQ_SYSTIME 89953F20 008C3E2A 64 BIT TIME WHEN ERROR LOGGED ERL$GL_SEQUENCE 00D5 UNIQUE ERROR SEQUENCE = 213. LONGWORD 1. 00000001 /..../ LONGWORD 2. 00410001 /..A./

Example of a Brief Report

The following example shows a report generated with the /BRIEF qualifier.

Error Log Report Generator Version 7.1 **************************** ENTRY 1. **************************** ERROR SEQUENCE 11. LOGGED ON: SID 08000000 DATA/TIME 18-JUL-1998 22:53:41.57 SYS_TYPE 00000000 DEVICE ERROR KA630 RD32 SUB-SYSTEM, UNIT _RICHIE$DUA0: DMA ADDRESS 000000 DSECT CHEAD DHEAD CCYL DCYL SCNT 06 14 14 9C 9C 01 RTCNT CSTAT MODE DSTAT TERM ISTAT F0 08 C0 B2 BD 28 CMD 56

11.1 INSTALL Description

Known file entries last only while the system is operating. If the system is shut down or fails for any reason, you must reinstall all known images after the system is rebooted. For this reason, you are encouraged to include additional INSTALL commands for selected images in the site-specific command procedure SYS$MANAGER:SYSTARTUP_VMS.COM.

11.2 INSTALL Usage Summary

Use the Install utility (INSTALL) to enhance the performance of selected executable and shareable images, to assign enhanced privileges to images, and to support user-written system services. The system stores the name and attributes of installed images on known file lists.

Format

INSTALL [command]

Parameter

command

Specifies an INSTALL command. This parameter is optional. If no command is specified, the utility displays its prompt and waits for command input.

Description

To invoke INSTALL, enter the DCL command INSTALL at the DCL prompt as follows:

$ INSTALL

The utility responds with the following prompt:

INSTALL>

You can then perform INSTALL operations by entering the appropriate INSTALL commands.

To exit from the Install utility, enter the EXIT command at the INSTALL> prompt or press Ctrl/Z. Either method returns control to the DCL command level.

Alternatively, you can enter a single INSTALL command on the same line as the command that invokes the utility, for example:

$ INSTALL LIST/FULL SYS$SYSTEM:LOGINOUT

This section describes and provides examples of the INSTALL commands. The following table summarizes the INSTALL command functions.

Command	Function
ADD	Synonym for the CREATE command
CREATE	Installs the specified image as a known image
DELETE	Synonym for the REMOVE command
EXIT	Exits from INSTALL
HELP	Describes how to use INSTALL
LIST	Displays a description of each specified known image, global sections, and the addresses of known image data structures
PURGE	Deletes all known images installed without the /NOPURGE qualifier
REMOVE	Deletes a known image
REPLACE	Associates a known image with the latest version of the image file or modifies the attributes of an installed image

ADD

Installs the specified image file as a known image. The ADD command is a synonym for the CREATE command. See the CREATE command for details.

Installs the specified image file as a known image. The CREATE command is a synonym for the ADD command.

Requires the CMKRNL privilege. Also requires the SYSGBL privilege to create system global sections and the PRMGBL privilege to create permanent global sections.

Format

CREATE file-spec

Parameter

file-spec

Names the file specification of an image to be installed as a known image. The file specification must name an existing executable or shareable image, which must have been linked with the /NOTRACEBACK qualifier. If you omit the device and directory specification, the default SYS$SYSTEM is used. The default file type is .EXE.

The highest existing version of the file is used by default. However, you can specify another version of the file as the known version of the image. Even if other versions of the file exist, the version that you specify will be the version that satisfies all known file lookups for the image.

Qualifiers

/ACCOUNTING

/NOACCOUNTING (default)

Enables image-level accounting for the specified image even if image accounting is disabled (by using the DCL command SET ACCOUNTING/DISABLE=IMAGE). When image accounting is enabled on the local node, it logs all images, and the /NOACCOUNTING qualifier has no effect.

/EXECUTE_ONLY

/NOEXECUTE_ONLY (default)

The /EXECUTE_ONLY qualifier is meaningful only to main programs. It allows the image to activate shareable images to which the user has execute access but no read access. All shareable images referenced by the program must be installed, and OpenVMS RMS uses trusted logical names (those created for use in executive or kernel mode).

You cannot specify this qualifier for an executable image linked with the /TRACEBACK qualifier.

/HEADER_RESIDENT

/NOHEADER_RESIDENT

Installs the file as a known image with a permanently resident header (native mode images only). An image installed header resident is implicitly installed open.

/LOG

/NOLOG (default)

Lists the newly created known file entry along with any associated global sections created by the installation.

/OPEN

/NOOPEN

Installs the file as a permanently open known image.

/PRIVILEGED[=(priv-name[,...])]

/NOPRIVILEGED[=(priv-name[,...])]

Installs the file as a known image with the privileges specified. Then, if the image is not located on the system volume, the image is implicitly installed open.

The /PRIVILEGED qualifier applies only to executable images.

You cannot specify this qualifier for an executable image linked with the /TRACEBACK qualifier.

You can specify one or more of the privilege names shown in the following table.

ACNT	ALLSPOOL	ALTPRI
AUDIT	BUGCHK	BYPASS
CMEXEC	CMKRNL	DIAGNOSE
DOWNGRADE	EXQUOTA	GROUP
GRPNAM	GRPPRV	IMPERSONATE
IMPORT	LOG_IO	MOUNT
NETMBX	OPER	PFNMAP
PHY_IO	PRMCEB	PRMGBL
PRMMBX	PSWAPM	READALL
SECURITY	SETPRV	SHARE
SHMEM	SYSGBL	SYSLCK
SYSNAM	SYSPRV	TMPMBX
UPGRADE	VOLPRO	WORLD

/PROTECTED

/NOPROTECTED (default)

Installs the file as a known image that is protected from user-mode and supervisor-mode write access. You can write into the image only from executive or kernel mode. The /PROTECTED qualifier together with the /SHARE qualifier are used to implement user-written services, which become privileged shareable images.

/PURGE (default)

/NOPURGE

Specifies that the image can be removed by a purge operation; if you specify /NOPURGE, you can remove the image only by a remove operation.

/RESIDENT[=([NO]CODE,[NO]DATA)]

On Alpha systems, causes image code sections or read-only data sections to be placed in the granularity hint regions and compresses other image sections, which remain located in process space. If you do not specify the /RESIDENT qualifier, neither code nor data is installed resident. If you specify the /RESIDENT qualifier without keyword arguments, code is installed resident, and data is not installed resident.

The image must be linked using the /SECTION_BINDING=(CODE,DATA) qualifier. An image installed with resident code or data is implicitly installed header resident and shared.

/SHARED[=[NO]ADDRESS_DATA]

/NOSHARED

Installs the file as a shared known image and creates global sections for the image sections that can be shared. An image installed shared is implicitly installed open.

When you use the ADDRESS_DATA keyword with the /SHARED qualifier, P1 space addresses are assigned for shareable images. With the assigned addresses, the Install utility can determine the content of an address data section when the image is installed rather than when it is activated, reducing CPU and I/O time. A global section is created to allow shared access to address data image sections.

/WRITABLE

/NOWRITABLE

Installs the file as a writable known image as long as you also specify the /SHARED qualifier. The /WRITABLE qualifier only applies to images with image sections that are shareable and writable. The /WRITABLE qualifier is automatically negated if you do not specify the /SHARED qualifier.

Examples

INSTALL> CREATE/OPEN/SHARED WRKD$:[MAIN]STATSHR
      

The command in this example installs the image file STATSHR as a permanently open shared known image.

INSTALL> CREATE/OPEN/PRIVILEGED=(GROUP,GRPNAM) GRPCOMM
      

The command in this example installs the image file GRPCOMM as a permanently open known image with the privileges GROUP and GRPNAM.

Any process running GRPCOMM receives the GROUP and GRPNAM privileges for the duration of the execution of GRPCOMM. The full name of GRPCOMM is assumed to be SYS$SYSTEM:GRPCOMM.EXE.

INSTALL> CREATE/LOG GRPCOMM
      

The command in this example installs the image file GRPCOMM as a known image and then displays the newly created known file entry.

INSTALL> CREATE/SHARED=ADDRESS_DATA WRKD$:[MAIN]INFOSHR
      

The command in this example installs the INFOSHR file as a shared known image and creates shared global sections for code sections and read-only data sections. Because the command includes the ADDRESS_DATA keyword, address data is also created as a shared global section.

	privacy and legal statement
6048PRO_027.HTML