×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
When you try to connect as QSECOFR are you select iseries user id or is
it
still looking for a ldap id?
At that point it was not using ldap, it appeared to be a straight AS/400
profile/password combination. I think I've fixed this. It appears that
the wizard was launching a job with the user profile of QDIRSRV, and this
profile did not have access to a number of libraries. I fixed the library
authorities and it still wouldn't run. I used the "unconfigure" option
under Network-->Servers-->TCP/IP-->IBM Directory Server-->(Right Click)
Properties. The EIM wizard then ran without a problem.
From there I was able to create my source and target identifiers, but now
I'm running into error message CWBSY1017 - rc=612. That would mean that
the password for the secret key on the KDC does not match the password
provided when running the Network Authentication Service wizard that
created the key. I could almost buy into that, but I used the batch file
created by the wizard to create the KDC entries. Since I selected the
option to include the passwords in the batch file, I don't see how there
could be a difference.
At least the "Test a Mapping" option shows that I'm getting matchups
between the network and iSeries ids. At this point I'm going to wait
until Monday when the network admin and I can call into IBM and figure out
where to go from here.
midrange.com
