Error and Warning Messages

Bad Transport File

This message appears when one of the following occurs:

• You are attempting to use PROC CIMPORT to move a transport file that was created in SAS 9 to an operating environment that is running SAS 6. You cannot move a transport file from a SAS 9 session on a source operating environment to a SAS 6 session on a target operating environment.

• A file was transported in a format other than BINARY or the attributes of the transport file changed while in transit to the target operating environment. See "Verifying Transfer Format and Transport File Attributes" on page 77 for recovery actions.

• Your site is using a translation table other than the default. A customized translation table is set with the TRANTAB= system option. See SAS Language Reference: Dictionary for details about setting this option. To verify the value of the TRANTAB= system option, submit the following statements:

   proc options option=trantab; run; 

  If you find that your site is using an alternative translation table, you must restore the option to its default value by using the following: options trantab=();

  Then create the transport file again, transfer it to the target operating environment, and import the file at the target operating environment.

• A source operating environment that runs SAS 6.12 and a target operating environment that imports the file at the target operating environment runs SAS 6.08, 6.09E, or 6.10. Data set sort features (specified by using the SORTEDBY= data set option) are included in the SAS 6.12 CPORT procedure but not in the SAS 6.08 CIMPORT procedure.

  Use either of the following to recover from this problem:

  • Disable the sorting feature by using the SORTINFO= option in the SAS 6.12 CPORT procedure. Here is an example:

     proc cport data=grades.junior  file='xgrades.junior'  sortinfo=no; 

  • Disable the SAS 6.12 sorting feature by using the V608 or V609 engine option in the SAS 6.12 CPORT procedure. Here is an example:

     proc cport data=grades.junior  file='xgrades.junior' v609; 

    The SORTEDBY= data set option information is included in SAS 6.12 PROC CPORT.

Catalog File Open Function is Not Supported by the XPORT Engine

This message appears when you attempt to create a transport file for a catalog or catalog entry by using PROC COPY with the XPORT engine. You must use PROC CPORT to create a transport file for a catalog or catalog entry and use PROC CIMPORT to import them at the target operating environment.

DATA= or LIBRARY= Parameter Expected Instead of CATALOG=

This message is displayed at the target operating environment when PROC CIMPORT contains a CATALOG= destination member and the source operating environment used PROC CPORT with the LIBRARY= destination member. The target operating environment must use either the DATA= or LIBRARY= member type. Here is an example:

 proc cport file=in libname=out; proc cimport infile=in catalog=new; 

Because the LIBNAME= option in PROC CPORT specifies a destination member of type LIBRARY, PROC CIMPORT must also specify either a LIBNAME= or a DATA= option.

In order to select only a catalog entry type from an imported library, specify the ET= option in PROC CIMPORT. To exclude a catalog entry type, use the EET= option. Here are examples:

 proc cimport infile=in library=new et=program memtype=catalog; proc cimport infile=in library=new eet=program memtype=catalog; 

In the first example, only catalog entries of type PROGRAM are imported. In the second example, only catalog entries of type PROGRAM are excluded. MEMTYPE=CATALOG restricts the import to catalogs only.

filename is Not a SAS File

Usually, this message appears when you use the CIMPORT procedure to import a data set at the target operating environment. There are two possible explanations .

The transport file that you are trying to import by using PROC CIMPORT might have been created by using the XPORT engine with either the COPY procedure or the DATA step. Read the beginning of the file to find out how the transport file was created. If the XPORT engine created the transport file, the beginning of the file contains this ASCII text:

 HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!00 

If the CPORT procedure created the transport file, the beginning of the file contains this ASCII text:

 **COMPRESSED** **COMPRESSED** **COMPRESSED** **COM 

Note  

If you set the NOCOMPRESS option in PROC CPORT, compression is suppressed, which prevents the display of the preceding text in a transport file.

If incompatible strategies were used to create and then restore the transport file, then use the correct strategy to restore the transport file.

This message might also appear if your site is using a translation table other than the default. For recovery actions for this problem, see "Bad Transport File" on page 71.

Entry Type Catalog-Entry-Type is Not Supported by CPORT

This message means that transporting this catalog entry type between operating environments and across SAS releases is not supported.

Because you cannot retrieve the definitions from the module itself, you can try to move the SAS statements that defined the entry type (such as IML modules) to the target operating environment and then re-create the modules.

Entry Type Catalog-Entry-Type is Not Compatible to Earlier Release

This message appears when you attempt to use PROC CPORT to move a catalog entry from SAS 9 back to SAS 6. SAS 9 does not support the backward compatibility of this catalog entry.

File library.member .DATA Has Too Long a Member Name for the XPORT Engine

