topic Re: Accessing the sas file converted from .xpt in SAS Programming

Accessing the sas file converted from .xpt

Tejaswini3 — Sun, 13 Feb 2022 06:24:09 GMT

/*Import XX.xpt file*/
libname xptfile xport 'path\XX.xpt';
libname sasfile 'destination path';
proc copy inlib=xptfile outlib=sasfile;
run;
proc copy inlib=xptfile outlib=sasfile;
run;

In the above code, the sasfile is created but not able to successfully open the file to check the content. Kindly help for any additional or deletion of syntax

To check and store the created dataset in above code had created below code but still not working but the plus point is that am able to check the table properties.

/*Storing in AA dataset*/

libname trial 'Destination path';
data trial.demo;
set xx;
run;

After writing above code following error is coming

The format BTPU11_ was not found or could not be loaded

Re: Accessing the sas file converted from .xpt

Kurt_Bremser — Sun, 13 Feb 2022 06:29:13 GMT

The dataset uses a custom format.

To make the dataset usable, use

options nofmterr;

To recreate the format, request the PROC FORMAT code from the source.

Re: Accessing the sas file converted from .xpt

Tejaswini3 — Sun, 13 Feb 2022 14:31:40 GMT

Thankyou for the reply.

How to recreate the format? I have format file in .xpt and as dataset.

libname library 'path';
options fmtsearch=(library.format_raw);
proc format cntlin=library.format_raw;
quit;

data PKDMG;
merge bapk (in=a) DMG (in=b);
keep country sex DOB1D race;
format formats.;
run;

Re: Accessing the sas file converted from .xpt

Tom — Sun, 13 Feb 2022 14:42:26 GMT

@Tejaswini3 wrote:

Thankyou for the reply.

How to recreate the format? I have format file in .xpt and as dataset.

libname library 'path';
options fmtsearch=(library.format_raw);
proc format cntlin=library.format_raw;
quit;

data PKDMG;
merge bapk (in=a) DMG (in=b);
keep country sex DOB1D race;
format formats.;
run;

That is not going to work.

First told it to use a CATALOG named FORMAT_RAW in the directory pointed to by LIBRARY as the place to look for formats. Does that CATALOG actually exist?

Then you told it to use a DATASET named FORMAT_RAW as input to PROC FORMAT to create a CATALOG named WORK.FORMATS. Does that DATASET actually exist?

If you have a dataset named FORMAT_RAW you can use it in one of two ways.

Leave the FMTSEARCH option alone so that it will search the WORK.FORMATS catalog your PROC FORMAT step is creating.

Or use the LIB=LIBRARY.FORMAT_RAW option on the PROC FORMAT statement to tell it where to write the catalog so that your modified FMTSEARCH option setting will search it.

Re: Accessing the sas file converted from .xpt

Kurt_Bremser — Mon, 14 Feb 2022 14:33:56 GMT

To recreate a format, you need either

the PROC FORMAT code that created the format (preferred)
a CNTLIN dataset for PROC FORMAT for automated creation (next best option)
a catalog containing the format (least preferred, because catalogs are platform- and SAS version dependent)

A CNTLIN dataset has (at least) the columns fmtname, start and label.

PROC FORMAT is a procedure that needs a RUN;, not a QUIT;

So which types of SAS files are contained in your XPT file? Only datasets (then look for one with the above mentioned structure) or catalogs also?

Re: Accessing the sas file converted from .xpt

Tejaswini3 — Mon, 14 Feb 2022 17:15:57 GMT

Thankyou sir for the reply. But still i am facing issue in it.

Can you please help me with draft code.

It would be a great help. I want to use the format sasfile in a data step

Re: Accessing the sas file converted from .xpt

Tom — Mon, 14 Feb 2022 19:43:57 GMT

@Tejaswini3 wrote:

Thankyou sir for the reply. But still i am facing issue in it.

Can you please help me with draft code.

It would be a great help. I want to use the format sasfile in a data step

What type of "format sasfile" do you have?

If you have XPT file that contains SAS V5 transport files so that your original code that use the XPORT libname engine works then the only types of file that can contain are SAS datasets.

