JC asks > An application group is doing a "stress test" against a CICS region, > using "batched" instream commands via an IEFBR14 job to invoke a user > transaction. Some of the MODIFY commands are being rejected with > message IEE342I MODIFY REJECTED-TASK BUSY. The part of the > explanation in M&C that appears applicable is: > > "The task associated with the command had not finished processing a > previous command." > > Question: Which is the "task associated with the command" in this > context: The user transaction invoked via the command? The CICS > command processor? Some other (MVS) task?
Dunno about which specific CICS task, but the underlying mechanism is pretty straight forward. Commands arrive and get queued. The length of that queue is set by the CIBCTR keyword on a QEDIT macro - usually the one that dequeues the start command. If more commands arrive than the limit set by that QEDIT, the system rejects any new command with "task busy". When you're done with processing any command (whatever that means in any given environment) somebody has to issue the QEDIT macro again to delete that command and "see" the next one. If the queued commands are not deleted, or not deleted fast enough, sooner or later you're going to get an IEE342I. CC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