This message appears when you use the XPORT engine with PROC COPY to move a data set whose name exceeds 8 characters from a source operating environment that is running SAS 9 to a SAS 6 library. Here is an explicit example of such a message:

 ERROR: The file OUT.THIS_IS_LONG_NAMED_DATA.DATA  has too long a member name for the XPORT engine. 

The member name THIS_IS_LONG_NAMED_DATA exceeds the 8-character member name length, which is enforced by the Version 5 feature set in which the XPORT engine was introduced.

The VALIDVARNAME system option and the assigned value of V6, which enables automatic truncation of long variable names, does not support member names . To recover, copy the member to another member whose name does not exceed 8 characters and try the transport operation again.

File library.member .DATA Has Too Long a Member Name for the V6 Engine

This message appears when you use PROC COPY to move a data set whose name exceeds 8 characters from a source operating environment that is running SAS 9 to a SAS 6 library. Here is an explicit example of such a message:

 ERROR: The file V6LIBMYDATABASE.DATA  has too long a member name for the V6 engine. 

The SAS 9 data set name MYDATABASE exceeds the maximum member name length of 8 characters that is supported in SAS 6. SAS 6 interprets the data set name MYDATABASE as containing 10 characters, which exceeds its maximum length of 8.

The VALIDVARNAME system option and the assigned value of V6, which enables automatic truncation of long variable names, does not support member names. To recover, rename the member or copy it to another member whose name does not exceed 8 characters and try the transport operation again.

File libref .ALL is Damaged. I/O Processing did Not Complete

Usually, this message indicates a file corruption. The most likely explanation is that your site's communications software inserted carriage returns into the transport file.

At the target operating environment, you can use an operating environment-specific utility (such as the UNIX hexadecimal dump utility xd ) to view the transport file in hexadecimal format to find out if carriage returns were inserted. See the UNIX xd (1) manual page for details. As another example, for z/OS, use the SPF 1 command for browsing, select a data set, and enter hex on in the command line.

Example Code 12.1 on page 74 shows an example of a transport file that contains a carriage-return character (0D) and a line-feed character (0A) toward the end of the first record. See the 0D and 0A hex values in the first two positions of the last line.

Example Code 12.1: Hexadecimal Representation of a Transport File

 48 45 41 44 45 52 20 52 45 43 4F 52 44 2A 2A 2A HEADER R ECORD*** 2A 2A 2A 2A 4C 49 42 52 41 52 59 20 48 45 41 44 ****LIBR ARY HEAD 45 52 20 52 45 43 4F 52 44 21 21 21 21 21 21 21 ER RECOR D!!!!! 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 00000000 000000 30 30 30 30 30 30 30 30 30 30 30 30 30 30 20 20 00000000 0000 0D 0A 53 41 53 20 20 20 20 20 53 41 53 20 20 20 ...SAS   SAS 

 

If you do not see carriage-return or line-feed characters, another form of corruption that is not immediately apparent might have occurred. To test this possibility, at the target operating environment, create another transport file from a member of the same type and then view its hexadecimal representation. Compare the appearance of the assumed uncorrupted file that you just created with the suspected corrupted file that you are trying to restore. A visual comparison might prove that the transport file that you are trying to restore is corrupt. In this case, re-create the transport file at the source operating environment, transfer it, and restore it at the target operating environment.

At the source operating environment, find out whether the transport file's attributes include carriage returns. For information about listing and correcting file attributes, see the appropriate operating environment chapter.

At the source operating environment, transfer the transport file to the target operating environment again.

If you are still unable to restore a transport file that has the correct file attributes, try using the reblocking program in " Reblocking a Transport File" on page 78.

Given Transport File is Bad

See "Bad Transport File" on page 71 for recovery actions.

Internal Error From Getting Data

Usually, this message appears because either a file was transported in a format other than BINARY or the attributes of the transport file changed while in transit to the target operating environment.

See "Verifying Transfer Format and Transport File Attributes" on page 77 for recovery actions.

Invalid Data Length

Usually, this message appears because either a file was transported in a format other than BINARY or the attributes of the transport file changed while in transit to the target operating environment.

See "Verifying Transfer Format and Transport File Attributes" on page 77 for recovery actions.

Member or Library Unavailable for Use in File Filename

Usually, this message appears because either a file was transported in a format other than BINARY or the attributes of the transport file changed while in transit to the target operating environment.

See "Verifying Transfer Format and Transport File Attributes" on page 77 for recovery actions.

Another possible explanation applies to a SAS 6.12 session on a source operating environment and a SAS 6.08 session on a target operating environment. Data set sort features (specified by using the SORTEDBY= data set option) are included in the SAS 6.12 CPORT procedure but not in the SAS 6.08 CIMPORT procedure.

Use either of the following to recover from this problem:

