|Date: ||Fri, 15 Sep 2006 12:29:26 -0500|
|Reply-To: ||"Peck, Jon" <email@example.com>|
|Sender: ||"SPSSX(r) Discussion" <SPSSX-L@LISTSERV.UGA.EDU>|
|From: ||"Peck, Jon" <firstname.lastname@example.org>|
|Subject: ||Re: availability of XML workspaces|
|Content-Type: ||text/plain; charset="utf-8"|
From: SPSSX(r) Discussion [mailto:SPSSX-L@LISTSERV.UGA.EDU] On Behalf Of Gary Rosin
Sent: Tuesday, September 12, 2006 3:17 PM
Subject: [SPSSX-L] availability of XML workspaces
I'm struggling through OMS syntax and the related commands
in the Python spssaux module: "CreateXMLOutput" and
My questions have to do with the extent(s) to which a "tagged"
XML workspace survives (is available for use) after:
(1) a change in platform:
For example, suppose spss syntax *embedded*
in a Python procedure directs SPSS output to a
"tagged" XML workspace. How long is info in
the workspace available to the Python procedure?
[>>>Peck, Jon] The XMLWorkspace exists for the duration of your SPSS session, although switching to distributed mode (SPSS Server) counts as a new session. The workspace lives in memory
(2) an embedded SPSS "OMSEND" or
[>>>Peck, Jon] OMS items are placed in the workspace only at OMSEND for an appropriate request. This timing is the same as if you wrote to a file or dataset.
(3) a Python/spssaux "spss.DeleteXPathHandle(handle)
[>>>Peck, Jon] That will kill the item from the workspace
CreateXMLOutput returns a handle to the item in the workspace. It wraps your syntax in appropriate OMS commands, but you need to specify the items to select if the default won't work.
GetValuesFromXMLWorkspace uses that tag that the previous call returned, but it does not remove anything from the workspace.
You can get a listing of all the current tags in the workspace with
Gary Rosin <email@example.com>
"The world is stronger
than ideas about the world."