Level check on VVDTA100 during import

[ThierryC]

Valence51 - version 5.1.20180118.0

i wanted to transfer a query definition i exported from Valence5.0 and do an import in V5.1.; however i now get a level-check on the iSeries.




when doing an import

File VVDTA220 in library VVIMPORT restored.                                
File VVDTA300 in library VVIMPORT restored.                                
File VVDTA400 in library VVIMPORT restored.                                
File VVDTA500 in library VVIMPORT restored.                                
File VVDTA600 in library VVIMPORT restored.                                
File VVDTA900 in library VVIMPORT restored.                                
File VVDTA910 in library VVIMPORT restored.                                
File VVDTA920 in library VVIMPORT restored.                                
12 objecten teruggezet van VVEXPORT naar VVIMPORT.                         
Level check on file VVDTA100 in library VVIMPORT with member VVDTA100.     
Error message CPF4131 appeared during OPEN.                                
Functiefout opgetreden.RNX1217 niet voorzien door VVIMPORT bij             
  programma-instructie 0000027300, systeeminstructie X'0000'.              
The call to INITIATEDA ended in error (C G D F). 

[robert.swanson]

Hi Theirry,

Which version of 5.0 are you exporting from? I suspect it may need to be upgraded to a later version.

[ThierryC]

i'm on the latest version i believe ... 5.0.20170415.0

[robert.swanson]

Hi Thierry,

I did a bit more digging on this and discovered that while it's possible to export widgets and query app definitions from 5.0 to 5.1, there was a substantial change made to the data sources in 5.1 -- hence the level check you're experiencing on VVDTA100 when you try to import from 5.0.

Would it be possible for you to go into your 5.1 Instance Manager and create a special instance just for handling query migrations like these? Then you could use VVMIGRATE to move all your 5.0 Nitro Query definitions into that 5.1 instance, from which you could then cleanly export/import over to your production 5.1 instance.