- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Device Logicals Names
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
тАО10-15-2008 04:37 AM
тАО10-15-2008 04:37 AM
Current storage device names are like;
DSA1 = $1$DKA100 + $1$DKB200 + $1$DKC200
We have about 20 shadow sets.
New storage will be like
DSA1= $1$DGA1010 + $1$DGA1020 + $1$DGA1030
The server will not be about for long in the future.
The server is riddled with command files that reference device names and numbers i.e. Remove member DKC200 from shadow set , mount it , do a backup from it and remount into shadow set.
I have done a quick and dirty fix of a
$DEFINE/SYS/EXEC/TRANS=(CONC,TERM) $1$DKC200 $1┬гDGA1030:
This seems to work ...but I have found that some command files reference the disk as _$1$DKC200: or _$1$DKC200 (Underscore at start of device name). This breaks my quick and ugly fix ...
This a dev server and has been a sandpit for the last 5 years !
Anyone have any ideas how I do a logical define to cope with the _ prior to device names ?
Avoiding editing the dozens of cammand files of course.
Thanks in Advance
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2008 06:10 AM
тАО10-15-2008 06:10 AM
SolutionIf the files are forcing the names, then there is little that can be done.
If the names are explicit, then using SEARCH, GREP, PERL or other tools to identify the command files (and possibly automate the editing) might be an option [I have done this in similar situations in the past].
I would also consider moving this using the techniques described in my presentation "Migrating OpenVMS Storage Environments without Interruption or Disruption" (slides available at http://www.rlgsc.com/hptechnologyforum/2007/1512.html ).
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2008 06:25 AM
тАО10-15-2008 06:25 AM
Re: Device Logicals Names
Yes it looks like we script something to search and make the changes in the numerous command files.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2008 07:00 AM
тАО10-15-2008 07:00 AM
Re: Device Logicals Names
$ DEFINE/SYS/EXEC/TRANS=(CONC,TERM) -
_$1$DKC200 $1$DGA1030:
$ DEFINE/SYS/EXEC/TRANS=(CONC,TERM) -
__$1$DKC200 $1$DGA1030:
I've also patched executables and data files to fix some of these cases; for what isn't accessible via logical name or editor or other and more reasonable means.
And tools such as Perl can make short order of mass DCL changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2008 07:02 AM
тАО10-15-2008 07:02 AM
Re: Device Logicals Names
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2008 01:44 PM
тАО11-03-2008 01:44 PM
Re: Device Logicals Names
*** Use at your own risk ***
[Despite the comments (I wrote this thing ca. 2000), a quick check showed it works with the ... wildcard.]
$!+ FIXALL.COM
$!
$! PURPOSE: TO S/OLD/NEW/WH IN MANY FILES IN A SINGLE DIRECTORY
$! P1 = FILE-SPEC (WILDCARDS OKAY)
$!
$!! Ask for file-spec:
$!
$ IF (P1 .EQS. "") THEN $ INQUIRE P1 "_File-spec"
$_ASK_P2:
$ IF (P2 .EQS. "") THEN $ INQUIRE P2 "_Old string"
$ IF (P2 .EQS. "") THEN $ WRITE SYS$COMMAND "Null value not allowed. Try again:"
$ IF (P2 .EQS. "") THEN $ GOTO _ASK_P2
$ IF (P3 .EQS. "") THEN $ INQUIRE P3 "_New string"
$!
$!! Create the command file that will be run to do the editing:
$!
$ ON ERROR THEN GOTO LEAVE
$ ON CONTROL_Y THEN GOTO LEAVE
$ OPEN/WRITE FIX FIXALL.TMP
$ WRITE FIX "$ ON CONTROL_Y THEN STOP "
$ WRITE FIX "$ EDIT/EDT/NOCOMMAND 'P1' "
$ FIX_STRING = "S|" + P2 + "|" + P3 + "|WH"
$ WRITE FIX FIX_STRING
$ WRITE FIX "EXIT "
$ CLOSE FIX
$!
$!! Look for files:
$!
$FIX_FILE:
$!
$ FILE = F$SEARCH(P1)
$ SHOW SYMBOL FILE
$ IF (FILE .EQS. "") THEN $ GOTO EXIT
$!
$!! Run the command file we just made, but do not alter it or directory files!
$!
$ FILE_NAME = F$PARSE(FILE,,,"NAME")
$ FILE_TYPE = F$PARSE(FILE,,,"TYPE")
$ FILE_NT = FILE_NAME + FILE_TYPE
$ IF (FILE_NT .NES. "FIXALL.TMP" .AND. FILE_TYPE .NES. ".DIR") THEN @FIXALL.TMP 'FILE'
$!
$!GO BACK TO THE TOP OF THE LOOP:
$ GOTO FIX_FILE
$!
$EXIT:
$ DELETE FIXALL.TMP;*
$ EXIT
$!
$LEAVE:
$ CLOSE FIX
$ STOP
$!
$!# END OF FIXALL.COM
AEFAEF
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2008 02:24 PM
тАО11-03-2008 02:24 PM
Re: Device Logicals Names
I wrote FIXALL.COM between about 1986 and Jun 1991, not ca. 2000.
Yeah, I should have fixed the comment about a "many files in a single directory" before I posted. Sorry. It should work fine with any file-spec that F$SEARCH is happy with.
AEFAEF