27.03.2013 Views

SPSS® 12.0 Command Syntax Reference

SPSS® 12.0 Command Syntax Reference

SPSS® 12.0 Command Syntax Reference

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

EXPORT 531<br />

• Tape density—200, 556, 800, 1600, or 6250 bits per inch (BPI).<br />

• Parity—even or odd. This must be known only when writing a 7-track tape.<br />

• Tape labeling—labeled or unlabeled. Check whether the site can use tape labels. Also<br />

make sure that the site has the ability to read multivolume tape files if the file being<br />

written uses more than one tape.<br />

• Blocksize—the maximum blocksize the receiving computer can accept.<br />

A tape written with the following characteristics can be read by most computers: 9 track,<br />

1600 BPI, unlabeled, and a blocksize of 3200 characters. However, there is no guarantee that<br />

a tape written with these characteristics can be read successfully. The best policy is to know<br />

the requirements of the receiving computer ahead of time.<br />

The following advice may help ensure successful file transfers by magnetic tape:<br />

• Unless you are certain that the receiving computer can read labels, prepare an unlabeled<br />

tape.<br />

• Make sure the record length of 80 is not changed.<br />

• Do not use a separate character translation program, especially ASCII/EBCDIC translations.<br />

EXPORT/IMPORT takes care of this for you.<br />

• Make sure the same blocking factor is used when writing and reading the tape. A blocksize<br />

of 3200 is frequently a good choice.<br />

• If possible, write the portable file directly to tape to avoid possible interference from copy<br />

programs. Read the file directly from the tape for the same reason.<br />

• Use the INFO LOCAL command to find out about using the program on your particular<br />

computer and operating system. INFO LOCAL generally includes additional information<br />

about reading and writing portable files.<br />

Communications Programs<br />

Transmission of a portable file by a communications program may not be possible if the<br />

program misinterprets any characters in the file as control characters (for example, as a line feed,<br />

carriage return, or end of transmission). This can be prevented by specifying TYPE=COMM on<br />

EXPORT. This specification replaces each control character with the character 0. The affected<br />

control characters are in positions 0–60 of the IMPORT/EXPORT character set (see Appendix B).<br />

The line length that the communications program uses must be set to 80 to match the<br />

80-character record length of portable files. A transmitted file must be checked for blank<br />

lines or special characters inserted by the communications program. These must be edited<br />

out prior to reading the file with the IMPORT command.<br />

Character Translation<br />

Portable files are character files, not binary files, and they have 80-character records so they<br />

can be transmitted over data links. A receiving computer may not use the same character set<br />

as the computer where the portable file was written. When it imports a portable file, the<br />

program translates characters in the file to the character set used by the receiving computer.<br />

Depending on the character set in use, some characters in labels and in string data may be

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!