Changed resource definition attributes

Table 6 shows changes to resource definition attributes.

Table 6. Changed resource definition attributes
Resource type Affected attributes Explanation
PROFILE RTIMOUT Now, in addition to specifying the terminal read time-out feature as in earlier releases, this also specifies the time-out value for IIOP request processor tasks that are waiting for method requests.

  1. The value of RTIMOUT is given as minutes and seconds (mmss) in the range 1--7000. The rounding of this value that was performed by earlier releases of CICS® no longer happens. CICS acts upon the RTIMOUT value exactly as it appears in the PROFILE definition. See 1 for more information.
  2. The READ TIMEOUT value on the transaction profile definition for MRO sessions is now observed by CICS. The field in the profile already exists. CICS honours it for ISC but used to ignore it for MRO. See 2 for more information.
PROGRAM
EXECKEY

JVMPROFILE

  • The EXECKEY attribute now applies to programs that run in a JVM. You can use the same JVM profile to invoke a JVM in either of the keys.
  • The JVM profiles that you specify using the JVMPROFILE attribute are now files in the HFS directory that is specified by the system initialization parameter JVMPROFILEDIR, and you need to specify the name using the same combination of upper and lower case characters that is present in the HFS file name.
TCPIPSERVICE
PORTNUMBER
TRANSACTION
The description of the PORTNUMBER attribute has been extended, with information regarding the use of well-known IIOP port numbers and port sharing within an MVS™™ image.

CIEP, for an ECI over TCP/IP TCPIPSERVICE definition, is added to the CICS transactions you can specify on the TRANSACTION attribute.

TRANSACTION SHUTDOWN The meaning of this parameter is changed. It now applies to ALL transactions whether the transaction is associated with a terminal or not. Therefore, SHUTDOWN(ENABLED) should be specified on all TRANSACTIONS that you want to run during shutdown. Alternatively, specify them on the XLT used at shutdown.
Notes:
  1. In earlier releases, CICS rounded this value up to an exact multiple of 16.78 seconds, for all communications methods. This rounding is now removed, CICS acts upon the RTIMOUT value exactly as it appears in the PROFILE definition. If you have set particular RTIMOUT values, to take account of the rounding up to a multiple of 16.78 seconds, in order to achieve a particular behavior in your CICS region, you may need to reconsider the values that you have set.
  2. In earlier Releases of CICS, read time-out is ignored for MRO sessions, tasks waiting on an MRO connection can hang indefinitely. If, for example, transactions in an AOR stall or deadlock for any reason the corresponding relay transactions in an MRO-connected TOR are left hanging. Eventually a problem in an AOR can cause the TOR to stall completely. Although you can prevent new transactions from being routed to, or queued for, the offending AOR, there has not been, until now, an easy way to purge every task that is in flight. This change to CICS enables the READ TIMEOUT value on the transaction profile definition for MRO sessions. The field in the profile already exists. CICS honours it for ISC but used to ignore it for MRO. CICS now checks this RTIMOUT value for MRO sessions. A new abend code is issued if the RTIMOUT value is exceeded for MRO sessions. By enabling the READ TIMEOUT value on the transaction profile definition for MRO sessions, a cause of intersystem queuing (sometimes referred to as "sympathy sickness") is eliminated. The situations which may benefit from this change include some which, because they result from stalls or deadlocks elsewhere, are unlikely to resolve themselves unaided.
[[ Contents Previous Page | Next Page Index ]]