f



Re: ods/pdf startpage=never doesn't work anymore in v92? #3

Hi Andre,

I read the doc and noticed the same line:

"specifying STARTPAGE= NEVER might cause graphics to overprint"

In other word, SAS never committed "NEVER" will behave consistently :-(

Too bad, I may have to make many changes to some validated codes.

Ya

-----Original Message-----
From: Andre Wielki [mailto:wielki@ined.fr]
Sent: Friday, January 30, 2009 2:35 AM
To: Huang, Ya
Cc: SAS-L@LISTSERV.UGA.EDU
Subject: Re: ods/pdf startpage=never doesn't work anymore in v92?

Ya,
I agree with you that some ods pdf functionning has changed but the use of never yes and now has always being not generating evident  pageskipping

the lessons are,        i think
1)yes or now has not the same effect in ods pdf 2)creating first a graph on a pdf page permit the addition of another tabular result which will be added from the head of the page but if you must put many graph on a pdf page follow a reasonnable sequence from top to bottom

======================  yours  modified=========== ods listing close; ods pdf file="d:\temp\v9junk.pdf" notoc style=minimal; *ods pdf startpage=no; ods pdf startpage=never; goptions reset=all  horigin=1 in vorigin=1 in hsize=2 in vsize= 2in;

proc gplot data=sashelp.class;
plot weight*height;
run;
quit;
proc print data=sashelp.class;
run;

ods pdf startpage=now;
ods pdf close;
ods listing;
=================
as showed with later code, the results are varying  see the excerpt of the documentation ______ ods listing close; ods pdf file="d:\temp\v92junk.pdf" notoc style=minimal; ods pdf startpage=never; goptions reset=all  horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit;

data class;set sashelp.class sashelp.class   sashelp.class;
run;
proc print data=class;
run;
ods pdf startpage=now;
ods pdf startpage=never;
goptions reset=all  horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit;
goptions   horigin=1 in vorigin=3 in hsize=2 in
vsize= 2in;
proc gplot data=sashelp.class;
plot weight*height;
run;
quit;
ods pdf close;
ods listing;


_________________
ods listing close;
ods pdf file="d:\temp\v92junk1.pdf" notoc style=minimal; ods pdf startpage=never; goptions reset=all  horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit;

data class;set sashelp.class sashelp.class   sashelp.class;
run;
proc print data=class;
run;
ods pdf startpage=yes;
ods pdf startpage=never;
goptions reset=all  horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit;
goptions   horigin=1 in vorigin=3 in hsize=2 in
vsize= 2in;
proc gplot data=sashelp.class;
plot weight*height;
run;
quit;
ods pdf close;
ods listing;
_________________

ods listing close;
ods pdf file="d:\temp\v92junk3.pdf" notoc style=minimal; ods pdf startpage=never; goptions reset=all  horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; data class;set sashelp.class sashelp.class; run; proc print data=class; run; ods pdf startpage=yes; ods pdf startpage=never;
goptions   horigin=1 in vorigin=3 in hsize=2 in
vsize= 2in;
proc gplot data=sashelp.class;
plot weight*height;
run;
quit;
goptions reset=all  horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; ods pdf close; ods listing;


from the v92 documentation
STARTPAGE=NEVER | NO | NOW | YES controls page breaks.

    NEVER
    specifies not to insert page breaks, even before graphics procedures.
CAUTION:Each graph normally requires an entire page. The default behavior forces a new page after a graphics procedure, even if you use STARTPAGE=NO. STARTPAGE=NEVER turns off that behavior, so specifying STARTPAGE= NEVER might cause graphics to overprint.

    NO
specifies that no new pages be inserted at the beginning of each procedure, or within certain procedures, even if new pages are requested by the procedure code. A new page will begin only when a page is filled or when you specify STARTPAGE=NOW.
CAUTION: Each graph normally requires an entire page. The default behavior forces a new page after a graphics procedure, even if you use STARTPAGE=NO. STARTPAGE=NEVER turns off that behavior.
    Alias:     OFF
