Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.



Upgrade 7.1 to 7.5. VersionSequence help. MaxUpgVersion: V71110-16.

From: alwin borda (2012-10-22 19:52)

Good afternoon, I'm writing regarding an error during a database migration.
I'm migrating a database from Maximo 5.2 to Maximo 7.5. I'm running Windows server 2008 64bit and SQL Server 2008R2. Currently, the database version is 7.1.1.10, and the updatebd has already been executed. I have successfully installed version 7.5, applied patch 7.5.0.2 and imported database 7.1.1.10. I have also run upgradeui.bat and the integrity has no errors. But when I try to execute the validation, the following error pops up:
MaxUpgVersion: V71110-16
BMXAA6940W - Information about the version was not found in the product description files.
java.lang.Exception: BMXAA8279I - Upgrade and upgrade validation are not supported for version V71110-16.
at psdi.configure.Validate.getCalloutSubdir(Validate.java:12624)
at psdi.configure.Validate.endSetupInstance(Validate.java:14000)
at psdi.configure.CommonShell.endSetup(CommonShell.java:1686)
at psdi.configure.CommonShell.setup(CommonShell.java:1198)
at psdi.configure.Validate.setup(Validate.java:14213)
at psdi.configure.Validate.main(Validate.java:14498)
BMXAA6849I - Validate completed with errors. Mon Oct 22 14:41:11 ART 2012
BMXAA6850I - Validate completed. Mon Oct 22 14:41:11 ART 2012
Validate.class:
public String getCalloutSubdir(String calloutDir, String versionStamp)
throws Exception
{
SAXBuilder builder = new SAXBuilder(false);
builder.setFactory(new ConfigXMLFactory(calloutDir));
Document versionDoc = builder.build((new StringBuilder()).append(calloutDir).append(File.separator).append("VersionSequence.xml").toString());
Element versionRoot = versionDoc.getRootElement();
Element version = getVersionRecord(versionRoot, versionStamp);
if(version == null)
{
if(messageCache.containsKey("upgradeNS"))
{
String params[] = {
maxUpgVersion
};
String msg = getDisplayMessage("upgradeNS", params);
throw new Exception(msg);
} else
{
throw new Exception((new StringBuilder()).append("BMXAA8279I - Upgrade and upgrade validation are not supported for version ").append(maxUpgVersion).append(".").toString());
}
} else
{
return version.getAttributeValue("dir");
}
}
VersionSequence.sql:
<document docid="VersionSequence">
<VERSION versionnum="V600-768 09/24/2010" dir="V600"/>
<VERSION versionnum="V7100-001 4/2/2008" dir="V7100"/>
</document>
C:\ibm\SMP\maximo\tools\maximo\classes\psdi\upgrade
22/10/2012 01:09 p.m. <DIR> .
22/10/2012 01:09 p.m. <DIR> ..
20/07/2011 05:27 p.m. 6.479 BuildDiff.class
20/07/2011 05:27 p.m. 25.341 BuildUpgMetadata.class
19/02/2012 10:00 p.m. 18.732 Diff.class
20/07/2011 05:29 p.m. 15.625 DifferenceReport.class
20/07/2011 05:31 p.m. 8.327 MetaDocData.class
10/10/2012 02:25 p.m. <DIR> product
20/07/2011 05:27 p.m. 1.039 RichTextMigration$MigrationFlag.class
20/07/2011 05:32 p.m. 16.646 RichTextMigration.class
20/07/2011 05:30 p.m. 2.731 screenupgrade.properties
20/07/2011 05:32 p.m. 47.777 ScrubCustomDatabase.class
20/07/2011 05:32 p.m. 11.896 UninstallMIG.class
20/07/2011 05:28 p.m. 650 UpgCodesEditor$EdButton.class
20/07/2011 05:27 p.m. 672 UpgCodesEditor$EdLabel.class
20/07/2011 05:29 p.m. 1.583 UpgCodesEditor$EdList.class
20/07/2011 05:31 p.m. 1.155 UpgCodesEditor$EdListener.class
20/07/2011 05:27 p.m. 687 UpgCodesEditor$EdPanel.class
20/07/2011 05:36 p.m. 500 UpgCodesEditor$EdTextField.class
20/07/2011 05:26 p.m. 18.274 UpgCodesEditor.class
20/07/2011 05:33 p.m. 2.360 upgmessages.properties
20/07/2011 05:37 p.m. 576 Upgrade$BasicFileNameFilter.class
19/02/2012 10:00 p.m. 80.630 Upgrade.class
20/07/2011 05:34 p.m. 8.931 UpgradeScreens.class
22/10/2012 01:09 p.m. <DIR> V600
10/10/2012 02:25 p.m. <DIR> V600_609
10/10/2012 02:25 p.m. <DIR> V600_662
10/10/2012 02:25 p.m. <DIR> V7100
10/10/2012 02:22 p.m. <DIR> V7110
10/10/2012 02:25 p.m. <DIR> V7117
10/10/2012 02:25 p.m. <DIR> V7118
10/10/2012 02:25 p.m. <DIR> V7500
20/07/2011 05:33 p.m. 203 VersionSequence.xml
22 archivos 270.814 bytes
11 dirs 7.063.367.680 bytes libres
Variables on table maxvars are:
DBVERSION 146
INTEGRITYDBKEY 5215259
DB2URFORVIEWS 0
DBITSME V600-10
DBCOMMON_PMP V7117-2
INTEGRITYDBVERSION 146
EAMUPG V7100-001
MAXUPG V71110-16
UPGRADE V600-0
I apologize for the e-mail's extension, I tried to add all the information that could be helpful.
Thank you in advance.
Looking forward to hearing from you soon.
Regards
Alwin.


