- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Problem with AXPVMS-VMS732_DCL-V0500
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
Forums
Discussions
Discussions
Discussions
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
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
01-26-2006 07:56 PM
01-26-2006 07:56 PM
Since installation a call such as
BASEDIR = F$ENVIRONMENT ("PROCEDURE")
returns a corrupt file spec. The version number is returned as a non-numeric character
(see attachment). This then causes subsequent F$PARSE operations to fail.
After de-installing the patch, the correct behaviour returns.
Has anybody else seen this behaviour?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2006 08:52 PM
01-26-2006 08:52 PM
Re: Problem with AXPVMS-VMS732_DCL-V0500
If F$ENVIRONMENT("PROCEDURE") returns exactly 30 characters, the last digit of the version number gets corrupted.
In most cases the last digit is overwritten by a binary zero, which causes F$PARSE to return a truncated version number. But especially in nested command procedures, I observe arbitrary bit patterns, which let F$PARSE fail completely (i.e. return of zero length strings).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2006 10:48 PM
01-26-2006 10:48 PM
Re: Problem with AXPVMS-VMS732_DCL-V0500
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2006 10:55 PM
01-26-2006 10:55 PM
Re: Problem with AXPVMS-VMS732_DCL-V0500
I am working on a test routine to try to nail down the exact combination of circumstances. However, from my work already, it would appear it be related to the total length of the string returned - not just the 30 chars mentioned by Dr Glasow.
Currently running the test in different directories with different name/type lengths - but there certainly is a real problem!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2006 11:13 PM
01-26-2006 11:13 PM
Re: Problem with AXPVMS-VMS732_DCL-V0500
Length String returned
23 $1$DGA1310:[0,0]AAA.Q;P
31 $1$DGA1310:[0,0]AAAAAAAAAAA.Q;P
39 $1$DGA1310:[0,0]AAAAAAAAAAAAAAAAAAA.Q;P
47 $1$DGA1310:[0,0]AAAAAAAAAAAAAAAAAAAAAAAAAAA.Q;P
31 SYS$SYSROOT:[SYSMGR]AAAAAAA.Q;P
39 SYS$SYSROOT:[SYSMGR]AAAAAAAAAAAAAAA.Q;P
47 SYS$SYSROOT:[SYSMGR]AAAAAAAAAAAAAAAAAAAAAAA.Q;P
55 SYS$SYSROOT:[SYSMGR]AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.Q;P
looks like a problem with lengths (n * 8)-1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2006 11:35 PM
01-26-2006 11:35 PM
Re: Problem with AXPVMS-VMS732_DCL-V0500
least of we owe you many thanks!
We planned on a rolling install of patches next week, but we will definitely leave THIS ONE out!
Thanks again.
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2006 12:43 AM
01-27-2006 12:43 AM
Re: Problem with AXPVMS-VMS732_DCL-V0500
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2006 01:13 AM
01-27-2006 01:13 AM
Re: Problem with AXPVMS-VMS732_DCL-V0500
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2006 05:21 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2006 11:44 PM
01-29-2006 11:44 PM
Re: Problem with AXPVMS-VMS732_DCL-V0500
memory management within DCL. The fix
is in the area of memory allocation making
sure that the amount of memory being allocated is the same amount being freed.
Sounds trivial..? yes...but it's a little
harder than it sounds....;-)
Anyway, we fixed the problem and expect to
ship a new kit VMS732_DCL-V0600 later this
week. In the meanwhile the V5 kit will be
put on hold.
Sorry for any inconvenience
Guy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2006 01:33 AM
01-30-2006 01:33 AM
Re: Problem with AXPVMS-VMS732_DCL-V0500
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2006 09:57 PM
02-01-2006 09:57 PM
Re: Problem with AXPVMS-VMS732_DCL-V0500
http://www.openvms.org/stories.php?story=06/02/01/1650225
but I can't see it on the ftp site yet
ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2
Purely Personal Opinion