AS400 rpg program 36/LE conflict question
I'm going to ask this question in a very general way... in case it is a well know issue. If backup is needed then I will post it.
I have a 36 program which calls a CL with a number of variables. The CL executes a RPGLE program and displays a window for verification. Then the control returns to the 36 program with an error flag set if necessary. Then 36 program re-shows the screen. When the screen is re-shown all the constants on the 36 screen are gone. Even without any logic in the call program this happens.... just displaying the window will cause the 36 program to display correctly even though all other aspects of the program are exactly the same.
I posted a screen cast for example. First one the constants are retained on the second (after window) they are not.
Thank you.
lynn-harris-541567.flv
I have a 36 program which calls a CL with a number of variables. The CL executes a RPGLE program and displays a window for verification. Then the control returns to the 36 program with an error flag set if necessary. Then 36 program re-shows the screen. When the screen is re-shown all the constants on the 36 screen are gone. Even without any logic in the call program this happens.... just displaying the window will cause the 36 program to display correctly even though all other aspects of the program are exactly the same.
I posted a screen cast for example. First one the constants are retained on the second (after window) they are not.
Thank you.
lynn-harris-541567.flv
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I've done some S36 Env development work over the years, but not a lot. Maybe one of the other experts with more S36 Env experience has a better idea.
- Gary
- Gary
ASKER
Thanks Gary.
I got it working with the internal screens... just a lot of jumping through hoops. Ugly stuff.
I got it working with the internal screens... just a lot of jumping through hoops. Ugly stuff.
ASKER
The screens are program-described. RSTDSP(*YES) is our default setting for externally described. I tried a couple variations of buffering the data and writing a screen with only the constants first upon return. I change the window to one that is working in another 36 program with internally described screens (just for testing purposed). No success with anything. It is in the 36 somewhere... 36 is not my strong suit (to say the least).
I will give making the screens externally described a try. (Wish I had time to rewrite!)