VLF-ONE iSeries Deployment Oddities

[jyoung]

I've deployed the beginnings of our VLF-ONE framework to our dev server that is an IBM i Series.

I am noticing a few oddities as compared to the local version that I don't really understand.

First off, I've included the VLFONE_Engine.js file and locally it works great, on the iSeries however it can't be found.

missing engine.png (33.13 KiB) Viewed 9602 times

I don't know if the install goofed up or what, but when I look in '/LANSA_dcxpgmlib/x_lansa/x_sys/web/vl' its not there. I can copy that file up there to get it to work, but that seems like a hack to something that broke.

Secondly, locally the Filter/Instance List and Command Handler Window position is remembered whereas when running on the iSeries it is not. For example, locally I enabled "Automatic Tiling" and "Arrange Vertically" and every time I execute that object, either in a new window, tab or the same tab, the windows are in the same place. On the iSeries, when I open a new tab or browser, the Filter/Instance list always shows up maximized and the command windows is always on the bottom.

Lastly, while I am planning on implementing my own LOGON handler, I am using UF_OLOGON at the moment with Framework Authority disabled. Locally, I can put anything in the username and password and get in, however on the iSeries I MUST use a valid iSeries username and profile. Is this by design? I had expected the same behavior on both systems, so was surprised by it automatically requiring me to use a valid username and password.

Has anyone else experienced these things or is it just me.

[jyoung]

Regarding the window position issues, once I shut down ALL the browsers (even the hidden Chrome ones) and tried it again, it seems it remembers their positions now.

[MarkDale]

I am assuming you are using VLF epc141017, since the VLFONE_Engine.js is quite a recent feature.

And I'm assuming VLF epc141017 has also been installed on the iSeries.

I just checked that the partition initialize on the iSeries does install VLFONE_Engine.js, so it would be worth checking whether the vf_* js files on the iSeries for the partition you are working with are up to date.

As a direct check, on the iSeries IFS, the \LANSA_pgmlib\x_lansa\x_PPP\web\vl directory should contain vf_*.js with the same modified dates as the equivalent directory on your PC.

(where PPP is the partition you are working with)

If they are not up to date
1. Check that epc141017 has been installed on the iSeries
(On the iSeries start lansa for your partition --> Administration tasks --> Settings --> General --> F10 (Logs))
2. Initialize the partitition (Administration tasks --> Initialize partition --> VLFBASE)

[MarkD]

Regarding - Locally, I can put anything in the username and password and get in, however on the iSeries I MUST use a valid iSeries username and profile. Is this by design?

Yes - the example UF_OLOGON you are using contains code to validate IBM i user profiles and passwords.

If you make your own copy and snap it in you can change that behaviour.

[MarkD]

Regarding saved positions and sizes - this tip From Patrick indicates hwo you can see what is being saved - http://vlforum.lansa.com.au/viewtopic.php?f=4&t=1202

[jyoung]

Yeah, we installed 141017 but we did not re-initialize the partition.

I checked the IFS files and sure enough the modified dates are different.

Capture.PNG (47.6 KiB) Viewed 9577 times

Whereas on my PC they are dated 2/2/2017.

I checked the logs and it is installed, we had some issues getting it installed but support helped us get it done.

I did not realize we had to (or forgot to) re-initialize the partition.

I should have checked UF_OFLOGN first and would have realized it was authenticating users on the iSeries.

Thanks.