×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
When we compile in development (at V5R4), we use MKS's Implementer to
promote the programs into production.
Whenever we upgrade development our development LPAR, I change the
process to compile it to the *PRV target release until production is
upgraded. I have not had any issues thus far with anything.
I do not expect any issues from programs promotions from development to
production. Once again, if all program objects pass the ANZOBJCNV test,
then I am confident that we should be ok.
As long as you have everything working for V5R1 or greater, you should
be ok.
iTera has their own V6R1 Audit that can be run as well.
I am going to compare the results with IBM's to see if there are any
issues.
Thanks.
James Salter
Systems Programmer
American Cast Iron Pipe Co
Email: jsalter@xxxxxxxxxx
------------------------------
message: 7
date: Tue, 6 May 2008 15:52:52 -0400
from: rob@xxxxxxxxx
subject: Re: V6R1 in A HA environment
Is your development lpar part of your HA cluster? If so, and you
compile
program XYZ123 for TGTRLS(*CURRENT) how will it go to your HA machine?
If
you compile it TGTRLS(*PRV) and run STROBJCVN on it do you expect any
audit issues because the attribute will be different on one machine than
the other?
We're relatively new to HA.
One, this will be our first OS upgrade since implementing HA.
Two, then obviously we didn't have this running the last time STROBJCVN
was a concern (CISC-to-RISC).
Of course, we won't upgrade before ANZOBJCVN passes with flying colors.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.