Progress Statement/Keyword that does not run on Appserver

_uJJwAL_

_uJJwAL_

New Member
I am wondering if there are statement/keywords that does not run on Appserver. I would appreciate if someone could share it in here. I am really looking for statement/keyword that run on either Appserver only or not Appserver at all.

Regards,
Ujjwal
 
Honestly, I think you won't have much luck getting such a keyword list. I doubt that anyone of us has such a list at hand.

IMHO you should focus on functionality instead.

As a rule of thumb:

  • The AppServer provides the same functionality that each character client running in batch mode does. For example the only output device is the log file and you can not intercept a request for user input.
  • The AppServer can make use of OS calls and is therefore able to use third party technology which is installed on the machine where it runs and - which might be dependent on the OS.


Heavy Regards, RealHeavyDude.
 
Forgot:

GUI specific statements might fail - but not necessarily. For example a MESSAGE VIEW-AS ALERT-BOX statement won't fail, instead a corresponding entry in the log file will be generated.

Heavy Regards, RealHeavyDude.
 
I am not sure if I am right, but I came to understand that program/widget handle does not run on App. If this is the case, then I wanted to learn about those statements/keywords that also does not run on Appserver. Also, I found some progress statement like Transaction-Mode Automatic which only runs on Appserver. I would really appreciate if all of us could share our knowledge and create one such list.

Regards,
Ujjwal
 
Sorry, but I don't get you.

I don't think it is just a question of syntax - keywords, it is about understanding the capabilities of the AppServer and how to use the AppServer. I've been developing AppServer applications and I never had the need to use the TRANSACTION-MODE-AUTOMATIC. From what I know it is only used when spawning a transaction from the client across multiple AppServer calls - and that is, although it is possible to do, bad practice. Secondly, why would you run a procedure that uses GUI widgets on the AppServer?

Maybe it would help to if you would tell us as to why you think you need such a list.

Heavy Regards, RealHeavyDude.
 
Yes, I agree with you when you have said that it is about understanding the capabilities of the Appserver and how to use it.... I am just trying to see for those progress statement which solely run on App or which does not and wondering that would be a great reference to work on.
 
The issue is that it is not solely the keyword - there might be exceptions like the TRANSACTION-MODE-AUTOMATIC keyword and keywords related to GUI widgets. Keywords are always used to solve requirements and, IMHO, it is the requirement itself that makes sense to be processed on the AppServer or not. Plus, some GUI specific keywords which don't work on the AppServer don't work because the AppServer is a character client and not because it is the AppServer. Anyway, if a program containing a specific statement won't run on the AppServer it is for good reason: It doesn't make any sense at all to have such a program running on the AppServer. On the other hand, even if a program would not contain any keywords which won't run on the AppServer, it does not mean that the program would run successfully on the AppServer. Therefore, I don't really see the benefit of such a list and I believe that such a list does not exist. If it does maybe someone else is able to point you to it.

Heavy Regards, RealHeavyDude.
 
You must log in or register to reply here.
Back
Top