Tip:  When you specify STARTPAGE=NO, system titles and footnotes are still produced only at the top and bottom of each physical page, regardless of the setting of this option. Thus, some system titles and footnotes that you specify might not appear when this option is specified.


    NOW
    forces the immediate insertion of a new page.
Tip:     This option is useful primarily when the current value of the
STARTPAGE= option is NO. Otherwise, each new procedure forces a new page automatically.

    YES
    inserts a new page at the beginning of each procedure, and within certain procedures, as requested by the procedure code.
    Alias:     ON
    Default:     YES

HTH
Andre


Ya Huang a �crit :
> Hi there,
>
> The following code when runs on v8.2 will generate a one-page report
> with a table on top and a figure on the bottom. But a two-page report
> with first page as the table and second page as the figure if runs on
> v92, which basically means the startpage=never dosen't work anymore. I
> have a routine report based on the startpage=never, this change
> totally mess up my report!
>
> Is there a way to force v92 to behave as v82 for this matter?
>
> Thanks
>
> Ya
>
> ods listing close;
> ods pdf file="c:\temp\v9junk.pdf" notoc style=minimal; ods pdf
> startpage=never;
>
> proc print data=sashelp.class;
> run;
>
> goptions reset=all device=sasprtc horigin=1 in vorigin=1 in hsize=2 in
> vsize= 2in;
>
> proc gplot data=sashelp.class;
> plot weight*height;
> run;
> quit;
>
> ods pdf close;
> ods listing;
>
>

--
   Andr� WIELKI
   INED (Institut National d'Etudes D�mographiques)
   Service Informatique
   133 Boulevard Davout      75980 Paris Cedex 20
   m�l : wielki@ined.fr      t�l :  33 (0) 1 56 06 21 54
0
ya.huang (1962)
1/30/2009 4:55:24 PM
comp.soft-sys.sas 142828 articles. 3 followers. Post Follow

0 Replies
354 Views

Similar Articles

[PageSpeed] 37

Reply:

Similar Artilces:

Re: ods/pdf startpage=never doesn't work anymore in v92?
Utilize the ODS Layout feature to get the desired text, graphics all in one page. You can refer to this SUGI paper<http://www2.sas.com/proceedings/sugi28/148-28.pdf> . Code: ods listing close; ods pdf file="abc.pdf" notoc style=minimal startpage=never; ods layout start; proc print data=sashelp.class; run; goptions reset=all device=sasprtc horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; ods layout end; ods pdf close; ods listing; AkshayA! On Thu, Jan 29, 2009 at 2:36 PM, Ya Huang <ya.huang@amylin.com> wrote: > Hi there, > > The following code when runs on v8.2 will generate a one-page report with > a table on top and a figure on the bottom. But a two-page report with > first page as the table and second page as the figure if runs on v92, > which basically means the startpage=never dosen't work anymore. I have a > routine report based on the startpage=never, this change totally mess up my > report! > > Is there a way to force v92 to behave as v82 for this matter? > > Thanks > > Ya > > ods listing close; > ods pdf file="c:\temp\v9junk.pdf" notoc style=minimal; > ods pdf startpage=never; > > proc print data=sashelp.class; > run; > > goptions reset=all device=sasprtc horigin=1 in vorigin=1 in hsize=2 in > vsize= 2in; > > proc gplot data=sashelp.class; > plot weight*height; > run; > quit; ...

Re: ods/pdf startpage=never doesn't work anymore in v92? #2
Ya, I agree with you that some ods pdf functionning has changed but the use of never yes and now has always being not generating evident pageskipping the lessons are, i think 1)yes or now has not the same effect in ods pdf 2)creating first a graph on a pdf page permit the addition of another tabular result which will be added from the head of the page but if you must put many graph on a pdf page follow a reasonnable sequence from top to bottom ====================== yours modified=========== ods listing close; ods pdf file="d:\temp\v9junk.pdf" notoc style=minimal; *ods pdf startpage=no; ods pdf startpage=never; goptions reset=all horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; proc print data=sashelp.class; run; ods pdf startpage=now; ods pdf close; ods listing; ================= as showed with later code, the results are varying see the excerpt of the documentation ______ ods listing close; ods pdf file="d:\temp\v92junk.pdf" notoc style=minimal; ods pdf startpage=never; goptions reset=all horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; data class;set sashelp.class sashelp.class sashelp.class; run; proc print data=class; run; ods pdf startpage=now; ods pdf startpage=never; goptions reset=all horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; goptions ...

