- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- SYS$DECDTM_INHIBIT TRUE
Operating System - OpenVMS
1753514
Members
7874
Online
108795
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
09-29-2010 01:25 PM
09-29-2010 01:25 PM
Re: SYS$DECDTM_INHIBIT TRUE
re Joseph:
> if assign/deassign was really case
>insensitive until DEFINE was introduced in
>VMS (version?).
DEFINE has been around since day 1, but in V1.0, the ASSIGN form was preferred in documentation and system provided command procedures.
My recollection was that all the DCL logical name commands uppercased everything, so in a sense they were case insensitive. I remember an issue using $crelog (not $crelnm, which didn't exist). I managed to create a lower case logical name which was effectively invisible to DCL. You could see it with SHOW LOGICAL, but not translate or DEASSIGN. Back then there were only 3 logical name tables PROCESS, GROUP and SYSTEM. $CRELOG and $TRNLOG still exist for compatibility, but are no longer documented. They can only see the original 3 tables.
Documentation changed with VMS V2.0 to favour DEFINE over ASSIGN, which was a throwback to earlier operating systems, RSTS and/or RSX. Makes me wonder why some folk still use the archaic ASSIGN form, since it was superceeded over 30 years ago! But then some people still persist with EDT. Thank the stars engineering didn't insist on compatibility and keep SOS ;-)
The more general logical name structures we know today were introduced with VMS V4.0, early 1980's.
> if assign/deassign was really case
>insensitive until DEFINE was introduced in
>VMS (version?).
DEFINE has been around since day 1, but in V1.0, the ASSIGN form was preferred in documentation and system provided command procedures.
My recollection was that all the DCL logical name commands uppercased everything, so in a sense they were case insensitive. I remember an issue using $crelog (not $crelnm, which didn't exist). I managed to create a lower case logical name which was effectively invisible to DCL. You could see it with SHOW LOGICAL, but not translate or DEASSIGN. Back then there were only 3 logical name tables PROCESS, GROUP and SYSTEM. $CRELOG and $TRNLOG still exist for compatibility, but are no longer documented. They can only see the original 3 tables.
Documentation changed with VMS V2.0 to favour DEFINE over ASSIGN, which was a throwback to earlier operating systems, RSTS and/or RSX. Makes me wonder why some folk still use the archaic ASSIGN form, since it was superceeded over 30 years ago! But then some people still persist with EDT. Thank the stars engineering didn't insist on compatibility and keep SOS ;-)
The more general logical name structures we know today were introduced with VMS V4.0, early 1980's.
A crucible of informative mistakes
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP