VLF-ONE Import / Export iSeries

[jyoung]

Ok, so we are working through getting an Import/Export process on the iSeries working and having some trouble.

After development is complete, I have created a save file on our DEV iSeries and export all the objects associated with the Task to that save file.
If I look in that save file with DSPSAVF I can see the server objects, but I don't see the client side objects (External Resources, Resuable Parts, etc.).
*** SEE EDIT BELOW ****

When we move the file to our PROD iSeries and import it, the import does two things:

1. It issues a message "Where to put the data base files"
2. It does not seem to import the client side objects

Regarding the first point, we answer the message with DCXMODLIB. ( We can discuss this later)
Regarding the second point, the import says it completed, but the application appears to have not been updated.

Here is a pic of the end of the spooled file.

Capture.PNG (43.07 KiB) Viewed 8601 times

Here is a pic of the export list, this SHOULD BE IN THE SAVE FILE

Capture2.PNG (32.95 KiB) Viewed 8601 times

Here is a partial pic of the save file.

Capture3.PNG (33.14 KiB) Viewed 8601 times

I don't understand why the import is not bringing over the client side objects.

EDIT
Inside the save file is another save file; EL_MGS0054. LANSA appears to have created this and after some digging around, we discovered that the JS
and client side files are in that save file.

So I am thinking now, do the SubSystems and HTTP Server need to be restarted after an Import?

EDIT
Looking on the production server (where the import took place) in LANSA_dcxpgmlib/x_lansa/x_SYS/execute I don't see the updated the VLF Data and Definition file (External Resources). I also don't see the new Resuable Parts JS files in LANSA_dcxpgmlib/x_lansa/x_SYS/web/vl.
So this tells me that for some reason the save file EL_MGS0054 in the save file was not extracted ... ?

[MarkDale]

For external resources, if you want the object to be created on import, you have to specify Compiled Form=Y for that object, on the export. If that flag is set, it should recreate the object in the target environment.

To avoid the message about the library, on import, you can use an export setting called Define Substitution variables - if you set $$DTALIB$$ to *PARTDTALIB, and Prompt User = Y. the import message will not appear.

[jyoung]

Ok, but in Capture 2, it shows the COMP FORM to be 'Y' as does all the reusable parts.
So they should have been extracted right?

EDIT

Ok, I see how to set the substitution variable.

[MarkDale]

It should work. Check that you are looking in the location where it should be. If its not, its probably a problem for support.

[jyoung]

I've double checked the locations, created a new save file and repeated the processes and still the VLF-ONE components are not getting imported.

I have contacted support for help. Will update when I have more info.

Thanks,
Joe

[jyoung]

Hey All, I wanted to bump this back up.

I've contacted support and am waiting to hear back what the "official recommended guidance" is for deploying VLF-ONE apps to the iSeries.

I've done some digging in the docs and found this. http://docs.lansa.com/14/en/lansa048/in ... e_0010.htm I don't recall seeing it before. Don't know if it was added recently or if I just missed it. I likely missed it.

However this causes me an IMMENSE amount of concern.

Reading through the steps of this, I have to:

• create 3 save files
• add the framework definition to a save file
• add the framework components to a save file
• add the server side components to a save file
• put all three save files in another save file
• move save file to production
• extract save file
• restore framework definition from save file
• restore framework components from save file
• restore server side components from save file

I find this to be VERY ERROR PRONE. Not to mention, without another LANSA install, we have no way to test this to see if we did not do something or type something wrong, like include the wrong component because we typed I instead of 1.

Is anyone else deploying VLF-ONE to production? Are you moving compiled components from a DEV iSeries to a PRODUCTION iSeries?

How are you doing it?

Edit

I ran into this doc here http://docs.lansa.com/14/en/lansa047/in ... eribmi.htm and it echos much of the above.

I really don't understand why all this is necessary and why the normal Export / Import does not work.