We do not have single-sign-on, and have an iSeries user profile named "AM2000" that also exists on our network. Historically, by compiling CL programs as AM2000 with USRPRF(*OWNER), any user could execute the program and access network files "as AM2000". Something has changed (possibly moving from V5R3 to V5R4, possibly something else), and now compiling CL programs this way no longer works; the executing user gets an error that HIS profile name is not recognized by the network. Does anyone know what has happened, and/or how we can fix it? I'm aware that I can submit a job to run "as AM2000", but we have dozens of programs in question and I would hate to have to rewrite all of them. Thanks in advance!
October 9, 2009 3:48 PM
October 28, 2009 3:09 PM