| Title: | VAX/DEC COBOL |
| Notice: | Kit,doc,performance talk info-->DIR/KEY=KIT or DOC or PERF_TALK |
| Moderator: | PACKED::BRAFFITT |
| Created: | Mon Feb 03 1986 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3250 |
| Total number of notes: | 13077 |
My customer has severall cobol programs, ran in batch mode, that are
taking a long time and he would like to try reducing the elapsed time.
With Decps PC sampling I noticed they are all spending substantial time
in EXE$ALLOCATE and EXE$DEALLOCATE pagedpool memory allocation/dealloc
routines. The programs are either accessing local sequential files and
spending an other substantial amount of time in RMS module (unresolved
part) or making calls to a remote Sybase database over TCPIP (Sybase
SQL cobol generator). There is also an important SPM synchro overhead
which, I suspect is mainly caused by the memory alloc/dealloc calls.
My question is: is there any way to reduce calls to EXE$ALLOCATE and
EXE$DEALLOCATE routines ?
There is plenty of memory on the system.
VMS 6.2 - COBOL 5.2
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3198.1 | no answers ?? | BACHUS::PETRIOLI | Tue Feb 25 1997 05:46 | 4 | |
Is my question so stupid that nobody answer ?
/Albert.
| |||||
| 3198.2 | QUARRY::neth | Craig Neth | Tue Feb 25 1997 11:50 | 5 | |
It's not a bad question, I just don't think anybody that frequents this conference has any idea what might be going on. I think you would have better luck in VMSNOTES - nothing in COBOL or the runtime system directly calls EXE$ALLOCATE - it must be something that RMS or some other system service is doing... | |||||
| 3198.3 | It is remote access to Sybase db. | BACHUS::PETRIOLI | Fri Feb 28 1997 06:19 | 12 | |
RE: -1
Thanks for your answer.
It is not RMS, it is the remote access to Sybase db. And this is code
created by Sybase Cobol generator.
I'll try on VMSNOTES.
Regards,
Albert.
| |||||