Did anyone have signon or authority issues after upgrading to 6.2.1 from 6.1.4?
When I was testing V6.1.4 I had created a user profile EDI614USER, where the
"Initial Program to call" was EDI614PGM/CED000.
The user profile called up the main menu for the server (AS/400) and client.
When I submitted our daily EDI job using ROBOT the job ran ok and successfully.
After I upgraded to V6.2.1 I changed my user profile EDI614USER to call
"Initial Program to call" was EDI614PGMN/CED000........where EDI614PGMN was my
upgraded 6.2.1 library. I cannot submit the daily EDI job using Robot and when
I try to sign on with user profile EDI614USER & password, to the server or the
client I keep getting the signon screen.......with no interactive joblog. Our
system is suppose to automatically disable the signon screen after 3 failed
attempts. This does not happen. I am working with Inovis support also. Can
anyone help?