Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- VMS 8.2 VMSINSTAL Bug with RUN_IMAGE Persists?
Operating System - OpenVMS
turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
-
Categories
- Topics
- Hybrid IT with Cloud
- Mobile & IoT
- IT for Data & Analytics
- Transformation
- Strategy and Technology
- Products
- Cloud
- Integrated Systems
- Networking
- Servers and Operating Systems
- Services
- Storage
- Company
- Events
- Partner Solutions and Certifications
- Welcome
- Welcome
- Announcements
- Tips and Tricks
- Feedback
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- Converged Data Center Infrastructure
- Digital Transformation
- Grounded in the Cloud
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- Networking
- OEM Solutions
- Servers: The Right Compute
- Telecom IQ
- Transforming IT
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Categories
-
Forums
-
Blogs
-
InformationEnglish
VMS 8.2 VMSINSTAL Bug with RUN_IMAGE Persists?
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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-23-2007 02:24 PM
04-23-2007 02:24 PM
VMS 8.2 VMSINSTAL Bug with RUN_IMAGE Persists?
VMS 8.2 VMSINSTAL Bug with RUN_IMAGE Persists?
Hi,
There was/is a bug with VMSINSTAL's Run_Image callback on 8.2 machines that exhibited the following symptoms at product installation time: -
* Do you want to purge files replaced by this installation [YES]?
%ANALYZE-E-OPENIN, error opening MISSING:[MISSING]VMI$NEW.EXE; as input
-SYSTEM-W-NOSUCHDEV, no such device available
%VMSINSTAL-E-INSFAIL, The installation of TIER3A V3.1 has failed.
The problem is that I've just had someone upgrading to 8.2 (Why not 8.3? I dunno :-) and the bug appears to still be there :-(
VMS 8.2 is still supported, is it not? Has anyone got a patch reference:
Below is from one of COVs kind souls many moons ago stating that this bug is *supposed* to have been fixed.
Any ideas?
Cheers Richard Maher
> 2. VMSINSTAL
>
> This failed miserably on VMS V8.2 on running T3$CHKACC, because there
> is a known bug in VMSINSTAL on V8.2 with the RUN_IMAGE vmi$callback.
>
> It craps out with:
>
> %ANALYZE-E-OPENIN, error opening MISSING:[MISSING]VMI$NEW.EXE; as input
> -SYSTEM-W-NOSUCHDEV, no such device available
> %VMSINSTAL-E-INSFAIL, The installation of TIER3A V3.1 has failed.
>
>
> This issue is allegedly fixed in VMS82A_KITTING-V0100, dated
> 10-JAN-2006, but that contains a copy of VMSINSTAL.COM from
> 10-AUG-2005, so doesn't solve the problem.
>
> Needless to say, I'm going to report that problem. I got Tier3
> installed by knobbling its KITINSTAL.COM thus:
>
> $! VMI$CALLBACK RUN_IMAGE "VMI$KWD:T3$CHKACC.EXE"
> $ tier3$missing = "true"
There was/is a bug with VMSINSTAL's Run_Image callback on 8.2 machines that exhibited the following symptoms at product installation time: -
* Do you want to purge files replaced by this installation [YES]?
%ANALYZE-E-OPENIN, error opening MISSING:[MISSING]VMI$NEW.EXE; as input
-SYSTEM-W-NOSUCHDEV, no such device available
%VMSINSTAL-E-INSFAIL, The installation of TIER3A V3.1 has failed.
The problem is that I've just had someone upgrading to 8.2 (Why not 8.3? I dunno :-) and the bug appears to still be there :-(
VMS 8.2 is still supported, is it not? Has anyone got a patch reference:
Below is from one of COVs kind souls many moons ago stating that this bug is *supposed* to have been fixed.
Any ideas?
Cheers Richard Maher
> 2. VMSINSTAL
>
> This failed miserably on VMS V8.2 on running T3$CHKACC, because there
> is a known bug in VMSINSTAL on V8.2 with the RUN_IMAGE vmi$callback.
>
> It craps out with:
>
> %ANALYZE-E-OPENIN, error opening MISSING:[MISSING]VMI$NEW.EXE; as input
> -SYSTEM-W-NOSUCHDEV, no such device available
> %VMSINSTAL-E-INSFAIL, The installation of TIER3A V3.1 has failed.
>
>
> This issue is allegedly fixed in VMS82A_KITTING-V0100, dated
> 10-JAN-2006, but that contains a copy of VMSINSTAL.COM from
> 10-AUG-2005, so doesn't solve the problem.
>
> Needless to say, I'm going to report that problem. I got Tier3
> installed by knobbling its KITINSTAL.COM thus:
>
> $! VMI$CALLBACK RUN_IMAGE "VMI$KWD:T3$CHKACC.EXE"
> $ tier3$missing = "true"
1 REPLY
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-25-2007 02:20 AM
04-25-2007 02:20 AM
Re: VMS 8.2 VMSINSTAL Bug with RUN_IMAGE Persists?
Re: VMS 8.2 VMSINSTAL Bug with RUN_IMAGE Persists?
I know this won't help, but why is the product still using VMSINSTAL?
PCSI kits are the standard these days, and are not particularly difficult to create.
[I'd better duck now ...]
PCSI kits are the standard these days, and are not particularly difficult to create.
[I'd better duck now ...]
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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2018 Hewlett Packard Enterprise Development LP