View previous topic :: View next topic |
Author |
Message |
Rahul Bansal Beginner
Joined: 18 May 2003 Posts: 9 Topics: 3
|
Posted: Fri Sep 19, 2003 6:32 am Post subject: TSQ Delete! |
|
|
Hi,
I am using the PB as a front end and CICS as a backhand. and we have a mainframe connect as a middleware. We code the RSP that communicate with the screen of the front end.
The Problem we are facing is the TSQ. Our CICS_DB2_COBOL programs created TSQs. Now we are asked to code a prg to delete all TSQ starts fro LR*.
Can you suggest any other solution apart from coding Program ???
What would be the logic in case if we use the CICS program ??
The normal manual process to delete the TSQ we follow is::
open the CICS screen--> CEMT I TSQ(LR*)-->Pick up the TSQ name one by one and--> CEBR Tsqname-->> PURGE...
Now we nned to automate the above process.
Thanks
Rahul |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12378 Topics: 75 Location: San Jose
|
Posted: Sat Sep 20, 2003 5:32 pm Post subject: |
|
|
Rahul,
Do you have Omegamon or any other CICS monitoring systems ? If you have Omegamon then then it has a TSQ Wildcard feature, which allows you to delete TSQ's with wild card.
Hope this helps...
cheers
kolusu |
|
Back to top |
|
 |
Mike Chantrey Intermediate
Joined: 10 Sep 2003 Posts: 234 Topics: 1 Location: Wansford
|
Posted: Thu Oct 02, 2003 11:57 am Post subject: |
|
|
Coding a program to do this is not very difficult. Here is a rough pseudo-code outline (which needs error handling, info messages and maybe generalizing for different prefixes of different lengths)
Code: |
startkey = low-values
startkey(1:2) = 'LR'
endkey = high-values
endkey(1:2) = 'LR'
EXEC CICS INQUIRE TSQNAME START AT(startkey)
EXEC CICS INQUIRE TSQNAME (delkey) NEXT
WHILE delkey <= endkey DO
EXEC CICS DELETEQ TS QNAME(delkey)
EXEC CICS INQUIRE TSQNAME (delkey) NEXT
ENDWHILE
EXEC CICS INQUIRE TSQNAME END
|
Note that the above example is for CICS/TS releases with long TSQ name support and so the key fields should be 16 bytes for long queue names. It's easily adapted for earlier releases - check the programmming ref for your release and change the queue name parameters accordingly. |
|
Back to top |
|
 |
|
|