How to start a channel automatically in s/390

[gunniya]

I have a sender channel in s/390 QMGR which communicates to Windows NT QMGR. The Disconnect interval that I have set to the sender channel is around 300 sec . After the expiry of this disconnect interval the sender channel is going to inactive state. I tried doing the following in s/390 side:

1. I set the trigger on the XMITQ( associated with the local definition of remoteq in NT) with trigger type as FIRST , with the process name as p1 and initiation queue as SYSTEM.CHANNEL.INITQ.

2. I defined the process P1 with the application type as CICS and application id as CKSG with the name of the sender channel in the USERDATA attribute.

3. The sender channel is in a inactive state.

Now when I put a message in the local definition of the remoteq , the sender channel is not getting started..
Could anybody help me in sorting out this problem?

We have made an entry in the channel definition file in CICS for this sender channel using CKMC transaction . But the problem is we don't know what connection name we have to give in the connection name attribute.

We are using MQseries along with CICS in our case. Do I need to set up anything in CICS side?

 

[emileke]

Do you have a channel initiator running?
You can set the disconnect interval to 0 if you do not want it to disconnect but I would not advise this.

 

[kevinf2349]

I am a little confused here. CICS has nothing to do with trigger a channel. Is sounds like you are confusing the issue a little. I assume that you want to do both things? (Start the channel automagically, and fire off a CICS transaction)?

First the channel....If I recall correctly, you don't need a PROCESS defining. If you leave it undefined the system will assume that it is a channel trigger.

In fact....here is the quote from the Application programming guide:

<quote>

For all MQSeries or WebSphere MQ Version 5 products, if you want to trigger the start of a channel, you do not need to define a process definition object. The transmission queue definition is used instead.

</quote>

The CICS queue is a totally different beast. The CICS trigger monitor transaction needs to be installed into the target CICS region on the destination queue manager's system. This trigger monitor watches the INITQ for a trigger message in the usual way. I am not sure if you are wanting to use the API or the CICS Bridge but the bottom line is that I would treat application triggering as a totally seperate thing than Channel triggering.

Kevin

 

[AlexAssis]

1) In transmition Queue definition:
define on INITQ parameter: SYSTEM.CHANNEL.INITQ
on PROCESS parameter: type a name of process. Sample:
PROCESS(START.CHANNEL1)

2) In process definition:
In appltype parameter: APLPTYPE(MVS)
In APPLICID parameter: APPLICID('CSQX START')
In Userdata parameter: USERDATA(<channel.name>)

 

[gunniya]

Thanks alex,

I tried out the way u told and it worked like a charm!!!

Raj