- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: VMS MAIL %MAIL-E-FILNOTDEL error
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 06:10 AM
тАО07-29-2004 06:10 AM
%MAIL-E-FILNOTDEL, error deleting SYS$SCRATCH:[UTIL.BKU]MAIL_210A_SEND.TMP;*
-RMS-F-DEV, error in device name or inappropriate device type for operation
%MAIL-E-FILNOTDEL, error deleting SYS$SCRATCH:[UTIL.BKU]MAIL_210A_EDIT.TMP;*
-RMS-F-DEV, error in device name or inappropriate device type for operation
This only reports the error when running a DCL script via batch.
Commands used is:
$ MAIL_PROCEDURE:
$set noon
$open/write mailfile tmp_mail.txt
$write mailfile "''err_msg1'"
$close mailfile
$mail/subj="Alert - OSIBK1 Backup ''status'" -tmp_mail.txt "user@mycompany.com"
$delete/nolog tmp_mail.txt;*
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 06:22 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 06:25 AM
тАО07-29-2004 06:25 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
Did you notice that the path in the error stated sys$scratch:[current_working_dir]
which is not correct.
a manual show log sys$scratch shows:
"SYS$SCRATCH" = "SYS$SYSROOT:[SYSMGR]" (LNM$JOB_81663980)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 07:02 AM
тАО07-29-2004 07:02 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 08:08 AM
тАО07-29-2004 08:08 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
I have another script that also runs via batch with same mail code and no errors.
$ MAIL_PROCEDURE:
$!MAIL SOMEBODY
$set noon
$open/write mailfile tmp_mail.txt
$write mailfile "''err_msg1'"
$close mailfile
$mail/subj="Alert - OSIBK1 BCV MERGE ''status'" tmp_mail.txt "user@mycompany.com"
$delete/nolog tmp_mail.txt;*
$ return
$!END MAIL_PROCEDURE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 08:10 AM
тАО07-29-2004 08:10 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
SYS$SCRATCH is defined at login time as the user's default directory and can be and usually is different for every user.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 08:15 AM
тАО07-29-2004 08:15 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 08:19 AM
тАО07-29-2004 08:19 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
Here is the output after using show log sys$scratch
%SHOW-S-NOTRAN, no translation for logical name SYS$SCRATCH
%MAIL-E-FILNOTDEL, error deleting SYS$SCRATCH:[UTIL.BKU]MAIL_2259_SEND.TMP;*
-RMS-F-DEV, error in device name or inappropriate device type for operation
%MAIL-E-FILNOTDEL, error deleting SYS$SCRATCH:[UTIL.BKU]MAIL_2259_EDIT.TMP;*
-RMS-F-DEV, error in device name or inappropriate device type for operation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 04:58 PM
тАО07-29-2004 04:58 PM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
>> Dale A. Marcy Jul 29, 2004 20:15:01 GMT ->> ---------------------------------------------
>> That is the error message you would receive if Sys$Scratch has been deassigned (or never defined). Is it possible there is a branch based on an f$mode() being batch or not being interactive that could cause the logical to be deassigned in either the sylogin procedure or the user's login procedure?
Sounds good Dale!
>> Tim Nelson Jul 29, 2004 20:19:21 GMT
>>-----------------------------------------
>> submitted under SYSTEM using.
>>Here is the output after using show log sys$scratch
>> %SHOW-S-NOTRAN, no translation for logical name SYS$SCRATCH
This confirms Dale's thoughts.
Please make sure a valid sys$scratch is defined for all users (Before F$MODE() check in sylogin!)
In the mean time I check the Mail sources a little. It suggests it will only conditionally delete (wildcarded) send and endi tmp file using a global flag. In practice though it seems always to try, whether a temp file was created or not.
The code explicitly checks for 'FNF' (File Not Found) and declares victory if it received that specific error. But 'DEV' triggers the 'FILNOTDEL' condition.
So just define sys$scratch and maill will get FNF back from RMS and it will be happy.
hth,
Hein.
%MAIL-E-FILNOTDEL, error deleting SYS$SCRATCH:[UTIL.BKU]MAIL_2259_SEND.TMP;*
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 05:53 PM
тАО07-29-2004 05:53 PM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
SYS$SCRATCH is defined as a JOB-wide EXEC-mode logical name by LOGINOUT and cannot easily be deleted.
You can easily test, if some code is deleting SYS$SCRATCH by submitting a simple DCL-procedure with just a SHOW LOG/FULL SYS$SCRATCH in the same environment in which your mail procedure is run.
Volker.