|
"Pears"
There are a few trees in a garden. On one of them, a pear tree, there are pears (quite logical).
But after a strong wind blew, there were neither pears on the tree nor pears on the ground. How come?
|
Geocaching (pronounced geo-cashing) is a worldwide game of hiding and seeking treasure. A geocacher can place a geocache anywhere in the world, pinpoint its location using GPS technology and then share the geocache's existence and location online. For more, click here. 
BSP's NJ office has sent a Geocache to our HQ in Chicago, and you can help get it there!
To Track Progress click Here! |
|
Join COGNOiSe.com, the largest independent, worldwide FREE IBM Cognos Support Community.
Access our
|
|
| Greetings!
Welcome to this month's BSP Newsletter. We have a lot of educational content this month, along with some great tips and tricks and other IBM Cognos related information as always! And remember, we enjoy hearing your suggestions regarding the content you'd like to see. Please e-mail us at Newsletter@brightstarpartners.com if you have a topic you'd like to see discussed in future newsletters. |
|
Over the past several years, BSP has managed and participated in Cognos User Groups throughout North America. Our recent Illinois user group, co-sponsored with The Nielson Company, was a tremendous outing. This month we will be visiting our friends in Quebec and Ohio at their local user group meetings, where we'll be presenting some of our Implementation-Based Software offerings and leaving behind a free product for all attendees!
We'd like to thank the many cities, states and Canadian provinces that have welcomed us at their local user groups, and we hope to see each of you at a user group meeting near you.
If you have any questions regarding user group participation or are interested in speaking with us about our experience running, presenting at and attending user group meetings, please contact Andy Rachmiel. |
| BSP SOFTWARE DELIVERS RECYCLE BIN FOR COGNOS |
 One of the most common fears we have as Cognos authors, developers and consumers is being able to recover from the inadvertent (or advertent) delete of an artifact (report, query, etc.).
Unlike Windows files, Cognos content is permanently deleted when deleted from Cognos Connection.
To see a product overview recording, please click here here. |
| STUMP THE DEVELOPERS WEBINAR |
|
On March 17th, BSP Software hosted a Stump the Developers webinar where many of our customers fired off challenges in their IBM Cognos environments and a few of our lead developers were put on the spot to solve them with MetaManager. The webinar was a huge success and a lot of fun for us and the attendees.
Please visit www.bspsoftware.com and register for a free account on the site. Once logged in, you can view this and other tips and techniques in the BSP Software Podcast Channel, located under Support >> Podcasts or by clicking http://www.bspsoftware.com/podcasts. | |
THE ISSUE OF USER ADOPTION |
 By Dustin Adkison, Solution Specialist, BrightStar Partners
Adapting a new technology is really quite simple... until the users get involved. If only we could build out our perfect Cognos environment like the one that we see in all of the demos and magically all of the users would flock to it. Unfortunately, in reality, user adoption is never that simple. Unlike technology, there is no manual or guide to user adoption. Most of us work in an environment where IT and business are quite separate. In these types of environments, there is a huge disconnect. This can manifest itself as simple issues like, "who pays for this technology?" Or they can be more complex like, "who owns this technology and is responsible for its success?" This article addresses practical ways for an IT group implementing Cognos to increase user adoption and gain business buy-in.
Click here to read the complete article. |
ENABLING ISAPI ON A 64 BIT WINDOWS IIS 6.0 |
By Bonnie Hsueh, Consultant
By default, Cognos uses the CGI gateway. For better performance when using Microsoft IIS as your web server, the ISAPI gateway is recommended.
The standard steps to enable ISAPI for a 32 bit do not fully meet the requirements on a 64-bit Windows operating machine. Regardless of whether you have installed the 32-bit or 64-bit version of Cognos 8, the cognosisapi.dll ISAPI module is a 32-bit DLL. In order to run 32-bit applications on 64-bit Windows, you must configure IIS to create 32-bit worker processes to run the 32-bit version of ASP.NET 2.0
For detailed steps with screen shots, click here |
 About Indian Calendar......
