-----------------------<snip>-------------------
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?
----------------------<unsnip>-----------------
John, on the CBT site there's a program named COMMAND that will issue
commands from the SYSIN file, or replies to WTOR's. It allows for a
special command called "DELAY", so you can space out the timing of the
commands to be issued. Pull it down, look it over and assemble it.
(I wish it had the capability to issue a command after the appearance of
a specific message.)
Between COMMAND and the NETINIT program, we almost completely automated
our start-up and shutdown processes at Clearing; all the operator had to
do was start the LOAD process and supply the "$s" command for JES2.
Shutdown was done by starting a SHUTDOWN proc that did everything but
close down JES2.
----------------------------------------------------------------------
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
