We run a CICS Configuration where we connect our TOR's trough APPC with our AOR's.
To install the connections we use the DFHZATDY autoinstall program.
Due to a production issue we want to set the MAXQTIME and QUEUELIMIT attributes to
protect our TOR's from going into a Max Task condition whenever an AOR is unable to process dynamically routed tasks.
The idea is to set MAXQTIME and QUEULIMIT so the task will be purged and not routed to the AOR when the queuelimit has been reached.
I have changed the CONNECTION model to include both attributes MAXQTIME and QUEUELIMIT but
when the connection has been autoinstalled this attributes are reverted back to the default value.
So it seems autoinstall ignores the attributes.
Has anyone experienced the same? The manuals are not specific in this case. The fact that i can define
an explizit connection with the attributes leds me to believe that this is an error in the autoinstall code?
Joined: 14 Jan 2008 Posts: 2504 Location: Atlanta, Georgia, USA
Have your VTAM personnel look at the MODEENT Macro for this ISC connection as there might be some "Embedded" value overriding these keywords.
Perhaps a VTAM GTF trace is in order? You'd then be able to view the bind characteristics and other important settings.
You should be working closely with VTAM and CICS System personnel.
If the TOR's and AOR's are within the same LPAR, you should be connecting TOR <---> AOR via XRF (similar to LU6.1, but more stable) instead of APPC/LU6.2, unless of course you're going from one VTAM to another.
Review the following link as well as Google both of the above keywords -
Thank you very much for your thoughts. I am one of 2 CICS System Engineers at this site. I have to admitt that i am quite new to CICS systems engineering. Our TOR's are connected cross system with our AOR's. So connecting trough MRO/XCF is not an option.
We are prototyping IPIC connections to connect our CICS regions. We are on CICS 4.2 but there are issues with IPIC connections. Sometimes they go into FREEING state and there is no way to Release the connection thereafter. We have to restart the CICS region which is not really an option (yet). But i think if we replace our APPC connections then we do it with IPIC.
If the MODEENT macro would override values this should also happen with explizit connections. So i'm not sure if that is really the case.
With explizit i mean connections i code in the CSD without autoinstalling them. If i do it that way the MAXQTIME and QUEUELIMIT attributes work just fine. So that is our workaround at the moment. We coded the APPC autoinstall in that way that if an autoinstall request comes in we use the CICS SPI to issue the CREATE CONNECTION and CREATE SESSION commands. Then we set the return code to tell the autoinstall exit that no model has been found. It's ugly but if works for now.
We use BMC Mainview for CICS so i am able to see all the connecition values.