MQ

IBM MQ

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Logging of Process definition executions on z/OS

  • 1.  Logging of Process definition executions on z/OS

    Posted 04/24/26 11:45 AM

    In some of our queue managers, on z/OS, the initiation queue for a sender channel, is defined to kick off a process definition, which executes the CSQX START command for the sender channel.  I believe this method for starting the sender was setup a long time ago, yet it's not what I am used to.  The queue is setup to trigger on the first message with trigger depth of 1.

    We had a situation where a sender channel disconnected, as per the disconnect interval defined for it, and even though some MQ/FTE jobs ran that should have caused it to start, the sender channel did not start up, until almost 40 minutes later, thus causing the FTE jobs to fail, as we use an ant script to run an fteping of the destination agent, to avoid the job just hanging, if there's problem in the mq/fte environment.  If the fteping fails, the ant script will stop the execution before submitting the actual file transfers.

    The lpar was very busy that the time, that the channel should have started, so that could come into play.  The queue manager and channel initiator are defined to run with the highest priority, so as to not starve it from the cpu.

    At the moment, we have updated the queue for that sender channel, to not kick off the process definition, but to directly start the sender channel, as is done on our Open systems queue managers.

    My question is this.  Where is there any logging of the process executions, on z/OS, so we could see why it either failed, or was delayed so much?  Or it is just left to be a guessing game.  

    Thanks

    Peter



    ------------------------------
    Peter Vander Woude
    ------------------------------


  • 2.  RE: Logging of Process definition executions on z/OS

    Posted 04/25/26 07:25 PM

    Hi Peter,

    You are correct that a long long time ago, to trigger start a channel on MVS, you needed to refer to a PROCESS object in the transmission queue definition and that PROCESS object contained the command CSQX START to indicate that it was a channel that needed to be started. However, this was changed to allow channels to be triggered simply by having the channel name in the TRIGDATA just as on the distributed platforms. Both methods are valid, and both methods cause a trigger message to be placed on the SYSTEM.CHANNEL.INITQ which your CHIN task will pick up and act upon. 

    The fact that the channel eventually started (you say after 40 minutes) tells me that the configuration in the trigger message was not in error and that therefore there must have been some delay. The main question is whether there was a delay in the CHIN task picking up the trigger message or whether there was a delay in the channel actually getting into RUNNING status. Given your statement about priority of the CHIN and MSTR jobs, the latter seems more likely.

    You should review the CHIN joblog for this time period to look for channel messages related to this particular channel. Did it, for example, not manage to get started immediately because of some network issue, or perhaps because too many other channels were already running and it had to wait until one ended before it could start? There are a number of possibilities, all of which are covered by channel error messages written to the CHIN joblog.

    I suggest you review that and if you need more help, paste in here the portion of the CHIN joblog that covers the time period in question so we can help you interpret the error messages that you see.

    Cheers,
    Morag



    ------------------------------
    Morag Hughson
    MQ Technical Education Specialist
    MQGem Software Limited
    Website: https://www.mqgem.com
    ------------------------------



  • 3.  RE: Logging of Process definition executions on z/OS

    Posted 04/27/26 09:42 AM

    Morag,

    Thanks for explaining that the process method was from way back.  My experience using MQ only goes back a few years, to around v7 timeframe, in my previous shop, but we weren't running sender/receiver channels there.  

    As far as messages, there are no abnormal messages in the CHIN messages saying that there were any errors or delays.  For the most recent occurrence, I was able to go back using RMF to see how busy the lpar was, and I do believe it was running at least 95% busy, at the time.  Thought I'm not sure it was that busy the entire time, as I didn't follow through all the intervals.

    At present, we have changed the queue for this sender channel to use, what is now, normal triggering of the channel.  We have a lot of other Process definitions to work through and I will let our main MQ guy know what you were able to let me know.

    Thanks,

    Peter



    ------------------------------
    Peter Vander Woude
    ------------------------------



  • 4.  RE: Logging of Process definition executions on z/OS

    Posted 04/27/26 10:06 AM

    Morag,

    As a follow-up, I looked in all of the sysout in both the CHIN and MSTR started tasks, I saw no CSQX command related output.

    One item I did notice, that around the time that the channel started, the queue manager MSTR address space shows that a checkpoint was started for all buffer pools.  Though the checkpoint message was 9 seconds after the channel started, so it probably is not directly related, just a coincidence.

    BTW, in reference to any SMF records, what audit/trace levels would need to be active for this?  Though I would expect that this might increase the SMF records, as I know that products like Omegamon for MQ, uses it's own queues for monitoring and will issue CSQX commands, via queues.

    I do have the latest version of the MP1B supportpac, but not sure where in there I might find anything that would relate to the process execution.

    Peter



    ------------------------------
    Peter Vander Woude
    ------------------------------



  • 5.  RE: Logging of Process definition executions on z/OS

    Posted 09/09/26 09:07 AM

    Hi Peter,

    You might also want to review the trigger intervall as this affects triggering. I usually set it at 5 mins (300000)

    Hope it helps



    ------------------------------
    Francois Brandelik
    ------------------------------



  • 6.  RE: Logging of Process definition executions on z/OS

    Posted 09/09/26 10:34 AM
    Edited by bruce2359 09/09/26 02:58 PM

    Missing from usual channel problem determination:

    What was the CHSTATUS of the sender channel?  What was the CHSTATUS at the receiver end of the channel?  

    What is MAX CHANNELS value at both channel ends?

    CHIN syslog should have logged the attempts to (re)start channel, and failures to do so - based on short and long retry interval values.  



    ------------------------------
    bruce2359
    Consultant/trainer
    CTTECH - Computer & Telecommunications Technology
    West Coast, almost
    000-000-0000
    ------------------------------



  • 7.  RE: Logging of Process definition executions on z/OS

    Posted 09/10/26 01:56 PM

    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
    ------------------------------



  • 8.  RE: Logging of Process definition executions on z/OS

    Posted 09/10/26 02:20 PM
    Edited by Peter Vander Woude 09/10/26 02:20 PM

    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
    ------------------------------



  • 9.  RE: Logging of Process definition executions on z/OS

    Posted 09/10/26 02:54 PM

    Hi Peter,

    The trigger interval (trigint) is at the queue manager level. Not at the channel level.



    ------------------------------
    Francois Brandelik
    ------------------------------



  • 10.  RE: Logging of Process definition executions on z/OS

    Posted 09/10/26 03:36 PM

    trigint is defined as 999999999 (it's taking the default).

    Peter



    ------------------------------
    Peter Vander Woude
    ------------------------------



  • 11.  RE: Logging of Process definition executions on z/OS

    Posted 09/11/26 10:05 AM

    "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
    ------------------------------



  • 12.  RE: Logging of Process definition executions on z/OS

    Posted 09/11/26 10:16 AM

    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
    ------------------------------