History
-
The history of calendars in India is a remarkably complex subject owing to the continuity of Indian civilization and to the diversity of cultural influences.
-
In the mid-1950s, when the Calendar Reform Committee made its survey, there were about 30 calendars in use for setting religious festivals for Hindus, Buddhists, and Jainists. Some of these were also used for civil dating. These calendars were based on common principles, though they had local characteristics determined by long-established customs and the astronomical practices of local calendar makers. In addition, Muslims in India used the Islamic calendar, and the Indian government used the Gregorian calendar for administrative purposes.
-
Early allusions to a lunisolar calendar with intercalated months are found in the hymns from the Rig Veda, dating from the second millennium B.C. Literature from 1300 B.C. to A.D. 300, provides information of a more specific nature. A five-year lunisolar calendar coordinated solar years with synodic and sidereal lunar months.
-
Indian astronomy underwent a general reform in the first few centuries A.D., as advances in Babylonian and Greek astronomy became known. New astronomical constants and models for the motion of the Moon and Sun were adapted to traditional calendric practices. This was conveyed in astronomical treatises of this period known as Siddhantas, many of which have not survived. The Surya Siddhanta, which originated in the fourth century but was updated over the following centuries, influenced Indian calendrics up to and even after the calendar reform of A.D. 1957.
As it exists today
- As a result of a calendar reform in A.D. 1957, the National Calendar of India is a formalized lunisolar calendar in which leap years coincide with those of the Gregorian calendar (Calendar Reform Committee, 1957). However, the initial epoch is the Saka Era, a traditional epoch of Indian chronology. Months are named after the traditional Indian months and are offset from the beginning of Gregorian months (see Table Below).
- In addition to establishing a civil calendar, the Calendar Reform Committee set guidelines for religious calendars, which require calculations of the motions of the Sun and Moon.
- Tabulations of the religious holidays are prepared by the India Meteorological Department and published annually in The Indian Astronomical Ephemeris.
Rules for Civil Use
-
Years are counted from the Saka Era;
-
1 Saka is considered to begin with the vernal equinox of A.D. 79.
-
The reformed Indian calendar began with Saka Era 1879, Caitra 1, which corresponds to A.D. 1957 March 22. Normal years have 365 days; leap years have 366. In a leap year, an intercalary day is added to the end of Caitra.
-
To determine leap years, first add 78 to the Saka year. If this sum is evenly divisible by 4, the year is a leap year, unless the sum is a multiple of 100. In the latter case, the year is not a leap year unless the sum is also a multiple of 400. Table below gives the sequence of months and their correlation with the months of the Gregorian calendar.
Rules for Religious Calendar
- A solar month is defined as the interval required for the Sun's apparent longitude to increase by 30o, corresponding to the passage of the Sun through a zodiacal sign (rasi). The initial month of the year, Vaisakha, begins when the true longitude of the Sun is 23o 15' (see Table 5.2.1). Because the Earth's orbit is elliptical, the lengths of the months vary from 29.2 to 31.2 days. The short months all occur in the second half of the year around the time of the Earth's perihelion passage.
- Lunar months are measured from one New Moon to the next (although some groups reckon from the Full Moon). Each lunar month is given the name of the solar month in which the lunar month begins. Because most lunations are shorter than a solar month, there is occasionally a solar month in which two New Moons occur. In this case, both lunar months bear the same name, but the first month is described with the prefix adhika, or intercalary. Such a year has thirteen lunar months. Adhika months occur every two or three years following patterns described by the Metonic cycle or more complex lunar phase cycles.
- More rarely, a year will occur in which a short solar month will pass without having a New Moon. In that case, the name of the solar month does not occur in the calendar for that year. Such a decayed (ksaya) month can occur only in the months near the Earth's perihelion passage. In compensation, a month in the first half of the year will have had two New Moons, so the year will still have twelve lunar months. Ksaya months are separated by as few as nineteen years and as many as 141 years.
- Lunations are divided into 30 tithis, or lunar days. Each tithi is defined by the time required for the longitude of the Moon to increase by 12o over the longitude of the Sun. Thus the length of a tithi may vary from about 20 hours to nearly 27 hours. During the waxing phases, tithis are counted from 1 to 15 with the designation Sukla. Tithis for the waning phases are designated Krsna and are again counted from 1 to 15. Each day is assigned the number of the tithi in effect at sunrise. Occasionally a short tithi will begin after sunrise and be completed before the next sunrise. Similarly a long tithi may span two sunrises. In the former case, a number is omitted from the day count. In the latter, a day number is carried over to a second day.
|
Months of the
Indian Civil Calendar |
Days |
Correlation of
Indian/Gregorian |
|
1. Caitra
2. Vaisakha
3. Jyaistha
4. Asadha
5. Sravana
6. Bhadra
7. Asvina
8. Kartika
9. Agrahayana
10. Pausa
11. Magha
12. Phalguna |
30*
31
31
31
31
31
30
30
30
30
30
30 |
Caitra 1 March 22*
Vaisakha 1 April 22
Jyaistha 1 May 22
Asadha 1 June 22
Sravana 1 July 23
Bhadra 1 August 23
Asvina 1 September 23
Kartika 1 October 23
Agrahayana 1 November 22
Pausa 1 December 22
Magha 1 January 21
Phalguna 1 February 20 |
* In a leap year, Caitra has 31 days and Caitra 1 coincides with March 21
Next Month....The Chinese Calendar..... |
|
|
