search for: cport

>>>>> "Stephen" == Stephen Arthur <sarthur67 at yahoo.com> writes: Stephen> The SAS data set I PROC CPORTed is [9] the result is [10]. Stephen> I PROC CIMPORTed [10] back to its orginal state [9], and it Stephen> worked. Stephen> So the SAS people think that the error is not with the SAS Stephen> XPORT file, but with R trying to load a text SAS XPORT Stephen> file, when it sho...

Dear Rxperts! My colleagues used SAS PROC COPY to generate the xpt files that could be read by the available "xpt" file reading packages in R. However, I am unable to use the R packages for reading SAS transport files generated through SAS PROC CPORT. I have tried SASxport, Hmisc, and foreign. Any ideas/suggestions are more than welcome! Thanks so much! Santosh [[alternative HTML version deleted]]

This is a minor release of Shorewall. WARNING: This release introduces incompatibilities with prior releases. See http://www.shorewall.net/upgrade_issues.htm. Changes are: a) There is now a new NONE policy specifiable in /etc/shorewall/policy. This policy will cause Shorewall to assume that there will never be any traffic between the source and destination zones. b) Shorewall no longer

...I am using SAS v8.2 and R 1.4.1 on a Windows platform. I have a large (6 megabyte) file in .sd2 format. I want to import it into R. If necessary, I can create a smaller file, as I don't need all the variables that are in this file I downloaded the package foreign. I then tried to use PROC CPORT in SAS to create a transport file. It gave no error message, but I cannot find the file it wrote. I also tried the SAS Export Wizard, but this didn't work. What's the best way to do this? More specifically 1) How do I import any .sd2 file to R ? 2) Is it better to create and import s...

...e SAS labels), but am unable to do so (I have read in a CSV version). I first created a transport file using the SAS code: libname ces2 'D:\CES Analysis\Data'; filename transp 'D:\CES Analysis\Data\fadata.xpt'; /* create a transport file - R cannot read file created by proc cport */ proc cport data=ces2.fadata file=transp; run; I then tried to read it in R using: > library(foreign) > library(Hmisc) > fadata2 <- sasxport.get("D:\\CES Analysis\\Data\\fadata.xpt") Error in lookup.xport(file) : file not in SAS transfer format Next I tried...

