home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!rutgers!uwm.edu!ux1.cso.uiuc.edu!moe.ksu.ksu.edu!mccall!ipmdf-newsgate!list
- From: dan@innosoft.com (Daniel C. Newman)
- Newsgroups: vmsnet.mail.pmdf
- Subject: RE: File create errors.
- Message-ID: <01GPZ5PV826A95MLWB@INNOSOFT.COM>
- Date: 15 Oct 92 18:39:43 GMT
- Organization: The Internet
- Lines: 29
- Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
- Resent-Date: 15 Oct 1992 11:39:43 -0700 (PDT)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-ID: <01GPZ5QOAKR68WXQAR@YMIR.CLAREMONT.EDU>
- X-Vms-To: IN%"SETH@speech.mit.edu"
- X-Vms-Cc: IPMDF
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-Transfer-Encoding: 7BIT
-
- > %MAIL-E-SENDERR, error sending to user audiodev@cbgrle.mit.edu at
- > -PMDF-E-FCRT, File create error, Pascal status = 2, VMS statuses = 99684 and 0
- > -PMDF-I-TEXT, cannot create channel queue entry
-
- This error, 99684, corresponds to
-
- $ exit 99684
- %RMS-F-IFI, invalid internal file identifier (IFI) value
-
- Your users are probably
- mixing foreign protocols in a single VMS MAIL session; e.g., sending mail to
- IN% and then SMTP% or vice versa. They must only use one of these in any given
- MAIL session. Also, if someone has set their forwarding to xx% then this
- problem may be triggered. The only work around is to only use one foreign
- protocol interface if at all possible. Given that you have PMDF, there's no
- need for them to be using things like SMTP%, JNET%, etc. If you'd prefer to
- not re-educate your users, you can always define executive mode logicals of
- the form
-
- $ define/system/exec mail$protocol_smtp pmdf_mailshr
- $ define/system/exec mail$protocol_jnet pmdf_mailshr
-
- etc.
-
- Both TGV and Innosoft is aware of this problem and have tracked it down to a
- bug in RMS. Despite being reported numerous times, DEC has refused to fix this
- bug.
-
- Dan
-