- 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-30-2004 02:47 AM
тАО07-30-2004 02:47 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
not in sylogicals, sylogin.com, login.com
I see a few references but not the define. It is definately defined as show log sys$scratch from a interactive login is valid. Where is the best place. I see it mentioned that it may/could be defined separetly per each user's login.com.
What would be the recommendation ?
Thanks to all for the help !!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 03:02 AM
тАО07-30-2004 03:02 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
Maybe if you provided us with the exact command you use to submit the job, and tell us more about your configuration, someone might think of something.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 03:11 AM
тАО07-30-2004 03:11 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
Well, perhaps better use a conditional like:
$ if f$mode().eqs."BATCH" then $ set verify
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 05:19 AM
тАО07-30-2004 05:19 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
If so, I am supprised that something like this is not already a "default" or "templated" item in either sylogin or login.com.
System info if interested:
AS1200
VMS 7.3-2
job submitted via a VMS CRON like process using:$ spawn/output=nl:/log/nowait/proc='prcnm' 'command'
CRON.COM submitted via:
$ run -
/detach -
/input = admin:[util.cron]cron.com -
/output = admin:[util.cron.log]cron.log -
/error = admin:[util.cron.log]cron.error -
/process = "Cron_DAEMON" -
/queue_limit = 20 -
/subprocess_limit = 20 - !make high enough for spawned commands
/page_file = 10000 -
/time_limit = 0 -
/extent = 1024 -
/file_limit = 50 -
/uic = [SYSTEM] -
/prior=10 -
sys$system:loginout.exe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 05:42 AM
тАО07-30-2004 05:42 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
I already had a thread in which I say that detached processes stink.
1) TT is defined differently (i'm at home, I can't check)
2) no login is executed
3) some logicals are missing (e.g. sys$scratch)
4) process is not really user bound
Yet another victem. When are they going to implement "su -" as in Unix ?
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 05:45 AM
тАО07-30-2004 05:45 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 06:15 AM
тАО07-30-2004 06:15 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
How do you start your 'mail procedure' - via SUBMIT or RUN/DETACH (the second command creates a detached process, not a batch job!).
Try a RUN/DETACH/AUTHORIZE - this should create SYS$SCRATCH (I haven't fully checked the threads that Wim has given, but I have seen /AUTHORIZE is mentioned, so I won't go in detail here.
I suggest you leave out the /ERROR qualifier fromthe RUN command. In that case all output to SYS$ERROR is writte to /OUTPUT as well. I found it much easier to read a complete logfile.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 06:21 AM
тАО07-30-2004 06:21 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
The DCL script that sends an email is executed via the "cron" process as a spawned process.
I will play around a little with the way the "cron" process is executed to see if /auth or some other switch helps.
If not I with either ignore the %MAIL error or include the define for the sys$scratch in somewhere.
Thank you !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2004 07:14 AM
тАО07-30-2004 07:14 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
Uwe is right. On Unix one should call this a batch job but on VMS we don't. It's detached.
But, for 1 time, Unix does the job better.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2004 10:33 AM
тАО07-31-2004 10:33 AM
Re: VMS MAIL %MAIL-E-FILNOTDEL error
which "Cron" are you using, a "homegrown" one or one of the publicly released implementations? I might be able to test this
a bit more around here.
A save way to make sure you have sys$scratch without messing with it in case it already has been put in place is something along the lines of
$ if f$trnlnm("sys$scratch") .eqs. "" then define sys$scratch dev:[dir]
Greetings, Martin