1. Whats New in OTMA, IMS Connect, and WebSphere MQ IMS User
GroupSteve [email protected] 2012 IBM Corporation
2. IMS Regional User GroupDisclaimer Copyright IBM Corporation
[current year]. All rights reserved. U.S. Government Users
Restricted Rights - Use, duplication or disclosure restricted by
GSA ADP Schedule Contract with IBM Corp. THE INFORMATION CONTAINED
IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.
WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF
THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED AS
IS WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION,
THIS INFORMATION IS BASED ON IBMS CURRENT PRODUCT PLANS AND
STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM
SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF,
OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER
DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED
TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR
REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR
ALTERING THE TERMS AND CONDITIONS OF ANY AGREEMENT OR LICENSE
GOVERNING THE USE OF IBM PRODUCTS AND/OR SOFTWARE.IBM, the IBM
logo, ibm.com, and IMS are trademarks or registered trademarks of
International BusinessMachines Corporation in the United States,
other countries, or both. If these and other IBM trademarked
termsare marked on their first occurrence in this information with
a trademark symbol ( or ), these symbolsindicate U.S. registered or
common law trademarks owned by IBM at the time this information was
published.Such trademarks may also be registered or common law
trademarks in other countries. A current list of IBMtrademarks is
available on the Web at Copyright and trademark information
atwww.ibm.com/legal/copytrade.shtml Whats New in OTMA, IMS Connect,
and WebSphere MQ 2
3. IMS Regional User GroupAgenda Introduction IMS 10+ OTMA and
IMS Connect OTMA IMS Connect IMS 11 OTMA and IMS Connect OTMA IMS
Connect IMS 11+ OTMA IMS 12 IMS 13 IMS Connect Extensions IMS
Enterprise Suite Whats New in OTMA, IMS Connect, and WebSphere MQ
3
4. IMS Regional User GroupIntroduction There have been MANY
enhancements in OTMA and IMS Connect Some of these were added in
IMS 10 via maintenance (10+) Some of these were added in IMS 11
Some of these were added in IMS 11 via maintenance (11+) Some of
these were added in IMS 12 Some have been announced for IMS 13 Some
of the these were enhancements to OTMA which also had enhancements
in IMS Connect or WebSphere MQ to take advantage of the OTMA
enhancements This presentation will cover all of these enhancements
Whats New in OTMA, IMS Connect, and WebSphere MQ 4
5. IMS Regional User GroupIMS 10 OTMA Reminder The following
were OTMA enhancements for IMS 10 Support /LOCK & /UNLOCK
commands via OTMA Routing descriptors for IMS Connect and NONOTMA
Resume TPIPE security Message flood control CM1 ACK timeout
Automatic TPIPE cleanup TMEMBER level security /DISPLAY
enhancements Supermember for Resume TPIPE Reroute/Purge of
undeliverable IOPCB output OTMA=M and /STA OTMA NOCHECK Whats New
in OTMA, IMS Connect, and WebSphere MQ 5
6. IMS Regional User GroupIMS 10 IMS Connect Reminder The
following were IMS Connect enhancements for IMS 10 Specify ACEE
aging value to OTMA Change password RACF mixed case password
Support OTMA message flood Support OTMA CM1 ACK timeout Resume
TPIPE alternate Clientid Resume TPIPE Port Affinity XML Adapter
Whats New in OTMA, IMS Connect, and WebSphere MQ 6
7. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout IMS supports synchronous callout from an IMS
application using OTMA Invoked with a new IMS call ICAL Application
will issue the call and wait for a reply First support is for IMS
Connect Implemented by OTMA APARs PK70078, PK71135, and PK73224
Also PK75209 (IMS10) and PK85023 IMS 11) for issuing ICAL from IMS
Java programs Whats New in OTMA, IMS Connect, and WebSphere MQ
7
8. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout The OTMA Client will do a Resume TPIPE
specifying that it wants synchronous callout messages OTMA sends
the synchronous callout request to the OTMA Client when it is
available The OTMA Client must send an ACK (or NAK) for the request
message The OTMA Client will send the reply via a special Send-Only
message The OTMA Client is responsible for maintaining a
correlation token Whats New in OTMA, IMS Connect, and WebSphere MQ
8
9. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout IMS Connect will support OTMA synchronous
callout via APARs PK70330 and PK74168 IMS TM Resource Adapter
support is APAR PK75460 IMS Connect Extensions support is APAR
PK74985 DFSUTR20 support is PM03084 There are several other APARs
PM30898 is very important The IMS Connect Client will do a Resume
TPIPE specifying that it wants synchronous callout messages The IMS
Connect Client will send the reply via a Send-Only message Whats
New in OTMA, IMS Connect, and WebSphere MQ 9
10. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout The IMS Connect Client is responsible for
maintaining the correlation token WAS/IMS TM Resource Adapter IMS
SOAP Gateway Roll-Your-Own (RYO) Client APARs PM20541 (IMS 10) and
PM20543 (IMS 11) have IMS Connect notify OTMA if there is an error
in the XML translation instead of just discarding the message OTMA
will notify the ICAL transaction immediately instead of waiting for
the timeout Whats New in OTMA, IMS Connect, and WebSphere MQ
10
11. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout The synchronous callout design is provided for
IMS TM users It does not provide support for BMP or JBP
applications running in a DBCTL environment OTMA Descriptors are
required to define the target destination Supermember is supported
for availability and failover Only the AIBTDLI call interface is
supported Supports messages larger than 32K without segmentation
The target of the synchronous callout could be any IMS Connect
Client WAS/IMS TM Resource adapter IMS SOAP Gateway Roll-Your-Own
(RYO) client The reply can be returned via a different IMS Connect
Whats New in OTMA, IMS Connect, and WebSphere MQ 11
12. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout The following will not be supported in the
first phase of the synchronous callout support Shared Queues with
FE and BE are different systems Two phase commit (distributed sync
point) IMS application will not be able to specify a password for
authenticating the external server on a per request basis Whats New
in OTMA, IMS Connect, and WebSphere MQ 12
13. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
WebSphere IMS Application Server EJB / IMS TM MDB Resource Adapter
IMS Application 1 OTMA Descriptor 1 IMS Connect IMS Roll-your-own
Connect IMS Application 2 Application OTMA Descriptor 2 OTMA IMS
Application 3 Descriptor 3 IMSWeb Service SOAP Provider Gateway
Send flow Receive flow Whats New in OTMA, IMS Connect, and
WebSphere MQ 13
14. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout The first thing to do is define and setup OTMA
Descriptors for each synchronous callout destination Use different
TPIPEs for asynchronous output messages and synchronous callout
messages Use different TPIPEs for synchronous callout request
messages for each client IMS TM Resource Adapter clients IMS SOAP
Gateway clients RYO application clients Whats New in OTMA, IMS
Connect, and WebSphere MQ 14
15. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout Use D descriptor type in DFSYDTx D destname
keywords destname is the destination name in the AIB Keywords are
TYPE=IMSCON (only supported by ICON at this time) TMEMBER=name
TPIPE=name SMEM=YES|NO ADAPTER=adapname CONVERTR=convname
SYNTIMER=timeout Whats New in OTMA, IMS Connect, and WebSphere MQ
15
16. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout The IMS application uses the AIBTDLI call for
the synchronous request CALL AIBTDLI USING ICAL, AIB, REQ-AREA,
RESP-AREA. ICAL is new call AIB is an AIB control block Synchronous
callout is only supported by the AIB interface REQ-AREA is the
Request data area for synchronous callout RESP-AREA is the Response
data area for returned data Whats New in OTMA, IMS Connect, and
WebSphere MQ 16
17. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout AIB AIBSFUNC = SENDRECV AIBRSNM1 = 8 byte OTMA
Descriptor name AIBRSFLD = Timeout value AIBOALEN = Request area
length Input parameter: 4 byte field containing the length of the
request area Output parameter: Actual length of the response
message Updated by IMS only when partial data is returned AIB
return code x100, AIB reason code x00C AIBOAUSE = Response area
length Input parameter: 4 byte field contains the length of the
response area Output parameter: Length of the response message
placed in the response area When partial data is returned because
the response area is not large enough, AIBOAUSE contains the length
of data returned in the response area and AIBOALEN contains the
actual length of the response message Whats New in OTMA, IMS
Connect, and WebSphere MQ 17
18. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout Timeout If both the AIB and the Descriptor have
a timeout value the lower of the two values will be used If only
one has a timeout value that one will be used If neither has a
timeout value the default value of 10 seconds will be used The
valid range is between 0 and 999999 in hundredths of a second The
maximum is about 2.7 hours Whats New in OTMA, IMS Connect, and
WebSphere MQ 18
19. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
IAPMDI27 JOHN DOE . RYO Application IMS Connect IMS Resume TPIPE
IMS Application TPIPE 1 TPIPE1 TPIPE1 ICAL SENDRECV OTMDEST1 JOHN
DOE Request 4 3 2 JOHN DOE 5 ACK Response 9 6 7 8 12345678 12345678
Whats New in OTMA, IMS Connect, and WebSphere MQ 19
20. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout1. IMS Connect Client issues Resume TPIPE2. The
IMS application issues the synchronous request using the ICAL
call3. OTMA breaks the message into 32K segments4. IMS Connect
combines the data and sends it to the IMS Connect Client including
the Correlation Token5. The IMS Connect Client must ACK or NAK the
synchronous output message6. The IMS Connect Client sends the
synchronous response message as a send-only message7. IMS Connect
breaks the message into 32K pieces to send to OTMA via XCF8. OTMA
combines all of the data and returns it to the IMS application in
the Response Area9. The IMS application processes the synchronous
response Whats New in OTMA, IMS Connect, and WebSphere MQ 20
21. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout enhancements IMS 10 PM09695, PM09696, and
PM14872 IMS 11 PM12142 and PM12172 OTMA will send a new NAK (sense
code x2B) when a late or invalid ACK is received for a callout
message If the reply message for sync callout is received BEFORE
the ACK for the output message OTMA will wait for the ACK Can be
caused by XCF race condition TPIPE cleanup will now clean-up unused
ICAL TPIPEs after 3 checkpoints Label NO_RSP changed to NO_COT for
/DIS TMEMBER TPIPE SYNC NO_COT = number of Synchronous Callout
Messages Whats New in OTMA, IMS Connect, and WebSphere MQ 21
22. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Synchronous Callout APARs PM20292 (IMS 10) and PM20293 (IMS 11) New
ICAL AIB AIBERRXT for why ICAL failed Extended reason codes in
addition to AIB return/reason codes New DFS4688E message for an
ICAL internal processing error ICAL times out with an AIBERRXT
extended reason code X67D0 log record written to show error
information IMS 12 PM39569 Support Send-Only with ACK for a
Synchronous Callout response Whats New in OTMA, IMS Connect, and
WebSphere MQ 22
23. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Asynchronous Callout When OTMA asynchronous output was sent via the
OTMA D type descriptors, OTMA was not setting the Port to ICONNECT
If IMS Connect was using PORTAFF=Y then IMS Connect would not find
the IMS Connect Client to receive the message Fixed with PM35619
(IMS 10), PM39450 (IMS 11), and PM39451 (IMS 12) Whats New in OTMA,
IMS Connect, and WebSphere MQ 23
24. IMS Regional User GroupIMS 10+ OTMA and IMS Connect Queued
Resume TPIPE Requests If a Resume TPIPE was sent in for a TPIPE
that was already processing a Resume TPIPE the second Resume TPIPE
would be ignored With PK80756 OTMA will now queue the Resume TPIPE
It will receive messages if the first Resume TPIPE is cancelled
This enhancement is for availability It allows another OTMA Resume
TPIPE client to immediately receive asynchronous output or sync
callout output if the current Resume TPIPE client fails Whats New
in OTMA, IMS Connect, and WebSphere MQ 24
25. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Transaction Expiration Distributed applications may timeout
transactions Not under IMS control IMS still processes the
transaction No one is interested in the output This uses
unnecessary resources Network resources CPU / storage / IO
Dependent region occupancy Whats New in OTMA, IMS Connect, and
WebSphere MQ 25
26. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Transaction Expiration Input message expiration = input message
timeout Allows OTMA input messages to expire and be deleted prior
to processing OTMA input messages can specify a timeout value in
the OTMA header in one of two ways An expiration STCK time Used by
IMS Connect An elapsed time value Used by Websphere MQ (7.0.1 and
7.1) Implemented via PK74017 (IMS 10) and PK74024 (IMS Connect 10)
Implemented via IMS TM Resource Adapter with PM01727 (IMS 10) and
PM01822 (IMS 11) A new transExpiration property is added to the
interactionSpec class Whats New in OTMA, IMS Connect, and WebSphere
MQ 26
27. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Transaction Expiration Transaction level input message timeout for
OTMA and non- OTMA messages was introduced in IMS 11 Specified on:
TRANSACT macro EXPRTIME parameter DFSINSX0 - Destination Creation
User Exit CREATE/UPDATE TRAN/TRANDESC DRD commands Whats New in
OTMA, IMS Connect, and WebSphere MQ 27
28. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Transaction Expiration IMS Connect Clients using sample exits set
x01 on in flag IRM_F1 IRM_F1_TRNEXP RYO exits will have their own
method IMS Connect User Message Exit sets flag OMHDRXP1 (x01) on in
flag OMHDRIST IMS Connect calculates the transaction expiry time
based on the OTMA timeout value for the message You can not
explicitly specify the expiration time IMS Connect passes a STCK
Expiry time to OTMA Whats New in OTMA, IMS Connect, and WebSphere
MQ 28
29. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Transaction Expiration Input message expiration is checked three
times When the input message is first received OTMA only Expiry NAK
x34 When the input message is enqueued to the transaction OTMA only
Expiry NAK x34 GU IOPCB OTMA and non-OTMA (IMS 11) Expiry
pseudoabend U0243 & DFS555I/DFS2224I DFS3688I An x67D0 log
record is written for all expirations Whats New in OTMA, IMS
Connect, and WebSphere MQ 29
30. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Transaction Expiration APARs PM05985 (IMS 10) and PM05984 (IMS 11)
will add new support for transaction expiration Dump for ABENDU0243
at GU timeout will be optional TODUMP=YES/NO in OTMA descriptor
Send message DFS3688I instead of DFS555I/DFS2224I DFS3688I
TRANSACTION xxxxxxxx EXPIRED: ELAPSE=yyyyyyyy TPIPE=zzzzzzzz
TMEMBER=aaaaaaaaaaaaaaaa Option to return input message instead of
DFS3688I The last two items help MQSeries to support Transaction
Expiration Whats New in OTMA, IMS Connect, and WebSphere MQ 30
31. IMS Regional User GroupIMS 10+ OTMA and IMS Connect Resume
TPIPE No Message Notification TMAMCRHQ_NOAUTO x00 OTMA will send
all the messages that are on the Asynchronous output queue one at a
time and then will stop when the queue is empty It will take
another Resume TPIPE to get more messages If there are no messages
when the Resume TPIPE is issued nothing happens The Resume TPIPE is
ignored there is no reply to the OTMA Client that there are no
messages but this is now fixed PK80756 will send a protocol command
indicating there are no more messages IMS Connect (PK80758) will
issue an immediate timeout to the IMS Connect Client Whats New in
OTMA, IMS Connect, and WebSphere MQ 31
32. IMS Regional User GroupIMS 10+ OTMA and IMS Connect Resume
TPIPE No Message Notification TMAMCRHQ_ONE x01 OTMA will send one
message from the Asynchronous output queue and then will stop It
will take another Resume TPIPE to get more messages If there are no
messages when the Resume TPIPE is issued nothing happens The Resume
TPIPE is ignored there is no reply to the OTMA Client that there
are no messages but this is now fixed PK80756 will send a protocol
command indicating there are no more messages IMS Connect (PK80758)
will issue an immediate timeout to the IMS Connect Client Whats New
in OTMA, IMS Connect, and WebSphere MQ 32
33. IMS Regional User GroupIMS 10+ OTMA and IMS Connect Cancel
Resume TPIPE OTMA added a new command to allow an OTMA client to
cancel a Resume TPIPE (PK80756) Allows another queued Resume TPIPE
to take over receiving asynchronous output messages for this TPIPE
Including Synchronous Callout messages IMS Connect (PK80758) will
send in this command when an IMS Connect Client waiting on a Resume
TPIPE times out in IMS Connect or when ICON notices that a Client
has disconnected This also allows OTMA to clean up the TPIPE after
3 checkpoints if there is no Auto or Auto One Resume TPIPE waiting
Whats New in OTMA, IMS Connect, and WebSphere MQ 33
34. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Resource Monitoring OTMA currently provides flood protection when
too many YTIB (unprocessed input message) control blocks are
created for an OTMA Client Message DFS1988W is issued as the TIB
limit is approached Message DFS1989E is issued when the TIB limit
is reached Input messages are rejected from that Client until the
flood is relieved Message DFS0767I is issued when the flood
condition is relieved There were requirements for the original
implementation The DFS messages were not written to the MTO so they
could not be processed by automation The OTMA clients were not
informed Whats New in OTMA, IMS Connect, and WebSphere MQ 34
35. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Resource Monitoring APAR PK49317 (IMS 10) routes these DFS messages
to the IMS MTO in addition to the current WTO This APAR also adds a
new message which can be monitored by automation DFS2386I OTMA IS
CONNECTING TO THE MEMBER xxxxxxxx Whats New in OTMA, IMS Connect,
and WebSphere MQ 35
36. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Resource Monitoring APARs PK70458 (OTMA 10) and PK70960 (ICON 10)
introduce the start of OTMA Degraded System Monitoring PK73670 is
for IMS Connect Extensions support OTMA sends x3C protocol messages
to OTMA clients At Client Bid with initial status Immediately when
status changes Stopped, Started, Flood Warn, Flood, Flood Relieved
Heartbeat once every 60 seconds IMS Connect externalizes the OTMA
status Expanded XIBDS table for ICON User Message Exits Event 45
issued when XIBDS status updated Not for heartbeat only the XIBDS
timestamp is updated Whats New in OTMA, IMS Connect, and WebSphere
MQ 36
37. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Resource Monitoring Original HWSXIBDS HWSXIBDS DSECT Exit Interface
Block Data Store entry XIBDS_NAME DS CL8 Data store name
XIBDS_STATUS DS X Data store status XIBDS_INACTIVE EQU X00 Data
store not active in ICON * OPENDS command is required XIBDS_ACTIVE
EQU X01 Data store active in ICON * And IMS is active in XCF group
XIBDS_DISC EQU X02 Data store disconnected * No OPENDS command is
required XIBDS_FLAG DS X Data store entry flags XIBDS_LAST_ENTRY
EQU X80 Last entry in list DS XL2 Reserved XIBDS_USER DS XL4 User
field Whats New in OTMA, IMS Connect, and WebSphere MQ 37
38. IMS Regional User GroupIMS 10+ OTMA and IMS Connect
Resource Monitoring Added to HWSXIBDS Can be used for routing
decisions * OTMA Status Section Follows @PK70960 XIBDS_ST_STATUS DS
H Overall Status Code 3, 2, or 1 @PK70960 * 3 - Available for work
@PK70960 * 2 - Warning, partly degraded @PK70960 * 1 - Severe, no
work possible @PK70960 * 0 - N/A no status available @PK70960
XIBDS_ST_SVRSTT DS 0XL4 Unavailable resource info @PK70960
XIBDS_ST_SVRFLG1 DS X Group 1 unavail resources @PK70960
XIBDS_ST_SVRFLG2 DS X Group 2 unavail resources @PK70960
XIBDS_ST_SVRFLG3 DS X Group 3 unavail resources @PK70960
XIBDS_ST_SVRFLG4 DS X Group 4 unavail resources @PK70960
XIBDS_ST_S4FLOOD EQU X01 Member reaches 100% flood @PK70960
XIBDS_ST_WRNSTT DS 0XL4 Degraded resource info @PK70960
XIBDS_ST_WRNFLG1 DS X Group 1 degraded resources @PK70960
XIBDS_ST_W1FLOOD EQU X80 Global flood warning @PK70960
XIBDS_ST_WRNFLG2 DS X Group 2 degraded resources @PK70960
XIBDS_ST_WRNFLG3 DS X Group 3 degraded resources @PK70960
XIBDS_ST_WRNFLG4 DS X Group 4 degraded resources @PK70960
XIBDS_ST_W4FLOOD EQU X01 Member 80%+ flood @PK70960 XIBDS_ST_UTC DS
CL12 UTC time for this status @PK70960 XIBDS_ST_LEN EQU
*-XIBDS_ST_STATUS Length of OTMA Status @PK70960 * @PK70960
XIBDS_LEN EQU *-HWSXIBDS XIB data store entry length Whats New in
OTMA, IMS Connect, and WebSphere MQ 38
39. IMS Regional User GroupIMS 10+ OTMA and Websphere MQ
Message Delivery Options Expiry A message can expire in MQSeries on
the IMS Bridge Queue before being sent to IMS The MQ application
that MQPUT the message is notified if one of the following
MQMD_REPORT options is set MQRO_EXCEPTION (Just the Expiration
report) MQRO_EXCEPTION_WITH_DATA (First 100 bytes of the message)
MQRO_EXCEPTION_WITH_FULL_DATA (All of the message) Whats New in
OTMA, IMS Connect, and WebSphere MQ 39
40. IMS Regional User GroupIMS 10+ OTMA and Websphere MQ
Message Delivery Options Expiry MQSeries 7.0.1 supports IMS
Transaction Expiration MQSeries passes the remaining Expiry time to
IMS as an IMS Transaction Expiration time This is rounded up to
whole seconds This requires ORing the MQ Service Parameter with
x00000000000001 to activate this feature ZPARM CSQ6SYSP
SERVICE=0000000001 + any other bits being used COMMAND SYSTEM
SERVICE(0000000001) + any other bits being used Whats New in OTMA,
IMS Connect, and WebSphere MQ 40
41. IMS Regional User GroupIMS 10+ OTMA and Websphere MQ
Message Delivery Options Expiry MQSeries 7.0.1 supports IMS
Transaction Expiration If the transaction expires in OTMA before
being placed on the IMS message queue it is NAKed by IMS (NACK_FOR
TRANS_EXPIRED, x0034) MQSeries treats this as if the message had
expired before being sent to IMS MQMD_REPORT options are honored
Whats New in OTMA, IMS Connect, and WebSphere MQ 41
42. IMS Regional User GroupIMS 10+ OTMA and Websphere MQ
Message Delivery Options Expiry MQSeries 7.0.1 supports IMS
Transaction Expiration If the transaction expires at the GU to the
IOPCB IMS returns message DFS3688I to MQSeries The DFS3688I message
is returned to the Reply_To Queue The MQMD_REPORT options are NOT
honored Whats New in OTMA, IMS Connect, and WebSphere MQ 42
43. IMS Regional User GroupIMS 10+ OTMA and Websphere MQ
Message Delivery Options Expiry MQSeries 7.1.0 enhances the support
for IMS Transaction Expiration Requires IMS APAR PM05984 If the
transaction expires at the GU to the IOPCB OTMA returns the
original input message to MQSeries instead of the DFS3688I message
The MQMD_REPORT options are honored This enhanced functionality was
retrofit to MQSeries 7.0.1 via APAR PM47795 Whats New in OTMA, IMS
Connect, and WebSphere MQ 43
44. IMS Regional User GroupIMS 10+ OTMA and Websphere MQ
Message Delivery Options Expiry The Reply message can also Expire
MQIIH_FLAGS has value MQIIH_PASS_EXPIRATION MQSeries will pass the
REMAINING expiry time in the OTMA header The reply on the reply-to
queue will start the Expiry process with that remaining time Any
time in IMS is NOT counted Whats New in OTMA, IMS Connect, and
WebSphere MQ 44
45. IMS Regional User GroupIMS 10+ OTMA and Websphere MQ
WebSphere MQ 7.1 Dead Letter Queue reason code for NAKed OTMA
message with x001A sense code Reason code was 326 Reason code is
now 600 + the OTMA NAK reason code e.g. OTMA NAK with Sense x001A
and Reason x0019 gives Dead Letter Queue reason code of 625 Whats
New in OTMA, IMS Connect, and WebSphere MQ 45
46. IMS Regional User GroupIMS 10+ OTMA Resource Monitoring
OTMA flood protection limits the number of YTIB control blocks
Having too many TPIPEs can also build up OTMA storage APAR PK79048
allows the specification of a maximum number of TPIPEs per OTMA
Client (TMEMBER) and for all of OTMA Specified with the MAXTP
parameter on the M (Member) control card in DFSYDTx There is no
command to set this value Values can be from 200 to 99999 The
maximum limit for all of OTMA is the highest Member limit Whats New
in OTMA, IMS Connect, and WebSphere MQ 46
47. IMS Regional User GroupIMS 10+ OTMA Resource Monitoring
APAR PK79048 allows the specification of a maximum number of TPIPEs
per OTMA Client (TMEMBER) and for all of OTMA Error messages are
issued when limits are reached/relieved DFS4382W at 80% for TMEMBER
limit DFS4383E when TMEMBER limit reached DFS4384I when TMEMBER
flood relieved ( -QRY--- | .-,-------------. | | V | |
-TMEMBER(---+-tmemname--+-+-)- -tmemname*-
.-TPIPE(*)--------------------.>--+-----------------------------+------------------------------>
| .-,--------------. | | V | | -TPIPE(---+-tpipename--+-+-)-
-tpipename*->--+-------------------------------+---------------------------->
| .-,-------------. | | V | | -TRANCODE(---+-tranname--+-+-)-
-tranname*->--+-------------------------+--+---------------------------+--->
| .-,----------. | | .-,-----------. | | V | | | V | |
-LTERM(---+-lterm--+-+-)- -USERID(---+-userid--+-+-)- -lterm*-
-userid*- Whats New in OTMA, IMS Connect, and WebSphere MQ 86
87. IMS Regional User GroupIMS 11 OTMA Type 2 Query Command -
continued>--+-----------------------------+------------------------------>
| .-,------------. | | V | | -GRPNAME(---+-grpname--+-+-)-
-grpname*->--+-----------------------------+--+----------------------+---->
| .-,------------. | | .-,-----. | | V | | | V | |
-MODNAME(---+-modname--+-+-)- -CMTMODE(---+-0-+-+-)- -modname*-
-1->--+----------------------+--+---------------+------------------>
| .-,-----. | -MSGAGE(nnnnn)- | V | | -SYNCLVL(---+-0-+-+-)- +-1-+
-2- Whats New in OTMA, IMS Connect, and WebSphere MQ 87
88. IMS Regional User GroupIMS 11 OTMA Type 2 Query Command -
continued
.-SHOW(MSGCNT)---------------.>--+----------------------------+------------------------------><
| .-,--------------. | | V | | -SHOW(---+-AGINGVAL---+-+-)-
+-ALL--------+ +-CMTMODE----+ +-CTTKN------+ +-GRPNAME----+
+-LTERM------+ +-MODNAME----+ +-MSGAGE-----+ +-MSGTKN-----+
+-SYNCLVL----+ +-TIMEOUTVAL-+ +-TRANCODE---+ +-TYPE-------+
-USERID----- Whats New in OTMA, IMS Connect, and WebSphere MQ
88
89. IMS Regional User GroupIMS 11 OTMA Type 2 Query Command
Example:QUERY OTMATI MSGAGE(3) SHOW(ALL)MbrName Tmember TpipeName
CC CText MsgAge UseridIMSA HWS1 APPLA 0 Completed Successfully 5
USER04IMSA HWS1 APPLA 0 Completed Successfully 6
USER88.........IMSB HWS2 APPLB 0 Completed Successfully 8 SVL01IMSB
HWS2 APPLB 0 Completed Successfully 4 SVL08 Whats New in OTMA, IMS
Connect, and WebSphere MQ 89
90. IMS Regional User GroupIMS 11 OTMA Flood Control for Total
TIBs /STA TMEMBER ALL INPUT #### Command enhancement to set the
global message flood warning level for ALL the OTMA members The new
ALL parameter provides a global value that OTMA additionally
monitors for all members combined Default is 8000 Whats New in
OTMA, IMS Connect, and WebSphere MQ 90
91. IMS Regional User GroupIMS 11 OTMA Flood Control for Total
TIBs When the global value is reached WTO and MTO messages are
issued DFS4388W when global maximum is reached DFS0793I when global
flood is relieved Action message is sent to all OTMA members New
input messages are not rejected Until IMS 13 /DISPLAY OTMA
enhancement New global message flood warning level display under
the INPT column of the OTMA Server name Whats New in OTMA, IMS
Connect, and WebSphere MQ 91
92. IMS Regional User GroupIMS 11 OTMA Dynamic Descriptors With
IMS 11, descriptors can be managed dynamically CREATE OTMADESC Used
to create a new OTMA message routing descriptor UPDATE OTMADESC
Used to modify an existing destination routing descriptor DELETE
OTMADESC Used to remove an existing destination routing descriptor
QUERY OTMADESC Used to display the characteristics of a specific
destination routing descriptor Whats New in OTMA, IMS Connect, and
WebSphere MQ 92
93. IMS Regional User GroupIMS 11 OTMA Virtual Storage Relief
OTMA obtains storage for TPIPEs, input anchor blocks (TIBs) and
output anchor blocks (QABs) as needed User processing can create
MANY of these blocks These control blocks have ITASKs associated
with them 2 ITASKs per TPIPE 1 ITASK per TIB 1 ITASK per QAB Each
ITASK has 6 control blocks Whats New in OTMA, IMS Connect, and
WebSphere MQ 93
94. IMS Regional User GroupIMS 11 OTMA Virtual Storage Relief
Storage for all of these control blocks are above the 16MB line
However each control block had a 64-byte CDE in LSQA below the 16
MB line These CDEs have been removed and replaced with control
blocks above the bar (> 2.2GB) This greatly reduces OTMA use of
virtual storage below the 16MB line and greatly reduces the chances
of S878, S80A, and S40D abends This also means that you can no
longer track these control blocks using the CDE chain Whats New in
OTMA, IMS Connect, and WebSphere MQ 94
95. IMS Regional User GroupIMS 11 IMS Connect Open Database IMS
Connect is now the TCP/IP portal for access to IMS data as well as
IMS transactions z/OS LPAR A IMS z/OS WAS Universal Traditional
ODBA DB Resource O ODBM Distributed T C Adapter J D S B C PC S C O
D PC CTL IMS DB P C A I I B I JEE A A WAS on Any Platform P
Universal 1.5 XCF S DB Resource T LPAR B IMS C Traditional ODBA O
Adapter IMS Universal Drivers P A J JDBC ODBM PC C I O CTL P S IMS
DB A P C D 1.5 DLI I B A Non- IMS Universal Drivers LPAR C JEE JDBC
IMS TCP/IP IMS Connect ODBM S O T D PC CTL DLI C S C IMS DB P C I B
TCP/IP I I A P RYO DRDA Appl. Whats New in OTMA, IMS Connect, and
WebSphere MQ 95
96. IMS Regional User GroupIMS 11 IMS Connect Port Input/Output
Edit Exit Specified on the HWSCFG TCP/IP control card
PORT=(ID=xxxx,KEEPAV=nn,EDIT=xxxxxxxx) EDIT=xxxxxxxx is the name of
an exit to edit the input and output data from this Port before and
after it is processed by IMS Connect This allows the IMS Connect
Client to send in any data stream, e.g. Pure XML (), and not have
to conform to IMS Connect format but LLLL is required The exit can
add LLZZPrefix, LLZZTrancode, etc. The exit can also reformat the
output data Remove IMS and IMS Connect artifacts The exit can be
dynamically refreshed via command PK48548 is required for this exit
to work properly LLLL will still be required Whats New in OTMA, IMS
Connect, and WebSphere MQ 96
97. IMS Regional User GroupIMS 11 IMS Connect Maximum Socket
Warning Specified on the HWSCFG TCP/IP control card
WARNSOC=nn,WARNINC=nn WARNSOC Decimal value between 50 and 99
(default 80) Sets a warning level as a % of the MAXSOC limit New
message issued HWSS0772W when the warning value is reached WARNINC
Decimal value between 1 and 50 (default 5) Sets the incremental
warning % after WARNSOC has been reached Re-issues HWSS0772W each
time sockets increase by nn% Existing message HWSS0771W is issued
when MAXSOC is reached Whats New in OTMA, IMS Connect, and
WebSphere MQ 97
98. IMS Regional User GroupIMS 11 IMS Connect Maximum Socket
Warning Message HWSS0773I is issued when the number of sockets
falls back below the warning level The message trigger is the lower
of Two times the WARNINC value below the WARNSOC value 5% below the
WARNSOC level Whats New in OTMA, IMS Connect, and WebSphere MQ
98
99. IMS Regional User GroupIMS 11 IMS Connect Automatic
Reconnect to TCP/IP IMS Connect will now automatically reconnect to
TCP/IP when the stack becomes available after a failure There is a
new loop and timer logic for each active Port Invoked if Port is
terminated due to a failure Internally issues an OPENPORT command
Loops back to timer delay if network is still not available Issues
message HWSS0780I for each Port that is successfully reactivated
Whats New in OTMA, IMS Connect, and WebSphere MQ 99
100. IMS Regional User GroupIMS 11 IMS Connect Supermember at
the Datastore Level The Supermember concept allows an IMS Connect
Client to retrieve asynchronous output from the same TPIPE in
multiple IMS TMEMBERs Prior to IMS 11 the Supermember name was
specified on the IMS Connect level All datastores in one IMS
Connect instance had to belong to the same Supermember In IMS 11
the Supermember name can be specified at the Datastore level One
IMS Connect instance can participate in multiple Supermembers Whats
New in OTMA, IMS Connect, and WebSphere MQ 100
101. IMS Regional User GroupIMS 11 IMS Connect Remove HWSIMSO0
and HWSIMSO1 These are object code only versions of IMS Connect
User Message Exits HWSSMPL0 and HWSSMPL1 As new features were added
to HWSSMPL0/1 they were not all added to HWSIMSO0/1 so they are out
of date The message IDs for these exits are *IRMREQ*, *IRMRE1*, and
their ASCII equivalents If you do not want to change your existing
IMS Connect Clients you will have to create new exits, based on
HWSSMPL0/1, with these IDs Do not try to keep a copy of the IMS
9/10 load module and use it in IMS 11 It will not work See next
foil Whats New in OTMA, IMS Connect, and WebSphere MQ 101
102. IMS Regional User GroupIMS 11 IMS Connect Restructure of
HWSEXPRM HWSEXPRM is the control block passed from IMS Connect to
the IMS Connect User Message Exit This has changed for IMS 11 All
IMS Connect User Message Exits must be re-assembled using the IMS
11 macro library This includes HWSSMPL0/HWSSMPL1 and HWSJAVA0 The
re-assembled exits will not work in prior versions of IMS Connect
Whats New in OTMA, IMS Connect, and WebSphere MQ 102
103. IMS Regional User GroupIMS 11 IMS Connect VIEWxxxx
Enhancements All new parameters are displayed VIEWHWS WARNSOC,
WARNINC VIEWPORT KEEPALIVE, EDIT VIEWDS STATE, Supermember, CM0ATOQ
State = AVAIL, WARN, SEVERE, N/A A DATASTORE column has been added
to the Socket data line for the VIEWHWS and VIEWPORT commands
HWSC0001I CLIENTID USERID TRANCODE DATASTORE STATUS SECOND CLNTPORT
IP-ADDRESS HWSC0001I CLIENT01 USRT001 APOL12 IMS1 CONN 7 1026
009.030.123.148 VIEWHWS SUMMARY shows all data except the
individual sockets There can be 1,000s of these Whats New in OTMA,
IMS Connect, and WebSphere MQ 103
104. IMS Regional User GroupIMS 11 IMS Connect Other
enhancements The recorder trace can now optionally be run as a BPE
external trace This provides better processing when the data set is
full The IMS Connect User Message Exit can return an error message
to the IMS Connect Client without disconnecting a persistent socket
Defining only one SSL Port is now enforced during IMS Connect
initialization Whats New in OTMA, IMS Connect, and WebSphere MQ
104
105. IMS Regional User GroupIMS 11+ OTMA APPC/OTMA RRS
Protected Conversation Processing with ROLB Call APAR PK84674
removes ABENDU711-20 when a ROLB call is issued in an RRS protected
conversation The ROLB call will not affect the entire RRS protected
Unit of Work The RRS protected input remains in process until a
commit point The outbound protected conversation will not be
notified to backout Migration consideration The IMS application
must now notify the outbound protected application to do backout
Whats New in OTMA, IMS Connect, and WebSphere MQ 105
106. IMS Regional User GroupIMS 12 IMS to IMS TCP/IP Messaging
Enhancements to leverage TCP/IP networks for communications between
IMS systems for: OTMA remote ALTPCB output (TCP/IP PGM-PGM Switch)
Uses one-way message communications Local IMS Connect Remote IMS
Connect IMS1 IMS 2 MSC TCP/IP Request and response message
communications IMS Connect processes both the request and response
messages as one-way asynchronous messages Local IMS Connect Remote
IMS Connect Send socket IMS1 IMS 2 Receive socket Whats New in
OTMA, IMS Connect, and WebSphere MQ 106
107. IMS Regional User GroupIMS 12 TCP/IP OTMA Remote ALTPCB
Output TCP/IP connections between the local and remote IMS systems
Are managed by IMS Connect to IMS Connect communications Without
having to write client code or invoke additional gateways Example:
Customer IMS1 IMS Connect1 IMS Connect2 IMS2Existing Gateway
Application Resume Tpipe OMethod O ISRT ALTPCB T T XCF TCP/IP
TCP/IP XCF Descriptor M M ICON1 A Tran output SendOnly A IMS1 IMS
Connect1 IMS Connect2 IMS2 O TCP/IP O New ISRT ALTPCB XCF XCF T T
Method Descriptor M M ICON1 A A Whats New in OTMA, IMS Connect, and
WebSphere MQ 107
108. IMS Regional User GroupIMS 12 TCP/IP OTMA Remote ALTPCB
Output OTMA Sends OTMA remote ALTPCB messages to IMS Connect using
new destination information OTMA destination descriptors or
DFSYDRU0 exit Routine IMS Connect Receives OTMA ALTPCB messages
from a local IMS and sends them to the remote IMS Connect for
processing in the remote IMS Enhanced IMS Connect configuration
specifications IMS1 IMS2 Local IMS Connect Remote IMS Connect App
TMEMBER/ Tran Auth TPIPE Msg Q ISRT ALTPCB ALTPCB destination is
resolved using an OTMA Destination Descriptor or the DFSYDRU0 exit
IMS Connect configuration defines the connection to the remote
Partner Whats New in OTMA, IMS Connect, and WebSphere MQ 108
109. IMS Regional User GroupIMS 12 TCP/IP OTMA Remote ALTPCB
Output New destination descriptor DFSYDRU0 exit parameters (DFSYDTx
Set output flag bit to indicate the member of proclib) message is
an OTMA remote RMTIMSCON= specifies the ALTPCB message. remote IMS
Connect (required) Set the required and optional information in the
OTMA prefix RMTIMS= specifies the target area (mapped by HWSOMPFX
remote IMS (required) macro). New specifications in the RMTTRAN=
specifies the user data section: transaction name to use on the
remote IMS (optional) OMUSR_RMTICON remote IMS Connect USERID=
specifies the RACF OMUSR_RMTIMSID remote userid name to use on the
IMS remote IMS for transaction OMUSR_RMTTRAN remote authorization
(optional) transaction Existing parameter (required) OMUSR_RMTUID
userid for TMEMBER= specifies the local transaction authorization
IMS Connect Whats New in OTMA, IMS Connect, and WebSphere MQ
109
110. IMS Regional User GroupIMS 12 ICON-ICON Communication IMS
Connect provides a new configuration statement RMTIMSCON to
describe the remote IMS Connect TCP/IP environment IMS1 TMEMBER/
Local IMS Connect TPIPE App ISRT ALTPCB ISRT ALTPCB Descriptor XCF
ICON1 WAIT_R DESC1 OTMAHDR | LLZZ | DATA TYPE=IMSCON TMEMBER=ICON1
HWS=(ID=ICON1,XIBAREA=100,RACF=N) RMTIMSCON= ICON2
TCPIP=(HOSTNAME=TCPIP,PORTID=(8888), RMTIMS=IMS2
MAXSOC=50,TIMEOUT=5000, RMTTRAN=TRANABC EXIT=(HWSSMPL0,HWSSMPL1)
USERID=USER01 DATASTORE=(ID=IMS1,GROUP=XCFGRP1,MEMBER=ICON1,
TMEMBER=IMS1,DRU=HWSYDRU0,APPL=APPLID1)
RMTIMSCON=(ID=ICON2,HOSTNAME=ICON2.IBM.COM,
PORT=9999,AUTOCONN=N,PERSISTENT=Y,
IDLETO=60000,RESVSOC=10,USERID=USER01, APPL=APPL01) Whats New in
OTMA, IMS Connect, and WebSphere MQ 110
111. IMS Regional User GroupIMS 12 ICON-ICON CommunicationNew
RMTIMSCON statement in the local IMS Connectidentifies the remote
IMS Connect partner information ID= Identifier for a remote IMS
Connect connection IPADDR= specifies the remote IMS Connect IP
address (IPADDR or HOSTNAME required, but not both) Accepts a
loopback IP address Local and remote IMS Connects are on the same
TCP/IP stack (same LPAR) In the range 127.0.0.0 to 127.255.255.255
Likely used only in test environments HOSTNAME= specifies the
remote IMS Connect hostname PORT= specifies the remote IMS Connect
port AUTOCONN= Y|N, specifies whether to automatically make socket
connections to the remote IMS Connect on startup (optional - for
OTMA only, MSC requires AUTOCONN=N) PERSISTENT= Y|N, specifies
whether the socket connections to this remote IMS Connect are
persistent (optional - for OTMA only, MSC requires PERSISTENT=Y)
Whats New in OTMA, IMS Connect, and WebSphere MQ 111
112. IMS Regional User GroupIMS 12 ICON-ICON Communication New
RMTIMSCON statement in the local IMS Connect identifies the remote
IMS Connect partner information IDLETO= specifies the amount of
time the socket connection is idle before terminating it due to
inactivity (Optional, for OTMA only) RESVSOC= specifies the number
of sockets to reserve for use to this remote IMS Connect USERID=
specifies user ID for generating RACF Passticket to be use by the
remote IMS Connect for authenticating the user (optional if
specified, then APPL must also be specified.) APPL= specifies the
application name for generating RACF Passticket to be use by the
remote IMS Connect for authentication optional if specified, then
USERID must also be specified
RMTIMSCON=(ID=ICON2,HOSTNAME=ICON2.IBM.COM,
PORT=9999,AUTOCONN=N,PERSISTENT=Y,
IDLETO=60000,RESVSOC=10,USERID=USER01,APPL=APPL01) Whats New in
OTMA, IMS Connect, and WebSphere MQ 112
113. IMS Regional User GroupIMS 12 ICON-ICON
CommunicationRemote IMS Connect Configuration IMS1 TMEMBER/ ICON1
config App RMTIMSCON=(ID=ICON2, TPIPE HOSTNAME=ICON2.IBM.COM, XCF
ICON1 ISRT WAIT_R PORT=9999) ALTPCB SendOnly with ACK
LLLL|IRM|LLZZ|TRANABC |DATADescriptorDESC1 Descriptors or DFSYDRU0
exit TCP/IP ICON2D DESC1TMEMBER=ICON1RMTIMSCON=ICON2
HWS=(ID=ICON2,XIBAREA=100,RACF=Y)RMTIMS=IMS2
TCPIP=(HOSTNAME=TCPIP,PORTID=(9999),RMTTRAN=TRANABC
MAXSOC=50,TIMEOUT=5000,EXIT=(HWSSMPL0,HWSSMPL1)USERID=USERXYZ
DATASTORE=(ID=IMS2,GROUP=XCFGRP1,MEMBER=ICON2,
TMEMBER=IMS2,DRU=HWSYDRU0,APPL=APPLID1 Whats New in OTMA, IMS
Connect, and WebSphere MQ 113
114. IMS Regional User GroupIMS 12 ICON-ICON CommunicationSend
to Remote IMS IMS1 TMEMBER/ ICON1 config App XCF ICON1
RMTIMSCON=(ID=ICON2, TPIPE HOSTNAME=ICON2.IBM.COM,PORT=9999) ISRT
WAIT_R ALTPCB SendOnly with ACK Descriptor DESC1 Descriptors or
DFSYDRU0 exit TCP/IP IMS2 XCF Tran Auth ICON2 Msg Q D DESC1
TMEMBER=ICON1 OTMAHDR|LLZZ|TRANABC |DATA RMTIMSCON=ICON2
RMTIMS=IMS2 ICON2 config RMTTRAN=TRANABC TCPIP=(PORTID=(9999),...)
USERID=USERXYZ DATASTORE=(TMEMBER=IMS2,...) Whats New in OTMA, IMS
Connect, and WebSphere MQ 114
115. IMS Regional User GroupIMS 12 ICON-ICON Communication IMS1
App TMEMBER/ TPIPE XCF ICON1 ISRT WAIT_R SendOnly with ACK ALTPCB
Descriptor TCP/IP IMS2 DESC1 Descriptors or DFSYDRU0 exit XCF Tran
Auth ICON2 Msg Q ACK / NAK IMS2 performs transaction authorization,
if necessary, and ACKs or NAKs the messageAnd finally If a message
is NAKed, the OTMAReturn the ACK/NAK correlator token from the
initial request is passed back so that IMS1 can match the NAK to
the request Whats New in OTMA, IMS Connect, and WebSphere MQ
115
116. IMS Regional User GroupIMS 12 ICON-ICON Communication
Supermember Support (Local IMS) (Local IMS Connect) (Remote IMS
Connect) (Remote IMS) ICON1 ICON1 config SMEM=SM01 IMS1 Msg1 IMS2
SM01 ICON4 Msg2 ICON2 Msg1 Msg2 ICON2 config SMEM=SM01 Msg3 ACK
Descriptor DESC1: Msg3 Note: Maximum of 8 IMS Connects TMEMBER=SM01
SMEM=Y Can participate in a super member ICON3 environment ICON3
config SM01 SMEM=SM01 OTMA dynamically updates the - ICON1 super
member list when a - ICON2 member of the group leaves or - ICON3
joins the group Whats New in OTMA, IMS Connect, and WebSphere MQ
116
117. IMS Regional User GroupIMS 12 MSC TCP/IP Support for MSC
communications across a TCP/IP network MSC TCP/IP leverages IMS
Connect and the Common Service Layer A new physical link MSPLINK
TYPE=TCPIP Provides a mechanism to Take advantage of TCP/IP
networks Complement or backup existing SNA/VTAM links Take
advantage of potentially higher bandwidths Supports operational
compatibility with other link types (CTC, MTM, VTAM) Starting,
stopping, updating, displaying, and assigning resources Only
between IMS 12 systems Whats New in OTMA, IMS Connect, and
WebSphere MQ 117
118. IMS Regional User GroupIMS 12 MSC TCP/IP MSC TCP/IP
leverages IMS Connect and the Common Service Layer IMS Connect
sends/receives messages via the TCP/IP network IMS Connect manages
the TCP/IP communications IMS MSC manages the message processing
CSL provides the Structured Call Interface (SCI) for communications
between IMS components including IMS Connect Each IMS and its local
MSC-routing IMS Connect system must be part of the same IMSplex
IMSPLEX= plexname parameter in the Common Layer Section of the
DFSDFxxx of IMS proclib The Operations Manager (OM) is not required
but recommended For type-2 command support Whats New in OTMA, IMS
Connect, and WebSphere MQ 118
119. IMS Regional User GroupIMS 12 MSC TCP/IP IMS to IMS
Connect functionality Isolates TCP/IP from the IMS Control Region
Uses the existing IMS Connect TCP/IP support Provides a new MSC
driver as well as TCP/IP driver for MSC Supports communication with
IMS via the Structured Call Interface (SCI) PLEX1 PLEX2 IMS1 IMS
Connect ICON1 IMS Connect ICON2 MSC IMS2 MSC IMS3 SCI MSC TCP/IP
TCP/IP TCP/IP MSC SCI Driver Driver Driver Driver MSC Whats New in
OTMA, IMS Connect, and WebSphere MQ 119
120. IMS Regional User GroupIMS 12 MSC TCP/IP Benefits Takes
advantage of TCP/IP networks for MSC Can potentially provide for a
higher MSC bandwidth Supports different configurations Coexistence
with or backup of VTAM/SNA links Increases availability Logical
links can be moved between VTAM and TCPIP Flexibility zOS zOS MSC
TCPIP IMSA MSC CTC IMSC MSC MTM IMSD IMSB MSC VTAM Whats New in
OTMA, IMS Connect, and WebSphere MQ 120
121. IMS Regional User GroupIMS 12 OTMA ACEE Reduction New
capability that creates, shares and caches a single ACEE associated
with a RACF userid Shared across multiple OTMA member clients
(TMEMBER) New maximum ACEE aging value during client-bid 999999
seconds (11.5 days) Previously 68 years (OTMA reduced to 2 years)
Range: 300 seconds to 999999 seconds A cached ACEE has an aging
value based on the OTMA member client with lowest aging value Whats
New in OTMA, IMS Connect, and WebSphere MQ 121
122. IMS Regional User GroupIMS 12 OTMA ACEE Reduction Cached
ACEEs Reduce the system storage requirements while providing better
security and performance Only one copy of the ACEE instead of
multiple per OTMA client Reduced storage usage Reduced security
exposure Improved performance Provide consistency Same security
result regardless of which OTMA client is used Lower maximum ACEE
aging value Triggers faster ACEE cache refresh Reduces security
exposure, e.g., userid is revoked or access permissions are changed
Whats New in OTMA, IMS Connect, and WebSphere MQ 122
123. IMS Regional User GroupIMS 12 CM1 Shared Queues XCF New
capability that removes the dependency on RRS in a Shared Queues
environment for APPC synchronous conversations and OTMA CM1
(send-then- commit) interactions Applies only to synclevel=None |
Confirm Synclevel=Syncpoint still requires RRS Communications use
XCF services Whats New in OTMA, IMS Connect, and WebSphere MQ
123
124. IMS Regional User GroupIMS 12 CM1 Shared Queues XCF Using
XCF rather than RRS allows IMS to be the syncpoint manager Enhances
the performance of the commit processing by eliminating RRS logging
overhead Potential RRS commit processing bottleneck Overhead
associated with communicating with an external syncpoint manager
Whats New in OTMA, IMS Connect, and WebSphere MQ 124
125. IMS Regional User GroupIMS 12 CM1 Shared Queues XCF New
options for the existing AOS= parameter in DFSDCxxx to request the
use of XCF AOS=B: Synchronous transactions synclevel=NONE|CONFIRM
can be processed in a back-end system using XCF communications
Note: Processing synclevel of SYNCPT depends on the RRS option
RRS=Y: transactions can be processed at either FE or BE, using RRS
RRS=N: transactions are only processed at the FE AOS=S: allows
synchronous transactions with synclevel of NONE|CONFIRM to be
processed in a back-end system using XCF communications Note:
Processing synclevel SYNCPT is equivalent to AOS=F. AOS=X: allows
synchronous transactions with synclevel of NONE|CONFIRM to be
processed in a back-end system using XCF communications Note:
Processing synclevel of SYNCPT is equivalent to AOS=N Note: (1)
Choice of B|S|X is dependent on how syncpoint messages are to be
processed Whats New in OTMA, IMS Connect, and WebSphere MQ 125
126. IMS Regional User GroupIMS 12 DFS2082 for CM0 Messages CM1
(Send-then-Commit) transactions rely on DFS2082 To end the
outstanding wait if the IMS transaction does not send IOPCB reply
Conversion from the use of CM1 to CM0 (Commit-then- send) For
remote programs waiting for a reply May result in a hang until
timeout if there is no IOPCB reply Enhancement A new
commit-then-send (CM0) optional flag to request DFS2082 Specified
on an input CM0 transaction message Triggers OTMA to send the
DFS2082 message if The IMS application does not reply to the IOPCB
Nor message switches to another transaction Whats New in OTMA, IMS
Connect, and WebSphere MQ 126
127. IMS Regional User GroupIMS 12 Front-End Trace Logging New
AOSLOG=Y|N keyword in the IMS DFSDCxxx PROCLIB member Specifies
whether or not the FE system is to write a 6701 log record for:
Response messages returned from the BE system via XCF Applicable to
all synclevels (NONE, CONFIRM and SYNCPT) Error messages returned
from the BE system via XCF Applicable to all synclevels of (NONE,
CONFIRM and SYNCPT) ID=TIB3 For diagnostics Whats New in OTMA, IMS
Connect, and WebSphere MQ 127
128. IMS Regional User GroupIMS 12 Type-2 Commands New Type-2
commands for IMS Connect resources QUERY IMSCON UPDATE IMSCON
Conform to the IMS command structure using the OM API Processed by
OM clients, e.g., TSO SPOC, REXX SPOC API, Batch SPOC, IMS Control
Center, etc. Can coexist with the previous WTOR and z/OS Modify
commands No changes to the existing command functionality Whats New
in OTMA, IMS Connect, and WebSphere MQ 128
129. IMS Regional User GroupIMS 12 Type-2 Commands QUERY IMSCON
TYPE(type) NAME(name1, name2,...) FILTER(filter) SHOW(attribute(s))
TYPE = Type of resource in IMS Connect ALIAS - aliases of
associated ODBMs (VIEWIA) CLIENT active IMS Connect clients (no
equivalent information in VIEWPORT) CONFIG IMS Connect status and
activity (VIEWHWS) DATASTORE datastores or IMS systems (VIEWDS)
IMSPLEX information about the IMSPLEX (VIEWIP) LINK MSC logical
link (no equivalent) MSC - MSC physical link (VIEWMSC - new for IMS
to IMS TCP/IP Communications) ODBM ODBMs and associated IMS aliases
(VIEWOD) PORT TCPIP port and associated clients (VIEWPORT)
RMTIMSCON - remote IMS Connect and associated send clients (VIEWRMT
- new for IMS to IMS TCP/IP Communications) SENDCLNT send clients
(no equivalent - new for IMS to IMS TCP/IP Communications) UOR -
display unit of recovery identifier (VIEWUOR) Whats New in OTMA,
IMS Connect, and WebSphere MQ 129
130. IMS Regional User GroupIMS 12 Type-2 Commands UPDATE
IMSCON TYPE(type) NAME(name1, name2,...)
START(condition1,condition2,) STOP(condition1,condition2,)
SET(condition1,condition2,) TYPE = Type of resource in IMS Connect
ALIAS - aliases of associated ODBMs (VIEWIA) CLIENT active IMS
Connect clients (no equivalent information in VIEWPORT) CONFIG IMS
Connect status and activity (VIEWHWS) DATASTORE datastores or IMS
systems (VIEWDS) IMSPLEX information about the IMSPLEX (VIEWIP)
LINK MSC logical link (no equivalent) MSC - MSC physical link
(VIEWMSC - new for IMS to IMS TCP/IP Communications) ODBM ODBMs and
associated IMS aliases (VIEWOD) PORT TCPIP port and associated
clients (VIEWPORT) RMTIMSCON - remote IMS Connect and associated
send clients (VIEWRMT - new for IMS to IMS TCP/IP Communications)
SENDCLNT send clients (no equivalent - new for IMS to IMS TCP/IP
Communications) UOR - display unit of recovery identifier (VIEWUOR)
Whats New in OTMA, IMS Connect, and WebSphere MQ 130
131. IMS Regional User GroupIMS 12 - XML Converter Refresh New
Command to refresh an XML converter file that is already in use
UPDATE IMSCON TYPE(CONVERTER) xx,REFRESH CONVERTER NAME(cvrname) F
hws,UPDATE CONVERTER NAME(cvtrname) OPTION(REFRESH) Supported by
all command interfaces: Type-2, WTOR, z/OS Modify Converter files
continue to be: Generated using RDz Loaded by IMS Connect from
STEPLIB/JOBLIB/LNKLST Whats New in OTMA, IMS Connect, and WebSphere
MQ 131
132. IMS Regional User GroupIMS 12 Return RACF Return Codes to
ICON Client Prior to IMS 12 IMS Connect sample User Message Exits
returned RSM RC=08 RSN=40 for any and all security violations No
indication of specific reason E.g. invalid userid, incorrect
password, password expired, etc. With IMS 12, enhancements to RACF
Return Codes: In the Request Status Message (RSM) for RYO and the
IMS SOAP Gateway RSM_RACFRC In the OTMA User Data section for the
IMS TM Resource Adapter OMUSR_RACF_RC New IMS Connect Protocol
level indicates support OMUSR_PROLEV = OMUSR_PR03 Whats New in
OTMA, IMS Connect, and WebSphere MQ 132
133. IMS Regional User GroupIMS 12 RACF Userid Caching Existing
IMS Connect security with RACF=Y Limited caching of RACF Utoken
Consecutive requests on a persistent socket with the same
Userid/Passsword/Group IMS 12 enhancement Common cache for userids
across ALL sessions and ALL ports HWSCFG HWS statement:
UIDCACHE={N|Y} , UIDAGE=aging_value Whats New in OTMA, IMS Connect,
and WebSphere MQ 133
134. IMS Regional User GroupIMS 12 CM0 Nowait ACK for RYO
Clients CM0 Nowait ACK for the IMS TM Resource Adapter (ITRA) was
introduced in IMS 10+ For IMS 12 this is now supported for non-ITRA
Clients IMS Connect indicates to the remote client that the support
is available in the CSM on response CSM_FLG1 = CSM_PRLVLFLG X10
Protocol Level Available CSM_PROTOLVL = CSM_PR02 X02 CM0 Nowait ACK
Support RYO client sends the ACK and indicates Nowait IRM_F1 =
IRM_F1_NoWait X02 IRM_TIMER = XE9 / CZ Whats New in OTMA, IMS
Connect, and WebSphere MQ 134
135. IMS Regional User GroupIMS 12 VIEWHWS Partial Read Status
New READ client status The message has been received by IMS Connect
but is not yet considered a complete input message Should be
transient but can be an indicator of a problem Affects VIEWPORT,
VIEWHWS, QUERY MEMBER, QUERY PORT, QUERY IMSCON command output
Targets the problem Remote clients sends a request to IMS Connect
specifying LLLL IMS Connect reads from TCP/IP until LLLL bytes
received If the client incorrectly has LLLL larger than message
size Client waits for the response message from IMS Connect BUT,
IMS Connect cannot process the message because it has to wait for
rest of the input up to the LLLL value Whats New in OTMA, IMS
Connect, and WebSphere MQ 135
136. IMS Regional User GroupIMS 12 VIEWHWS Partial Read Status
Implementation xx,VIEWPORT 9999 HWSC0001I PORT=9999 STATUS=ACTIVE
KEEPAV=0 NUMSOC=4 EDIT= TIMEOUT=0 HWSC0001I CLIENTID USERID
TRANCODE DATASTORE STATUS SECOND CLNTPORT IP-ADDRESS HWSC0001I
CLIENT01 USRT001 APOL12 IMS1 RECV 113 2414 009.023.038.110
HWSC0001I CLIENT02 USRT002 IMS1 READ 2147 2416 009.023.038.110
HWSC0001I CLIENT03 USRT003 IMS1 CONN 13 2418 009.023.038.110
HWSC0001I TOTAL CLIENTS=3 RECV=1 READ=1 CONN=1 XMIT=0 OTHER=0 If
the client remains in READ for an extended period then a potential
problem exists Whats New in OTMA, IMS Connect, and WebSphere MQ
136
137. IMS Regional User GroupIMS 12 Sample Exit Object Code IMS
11 removed Object Code Only sample User Message exits HWSIMSO0 and
HWSIMSO1 They were old and did not support many new features Sample
exits HWSSMPL0 and HWSSMPL1 were only shipped as source The
customer had to assemble and link these modules even if they were
not modified IMS 12 ships object code for HWSUNIT0, HWSJAVA0,
HWSSMPL0, HWSSMPL1 in addition to the source code Whats New in
OTMA, IMS Connect, and WebSphere MQ 137
138. IMS Regional User GroupIMS 12 New Recorder Trace Records
New level of tracing adds records for TCP/IP and XCF sends and
receives ICONTR TCP/IP Receive ICONTS TCP/IP Send ICONIR IMS OTMA
Receive ICONIS IMS OTMA Send Requires the use of BPE External Trace
support introduced in IMS 11 Due to the amount of data that can be
produced Whats New in OTMA, IMS Connect, and WebSphere MQ 138
139. IMS Regional User GroupIMS 13 OTMA Enhancements The
following enhancements have been announced for OTMA for IMS 13
Synchronous callout (ICAL) to another IMS transaction Early
notification to OTMA Clients at IMS shutdown OTMA D descriptors
support WebSphere MQ DFSYPRX0 and DRU exits called even if D
descriptors Global TIB flood control rejects new messages
Synchronous callout retrieve the rest of truncated response message
OTMA C/I use HOLDQ for asynchronous output /DIS TMEMBER xxx TPIPE
yyy displays HOLDQ messages WTO important OTMA messages Other minor
enhancements Whats New in OTMA, IMS Connect, and WebSphere MQ
139
140. IMS Regional User GroupIMS 13 IMS Connect Enhancements The
following enhancements have been announced for IMS Connect for IMS
13 ISC over TCP/IP Dynamic addition of Ports to monitor Dynamic
creation of Datastores QUERY XML converters Automatic restart of LE
environment after XML Converter abend Use RACF ENF (Event
Notification Facility) for Userid ACEE cache Notify WLM so Sysplex
Distributor can direct connections Maximum number of XML converters
increased from 100 to 2000 Whats New in OTMA, IMS Connect, and
WebSphere MQ 140
141. IMS Regional User GroupIMS 13 ESAF Enhancement IMS Java
regions can now use ESAF (ESS) Connections to DB2 Eliminates the
need for RRS Connections to MQ Whats New in OTMA, IMS Connect, and
WebSphere MQ 141
142. IMS Regional User GroupIMS Connect Extensions There have
been many enhancements to IMS Connect Extensions V2.1 Rules-based
routing Routing intelligence improved to use IMS flood-warn state
Improved management of IMS Connect transaction options Persistent
trace: activate IMS Connect Extensions tracing on every system
restart Verify user service exit function Batch Command utility
refresh of Connect Extensions options Mixed-case password support
Whats New in OTMA, IMS Connect, and WebSphere MQ 142
143. IMS Regional User GroupIMS Connect Extensions There have
been many enhancements to IMS Connect Extensions in new Version 2.2
Eclipse-based operational management GUI Extended status
information TCP/IP information (similar to NETSTAT) for active
sessions IMS 11 command support IMS 11 event collection Simplified
configuration with setup dialog Whats New in OTMA, IMS Connect, and
WebSphere MQ 143
144. IMS Regional User GroupIMS Connect Extensions There have
been many enhancements to IMS Connect Extensions in new Version 2.3
Support MSC via IMS Connect Support Remote ICON feature Buffer
Journal output Display Timeout value ODBM security exit IVP with
DRDA workload Security based on Client IP address and IMS Connect
Port Override Expiry and Cancel Client Operations Console
enhancements Whats New in OTMA, IMS Connect, and WebSphere MQ
144
145. IMS Regional User GroupIMS Enterprise Suite There are
several IMS features which are currently downloaded from the IMS
Web site The IMS Enterprise Suite will now package several of these
feature in an SMP installable package IMS SOAP Gateway enhanced
with WS*Security and Business Events support IMS DLIModel Utility
IMS JMS API IMS Connect API for Java IMS Connect API for C and C++
IMS Explorer Whats New in OTMA, IMS Connect, and WebSphere MQ
145
146. IMS Regional User GroupIMS Enterprise Suite IMS Explorer
IMS GUI-based framework for consistent and integrated tools across
environment Easier visualization and editing of IMS Database and
Program Definitions Graphical display of IMS segment hierarchy
and
