|
View previous topic :: View next topic
|
| Author |
Message |
anvit
Warnings : 1
New User
Joined: 25 Jan 2006
Posts: 6
|
|
|
|
Hi,
Consider a case of TWO Application Owning regions(AOR) CICSA and CICSB set up in CICS catering to two different Modules (Mod1 and Mod2) as below:-
CICSA caters to Mod1
CICSB caters to Mod2
I am facing a problem as below:-
1. Enter the Txn for Mod2 in CICSA
2. Dont clear the screen and enter the command CESF.
Ideally it should logoff from CICSa, but its not!
Please help me in this. |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10872
Location: italy
|
|
|
|
I do not see how the issue is related to a mro environment...
anyway a CESF logoff will logoff from the TOR, not the AOR
| Quote: |
| Ideally it should logoff from CICSa.... |
that' s what You would like, but it' s against the 3270 data stream architecture... and CICS use of it
it all depends on hoew the leftover map is built
and in what field of the map You enter the CSSF string
the CICS 3270 data flow will read from the screen and use as transid the chars
found in the first field with the MDT ( modified data tag on )...
if the map is built, as it happens sometimes with a hidden transaction code
in the first field of the map ( PROT/ASKIP/DARK/MDTon)
CICS will invoke that transaction regardless of what the user enters on the screen |
|
| Back to top |
|
|
anvit
Warnings : 1
New User
Joined: 25 Jan 2006
Posts: 6
|
|
|
|
Hi,
The issue is related to MRO.
Considering the above case, once in the CICSA, on requesting the Transaction for MODB, the data would be passed to XCTL would be picked from CICSB. Hence the request now would be sent from CICSB to logoff off from CICSA which would be rejected.
Just to give the message of CICSLOG:-
AOR 1:-
HICSJHB1 Request from system JHC1 to initiate transaction CESF on that system on terminal HICSJHB1.hBac was not executed. Transaction invalid on this system.
AOR 2:-
HICSJHC1 Transaction CESF not executed on terminal HICSJHB1.hBac on system JHB1. Transaction invalid on that system. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| CESF is not working as expected in MRO Environment |
It may be that you need to change your expectation. . .
| Quote: |
| that' s what You would like, but it' s against the 3270 data stream architecture... and CICS use of it |
This is why you may need to change the way these transactions are implemented.
How long has this worked successfully in production? Is this some completely new set of transactions? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10872
Location: italy
|
|
|
|
again
You do not logoff from an AOR, YOU LOGOFF FROM A CICS ENVIRONMENT...
the logon logoff is independent from the AOR setup....
if in Your organization, logon logoff is dependent on the AOR setup,
well, it would be better to review the understanding of the whole thing |
|
| Back to top |
|
|
anvit
Warnings : 1
New User
Joined: 25 Jan 2006
Posts: 6
|
|
|
|
Hi,
Understood ur point of view.
But in our case now AORs and TORs are in one region.
Going as per the updates given by u,
CICSA is the region defined for TORA
CICSB is the region defined for TORB
In case of MRO, we could execute Txns associated with TORB in CICSA and viceversa.
But we come to the same question again, I fire Txn associated with TORB in CICSA. Having this done we fire CESF to logoff from the screen.
Its not able to logoff as when we are firing the TORB in CICSA, the control has been passed to CICSB. When we fire CESF, then CICSB send a request to CICSA to logoff which is terminated.
Please do let me know if my understanding is correct. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10872
Location: italy
|
|
|
|
calling the same thing with two names is confusing...
so You have two FULL cics regions
each region own some terminals/ a terminal can logon to each cics independently ??
that' s not strictly speaking MRO
if You work independently in each region does the cesn and cesf stuff work...
connect to CICSA, logon/logoff does it work ??
connect to CICSB, logon/logoff does it work ??
if You get the message transaction invalid on this system then Your setup must be reviewed
looks like in one of the two systems the logon/logoff group has not been defined, or has been defined improperly
but why not have a true MRO with a single TOR and all the rest,
might be simpler to manage
or somehow also the cesf is in some remote grou
never had this kind of problem  |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hi Enrico,
| Quote: |
| never had this kind of problem |
Probably because your systems had either stand-alone cics regions or a properly set up mro environment.
This hybrid configuration may offer considerable long-term support "opportunities". |
|
| Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006
Posts: 475
|
|
|
|
| Quote: |
Enter the Txn for Mod2 in CICSA - don't clear screen, enter
CESF
|
Sounds like Txn for MOD2 has performed an
EXEC CICS RETURN TRANSID ('TXN')
which is always going to cause it to return to TXN for MOD2
What results do you get when you enter CESF transaction ?
run your TXN through a debugger' and if you still can't resolve,
contact your CICS Systems Programmer |
|
| Back to top |
|
|
|
|
