Date: Fri, 13 Feb 1998 01:40:38 -0800
Reply-To: "Karsten M. Self" <kmself@IX.NOSPAMHERE.NETCOM.COM>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: "Karsten M. Self" <kmself@IX.NOSPAMHERE.NETCOM.COM>
Organization: Self Analysis
Subject: Re: SOLVED: Watch log while Batch job runs? (Win NT)
Content-Type: text/plain; charset=us-ascii
Stephen & SAS-L
This repeats some information provided in a private post.
SAS's mutithreaded product is (I think) SMTP, standing for Symmetric
Multi-Threaded Processing, and is available for a limited number of Unix
platforms. I've read little, misunderstood much, and forgotten
virtually everything, about this product. There are a couple of SAS
papers/tech notes on this topic, one or more of which may have wormed
into a recent SUGI. Contact your SAS Institute representative for more
information.
The answer I've developed to the read-only profile is to set my standard
session configuration to include RASASUSER, causing SAS to open the
SASUSER profile in read-only (thus sharable) mode. This, of cource,
means that you need to launch a special SAS session with the NORASASUSER
(not read-only SASUSER profile) option to make permanent changes to your
profile configuration. I find that once I set a profile I don't tend to
muck with it. Setting it can take days though....
This solution applyies to all Unixes I'm aware of, and other
multi-user/multi-tasking environments. I stole it from Jack Hamilton's
configuration of our VAX/VMS environment back in the days I worked at
HealthCare COMPARE (now First Health Group Corp., according to my very
own personal stockholder's letter. Gee, I liked it soooo much I bought
the company....).
BTW -- not sure what you're referring to when you talk about resetting
your printer. Is this your printer configuration under the menus
printer configuration, your printer forms, or what? I'll admit I rarely
print directly from SAS, generally preferring the command line.
Stephen A. Mandel wrote:
>
> Karsten,
> In your experience with SAS and UNIX do you understand why SI never
> developed a multithreaded version? It is available under SAS for OS/2.
>
> Also, on our machine(SUN ES6000 Solaris 2.6) I can have multi display
> manager sessions but only 1 session has access to my profile. Is there a
> way to make my profile available to more than one session? It's a pain to
> have to reset my function keys and printer for these other sessions.
>
> TIA,
> Stephen Mandel
>
> ----------
> > From: Karsten M. Self <kmself@IX.NETCOM.COM>
> > To:
> > Subject: Re: SOLVED: Watch log while Batch job runs? (Win NT)
> > Date: Tuesday, February 10, 1998 12:42 AM
> >
> > On Monday, February 09, 1998 10:03 AM, Jack Hamilton
> > [SMTP:jack_hamilton@HCCOMPARE.COM] wrote:
> > > Tom Frenkel <taf2@IS8.NYU.EDU> wrote:
> > >
> > > >SI (are you listening?) please note: This $LOGFLUSH option seems
> > > >*undocumented* (except for, Howard says, Tech Report #55330:
> > > > "SAS/SHARE
> > > >[sic] Technical Report for the Microsoft Windows Enviroment, Release
> > > >6.11"). In particular (unless I just somehow missed it), it is *not*
> > > >mentioned in my SAS online help for NT, nor on the SAS web site. And
> > > >it
> > > >is *not* mentioned in the SAS Win NT companion. But perhaps this is
> > > >because that manual dates back to 1993! This is presumably the most
> > > >"recent" release of that manual, because I just received it from SI a
> > > >few
> > > >days ago.
> > >
> > > In general, system options whose names start with $ are experimental or
> > > unsupported or both. The name will probably change sometime along the
> > > way.
> > >
> > > Under OpenVMS, by the way, the system option name is LOGMULTREAD, and
> > > is documented.
> >
> > It's not always the case thaat undocumented features have dollar strings
> > attached.
> >
> > A similar feature under Unix environments, UNBUFLOG, is similarly
> > undocumented. This option prevents SAS from buffering writes to the
> > session log, and is particularly useful in determining the cause of SAS
> > session crashes which otherwise leave no indication of what went wrong
> > because the final messages were never flushed. I select the option as a
> > matter of course, and have noted no increase in runtime.
> >
> > Note that in Unix, unlike other OSs, mulitiple processes may accell a
> file
> > simultaneously. This *can* lead to interesting circumstances from time
> to
> > time (I generally check before opening an editor to see that I'm not
> > already working on a file), but also makes monitoring SAS much easier.
> >
> > Karsten M. Self (kmself@ix.netcom.com)
> >
> > What part of "gestalt" don't you understand?
> > (Welchen Teil von "Gestalt" verstehen Sie nicht?)
> >
--
Karsten M. Self (kmself@ix.netcom.com)
Use address above, or edit spam trap
from reply address,when responding.
What part of "gestalt" don't you understand?
| 
