- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: migration queue databased from OpenVMS 7.3-2 t...
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
тАО01-17-2008 08:50 AM
тАО01-17-2008 08:50 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2008 09:12 AM
тАО01-17-2008 09:12 AM
Re: migration queue databased from OpenVMS 7.3-2 to OpenVMS 8.3
I do not recall any special issues. Precisely what was involved? Was the update done in-place?
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2008 09:16 AM
тАО01-17-2008 09:16 AM
Re: migration queue databased from OpenVMS 7.3-2 to OpenVMS 8.3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2008 10:08 AM
тАО01-17-2008 10:08 AM
Re: migration queue databased from OpenVMS 7.3-2 to OpenVMS 8.3
Don't know about your system, but on my system, my user files aren't on the system disk and I don't mount my user disks during an upgrade. Just an idle thought...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2008 10:22 AM
тАО01-17-2008 10:22 AM
Re: migration queue databased from OpenVMS 7.3-2 to OpenVMS 8.3
Yes, the data disk is different to the system disk. I verify with the system startup file that the data disk has been mounted before queue start.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2008 05:20 PM
тАО01-17-2008 05:20 PM
Re: migration queue databased from OpenVMS 7.3-2 to OpenVMS 8.3
For example:
$ submit/hold/noprint/log=sys$scratch disk$itrcdemo:[demo]showtime/retain=always /que=sigma$oper
Job SHOWTIME (queue SIGMA$OPER, entry 549) holding
$ sho ent/ful 549
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
549 SHOWTIME JON Holding
On available batch queue SIGMA$OPER
Submitted 17-JAN-2008 20:08:15.03 /KEEP /LOG=DSA1200:[USERS.][JON.SCRATCH].LOG; /NOPRINT /PRIORITY=100 /RETAIN=ALWAYS
File: _$4$LDA3:[DEMO]SHOWTIME.COM;1
$ sho dev disk$itrcdemo
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$4$LDA3: (SIGMA) Mounted 0 ITRCDEMO 1478 1 1
$ dism disk$itrcdemo
$ ld sho lda3
%LD-I-CONNECTED, Connected $4$LDA3: to DSA3403:[000000]DISK3.DSK;1
$ ld disc lda3
$ ld conn DSA3403:[000000]DISK3.DSK;1 lda4:/shar
$ mou/sys/noassist lda4 itrcdemo
%MOUNT-I-MOUNTED, ITRCDEMO mounted on _$4$LDA4: (SIGMA)
$ sho dev disk$itrcdemo
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$4$LDA4: (SIGMA) Mounted 0 ITRCDEMO 1478 1 1
$ sho ent/ful 549
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
549 SHOWTIME JON Holding
On available batch queue SIGMA$OPER
Submitted 17-JAN-2008 20:08:15.03 /KEEP /LOG=DSA1200:[USERS.][JON.SCRATCH].LOG; /NOPRINT /PRIORITY=100 /RETAIN=ALWAYS
File: _$4$LDA3:[DEMO]SHOWTIME.COM;1
$ set ent/rel 549
$ sho ent 549/ful
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
549 SHOWTIME JON Retained on error
%RMS-F-DEV, error in device name or inappropriate device type for operation
-RMS-F-DEV, error in device name or inappropriate device type for operation
-SYSTEM-W-NOSUCHDEV, no such device available
On available batch queue SIGMA$OPER
Submitted 17-JAN-2008 20:08:15.03 /KEEP /LOG=DSA1200:[USERS.][JON.SCRATCH].LOG; /NOPRINT /PRIORITY=100 /RETAIN=ALWAYS
File: _$4$LDA3:[DEMO]SHOWTIME.COM;1
Completed 17-JAN-2008 20:11:08.35 on queue SIGMA$OPER
$
If this was the problem, use forum search for "DISPLAY_JOBS", a command procedure that can be used to create a command procedure to create a command procedure that will be able to resubmit the jobs. You will have to edit the command procedure to replace the old device name with the new.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2008 08:35 PM
тАО01-17-2008 08:35 PM
Re: migration queue databased from OpenVMS 7.3-2 to OpenVMS 8.3
I was able to reproduce the "File not found" error.
$ submit/que=sigma$oper disk$itrcdemo:[demo]showtime/noprint/hold/log=sys$scratch/retain=always
Job SHOWTIME (queue SIGMA$OPER, entry 1681) holding
$ copy _$4$LDA4:[DEMO]SHOWTIME.COM;1 _$4$LDA4:[DEMO]SHOWTIME.COM;/log
%COPY-S-COPIED, _$4$LDA4:[DEMO]SHOWTIME.COM;1 copied to _$4$LDA4:[DEMO]SHOWTIME.COM;2 (1 block)
$ pu _$4$LDA4:[DEMO]SHOWTIME.COM/log
%PURGE-I-FILPURG, _$4$LDA4:[DEMO]SHOWTIME.COM;1 deleted (1 block)
$ ren _$4$LDA4:[DEMO]SHOWTIME.COM;2 ;/log
%RENAME-I-RENAMED, _$4$LDA4:[DEMO]SHOWTIME.COM;2 renamed to _$4$LDA4:[DEMO]SHOWTIME.COM;1
$ sho ent/ful 1681
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
1681 SHOWTIME JON Holding
On available batch queue SIGMA$OPER
Submitted 17-JAN-2008 20:35:13.88 /KEEP /LOG=DSA1200:[USERS.][JON.SCRATCH].LOG; /NOPRINT /PRIORITY=100 /RETAIN=ALWAYS
File: _$4$LDA4:[DEMO]SHOWTIME.COM;1
$ ! here everything looks ok...
$ sho sym dw
DW == "DIRECTORY/SIZE=ALL/DATE/WIDTH=(FILE:38,SIZE:7)"
$ dw _$4$LDA4:[DEMO]SHOWTIME.COM;1
Directory _$4$LDA4:[DEMO]
SHOWTIME.COM;1 1/1 17-JAN-2008 20:35:50.20
Total of 1 file, 1/1 block.
$ ! but watch this...
$ set ent/rel 1681
$ sho ent/ful 1681
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
1681 SHOWTIME JON Retained on error
%RMS-E-FNF, file not found
-RMS-E-FNF, file not found
-SYSTEM-W-NOSUCHFILE, no such file
On available batch queue SIGMA$OPER
Submitted 17-JAN-2008 20:35:13.88 /KEEP /LOG=DSA1200:[USERS.][JON.SCRATCH].LOG; /NOPRINT /PRIORITY=100 /RETAIN=ALWAYS
File: _$4$LDA4:[DEMO]SHOWTIME.COM;1
Completed 17-JAN-2008 20:37:40.92 on queue SIGMA$OPER
$
Did you possibly run a command procedure to "resequence" the versions? At least one version I have seen backup instead of rename to avoid the files revision data from being changed, However it does change the File ID, and that must remain the same for the queue manager to be able to find the file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2008 05:03 AM
тАО03-12-2008 05:03 AM
SolutionDave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2008 09:38 AM
тАО03-12-2008 09:38 AM
Re: migration queue databased from OpenVMS 7.3-2 to OpenVMS 8.3
Error opening primary input file SYS$INPUT
That line is followed by the text part of the RMS error message that explains why the batch file could not be opened. So if the batch file was deleted the complete log file would be:
Error opening primary input file SYS$INPUT
File not found
SYSTEM job terminated at 12-MAR-2008 17:08:11.64
But if the problem was with the device name changing or not being mounted then you get:
Error opening primary input file SYS$INPUT
Device not ready, not mounted, or unavailable
SYSTEM job terminated at 12-MAR-2008 17:13:00.48
If the log file device is not mounted the job won't run either and there is no log file to check obviously, but in this case you shouldn't see a "file not found" error either in accounting or on SHOW ENTRY if the job was retained.
Sorry, but this issue sounds more like some user error than a system problem.