From: Hanna, Christopher CTR (2012-10-23 08:49)

Mx75 upgrade does not care about the pass or fail status of the integrity check or validation. Double check to be sure that you're path is supported (7110 - 7502) as I saw several contradictory pieces of information from IBM on upgrade path during my upgrade from 7118 - 7503. If you have 7502 installed on your app server and it is pointed at the 7110 DB, you 'should' be able to simply run updatedb to bring the DB up to 7502.

-Chris H

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of alwin borda
Sent: Monday, October 22, 2012 3:52 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Upgrade 7.1 to 7.5. VersionSequence help. MaxUpgVersion: V71110-16.


Good afternoon, I'm writing regarding an error during a database migration.
I'm migrating a database from Maximo 5.2 to Maximo 7.5. I'm running Windows server 2008 64bit and SQL Server 2008R2. Currently, the database version is 7.1.1.10, and the updatebd has already been executed. I have successfully installed version 7.5, applied patch 7.5.0.2 and imported database 7.1.1.10. I have also run upgradeui.bat and the integrity has no errors. But when I try to execute the validation, the following error pops up:
MaxUpgVersion: V71110-16
BMXAA6940W - Information about the version was not found in the product description files.
java.lang.Exception: BMXAA8279I - Upgrade and upgrade validation are not supported for version V71110-16.
at psdi.configure.Validate.getCalloutSubdir(Validate.java:12624)
at psdi.configure.Validate.endSetupInstance(Validate.java:14000)
at psdi.configure.CommonShell.endSetup(CommonShell.java:1686)
at psdi.configure.CommonShell.setup(CommonShell.java:1198)
at psdi.configure.Validate.setup(Validate.java:14213)
at psdi.configure.Validate.main(Validate.java:14498)
BMXAA6849I - Validate completed with errors. Mon Oct 22 14:41:11 ART 2012
BMXAA6850I - Validate completed. Mon Oct 22 14:41:11 ART 2012
Validate.class:
public String getCalloutSubdir(String calloutDir, String versionStamp)
throws Exception
{
SAXBuilder builder = new SAXBuilder(false);
builder.setFactory(new ConfigXMLFactory(calloutDir));
Document versionDoc = builder.build((new StringBuilder()).append(calloutDir).append(File.separator).append("VersionSequence.xml").toString());
Element versionRoot = versionDoc.getRootElement();
Element version = getVersionRecord(versionRoot, versionStamp);
if(version == null)
{
if(messageCache.containsKey("upgradeNS"))
{
String params[] = {
maxUpgVersion
};
String msg = getDisplayMessage("upgradeNS", params);
throw new Exception(msg);
} else
{
throw new Exception((new StringBuilder()).append("BMXAA8279I - Upgrade and upgrade validation are not supported for version ").append(maxUpgVersion).append(".").toString());
}
} else
{
return version.getAttributeValue("dir");
}
}
VersionSequence.sql:
<document docid="VersionSequence">
<VERSION versionnum="V600-768 09/24/2010" dir="V600"/>
<VERSION versionnum="V7100-001 4/2/2008" dir="V7100"/>
</document>
C:\ibm\SMP\maximo\tools\maximo\classes\psdi\upgrade
22/10/2012 01:09 p.m. <DIR> .
22/10/2012 01:09 p.m. <DIR> ..
20/07/2011 05:27 p.m. 6.479 BuildDiff.class
20/07/2011 05:27 p.m. 25.341 BuildUpgMetadata.class
19/02/2012 10:00 p.m. 18.732 Diff.class
20/07/2011 05:29 p.m. 15.625 DifferenceReport.class
20/07/2011 05:31 p.m. 8.327 MetaDocData.class
10/10/2012 02:25 p.m. <DIR> product
20/07/2011 05:27 p.m. 1.039 RichTextMigration$MigrationFlag.class
20/07/2011 05:32 p.m. 16.646 RichTextMigration.class
20/07/2011 05:30 p.m. 2.731 screenupgrade.properties
20/07/2011 05:32 p.m. 47.777 ScrubCustomDatabase.class
20/07/2011 05:32 p.m. 11.896 UninstallMIG.class
20/07/2011 05:28 p.m. 650 UpgCodesEditor$EdButton.class
20/07/2011 05:27 p.m. 672 UpgCodesEditor$EdLabel.class
20/07/2011 05:29 p.m. 1.583 UpgCodesEditor$EdList.class
20/07/2011 05:31 p.m. 1.155 UpgCodesEditor$EdListener.class
20/07/2011 05:27 p.m. 687 UpgCodesEditor$EdPanel.class
20/07/2011 05:36 p.m. 500 UpgCodesEditor$EdTextField.class
20/07/2011 05:26 p.m. 18.274 UpgCodesEditor.class
20/07/2011 05:33 p.m. 2.360 upgmessages.properties
20/07/2011 05:37 p.m. 576 Upgrade$BasicFileNameFilter.class
19/02/2012 10:00 p.m. 80.630 Upgrade.class
20/07/2011 05:34 p.m. 8.931 UpgradeScreens.class
22/10/2012 01:09 p.m. <DIR> V600
10/10/2012 02:25 p.m. <DIR> V600_609
10/10/2012 02:25 p.m. <DIR> V600_662
10/10/2012 02:25 p.m. <DIR> V7100
10/10/2012 02:22 p.m. <DIR> V7110
10/10/2012 02:25 p.m. <DIR> V7117
10/10/2012 02:25 p.m. <DIR> V7118
10/10/2012 02:25 p.m. <DIR> V7500
20/07/2011 05:33 p.m. 203 VersionSequence.xml
22 archivos 270.814 bytes
11 dirs 7.063.367.680 bytes libres
Variables on table maxvars are:
DBVERSION 146
INTEGRITYDBKEY 5215259
DB2URFORVIEWS 0
DBITSME V600-10
DBCOMMON_PMP V7117-2
INTEGRITYDBVERSION 146
EAMUPG V7100-001
MAXUPG V71110-16
UPGRADE V600-0
I apologize for the e-mail's extension, I tried to add all the information that could be helpful.
Thank you in advance.
Looking forward to hearing from you soon.
Regards
Alwin.


