1 @node System and Portable File IO
2 @chapter System and Portable File I/O
4 The commands in this chapter read, write, and examine system files and
8 * APPLY DICTIONARY:: Apply system file dictionary to active file.
9 * EXPORT:: Write to a portable file.
10 * GET:: Read from a system file.
11 * GET DATA:: Read from foreign files.
12 * IMPORT:: Read from a portable file.
13 * SAVE:: Write to a system file.
14 * SYSFILE INFO:: Display system file dictionary.
15 * XEXPORT:: Write to a portable file, as a transformation.
16 * XSAVE:: Write to a system file, as a transformation.
19 @node APPLY DICTIONARY
20 @section APPLY DICTIONARY
21 @vindex APPLY DICTIONARY
24 APPLY DICTIONARY FROM=@{'file-name',file_handle@}.
27 @cmd{APPLY DICTIONARY} applies the variable labels, value labels,
28 and missing values taken from a file to corresponding
29 variables in the active file. In some cases it also updates the
32 Specify a system file, portable file, or scratch file with a file name
33 string or as a file handle (@pxref{File Handles}). The dictionary in the
34 file will be read, but it will not replace the active file dictionary.
35 The file's data will not be read.
37 Only variables with names that exist in both the active file and the
38 system file are considered. Variables with the same name but different
39 types (numeric, string) will cause an error message. Otherwise, the
40 system file variables' attributes will replace those in their matching
41 active file variables:
45 If a system file variable has a variable label, then it will replace the
46 active file variable's variable label. If the system file variable does
47 not have a variable label, then the active file variable's variable
48 label, if any, will be retained.
51 If the system file variable has custom attributes (@pxref{VARIABLE
52 ATTRIBUTE}), then those attributes replace the active file variable's
53 custom attributes. If the system file variable does not have custom
54 attributes, then the active file variable's custom attributes, if any,
58 If the active file variable is numeric or short string, then value
59 labels and missing values, if any, will be copied to the active file
60 variable. If the system file variable does not have value labels or
61 missing values, then those in the active file variable, if any, will not
65 In addition to properties of variables, some properties of the active
66 file dictionary as a whole are updated:
70 If the system file has custom attributes (@pxref{DATAFILE ATTRIBUTE}),
71 then those attributes replace the active file variable's custom
75 If the active file has a weighting variable (@pxref{WEIGHT}), and the
76 system file does not, or if the weighting variable in the system file
77 does not exist in the active file, then the active file weighting
78 variable, if any, is retained. Otherwise, the weighting variable in
79 the system file becomes the active file weighting variable.
82 @cmd{APPLY DICTIONARY} takes effect immediately. It does not read the
84 file. The system file is not modified.
93 /UNSELECTED=@{RETAIN,DELETE@}
97 /RENAME=(src_names=target_names)@dots{}
102 The @cmd{EXPORT} procedure writes the active file dictionary and data to a
103 specified portable file or scratch file.
105 By default, cases excluded with FILTER are written to the
106 file. These can be excluded by specifying DELETE on the UNSELECTED
107 subcommand. Specifying RETAIN makes the default explicit.
109 Portable files express real numbers in base 30. Integers are always
110 expressed to the maximum precision needed to make them exact.
111 Non-integers are, by default, expressed to the machine's maximum
112 natural precision (approximately 15 decimal digits on many machines).
113 If many numbers require this many digits, the portable file may
114 significantly increase in size. As an alternative, the DIGITS
115 subcommand may be used to specify the number of decimal digits of
116 precision to write. DIGITS applies only to non-integers.
118 The OUTFILE subcommand, which is the only required subcommand, specifies
119 the portable file or scratch file to be written as a file name string or
120 a file handle (@pxref{File Handles}).
122 DROP, KEEP, and RENAME follow the same format as the SAVE procedure
125 The TYPE subcommand specifies the character set for use in the
126 portable file. Its value is currently not used.
128 The MAP subcommand is currently ignored.
130 @cmd{EXPORT} is a procedure. It causes the active file to be read.
138 /FILE=@{'file-name',file_handle@}
141 /RENAME=(src_names=target_names)@dots{}
144 @cmd{GET} clears the current dictionary and active file and
145 replaces them with the dictionary and data from a specified file.
147 The FILE subcommand is the only required subcommand. Specify the system
148 file, portable file, or scratch file to be read as a string file name or
149 a file handle (@pxref{File Handles}).
151 By default, all the variables in a file are read. The DROP
152 subcommand can be used to specify a list of variables that are not to be
153 read. By contrast, the KEEP subcommand can be used to specify variable
154 that are to be read, with all other variables not read.
156 Normally variables in a file retain the names that they were
157 saved under. Use the RENAME subcommand to change these names. Specify,
158 within parentheses, a list of variable names followed by an equals sign
159 (@samp{=}) and the names that they should be renamed to. Multiple
160 parenthesized groups of variable names can be included on a single
161 RENAME subcommand. Variables' names may be swapped using a RENAME
162 subcommand of the form @samp{/RENAME=(A B=B A)}.
164 Alternate syntax for the RENAME subcommand allows the parentheses to be
165 eliminated. When this is done, only a single variable may be renamed at
166 once. For instance, @samp{/RENAME=A=B}. This alternate syntax is
169 DROP, KEEP, and RENAME are executed in left-to-right order.
170 Each may be present any number of times. @cmd{GET} never modifies a
171 file on disk. Only the active file read from the file
172 is affected by these subcommands.
174 @cmd{GET} does not cause the data to be read, only the dictionary. The data
175 is read later, when a procedure is executed.
177 Use of @cmd{GET} to read a portable file or scratch file is a PSPP
186 /TYPE=@{GNM,PSQL,TXT@}
187 @dots{}additional subcommands depending on TYPE@dots{}
190 The @cmd{GET DATA} command is used to read files and other data sources
191 created by other applications.
192 When this command is executed, the current dictionary and active file are
193 replaced with variables and data read from the specified source.
195 The TYPE subcommand is mandatory and must be the first subcommand
196 specified. It determines the type of the file or source to read.
197 PSPP currently supports the following file types:
201 Spreadsheet files created by Gnumeric (@url{http://gnumeric.org}).
204 Relations from PostgreSQL databases (@url{http://postgresql.org}).
207 Textual data files in columnar and delimited formats.
210 Each supported file type has additional subcommands, explained in
211 separate sections below.
214 * GET DATA /TYPE=GNM::
215 * GET DATA /TYPE=PSQL::
216 * GET DATA /TYPE=TXT::
219 @node GET DATA /TYPE=GNM
220 @subsection Gnumeric Spreadsheet Files
224 /FILE=@{'file-name'@}
225 /SHEET=@{NAME 'sheet-name', INDEX n@}
226 /CELLRANGE=@{RANGE 'range', FULL@}
227 /READNAMES=@{ON, OFF@}
232 @cindex spreadsheet files
233 To use GET DATA to read a spreadsheet file created by Gnumeric
234 (@url{http://gnumeric.org}), specify TYPE=GNM to indicate the file's
235 format and use FILE to indicate the Gnumeric file to be read. All
236 other subcommands are optional.
238 The format of each variable is determined by the format of the spreadsheet
239 cell containing the first datum for the variable.
240 If this cell is of string (text) format, then the width of the variable is
241 determined from the length of the string it contains, unless the
242 ASSUMEDVARWIDTH subcommand is given.
245 The FILE subcommand is mandatory. Specify the name of the file
248 The SHEET subcommand specifies the sheet within the spreadsheet file to read.
249 There are two forms of the SHEET subcommand.
251 @samp{/SHEET=name @var{sheet-name}}, the string @var{sheet-name} is the
252 name of the sheet to read.
253 In the second form, @samp{/SHEET=index @var{idx}}, @var{idx} is a
254 integer which is the index of the sheet to read.
255 The first sheet has the index 1.
256 If the SHEET subcommand is omitted, then the command will read the
257 first sheet in the file.
259 The CELLRANGE subcommand specifies the range of cells within the sheet to read.
260 If the subcommand is given as @samp{/CELLRANGE=FULL}, then the entire
262 To read only part of a sheet, use the form
263 @samp{/CELLRANGE=range '@var{top-left-cell}:@var{bottom-right-cell}'}.
264 For example, the subcommand @samp{/CELLRANGE=range 'C3:P19'} reads
265 columns C--P, and rows 3--19 inclusive.
266 If no CELLRANGE subcommand is given, then the entire sheet is read.
268 If @samp{/READNAMES=ON} is specified, then the contents of cells of
269 the first row are used as the names of the variables in which to store
270 the data from subsequent rows.
271 If the READNAMES command is omitted, or if @samp{/READNAMES=OFF} is
272 used, then the variables receive automatically assigned names.
274 The ASSUMEDVARWIDTH subcommand specifies the maximum width of string
275 variables read from the file.
276 If omitted, the default value is determined from the length of the
277 string in the first spreadsheet cell for each variable.
280 @node GET DATA /TYPE=PSQL
281 @subsection Postgres Database Queries
285 /CONNECT=@{connection info@}
295 The PSQL type is used to import data from a postgres database server.
296 The server may be located locally or remotely.
297 Variables are automatically created based on the table column names
298 or the names specified in the SQL query.
299 Postgres data types of high precision, will loose precision when
301 Not all the postgres data types are able to be represented in PSPP.
302 If a datum cannot be represented a warning will be issued and that
303 datum will be set to SYSMIS.
305 The CONNECT subcommand is mandatory.
306 It is a string specifying the parameters of the database server from
307 which the data should be fetched.
308 The format of the string is given in the postgres manual
309 @url{http://www.postgresql.org/docs/8.0/static/libpq.html#LIBPQ-CONNECT}.
311 The SQL subcommand is mandatory.
312 It must be a valid SQL string to retrieve data from the database.
314 The ASSUMEDVARWIDTH subcommand specifies the maximum width of string
315 variables read from the database.
316 If omitted, the default value is determined from the length of the
317 string in the first value read for each variable.
319 The UNENCRYPTED subcommand allows data to be retrieved over an insecure
321 If the connection is not encrypted, and the UNENCRYPTED subcommand is not
322 given, then an error will occur.
323 Whether or not the connection is
324 encrypted depends upon the underlying psql library and the
325 capabilities of the database server.
327 The BSIZE subcommand serves only to optimise the speed of data transfer.
328 It specifies an upper limit on
329 number of cases to fetch from the database at once.
330 The default value is 4096.
331 If your SQL statement fetches a large number of cases but only a small number of
332 variables, then the data transfer may be faster if you increase this value.
333 Conversely, if the number of variables is large, or if the machine on which
334 PSPP is running has only a
335 small amount of memory, then a smaller value will be better.
338 The following syntax is an example:
341 /CONNECT='host=example.com port=5432 dbname=product user=fred passwd=xxxx'
342 /SQL='select * from manufacturer'.
346 @node GET DATA /TYPE=TXT
347 @subsection Textual Data Files
351 /FILE=@{'file-name',file_handle@}
352 [/ARRANGEMENT=@{DELIMITED,FIXED@}]
353 [/FIRSTCASE=@{first_case@}]
354 [/IMPORTCASE=@{ALL,FIRST max_cases,PERCENT percent@}]
355 @dots{}additional subcommands depending on ARRANGEMENT@dots{}
360 When TYPE=TXT is specified, GET DATA reads data in a delimited or
361 fixed columnar format, much like DATA LIST (@pxref{DATA LIST}).
363 The FILE subcommand is mandatory. Specify the file to be read as
364 a string file name or (for textual data
365 only) a file handle (@pxref{File Handles}).
367 The ARRANGEMENT subcommand determines the file's basic format.
368 DELIMITED, the default setting, specifies that fields in the input
369 data are separated by spaces, tabs, or other user-specified
370 delimiters. FIXED specifies that fields in the input data appear at
371 particular fixed column positions within records of a case.
373 By default, cases are read from the input file starting from the first
374 line. To skip lines at the beginning of an input file, set FIRSTCASE
375 to the number of the first line to read: 2 to skip the first line, 3
376 to skip the first two lines, and so on.
378 IMPORTCASE can be used to limit the number of cases read from the
379 input file. With the default setting, ALL, all cases in the file are
380 read. Specify FIRST @i{max_cases} to read at most @i{max_cases} cases
381 from the file. Use PERCENT @i{percent} to read only @i{percent}
382 percent, approximately, of the cases contained in the file. (The
383 percentage is approximate, because there is no way to accurately count
384 the number of cases in the file without reading the entire file. The
385 number of cases in some kinds of unusual files cannot be estimated;
386 PSPP will read all cases in such files.)
388 FIRSTCASE and IMPORTCASE may be used with delimited and fixed-format
389 data. The remaining subcommands, which apply only to one of the two file
390 arrangements, are described below.
393 * GET DATA /TYPE=TXT /ARRANGEMENT=DELIMITED::
394 * GET DATA /TYPE=TXT /ARRANGEMENT=FIXED::
397 @node GET DATA /TYPE=TXT /ARRANGEMENT=DELIMITED
398 @subsubsection Reading Delimited Data
402 /FILE=@{'file-name',file_handle@}
403 [/ARRANGEMENT=@{DELIMITED,FIXED@}]
404 [/FIRSTCASE=@{first_case@}]
405 [/IMPORTCASE=@{ALL,FIRST max_cases,PERCENT percent@}]
407 /DELIMITERS="delimiters"
408 [/QUALIFIER="quotes" [/ESCAPE]]
409 [/DELCASE=@{LINE,VARIABLES n_variables@}]
410 /VARIABLES=del_var [del_var]@dots{}
411 where each del_var takes the form:
415 The GET DATA command with TYPE=TXT and ARRANGEMENT=DELIMITED reads
416 input data from text files in delimited format, where fields are
417 separated by a set of user-specified delimiters. Its capabilities are
418 similar to those of DATA LIST FREE (@pxref{DATA LIST FREE}), with a
421 The required FILE subcommand and optional FIRSTCASE and IMPORTCASE
422 subcommands are described above (@pxref{GET DATA /TYPE=TXT}).
424 DELIMITERS, which is required, specifies the set of characters that
425 may separate fields. Each character in the string specified on
426 DELIMITERS separates one field from the next. The end of a line also
427 separates fields, regardless of DELIMITERS. Two consecutive
428 delimiters in the input yield an empty field, as does a delimiter at
429 the end of a line. A space character as a delimiter is an exception:
430 consecutive spaces do not yield an empty field and neither does any
431 number of spaces at the end of a line.
433 To use a tab as a delimiter, specify @samp{\t} at the beginning of the
434 DELIMITERS string. To use a backslash as a delimiter, specify
435 @samp{\\} as the first delimiter or, if a tab should also be a
436 delimiter, immediately following @samp{\t}. To read a data file in
437 which each field appears on a separate line, specify the empty string
440 The optional QUALIFIER subcommand names one or more characters that
441 can be used to quote values within fields in the input. A field that
442 begins with one of the specified quote characters ends at the next
443 matching quote. Intervening delimiters become part of the field,
444 instead of terminating it. The ability to specify more than one quote
445 character is a PSPP extension.
447 By default, a character specified on QUALIFIER cannot itself be
448 embedded within a field that it quotes, because the quote character
449 always terminates the quoted field. With ESCAPE, however, a doubled
450 quote character within a quoted field inserts a single instance of the
451 quote into the field. For example, if @samp{'} is specified on
452 QUALIFIER, then without ESCAPE @code{'a''b'} specifies a pair of
453 fields that contain @samp{a} and @samp{b}, but with ESCAPE it
454 specifies a single field that contains @samp{a'b}. ESCAPE is a PSPP
457 The DELCASE subcommand controls how data may be broken across lines in
458 the data file. With LINE, the default setting, each line must contain
459 all the data for exactly one case. For additional flexibility, to
460 allow a single case to be split among lines or multiple cases to be
461 contained on a single line, specify VARIABLES @i{n_variables}, where
462 @i{n_variables} is the number of variables per case.
464 The VARIABLES subcommand is required and must be the last subcommand.
465 Specify the name of each variable and its input format (@pxref{Input
466 and Output Formats}) in the order they should be read from the input
469 @subsubheading Examples
472 On a Unix-like system, the @samp{/etc/passwd} file has a format
476 root:$1$nyeSP5gD$pDq/:0:0:,,,:/root:/bin/bash
477 blp:$1$BrP/pFg4$g7OG:1000:1000:Ben Pfaff,,,:/home/blp:/bin/bash
478 john:$1$JBuq/Fioq$g4A:1001:1001:John Darrington,,,:/home/john:/bin/bash
479 jhs:$1$D3li4hPL$88X1:1002:1002:Jason Stover,,,:/home/jhs:/bin/csh
483 The following syntax reads a file in the format used by
486 @c If you change this example, change the regression test in
487 @c tests/command/get-data-txt-examples.sh to match.
489 GET DATA /TYPE=TXT /FILE='/etc/passwd' /DELIMITERS=':'
490 /VARIABLES=username A20
500 Consider the following data on used cars:
503 model year mileage price type age
504 Civic 2002 29883 15900 Si 2
505 Civic 2003 13415 15900 EX 1
506 Civic 1992 107000 3800 n/a 12
507 Accord 2002 26613 17900 EX 1
511 The following syntax can be used to read the used car data:
513 @c If you change this example, change the regression test in
514 @c tests/command/get-data-txt-examples.sh to match.
516 GET DATA /TYPE=TXT /FILE='cars.data' /DELIMITERS=' ' /FIRSTCASE=2
526 Consider the following information on animals in a pet store:
529 'Pet''s Name', "Age", "Color", "Date Received", "Price", "Height", "Type"
530 , (Years), , , (Dollars), ,
531 "Rover", 4.5, Brown, "12 Feb 2004", 80, '1''4"', "Dog"
532 "Charlie", , Gold, "5 Apr 2007", 12.3, "3""", "Fish"
533 "Molly", 2, Black, "12 Dec 2006", 25, '5"', "Cat"
534 "Gilly", , White, "10 Apr 2007", 10, "3""", "Guinea Pig"
538 The following syntax can be used to read the pet store data:
540 @c If you change this example, change the regression test in
541 @c tests/command/get-data-txt-examples.sh to match.
543 GET DATA /TYPE=TXT /FILE='pets.data' /DELIMITERS=', ' /QUALIFIER='''"' /ESCAPE
554 @node GET DATA /TYPE=TXT /ARRANGEMENT=FIXED
555 @subsubsection Reading Fixed Columnar Data
559 /FILE=@{'file-name',file_handle@}
560 [/ARRANGEMENT=@{DELIMITED,FIXED@}]
561 [/FIRSTCASE=@{first_case@}]
562 [/IMPORTCASE=@{ALL,FIRST max_cases,PERCENT percent@}]
565 /VARIABLES fixed_var [fixed_var]@dots{}
566 [/rec# fixed_var [fixed_var]@dots{}]@dots{}
567 where each fixed_var takes the form:
568 variable start-end format
571 The GET DATA command with TYPE=TXT and ARRANGEMENT=FIXED reads input
572 data from text files in fixed format, where each field is located in
573 particular fixed column positions within records of a case. Its
574 capabilities are similar to those of DATA LIST FIXED (@pxref{DATA LIST
575 FIXED}), with a few enhancements.
577 The required FILE subcommand and optional FIRSTCASE and IMPORTCASE
578 subcommands are described above (@pxref{GET DATA /TYPE=TXT}).
580 The optional FIXCASE subcommand may be used to specify the positive
581 integer number of input lines that make up each case. The default
584 The VARIABLES subcommand, which is required, specifies the positions
585 at which each variable can be found. For each variable, specify its
586 name, followed by its start and end column separated by @samp{-}
587 (e.g.@: @samp{0-9}), followed by the input format type (e.g.@:
588 @samp{F}). For this command, columns are numbered starting from 0 at
589 the left column. Introduce the variables in the second and later
590 lines of a case by a slash followed by the number of the line within
591 the case, e.g.@: @samp{/2} for the second line.
593 @subsubheading Examples
596 Consider the following data on used cars:
599 model year mileage price type age
600 Civic 2002 29883 15900 Si 2
601 Civic 2003 13415 15900 EX 1
602 Civic 1992 107000 3800 n/a 12
603 Accord 2002 26613 17900 EX 1
607 The following syntax can be used to read the used car data:
609 @c If you change this example, change the regression test in
610 @c tests/command/get-data-txt-examples.sh to match.
612 GET DATA /TYPE=TXT /FILE='cars.data' /ARRANGEMENT=FIXED /FIRSTCASE=2
613 /VARIABLES=model 0-7 A
631 /RENAME=(src_names=target_names)@dots{}
634 The @cmd{IMPORT} transformation clears the active file dictionary and
636 replaces them with a dictionary and data from a system, portable file,
639 The FILE subcommand, which is the only required subcommand, specifies
640 the portable file to be read as a file name string or a file handle
641 (@pxref{File Handles}).
643 The TYPE subcommand is currently not used.
645 DROP, KEEP, and RENAME follow the syntax used by @cmd{GET} (@pxref{GET}).
647 @cmd{IMPORT} does not cause the data to be read, only the dictionary. The
648 data is read later, when a procedure is executed.
650 Use of @cmd{IMPORT} to read a system file or scratch file is a PSPP
659 /OUTFILE=@{'file-name',file_handle@}
660 /UNSELECTED=@{RETAIN,DELETE@}
661 /@{COMPRESSED,UNCOMPRESSED@}
662 /PERMISSIONS=@{WRITEABLE,READONLY@}
666 /RENAME=(src_names=target_names)@dots{}
671 The @cmd{SAVE} procedure causes the dictionary and data in the active
673 be written to a system file or scratch file.
675 OUTFILE is the only required subcommand. Specify the system file or
676 scratch file to be written as a string file name or a file handle
677 (@pxref{File Handles}).
679 By default, cases excluded with FILTER are written to the system file.
680 These can be excluded by specifying DELETE on the UNSELECTED
681 subcommand. Specifying RETAIN makes the default explicit.
683 The COMPRESS and UNCOMPRESS subcommand determine whether the saved
684 system file is compressed. By default, system files are compressed.
685 This default can be changed with the SET command (@pxref{SET}).
687 The PERMISSIONS subcommand specifies permissions for the new system
688 file. WRITEABLE, the default, creates the file with read and write
689 permission. READONLY creates the file for read-only access.
691 By default, all the variables in the active file dictionary are written
692 to the system file. The DROP subcommand can be used to specify a list
693 of variables not to be written. In contrast, KEEP specifies variables
694 to be written, with all variables not specified not written.
696 Normally variables are saved to a system file under the same names they
697 have in the active file. Use the RENAME subcommand to change these names.
698 Specify, within parentheses, a list of variable names followed by an
699 equals sign (@samp{=}) and the names that they should be renamed to.
700 Multiple parenthesized groups of variable names can be included on a
701 single RENAME subcommand. Variables' names may be swapped using a
702 RENAME subcommand of the form @samp{/RENAME=(A B=B A)}.
704 Alternate syntax for the RENAME subcommand allows the parentheses to be
705 eliminated. When this is done, only a single variable may be renamed at
706 once. For instance, @samp{/RENAME=A=B}. This alternate syntax is
709 DROP, KEEP, and RENAME are performed in left-to-right order. They
710 each may be present any number of times. @cmd{SAVE} never modifies
711 the active file. DROP, KEEP, and RENAME only affect the system file
714 The VERSION subcommand specifies the version of the file format. Valid
715 versions are 2 and 3. The default version is 3. In version 2 system
716 files, variable names longer than 8 bytes will be truncated. The two
717 versions are otherwise identical.
719 The NAMES and MAP subcommands are currently ignored.
721 @cmd{SAVE} causes the data to be read. It is a procedure.
724 @section SYSFILE INFO
728 SYSFILE INFO FILE='file-name'.
731 @cmd{SYSFILE INFO} reads the dictionary in a system file and
732 displays the information in its dictionary.
734 Specify a file name or file handle. @cmd{SYSFILE INFO} reads that file as
735 a system file and displays information on its dictionary.
737 @cmd{SYSFILE INFO} does not affect the current active file.
749 /RENAME=(src_names=target_names)@dots{}
754 The @cmd{EXPORT} transformation writes the active file dictionary and
755 data to a specified portable file.
757 This transformation is a PSPP extension.
759 It is similar to the @cmd{EXPORT} procedure, with two differences:
763 @cmd{XEXPORT} is a transformation, not a procedure. It is executed when
764 the data is read by a procedure or procedure-like command.
767 @cmd{XEXPORT} does not support the UNSELECTED subcommand.
770 @xref{EXPORT}, for more information.
779 /@{COMPRESSED,UNCOMPRESSED@}
780 /PERMISSIONS=@{WRITEABLE,READONLY@}
784 /RENAME=(src_names=target_names)@dots{}
789 The @cmd{XSAVE} transformation writes the active file dictionary and
790 data to a system file or scratch file. It is similar to the @cmd{SAVE}
791 procedure, with two differences:
795 @cmd{XSAVE} is a transformation, not a procedure. It is executed when
796 the data is read by a procedure or procedure-like command.
799 @cmd{XSAVE} does not support the UNSELECTED subcommand.
802 @xref{SAVE}, for more information.