| View previous topic :: View next topic |
| Author |
Message |
chintakindi
Beginner
Joined: 05 May 2003
Posts: 1
Topics: 1
|
 Posted: Mon May 05, 2003 2:51 pm Post subject: CICS Working Storage Issue |
 |
|
CICS research of the problem has found that the majority of the EDSA storage is being consumed by program working storage. The process calls an extensive amount of programs. Each call is building a working storage area for each program. This storage continues to build until the CICS transaction ends at which time it is released.
It was thought the use of the cobol Cancel command would free the working storage before task termination, i.e. CALL program-x / CANCEL program-x
However testing the use of the CANCEL command seem not to do anything. No storage was freed in fact it increased storage usage by 50k.
Can someone advise on this please?? |
|
| Back to top |
|
 |
Novice
Beginner
Joined: 27 Dec 2002
Posts: 46
Topics: 15
|
| Posted: Thu Jun 12, 2003 10:29 pm Post subject: |
|
|
CANCEL will initialize the W/S variables back to their initial values. So as far as storage is concerned, it will be of not much use. If you are sure that you won't need some of the modules, try using CICS RELEASE PROGRAM command. This should release the program from the memory.
HTH
Novice |
|
| Back to top |
|
|
Meera
Beginner
Joined: 27 Jun 2003
Posts: 7
Topics: 0
|
| Posted: Fri Jun 27, 2003 9:22 am Post subject: |
|
|
| I am yet to run into w-s hogging storage! The usual scenerio is TSQ hogging storage. Check with tour SysSupport. If you R absolutely sure it is the w-s, then stop "calling" other programs - redesign to exploit xctl. |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
