SPSS Statistics

SPSS Statistics

Your hub for statistical analysis, data management, and data documentation. Connect, learn, and share with your peers! 

 View Only
Expand all | Collapse all

A somewhat imprecise error message in Statistics 24 - "Connection is busy with results for another hstmt"?

  • 1.  A somewhat imprecise error message in Statistics 24 - "Connection is busy with results for another hstmt"?

    Posted Wed January 26, 2022 10:55 AM
    When I forgot to add the EXECUTE command after a GET DATA and CACHE command before any subsequent ALTER TYPE commands, SPSS Statistics 24 returns (in my opinion) a somewhat imprecise error message "Connection is busy with results for another hstmt".

    Is it possible to add a suggestion to the existing error message: "Possible missing EXECUTE command?" to focus the users attention on possible errors in the script code?

    ------------------------------
    Frank Krogh
    ------------------------------

    #SPSSStatistics


  • 2.  RE: A somewhat imprecise error message in Statistics 24 - "Connection is busy with results for another hstmt"?

    Posted Wed January 26, 2022 12:14 PM
    Actually, the message is probably too precise, but it would mean nothing to most users.

    Just fyi, it isn't specifically an EXECUTE command that is needed - any command that passes the data would do.

    ALTER TYPE is unique among SPSS commands in that sometimes it requires a data pass, e.g., when resizing strings, and other times, e.g., changing a format, it does not.  So it can be thought of either as a procedure or a transformation command, depending on what it is doing.

    --





  • 3.  RE: A somewhat imprecise error message in Statistics 24 - "Connection is busy with results for another hstmt"?

    Posted Mon January 31, 2022 03:50 AM
    Edited by System Admin Fri January 20, 2023 04:42 PM

    Thanks for your reply, and I am aware of the use of any command that passes the data would do (FREQUENCIES and so on).

    However, I have earlier experienced challenges with the SPSS Server connection caused by concurrent active sessions (that should have been terminated) and hence I wrongly interpreted this error message ("Connection is busy with results for another hstmt") to indicate something else than simply script issues. That is why I would appreciate a reformulation of the error message I received.

    So a better error message (informative and intuitive) could be formulated as easy as "Data must be passed before transformation commands are accepted" or something like that in order to make the user disregard SPSS Server connection or other network issues and focus on the script error issue. 


    --
    Frank Krogh