- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Time Zone Patch
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
02-23-2007 11:12 AM
02-23-2007 11:12 AM
Time Zone Patch
Thanx for answering my question.
Fred
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2007 12:29 PM
02-23-2007 12:29 PM
Re: Time Zone Patch
What is your relative tolerance for risk, and for local testing and related support?
You might need to rejigger the VMSINSTAL kit as a start, as it would not surprise me that it won't install without a tweak or two. That rejiggering should be pretty simple, just use BACKUP to pull the kit apart, adjust KITINSTAL, re-roll the kit, and try it.
Then test the results, after the installation.
The most reliable would be an upgrade to the current OpenVMS VAX release; to V7.3. You'll get the other patches with that upgrade, too.
As for previous discussions, you might want to start here:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1102917
Though unlike that thread, you won't have to deal with Java, as you're on OpenVMS VAX, and Java isn't.
It might well work. Try it. Tweak the kit. Test it. Let us know.
Stephen Hoffman
HoffmanLabs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2007 12:47 PM
02-23-2007 12:47 PM
Re: Time Zone Patch
I am just hoping that there is someone out there that has applied this patch to an VAX 7.2 environment with a degreee of sucess.
Regardless thanx for your input.
Fred
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2007 09:47 PM
02-23-2007 09:47 PM
Re: Time Zone Patch
to start with,
Welcome to the VMS Forum.
Secondly, for the way to say Thanks< see
http://forums1.itrc.hp.com/service/forums/helptips.do?#33
Thirdly,
If this system really is that critical, then you REALLY should convince Management of the equally critical need for a "sandbox" (which can also serve as a spare in case of need).
In that sandbox you can try 7.3 without risk, and it would not surprise me if you find that even your "very flackey application" would gain in stability and performanc.
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2007 06:59 AM
02-24-2007 06:59 AM
Re: Time Zone Patch
Should you need support for a critical problem with OpenVMS itself here, then you'll likely be encouraged to roll forward to V7.3. Regardless, that V7.3 upgrade should not be a significant change to your configuration. I'd be surprised if that upgrade perturbed anything, too.
Assuming source code and with prerequisite products available, I'd also be looking at what to do with the configuration in general. A couple of Integrity rx2660 servers will use far less space, far less power, and far less hardware support than a flock of VAX 7000 model 700 series boxes with the usual accouterments. And each of these 2U boxes will be seriously faster than your entire configuration, and with massively more storage.
The other approach forward (for space and for various other savings) would be emulation, as most any current VAX emulator would be seriously faster than these VAX 7000 series boxes. This requires fewer changes to the existing applications, assuming you have no hardware-level dependencies. (Weird XMI widgets, for instance.)
The least-change approach is to determine if the timezones matter for your specific configuration. There are certainly established configurations that are switched over manually twice a year, and that do not utilize nor particularly need the daylight saving time (DST) or even the timezone settings. This was the classic environment on OpenVMS for eons. C and some more recent applications can and do play into this TZ and DST requirement here, however.
Rolling your own fix is certainly potentially viable. Probably even fairly straightforward, if all that's required here is resetting an installation-time version check. (I have not looked at the TZ kit.) Though even assuming somebody else has built and tested that approach and confirms it here, it's not clear that what testing was performed would match your environment.
Here, I'd tend to assume it would be safest and most expedient to roll forward to V7.3, to ECO it, and to apply the other mandatory ECO kits for that release. The other benefit: with the approach of an upgrade, you have somebody to call if something should go off the rails here. And you would again have access to the current ECOs for OpenVMS.
Unfortunately, there's no good and no easy and no certain answer here. And not that a production site such as your own would likely want to commit to without making a rather more detailed look at the associated options and risks of each. And testing.
Stephen Hoffman
HoffmanLabs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2007 09:27 AM
02-25-2007 09:27 AM
Re: Time Zone Patch
>I am just hoping that there is someone out
>there that has applied this patch to an
>VAX 7.2 environment with a degreee of
>sucess.
Easy (dumb) answer. A V7.3 patch will not install on a V7.2 system. It will fail the version check.
In the case of the time zone patch, it's really just a bunch of TEXT changes to your timezone definition files. You can do these manually yourself. Break open the V7.3 patch kit (it's a BACKUP saveset), and dig through the KITINSTAL procedure to work out what it's doing.
Your most likely task is to compare the TZ definition files provided in the kit with those on your system. Merge in any changes (or just replace the files) and recompile them (sorry, I don't have a VAX available at the moment to look into the kit file and see how it works)
HP doesn't support V7.2, so you're on your own, unless you want to engage (ie: pay for) the services of an independent consultant.