MKlehm
Member
Hello All,
We are having the following BIG issue:
When users sign on to the "W" environment (BSFNs mapped to run on AS/400) on Terminal Server, they get Address Book Invalid and Data Dictionary Invalid errors on any application that uses A/B as part of the MBF data structure. We've debugged the applications and can see that in the middle of a MBF, it is inadvertantly calling the next number routine and passing the next number into the address field, and that is why the users are seeing this error. So, this looks like a data dictionary trigger issue, right? We've verified the DD attributes, deleted all the appropriate DD spec files on the AS/400 to make them re-jiti down, but this didn't work. We tried running the old B733.1 process of R98TAM to rebuild the DD spec files on the AS/400, but this didn't work either. Also, we've rebuilt and deployed a full package to the AS/400, but once again, no luck.
This only happens when the BSFNs are running on the AS/400. If they are running locally, either on fat client or Terminal Server, no error is received.
Has anyone seen this before?
AS400, Xe, Update 6, SP20
Mike
We are having the following BIG issue:
When users sign on to the "W" environment (BSFNs mapped to run on AS/400) on Terminal Server, they get Address Book Invalid and Data Dictionary Invalid errors on any application that uses A/B as part of the MBF data structure. We've debugged the applications and can see that in the middle of a MBF, it is inadvertantly calling the next number routine and passing the next number into the address field, and that is why the users are seeing this error. So, this looks like a data dictionary trigger issue, right? We've verified the DD attributes, deleted all the appropriate DD spec files on the AS/400 to make them re-jiti down, but this didn't work. We tried running the old B733.1 process of R98TAM to rebuild the DD spec files on the AS/400, but this didn't work either. Also, we've rebuilt and deployed a full package to the AS/400, but once again, no luck.
This only happens when the BSFNs are running on the AS/400. If they are running locally, either on fat client or Terminal Server, no error is received.
Has anyone seen this before?
AS400, Xe, Update 6, SP20
Mike