From: alwin borda (2012-10-23 19:41)

I thought that the normal steps to update from 7.1 to 7.5 were integrity, validate and upgrade. But thanks to your answer I was able to fix the erros before running the updatebd. It is my understanding that by doing this the migration is completed. Thanks you for your answer.
Regards
--- In MAXIMO@yahoogroups.com, "Hanna, Christopher CTR" <christopher.a.hanna@...> wrote:
>
> Mx75 upgrade does not care about the pass or fail status of the integrity check or validation. Double check to be sure that you're path is supported (7110 - 7502) as I saw several contradictory pieces of information from IBM on upgrade path during my upgrade from 7118 - 7503. If you have 7502 installed on your app server and it is pointed at the 7110 DB, you 'should' be able to simply run updatedb to bring the DB up to 7502.
>
>
>
> -Chris H
>
>
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of alwin borda
> Sent: Monday, October 22, 2012 3:52 PM
> To: MAXIMO@yahoogroups.com
> Subject: [MAXIMO List] Upgrade 7.1 to 7.5. VersionSequence help. MaxUpgVersion: V71110-16.
>
>
>
>
>
> Good afternoon, I'm writing regarding an error during a database migration.
> I'm migrating a database from Maximo 5.2 to Maximo 7.5. I'm running Windows server 2008 64bit and SQL Server 2008R2. Currently, the database version is 7.1.1.10, and the updatebd has already been executed. I have successfully installed version 7.5, applied patch 7.5.0.2 and imported database 7.1.1.10. I have also run upgradeui.bat and the integrity has no errors. But when I try to execute the validation, the following error pops up:
>
> MaxUpgVersion: V71110-16
> BMXAA6940W - Information about the version was not found in the product description files.
> java.lang.Exception: BMXAA8279I - Upgrade and upgrade validation are not supported for version V71110-16.
> at psdi.configure.Validate.getCalloutSubdir(Validate.java:12624)
> at psdi.configure.Validate.endSetupInstance(Validate.java:14000)
> at psdi.configure.CommonShell.endSetup(CommonShell.java:1686)
> at psdi.configure.CommonShell.setup(CommonShell.java:1198)
> at psdi.configure.Validate.setup(Validate.java:14213)
> at psdi.configure.Validate.main(Validate.java:14498)
> BMXAA6849I - Validate completed with errors. Mon Oct 22 14:41:11 ART 2012
> BMXAA6850I - Validate completed. Mon Oct 22 14:41:11 ART 2012
>
> Validate.class:
> public String getCalloutSubdir(String calloutDir, String versionStamp)
> throws Exception
> {
> SAXBuilder builder = new SAXBuilder(false);
> builder.setFactory(new ConfigXMLFactory(calloutDir));
> Document versionDoc = builder.build((new StringBuilder()).append(calloutDir).append(File.separator).append("VersionSequence.xml").toString());
> Element versionRoot = versionDoc.getRootElement();
> Element version = getVersionRecord(versionRoot, versionStamp);
> if(version == null)
> {
> if(messageCache.containsKey("upgradeNS"))
> {
> String params[] = {
> maxUpgVersion
> };
> String msg = getDisplayMessage("upgradeNS", params);
> throw new Exception(msg);
> } else
> {
> throw new Exception((new StringBuilder()).append("BMXAA8279I - Upgrade and upgrade validation are not supported for version ").append(maxUpgVersion).append(".").toString());
> }
> } else
> {
> return version.getAttributeValue("dir");
> }
> }
>
> VersionSequence.sql:
> <document docid="VersionSequence">
> <VERSION versionnum="V600-768 09/24/2010" dir="V600"/>
> <VERSION versionnum="V7100-001 4/2/2008" dir="V7100"/>
> </document>
>
> C:\ibm\SMP\maximo\tools\maximo\classes\psdi\upgrade
> 22/10/2012 01:09 p.m. <DIR> .
> 22/10/2012 01:09 p.m. <DIR> ..
> 20/07/2011 05:27 p.m. 6.479 BuildDiff.class
> 20/07/2011 05:27 p.m. 25.341 BuildUpgMetadata.class
> 19/02/2012 10:00 p.m. 18.732 Diff.class
> 20/07/2011 05:29 p.m. 15.625 DifferenceReport.class
> 20/07/2011 05:31 p.m. 8.327 MetaDocData.class
> 10/10/2012 02:25 p.m. <DIR> product
> 20/07/2011 05:27 p.m. 1.039 RichTextMigration$MigrationFlag.class
> 20/07/2011 05:32 p.m. 16.646 RichTextMigration.class
> 20/07/2011 05:30 p.m. 2.731 screenupgrade.properties
> 20/07/2011 05:32 p.m. 47.777 ScrubCustomDatabase.class
> 20/07/2011 05:32 p.m. 11.896 UninstallMIG.class
> 20/07/2011 05:28 p.m. 650 UpgCodesEditor$EdButton.class
> 20/07/2011 05:27 p.m. 672 UpgCodesEditor$EdLabel.class
> 20/07/2011 05:29 p.m. 1.583 UpgCodesEditor$EdList.class
> 20/07/2011 05:31 p.m. 1.155 UpgCodesEditor$EdListener.class
> 20/07/2011 05:27 p.m. 687 UpgCodesEditor$EdPanel.class
> 20/07/2011 05:36 p.m. 500 UpgCodesEditor$EdTextField.class
> 20/07/2011 05:26 p.m. 18.274 UpgCodesEditor.class
> 20/07/2011 05:33 p.m. 2.360 upgmessages.properties
> 20/07/2011 05:37 p.m. 576 Upgrade$BasicFileNameFilter.class
> 19/02/2012 10:00 p.m. 80.630 Upgrade.class
> 20/07/2011 05:34 p.m. 8.931 UpgradeScreens.class
> 22/10/2012 01:09 p.m. <DIR> V600
> 10/10/2012 02:25 p.m. <DIR> V600_609
> 10/10/2012 02:25 p.m. <DIR> V600_662
> 10/10/2012 02:25 p.m. <DIR> V7100
> 10/10/2012 02:22 p.m. <DIR> V7110
> 10/10/2012 02:25 p.m. <DIR> V7117
> 10/10/2012 02:25 p.m. <DIR> V7118
> 10/10/2012 02:25 p.m. <DIR> V7500
> 20/07/2011 05:33 p.m. 203 VersionSequence.xml
> 22 archivos 270.814 bytes
> 11 dirs 7.063.367.680 bytes libres
>
> Variables on table maxvars are:
> DBVERSION 146
> INTEGRITYDBKEY 5215259
> DB2URFORVIEWS 0
> DBITSME V600-10
> DBCOMMON_PMP V7117-2
> INTEGRITYDBVERSION 146
> EAMUPG V7100-001
> MAXUPG V71110-16
> UPGRADE V600-0
>
> I apologize for the e-mail's extension, I tried to add all the information that could be helpful.
> Thank you in advance.
> Looking forward to hearing from you soon.
>
> Regards
> Alwin.
>
>
>
>
>
>
>


