Providing software solutions since 1976
Running PROC CPORT to create a transport file from a SAS data set that was created on a different operating system generates a warning if there are associated files that cannot be added to the transport file.
Mistakes in defining the file characteristics or DCB (Data Control Block) characteristics of the transport file to the operating system at the time of file transfer to MVS are an important cause of the following error ...
Beginning with SASŪ 9.3, you can read, write, and update Windows 32-bit data sets in Windows 64-bit SAS and Windows 64-bit SAS data sets in Windows 32-bit SAS. <p> Catalogs are unaffected by this change and require ...
24454 - Using SASŪ 9 for Windows to directly read a file that is created by SASŪ 9 for UNIX- Usage Note
You can use SASŪ 9 for Windows to directly read a file that is created by SASŪ 9 for UNIX.
35657 - Migrating from OpenVMS Alpha Server Environments to OpenVMS on HP Integrity Servers- Usage Note
Hewlett-Packard offers the following links for making an easy transition from OpenVMS Alpha to OpenVMS on HP Integrity: HP's OpenVMS homepage for OpenVMS Transition Overview Transition Modules Transition Tools ...
36619 - SAS 6.09E (zOS) libraries can be migrated to SAS 9.1.3 with the MIGRATE procedure- Usage Note
This note clarifies a restriction in the Base SAS 9.1.3 Procedures Guide regarding SAS 6.09E libraries that were created under z/OS.
36075 - "Browser and Platform Reports already exists" might occur when using the Batch Import Tool to import packages- Problem Note
The following error might occur when importing packages into SASŪ Management Console: com.sas.report.repository.RepositoryDuplicateNameException: Browser and Platform Reports already exists. at com.sas.report. ...
35595 - I created SAS data sets under Windows for Itanium. Can I use the data sets under Windows for x64?- Usage Note
This note covers SAS files that were created under Microsoft Windows for 64-bit Itanium-based systems, and processed under Windows for x64.
24018 - Can multiple versions of SASŪ software coexist on one computer?- Usage Note
Most SAS products can install side-by-side with a previous version. See Peaceful Coexistence: Multiple SASŪ Releases.
24282 - How do I upgrade a site from an early SASŪ9 release to the latest SAS 9 release?- Usage Note
See the Migration Focus Area on support.sas.com.
22698 - What does the error "ERROR: Encrypted data is invalid" mean?- Usage Note
The error message "ERROR: Encrypted data is invalid" generally means that at least one file in a directory was renamed to new extensions that are not appropriate for the release of SAS they were created by; that is, . ...
22697 - "ERROR: Encrypted data is invalid" occurs with PROC CPORT- Usage Note
The following error usually means that data set or catalog you are attempting to CPORT has become corrupted: "ERROR: Encrypted data is invalid" It is possible that the file has been renamed using the DOS rename ...
24456 - When I migrate a file from 32-bit to 64-bit UNIX, does the file size change?- Usage Note
In general, when you use PROC MIGRATE to migrate a 32-bit library to a 64-bit library, the SAS file size can increase slightly. The increase can occur for the following reasons: The size of the descriptor information ...
22738 - What does ERROR: Member or library unavailable for use in file libref.&&&&&&.data mean?- Usage Note
This message is commonly seen on the the personal computer or UNIX platforms when the transport file has not had the record attribute Carriage Return Carriage Control removed before moving it to the new machine. You ...
In the following examples, we are assume that the transport file made by the CPORT procedure is the same or lower release than your OpenVMS release of SAS. Note: PROC CIMPORT cannot read or process a transport file ...
In the following examples, assume you are running Release 6.08 of the SAS System at TS405 level or higher. The examples use the CC=NONE option as appropriate. If you are running Release 6.08 on OpenVMS/VAX at the TS ...
While OpenVMS can read a transport file with or without this attribute, other hosts will not be able read a transport file created with this file characteristic. The record attribute must be removed from the transport ...
Example 1: The next program reads a transport file from tape containing SAS data sets. cms filedef tran tap1 nl (recfm fb lrecl 80 blksize 8000; run; libname tran xport; libname mylib 'a'; proc copy ...
In the following examples, we are assuming you are moving SAS files from a lower release to a higher release. Example 1: When exporting SAS catalogs to tape, you can use the following approach. The TAPE option ...
22724 - How can I specify the correct file characteristics when creating a transport file on VM/CMS?- Usage Note
What are common mistakes creating transport files on VM? How can I specify the correct file characteristics when creating a transport file on VM/CMS? A transport file for moving SAS data sets can be created by any of ...
Example 1: The transport file was made on the originating machine with PROC COPY or a DATA step with the XPORT engine, PROC COPY with the SASV5XPT engine on PC Release 6.03/6.04 or PROC XCOPY. The libref TRANS ...
Example 1: In this example, we are writing the transport file to tape. First, mount the tape using the appropriate command at your site. The tape should be nonlabeled. Next, execute the following program, ...
Example 1: This example creates a data set transport file on tape. Only one data set, JUL91, is copied. The tape device name in this example is '/dev/tape1'. This example assumes that the tape has an LRECL=80 ...
You can use the extension of the data set and the release number of SAS on 68K Mac and/or a PowerMAC to assist you in grouping UNIX compatible plaforms. The MIPS ABI platforms like SGI are running Release 6.10 and have ...
In the following examples, we are assuming you are moving SAS files from a lower release to a higher release. Example 1: In this example, we are copying all the catalogs in the directory referenced by the libref ...
