|
View previous topic :: View next topic
|
| Author |
Message |
mpketkar
New User
Joined: 27 Dec 2006
Posts: 3
Location: Mumbai, India
|
|
|
|
Hello all,
I am new to CICS. But now I have a problem to solve.
Situation: We have a Job Stream which process the supply data information. This data is stored in DB2 tables. Also we have some CICS screens where manual entries of Supply data is possible.
If I start the job stream and some user is logged in to the CICS screen, one job would abend.
Question: As we can find in SDSF the users which are logged in to TSO, is there any way I can find out the users which are logged in to CICS region. And is it possible to end their sessions? |
|
| Back to top |
|
 |
raghunathns
Active User
.jpg)
Joined: 08 Dec 2005
Posts: 127
Location: rochester
|
|
|
|
in your problem.. the db2 will take care of locks. you dont have to worry about the program. the program will not abend. but if any one is updating a record then you wont get the access to that record. so you get that record in your next batch run.
you can get the userlist currently logged in and terminate the user using this transaction but you need a supervisor privillege to do that. i think no one will allow to terminate the user by application program. |
|
| Back to top |
|
|
Mickeydusaor
Active User
Joined: 24 May 2006
Posts: 258
Location: Salem, Oregon
|
|
|
|
I don't think you want to terminate the users signed on, why not just
disable your cics transaction and then process your data, then enable
you cics transaction. |
|
| Back to top |
|
|
Earl
Active User
Joined: 17 Jun 2007
Posts: 148
Location: oklahoma
|
|
|
|
suggest you review vendor product BatchCICS-Connect, you can write cobol application to get at any thing in related cics region. (if you have the right security access).
From the batch program;
You can disable CICS transaction, close DB2 to CICS, execute logic
to update DB2, then open DB2, and enable CICS transaction.
OR
you could run a CICS program that performs DB2 update without close,
disable, open, enable.
more info at Use [URL] BBCode for External Links |
|
| Back to top |
|
|
Mickeydusaor
Active User
Joined: 24 May 2006
Posts: 258
Location: Salem, Oregon
|
|
|
|
Earl, I would find it very hard to see a vendor product that would
try to close the cics DB2 tread, number one its not required to
close DB2, number 2 I doubt that your system programs would
even let this happen if it was even possible. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
If you disable the transaction(s), shouldn't that be sufficient  |
|
| Back to top |
|
|
Mickeydusaor
Active User
Joined: 24 May 2006
Posts: 258
Location: Salem, Oregon
|
|
|
|
Dick, Thank you. as I stated that and Its really the only safe and
logical thing to do. |
|
| Back to top |
|
|
Earl
Active User
Joined: 17 Jun 2007
Posts: 148
Location: oklahoma
|
|
|
|
Mickeydusaor,
sorry, my comments was not meant to suggest close entire DB2 thread.
I am not a DB2 guru by any means, so was emulating how it could be accomplished if VSAM file.
Disabling the transaction might solve the existing condition, but I would
think cause grief for the CICS terminal users.
From what I understand of vendor product, you can run any CICS
transaction , including CEMT (if you are authorized). Your right, Systems
programmer would want to control this.
However, the product could be used to write COBOL code that would run the CICS Supply entry screens and logically feed batch updates from the program.
No need to disable transaction and no impact on CICS terminal users. |
|
| Back to top |
|
|
|
|
