🚀 go-pugleaf

From:   MX%"MX-List@WKUVX1.BITNET"  8-JAN-1993 10:12:10.76
To:     GOATHUNTER
CC:
Subj:   "opcode reserved to DIGITAL fault" still killing SMTP

Return-Path: <list-mgr@WKUVX1.BITNET>
Received: from WKUVX1 (WKUVX1::MXMAILER) by HUNTER (MX V3.1C) with SMTP
          (DECnet); Fri, 08 Jan 1993 10:12:06 CST
Errors-To: list-mgr@WKUVX1.BITNET
X-ListName: Message Exchange Discussion List <MX-List@WKUVX1.BITNET>
Received: from watson.acc.Virginia.EDU (MAILER) by WKUVX1 (MX V3.1C) with
          BSMTP; Fri, 08 Jan 1993 10:07:32 CST
Received: from WATSON by watson.acc.Virginia.EDU (Mailer R2.07) with BSMTP id
          3389; Fri, 08 Jan 93 11:01:30 EST
Received: from Virginia.EDU by WATSON.ACC.VIRGINIA.EDU (IBM VM SMTP V2R1) with
          TCP; Fri, 08 Jan 93 11:01:29 EST
Received: from che.phys.virginia.edu by uvaarpa.Virginia.EDU id aa27979; 8 Jan
          93 10:59 EST
Date: Fri, 08 Jan 1993 10:59:09 EST
From: pat@che.phys.Virginia.EDU
Reply-To: MX-List@WKUVX1.BITNET
To: mx-list@WKUVX1.BITNET
CC: pat@gomez.phys.Virginia.EDU
Subject: "opcode reserved to DIGITAL fault" still killing SMTP

A few days ago I wrote (in part):

>Now I have a new question:  my SMTP process is dying on me as soon as I try
>to SEND.  The appropriate *.HDR_INFO, *.MSG_TEXT, *.SRC_INFO and *.SMTP_INFO
>files are being created in the (now correctly-defined) FLQ_DIR directory,
>but they all end up stranded there because SMTP has died.  The VMS accounting
>utility tells me that SMTP is dying with status code 1000043C,

>%SYSTEM-F-OPCDEC, opcode reserved to DIGITAL fault at PC=!XL

>Does this ring a bell with anyone?  A bug in MX 3.1 (i.e., "Try 3.1C, dummy!),
>or am I still doing something wrong?

>(A review of my MX environment:  7-node Vaxcluster, all nodes running VMS 5.5
> and CMU-TEK 6.6-5.  MX 2.0 currently running successfully on all nodes with
> the exception of occasional failures to deliver, particularly to CERN in
> Europe (addresses ending in .CH).  ROUTER, LOCAL and MLF run on 3 of the
> 7 nodes; SMTP runs on these 3 plus 1 other node, and all 7 nodes run
> SMTP Server.)

Well, I've just tried reinstalling MX 3.1 from scratch, creating a new
CONFIG.MCP, etc., and I'm getting the same "opcode reserved to DIGITAL fault"
error.  Any ideas?  Any more information I can supply?  Thanks.

- Patrick Walsh
  University of Virginia Department of Physics
  pw@virginia.bitnet, pw@virginia.edu, pat@gomez.phys.virginia.edu