The channel that we were concerned about, at that time, is not a new channel. The Inactive status was due to Disconnect interval.
As with all MQ/FTE channels, they are a pair, 1 sender and 1 receiver channel. The activity level is solely based on the # of MQ/FTE (MFT) transfers being submitted to send to an agent on that target queue manager.
Do I know what the activity level was almost 5 months ago, no. I'm not sure if events are enabled for the queue manager, so no idea on what's in the SMF data from back then.
The whole thing behind my original post was specifically about why, even though there were records in the queue, that should have triggered the process to start the sender channel, it appeared that it wasn't.
I do NOT remember what we did to get it working, at that time. It could have been an issue with the channel connection between queue managers, or something else.
Had these questions come in, when I originally posted this topic, I might have been able to answer them better. We have not experienced any issue with the channel since then.
As such, I consider this topic to be closed.
------------------------------
Peter Vander Woude
------------------------------
Original Message:
Sent: 09/11/26 10:04 AM
From: bruce2359
Subject: Logging of Process definition executions on z/OS
"The CHSTATUS at the time was Inactive and the max channel is 200".
CHSTATUS Inactive most commonly indicates a new channel definition (DEF CHL), or a channel that has reached disconnect interval DISCINT.
Please tell us about the transaction rate of the MQPUTting application. Is the application frequently used? Seldom or rarely used? Is this channel continuously used? Or seldom used?
Do you have channel EVENTS enabled for the queue manager?
------------------------------
bruce2359
Consultant/trainer
CTTECH - Computer & Telecommunications Technology
West Coast, almost
000-000-0000
------------------------------
Original Message:
Sent: 09/10/26 02:19 PM
From: Peter Vander Woude
Subject: Logging of Process definition executions on z/OS
Being as it's just over 4 months from when I first posted, my memory on the exact situation that was happening and the final solution is a little hazy.
I will admit though, that my comments about the channel not restarting until 40 minutes later turned out to be a different channel. In all the craziness that day, I misread the message and channel, and the channel was unrelated to the MQ/FTE channels,
to answer the questions asked about triggering, all of the queues related to mq/fte are defined with trigger type of First, depth of 1. I don't see a trigger interval on the channel, when I view it through mq explorer.
The CHSTATUS at the time was Inactive and the max channel is 200, and we are well below that, on the queue manager in question. For that queue, we did switch away from the process to trigger the sending channel, to using the standard Trigger Data field in the queue definition. As mentioned before, all of these queues were defined long ago, probably before the usage of Trigger data was added to the z/OS queue manager.
There were no (i.e. zero) messages about any problems in the queue manager at the time, which is why my original post was asking if there was any logging of attempts to run Process entries.
I can't exactly recall what got found, at the time, however I think there were some issues, with other queue managers.. As it sits right now, we have not had the issue in several months.
Peter
------------------------------
Peter Vander Woude
------------------------------
Original Message:
Sent: 09/10/26 01:56 PM
From: Jason Andersen
Subject: Logging of Process definition executions on z/OS
Sounds like your trigger condition was messed up - FIRST, EVERY, DEPTH?. Don't forget with the DEPTH you need to reset that trigger condition yourself. Are there any messages on your INITQ? Queue Full? PUT/GET DISABLED? RACF error?
You might check some of your EVENT messages if you have those turned on. You will have event messages for channels. IF the channel truly was attempted to start, you'd see something in the JES2 LOG for that channel - the good and the bad.
If this is a critical process, might want to get your automation group involved. If your XMITq is filling with messages or it is at a depth that's unreasonable, you might have your monitoring package kick a message to the system log and or issue a START CHANNEL. If that CHANNEL doesn't go RUN with in 5 seconds have that AUTOMATION page someone out.
------------------------------
Jason Andersen
------------------------------