How many dataset where in the XPT file? The SAS log from your PROC COPY step should show you the names of the files that were copied out of the XPT file. If the PROC COPY step generated an error reading from the XPT file then you do not have a SAS V5 transport file. If you have a file created by PROC CPORT then it could contain a format catalog. You would need to use PROC CIMPORT to read such a file.

If one the SAS dataset has a name that makes your think it might have the format definitions then take a look at what it has in it it. Run PROC CONTENTS to see what the variables are. Run PROC PRINT or a simple data step like below to see what some of the values look like.

Say you have a dataset named SASFILE.FORMAT_NEW. To look at some of the values you could run this code to dump the values of the variables in the first three observations to the SAS log.

data _null_;
  set sasfile.format_new (obs=3);
  put (_all_) (=/);
run;

Re: Accessing the sas file converted from .xpt

Tejaswini3 — Tue, 15 Feb 2022 16:37:17 GMT

Convert .xpt file to sas dataset format

libname xptfile xport 'path\formats.xpt';
libname sasfile 'path';
proc copy inlib=xptfile outlib=sasfile;
options nofmterr;
run;

Dataset code where want to read the file with the help of formats

data trial;
merge Y (in=a) X (in=b);
keep country sex DOB1D race;
format country CHIP11. sex SEX11_. DOB1D ETH11_. race RCE51_.;
run;

Here in this file, the format CHIP11. and others are from formats file. Still not able to read it.

Re: Accessing the sas file converted from .xpt

Kurt_Bremser — Tue, 15 Feb 2022 17:03:22 GMT

What is your "formats file"?

Re: Accessing the sas file converted from .xpt

Tom — Tue, 15 Feb 2022 17:23:54 GMT

Please post the SAS log from running this step so we can tell whether the LIBNAME and PROC COPY step worked. And if they did what datasets were found in the XPT file.

options nofmterr;
libname xptfile xport 'path\formats.xpt';
libname sasfile 'path';
proc copy inlib=xptfile outlib=sasfile;
run;

Copy the lines from the SAS log and paste into the window that pops up when you push the Insert Code icon (The icon looks like the characters < / > ). You might want to remove the actual physical path from the log rather than post it on-line. But make sure to do it in the pop-up window so that the formatting of the lines from the SAS log is preserved.

If the PROC COPY step actually created a dataset then also run PROC CONTENTS on the dataset it created so we can see if it looks like a dataset that could actually define your formats.

Re: Accessing the sas file converted from .xpt

Tejaswini3 — Fri, 18 Feb 2022 15:57:06 GMT

I am able to convert the format file into .sas7bdat.
Using proc content code able to see the content.
The only doubt is how to use this format datafile while reading a different dataset

Re: Accessing the sas file converted from .xpt

Tom — Fri, 18 Feb 2022 16:44:00 GMT

@Tejaswini3 wrote:
I am able to convert the format file into .sas7bdat.
Using proc content code able to see the content.
The only doubt is how to use this format datafile while reading a different dataset

So you have a dataset that you think describes the formats? What does it look like? Does it look like the dataset that PROC FORMAT creates with CNTLOUT= option? If not could you convert it into one? The key things you need to define a format are the name for the format, the raw or uncoded value and the display or coded value. FMTNAME, START, LABEL are the variable names you will need for that informat. Remember that a format name cannot end with a digit.

Do the values mentioned in the format definition look like the values in the dataset variables that are supposed to use those formats? You can use NOFMTERR option to allow you to look a the dataset that has a permanently attached format that your current session cannot find. You can use a FORMAT statement that lists variable(s) without any format specification after them to remove a permanently attached format so that you can print the actual values.

If you have the information to define the formats then you can use PROC FORMAT to create a format catalog from the data. Use the FMTSEARCH option to tell SAS to look for format there. Then use the formats with the actual data you have.

To get detailed help you need to provide detail information. Show the lines from your SAS log of the code you tried. Show the content information of the format dataset. Show some of the values. Show the content information of the dataset that needs to use the format. Show some of the values.

