Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

CESF is not working as expected in MRO Environment

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CICS
View previous topic :: :: View next topic  
Author Message
anvit
Warnings : 1

New User


Joined: 25 Jan 2006
Posts: 6

PostPosted: Sun Nov 02, 2008 8:40 pm    Post subject: CESF is not working as expected in MRO Environment
Reply with quote

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
View user's profile Send private message

enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10232
Location: italy

PostPosted: Sun Nov 02, 2008 10:20 pm    Post subject: Reply to: CESF is not working as expected in MRO Environment
Reply with quote

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
View user's profile Send private message
anvit
Warnings : 1

New User


Joined: 25 Jan 2006
Posts: 6

PostPosted: Sun Nov 02, 2008 10:47 pm    Post subject: CESF is not working as expected in MRO Environment
Reply with quote

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
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Sun Nov 02, 2008 11:13 pm    Post subject:
Reply with quote

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
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10232
Location: italy

PostPosted: Sun Nov 02, 2008 11:50 pm    Post subject: Reply to: CESF is not working as expected in MRO Environment
Reply with quote

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
View user's profile Send private message
anvit
Warnings : 1

New User


Joined: 25 Jan 2006
Posts: 6

PostPosted: Mon Nov 03, 2008 12:19 am    Post subject:
Reply with quote

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
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10232
Location: italy

PostPosted: Mon Nov 03, 2008 12:42 am    Post subject: Reply to: CESF is not working as expected in MRO Environment
Reply with quote

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 icon_biggrin.gif
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Mon Nov 03, 2008 5:56 am    Post subject:
Reply with quote

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
View user's profile Send private message
Earl Haigh

Active User


Joined: 25 Jul 2006
Posts: 475

PostPosted: Mon Nov 03, 2008 6:49 am    Post subject:
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CICS All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Join giving more records than expected Danielle.Filteau SYNCSORT 2 Thu Mar 09, 2017 3:28 am
No new posts SQL query not working in Cobol program. CuriousMainframer COBOL Programming 14 Wed Feb 22, 2017 5:56 pm
No new posts SCRNAME not working on my mainframe? mrsidhu12 TSO/ISPF 7 Thu Sep 01, 2016 2:17 pm
No new posts 2 same CLIST pgm but with different n... boyti ko CLIST & REXX 5 Fri Jun 03, 2016 4:55 pm
No new posts REXX Screen not working due to LINKED... sundarkudos CLIST & REXX 1 Mon May 09, 2016 1:44 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us