Re: ods/pdf startpage=never doesn't work anymore in v92? #4
I have used ODS Layout as described in that paper and it is indeed very nice. HOWEVER, be forewarned that what is described there may not work in 9.2. I created (what I thought) was a simple layout where the page was divided into four equally sized regions (top left, top right, bottom left, bottom right) where I positioned graphs in the top right and bottom left, and proc reports in the other two quadrants. I did that in 9.1.3. When I tested it in 9.2 the graphs were not positioned even close to where they should have been. I reported the problem to SAS TS in December and they still have not been able come up with a solution. And please note that this is not a criticism of TS. ODS Layout was experimental when that paper was written and it is still experimental in 9.1.3 and 9.2. I understand that it is scheduled for production in 9.3. So if you are going to do anything with it, I would encourage you to use 9.2 instead of 9.1.3. Regards, -donh -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Akshaya Nathilvar Sent: Thursday, January 29, 2009 2:56 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: ods/pdf startpage=never doesn't work anymore in v92? Utilize the ODS Layout feature to get the desired text, graphics all in one page. You can refer to this SUGI paper<http://www2.sas.com/proceedings/sugi28/148-28.pdf> . Code: ods listing close; ods pdf file="abc.pdf" notoc style=minimal startpage=never; ods layout sta...

ods/pdf startpage=never doesn't work anymore in v92?
Hi there, The following code when runs on v8.2 will generate a one-page report with a table on top and a figure on the bottom. But a two-page report with first page as the table and second page as the figure if runs on v92, which basically means the startpage=never dosen't work anymore. I have a routine report based on the startpage=never, this change totally mess up my report! Is there a way to force v92 to behave as v82 for this matter? Thanks Ya ods listing close; ods pdf file="c:\temp\v9junk.pdf" notoc style=minimal; ods pdf startpage=never; proc print data=sashelp.class; run; goptions reset=all device=sasprtc horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; ods pdf close; ods listing; ...

Re: 'do over' doesn't work #3
On Sat, 24 Jan 2009 14:25:41 +0000, karma <dorjetarap@GOOGLEMAIL.COM> wrote: >Hi Ash, > >What is the purpose of your code? Looking at the test data it appears >you want to replace missing numeric values with the number zero and >missing character data with a "Z". Replacing missing numerics with >zero seems like a pretty standard thing, and therefore there are a few >ways to handle this in SAS. Yes. See http://www.sascommunity.org/wiki/Generating_Zeroes_in_PROC_TRANSPOSE_Output or http://tinyurl.com/abozdc >Replacing missing character variables with >a character, on the other hand is a bit more difficult. > >You could either approach it with your array method as such: > >data have; > infile cards missover; > input x2 x1 x3 x4 x5$ x6$; > cards; >2 . 5 1161 AB�LIEN ANIEL >35 6 3 1336 ALM�RIC >82 1 5 1499 > ;run; > >data array_method; > set have; > array a_varnum _numeric_; > array a_varchar _character_; > do over a_varnum; > if missing(a_varnum) then a_varnum = 0; > end; > do over a_varchar; > if missing(a_varchar) then a_varchar = 'Z'; > end; > run; >proc print;run; > >An alternative, on your test data would also be to use a Dorfmanesque >peek/poke solution. This will only work for provided all your >character variables are a length of 8. The array statements are not >required, but it will force the...

