Ok I have a reproducable behavior figured out. The reason the one reort was working is becasue it was developed under a different
IBM account. I confirmed it was locking that acocount when the report file is opened in logicity then when I changed the login to an enabled account that was not the default account it worked.
Here is a step by step breakdown
Connection type 32 bit ODBC IBM-Iseries Access ODBC v13.00.01.00
1.) Report is developed in Crystal XI using IBM user account "A" and saved
2.) Report file is opened using Logicity and a default login prompt for IBM account "A" is presented by logicity
3.) The Logicity prompt seems to lock IBM account "A"
4.) Change the logicity login prompt to an enabled IBM account "B" and the report runs fine
This also works
1.) Report is developed in Crystal XI using IBM user account "A" and saved
2.) Report file is opened using Logicity and a default login prompt for IBM account "A" is presented by logicity
3.) The Logicity prompt seems to lock IBM account "A"
4.) Login to IBM server and re-enable IBM account "A"
5.) complete login to logicity with IBM account "A" and report runs fine
Why is logicity locking the default IBM account that it prompts for login? There seems to be no way to prevent it, it locks as soon as the file is opened.