Re: Accessing the sas file converted from .xpt

Tejaswini3 — Mon, 21 Feb 2022 17:16:33 GMT

Thankyou sir.

Kindly find below screenshot of format file in .sas7bdat format. I want to use this format file in some other dataset. the resulting dataset which have usage of different sas data process. Kindly help.

Re: Accessing the sas file converted from .xpt

Tom — Mon, 21 Feb 2022 17:48:53 GMT

Hard to tell since you posted a photograph of something that appears to be using the LABEL as the column header instead of the NAME of the variable. But it looks like that is valid for use with PROC FORMAT. Try it.

So if you converted that XPT file into the WORK.FORMATS dataset you could run this code to create the formats in the WORK.FORMATS catalogs.

proc format cntlin=formats;
run;

Then you could try running PROC FREQ on one of your variables that is using that DART11_ format that it looks like your dataset contains. So if you have a dataset name HAVE with a variable named DART11 you might use

proc freq data=HAVE;
  tables dart11 ;
  format dart11 dart11_. ;
run;

To see the raw values remove the format from the variable. So run code like this and compare to the previous table.

proc freq data=HAVE;
  tables dart11 ;
  format dart11  ;
run;

Re: Accessing the sas file converted from .xpt

Tejaswini3 — Wed, 23 Feb 2022 09:53:00 GMT

data trial;
merge Y (in=a) X (in=b);
keep country sex DOB1D race;
format country sex DOB1D race;
run;
By writing this code I am able to merge the dataset. But the problem is if I want to perform some other process on trial and in log 'xxx format cannot be identified'.
Kindly help

Re: Accessing the sas file converted from .xpt

Kurt_Bremser — Wed, 23 Feb 2022 10:08:47 GMT

@Tejaswini3 wrote:

Thankyou sir.

Kindly find below screenshot of format file in .sas7bdat format. I want to use this format file in some other dataset. the resulting dataset which have usage of different sas data process. Kindly help.

Run

proc format cntlin=dataset;
run;

where dataset is this dataset you show here, and then try to open/use your other dataset(s) again.

Re: Accessing the sas file converted from .xpt

Tejaswini3 — Wed, 23 Feb 2022 13:45:14 GMT

Kindly see the error in log file and suggest the solution

Re: Accessing the sas file converted from .xpt

Tom — Wed, 23 Feb 2022 14:22:14 GMT

Please post text as text and not as photographs!

Your photograph does not show any attempt to define the formats. Did the dataset you posted the photograph of before work as a CNTLIN= dataset in PROC FORMAT step? Did the log show it creating any of the formats named in the errors message in your photograph of the data step?

Why are you referencing variables in the KEEP and FORMAT statements that do not exist?

Re: Accessing the sas file converted from .xpt

Kurt_Bremser — Wed, 23 Feb 2022 14:46:24 GMT

Always (as in ALWAYS) post logs by copy/pasting the log text directly into a window opened with this button:

There is absolutely no need to take a screenshot and insert the picture, copy/pasting is much easier for you and the text is much easier to read and commentate on.

I do not see the PROC FORMAT code I gave you.

Re: Accessing the sas file converted from .xpt

Tejaswini3 — Wed, 23 Feb 2022 16:35:34 GMT

Log file

11 libname sasfile 'D:\SAS\Project\Project 3- Interating Data
11 ! for PKAnalysis\Project 3- Interating Data for
11 ! PKAnalysis\Work\04utility';
NOTE: Libref SASFILE was successfully assigned as follows:
Engine: V9
Physical Name: D:\SAS\Project\Project 3- Interating Data
for PKAnalysis\Project 3- Interating Data for
PKAnalysis\Work\04utility
12 proc copy inlib=xptfile outlib=sasfile;
NOTE: Writing HTML Body file: sashtml.htm
13 run;

NOTE: Input library XPTFILE is sequential.
NOTE: Copying XPTFILE.DMG to SASFILE.DMG (memtype=DATA).
NOTE: BUFSIZE is not cloned when copying across different
engines. System Option for BUFSIZE was used.
NOTE: There were 25 observations read from the data set
XPTFILE.DMG.
NOTE: The data set SASFILE.DMG has 25 observations and 14
variables.
NOTE: PROCEDURE COPY used (Total process time):
real time 6.37 seconds
cpu time 0.50 seconds

