Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Cobol job taking too long

Author  Topic 

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2003-05-28 : 18:12:28
Hi,
I have a cobol sql job which used to take 30 mins to run which now is taking 50-60 mins to run. This is happening after we rolled out a new PS module to a larger group (we added another web server to anticipating more traffic) but the new group has nothing to do with this cobol job. Web server admin thinks there is nothing wrong with the web server. Since, I don't know cobol, I thought of starting running the cobol job with trace on. Is this the right way to go?
Thanks,
Sarat.

**To be intoxicated is to feel sophisticated, but not be able to say it.**

nr
SQLTeam MVY

12543 Posts

Posted - 2003-05-28 : 18:40:03
If you don't know what it's doing just run the profiler to log things.


Lucky you - an opportunity to learn cobol.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-05-28 : 18:45:50
Yes run SQL Profiler to determine what the problem is. You should also consider updating the statistics and rebuilding the indexes.

Tara
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2003-05-29 : 15:11:23
quote:

Hi,
I have a cobol sql job which used to take 30 mins to run which now is taking 50-60 mins to run.



Sounds like a cursor to me

quote:

This is happening after we rolled out a new PS module to a larger group (we added another web server to anticipating more traffic) but the new group has nothing to do with this cobol job.



What's the rate of growth of the data?

quote:

Web server admin thinks there is nothing wrong with the web server.



Don't they always? (It's always a database problem)

quote:

Since, I don't know cobol



Lucky You..add 10 to 15 years to your age and you would...

quote:

I thought of starting running the cobol job with trace on. Is this the right way to go?



Yup...But I thought PeopleSoft (actually PeopleHard) was all written using SQR?

Saw a developer who decided to write extracts as 7 levels of nested cursors...HUGE overhead..

And if it is COBOL (does anyone knows what that means?) What platform is it running? Never heard of a COBOL Compiler for NT?




Brett

8-)
Go to Top of Page

chadmat
The Chadinator

1974 Posts

Posted - 2003-05-29 : 15:16:04
quote:
Never heard of a COBOL Compiler for NT?



There is a a COBOL.Net compiler. At least so I've heard (Never seen it)

-Chad

http://www.clrsoft.com

Software built for the Common Language Runtime.
Go to Top of Page

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2003-05-30 : 16:14:51
Actually PS is written in C++ and SQL. Ofcourse now the web version includes Java, HTML etc. I think there are about 20 additional transactions affecting about 8-10 tables since the new application roll-out which ofcourse have nothing to do with cobol job that affects payroll tables except for increase in database hits.
I don't anything about cobol or its compiler but I do have a group of cobol programmers but i wanted to see if i can get anything from profiler first.
SQR is a reporting tool (Ex: crystal) but ofcourse with a lot more functionality.
thanks,
Sarat

**To be intoxicated is to feel sophisticated, but not be able to say it.**
Go to Top of Page

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2003-05-30 : 16:48:05
Ok, I asked a cobol prog to look at this issue. he says it is a mere calculation prog which gets/sends values from/to other cobol programs. This program doesn't give any file(table) names either so i can only guess the table names by field variable names.
so, should my expectation from profiler readings be to see what other transactions are occuring (which i know are very minimal) but not necessarily what the cobol job is doing?
Well, in that case, i may as well rebuild indexes or update stats for the tables i think are getting updated.
Thanks,
Sarat


**To be intoxicated is to feel sophisticated, but not be able to say it.**
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2003-06-02 : 10:39:44
That's not true...if the COBOL program does not include a DCLGEN, then it's not using sql tables...(at least that's what I recall from DB2). Maybe it's different, but I don't know how it would set up the declarations...

Also, COBOL usually use "EXEC SQL" "END EXEC" statement to define when it makes a SQL Call...

You should see these (again, read disclaimer above).



Brett

8-)
Go to Top of Page

gfahrlander
Starting Member

23 Posts

Posted - 2003-06-02 : 11:25:08
COBOL - COmmon Business Oriented Language. Started using it in 1978. Even had a compiler for a TRS-80 (step up from IBM-029 card punch/reader). Even had the honor of meeting Commodore Grace Hopper, USN -- who gave me a nanosecond.
Have your COBOL types find the calling programs and what tables they're accessing. Check your bind parameters for the calling programs and run an explain on the calling programs.

Gary
IBM Certified Solutions Expert
DB2 UDB V7.1 Database Administration
for OS/390

MCDBA - Someday Soon!!

No trees were killed in posting this message. However, a large number of electrons were seriously inconvenienced!
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2003-06-02 : 12:34:52
quote:

Check your bind parameters for the calling programs and run an explain on the calling programs.



Gary,
I think that most of the people at this site think you're talking martian.



I can't even get DB2 COBOL programmers to do an EXPLAIN, and never mind try to have a discussion about set based processing?

Ever meet Bonnie Baker?

Sheer Genius..."Nulls, much ado about nothing"...excellent.



Brett

8-)
Go to Top of Page
   

- Advertisement -