View previous topic :: View next topic |
Author |
Message |
deepa12 Beginner
Joined: 05 Apr 2005 Posts: 131 Topics: 64 Location: chennai
|
Posted: Mon Oct 30, 2017 3:28 am Post subject: branching from 1 foreground task to another application |
|
|
We are working on a Depot management System software in COBOL,CICS,VSAM
There is a requirement that when a person walks in a Depot area and is currently doing some work, e.g. picking a product from a location [Application A] & filling a cage to dispatch to stores, he would just see some hazardous things or some spillage on floor which he wants to record somewhere[Application b].
So when he is in the middle of an application, say he presses some key, he needs to be taken into Application B, to enter the details. Once he finishes with this, he would press say PFKEY3 & he needs to be voyaged back to Application A, to the same point where he was working.
In a CICS application, I think we can do this by attaching a TASKREQ(PF24) for application B in CEDA, so that from any application whenever the user presses this key[pfkey24], he would be taken to application B
But we are not clear about how to restore the status of application A
Please suggest
Is it possible to use the Transaction Server concepts of CICS and design the Application A differently, so that the CICS runtime environment would take care of restoring the Application A status. Also let the Application A know that Application B is a call back interface or sort of an interrupt _________________ deepa |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12375 Topics: 75 Location: San Jose
|
Posted: Mon Oct 30, 2017 8:05 am Post subject: |
|
|
deepa12,
Unless this is a trick question why can't you simply LINK tran B from A and after the completion you would get the control back to A.
You can also have a wait state in Tran A and if TRAN B does not come within this reasonable time, it would resume tran A.
This is a simple 101 CICS LINK execrcise. _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
deepa12 Beginner
Joined: 05 Apr 2005 Posts: 131 Topics: 64 Location: chennai
|
Posted: Mon Oct 30, 2017 11:08 pm Post subject: |
|
|
Thanks a lot. We will try this
1. Actually in this environment they have always used only XCTL for foreground transactions, instead of link. I think the reason for this is they do not want to lock the resources - memory & CI LOCK Is this the only reason or could there be any other reason
2. The frequency of this transaction B is not going to be much. So i think even if we Link, it will not bring down the overall online performance or response for other active tasks. Is it not.
3. Also by ' have a wait state in Tran A' as i understand is the usage of POST,DELAY commands or is it any other CEDA definition _________________ deepa |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12375 Topics: 75 Location: San Jose
|
Posted: Tue Oct 31, 2017 8:33 am Post subject: |
|
|
deepa12 wrote: |
3. Also by ' have a wait state in Tran A' as i understand is the usage of POST,DELAY commands or is it any other CEDA definition |
Check this link which explains in detail about How tasks are made to wait _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
|
|