Does the handler call the RPG app and keep it open?
Posted: Tue Aug 03, 2010 10:46 am
Question:
When the user launches an app does that handler call the RPG app and then keep it open until the user exits? Simulating a typical 5250 session?
Answer:
Yes, when the user launches an app, our session controller calls the RPG application, which remains active in a dedicated job -- much like a 5250 session. When the RPG program, for example, is waiting on screen input (i.e. EXFMT), it will actually suspend at that point until the user submits the browser screen. This allows both for accurate conversion of existing applications, and also for new development within a familiar programming model.
When the user launches an app does that handler call the RPG app and then keep it open until the user exits? Simulating a typical 5250 session?
Answer:
Yes, when the user launches an app, our session controller calls the RPG application, which remains active in a dedicated job -- much like a 5250 session. When the RPG program, for example, is waiting on screen input (i.e. EXFMT), it will actually suspend at that point until the user submits the browser screen. This allows both for accurate conversion of existing applications, and also for new development within a familiar programming model.