SPSS 14 features, compatibilty and upgrade questions

[O'Connor, Patricia (OTDA)]

Below Marc mentioned being able to with multiple datasets.
        What is meant by datasets.
                  Multiple flat files / txt files
                  multiple tables in ONE database  (table1a & table2b in
Oracle1)
                  Multiple tables in two databases (table1a in Oracle1 &
table2b in Oracle2)
                  Multiple table in two types of databases (table1a in
Oracle1 & table2d in Access2003)
      Those above plus something else?

Has SPSS 14 become more compatible with prior versions?
Should we still hold off on upgrading from 12 to 14 - why

**************************************************
* Patricia O'Connor
* Associate Computer Programmer Analyst
* OTDA - BDMA
* (W) mailto:Patricia.O'[hidden email]
**************************************************


>
--------------------------------------------------------
This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments.  Please notify the sender immediately by reply e-mail and delete the e-mail from your system.


-----Original Message-----

> From: SPSSX(r) Discussion [mailto:[hidden email]]
> On Behalf Of Marc
> Sent: Thursday, March 23, 2006 01:47 PM
> To: [hidden email]
> Subject: Re: to upgrade or not to upgrade
>
> Hey list,
>
> Now that this is said...
>
> SPSS 14 ability to work with multiple datasets is awesome and
> changes *a
> lot* in the usage and capabilities of the system. Scripting
> capabilities and automation possibilities are greatly
> enhanced (can you spell Python ?), many functions are easier
> to use in a more efficient and productive way, the output
> management system is more performant -- the possibility to
> rout results of an analysis to a new dataset is a very
> powerful feature, etc...
>
> In terms of "purely analytic" capabilities, I don't think
> there are so many differences, but the platform has evolved
> for the better, in general.
>
> Give a try to the evaluation version to judge for yourself,
> and share your impressions with us.
>
> Bye,
>
> Marc.
>

[Hector Maletta]

Patricia,
regarding solely your last question, namely: "Should we still hold off on
upgrading from 12 to 14 - why", I can only think of one valid reason: wait
for version 15, which is already in the works (finishing beta testing).
Hector

-----Mensaje original-----
De: SPSSX(r) Discussion [mailto:[hidden email]] En nombre de
O'Connor, Patricia (OTDA)
Enviado el: Monday, July 17, 2006 1:15 PM
Para: [hidden email]
Asunto: SPSS 14 features, compatibilty and upgrade questions
Importancia: Alta

Below Marc mentioned being able to with multiple datasets.
        What is meant by datasets.
                  Multiple flat files / txt files
                  multiple tables in ONE database  (table1a & table2b in
Oracle1)
                  Multiple tables in two databases (table1a in Oracle1 &
table2b in Oracle2)
                  Multiple table in two types of databases (table1a in
Oracle1 & table2d in Access2003)
      Those above plus something else?

Has SPSS 14 become more compatible with prior versions?
Should we still hold off on upgrading from 12 to 14 - why

**************************************************
* Patricia O'Connor
* Associate Computer Programmer Analyst
* OTDA - BDMA
* (W) mailto:Patricia.O'[hidden email]
**************************************************


>
--------------------------------------------------------
This e-mail, including any attachments, may be confidential, privileged or
otherwise legally protected. It is intended only for the addressee. If you
received this e-mail in error or from someone who was not authorized to send
it to you, do not disseminate, copy or otherwise use this e-mail or its
attachments.  Please notify the sender immediately by reply e-mail and
delete the e-mail from your system.


-----Original Message-----

> From: SPSSX(r) Discussion [mailto:[hidden email]]
> On Behalf Of Marc
> Sent: Thursday, March 23, 2006 01:47 PM
> To: [hidden email]
> Subject: Re: to upgrade or not to upgrade
>
> Hey list,
>
> Now that this is said...
>
> SPSS 14 ability to work with multiple datasets is awesome and
> changes *a
> lot* in the usage and capabilities of the system. Scripting
> capabilities and automation possibilities are greatly
> enhanced (can you spell Python ?), many functions are easier
> to use in a more efficient and productive way, the output
> management system is more performant -- the possibility to
> rout results of an analysis to a new dataset is a very
> powerful feature, etc...
>
> In terms of "purely analytic" capabilities, I don't think
> there are so many differences, but the platform has evolved
> for the better, in general.
>
> Give a try to the evaluation version to judge for yourself,
> and share your impressions with us.
>
> Bye,
>
> Marc.
>

[DEMUNA Chorrillos-Peru]

Hello.
I need help for some correlational analysis: this test hypothesis
correlations, measured two times on the same individuals (dependent
samples), has not changed.

Thanks

Cesar Merino

>From: Hector Maletta <[hidden email]>
>Reply-To: Hector Maletta <[hidden email]>
>To: [hidden email]
>Subject: Re: SPSS 14 features, compatibilty and upgrade questions
>Date: Mon, 17 Jul 2006 14:38:11 -0300
>
>Patricia,
>regarding solely your last question, namely: "Should we still hold off on
>upgrading from 12 to 14 - why", I can only think of one valid reason: wait
>for version 15, which is already in the works (finishing beta testing).
>Hector
>
>-----Mensaje original-----
>De: SPSSX(r) Discussion [mailto:[hidden email]] En nombre de
>O'Connor, Patricia (OTDA)
>Enviado el: Monday, July 17, 2006 1:15 PM
>Para: [hidden email]
>Asunto: SPSS 14 features, compatibilty and upgrade questions
>Importancia: Alta
>
>Below Marc mentioned being able to with multiple datasets.
>         What is meant by datasets.
>                   Multiple flat files / txt files
>                   multiple tables in ONE database  (table1a & table2b in
>Oracle1)
>                   Multiple tables in two databases (table1a in Oracle1 &
>table2b in Oracle2)
>                   Multiple table in two types of databases (table1a in
>Oracle1 & table2d in Access2003)
>       Those above plus something else?
>
>Has SPSS 14 become more compatible with prior versions?
>Should we still hold off on upgrading from 12 to 14 - why
>
>**************************************************
>* Patricia O'Connor
>* Associate Computer Programmer Analyst
>* OTDA - BDMA
>* (W) mailto:Patricia.O'[hidden email]
>**************************************************
>
>
> >
>--------------------------------------------------------
>This e-mail, including any attachments, may be confidential, privileged or
>otherwise legally protected. It is intended only for the addressee. If you
>received this e-mail in error or from someone who was not authorized to
>send
>it to you, do not disseminate, copy or otherwise use this e-mail or its
>attachments.  Please notify the sender immediately by reply e-mail and
>delete the e-mail from your system.
>
>
>-----Original Message-----
>
> > From: SPSSX(r) Discussion [mailto:[hidden email]]
> > On Behalf Of Marc
> > Sent: Thursday, March 23, 2006 01:47 PM
> > To: [hidden email]
> > Subject: Re: to upgrade or not to upgrade
> >
> > Hey list,
> >
> > Now that this is said...
> >
> > SPSS 14 ability to work with multiple datasets is awesome and
> > changes *a
> > lot* in the usage and capabilities of the system. Scripting
> > capabilities and automation possibilities are greatly
> > enhanced (can you spell Python ?), many functions are easier
> > to use in a more efficient and productive way, the output
> > management system is more performant -- the possibility to
> > rout results of an analysis to a new dataset is a very
> > powerful feature, etc...
> >
> > In terms of "purely analytic" capabilities, I don't think
> > there are so many differences, but the platform has evolved
> > for the better, in general.
> >
> > Give a try to the evaluation version to judge for yourself,
> > and share your impressions with us.
> >
> > Bye,
> >
> > Marc.
> >

_________________________________________________________________
MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/

[Richard Ristow]

At 12:15 PM 7/17/2006, O'Connor, Patricia (OTDA) wrote:

>Below Marc mentioned being able to with multiple datasets [in SPSS
>14].         What is meant by datasets?
>- Multiple flat files / txt files
>- multiple tables in ONE database  (table1a & table2b in Oracle1)
>- Multiple tables in two databases (table1a in Oracle1 & table2b in
>Oracle2)
>- Multiple table in two types of databases (table1a in Oracle1 &
>table2d in Access2003)
>- Those above plus something else?

Watch, as well, for what anyone from SPSS, Inc., posts.

However, SPSS 14 uses 'dataset' in a particular way. It's essentially a
generalization of the 'working file' or 'active file' that we all know
and, mostly, love: It's now called a 'dataset', and there can be more
than one of them open at a time. (So, there can be more than one Data
Editor window open.) The working file - what procedures read, what
transformations write - is now the 'active dataset.'

You can use a 'dataset' in some of the ways you can use a scratch saved
file; that is you can ADD FILES and MATCH FILES from datasets other
than the active one, but not SAVE FILE or XSAVE FILE to a dataset.
(Shhhh - for GET FILE, you can cheat: use ADD FILES, naming only the
dataset you want.)

I said the differences are maddening. I meant, writing this, to give
the rules for when a dataset is created and when it becomes active, and
managed to confuse myself badly, so I'll let that be another posting.

[Oliver, Richard]

Just to clarify: One of the major benefits of multiple datasets is the ability to merge data from multiple data sources -- without requiring the intermediate step of saving each one in the form of an SPSS data file first. The  example below, from the Command Syntax Reference, shows how you could merge data from an SPSS data file, and Excel file, and a database table.

GET FILE='c:\examples\data\spssdata.sav'.
SORT CASES BY ID.
DATASET NAME spssdata.
GET DATA /TYPE=XLS
  /FILE='c:\examples\data\excelfile.xls'.
SORT CASES BY ID.
DATASET NAME excelfile.
GET DATA /TYPE=ODBC /CONNECT=
 'DSN=MS Access Database;DBQ=C:\examples\data\dm_demo.mdb;'+
 'DriverId=25;FIL=MS Access;MaxBufferSize=2048;PageTimeout=5;'
 /SQL='SELECT * FROM main'.
SORT CASES BY ID.
MATCH FILES
 /FILE='spssdata'
 /FILE='excelfile'
 /FILE=*
 /BY ID.

-----Original Message-----
From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Richard Ristow
Sent: Monday, July 17, 2006 2:53 PM
To: [hidden email]
Subject: Re: SPSS 14 features, compatibilty and upgrade questions

At 12:15 PM 7/17/2006, O'Connor, Patricia (OTDA) wrote:

>Below Marc mentioned being able to with multiple datasets [in SPSS
>14].         What is meant by datasets?
>- Multiple flat files / txt files
>- multiple tables in ONE database  (table1a & table2b in Oracle1)
>- Multiple tables in two databases (table1a in Oracle1 & table2b in
>Oracle2)
>- Multiple table in two types of databases (table1a in Oracle1 &
>table2d in Access2003)
>- Those above plus something else?

Watch, as well, for what anyone from SPSS, Inc., posts.

However, SPSS 14 uses 'dataset' in a particular way. It's essentially a generalization of the 'working file' or 'active file' that we all know and, mostly, love: It's now called a 'dataset', and there can be more than one of them open at a time. (So, there can be more than one Data Editor window open.) The working file - what procedures read, what transformations write - is now the 'active dataset.'

You can use a 'dataset' in some of the ways you can use a scratch saved file; that is you can ADD FILES and MATCH FILES from datasets other than the active one, but not SAVE FILE or XSAVE FILE to a dataset.
(Shhhh - for GET FILE, you can cheat: use ADD FILES, naming only the dataset you want.)

I said the differences are maddening. I meant, writing this, to give the rules for when a dataset is created and when it becomes active, and managed to confuse myself badly, so I'll let that be another posting.

["Marc Halbrügge"]

> I need help for some correlational analysis: this test hypothesis
> correlations, measured two times on the same individuals (dependent
> samples), has not changed
It's here:
Steiger, J.H. (1980).
Tests for comparing elements of a correlation matrix.
Psychological Bulletin

Greetings
Marc
--


"Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

[Richard Ristow]

In thread "Re: SPSS 14 features, compatibilty and upgrade questions" I
wrote,

>SPSS 14 uses 'dataset' in a particular way. It's essentially a
>generalization of the 'working file' or 'active file' that we all know
>and, mostly, love: It's now called a 'dataset', and there can be more
>than one of them open at a time. (So, there can be more than one Data
>Editor window open.) The working file - what procedures read, what
>transformations write - is now the 'active dataset.'

The rules for creating and managing datasets aren't laid out very
clearly. Here's what I *think* is the case, all or almost all confirmed
by testing:


A. Datasets, dataset names, and what they're good for: As I wrote, the
new term for what was the 'working file' is the 'active dataset.' The
active dataset may, but need not, have a dataset name.

There may also be 'inactive datasets'. They are files just like the
working file, and they have Data Editor windows. All inactive datasets
must have names; inactivating an unnamed dataset, loses it.

(In the documentation, the connection of a dataset name with its
dataset is termed an 'association'. I don't find that useful, since
un-associated dataset names can't exist; and un-associated datasets
can't exist, except the active dataset.)

1. To list all open datasets, active and inactive:
.  DATASET DISPLAY.

2. Datasets may remain open, though inactive, and be available for
later use, somewhat like scratch saved files. Creating, naming and
copying, and activating datasets, are described below.

3. Dataset names are accepted in FILE= subcommands for ADD FILES, MATCH
FILES, and UPDATE, and in OUTFILE= subcommands for procedures. (Not,
however, in SAVE OUTFILE= or XSAVE OUTFILE=.)


B. Create a dataset

1. Commands that used to create a new working file, now create a new
dataset, which is active but unnamed. If the previously active dataset
is not named, it is lost. If it is named, it remains open with that
name, but is no longer active.

Commands that create a new working file are,
.  NEW FILE.
.  DATA LIST.
.  GET {FILE,DATA,TRANSLATE,CAPTURE,SAS,STATA,...}
.  ADD FILES,   with no "/FILE=*"
.  MATCH FILES, with no "/FILE=*".

(The practical distinction between having "/FILE=*", and not having
one, is new in the dataset system.)

If no DATASET commands are used, the above mirrors the functioning of
the old working file.

2. Create a copy of the working file ('active dataset'); analogous to
SAVE FILE:
.  DATASET COPY <name>.
Creates a copy of the active dataset, under name "<name>", as an
inactive dataset. Any dataset that had that name is lost.

A modest nuisance: Unlike SAVE FILE, DATASET COPY doesn't accept a
KEEP= or DROP= lists. (Possible work-around: following DATASET COPY,
ADD FILES/FILE=* with the desired KEEP= and DROP= lists.)

3. Create an empty, named, inactive dataset:
.  DATASET DECLARE <name>.
This is of use ONLY to create an empty dataset that can then be named
on OUTFILE= subcommands for procedures that have them, including
AGGREGATE. (Yes, procedures can write to datasets, although SAVE and
XSAVE can't.)


C. Keep the active dataset, and switch which dataset is active

1. Name the active dataset, and so cause it to be kept open:
.  DATASET NAME <name>.
The active dataset now has name "<name>", whether or not it had a name
before. Any dataset that had that name is lost.

2. Activate an open but inactive dataset; analogous to GET FILE:
.  DATASET ACTIVATE <name>
The dataset named "<name>" becomes the active dataset. If the previous
active dataset was unnamed, it is lost. If it was named, it remains
open, but not active, under its name.


D. Modify the active dataset

1. A transformation program keeps the active dataset under the same
name, with changes applied

2. MATCH FILES or ADD FILES with /FILE=* keep the active dataset under
its same name, with added variables or cases. (As stated above, if
/FILE=* is not specified, a new, unnamed dataset becomes active. This
is true even if /FILE=<name> is specified, where '<name>' is the name
of the active dataset.)



E. Control display of the Data Editor windows:

Most DATASET commands take a WINDOW=<status> subcommand (no slash
before 'WINDOW'). Allowed values vary by command. Descriptions are from
the SPSS 14 Command Syntax Reference.

1. DATASET NAME and DATASET ACTIVATE:
   WINDOW=FRONT
"The Data Editor window containing the dataset is brought to the front
and the dataset becomes the active dataset for dialog boxes."
   WINDOW=ASIS
"The Data Editor window containing the dataset is not affected. This is
the default."

2. DATASET COPY and DATASET DECLARE:
   WINDOW=MINIMIZED
"The Data Editor window associated with the new dataset is opened in a
minimized
state. This is the default."
   WINDOW=HIDDEN
"The Data Editor window associated with the new dataset is not
displayed."
   WINDOW=FRONT
"The Data Editor window containing the dataset is brought to the front
and the dataset becomes the active dataset for dialog boxes."


F. Deleting a dataset:
.  DATASET CLOSE <name>.






* To make the active dataset be a named dataset, use
.  DATASET NAME <name>
The active dataset is the same as it was, but now has name "<name>";
any dataset that had that name is lost.
.  DATASET ACTIVATE <name>
The dataset named "<name>" becomes the active dataset. If the previous
active dataset was unnamed, it is lost. If it was named, it remains
open, but not active, under its name.

*

[Marks, Jim]

Richard:

Many thanks! I've reading (slowly) thru the syntax manual, and pasted
syntax. This is very helpful in connecting the dots

Maybe you will tackle python next :~)

--jim

-----Original Message-----
From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of
Richard Ristow
Sent: Tuesday, July 18, 2006 2:49 PM
To: [hidden email]
Subject: Using datasets in SPSS 14

In thread "Re: SPSS 14 features, compatibilty and upgrade questions" I
wrote,

>SPSS 14 uses 'dataset' in a particular way. It's essentially a
>generalization of the 'working file' or 'active file' that we all know
>and, mostly, love: It's now called a 'dataset', and there can be more
>than one of them open at a time. (So, there can be more than one Data
>Editor window open.) The working file - what procedures read, what
>transformations write - is now the 'active dataset.'

The rules for creating and managing datasets aren't laid out very
clearly. Here's what I *think* is the case, all or almost all confirmed
by testing:


A. Datasets, dataset names, and what they're good for: As I wrote, the
new term for what was the 'working file' is the 'active dataset.' The
active dataset may, but need not, have a dataset name.

There may also be 'inactive datasets'. They are files just like the
working file, and they have Data Editor windows. All inactive datasets
must have names; inactivating an unnamed dataset, loses it.

(In the documentation, the connection of a dataset name with its dataset
is termed an 'association'. I don't find that useful, since
un-associated dataset names can't exist; and un-associated datasets
can't exist, except the active dataset.)

1. To list all open datasets, active and inactive:
.  DATASET DISPLAY.

2. Datasets may remain open, though inactive, and be available for later
use, somewhat like scratch saved files. Creating, naming and copying,
and activating datasets, are described below.

3. Dataset names are accepted in FILE= subcommands for ADD FILES, MATCH
FILES, and UPDATE, and in OUTFILE= subcommands for procedures. (Not,
however, in SAVE OUTFILE= or XSAVE OUTFILE=.)


B. Create a dataset

1. Commands that used to create a new working file, now create a new
dataset, which is active but unnamed. If the previously active dataset
is not named, it is lost. If it is named, it remains open with that
name, but is no longer active.

Commands that create a new working file are, .  NEW FILE.
.  DATA LIST.
.  GET {FILE,DATA,TRANSLATE,CAPTURE,SAS,STATA,...}
.  ADD FILES,   with no "/FILE=*"
.  MATCH FILES, with no "/FILE=*".

(The practical distinction between having "/FILE=*", and not having one,
is new in the dataset system.)

If no DATASET commands are used, the above mirrors the functioning of
the old working file.

2. Create a copy of the working file ('active dataset'); analogous to
SAVE FILE:
.  DATASET COPY <name>.
Creates a copy of the active dataset, under name "<name>", as an
inactive dataset. Any dataset that had that name is lost.

A modest nuisance: Unlike SAVE FILE, DATASET COPY doesn't accept a KEEP=
or DROP= lists. (Possible work-around: following DATASET COPY, ADD
FILES/FILE=* with the desired KEEP= and DROP= lists.)

3. Create an empty, named, inactive dataset:
.  DATASET DECLARE <name>.
This is of use ONLY to create an empty dataset that can then be named on
OUTFILE= subcommands for procedures that have them, including AGGREGATE.
(Yes, procedures can write to datasets, although SAVE and XSAVE can't.)


C. Keep the active dataset, and switch which dataset is active

1. Name the active dataset, and so cause it to be kept open:
.  DATASET NAME <name>.
The active dataset now has name "<name>", whether or not it had a name
before. Any dataset that had that name is lost.

2. Activate an open but inactive dataset; analogous to GET FILE:
.  DATASET ACTIVATE <name>
The dataset named "<name>" becomes the active dataset. If the previous
active dataset was unnamed, it is lost. If it was named, it remains
open, but not active, under its name.


D. Modify the active dataset

1. A transformation program keeps the active dataset under the same
name, with changes applied

2. MATCH FILES or ADD FILES with /FILE=* keep the active dataset under
its same name, with added variables or cases. (As stated above, if
/FILE=* is not specified, a new, unnamed dataset becomes active. This is
true even if /FILE=<name> is specified, where '<name>' is the name of
the active dataset.)



E. Control display of the Data Editor windows:

Most DATASET commands take a WINDOW=<status> subcommand (no slash before
'WINDOW'). Allowed values vary by command. Descriptions are from the
SPSS 14 Command Syntax Reference.

1. DATASET NAME and DATASET ACTIVATE:
   WINDOW=FRONT
"The Data Editor window containing the dataset is brought to the front
and the dataset becomes the active dataset for dialog boxes."
   WINDOW=ASIS
"The Data Editor window containing the dataset is not affected. This is
the default."

2. DATASET COPY and DATASET DECLARE:
   WINDOW=MINIMIZED
"The Data Editor window associated with the new dataset is opened in a
minimized state. This is the default."
   WINDOW=HIDDEN
"The Data Editor window associated with the new dataset is not
displayed."
   WINDOW=FRONT
"The Data Editor window containing the dataset is brought to the front
and the dataset becomes the active dataset for dialog boxes."


F. Deleting a dataset:
.  DATASET CLOSE <name>.






* To make the active dataset be a named dataset, use .  DATASET NAME
<name> The active dataset is the same as it was, but now has name
"<name>"; any dataset that had that name is lost.
.  DATASET ACTIVATE <name>
The dataset named "<name>" becomes the active dataset. If the previous
active dataset was unnamed, it is lost. If it was named, it remains
open, but not active, under its name.

*

[Richard Ristow]

Addendum, and correction, to a posting from last summer. This applies
to SPSS 15 as well, of course, but I'm keeping the subject to keep the
thread together.

If you're interested, check the original posting in the List archives;
I think it's a useful summary. (For 'active' and 'inactive' datasets,
see that posting.) But on one point,

At 02:48 PM 7/18/2006, I wrote:

>B. Create a dataset
>[...]
>2. Create a copy of the working file ('active dataset'); analogous to
>SAVE FILE:
>.  DATASET COPY <name>.
>Creates a copy of the active dataset, under name "<name>", as an
>inactive dataset. Any dataset that had that name is lost.
>
>A modest nuisance: Unlike SAVE FILE, DATASET COPY doesn't accept a
>KEEP= or DROP= lists. (Possible work-around: following DATASET COPY,
>activate the new dataset, and ADD FILES/FILE=* with the desired KEEP=
>and DROP= lists.)

I believe that's right, though I omitted "activate the new dataset"
befoe.

>C. Keep the active dataset, and switch which dataset is active
>[...]
>2. Activate an open but inactive dataset; analogous to GET FILE:
>.  DATASET ACTIVATE <name>
>The dataset named "<name>" becomes the active dataset. If the previous
>active dataset was unnamed, it is lost. If it was named, it remains
>open, but not active, under its name.

DATASET ACTIVATE is not fully analogous to GET FILE. GET FILE is
'non-destructive': The file that's loaded remains on disk exactly as it
was, and can be loaded any number of times, no matter what's done to
the working file.

DATASET ACTIVATE is 'destructive': it activates the ONLY copy of the
dataset. Any changes made, are made to that copy; the exact form of the
dataset before the changes, is lost. (If only procedures, or procedures
and TEMPORARY transformations, are intended, this causes no harm.
However, it's common practice - including my own - to modify the
working file freely, counting on its unmodified input to be available
if needed.)

So, non-destructive method, analogous to GET FILE:

i. (multi-step, pure DATASET commands):
DATASET ACTIVATE <name>.
DATASET COPY     WORKING.
DATASET ACTIVATE WORKING.

The active dataset will be an exact copy of dataset "<name>", with name
"WORKING". (If desired, replace "WORKING" by any name you like, that
isn't already the name of a dataset or file handle.)

ii. (One-step, sidestepping DATASET restrictions.)
ADD FILES
    /FILE=<name>.

ADD FILES and MATCH FILES can read datasets, although GET FILE can't.

(Caution: I think I remember there being some kind of drawback to this
method, though I forget what it is.)

As in previous releases, ADD FILES, like GET FILE, obliterates the
working file (the 'active dataset'), though if the active dataset is
named, it is retained, but inactive, under that name. The new active
dataset after an ADD FILES is unnamed, unless "FILE=*" was specified on
the ADD FILES. (In the latter case, if the active dataset had a name,
the new active dataset retains that name.)