Hi everyone.
I hope you don't mind me posting a SCL problem here.
For the past few weeks I have been working on an SCL application (Mainframe OS390). A 'simple' database with various bells and whistles on.
I have now run into a wee problem.
One of the programs has a field on it that kicks of another program when the field value is changed to 'Y'.
The problem is that I when alter the field and hit the enter key the MAIN does not seem to execute. However, when I hit the enter key for the second time, it does. In fact, when I hit any other 'function' key after the enter the first enter seems to execute.
e.g alter field to 'Y', hit enter, hit enter again.
or alter field to 'Y', hit enter, hit 'F'whatever.
I have made sure that 'Control Enter' is specified in the INIT. And once you have returned back from the 2nd program screen the field interface, on the 1st program screen, works as intended. The problem only occurs the first time that you enter the 1st program.
The really bizarre thing is that the error does not occur in debug mode so the program appears to be working ok.
Has anyone seen anything like this before.
Thank you for reading.
Best Regards.
I hope you don't mind me posting a SCL problem here.
For the past few weeks I have been working on an SCL application (Mainframe OS390). A 'simple' database with various bells and whistles on.
I have now run into a wee problem.
One of the programs has a field on it that kicks of another program when the field value is changed to 'Y'.
The problem is that I when alter the field and hit the enter key the MAIN does not seem to execute. However, when I hit the enter key for the second time, it does. In fact, when I hit any other 'function' key after the enter the first enter seems to execute.
e.g alter field to 'Y', hit enter, hit enter again.
or alter field to 'Y', hit enter, hit 'F'whatever.
I have made sure that 'Control Enter' is specified in the INIT. And once you have returned back from the 2nd program screen the field interface, on the 1st program screen, works as intended. The problem only occurs the first time that you enter the 1st program.
The really bizarre thing is that the error does not occur in debug mode so the program appears to be working ok.
Has anyone seen anything like this before.
Thank you for reading.
Best Regards.