Re: Adoption of RPG OA (Summary)

For those who've not looked at the OA documentation, there is a data structure passed to the handler. It contains a subfield for rrn - this can be set by either RPG or the handler. There are also pointers to the 3 file feedback areas. AID bytes can be set there, for example.

The only thing we can affect directly in PSDS is the RPG status code, as I remember. So far!

If a handler needs some kind of pseudo-cursor handling, it can keep that in a stateful information structure whose pointer goes back to RPG and is handed back again on successive calls of the handler.

WINGS uses the ASNA Monarch architecture - based on ASP.Net objects that are generated from something on the IBM i, so far as I know. Then developers work mostly with the ASP code.

That's about all I know - and actually a little more than I know, probably. Maybe they ignore cursor position or replace it with something to achieve the same end. I find that the details deep down are almost irrelevant - the key thing is to understand top-level behavior - that has let me write a DISK-style handler and cover everything with it. Basically, make it behave at the programmer's level of use the same as it does in native RPG IO, then it's all good.

Regards
Vern

On 3/18/2011 1:07 PM, Joe Pluta wrote:

How in the world does WINGS handle things like cursor position in the PSDS?

Joe

We are using ASNA WINGS, and it is true, other than best practice for the
HANDLER keyword, I don't need YALL/YINS much.
ALL of the rest of our work will be done in VS2010. Java Script HTML Code
behind language, deployment, manage projects in the studio.
We are hoping to leave the RPG untouched except for the HANDLER keyword.

Tom Deskevich
No stupid salutation