• Disable the sorting feature by using the SORTINFO= option in the SAS 6.12 CPORT procedure. Here is an example:

   proc cport data=grades.jr file='tranfile.jr' sortinfo=no; 

• Disable the SAS 6.12 sorting feature by using the V608 engine explicitly in the SAS 6.12 CPORT procedure. Here is an example:

   proc cport data=grades.jr file='tranfile.j v608; 

The SORTEDBY= data set option information is included in SAS 6.12 PROC CPORT.

More Library Members Exist in the Input File. For all of Them to Get Converted, Please Specify LIBRARY=libref Parameter in the PROC Statement

This warning message is displayed at the target operating environment when PROC CIMPORT contains a DATA= destination member and the source operating environment used PROC CPORT with the LIBRARY= destination member. Although, the target operating environment successfully imports only one data set, the message indicates that other members are contained in the library that can also be imported. Here is an example:

 proc cport file=in library=out; proc cimport infile=in data=new; 

In order to expand the import operation to include the entire contents of the destination library, specify the LIBRARY= option instead of the DATA= option in PROC CIMPORT.

PROC SQL Will Not Store a V9 View into a V6 Library

Usually, this message appears when you use the XPORT engine to create a SAS 9 PROC SQL view in transport format in a SAS 6 library. However, you can use the XPORT engine to create an SQL table.

To recover, transport the data set that contains the SQL table to the target operating environment and re-create the PROC SQL view there.

Requested Function is Not Supported

This message indicates a failure to move a library from a source operating environment that is running SAS 9 to a library on a target operating environment that is running SAS 6 because of cross-version incompatibilities. For example, SAS 9 features such as generations data sets and integrity constraints are not supported.

To recover, you must remove SAS 9 features from the library or the member to be moved to the library on the operating environment that is running SAS 6 and try the transport operation again. Preceding notes in the log can give a hint about the offending SAS 9 feature that is not supported. Here is an example:

 NOTE: Integrity constraint mc defined. 

You can infer from this message that SAS 6 does not support integrity constraints.

For tips about removing SAS 9 features, see the recovery actions for these messages: "File library.member .DATA has too long a member name for the V6 engine" on page 73 and "Variable name XXXXXXXXX is illegal for file Version-6-data-set " on page 77.

Truncated Record

Usually, this message appears because either a file was transported in a format other than BINARY or the attributes of the transport file changed in transit to the target operating environment.

See "Verifying Transfer Format and Transport File Attributes" on page 77 for recovery actions.

This message can indicate that the transport file was moved to a virtual disk or shared disk with other operating environments such as DOS, Macintosh, or UNIX. For recovery actions, see the appropriate operating environment chapter.

Updating Not Allowed for libref.member-name because it was Created for a Different Operating System

This message appears when an operating environment attempts to update a file whose format is foreign to that of the accessing operating environment. Use PROC CONTENTS on the file to verify the file's data representation. A data representation of FOREIGN proves that the formats of the file and the accessing operating environment are incompatible.

UTILITY FILE OPEN Function is Not Supported by the XPORT Engine

This message appears when you attempt to use PROC COPY with the XPORT engine to create a transport file for a utility file, such as an MDDB. The XPORT engine does not support utility files.

The Value y Code is Not a Valid SAS Name; Skipping Data Set Due to Error

These error and warning messages appear when you use PROC CIMPORT in SAS 8 to read a transport file that was created using PROC CPORT in SAS 9.

The PROCS CPORT and CIMPORT are forward compatible (SAS 9 CIMPORT can read a SAS file created using SAS 8 CPORT), but they are not backward compatible (SAS 8 CIMPORT cannot read a SAS file created using SAS 9 CPORT).

To identify the version of SAS that was used to create the transport file, use the following SAS program, specifying the appropriate transport file.

 data _null_; infile '  transport-file-path  '; input @109 rel .; put rel=; stop; run; 

The output shows which version of SAS was used to create the transport file.

Variable Name XXXXXXXXX is Illegal for File Version-6-Data-Set

This message appears when using PROC CIMPORT to move a SAS 9 data set that contains long variable names to a SAS 6 data set. Here is an explicit example of such a message:

 ERROR: The variable name Region_Of_The_Country is illegal for file V6LIB.CITY.DATA. 

The SAS 9 variable name Region_Of_The_Country exceeds the maximum variable name length of 8 characters that is supported in SAS 6. To recover, in the SAS session on the client, set the VALIDVARNAME system option to V6 to enable automatic truncation of long variable names and try the transport operation again. Here is an example:

 options validvarname=v6; 

In this example, Region_Of_The_Country truncates to Region_O . However, if the data set contains multiple variables names in which the first 8 characters conflict, SAS 9 uses a truncation algorithm that ensures uniquely truncated variable names. For details, see "Regressing SAS Data Sets to SAS 6 Format" on page 26.