Moving and Accessing SAS Files across Operating Environments

OpenVMS Error Messages

For general recovery actions for this error message, see Given transport file is bad.

The transport file is suspected to be corrupt. When checking file attributes, the output confirms that the transport file contains a corrupting character:

$DIR/FULL transport-file

Output includes:

Record attributes: Carriage return Carriage control

If your system has the NFTCOPY (Network File Transfer Copy) command and you are moving the transport file to a DOS target system, remove the carriage return (CC) attribute from the transport file and move the transport file again to the target system:

NFTCOPY/IMAGE/FIXED/CC=NONE NODE"userid
password"
  ::disk:[dir] tranfile target

Here is an example:

NFTCOPY/IMAGE/FIXED/CC=NONE CHEX "brown bird":
 dua0[brown]tranfile c:\blue\target

If your source system is running SAS Release 6.08 at maintenance level TS405 or later, set the NONE value to the CC= option in the LIBNAME or FILENAME statement, whichever is appropriate.

Note: See the top of the SAS log for the SAS release and maintenance level. [cautionend]
Here is an example.

libname grades 'file-path';
libname tranfile xport 'file-path' cc=none;
proc copy in=grades out=tranfile;
run;

If you are running a SAS release that precedes Release 6.08 at maintenance level TS405, you must post-process the transport file to remove the carriage returns.

Create a new file named REMCC.FDL to contain these entries, including CARRIAGE_CONTROL to NONE.

RECORD
BLOCK_SPAN YES
CARRIAGE_CONTROL NONE
FORMAT FIXED
SIZE 80

Issue this DCL command to create a new file named NEWTRAN.SEQ:

$ CONVERT/FDL=REMCC.FDL TRAN.SEQ NEWTRAN.SEQ
$ DELETE TRAN.SEQ

Verify that the file attributes of the new transport file do not include carriage returns:

$ DIR/FULL NEWTRAN.SEQ

At the source system, transfer the transport file to the target system again.

If you are still unable to import a transport file that has the correct attributes, you may try using the re-blocking program in Reblocking a Transport File.

Member or library unavailable for use in file file

The transport file is suspected to be corrupt. See Given transport file is bad for recovery actions.

Truncated record

For general recovery actions for this error message, see Truncated record.

This message is typically displayed when the transport file is moved to a virtual disk or a shared disk with other operating systems such as DOS, Macintosh, or UNIX. Virtual disk or shared disk directories often have a record format of STREAM instead of FIXED.

Verify the transport file attributes by using the DIR/FULL command.

To set record attributes correctly, create a new file named FIXREC.FDL file to contain these entries.

RECORD
BLOCK_SPAN YES
CARRIAGE_CONTROL NONE
FORMAT FIXED
SIZE 80

Issue this DCL command to create a new file named NEWTRAN.FDL:

$ EXCHANGE/NETWORK/TRANSFER_MOD=BLOCK/FDL=TRAN.FDL 
 TRAN.SEQ NEWTRAN.SEQ

Verify that the new transport file attributes do not include carriage returns:

$ DIR/FULL NEWTRAN.SEQ

At the source system, transfer the transport file to the target system again.

Internal error from getting data

The transport file is suspected to be corrupt. See Truncated record for recovery actions.

Procedure VAXTOAXP is not supported on VAX

You get this message when migrating SAS files from an OpenVMS VAX system to an OpenVMS Alpha system. Only the Alpha system supports this procedure. The VAX system does not support this procedure.

Chapter Contents
Previous
Next
Top of Page