Mark=2C I think you're asking for a bit much.  The problem with holidays is=
 that they're not really standardized.  Some places celebrate holidays that=
 others in the same geographical area don't.  Some companies work on days w=
hen other companies in the same city don't.  The holidays for truckers in N=
ew York is different for those in Miami... and the holidays might change wi=
thin a SAS release.  So many SAS users do their own holiday table lookup.  =
Then they can call in SAS consultants (who get no holidays) to maintain the=
ir custom holiday application. =20

=20

=20

Date: Wed=2C 16 Dec 2009 10:45:01 -0500
From: "Keintz=2C H. Mark" <mkeintz@WHARTON.UPENN.EDU>
Subject: Holiday function needs (WAS: Getting next weekday)
=20
Anders suggested the HOLIDAY function (new in SAS 9.2) to address
one of the concerns brought up for getting the next weekday:
=20
> -----Original Message-----
> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
> Anders M=F8rup Jensen
> Sent: Wednesday=2C December 16=2C 2009 2:47 AM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Re: Getting next weekday
>
> In SAS 9.2 the new SAS function HOLIDAY may be of help.
>
> / Anders
>
>
> "Murphy Choy" <goladin@gmail.com> skrev i en meddelelse
> news:1698639387-1260918779-cardhu_decombobulator_blackberry.rim.net-
> 2067722148-@bda019.bisx.prodap.on.blackberry...
> > Hi=2C
> >
> > I am not sure whether this is useful information. In SAS=2C there is a
> proc
> > calendar that allows you to input holidays and then it produces a
> > calendar. Maybe you can tweak it to produce a calendar list?
> >
> >
=20
=20
Folks=2C given that SAS is a global company trying to serve
global companies=2C I find the HOLIDAY function (restricted to
US and Canadian holidays) disappointing. It would be much
more useful if it would use=2C say=2C the value of the LOCALE
option (with optional override). Something like:
=20
holdate =3D HOLIDAY('holiday'=2Cyear=2C['locale'])=3B
=20
For example: (en_IN =3D=3D LOCALE value for English_India)=3B
=20
next_purim =3D HOLIDAY('PURIM'=2C2010=2C'en_IN')=3B
=20
=20
But even if this extension were made=2C there would still be
a missing piece. The HOLIDAY function returns a date for a
specified holiday=2C but those international SAS clients and
users of international data also need to know whether a
given date is a holiday (and the name of the holiday). So
a complete holiday suite of functions should include
ISHOLIDAY and NAMEHOLIDAY=2C as in:
=20
call_center_empty =3D ISHOLIDAY(sasdatavalue=2C[locale])=3B
** Return 0 or 1 **=3B
=20
and
=20
** Returns a blank if sasdatevalue is not a holiday **=3B
holiday_name =3D NAMEHOLIDAY(sasdatevalue=2C[locale])=3B
=20
=20
And once a NAMEHOLIDAY function is in place=2C it can be combined
with the "locale-ized" HOLIDAY function to make a calendar
relevant to your (or your customer's or vendor's) international
enterprise.
=20
In short=2C it appears that SAS probably got some requests for a
HOLIDAY function=2C but responded at the minimal level=2C rather
seeing an opportunity for real forward-looking added value.
=20
In this case=2C I don't think SAS development even paid attention
to its own marketing emphasis on being a globally-oriented
provider of "business intelligence".
=20
=20
Regards=2C
Mark

                                         =20
_________________________________________________________________
Hotmail: Free=2C trusted and rich email service.
http://clk.atdmt.com/GBL/go/171222984/direct/01/=