Page 1
IMS 10 2Q2007
[email protected] 1
IMS 10 for your On Demand Business
Alison [email protected]
Page 2
Important Disclaimer
� 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 IBM’S 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, OR SHALL HAVE THE EFFECT OF:�CREATING ANY WARRANTY OR REPRESENTATION FROM IBM (OR ITS
AFFILIATES OR ITS OR THEIR SUPPLIERS AND/OR LICENSORS); OR �ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE
AGREEMENT GOVERNING THE USE OF IBM SOFTWARE.
Page 2
IMS 10 2Q2007
[email protected] 2
Page 3
IMS 10 General Availability - 26th October 2007
� The new version of IMS is a great example of one of the things IBM does best: leverage its deep technical expertise to develop and deliver solutions for customers' fundamental business challenges.
Charles King
Principal analyst at Pund-IT
For software, age 40 “could be the
new 20”. We’ve seen the first 40 years of IMS, now let’s see what the next 40 will be like. Bernie Spang, IBM
� ..alternatives to IMS..but few (if any?) provide the performance and reliability of IMS.
� IBM continues to invest in and market IMS as its best high transaction data processing
solution.
� ..high transaction competence..
� Helping Customers migrate business critical applications to Service Oriented Architecture
with the upcoming release of IMS 10..
� ..continuation of IBM’s Information On-Demand initiative..
ComputerWorld
eWeek
CIO Today
PC Magazine
Sci-Tech Today
InfoWorld
CNNMoney.com
Web Services
Journal
Page 4
An On Demand Business …
An enterprise whose business processes -- integrated end-to-end across the company and with key partners, suppliers and customers --can respond with speed to any customer demand, market opportunity or external threat.
Page 3
IMS 10 2Q2007
[email protected] 3
Page 5
The Four Aspects of the IBM On Demand Strategy…
…exactly match IMS’s strategy
IntegrationIntegration
AutonomicsAutonomicsVirtualizationVirtualization
OpennessOpenness
Page 6
IMS 10 Major Enhancements
� Manageability�Dynamic Resource Definition (DRD)
�ACBLIB Member Online Change
�Operations and Systems Management Enhancements
� Scalability�Parallel RECON Access
�MSC Bandwidth Improvement
� Integration/Open Development �XQuery
�Callout Support
Page 4
IMS 10 2Q2007
[email protected] 4
Page 7
IMS 10
Systems Management
Page 8
IMS 10 Systems Management
Overview
� Operations Manager Enhancements
� Dynamic Resource Definition
� ACBLIB Member Online Change
� ACB Online Change
Page 5
IMS 10 2Q2007
[email protected] 5
Page 9
Common Service Layer (Reminder)
� Structured Call Interface (SCI)�Provides communication between components
� Operations Manager (OM)� Implements an API for the entry and response of
commands
� Resource Manager (RM)�Provides infrastructure for IMS’s management of its
resources and IMSplex-wide processes
CF
Resource Structure
IMSControlRegion
SCI
SCICommunications
SCI
OperationsManager
(OM)
SCI
ResourceManager
(RM)
SCI
StructuredCall
Interface
SCI
CQS
Page 10
Sample IMSplex Configurations
CF
IMSCTL
SCI
OM
SCI
RMSCI
SCISCI
SCI
SCI
CQS
OM
SCI
IMSCTL
SCI
RMSCI
SCISCI
SCI
ResourceList Structure
LOGRList Structures
SMQList Structures
OSAMCache Structure
VSAMCache Structure
Shared VSOCache
Structures
IRLMLock Structure
VGRList Structure
OM
SCI
RMSCI
SCISCI
IMSCTL
SCI
OM
SCI
RMSCI
SCISCI
IMSCTL
SCI
SCI
SCI
CQS
SCI
CQS SCI
CQS
SCI
XCF
XCF
XCF XCF
SCI
IMS 9/10ControlRegion
OM
Automation
SPOC
4-way IMSplex 1-way IMSplex
An IMSplex is a set of one or more IMS systems implemented with the Common Service Layer
Page 6
IMS 10 2Q2007
[email protected] 6
Page 11
IMS Single Points of Control (SPOCs)
� A SPOC is a program that interfacesbetween a user and the OM
� From this single point, user can enter commands to any or all IMSs
� TSO SPOC (enhanced in IMS 10)� Workstation SPOC (IMS Control Centre)� REXX SPOC (enhanced in IMS 10)
Single Point Single Point of Control of Control
(SPOC)(SPOC)SCI
OperationsManager
(OM)
SCI
StructuredCall
Interface
IMSControlRegion
SCI
IMSControlRegion
SCI
IMSControlRegion
SCI
Page 12
Display formatted as a table by SPOC from XML response.
TSO SPOC – “Type-2” Command Response
File A ction M anage Resources S POC View O ptions H elp
PLX0 IMS Single Point of Control
Command ===> Plex . _____ Route . IMS13____ Wait
Response for: QRY TRAN NAME(A*) SHOW(ALL) More: +> Trancode MbrName CC PSBname QCnt LCls LQCnt LLCT LPLCTADDINV IMS1 0 0 ADDINV IMS1 0 DFSSAM04 4 0 2 65535ADDINV IMS3 0 DFSSAM04 4 0 2 65535ADDPART IMS1 0 0 ADDPART IMS3 0 DFSSAM04 4 0 2 65535AOBMP IMS1 0 0 AOBMP IMS1 0 TS2IAOB0 23 0 65535 65535etc.
Type-2 Commands
• QUERY (QRY)
• INIT
• TERM
• UPDATE (UPD)
• DELETE (DEL)
IMS 10 adds
• QUEUE
• CREATE
• EXPORT*
• IMPORT*
*Through the IMS 10 Service Process
Page 7
IMS 10 2Q2007
[email protected] 7
Page 13
Operator Interface
� Type-2 commands have a simple standard syntax providing a consistent and modern look-and-feel
UPDATE DB NAME(CUSTADD,CUSTUPD) SET(ACCTYPE(EXCL) RESIDENT(N))
� The strategy is to enable all but the least common command functions to be available with type- 2 commands, entered at a SPOC� V8 introduced UPDATE TRAN (and QUERY TRAN)
� V9 added UPDATE DB, AREA and DBGRP (and related QUERY)
� Enhanced in IMS 10
� IMS 10 adds UPDATE PGM, RTC and MSC resources (and QUERY)
� IMS 10 adds significant enhancements to most QUERY commands
� IMS 10 adds new QUEUE command
� To enqueue transaction or LTERM message, or dequeue transactions or LTERM messages
Page 14
Operator Interface …
� IMS 10 adds viewable SPOC audit trail �TSO SPOC option for viewing zOS logstream
�Can include OM commands/responses and
�unsolicited messages
�Can choose sources or types of sources
� Includes replies to new QUEUE TRAN command
�More generally, a SPOC (e.g. a REXX SPOC) can SUBSCRIBE to receive such messages in real time
� IMS 10 adds a Batch SPOC�No need to use REXX or
handle XML parsing
�Commands defined in SYSIN file
�Multiple commands allowed
�Commands executed serially
�Output to SYSPRINT
�Responses formatted to look like TSO SPOC screen format
IMS 10 provides “critical mass” to enable general operator use of SPOCs and OM for IMS operations
�Single system image of IMSplex
�Use of simpler modern consistent type-2 commands
Page 8
IMS 10 2Q2007
[email protected] 8
Page 15
TSO SPOC Audit Trail option
Help
PLEX1 IMSplex Audit Trail
Command ===>
Fill in the fields and press the Enter key.
* Datastream name . . . syslog.om2q01.log
Start date . . . . . . 2007.230 YYYY.DDD or *
Start time . . . . . . 14:00:00 HH:MM:SS or *
End date . . . . . . . * YYYY.DDD or *
End time . . . . . . . * HH:MM:SS or *
Log stream name defined in OM Initialization
PROCLIB Member and LOGR Policy
Asterisk means current date and time
Page 16
Audit Trail Display from TSO SPOC
File Action Manage resources SPOC View Options Help
PLEX1 IMSplex Audit Trail
Command ===>
Members . . Type . .
More: +>
MbrName Time Message
IM1A 2007.298 09:25:49.60 DFS3499I ACTIVE DDNAM ES: MODBLKSA IMSACBB FORMATA
IM1A 2007.298 09:25:49.61 DFS3804I LATEST RESTA RT CHKPT: 07298/102549, LATES
COUGHTA 2007.298 09:33:32.60 Cmd input . : DIS OLDS
COUGHTA 2007.298 09:33:32.60 Response for: DIS OLDS
COUGHTA 2007.298 10:26:29.28 Cmd input . : QRY TRAN NAME(*) SHOW(TIMESTAMP)
COUGHTA 2007.298 10:26:29.28 Response for: QRY TRAN NAME(*) SHOW(TIMESTAMP)
COUGHTA 2007.298 10:26:51.44 Cmd input . : QRY TRAN NAME(*) SHOW(TIMESTAMP)
COUGHTA 2007.298 10:26:51.44 Response for: QRY TRAN NAME(*) SHOW(TIMESTAMP)
COUGHTA 2007.298 12:52:56.87 Cmd input . : QUEUE TR AN NAME(PART) DATA(an960c10)
COUGHTA 2007.298 12:52:56.87 Response for: QUEUE TRAN NAME(PART) DATA(an960c10)
IM1A 2007.298 13:00:01.07 DFS3257I ONLINE LOG N OW SWITCHED - FROM DFSOLP00 T
IM1A 2007.298 13:00:01.08 .DFS058I 14:00:01 SWI TCH COMMAND COMPLETED.
IM1A 2007.298 13:00:01.10 DFS3257I ONLINE LOG N OW SWITCHED - FROM DFSOLS00 T
IM1A 2007.298 13:00:01.29 DFS2484I JOBNAME=IVPG NJCL GENERATED BY LOG AUTOMAT
IM1A 2007.299 11:30:49.53 DFS2864I EXTERNAL TRA CE DATASET DFSTRA01 FULL - SW
IM1A 2007.299 13:00:01.08 DFS3257I ONLINE LOG N OW SWITCHED - FROM DFSOLP01 T
Press enter to see command response
Page 9
IMS 10 2Q2007
[email protected] 9
Page 17
TSO SPOC Audit Trail - Highlighting
File Action Manage resources SPOC View Options Help
PLEX1 IMSplex Audit Trail
Command ===>
Members . . Type . .
More: -+>
MbrName Time Message
IM1A 2007.232 15:59:22.11 DFS2208I DUAL LOGGI NG IN EFFECT ON IMS LOG DATA
IM1A 2007.232 15:59:22.11 DFS2208I DUAL LOGGI NG IN EFFECT ON WRITE AHEAD D
IM1A 2007.232 15:59:22.11 DFS2207I IMS LOG(S) BLOCKSIZE= 22528, BUFNO=0005
IM1A 2007.232 15:59:22.11 DFS3613I - DLG TCB INI TIALIZATION COMPLETE IM1A
IM1A 2007.232 15:59:22.15 DFS0578I - READ SUCCES SFUL FOR DDNAME PROCLIB MEM
IM1A 2007.232 15:59:22.15 DFS0578I - READ SUCCES SFUL FOR DDNAME PROCLIB MEM
IM1A 2007.232 15:59:22.16 DFS0579W - FIND FAILED FOR DDNAME PROCLIB MEMBER =
IM1A 2007.232 15:59:22.16 DFS0579W - FIND FAILED FOR DDNAME PROCLIB MEMBER =
IM1A 2007.232 15:59:22.18 DFS0579W FIND FAILED FOR DDNAME PROCLIB MEMBER=DF
IM1A 2007.232 15:59:22.18 DFS0579W FIND FAILED FOR DDNAME PROCLIB MEMBER=DF
IM1A 2007.232 15:59:22.32 DFS0759I THE FOLLOWIN G VIRTUAL ADDRESSES HAVE BEEN
IM1A 2007.232 15:59:22.32 DFS0759I DFSVNUCI 00044A50-00097978 IM1A
IM1A 2007.232 15:59:22.36 DFS3613I - FP TCB INIT IALIZATION COMPLETE IM1A
IM1A 2007.232 15:59:22.37 DFS225A - CTL REGION WAITING FOR DBRC REGION (IM1A
IM1A 2007.232 15:59:22.62 DFS3613I - CTL TCB INI TIALIZATION COMPLETE IM1A
IM1A 2007.232 15:59:22.62 DFS3349I UNABLE TO IN ITIALIZE TIME CONTROL OPERATI
Page 18
IMS Information Center
Page 10
IMS 10 2Q2007
[email protected] 10
Page 19
Operator Interface …
� IMS 10 adds a REXX XML Parser for interpreting command r esponses from OM�Responses to OM-submitted commands always encapsulated in XML
�Parses XML output directly into a “stem variable” and “suffix”
�Makes interpreting command responses easier for REXX programmer
�Stem variable is “qryinfo.”
�Stem variable suffix is “xmltag1.xmltag2”
<cmd><verb>QRY </verb> <kwd>TRAN </kwd><input>QRY TRAN NAME(CUS*) SHOW(PGM,QCNT) </input>
</cmd>
qryinfoqryinfo. cmd.verbqryinfoqryinfo. cmd.kwdqryinfoqryinfo. cmd.input
Suffixes are documented in the IMS 10 System Programming API Ref.
Page 20
IMS Resource Definition Evolution
� Objective: � Reduce IMS System Generation and System Change
time and effort
� History:�� IMS V4IMS V4 stopped using sysgen to support major new function
�� IMS V5/6IMS V5/6 removed conditional assembly modules
�� IMS V7IMS V7 put non-conditional link-edit modules under SMP control
�� IMS V8IMS V8 enabled installation to use SMP in the standard way
�� IMS V9IMS V9 enabled multiple systems to share same SDFSRESL, removed ETO specification, simplified the nucleus (removed OLC modules) and simplified implementation (no install of cleanup modules, etc.)
�� IMS 10IMS 10 removes FPCTRL macro (replaced by JCL EXEC parameters)
�IMS 10 Includes Dynamic Resource Definition
Page 11
IMS 10 2Q2007
[email protected] 11
Page 21
IMS 10 Dynamic Resource Definition (DRD)
� DATABASE, APPLCTN, TRANSACT and RTCODE macros can b e optionallyoptionallyremoved from the IMS GEN�Replaced by definitions in Resource Definition Dataset (RDDS)
� IMS can acquire these “MODBLKS resources” dynamicall y �At start-up (auto-import) or using IMPORT type-2 command
� Changes can be made using CREATE, DELETE and UPDATE type-2 commands �Superior and non-disruptive alternative to online change of MODBLKS resources
�TSO SPOC enhanced to include a “Manage Resources” application
�Can submit changes in batch using the new batch SPOC
� Changes automatically get saved to RDDS
� Traditional online change is still available�Still needed for ACB or MFS changes
Page 22
Dynamic Resource Definition Flow
IMS System
Definition
Process
DFSINSX0 Exit
IMS
IMS.MODBLKS
AutomaticImport (cold start)
IMPORT*
command
CREATE,
DELETE,
EXPORT*,
IMPORT*,or
UPDATE
commands
Resource
Definition
Dataset
System Resource
Definition
Datasets
(RDDS)
EXPORT*
command
Automaticexport
Control BlocksDDIRsPDIRsSMBsRCTEs
OM Interface
Non-system
RDDS
EXPORT*
command
IMPORT*
command
To Enable DRD specify MODBLKS=DYN in DFSDFxxx IMS.PROCLIB member
1First cold start
2 4
3
5
*Provided through IMS 10 Service Process*Provided through IMS 10 Service Process
Page 12
IMS 10 2Q2007
[email protected] 12
Page 23
Descriptors
� A model (template) for defining (creating) a resour ce or anotherdescriptor�Establishes defaults for attributes not SET in the CREATE command
� IMS-defined descriptors�Provided with the IMS product
�DFSDSDB1, DFSDSPG1, DFSDSTR1, DBFDSRT1
� User-defined descriptors�Created by the user
� Default descriptors�Each resource type will have one current default descriptor
�IMS-defined or user-defined
CREATE TRAN NAME(PART) LIKE(DESC(FPDESC)) SET(CLASS(2))CREATE TRAN NAME(PART) LIKE(DESC(FPDESC)) SET(CLASS(2))
Page 24
Entry Point for DRD Commands
� Commands to CREATE, UPDATE, DELETE or QUERY resources and descriptors are entered through OM interface�TSO SPOC, BATCH SPOC or other OM interface
� Manage Resources User Interface�Subfunction of the ISPF SPOC program
�Screens have same look and feel
� Greatly reduces user’s need to �Format CREATE, DELETE, UPDATE, and QUERY commands
�Know names and valid values for attributes
� Provides two views�List view for less skilled operators
�Requires more screens (in most cases)
�Command syntax view for more skilled operators
�Generally requires a single screen
CREATE TRAN NAME(TESTRAN) SET(AOCMD(N)CLASS(1) CMTMODE( SNGL ) CONV(N)DCLWA( Y )DIRROUTE( N ) EDITUC( Y ) FP( N ) INQ( N ) LCT( 65535 ) LPRI( 1 ) MAXRGN( 0 ) MSGTYPE( MULTSEG )etc…….
Page 13
IMS 10 2Q2007
[email protected] 13
Page 25
DRD Interface – Manage Resources
File Action Manage resources SPOC View Options Help IMS Create Transactions
Command ===> Plex . . Route . . Wait . .
Press Enter to continue More: +
* NAME Transaction name . . TESTRAN
SET
AOCMD AOI command option . . . . . . . N CMD,N,Tran,Y
CLASS Class. . . . . . . . . . . . . . 1 1- 999
CMTMODE Commit mode. . . . . . . . . . . SNGL Sngl, Mult
CONV Conversational . . . . . . . . . N Y, N
DCLWA Log write-ahead option . . . . . Y Y, N
DIRROUTE MSC direct routing option. . . . N Y, N
EDITRTN Input edit routine . . . . . . .
EDITUC Edit to uppercase. . . . . . . . Y Y, N
EMHBSZ EMH buffer size. . . . . . . . . 12-30720
“LIST” View – requires more screens in most
cases
Page 26
DRD Interface – Manage Resources …
File Action Manage resources SPOC View Options Help
IMS Create Transactions Top of data
Command ===> Plex . . Route . . Wait . .
Press Enter to continue
CREATE TRAN NAME( TESTRAN )
SET( AOCMD( N ) CLASS( 1 ) CMTMODE( SNGL ) CONV( N ) DCLWA( Y )
DIRROUTE( N ) EDITRTN( ) EDITUC( Y ) EMHBSZ( )
FP( N ) INQ( N ) LCT( 65535 ) LPRI( 1 ) MAXRGN( 0 ) MSGTYPE( MULTSEG)
MSNAME( ) NPRI( 1 ) PARLIM( 65535 ) PGM( )
PLCT( 65535 ) PLCTTIME( 6553500 ) RECOVER( Y ) REMOTE( N ) RESP( N )
SEGNO( 0 ) SEGSZ( 0 ) SERIAL( N ) SIDL( 0 ) SIDR( 0 )
SPASZ( ) SPATRUNC( ) TRANSTAT( N ) WFI( N ))
F1=Help F3=Exit F4=Showlog F6=Expand F9 =Retrieve“COMMAND SYNTAX View” – one screen
Page 14
IMS 10 2Q2007
[email protected] 14
Page 27
ACB Member Online Change
� Goal is to improve usability and availability with online change
� Capability to add/change specified ACBs by only quiescing resources that are affectedby the online change
� Implemented as an enhancement to Global Online Change� Requires a SPOC
� INIT OLC PHASE(PREPARE) TYPE(ACBMBR) …
� Coexists with existing online change ACBLIB full library switch capability
� ACBGEN is done into the staging ACBLIB, and then …
� … active ACBLIB is backed up to inactive ACBLIB, and then …
� … member OLC copies modified ACBs into active ACBLIB
Page 28
ACB Member Online Change
� Goal is to improve usability and availability with online change
� Capability to add/change specified ACBs by only quiescing resources that are affectedby the online change
� Implemented as an enhancement to Global Online Change� Requires a SPOC
� INIT OLC PHASE(PREPARE) TYPE(ACBMBR) …
� Coexists with existing online change ACBLIB full library switch capability
Page 15
IMS 10 2Q2007
[email protected] 15
Page 29
Online Change Enhancement
� IMS 10 makes available to non-shared queues, an enha ncement already added to shared queues
� Current situation�An online change of an ACB will fail if there are messages on the queue (normal or
suspend queue) for a transaction that has a changed PSB but an unchanged TRANSACT macro
�Similarly for an APPLCTN change with a MODBLKS gen, when TRANSACT macro remains unchanged
� DFS3452I Work in progress for resources to be changed/deleted
� Solution in IMS 10�When attributes of the TRANSACT macro are not changed, IMS 10 will allow online
change to continue even when there are messages on the queue
�For an associated ACB PSB change
�For the related APPLCTN macro change
� Improves chances of successful OLC COMMIT completio n, particularly for ACBLIB-only online change
Page 30
Simplifying PROCLIB Member Usage
� IMS 10 introduces a new PROCLIB member� DFSDFxxx
� DFSDFxxx contains multiple sets of parameters (with appropriate section headers)<SECTION=DYNAMIC_RESOURCES>
<SECTION=SHARED_QUEUES>
<SECTION=COMMON_SERVICE_LAYER>
<SECTION=DIAGNOSTICS_STATISTICS>
<SECTION=USER_EXITS>
� Can be used as an alternative to DFSCGxxx and DFSSQxxx
�� IMS 10 Syntax CheckerIMS 10 Syntax Checker is enhanced to support DFSDFxxx plus 9 other members (in addition to DFSPBxxx, DFSDCxxx and DFSSQxxx from previous releases)
Indicates another strategic IMS direction
Page 16
IMS 10 2Q2007
[email protected] 16
Page 31
IMS 10
Connectivity and Integration
Page 32
IMS 10 Connectivity and Integration
Overview
� DLIModel utility
� IMS XML DB enhancements and XQUERY
� IMS Java
� OTMA
� Connectivity enhancements
� IMS Callout
Data Base
Transaction
Manager
Page 17
IMS 10 2Q2007
[email protected] 17
Page 33
IMS Java Dependent Regions in IMS TM 10
� Requires SDK V5�New JVM
�Simpler setup
�More efficient
� Simplifies the message programming model� Includes syncpoint on message GU
�Consistent with all other languages
Page 34
IMS Java Enhancements
� IMS 10 extends the GSAM support added in V9 � Allows GSAM record to be handled in same way as DB segment
� DLIModel utility can generate GSAM metadata
�offers GSAM database support in the same manner that the IMS Java class libraries support all other IMS database types
� Provides capability to return IMS data from a DB2 J ava Stored Procedure as a DB2 Result Set
� Currently, stored procedure has to return a predefined string of parameters to the caller
� IMS Java provides a java method for converting the IMS result set into a DB2 result set
�which can be returned to the caller
� Makes the stored procedure more flexible to database and client changes
Page 18
IMS 10 2Q2007
[email protected] 18
Page 35
DLIModel Utility Enhancements
� Read COBOL copybooks (without first converting to XMI)
� Generate separate PSB and DBD XMIs and be able to impor t the PSB and/or DBD XMIs
� Fully support GSAM “tables”
IMS Javaclass IMS Java
report
COBOLCopybook members
Control statements:Control statements:1) Choose PSBs/DBDs1) Choose PSBs/DBDs2) Choose copybook 2) Choose copybook
membersmembers3) Aliases, data types, 3) Aliases, data types,
additional fields additional fields
PSB
DLIModel I MS Java Repo rt
== == = == == = == == = == == = == = =
Class: AUTPSB11DatabaseView in package: sa mples.d ealers hip gene rated fo r PSB: AUTPSB11
== == = == == = == == = == == = == = == == = == == = == == = == == = == == = ==
PCB: Dealer
== == = == == = == == = == == = == = == == = == == = == == = == == = == == = ==
Segment: Deale rSegment
Field: Deale rNo Type =CHAR Start =1 Length =4 ++ Pri ma ry Key Fiel d + +
Field: Deale rNa me Type=C HAR Start=5 Length =30 (Sea rch Field)
Field: Deale rCity Type =CHAR Start =35 Length =10 (Search Field )
Field: Deale r Zip Typ e=CHAR Star t=45 Le ngth=1 0 (Sea rch Fi eld)
Field: Deale rPhone Type=C HAR Start=55 Length =7 (Sea rch Field)
== == = == == = == == = == == = == = == == = == == = == == = == == = == == = ==
Segment: ModelSegment
Field: ModelKey T ype=C HAR Start=3 L ength= 24 + + Pri ma ry Key Field + +
Field: Model Type Type= CHAR Start=1 Length =2 (Sea rch F ield)
Field: Make Type =CHAR Start= 3 Length =10 (Search Field)
Field: Model Type =CHAR Start =13 Length =10 (Search Field )
Field: Year Type =CHAR Start =23 Lengt h=4 (Search Field )
Field: MSRP Type =CHAR Start =27 Length =5 (Search Field )
Field: Coun t Type =CHAR Start =32 Len gth=2 (Searc h Field )
== = == == = == == = == == = == == = == == = == = == == = == == = == == = == ==
Segment: O rderSeg ment
Field: O rde rNo Type= CHAR Start=1 Length =6 + + Pri ma ry Key Field + +
Field: La stNam e Type =CHAR Start =7 Lengt h=25 (Searc h Field )
Field: Fir stNam e Type =CHAR Start =32 Len gth=25 (Sear ch Fiel d)
Field: Da te Typ e=CHAR Start =57 Le ngth=1 0 (Sea rch Fie ld)
Field: Ti me Typ e=CHAR Star t=67 Le ngth=8 (Sear ch Fiel d)
= == == = == == = == == = == == = == == = == == = == == = == = == == = == == = =
Segment: SalesSegme nt
Field: SaleNo Type =CHAR Start =49 Length =4 ++ P rima ry Key Field + +
...
If you can read this you do not need glasses; however this is just silly writting to represent
the control statements that are the input to the utility.
DLIModelDLIModelUtilityUtility
DBD
XML Schema(s)
PSB XMI metadata
DBD XMI metadata
package samples.dealership;
import com.ibm.ims.db.*;
import com.ibm.ims.base.*;
public class AUTPSB11DatabaseView extends DLIDatabaseView {
// The following DLITypeInfo[] array describes Segment: DEALER in PCB: AUTOLPCB
static DLITypeInfo[] AUTOLPCBDEALERArray= {
new DLITypeInfo("DealerNo", DLITypeInfo.CHAR, 1, 4, "DLRNO"),
new DLITypeInfo("DealerName", DLITypeInfo.CHAR, 5, 30, "DLRNAME"),
new DLITypeInfo("DealerCity", DLITypeInfo.CHAR, 35, 10, "CITY"),
new DLITypeInfo("DealerZip", DLITypeInfo.CHAR, 45, 10, "ZIP"),
new DLITypeInfo("DealerPhone", DLITypeInfo.CHAR, 55, 7, "PHONE")
};
static DLISegment AUTOLPCBDEALERSegment= new DLISegment
("DealerSegment","DEALER",AUTOLPCBDEALERArray,61);
...
// An array of DLISegmentInfo objects follows to describe the view for PCB: AUTOLPCB
static DLISegmentInfo[] AUTOLPCBarray = {
new DLISegmentInfo(AUTOLPCBDEALERSegment,DLIDatabaseView.ROOT),
new DLISegmentInfo(AUTOLPCBMODELSegment,0),
new DLISegmentInfo(AUTOLPCBORDERSegment,1),
new DLISegmentInfo(AUTOLPCBSALESSegment,1),
new DLISegmentInfo(AUTOLPCBSTOCKSegment,1),
new DLISegmentInfo(AUTOLPCBSTOCSALESegment,4),
new DLISegmentInfo(AUTOLPCBSALESINFSegment,5)
};
...
}
Page 36
IMS 10 XQuery support
� XQuery is a hierarchical query language for XML docum ents� Used to query XML documents and return newly created XML
documents from the data that satisfy the query criteria
� XQuery is a W3C Recommendation
�XQuery is compatible with several W3C standards, such as XML, Namespaces, XSLT, XPath and XML Schema
� XQuery is to XML as SQL is to relational databases
�Or DL/I is to IMS databases
� XQuery is built on XPath expressions
�XPath is used to navigate the XML hierarchy
�Similar to a path call for IMS hierarchies
� Simple tutorial on XQuery is available at:
�w3schools.com/xquery/default.aspAA
BDCB
DC
<bib>for $b in /bib/book where $b/publisher = "Addison-
Wesley" and $b/@year > 1991 return
<book year="{ $b/@year }">{ $b/title }
</book></bib>
Page 19
IMS 10 2Q2007
[email protected] 19
Page 37
XQuery Example with XML DB
SELECT retrieveXML(B, ’<library>{for $x in /bib/book
where $x/price<75 and $x/@year>2004return
<book{$x/@year}>
{$x/title}</book>}
</library>’)
FROM PCB.BOOKS
Result: <library>
<book year=“2005”><title>An Introduction to IMS</title></book>
<book year=“2007”><title>All Data Is Naturally Hierarchical</title></book>
</library>
path to the data
Look at each book and find those that meet thesecriteria
For each match return this
elementattribute
Page 38
XQuery Support with XML DB
� Sample document on which XQuery was done
Page 20
IMS 10 2Q2007
[email protected] 20
Page 39
OTMA Autonomic and Security Enhancements
� Use of OTMA is growing rapidly�Especially for IMS Connect and MQ with WAS
� IMS 10 recognises this by enhancing OTMA and especially its autonomic aspects�Automatic flood control
�TPIPE storage clean-up
�Asynchronous reroute
�Enhanced Time-out control (for commit mode 1, to avoid program hangs waiting for confirmation of SEND of reply)
�Enhanced OTMA display information
�OTMA Routing Descriptors
�To reduce (or eliminate) need for OTMA routing exits
�Member level security
�Resume TPIPE security
Partially retrofitted to IMS V9
IMS TM
Page 40
IMS Connect and IMS TM Resource Adapter* Enhancements
� RACF Mixed Case Password
� Client Password Change Request� Allow user to change security password by submitting a password change request message to the
IMS Connect message exit routine
� ACEE Aging Value� Allow user to set aging value of the cached ACEE for the OTMA security checking for better
performance throughput.
� CM1 Timeout� Allow user to specify timeout value for dependent region wait-syncpoint condition when
acknowledgement message is not received for an OTMA CM1 output response
� Alternate Client ID (also provided as V9 SPE)� Allow user to retrieve IMS asynchronous output by specifying the client ID (TPIPE) of the waiting
message when issuing the RESUME TPIPE
� OTMA provides new security checking
� This is the final step in enabling all Commit Mode 0 (commit-then-send) input to exploit shareable persistent sockets
� Gives best performance
� Avoids potential problems with zOS Sysplex Distributor
� Makes listening for Callout more practical
* Previously known as IMS Connector for Java
Page 21
IMS 10 2Q2007
[email protected] 21
Page 41
IMS V10 Asynchronous CalloutAsynchronous outbound support from IMS applications using ALTPCB1. Asynchronous Callout to EJB
� Customer provides “listener code” in JCA EJB application
2. Asynchronous Callout to Message Driven Bean (MDB)� Use JCA 1.5 inbound architecture support – MDB acts as listener, and calls appropriate service or routine � End-to-end tooling available
3. Outbound Web Services support in IMS SOAP Gateway� IMS SOAP Gateway acts as listener and calls Web Service� WDz tooling used to read WebService Description and generate IMS message definition and XML
transformation routine
In each case, a reply from the called service will be processed by a new IMS transaction
IMS
IMS App 1
z/OS
Request
InitiatingClient
IMS App 2
Response
Web Service
J2EE App
Win, AIX,Solaris, Linux,
etc..
SOAP Gateway
RESUME TPIPE ALT CLIENTID
EJB
MDB
Web Service
WebSphere Application Server
Web Service
IMS z/OS
InitiatingClient
IMS App 2
Response
OTMA RT Security
XMLAdapter
IMSConnect
IMS App 1
(ISRT ALTPCB)Request
Win, AIX, Solaris, Linux etc.
IMS TM Resource Adapter
RESUME TPIPE ALT CLIENTID
OTMA Routing Descriptors
DFSYDTxIMSEJB
TYPE=IMSCON
TMEMBER=SM01
TPIPE=TP3Hold
Q
Page 42
IMS 10
DB Manager and DBRC
Page 22
IMS 10 2Q2007
[email protected] 22
Page 43
IMS 10 Database and DBRC
Overview
� IC2
� ILDS Rebuild Utility
� Large Sequential Dataset support
� Parallel RECON Access
� DBRC API
� RECON READONLY
� DBRC Time stamp precision
Page 44
DB Enhancements
� IC2 utility supports FlashCopy/SnapShot Copy� DB Recovery utility extended to use these
image copies
� The HALDB utility, DFSPREC0 – when used to build the ILDS – can optionally exploit data spaces to sort and load ILDS sequentia lly� Faster
� Has defined free space after load
� Reduces CI/CA splits during subsequent DB Reorganisations
� Large Sequential Dataset Support � More than 65,535 tracks on one volume for a data set
� IMS 10 adds large sequential data set support
� GSAM/BSAM and OSAM data sets
� Logs
� Trace data sets
� Message queue data sets
� GSAM/BSAM files
� OSAM database data sets
Page 23
IMS 10 2Q2007
[email protected] 23
Page 45
Parallel RECON Access (PRA)
� Customers (with or without data sharing) sometimes experience RECON contention problems� typically when running multiple batch/utilities concurrently with online IMS or when
restarting multiple online systems
� IMS 10 Solution (Optional)� Exploit Transactional VSAM (TVS)* to provide record level locking on the RECON
data set� “Data Sharing of RECONs”
� Value� Eliminate RECON contention as a source of problems
�e.g. eliminate ATM timeouts caused by RECON contention at OLDS switch� Increase throughput and remove growth constraint
* TVS is a chargeable feature of DFSMS – but with a specially reduced price for use just with RECON sharing
Page 46
DBRC Recon - Serial Request Processing
IMS1
Switch
DBRC1
IMS2
DBRC2
DB1, DB2, DB3, …DBn
IMS2 OLDS
DFSOLP00
IMS1
DFSOLP01
RECON
OLDS0
OLDS1
DBn
DB2DB1
Auth DBs
Page 24
IMS 10 2Q2007
[email protected] 24
Page 47
DBRC RECON - Parallel Request Processing
IMS1
Switch
DBRC1
IMS2
DBRC2
DB1, DB2, DB3, …DBn
IMS2 OLDS
DFSOLP00
IMS1
DFSOLP01
RECON
OLDS0
OLDS1
DBn
DB2DB1
Auth DBs
Page 48
DBRC API Enhancements
� DBRC API was introduced in V9 for query only
� IMS 10 enhances the QUERY functions …
� … and API is extended to support all DBRC update comm ands
� DBRC security enhanced to provide different levels of access control� READ or UPDATE (and ALTER for AMS DELETE/DEFINE)� A user authorised for READ access only, must specify new READONLY execution
parameter
� The new API will simplify update access from IBM and third-party tools –especially when Parallel RECON Access is enabled
Page 25
IMS 10 2Q2007
[email protected] 25
Page 49
DBRC Timestamp Precision
� Challenge� Because of the speed of today’s processors,
DBRC is recording more duplicate timestamps (log open, log close, allocation)
� Solution� Once all systems are on IMS 10 and MINVERS is set to 10.1, DBRC will increase
the precision of timestamps from tenths of a second to microseconds
� Effects control statements for CA and timestamp DB r ecovery utilities� No problem if using GENJCL.CA and GENJCL.RECOV
� Identifying any RECON record that has timestamp as p art of VSAM key will require a new format timestamp� e.g. CHANGE IC .. RECTIME('2007.078 16:23:31.123456 +1')
Page 50
IMS 10
Transaction Manager
Page 26
IMS 10 2Q2007
[email protected] 26
Page 51
IMS 10 Transaction Manager
Overview
� SERIAL program support in IMSPlex
� Enterprise Workload Manager
� Enhanced log analysis utilities
� Transaction Level Statistics
� Enhanced Display of System parameters
� Fast path enhancements
� MSC enhancements
� Serviceability (BPE trace / ABEND Search & Notification / etc)
Page 52
TM Enhancements
� SERIAL program support with Shared Queues� Previously it required a customer solution to guarantee that SCHDTYPE=SERIAL programs were
scheduled serially within an IMSplex
� This function is now provided by the Resource Manager in IMS 10
� Automatically enabled when RM and Resource Structure are defined
� Enterprise Work Load Manager � IMS 10 is enhanced to support the Enterprise Workload Management (EWLM) function of z/OS
for transactions that are sent to OTMA from IMS TM Resource Adapter or WebSphere MQ bridge
� Log Transaction Analysis utility (DFSILTA0) and Sta tistical Analysis utility (DFSISTS0) have been rewritten � Support shared queues and MSC
� no log merging is required
� Easier to use
� Provide better performance
Page 27
IMS 10 2Q2007
[email protected] 27
Page 53
TM Enhancements
� Transaction Level Statistics� In IMS V8/V9, and still in IMS 10, IMS TM logs transaction
statistics (type ’07’ log record) for the whole program schedule� Optionally in IMS 10 these statistics can additionally be logged
at the transaction level for easier performance analysis or chargeback purposes�System Default specified in DFSDFxxx
�TRANSACT macro can specify (APPLCTN for BMP)�Dynamically activated/deactivated by UPDATE TRAN type-2
command
� Enhanced Display of System parameters� At startup, IMS displays system parameters defined by user
�Some can be wrong – correct values are taken from log later in restart
� IMS 10 displays values again once all modifiable values have been resolved
�Only shows selected values – just those that apply to this system
Page 54
TM Enhancements …
� Fast Path Enhancements in IMS 10�Maximum number of Fast Path Global buffers increased
from 64K to 4G
�DBFCONT0 no longer requires a single contiguous chunk of storage – but is broken down into multiple pieces
�UPDATE type-2 command extended to allow all areas of a DEDB to be restarted
�Ability to leave randomiser loaded when a DEDB is stopped
�Avoids storage fragmentation issues
�Enhanced commands for displaying and removing terminals from fast path (EMH) response mode
�Support for Non Recoverable DEDBs with SDEPs (through the IMS 10 service process)
Page 28
IMS 10 2Q2007
[email protected] 28
Page 55
TM Enhancements …
� MSC Bandwidth� MSC link performance is sometimes constrained by the MSC messaging protocols
(basically, “one message at a time”)
� IMS 10 introduces an optional technique – bandwidth mode - for increasing the number of messages/responses that are delivered together
�Reduces number of log check-writes
�Switched on/off with UPDATE or /UPD command
� MSC Dynamic Resource Definition support � Almost all attributes (including names) of physical links, logical links and MSNAMEs
can be changed with UPDATE type-2 command
� MSC VTAM Generic Resources support� Remote IMSs may use a generic resources node name for local IMS
Page 56
TM Enhancements …
� Serviceability Enhancements
�Abend search and notification
�Automatic notifications, via email or telephone text message, of IMS system failures
�Message contains URLs to help identify problem
�Enhanced system dumpsand shutdown trace
�BPE External Trace
�Writes trace tables to external storage -previously internal only
�CQS, IMS Connect, OM, RM, or SCI
Page 29
IMS 10 2Q2007
[email protected] 29
Page 61
Redbooks
� IMS Version 10 Implementation Guide – SG24-7526 �Latest draft of the redbook is available:http://www.redbooks.ibm.com/redpieces/abstracts/sg247526.html
Page 62
IMS 10 Summary
� With IMS 10, SPOCs become the operator interface of ch oice�New and enhanced type-2 commands for complete control of DBs,
transactions, applications, and MSC links
�Required for DRD, ACB Member Online Change, QUEUE commands, etc.
� Dynamic Resource Definition�Reduces IMSGEN to a handful of macros
�Provides an efficient, easy and less disruptive alternative to MODBLKS online change
� Online Change for ACBs is made quicker, less disrup tive and with less chance of failing due to queued transactions
� Addresses potential performance problems with RECON access, and with MSC
� Increases robustness of OTMA for working in very hi gh-stress environments
� Enables use of XQUERY against IMS DBs
These, and many more enhancements make IMS 10 the most These, and many more enhancements make IMS 10 the most exciting IMS release for many yearsexciting IMS release for many years
