× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 13-Oct-2016 07:19 -0500, a4g atl wrote:
I have noticed this several times when working with TCP servers.

Noticed what, specifically? A particular job name; e.g. QXDAEDRSQL? Or perhaps noticed that there is a special value *ERDSQL available on the Server Application (SERVER) parameter of the Start TCP/IP Server (STRTCPSVR) command? For which the following help text is available:

*EDRSQL

The Extended Dynamic Remote SQL (EDRSQL) server is started.
Subsequent use of the STRTCPSVR command specifying
SERVER(*EDRSQL) will result in a diagnostic message if the
EDRSQL server has already been started.


It is never started and I was wondering what and how it is used?

What specifically is "it"; one might infer, a particular job? Is there a particular error message logged on the Start request suggesting why the job does not start? Or perhaps instead that the job start is attempted, but the job ends with some particular error message(s)? The Job Description (JOBD) named QXDAJOBD in QSYS is what is used to start the work for the QXDAEDRSQL job, so if there is no joblog produced, then modify that JOBD to ensure logging and that the joblog is kept for review after the job ends -- if the problem is that the job goes away and the situation is that the "how" and "why" is not understood. Note: empirically noted, the job issues a CALL PGM(QSYS/QXDALISTEN) as user QUSER; thus activates the QXDALISTEN in QSYS as the Daemon Program per the doc reference [Extended Dynamic Remote SQL server (QXDAEDRSQL)
](https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/rzajr/rzajrmst16.htm) somebody else provided.

And how specifically is the /start/ request made? If using STRTCPSVR with *AUTOSTART specified for the Server Special Value (SVRSPCVAL) parameter, then only those servers that are defined with the Auto-Start (AUTOSTART) setting of *YES will be started. To check the current setting for that particular server, type the following Change TCP/IP Server (CHGTCPSVR) request on a command line and press Enter, to cause the request to prompt and present the current Auto-Start setting; NB, requesting user must have *IOSYSCFG and any other necessary authorities:

CHGTCPSVR *EDRSQL ??AUTOSTART()


WAG: I suspect possibly, the Extended Dynamic API (XDA) support is available when a client has both the capability to, and asks for, that support to be activated; possibly in the form of a "use SQL Packages" option-setting vs "enable XDA" or "enable EDRS"; e.g. an XDYNAMIC or ExtendedDynamic property setting. I expect that when a client [e.g. ODBC requester] asks for that /package support/, then the Extended Dynamic Remote SQL (EDRS or EDR SQL) server support must be available to actually use the feature as intended? *Or maybe* the database servers processing such XD requests perform that SQL Package stuff automatically, but for non-IBM drivers or for user-written applications, perhaps those must use the EDRS server feature to get that capability, because those would not be using the IBM-supplied database access connection methods?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.