Code to find weekends in Sybase.


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Code to find weekends in Sybase.
# 1  
Old 11-26-2008
Code to find weekends in Sybase.

Hi All,

I need a help here, actually i want SQl code which will determine all Saturdays and Sunday in given year (say 2009) and display it's dates.

E.g :-
3 ---> Saturday
4 --> Sunday (for 2009) and so on.

Thanks in Advance for help.

Regards,
Arvind.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Programming

Sybase ASE: Query to find correct format issue.

Hi Team , I am new to Sybase Adaptive Server Enterprise/15.7 (ASE) and need some guidance to find the different values in serial format column. SELECT DISTINCT SERIAL_FORMAT FROM PRODUCTS It has values with below format which contains 12 digits hexadecimal characters with... (2 Replies)
Discussion started by: Perlbaby
2 Replies

2. Shell Programming and Scripting

Script to find n.of weekdays and n.of weekends in a given date

Hi All, Could you please provide the shell script to find number of weekdays and number of weekends for a given date for that month. Monday to friday should be considered as weekdays and Saturday and Sunday should be considered as weekends. Date should be passed as parameter. For... (13 Replies)
Discussion started by: ROCK_PLSQL
13 Replies

3. Emergency UNIX and Linux Support

Help with Sybase DB

Hi, I'm facing an emergency situation, wherein I have to provide limited support to a Sybase DB temporarily as the DBA was fired. There is an urgent need of adding to users to the database. After some time on google, I was able to gather the below information on the database setup ... (1 Reply)
Discussion started by: maverick_here
1 Replies

4. Shell Programming and Scripting

Sybase server

I have requirement to connect to different sybase server's and store the data into flat file and load into oracle using sqlloader for each day drop the table and re create it and load the data based on business date as parameter which was taking from parameter file.Any help on this should be... (0 Replies)
Discussion started by: mohan705
0 Replies

5. Shell Programming and Scripting

Sybase 12/15 compatability

This is more a database problem than a shell one, but we have a problem affecting our scripts, so I'm stretching the limits a bit! ;) We're in the process of migrating our application and a large number of associated scripts from Sybase 12.5.4 to Sybase 15. Scripts using 'isql' and 'bcp' include... (1 Reply)
Discussion started by: JerryHone
1 Replies

6. Shell Programming and Scripting

sybase::bcp

I am trying to bcp in using sybase::bcp perl module. I can find we can give user, pwd and server name in the parameters. How can I give database and table name? (1 Reply)
Discussion started by: Deei
1 Replies

7. What is on Your Mind?

What do you do during weekends ? :)

Its been a while since we had any fun polls or interesting topics in this forum. So, here I start a thread rather calling it as a question - " What do you do during weekends ? :) " For many, on hearing the term - weekends should excite them :b: for ( few ) some - uhhh .. its just another day... (11 Replies)
Discussion started by: matrixmadhan
11 Replies

8. Shell Programming and Scripting

sybase and shell

I am writing a shell script that verifies if a device is created on wrong mounts 1> sp_helpdevice 2> go | awk '{print $2}' | grep database | grep -v `df -k | grep /dev/dsk | awk '{print $6}'` So if things are ok, the output should return nothing If the result gives 1 or more entry, then... (1 Reply)
Discussion started by: melanie_pfefer
1 Replies

9. Solaris

Connect From VB to Sybase 11

Dear All I have a problem that I can't connect from VB to Sybase 11. Could you help me? (2 Replies)
Discussion started by: Than Chanroeun
2 Replies
Login or Register to Ask a Question
invcutter(1)						      General Commands Manual						      invcutter(1)

Name
       invcutter - generate subset inventory files

Syntax
       /usr/sys/dist/invcutter [ -d ] [ -f root-path ] [ -f version-code ]

Description
       The  command  reads master inventory records from standard input.  A subset inventory record is written to standard output for every record
       read from the input. The information contained in the output record is derived from the input record and the file attribute information	in
       the file hierarchy rooted in the current directory.

Options
       -d		   Enable debugging. No useful diagnostics are printed.

       -f root-path	   Specify an alternate root path for finding file attribute information.

       -v version-code	   Specify a 3-digit version code for use in the version field of the output records. The default version code is 010.

Restrictions
       All input records must be sorted in ascending order on the pathname field.

       Files described in an input record which exist as sockets in the file hierarchy are not processable.

       If a file is described in an input record has a link count greater than 1, all other links to the file must be represented in the input.

Examples
       The following command will generate inventory records for the master inventory entries in PDS020.mi containing version fields set to 020:
	   invcutter -v 020 < PDS020.mi

Return Values
       An exit status of 0 is returned if all goes well. An exit status of 1 is returned if an error occurs. See Diagnostics.

Diagnostics
       "cannot chdir to pathname (error-message)"
       The  program  cannot  change  directories to the pathname directory specified with the -f option. The error-message will provide additional
       information.

       "sort error, record #n"
       The nth input record is not in the correct sort order. All input records must be in ascending  ASCII  colating  sequence  on  the  pathname
       field.

       "cannot stat filename (error-message)"
       An error has occurred attempting to read the attributes of filename.  The error-message explains exactly what happened.

       "pathname: illegal file type code 0140000"
       The file pathname is a socket. Sockets are not supported as valid file types for distribution.

       "unresolved nlink n: pathname"
       This indicates that file pathname in the master inventory is linked to n files which do not appear in the master inventory. Check inventory
       for validity with the program.

       "n unresolved hard links"
       This is an informational message stating how many files were detected in the input inventory which had unresolved links.

See Also
       newinv(1), stl_inv(5), stl_mi(5)
       Guide to Preparing Software for Distribution on ULTRIX Systems

																      invcutter(1)