IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

What is the use of trapping online programs in CICS Xpedior?


IBM Mainframe Forums -> CICS
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
sunnybunny

New User


Joined: 29 Nov 2005
Posts: 49

PostPosted: Tue Feb 14, 2006 11:53 am
Reply with quote

Hi,

Could any one tell me why we need to trap the online programs in CICS Xpeditor? and also what is the difference between trapping Queue triggered programs and by trapping normal CICS programs?


Thanks,
Suneel.
Back to top
View user's profile Send private message
ofer71

Global Moderator


Joined: 27 Dec 2005
Posts: 2358
Location: Israel

PostPosted: Tue Feb 14, 2006 12:25 pm
Reply with quote

Xpediter does not "trap" programs. Xpediter gives you the ability to debus and test online programs interactively, by tracking the program's process.

O.
Back to top
View user's profile Send private message
sunnybunny

New User


Joined: 29 Nov 2005
Posts: 49

PostPosted: Tue Feb 14, 2006 2:18 pm
Reply with quote

Hi,

I think the question what i written is not clear for u. Actually what i want to know is In what situations we need to trap the programs in CICS region? and also what is the difference between trapping Queue triggered programs and some normal online programs in CICS region?
Back to top
View user's profile Send private message
ofer71

Global Moderator


Joined: 27 Dec 2005
Posts: 2358
Location: Israel

PostPosted: Tue Feb 14, 2006 2:29 pm
Reply with quote

Again - you don't trap a program. You set breakpoints and "WHENs", you control varibales' values, and you track the process of your program in order to debug or test it.

Therre is no essential difference in this process between CICS and batch, and no difference at all between queue triggered and "normal" programs.

O.
Back to top
View user's profile Send private message
sreehari_04

New User


Joined: 23 Jan 2006
Posts: 7

PostPosted: Tue May 09, 2006 3:58 pm
Reply with quote

Hi,

When control is coming from another region or from frontend,then u need to set trap as * on Xpeditier option (I did not remember that option)

Hari
Back to top
View user's profile Send private message
vijayamadhuri

Active User


Joined: 06 Apr 2005
Posts: 180

PostPosted: Tue May 09, 2006 6:48 pm
Reply with quote

Hello,

we can set the dump option to yes which gives you the details of why u r program abended if this is what u mean...by trapping the pgm
Back to top
View user's profile Send private message
gskulkarni

New User


Joined: 01 Mar 2006
Posts: 70

PostPosted: Thu May 18, 2006 3:36 pm
Reply with quote

You may need to trap transactions in xpeditor for:

1) Say you are dealing with a system where a java front end triggers a transaction on mainframe by putting a message in MQ (MQ is linked with CICS region so whnever a message is put in that MQ, a transactioin is triggered). Now in this system, your front end must be passing you string of data as input for mainfram CICS program. In testing region, you may want to see if front end has sent correct data and what exactly is the data received when program is being executed.

2) in a DPL transaction execution mode where transactions are remotely defined and a master program in region A, calls a program which is actually executed in Region B. In this case in region B you can set he xpeditor trap to catch a transaction triggered from master program in region A.

To answer teh other part of your questions i will have to be little more detailed.
When you say queue trigerred, I assume that you are talking about a transaction triggerred by putting message in a MQ.
In this case in XPEDITOR, in option 1.6, you can not give USER-ID/NETNAME. because at any point of time your transaction will be executed under one contact user-id. So if 5 different users sitting at 5 different machines trigger same transaction by putting messages in MQ, with different inputs for that same transaction, you can not trap any one particular transaction of those 5. You have to give "*" option while trapping. That will trap transaction regardless of who has trigerred it.

However, if the transaction is triggerred from within the CICS region i.e. non-DPL transactions, you can specify the trap options as USER-ID that is executing the transaction, terminal ID and few other advanced filters. So a specific transaction can be trapped.

i hope that answers most of your questions.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CICS

 


Similar Topics
Topic Forum Replies
No new posts Using API Gateway from CICS program CICS 0
No new posts Calling an Open C library function in... CICS 1
No new posts How to 'Ping' a CICS region in JCL CICS 2
No new posts Parallelization in CICS to reduce res... CICS 4
No new posts Fetch data from programs execute (dat... DB2 3
Search our Forums:

Back to Top