search for: 000000000000000000000000000000

...st = FALSE, include.formats = FALSE) When I look at the SASxport::read.xport function code, it is in fact, _not_ the same function. But it does have the R statement about what it thinks qualifies as a SAS xprot file: xport.file.header <- "HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!000000000000000000000000000000 " It checks to see whether the file starts with that string. This is what appeared in my first message: > > The "export" or "transfer format from SA is supposed to make reading data less difficult and standardized. This is what a header from the version used by the NH...

...linux, reading the same sas export file as used on MAC, in this case the results are not rational. Many of the numbers are interpreted as INF etc. Is it possible that the SOLARIS to Linux is causing this problem? Here is a sample of the input file HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!000000000000000000000000000000 SAS SAS SASLIB 9.1 SunOS 13JUN06:14:51:0313JUN06:14:51:03 HEADER RECORD*******MEMBER HEADER RECO RD!!!!!!!000000000000000001600000000140 HEADER RECORD*******DSCRPTR HEADER RECORD!!!!!!!00000000000...

...lt;81>CC14537<BC><85>RL507<BC><87>1<BC><87>S 0 0 20 CHAR In contrast, I can read.xport a different file successfully. That file (and others that I can import successfully) contains the following first line: HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!000000000000000000000000000000 SAS SAS SASLIB 6.12 WIN_NT 21OCT02:13:30:0721OCT02:13:30:07 I know little about SAS but I wonder whether the problem relates to the export characteristics of different versions of SAS. If so, it appears that read.xport may not work with newer versions of...

...xport file header means either... The "export" or "transfer format from SA is supposed to make reading data less difficult and standardized. This is what a header from the version used by the NHANES releases (that's all one line): HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!000000000000000000000000000000 SAS SAS SASLIB 9.2 XP_PRO 16SEP09:09:39:2516SEP09:09:39:25 HEADER RECORD*******MEMBER HEADER RECORD!!!!!!!000000000000000001600000000140 HEADER RECORD*******DSCRPTR HEADER RECORD!!!!!!!000000000000...

-------- Original Message ---------- From: WRAY NICHOLAS <nicholas.wray at ntlworld.com> To: peter dalgaard <pdalgd at gmail.com> Date: 14 April 2018 at 20:18 Subject: Re: [R] Reading xpt files into R Well yesterday I'd downloaded the "foreign" package and tried to open the xpt file using that: library(foreign) read.xport("test.xpt") I got the following

Hello R folk I have an xpt file which I have been trying to open into R in R studio On the net I found guidance which says that I need packages Hmisc and SASxport which I have successfully loaded. I had also found some code which says that this would allow me to read the xpt file into R: library(SASxport) data(Alfalfa) lookup.xport("test.xpt")

Hi I'm trying to read SAS-data on VAX/VMS to Windows R using foreign pakage read.xport and experience some problems. Following lines are used in SAS to create XPORT file LIBNAME a ''xxx; LIBNAME b XPORT ''; PROC COPY IN=a OUT=b; RUN; and I succeed in getting file that looks like correct xport file.However when typing in R following

...seen a note in the documentation anywhere about the maximum number of variables for a dataset in R or for importing with read.xport, but I suspect this is the issue. For completeness, here is the start of the .xport file (it's all on one line): HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!000000000000000000000000000000 SAS SAS SASLIB 9.1 SunOS If anyone has any insights into this, I would greatly appreciate it. Thanks! Mike Greene [[alternative HTML version deleted]]

....201(137) header: id=27220 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=No rec_des=No trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=*<00> rr_type=33 rr_class=1 ttl=0 answers 0 char ................ hex 00000000000000000000000000000000 answers 10 char ................ hex 00000000000000000000000000000000 answers 20 char ................ hex 000000000000000000000000000000 *Case 2:* nmb packet from 192.168.0.201(137) header: id=27185 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=No rec_de...

...p objectClass: shadowAccount objectClass: sambaSamAccount shadowMax: 99999 shadowWarning: 7 loginShell: /bin/sh uidNumber: 1359 gidNumber: 1359 homeDirectory: /home/admin sambaSID: S-1-5-21-3936576374-1604348213-1812465911-1006 sambaNTPassword: B8AF1F54013E322D0A02F9B9FF4B5B1F sambaPasswordHistory: 00000000000000000000000000000000000000000000000000000000 00000000 sambaAcctFlags: [U ] sambaPwdLastSet: 1520247253 # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 Tried to add the machine to the domain using the "sadmin" Mar 6 00:22:28 sam3dc slapd[5581]: <= bdb_equality_...

On 2016-12-04 10:25, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 09:43:25 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > On 2016-12-04 09:11, Rowland Penny via samba wrote: > > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > I have two DC's running

...00554E41562D answers 60 char PDC-01 ...UNA hex 5044432D3031202020201CE400554E41 answers 70 char V-PDC-01 .d.U hex 562D5044432D3031202020201D640055 answers 80 char NAV-PDC-01 .. hex 4E41562D5044432D3031202020201EE4 answers 90 char ................ hex 00000000000000000000000000000000 answers a0 char ................ hex 00000000000000000000000000000000 answers b0 char ............... hex 000000000000000000000000000000 [2006/11/24 12:28:26, 10] libsmb/namequery.c:parse_node_status(158) PDC10#00: flags = 0x64 [2006/11/24 12:28:26, 10] libsmb/namequery.c:par...

...1E84004F4646 answers 70 char ICE .... hex 4943452020202020202020201D040001 answers 80 char .__MSBROWSE__... hex 025F5F4D5342524F5753455F5F020184 answers 90 char .....h.......... hex 0000B0D0F0680E000000000000000000 answers a0 char ................ hex 00000000000000000000000000000000 answers b0 char ............... hex 000000000000000000000000000000 [2005/02/28 13:24:27, 10] libsmb/namequery.c:parse_node_status(70) CIRCLE#00: flags = 0x04 [2005/02/28 13:24:27, 10] libsmb/namequery.c:parse_node_status(70) OFFICE#00: flags = 0x84 [2005/02/28 13:24:27, 10] lib...

...2020202020201E8400494F57 answers 70 char ATRIBE .... hex 4154524942452020202020201D040001 answers 80 char .__MSBROWSE__... hex 025F5F4D5342524F5753455F5F020184 answers 90 char ...[............ hex 0000065BEEE1EB000000000000000000 answers a0 char ................ hex 00000000000000000000000000000000 answers b0 char ............... hex 000000000000000000000000000000 cli_establish_connection: IOWAWBSRV1<00> connecting to IOWASRV1<20> (xxx.xx.x.x) - jlinderman [IOWATRIBE] Connecting to xxx.xx.x.x at port 445 socket option SO_KEEPALIVE = 0 socket option SO_REUSEADDR = 0 socket...