14 options nofmterr;

15 libname xptfile xport 'D:\SAS\Project\Project 3- Interating
15 ! Data for PKAnalysis\Project 3- Interating Data for
15 ! PKAnalysis\Work\02data_raw\formats.xpt';
NOTE: Libref XPTFILE was successfully assigned as follows:
Engine: XPORT
Physical Name: D:\SAS\Project\Project 3- Interating Data
for PKAnalysis\Project 3- Interating Data for
PKAnalysis\Work\02data_raw\formats.xpt
16 libname sasfile 'D:\SAS\Project\Project 3- Interating Data
16 ! for PKAnalysis\Project 3- Interating Data for
16 ! PKAnalysis\Work\04utility';
NOTE: Libref SASFILE was successfully assigned as follows:
Engine: V9
Physical Name: D:\SAS\Project\Project 3- Interating Data
for PKAnalysis\Project 3- Interating Data for
PKAnalysis\Work\04utility
17 proc copy inlib=xptfile outlib=sasfile;
18 options nofmterr;
19 run;

NOTE: Input library XPTFILE is sequential.
NOTE: Copying XPTFILE.FORMATS to SASFILE.FORMATS (memtype=DATA).
NOTE: BUFSIZE is not cloned when copying across different
engines. System Option for BUFSIZE was used.
NOTE: There were 500 observations read from the data set
XPTFILE.FORMATS.
NOTE: The data set SASFILE.FORMATS has 500 observations and 21
variables.
NOTE: PROCEDURE COPY used (Total process time):
real time 0.25 seconds
cpu time 0.04 seconds

20 libname form 'D:\SAS\Project\Project 3- Interating Data for
20 ! PKAnalysis\Project 3- Interating Data for
20 ! PKAnalysis\Work\04utility';
NOTE: Libref FORM refers to the same physical library as
SASFILE.
NOTE: Libref FORM was successfully assigned as follows:
Engine: V9
Physical Name: D:\SAS\Project\Project 3- Interating Data
for PKAnalysis\Project 3- Interating Data for
PKAnalysis\Work\04utility
21 proc format cntlin=sasfile.formats;
NOTE: Format BTPU11_ has been output.
NOTE: Format CHIP11_ has been output.
NOTE: Format CRN11_ has been output.
NOTE: Format DART11_ has been output.
NOTE: Format DOSR11_ has been output.
NOTE: Format ETH11_ has been output.
NOTE: Format HGTU11_ has been output.
NOTE: Format RCE51_ has been output.
NOTE: Format RSND21_ has been output.
NOTE: Format SEX11_ has been output.
NOTE: Format VOLU11_ has been output.
NOTE: Format WGTU11_ has been output.
NOTE: Format YNO11_ has been output.
22 run;

NOTE: PROCEDURE FORMAT used (Total process time):
real time 0.29 seconds
cpu time 0.15 seconds

NOTE: There were 500 observations read from the data set
SASFILE.FORMATS.

36 data PKDMG;
37 merge bapk (in=a) DMG (in=b);
38 format country sex DOB1D race;
39 keep country sex DOB1D race;
40 options nofmterr;
41 run;

NOTE: Variable country is uninitialized.
NOTE: Variable sex is uninitialized.
NOTE: Variable race is uninitialized.
WARNING: The variable country in the DROP, KEEP, or RENAME list
has never been referenced.
WARNING: The variable sex in the DROP, KEEP, or RENAME list has
never been referenced.
WARNING: The variable race in the DROP, KEEP, or RENAME list
has never been referenced.
NOTE: There were 300 observations read from the data set
WORK.BAPK.
NOTE: There were 25 observations read from the data set
WORK.DMG.
NOTE: The data set WORK.PKDMG has 300 observations and 1
variables.
NOTE: DATA statement used (Total process time):
real time 0.10 seconds
cpu time 0.09 seconds