passing along a user note:

> From:         A Concerned Reader
> Subject:      SAS -> XML

> I discovered a difference in the way SAS 9.1.3
> creates the XML file and the way SAS 9.2 creates it.
> It's not a big deal,
> but users will need to make adjustments in the programs
> that read the XML file.

> SAS 9.1.3:

> <?xml version="1.0" encoding="windows-1252" ?>
> <TABLE>
>    <PROVIDERTEST>
>       <ID_num>01D0026356</ID_num>
>       .
>       .
>       .
>          </PROVIDERTEST>
>       </TABLE>

>       SAS 9.2
>
> <?xml version="1.0" encoding="windows-1252" ?>
> <LIBRARY type="GENERIC" version="9.2">
>    <PROVIDERTEST>
>       <clia_num>01D0026356</clia_num>
>             <region>04</region>
>       .
>       .
>       .
>       </PROVIDERTEST>
>       </LIBRARY>
>

summary:

> Where SAS 9.1.3 uses the delimiter 'TABLE' alone
> while SAS 9.2 uses 'LIBRARY' and other text using the same SAS code.
> While the MS SQL Server Integration Service process
> runs correctly (i.e. no error report),
> no data load into the table.
> It might be useful to let other SAS users
> know about this before they spend half a day
> figuring out why their data transfer process doesn't work.

On Dec 11, 7:34=A0am, r...@CDC.GOV ("Fehd, Ronald J. (CDC/CCHIS/NCPHI)")
wrote:
> passing along a user note:
>
>
>
>
>
> > From: =A0 =A0 =A0 =A0 A Concerned Reader
> > Subject: =A0 =A0 =A0SAS -> XML
> > I discovered a difference in the way SAS 9.1.3
> > creates the XML file and the way SAS 9.2 creates it.
> > It's not a big deal,
> > but users will need to make adjustments in the programs
> > that read the XML file.
> > SAS 9.1.3:
> > <?xml version=3D"1.0" encoding=3D"windows-1252" ?>
> > <TABLE>
> > =A0 =A0<PROVIDERTEST>
> > =A0 =A0 =A0 <ID_num>01D0026356</ID_num>
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 =A0 =A0</PROVIDERTEST>
> > =A0 =A0 =A0 </TABLE>
> > =A0 =A0 =A0 SAS 9.2
>
> > <?xml version=3D"1.0" encoding=3D"windows-1252" ?>
> > <LIBRARY type=3D"GENERIC" version=3D"9.2">
> > =A0 =A0<PROVIDERTEST>
> > =A0 =A0 =A0 <clia_num>01D0026356</clia_num>
> > =A0 =A0 =A0 =A0 =A0 =A0 <region>04</region>
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 </PROVIDERTEST>
> > =A0 =A0 =A0 </LIBRARY>
>
> summary:
>
>
>
> > Where SAS 9.1.3 uses the delimiter 'TABLE' alone
> > while SAS 9.2 uses 'LIBRARY' and other text using the same SAS code.
> > While the MS SQL Server Integration Service process
> > runs correctly (i.e. no error report),
> > no data load into the table.
> > It might be useful to let other SAS users
> > know about this before they spend half a day
> > figuring out why their data transfer process doesn't work.- Hide quoted=
 text -
>
> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Great to know Ron, great to know. This could have significant impacts
for me and I haven't tested it as of yet.

Alan
http://www.savian.net

On Dec 11, 7:34=A0am, r...@CDC.GOV ("Fehd, Ronald J. (CDC/CCHIS/NCPHI)")
wrote:
> passing along a user note:
>
>
>
>
>
> > From: =A0 =A0 =A0 =A0 A Concerned Reader
> > Subject: =A0 =A0 =A0SAS -> XML
> > I discovered a difference in the way SAS 9.1.3
> > creates the XML file and the way SAS 9.2 creates it.
> > It's not a big deal,
> > but users will need to make adjustments in the programs
> > that read the XML file.
> > SAS 9.1.3:
> > <?xml version=3D"1.0" encoding=3D"windows-1252" ?>
> > <TABLE>
> > =A0 =A0<PROVIDERTEST>
> > =A0 =A0 =A0 <ID_num>01D0026356</ID_num>
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 =A0 =A0</PROVIDERTEST>
> > =A0 =A0 =A0 </TABLE>
> > =A0 =A0 =A0 SAS 9.2
>
> > <?xml version=3D"1.0" encoding=3D"windows-1252" ?>
> > <LIBRARY type=3D"GENERIC" version=3D"9.2">
> > =A0 =A0<PROVIDERTEST>
> > =A0 =A0 =A0 <clia_num>01D0026356</clia_num>
> > =A0 =A0 =A0 =A0 =A0 =A0 <region>04</region>
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 .
> > =A0 =A0 =A0 </PROVIDERTEST>
> > =A0 =A0 =A0 </LIBRARY>
>
> summary:
>
>
>
> > Where SAS 9.1.3 uses the delimiter 'TABLE' alone
> > while SAS 9.2 uses 'LIBRARY' and other text using the same SAS code.
> > While the MS SQL Server Integration Service process
> > runs correctly (i.e. no error report),
> > no data load into the table.
> > It might be useful to let other SAS users
> > know about this before they spend half a day
> > figuring out why their data transfer process doesn't work.- Hide quoted=
 text -
>
> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Ron,

A birdie tested it and I tested it and we do not see this behavior.
Check this code out:

libname test xml 'c:\temp\test.xml' ;

data test.class;
   set sashelp.class;
run;

Alan
http://www.savian.net