- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: NOMSG + create failed
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
тАО03-08-2004 02:20 AM
тАО03-08-2004 02:20 AM
Re: NOMSG + create failed
Yes, it is create/fdl that is causing the problem. I have errorhandling but only get the error code, not the message stack. Unless I explecitly ask for it (as I will do from now).
Yes, I used to maintain (generate) fdl's too, 10-15 years ago.
The FDL is a static files that doesn't move and is only accessed by the procedure itself.
I tested if exclusive access is needed and the answer is NO. So, I think it must be something differently.
Filling error messages based upon user complaints is the wrong way to go. You need someway of scanning the sources and checking if all codes are present in the libraries. That's how we used to work in COBOL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2004 02:47 AM
тАО03-08-2004 02:47 AM
Re: NOMSG + create failed
> I have errorhandling but only get the error code, not the message stack.
> Unless I explecitly ask for it (as I will do from now).
'Normally' it just shows up in the batch log no? Or is this spawned perhaps.
If it is spawned, then I'd strongly recommend to call FDL$CREATE instead.
> Yes, I used to maintain (generate) fdl's too, 10-15 years ago.
I think you mis-read or I did not write clearly enough.
I actually maintained the FDL code for the VMS sources. :-).
> The FDL is a static files that doesn't move and is only accessed by the procedure itself.
As they normally are. So some other 'environmental' condition happened.
Some (pooled) process quota ran out?
Normally the FAB$L_STV field would have those details, not the primary FAB$L_STS.
> I tested if exclusive access is needed and the answer is NO. So, I think it must be something differently.
Well... exclusive access is indeed not needed, just read will do. But it will not work if an other stream already has exclusive access:
$ open x tmp.fdl
$ create/fdl=tmp test
$ close x
$ open/write x tmp.fdl
$ create/fdl=tmp test
%FDL-F-OPENFDL, error opening U$1:[HEIN]TMP.FDL;
-RMS-E-FLK, file currently locked by another user
> Filling error messages based upon user complaints is the wrong way to go.
> You need someway of scanning the sources and checking if all codes are present in the libraries. That's how we used to work in COBOL.
Again, I mis-communicated. Sorry.
It is 99.99% sure that all message are caught in message files. The purpose of filing a full documented report would be to learn how the application got in trouble and maybe fix that somehow or just help the customer to fix the problem... because it will be a customer applicaiton problem, not a 'missing' error message.
There are no missing error messages in VMS. Period.
In the VMS sources error message are never hard coded.
They are always symbolic and the symbols/values are generated from message sources files. If a a message is 'forgotten' a compile / link error (while building VMS) will occur and will be fixed.
The above has to be the assumtion / expectation. Sure, something may have sneeked by, but that's pretty darn unliekly and so an application problem is expected.
Now that application problem, may be due to a sub-optimal VMS setup choice ('surprise' location for an msg file) which VMS may be able to address, but it woudl be kinda od to run into that now, after decades of few / no problems
Groets,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2004 10:08 AM
тАО03-08-2004 10:08 AM
Re: NOMSG + create failed
one more thing you could try:
Bracket the create/fdl operation in a
set watch file/class=major
create/fdl...
set watch file/class=none
This should provide addtional information on the attempted file system operations. Yes, I know set watch is undocumented, but I have it from a reliable source that it is save to use ;-)
Greetings, Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2004 07:36 PM
тАО03-08-2004 07:36 PM
Re: NOMSG + create failed
(but don't forget it needs CMKRNL)
Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2004 07:40 PM
тАО03-08-2004 07:40 PM
Re: NOMSG + create failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2004 10:30 PM
тАО05-26-2004 10:30 PM
Re: NOMSG + create failed
While the procedure was doing create/fdl, another procedure was changing the protection on the directory in which the FDL was placed. Result : file currently locked by another user.
Wim
(wie zoekt die vindt)
- « Previous
-
- 1
- 2
- Next »