Hi all, I''m trying to make a simple mapping application that shows to a given point (city, zip etc.) the appropriate map from Google. This is done by updating a div tag via link_to_remote with the Google map code (lot of JavaScript code; see example http://www.google.com/apis/maps/documentation/) Clicking on the ajax''ed link let crash Firefox immediately whereas IE seems

Let''s move this to the Shorewall Development list.... On Tuesday 10 February 2004 03:14 pm, xavier wrote: > here is a patch to allow this : > |ACCEPT<10/sec:20>:debug fw lan:$ntp_servers udp 123 - - - - ntp > > a problem with the patch is that now the logprefix is mandatory. > i''m trying to debug it, but i can''t find the flaw. Also, with

Hello, everyone! I would like to solve the following problem. Btw, I''m terribly sorry about the pseudo-asciiart, but that''s all I can paint as a tropology. I''m hoping it''ll be enough. ----Internet---- | | | eth0 machine A routing+ipchains eth1 | ------------------ machine B So, given I''m running kernel 2.4.19 and using ipchains

I have encountered a problem reading SAS transport files on both a Mac (OS X) and Linux (RedHat 9), both using R2.0.1. After loading "foreign", the command: read.xport("V1622101_050304.xpt") yields: Error in lookup.xport(file) : File not in SAS transfer format In Linux, I can "cat" the file. The first few lines are: **COMPRESSED** **COMPRESSED** **COMPRESSED**

I am getting the following message when Shorewall stops can anybody shed any light on this message and where I should be looking? Thanks root@bobshost:~# shorewall stop Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules... Stopping Shorewall...Processing /etc/shorewall/stop ... IP Forwarding Enabled

...e found a strange bug, here is my situation: - all of our computers makes a pxeboot request by default dhcp server is configured: option option-128 code 128 = string; option option-129 code 129 = text; option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned integer 16; option PXE.mtftp-tmout code 4 = unsigned integer 8; option PXE.mtftp-delay code 5 = unsigned integer 8; .../... host computer-01 { hardware ethernet 00:27:0e:0a:d2:73; fixed-a...

...: Number of seconds a client must listen for activity before trying # to start a new MTFTP transfer # Code 5: Number of seconds a client must listen before trying to restart # a MTFTP transfer option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned integer 16; option PXE.mtftp-tmout code 4 = unsigned integer 8; option PXE.mtftp-delay code 5 = unsigned integer 8; option PXE.discovery-control code 6 = unsigned integer 8; optio...

...# ddns key key updatekey { algorithm HMAC-MD5.SIG-ALG.REG.INT; secret qXv5V0wgDcCO4h+OvAEL3g==; } option domain-name "realss"; option domain-name-servers 10.0.0.1; allow booting; allow bootp; option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned integer 16; option PXE.mtftp-tmout code 4 = unsigned integer 8; option PXE.mtftp-delay code 5 = unsigned integer 8; option PXE.discovery-control code 6 = unsigned integer 8; optio...

...full content of my dhcp.conf: max-lease-time 86400; ddns-update-style interim; ddns-domainname "mydomain.org."; ddns-rev-domainname "in-addr.arpa."; ignore client-updates; ddns-updates on; option space PXE; option PXE.mtftp-ip?????????????? code 1 = ip-address; option PXE.mtftp-cport??????????? code 2 = unsigned integer 16; option PXE.mtftp-sport??????????? code 3 = unsigned integer 16; option PXE.mtftp-tmout??????????? code 4 = unsigned integer 8; option PXE.mtftp-delay??????????? code 5 = unsigned integer 8; option PXE.discovery-control????? code 6 = unsigned integer 8; optio...

...bal Settings for DHCP Services ### option domain-name="dom.com"; default-lease-time 900; max-lease-time 1800; ddns-update-style none; authoritative; allow bootp; allow booting; ### Static PXE Boot options ### option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned integer 16; option PXE.mtftp-tmout code 4 = unsigned integer 8; option PXE.mtftp-delay code 5 = unsigned integer 8; ### Global config per subnet ### subnet 192.168.15.0 netmask 255.255.255.0 { option d...

...eginning of Study"; race=2; d1='3mar2002'd ; dt1='3mar2002 9:31:02'dt; t1='11:13:45't; output; age=31; race=4; d1='3jun2002'd ; dt1='3jun2002 9:42:07'dt; t1='11:14:13't; output; format d1 mmddyy10. dt1 datetime. t1 time. race race.; run; /* PROC CPORT LIB=work FILE='test.xpt';run; * no; */ PROC COPY IN=work OUT=x;SELECT test;RUN; PROC COPY IN=work OUT=y;SELECT test format;RUN; > lookup.xport('test.xpt') $TEST $TEST$headpad [1] 1200 $TEST$type [1] "numeric" "numeric" "numeric" "numeric&quo...

...: Number of seconds a client must listen for activity before trying # to start a new MTFTP transfer # Code 5: Number of seconds a client must listen before trying to restart # a MTFTP transfer option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned integer 16; option PXE.mtftp-tmout code 4 = unsigned integer 8; option PXE.mtftp-delay code 5 = unsigned integer 8; option PXE.discovery-control code 6 = unsigned integer 8; optio...

...library there is a > function called 'sas.get' that will start a sas job > from within R, write > out the file from within a dataset, and read it into > R. This might get > around the long variable name truncation since it > never calls the XPORT > engine or uses PROC CPORT. I've not ever used it > however, so can't > testify on it's use. In addition, the call to SAS > might need some > configuring. Frank Harrell often posts to the > R-help list and has been > extremely helpful in answering questions, if you > wanted to try that rou...

...-time 86400; > ddns-update-style interim; > ddns-domainname "mydomain.org."; > ddns-rev-domainname "in-addr.arpa."; > ignore client-updates; > ddns-updates on; > option space PXE; > option PXE.mtftp-ip code 1 = ip-address; > option PXE.mtftp-cport code 2 = unsigned integer 16; > option PXE.mtftp-sport code 3 = unsigned integer 16; > option PXE.mtftp-tmout code 4 = unsigned integer 8; > option PXE.mtftp-delay code 5 = unsigned integer 8; > option PXE.discovery-control code 6 = unsig...

...-j ACCEPT ++ sed ''s/!/! /g'' + iptables -A loc2fw -p tcp -m state --state NEW --dport www -j ACCEPT + echo '' Rule "ACCEPT loc fw::3128 tcp www" added.'' Rule "ACCEPT loc fw::3128 tcp www" added. + read target clients servers protocol ports cports address