From: Hanna, Christopher CTR (2012-10-24 07:49)

Yeah, IBM is not really publicizing that the integrity check is no longer in play for 75 upgrades. The only reason I became aware was that we had/have a PMR in for some false positives on the integrity check, and the tech working the PMR told us to just go forward with the upgrade, that the integrity flag would no longer prohibit it from going forward.
Glad it worked out for you!
-Chris H
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of alwin borda
Sent: Tuesday, October 23, 2012 3:41 PM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Upgrade 7.1 to 7.5. VersionSequence help. MaxUpgVersion: V71110-16.

I thought that the normal steps to update from 7.1 to 7.5 were integrity, validate and upgrade. But thanks to your answer I was able to fix the erros before running the updatebd. It is my understanding that by doing this the migration is completed. Thanks you for your answer.
Regards
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Hanna, Christopher CTR" <christopher.a.hanna@...> wrote:
>
> Mx75 upgrade does not care about the pass or fail status of the integrity check or validation. Double check to be sure that you're path is supported (7110 - 7502) as I saw several contradictory pieces of information from IBM on upgrade path during my upgrade from 7118 - 7503. If you have 7502 installed on your app server and it is pointed at the 7110 DB, you 'should' be able to simply run updatedb to bring the DB up to 7502.
>
>
>
> -Chris H
>
>
>
> From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> [mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On
> Behalf Of alwin borda
> Sent: Monday, October 22, 2012 3:52 PM
> To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> Subject: [MAXIMO List] Upgrade 7.1 to 7.5. VersionSequence help. MaxUpgVersion: V71110-16.
>
>
>
>
>
> Good afternoon, I'm writing regarding an error during a database migration.
> I'm migrating a database from Maximo 5.2 to Maximo 7.5. I'm running Windows server 2008 64bit and SQL Server 2008R2. Currently, the database version is 7.1.1.10, and the updatebd has already been executed. I have successfully installed version 7.5, applied patch 7.5.0.2 and imported database 7.1.1.10. I have also run upgradeui.bat and the integrity has no errors. But when I try to execute the validation, the following error pops up:
>
> MaxUpgVersion: V71110-16
> BMXAA6940W - Information about the version was not found in the product description files.
> java.lang.Exception: BMXAA8279I - Upgrade and upgrade validation are not supported for version V71110-16.
> at psdi.configure.Validate.getCalloutSubdir(Validate.java:12624)
> at psdi.configure.Validate.endSetupInstance(Validate.java:14000)
> at psdi.configure.CommonShell.endSetup(CommonShell.java:1686)
> at psdi.configure.CommonShell.setup(CommonShell.java:1198)
> at psdi.configure.Validate.setup(Validate.java:14213)
> at psdi.configure.Validate.main(Validate.java:14498)
> BMXAA6849I - Validate completed with errors. Mon Oct 22 14:41:11 ART
> 2012 BMXAA6850I - Validate completed. Mon Oct 22 14:41:11 ART 2012
>
> Validate.class:
> public String getCalloutSubdir(String calloutDir, String versionStamp)
> throws Exception { SAXBuilder builder = new SAXBuilder(false);
> builder.setFactory(new ConfigXMLFactory(calloutDir)); Document
> versionDoc = builder.build((new
> StringBuilder()).append(calloutDir).append(File.separator).append("Ver
> sionSequence.xml").toString()); Element versionRoot =
> versionDoc.getRootElement(); Element version =
> getVersionRecord(versionRoot, versionStamp); if(version == null) {
> if(messageCache.containsKey("upgradeNS"))
> {
> String params[] = {
> maxUpgVersion
> };
> String msg = getDisplayMessage("upgradeNS", params); throw new
> Exception(msg); } else { throw new Exception((new
> StringBuilder()).append("BMXAA8279I - Upgrade and upgrade validation
> are not supported for version
> ").append(maxUpgVersion).append(".").toString());
> }
> } else
> {
> return version.getAttributeValue("dir"); } }
>
> VersionSequence.sql:
> <document docid="VersionSequence">
> <VERSION versionnum="V600-768 09/24/2010" dir="V600"/> <VERSION
> versionnum="V7100-001 4/2/2008" dir="V7100"/> </document>
>
> C:\ibm\SMP\maximo\tools\maximo\classes\psdi\upgrade
> 22/10/2012 01:09 p.m. <DIR> .
> 22/10/2012 01:09 p.m. <DIR> ..
> 20/07/2011 05:27 p.m. 6.479 BuildDiff.class
> 20/07/2011 05:27 p.m. 25.341 BuildUpgMetadata.class
> 19/02/2012 10:00 p.m. 18.732 Diff.class
> 20/07/2011 05:29 p.m. 15.625 DifferenceReport.class
> 20/07/2011 05:31 p.m. 8.327 MetaDocData.class
> 10/10/2012 02:25 p.m. <DIR> product
> 20/07/2011 05:27 p.m. 1.039 RichTextMigration$MigrationFlag.class
> 20/07/2011 05:32 p.m. 16.646 RichTextMigration.class
> 20/07/2011 05:30 p.m. 2.731 screenupgrade.properties
> 20/07/2011 05:32 p.m. 47.777 ScrubCustomDatabase.class
> 20/07/2011 05:32 p.m. 11.896 UninstallMIG.class
> 20/07/2011 05:28 p.m. 650 UpgCodesEditor$EdButton.class
> 20/07/2011 05:27 p.m. 672 UpgCodesEditor$EdLabel.class
> 20/07/2011 05:29 p.m. 1.583 UpgCodesEditor$EdList.class
> 20/07/2011 05:31 p.m. 1.155 UpgCodesEditor$EdListener.class
> 20/07/2011 05:27 p.m. 687 UpgCodesEditor$EdPanel.class
> 20/07/2011 05:36 p.m. 500 UpgCodesEditor$EdTextField.class
> 20/07/2011 05:26 p.m. 18.274 UpgCodesEditor.class
> 20/07/2011 05:33 p.m. 2.360 upgmessages.properties
> 20/07/2011 05:37 p.m. 576 Upgrade$BasicFileNameFilter.class
> 19/02/2012 10:00 p.m. 80.630 Upgrade.class
> 20/07/2011 05:34 p.m. 8.931 UpgradeScreens.class
> 22/10/2012 01:09 p.m. <DIR> V600
> 10/10/2012 02:25 p.m. <DIR> V600_609
> 10/10/2012 02:25 p.m. <DIR> V600_662
> 10/10/2012 02:25 p.m. <DIR> V7100
> 10/10/2012 02:22 p.m. <DIR> V7110
> 10/10/2012 02:25 p.m. <DIR> V7117
> 10/10/2012 02:25 p.m. <DIR> V7118
> 10/10/2012 02:25 p.m. <DIR> V7500
> 20/07/2011 05:33 p.m. 203 VersionSequence.xml
> 22 archivos 270.814 bytes
> 11 dirs 7.063.367.680 bytes libres
>
> Variables on table maxvars are:
> DBVERSION 146
> INTEGRITYDBKEY 5215259
> DB2URFORVIEWS 0
> DBITSME V600-10
> DBCOMMON_PMP V7117-2
> INTEGRITYDBVERSION 146
> EAMUPG V7100-001
> MAXUPG V71110-16
> UPGRADE V600-0
>
> I apologize for the e-mail's extension, I tried to add all the information that could be helpful.
> Thank you in advance.
> Looking forward to hearing from you soon.
>
> Regards
> Alwin.
>
>
>
>
>
>
>