Re: STRSQL "Slowness Gremlin" infecting 5250 Session B, or Session C, or Session A

elehti@xxxxxxxxxxxxxxxxxx wrote:

I have identified and corrected the "Slowness Gremlin"
impacting STRSQL on one of my 5250 sessions. In Session
Attributes (F13 function key) the Data Refresh parameter
can be set to *ALWAYS or *FORWARD. The slow session was
set to *FORWARD instead of *ALWAYS. The help text for
*FORWARD says, "The results of a SELECT statement are
written to a temporary file as you page forward.
<<SNIP>>

Someday I may research to see which file and location
the *FORWARD results are put. For now though, I am
avoiding it like the plague!

The term /file/ is used in the generic sense, as so often used to describe almost every /thing/ on another OS. That is, there is no STMF nor *FILE which holds the data. The Query/400 report writer [which provides the OUTPUT(*) for STRSQL for *LOCAL connections] stores the retrieved rows in, I believe, /temporary miscellaneous spaces/ of what I recall was object type *QTSP. If you were to run a report, perform the B=Bottom, then issue a DMPJOB with the parameters set to include /spaces/, then you could track down the /file/ where the data resides; of course they are one or more space objects, with no discernible order because that is maintained by the report writer outside of those spaces. Of course that is all implementation detail, which is subject to change, which means knowing it is interesting, but nothing that can be assumed for future reference.

Regards, Chuck