JAS Single - This structure is used for standalone JAS Applications run as CGI applications. Note this is a way to leverage the JAS Database, JegasAPI, JAS API, Security, Configured Database connections etc. Now JAS Single applications do NOT handle things that the JAS Application exclusively manages - however it does allow testing and development of code without compiling the code directly into the JAS server which makes it stellar for testing, and making scheduled tasks for the JAS JobQ subsystem.
NOTE: This structure is passed by reference - and the i8CgiResult variable gets modified in the InitSingle function. For this particular variable - ZERO means success - so the reason for passing it back is to allow acting upon error codes in a reasonable manner.
How you use this record structure is basically populate all the values with the defaults you'd like and then you call the Single_Init function in the uxxj_single unit. Note - the jegas_application.pas file is not the same as the jegas_application_server file. The jegas_application.pas file is the prototype for building JAS SINGLE applications.
Integration JAS SINGLE applications into JAS takes a little work because you need to choose WHAT kind of "program it is" (xml api or a standard Jegas Application) - and make it so your "single" app runs under the correct circumstances.