Re: Weird problem with ODS PDF
Problem Note 32003: Text searches return different results in PDF files created by ODS PDF http://support.sas.com/kb/32/003.html The Details section for the note clarifies that "different" means "not correct". ;-) Fortunately, a hot fix is available. Search strategy -- I searched in Samples and SAS Notes for the words ODS, PDF, and search. HTH! Mike Rhoads RhoadsM1@Westat.com -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Jeremy Miles Sent: Friday, February 19, 2010 1:02 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Weird p...

Re: Weird problem with ODS PDF
Mike That is a good idea to add the search strategy keywords to your answer. And, if I have not noticed your (and, maybe, others') doing this, shame on me. Nat -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Mike Rhoads Sent: Friday, February 19, 2010 2:14 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: Weird problem with ODS PDF - searching within PDF doesn't work (SAS 9.2 only?) Problem Note 32003: Text searches return different results in PDF files created by ODS PDF http://support.sas.com/kb/32/003.html The Details section for the n...

Re: 'do over' doesn't work
Ash As I recall, the first SAS arrays were not subscripted and did not use direct array references. The do over statement simply said, go through the variables listed in the array starting with the first and going to the last. The erro messages that you received were telling you that you should not use the brackets on the array names. From my standpoint, the beauty of the do over is that it makes coding simpler and, given my clumsy fingers, anything that reduces my chances of screwing up are a help. However, these days, I would not choose to use a do over expression in code that was going to be used in the future since someone following me would probably not know of the syntax and the Do over has not been documented in years. The following code worked for me. DATA TABLE_BIDON; INPUT X1 X2 X3 X4 X5 $; infile cards missover;** missover added; CARDS; 2 . 5 1161 AB�LIEN 35 6 3 1336 ALM�RIC 82 1 5 1499 ;RUN; DATA TABLE_BIDON ; * no drop statement needed here; SET TABLE_BIDON; ARRAY A_VARNUM _NUMERIC_; ARRAY A_VARCAR _CHARACTER_; DO OVER A_VARNUM; IF A_VARNUM = . THEN A_VARNUM = 0; END; DO OVER A_VARCAR; IF COMPRESS(A_VARCAR) IN (".","") THEN A_VARCAR = "Z"; END; RUN; Nat Wooding Environmental Specialist III Dominion, Environmental Biology 4111 Castlewood Rd Richmond, VA 23234 Phone:804-271-5313, Fax: 804-271-2977 ash007 <R...

Re: why it doesn't work? #3
On Fri, 6 Oct 2006 17:49:12 -0700, Allan <rakulak@GMAIL.COM> wrote: >I have a raw data file containing 3 fields: Goods Name, price, and >Markets. The Markets field is seperated by semicolons with values >Marketing, lowest Price, Hightest Price. The Markets fields are in >varied length. eg: > >"shoes1",35.33,"west bank; 28.00;45.8;east side; 8.05; 33.4;" >"shoes2",50.55,"northeast; 77.66;88.7;east >side;45;90.5;southwest;89.67;150;north; 90;150.45" >..... > >the do loop in below code doesn't work. Could you...

Re: 'do over' doesn't work #2
Ramsamy, The code that follows will get you into DO OVER. Do not use '*' in the dimension statements. Use the implicit index of _I_ t= o refer to individual elements of the array. DATA TABLE_BIDON; INPUT X1 X2 X3 X4 X5 $; CARDS; 2 . 5 1161 ABELIEN 35 6 3 1336 ALMERIC 82 1 5 1499 . ; RUN; DATA TABLE_BIDON ; SET TABLE_BIDON; ARRAY A_VARNUM _NUMERIC_; ARRAY A_VARCAR _CHARACTER_; DO OVER A_VARNUM; IF A_VARNUM[_i_] =3D . THEN A_VARNUM[_i_] =3D 0; END; DO OVER A_VARCAR; IF COMPRESS(A_VARCAR[_i_]) IN (".","") THEN A_VARCAR[_i_] =3D "Z"; END; RUN; Kind regards, Muthia Kachirayan On Sat, Jan 24, 2009 at 6:40 AM, ash007 <RamsamyAshley@gmail.com> wrote: > hi, > > why my code doesn't work with 'do over'. thanks. > > ash007. > > DATA TABLE_BIDON; > INPUT X1 X2 X3 X4 X5 $; CARDS; > 2 . 5 1161 AB=C9LIEN > 35 6 3 1336 ALM=C9RIC > 82 1 5 1499 > ;RUN; > > DATA TABLE_BIDON (DROP =3D _I); > SET TABLE_BIDON; > ARRAY A_VARNUM[*] _NUMERIC_; ARRAY A_VARCAR[*] _CHARACTER_; > > DO OVER A_VARNUM[*]; > IF A_VARNUM[*] =3D . THEN A_VARNUM[*] =3D 0; > END; > > DO OVER A_VARCAR[*]; > IF COMPRESS(A_VARCAR[*]) IN (".","") THEN A_VARCAR[*] =3D = "Z"; > END; > RUN; > ...

Re: 'do over' doesn't work #4
Hi Ash, What is the purpose of your code? Looking at the test data it appears you want to replace missing numeric values with the number zero and missing character data with a "Z". Replacing missing numerics with zero seems like a pretty standard thing, and therefore there are a few ways to handle this in SAS. Replacing missing character variables with a character, on the other hand is a bit more difficult. You could either approach it with your array method as such: data have; infile cards missover; input x2 x1 x3 x4 x5$ x6$; cards; 2 . 5 1161 AB�LIEN ANIEL 35 6 3 1336 ALM�RIC 82 1 5 1499 ;run; data array_method; set have; array a_varnum _numeric_; array a_varchar _character_; do over a_varnum; if missing(a_varnum) then a_varnum = 0; end; do over a_varchar; if missing(a_varchar) then a_varchar = 'Z'; end; run; proc print;run; An alternative, on your test data would also be to use a Dorfmanesque peek/poke solution. This will only work for provided all your character variables are a length of 8. The array statements are not required, but it will force the variables to occupy contiguous space which is required here. If anyone can suggest a way to make handling variable length character variables using this technique, I would very interested. data peek_poke; array nums [*] x1-x4; array chars [*] $x5 x6; set have; _n_ = dim(nums)*8; call poke(tranwrd(peekc(addr(x1),_n_),put(.,rb8.), put...

Re: why the array doesn't work #3
How could I use of here, delete one "-"? 2009/3/16 Nat Wooding <Nathaniel.Wooding@dom.com> > Terry > > Try removing the "of" from your mean function. The error message > disappeared when I dropped it. > > data; > retain total_bal_amt_1 - total_bal_amt_25 tot_rv_bal_amt_1 - > tot_rv_bal_amt_25 > monthly_spd_1 - monthly_spd_25 1; > > array total_bal_amt_arr(*) total_bal_amt_1 - total_bal_amt_25; > array tot_rv_bal_amt_arr(*) tot_rv_bal_amt_1 - tot_rv_bal_amt_25; > array monthly_spd_arr(*) monthly_spd_1 - monthly_spd_25; > gl_mns_lr_m_intvl = 1 ; > bal_between = > mean( total_bal_amt_arr(13) -- total_bal_amt_arr(gl_mns_lr_m_intvl + > 13) ); > > run; > > Nat Wooding > Environmental Specialist III > Dominion, Environmental Biology > 4111 Castlewood Rd > Richmond, VA 23234 > Phone:804-271-5313, Fax: 804-271-2977 > > > > Terry He > <he.terry@GMAIL.C > OM> To > Sent by: "SAS(r) SAS-L@LISTSERV.UGA.EDU > Discussion" cc > <SAS-L@LISTSERV.U > GA.EDU <http://ga.edu/>> > Subject > why the array doesn't work > > 03/16/2009 11:13 > AM &g...

Re: Why doesn't the macro variables work? #3
Sajit , Two problems: First you dont need this: %LET mm =''; %LET yyyy =''; It does nothing useful and only serves to confuse people. You will find you only a few situations in which you have to define a macro var before you load a value into it and when you need to do that all you need to do is: %Global mm yyyy ; or %Local mm yyyy ; Next to your actual problem I would use call symputX if you have V9 or if you have V8 use call symput with the trim function. V9: Data _Null_ ; Set Parameters ; If Name = "yyyy" Then Call SymputX( 'yyyy' , Va...

Re: Colon modifer doesn't work for where statement? #3
On Tue, 25 Mar 2008 10:48:49 -0700, Pardee, Roy <pardee.r@GHC.ORG> wrote: >Still busted in 9.1.3. and in 9.2 as well > >I believe the WHEREs get handed off to the same engine that handles PROC >SQL--you can't use that wildcard in SQL either, I don't think... > >-Roy > >-----Original Message----- >From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Ya >Huang >Sent: Tuesday, March 25, 2008 9:45 AM >To: SAS-L@LISTSERV.UGA.EDU >Subject: Colon modifer doesn't work for where statement? > >Just noticed I can't use ...

RE: wxMac: SetFocus() for a wxScrolledWindow doesn't work #3
Hi Robert could you please try whether the following works as well : in src/mac/carbon/window.cpp line 1052 immediately after the return ; in case of errCouldntSetFocus for the m_peer->SetFocus() line add the same idea :=20 SetUserFocusWindow((WindowRef)MacGetTopLevelWindowRef()); if this solves the problem as well, I'd prefer it Thanks, Stefan > -----Original Message----- > From: Robert J. Lang [mailto:robertlang@earthlink.net]=20 > Sent: Donnerstag, 8. Dezember 2005 19:35 > To: wx-users@lists.wxwidgets.org > Subject: Re: wxMac: SetFocus() for a ...

Re: Moderate doesn't work (no such thing as moderate circumcized) #3
> > > > All or nothing. Republican or Democrat. > > > > > > See the tradition comes from Abraham Mustafa Arafat Lincoln as a Continental tradition, > > > 4 scores and 4 thousand years ago, he punked his appearance at age 99 himself > > > with a sharp tool. As an ancient punk, he declared his appearance 'perfect' as > > > God does not forskin women, thus the perfect admirable holy dick in the > > > tradition of punk traditon, and there is something about it, unspeakable > > > and voodoo. But from this we find the...

Re: 'just' option doesn't work in proc format ?
Hi, The format of the format needs to be a little different ... Try proc format; invalue yy (just default=20) '1.2' = 0 ; run; The options for the invalue need to be in brackets, otherwise PROC FORMAT will think the first value it has to format is "just1.2". The "default=20" part is required, otherwise the comparisons will be done within the length of the format string (3 in this case for "1.2"). Regards ++ Guido. On 27/09/2007, Ya Huang <ya.huang@amylin.com> wrote: > > Hi there, > > According to SAS Online Doc, 'JUS...

SAS TIP: Using Noprint and Ods output together? Doesn't work!
Have ever used the ODS OUTPUT statement to put output into a SAS dataset and then used the noprint option so that the output does not print in the output window? If so, then you know that this does not work. The SAS dataset is empty! The noprint option prevents output from going to any ODS destination, so you cannot use it. However, if you do not want your output to print in the output window, then there is an alternative. ODS Listing Close; This statement prevents any output from showing in the output window, but still allows the ODS OUTPUT statement to store the results in the SAS dataset. Note: The above statement prevents ALL output from going to the output window until you turn the listing back on. Here's how to turn it back on: ODS Listing; Enjoy! Wendi ************************************************************************** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ...

Re: SAS xport to R: doesn't work, at least in Open VMS #2
>> Hi, everybody, >> I am a "long time SAS user" not an R user. I have got a task to >> transfer to R some SAS datatsets. Forst I started to pilot xport files >> created by SAS. However, for some unknown reason, R doesn't recognize >> the xport format created by SAS in Open VMS saying >> >> > test1= read.xport( "NEW_DSIN.XPT") >> Error in lookup.xport(file) : file not in SAS transfer format >> >> I have created these files using several ways. >> 1. >> >> libname xpt xport "NEW_D...

Re: Get["file.mx"] doesn't work #2 #3
Wow. Take away message? NEVER save to .mx format. EVER. Too many things can go wrong. Bobby On Wed, 18 May 2011 06:14:29 -0500, Scot T. Martin <smartin@seas.harvard.edu> wrote: > To add to what Albert writes, somewhat surprisingly to me the .mx format > also depends on the storage medium. That is, when using the same machine > (i.e., control therefore on OS and 32/64-bit), I have made .mx files and > stored that to my local hard drive. I then copy those files over to a > network drive, which I believe is Linux but appears to me just as a > ...

Re: SAS xport to R: doesn't work, at least in Open VMS #4
i just like to use a lightweight db to bridge sas and r, such as a mdb or sqlite. and it works pretty well. i think it is much better than conversion to csv, since the data attributes will be preserved. On 6/27/07, Vlad <vladislav.moltchanov@ktl.fi> wrote: > Hi, everybody, > I am a "long time SAS user" not an R user. I have got a task to > transfer to R some SAS datatsets. Forst I started to pilot xport files > created by SAS. However, for some unknown reason, R doesn't recognize > the xport format created by SAS in Open VMS saying > > > test1= ...

RE: [tao-bugs] BiDirectional GIOP Tests doesn't work anymore #2
Hi, > >>thanks for the answer. > >>Yes, I know, 'AIX is a platform that is not tested at all for TAO', > >>but we are using TAO since about 4 years on AIX with g++ > >>and Bidirectional GIOP was working all the time. > > > > > > We did a lot of work before the summer for AIX with Visual Age. > > But not for g++ :-) No, the customer uses Visual Age. > > Run the server at debug level 10 and look at the output why > the server > > recreates a new connection? Maybe dns is broken? > > No, dns is not broken, but with debug level 10, TAO is saying for the > callback: > > Transport_Cache_Manager::find_i, no idle transport is available > > That is, he simply couldn't find the existing Connection and then > makes a new connection. Could you post a little bit more of the log, maybe it triggers something? Johnny ...

Re: Re: SphericalPlot3D doesn't work
David, I'm not sure if this is an old message. But, just in case you still need some help, I tried running your program and found no problems. To make a cylindrical or spherical plot, you first need to execute the following command: <<Graphics`ParametricPlot3D`; This command will load the standard package ParametricPlot3D.m. Then, you will need to execute the following command: SphericalPlot3D[2, {theta, 0, Pi}, {phi, -Pi, Pi}]; This should produce the results you are looking for. If you need a soft copy of the notebook that I created, please let ...

TCL 'infotag get med_envelope_from' doesn't work on IOS 12.3(6) ?
Hallo, Does anybody know why I cant use: infotag get med_envelope_from on IOS 12.3(6) ? How can I obtain e-mail from address in mmoip dial-peer application (off-ramp fax). Thank you in advance, Hypnos ...

Web resources about - Re: ods/pdf startpage=never doesn't work anymore in v92? #3 - comp.soft-sys.sas

Resources last updated: 3/16/2016 12:41:58 PM