- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- BACKUP /N(ew) change in behaviour
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
10-25-2007 06:05 AM
10-25-2007 06:05 AM
The customer has command procedures with the BACKUP command utilizing the abbreviation /n to specify /new. It would appear that VAXBACK03_062 introduced a new switch called /no_incremental and their procedures now give eg.:
$ backup/log vupometer.com;0 *.*/n
%DCL-W-ABKEYW, ambiguous qualifier or keyword - supply more characters
\N\
I downloaded VERB and extracted the BACKUP cld, took out the: qualifier NO_INCREMENTAL and replaced the BACKUP command in the correct DCLTABLES, replaced the installed image, logged out and back in.
Now it gives a different error whether using /n , /new or /no eg.:
$ backup /log vupometer.com;0 *.*/n
%CLI-F-SYNTAX, error parsing 'NO_INCREMENTAL'
-CLI-E-ENTNF, specified entity not found in command tables
Have I done something wrong, or is it not a legitimate "fix" to modify commands in this fashion?
I have no idea how many procedures are affected ... waiting for that answer. If it's a couple then there is no issue, some simple edits can deal with it, but if it's "lots" ...
Cheers,
Art
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2007 06:37 AM
10-25-2007 06:37 AM
Re: BACKUP /N(ew) change in behaviour
maybe you missed removing something. Can you put /NEW in the procedures, it would
certainly make the clearer to read. Dean
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2007 06:59 AM
10-25-2007 06:59 AM
SolutionGuenther
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2007 07:28 AM
10-25-2007 07:28 AM
Re: BACKUP /N(ew) change in behaviour
Guenther - thanks.
Hopefully it's not "hundreds" of procedures to edit!
Cheers,
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2007 02:07 PM
10-25-2007 02:07 PM
Re: BACKUP /N(ew) change in behaviour
You can adjust some things by modifying the CLD, but you can't remove stuff that the program image looks for if the program considers missing entities to be fatal.
Use of contracted commands and/or qualifiers is not recommended in command procedures, for precisely the reason you've posted this question! Just because a particular contraction is unambiguous now, doesn't mean it will remain so in future.
The usual recommendation for writing DCL command procedures is to spell all DCL tokens (verbs, qualifiers and keywords) in full. If you MUST contract them, don't go below four letters.
There is even an undocumented command to force fully spelled DCL tokens (I'll post it if I can find it...)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2007 03:51 PM
10-25-2007 03:51 PM
Re: BACKUP /N(ew) change in behaviour
WARNING - be very careful with this, it seems to be badly broken on V7.3 and above, not sure about other versions:
$ SET COMMAND SYS$INPUT
DEFINE VERB SETDCL
CLIROUTINE SETDCL
QUALIFIER SPELL_CHECK, NEGATABLE
^Z
$ SETDCL/SPELL
should turn on spell checking.
$ SETDCL/NOSPELL
to turn it off,
It's supposed to issue a warning "%DCL-I-MISSPELL" for any command token which isn't completely spelled properly, BUT it appears the message string overflows into junk, and may even corrupt some DCL structures. Unsupported and even less documented than most unsupported stuff.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2007 11:59 AM
10-26-2007 11:59 AM
Re: BACKUP /N(ew) change in behaviour
One of the two interfaces to VERB port found on Freeware V8 is busted. There's a work-around (fix), or you can use the other command interface. See topic 3537.* over in the EISNER::VMS notes conference for a recent discussion of VERB.