Date post: | 23-Jan-2018 |
Category: |
Technology |
Upload: | ibm-ims |
View: | 255 times |
Download: | 2 times |
© 2014 IBM Corporation© 2012 IBM Corporation
IMS Version 13
© 2016 IBM Corporation
IBM
IMS Connect Extensions for
z/OS
James Martin
IBM Client Technical Professional
IBM Systems Software Technical Sales - IMS and Tools
IMS Version 14
IMS Connect Extensions
For customers looking to modernize IMS, IMS Connect Extensions helps
manage new workloads and the transformation of existing workloads to use
TCP/IP networks. Supporting IMS Connect, a free gateway into IMS, IMS
Connect Extensions records TCP/IP events, provides fail-over and routing
to new traffic, and helps make workload scale by improving parallelism.
With Connect Extensions, modern workloads gain higher availability and
clients are insulated from the physical implementation of the network.
IMS Version 14
An IMS Connect customer’s profile
P.O.C
Network Modernization
GreenfieldDevelopment
• Gradual migration
• Incremental growth in use
• Experiences growth painsApplication Modernization
IMS Connect use
IMS Version 14
Availability requirements change
Early solutions might not be fit to scale
Increasing customization needs
Operations and maintenance challenges
Balance consolidated workloads with built-in
redundancy
Clients coded to an inflexible topology
IMS Connect Growing pains
IMS Version 14
IMS Connect Extensions value proposition
Flexible out of the box solutions to many problems new customers face.
Minimises or removes the need for expensive customisation of IMS Connect exits.
Incudes modern centralized interfaces to monitor and control their modernized workloads.
Instrumentation to help fine-tune implementation and identify application problems.
Positions customer for incremental growth in the use of IMS Connect.
For customers new to IMS Connect
For established IMS Connect customers
Allows rationalisation of IMS Connect use.
Inexpensive transition to a more flexible configuration with increased reliability and availability.
Central management of many options typically set by the (distributed) clients.
Allows customers to retire home-grown customizations, reducing support costs.
Modern centralized interface to monitor and control multiple IMS Connect systems.
Built-in scripting environment for sophisticated operational automation.
Cost
reduction
Time to
marketStrong
foundation
for growth
Reduced
development
costs
Modernize
operations
Improving
availability
IMS Version 14
Key features - Routing
Routing introduces a level of abstraction between TCP/IP clients and IMS. Routing Rules provide the connection between IMS connect client requests and IMS resources.
What is Routing?
Why is routing important?
Routing enables fine control over IMS Connect workloads including:
Redirection and distribution of workload.
Control of workload by Transaction/Database or by a logical grouping.
Seamless single command transitions between different management plans.
Automate IMS shutdowns (with no interruptions to in-flight transactions).
Open Database support.
Insulate clients
from IMS
topology
changes
Respond to
stopped or
stressed
systems
Simplifies
change
management
Optimize
use of
resources
Improves
reliability and
availability
IMS Version 14 User Story: System administrator wants to be able to manage IMS connect workload by transaction, database or application groups.
IMS Connect Extensions OTMA routing
incudes the ability to qualify by Transaction
code. Open database routing support can also
qualify by the database name.
Further to this, greenfield customers have the
opportunity to develop a system of generic
destination identities that can be used to group
workload however they wish.
Routing rules can be designed to route
workload based on these criteria to one or
more destinations.
Optionally fallback destinations can be
specified. Fallback destinations are
automatically used when the primary
destinations become unavailable or are in a
flooded state.
IMS ConnectDatastore ADatastore BDatastore CDatastore D
OTMAMessages
Routing rules
Use Original IMS DestID and
optionally Transaction Code to
determine candidates
IMS ConnectAlias AAlias BAlias CAlias D
Open Database requests
Routing rules
Use Alias or PSB to determine
candidates
Fallback Datastores
Fallback Datastores
IMS Version 14 User Story: System administrator wants to change transaction distribution so that less expensive machinery is favoured during quite periods.
0
20
40
60
80
100
Peak Off-peak Weekend
Wo
rklo
ad
IMS Connect
DS1 ($)
DS2 ($)
DS3 ($$$)
IMS Connect extensions routing plans and
datastore capacity weights allow operations to
pre-configure different workload management
plans to suite changing conditions.
Operations can transition from one plan to
another manually using the IMS Connect
Extensions Operations Console.
Alternatively the process can be packaged as an
automated job to be run as part of a regular
schedule.Automation
Sample is
shipped with
the product.
IMS Version 14 User Story: Operations need to be able to take down IMS resources without interrupting in-flight work.
IMS Connect Extensions includes a facility that
allows for the draining of datastore associated
with an IMS system before it is shut down.
A co-ordinated drain of multiple Datastores
across multiple IMS Connect systems for the
same IMS system can be initiated manually
using the IMS Connect Extensions Operations
Console.
Alternatively the process can be packaged as
an automated job that can monitor each
datastore for activity and automatically stop the
IMS system when all in-flight workload has
completed.
Automation
Sample is
shipped with
the product.
IMSICON 1 Datastore for IMSA
ICON 2 Datastore for IMSA
ICON 3 Datastore for IMSA
IMSICON 1 Datastore for IMSA
ICON 2 Datastore for IMSA
ICON 3 Datastore for IMSA
IMSICON 1 Datastore for IMSA
ICON 2 Datastore for IMSA
ICON 3 Datastore for IMSA
1. Active IMS system used by
three IMS Connects
2. Drain initiated stopping
new transactions to IMS
system. Workload is routed
to other IMS systems
3. When all activity has
completed the IMS system
can be bought down safely
4. When the IMS system is restarted
IMS Connect Extensions
automatically resumes routing
workload to it.
IMS Version 14
Key features - Security
Password, Passticket and Password Phrase verification.
ACEE caching.
Automatically monitors RACF Event Notification Facility (ENF) events for changes.
What does IMS Connect provide?
Why use IMS Connect Extensions security?
It provides all of the above and.
Access control by system name, client IP address and port.
Consistent implementation for both traditional OTMA clients and Open Database clients.
IP Address
white and
black lists
Works with
routing to
enhance
security
Manage
cache with
GUI
IMS Version 14 User Story: Customers security standards requires that TCP/IP access to enterprise systems is restricted by IP address.
IMS Connect Extensions includes a facility to
manage access to IMS Connect systems
based on the IMS Connect system a client is
connecting through and the IP address they
are connecting from.
Security rules (RACF or other) can be used to
produce white lists that only allow certain IP
addresses access through IMS Connect.
Equally rules can be formed to produce black
lists that reject access from certain IP
addresses or address ranges.
Access can be restricted further based on the
IMS Connect Port being used by the client.
With this facility a customer can trust the
source of a trusted user.
IMS Cloud – ICON, IMS, CEX
Is the user at that IP address authorized to access the requested
IMS Connect, via this port?
IMS Version 14
Key features - Centralised management of clients
Transaction expiration
IRM Timer values
Client ID cancellation
Extended RSM feedback
Message translation maps
Duration of persistent sessions
What client options can IMS Connect Extension manage?
Why is this important?
Centralized management of these options removes the need to rollout expensive and difficult
changes to distributed clients.
Fine tuning
options by
transaction
Restrict client
session life
Removes
the need to
customize
exits
Changes
are immediate
IMS Version 14 User Story: System administrator needs to redistribute persistent sessions to newly started IMS Connect systems.
When a IMS Connect system is restarted after
maintenance, established persistent socket
sessions on other IMS Connect systems
remain in place. The newly started IMS
Connect is under utilized and the sysplex
workload appears out of balance.
IMS Connect Extensions includes a facility to
limit the number of transactions on a persistent
session. Once the limit is reached the socket is
automatically and safely closed allowing a
client to reconnect on other systems. Over time
sessions are re-balanced between systems.
In addition to this individual sessions can be
safely ‘drained’. This can be done manually
using the IMS Connect Extensions Operations
Console. Alternatively the process can be
packaged as an automated job to be run at
regular intervals.
ExistingIMS Connect(300 clients)
PersistentTCP/IPClients
ExistingIMS Connect(300 Clients)
NewIMS Connect
(0 Clients)
+
IMS Version 14
Key features - Centralized monitoring and control
P
You’ve modernized your applications. Now modernize your administration
File Option Help
----------------------
_ Stop IMS 1 link
_ View TOKYO sessions
_ Stop NY sessions
F1 – Help F2 - Scroll
Eclipse
or ISPF
And REXX
for
Automation
/* REXX */
address LINK "CEXRXENV INIT“
address CEX
"CONNECT HOST=FTSD,"||,
"PORT=13883,HWSID=HWS1,
“SWITCH TYPE=JOURNAL"
address LINK "CEXRXENV TERM"
Sysplex
view and
control of
resources
REXX
environment
for automation
Sysplex
view and
control of
sessions
Starting point
for problem
determination
IMS Version 14
You don’t need to use VIEWHWS
• Consolidated output from multiple systems.
• Output is tabulated.
• Built-in filtering and sorting.
• Instant export to spreadsheet applications.
• Context actions: perform commands directly against objects in table.
• Output in system-specific joblogs.
• Output is cluttered and fills spool.
• Difficult to filter, search, sort, summarize and export.
• Displays don’t provide leads to command actions.
VIEWHWS IMS Connect Extensions
Key customer
message
IMS Version 14
Still using /VIEWHWS? The Status Monitor
The Status Monitor view provides you with:
• Tabbed views of each resource type.
• Context actions against resource instances like drain, stop and start.
• Sortable, searchable and filterable sysplex view of resources.
• Summarise, save and export the session list as a CSV file.
• Auto update and highlighting any criteria.
• Many more session attributes.
IMS Version 14
Properties view…
The sessions view provides you with:
• Context actions to cancel sessions and get network status.
• Sortable, searchable and filterable Sysplex view of sessions.
• Ability to summarize, save and export the session list as a CSV file.
• Auto update highlighting any criteria.
• Many more session attributes.
Still using /VIEWHWS ? Sessions Display
IMS Version 14
IMS Connect Extensions Host command environment for REXX
Host command environment for REXX:
• Includes most IMS Connect Extensions commands.
• Improves options for automated solutions
• allows flexible and tightly integrated automation
Move up a gear and automate
Utilize the
Flexibility
of REXX
Integrate
with other host
command
environments
Single REXX
to control
multiple
systems
Automate
routine
operational
activities
Includes many
useful working
REXX
samples
IMS Version 14
IMS Connect Extensions with IMS PA and IMS PIOTMA Workloads ODBM Workloads
IMS Version 14
IMS Connect Extensions with IMS PA and IMS PI
Tracks DRDAflow
Reports separateresponse timesfor IMS Connect
and IMS
WebSphereApplicationServer (WAS)
IMSConnect
IMSConnectExtensions
IMSPerformance
Analyzer
IMSProblemInvestigator
ODBM IMS
WASsupport staff
The problem is somewhere in here:a reporting "black hole" betweenthe two product support teams IMS
support staff
Response times over 2 seconds!
"WebSphere Application Server waits 2 secondsfor a response from IMS. Contact IMS support."
"IMS respondsin a millisecond."
Event journal
IMS log
IMS Version 14
You don’t need to use the Recorder Trace
• Conditional trace record generation may be based on a variety of criteria.
• Trace records are contained in existing journals.
• Trace records contain detailed IRM, RSM, CSM and RXML sections for both READ and XMIT.
• Trace records have correlation tokens that allow transaction tracking and reporting in IMS Problem Investigator and IMS Performance Analyzer.
• The journal can be merged with IMS logs to give an end-to-end view of a transaction initiated by a distributed client.
• Invoke via GUI, ISPF and REXX (batch).
• Tracing is non-specific.
• Recorder trace and BPE trace records are produced in separate log datasets.
• There are no mechanisms to correlate recorder trace records with other log sources.
Recorder Trace IMS Connect Extensions
Key customer
message
IMS Version 14
22
IMS Version 14
Resources
IMS Connect Extensions for z/OS V2.4 User Guide
https://www-01.ibm.com/support/knowledgecenter/SSAVHV_2.4.0/cex-welcome.dita
IMS Performance Solution Pack: Overview and Customization V1.3
https://www-01.ibm.com/support/knowledgecenter/SSS8SV_1.3.0/fun_home.dita
Technotes
http://www-01.ibm.com/support/search.wss?rs=434&tc=SSCX88S&dc=DB520+D800+D900+DA900+DA800+DB560&dtm
IMS Version 14
24