ims tm updates - ims ug may 2014 san ramon

®

What’s New in IMS TM

IMS User Group Meeting

© 2014 IBM Corporation

IMS User Group MeetingMay 1, 20134 – San Ramon

Jack [email protected]

Acknowledgements and DisclaimersAvailability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all

countries in which IBM operates.

The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They areprovided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance oradvice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in thispresentation, it is provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damagesarising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation isintended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering theterms and conditions of the applicable license agreement governing the use of IBM software.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they mayhave achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in thesematerials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specificsales, revenue growth or other results.

2

© Copyright IBM Corporation 2014. All rights reserved.

• U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.

– IBM, the IBM logo, ibm.com, InfoSphere, IMS, DataPower, DB2, and Optim are trademarks or registered trademarksof International Business Machines Corporation in the United States, other countries, or both. If these and other IBMtrademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), thesesymbols indicate 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” at www.ibm.com/legal/copytrade.shtml

– .NET is a trademark of Microsoft; SAP is a trademark of SAP.

– Other company, product, or service names may be trademarks or service marks of others.

Agenda

IMS TM Security Enhancements

IMS Open TM Access Enhancements

IMS TM Performance Enhancements

IMS TM ISC over TCP/IP

33

®

IMS TM Security Enhancements


With THANKS to IMS security expert – Richard Schneiderto IMS Connect expert – Carlos Alvarado

Password Phrases support

RACF password phrases (“passphrases”) can now optionally beused

– When signing on to IMS, and

– Within TM Resource Adapter messages to IMS Connect

Security checking

– Passphrase sent to RACF at authentication time

5

– Passphrase sent to RACF at authentication time

Benefit

– Passphrases are

• More robust

– 9 to 100 bytes

– Can contain mixed-case letters, numbers and special characters

• Easier to remember

IMS /SIGN command -- RACF password phrase support added

– /SIGN PASSPHRASE used when specifying a passphrase

• Must be 100 bytes passed to IMS

• IMS will remove leading/trailing blanks

• If < 9 bytes, IMS will pass it as a password to RACF

– /SIGN PASSPHRASEQ used when specifying a passphrase with single quotes

• Most appropriate for use when signing on from a terminal

Enhancements to IMS Existing Function - IMS V12 APAR PM77494

6

• Most appropriate for use when signing on from a terminal

• IMS will not remove leading/trailing blanks

When changing password phrases, must specify another password phrase(same for passwords – can only change to another 8-byte password)

Traditional password support with /SIGN ON <userid> <userpw>maintained

VTAM logon user data

– Enclose the user ID and password phrase with quotes required by LOGON, forexample:

LOGON APPLID(APPL1) DATA(‘USRT001 “this is my passphrase”’)

Command Examples:

Example 1:

Entry ET:

/SIGN PASSPHRASE IMSUS01 I give my wife 24 roses everyday.

7

Example 2:

Entry ET:

/SIGN PASSPHRASEQ IMSUS02 'this is my ''password'' now'

Password Phrase Enhancements to TMRA & ICON

IMS TM Resource Adapter (TMRA)

– Will use new functionality to build a message including password phrase and sendit to IMS Connect

IMS Connect

– Will be able to accept messages from IMS TM Resource Adapter that contain apassphrase

8

• Users will be able to change their password phrase in the application data

section of the message received from TMRA

– Format: ‘oldphrase’ ‘newphrase’ ‘newphrase’

– To preserve single quotes that are part of the passphrase, add another single quote

next to each

– Layout of TMRA message:

LLLL IRM OTMA LLZZApplication_Data

Enhancements to Existing Function – TMRA & ICON


OTMA headers always present for TMRA messages

28 bytes in length for TMRA messages IRM

9

Length of the entire message LLLL

Enhancements to Existing Function – TMRA & ICON


LLZZHWSPWCH 'THE NIGHT IS ''YOUNG''' 'TODAY IS A NEW DAY' 'TODAY IS A NEW DAY'

10

Password and passphrase change request eyecatcher

Old passphrase New passphrase x 2

IMS Connect password phrases support in IMS V12

Password phrases support in IMS Connect is currently only for IMS TMRAclients.

– PM77999: IMS Connect password phrases support for TMRA

– PM78001: IMS TM Resource Adapter (TMRA) password phrases support

• PM16303 for TMRA messages supporting 2-phase commit

Important changes in IMS Connect are:

11

Important changes in IMS Connect are:

– HWSJAVA0 user exit was enhanced:

• Support IRM architecture level 5.

• Look for the IRM extension containing a password phrase.

• Copy the password phrase and its length to the location pointed to byEXPREA_PHR_HLD in HWSEXPRM

– HWSPWCH0 Modified to support changing a RACF password phrase for IMSTMRA clients.

RACF Event Notification Facility (ENF) Support

Background

– IMS Connect V12 provided the option to cache verified RACF UserIDs (UIDs)along with a command to refresh them

IMS Connect V13: RACF ENF Support for Cached UserIDs (UID)

– Automatically refreshes cached UIDs by listening to RACF events (ENFsignals) indicating that a change has been made to a UID

IMS V13

12

signals) indicating that a change has been made to a UID

• RACF commands: CONNECT, REMOVE, and ALTUSER REVOKE

– NOTE: This function applies only when RACF UID caching has beenenabled in IMS Connect

Benefit

– Allows IMS Connect to listen for certain RACF events indicating that achange has been made to a specific UserID

• Avoids manual intervention

SECURITY Macro removed from System Definition

System Definition macro SECURITY is no longer used as part of the IMS systemgeneration process

Specify security settings through PROCLIB members

RCLASS parameter added to DFSPBxxx

– RCLASS also supported in DFSDCxxx

– DFSPBxxx RCLASS parameter value overrides DFSDCxxx if both specified

SECCNT parameter added to DFSDCxxx

IMS V13IMS V13

1313

Other Security settings continue to be specified in DFSPBxxx

– SECLVL parameter is replaced by RCF, TRN and SGN in DFSPBxxx

– TYPE parameter is replaced by ISIS in DFSPBxxx

Security preconditioning for IMS V11 and V12:

– IMS 11 - PM48203, PM72199 ; IMS 12 - PM48204, PM73558

Benefits

– Simplified system generation process

– Easier method to update security related settings

Security User Exits removed from Nucleus

User exits DFSCSGN0, DFSCTRN0 and DFSCTSE0 now linked separately, loadedfrom STEPLIB (if present) into 31-bit storage

New DFS1937I message indicates which user exits have been loaded

– Can be used in automation to ensure that exits are being used

DFSCSGN0 now called at IMS initialization

– Storage can be obtained and shared with the other exits

IMS V13

1414

Benefits

– Simplifies process to customize IMS with user exits

– Simplifies writing of user exit DFSCSGN0

– Reduces 24-bit private virtual storage usage

®

IMS OTMA Enhancements


With THANKS to IMS OTMA expert – Dave Cameron

OTMA Global Flood Control Enhancement

A new global flood control option that enforces the global flood limit

– Rejects new transaction input and protects IMS from storage exhaustion

• Versus just a warning message

IMS V13

16

Benefit

– Ability to address the global flood condition rather than just be warned

OTMA Global Flood Control Enhancement...

Background

– OTMA message flood detection and control support from previous releases

• Individual OTMA TMEMBER support

– Monitors growth of active INPUT messages per member (default of 5000)

• At 100% of threshold, new input messages from that member are rejected

17

• At 100% of threshold, new input messages from that member are rejected

• Warning at 80% of flood value and in 5% increments until relieved

• Global Flood Control

/STA TMEMBER ALL INPUT #### (default 8000)

– Monitors the total number of active input messages for all OTMA members

– DFS4388W to the IMS MTO and system console along with OTMA protocolmessages with a warning status to all of the OTMA clients

• At 100% of the global flood value

OTMA Global Flood Control Enhancement ...

Global flood control enhancements

– New defaults:

• OTMA global flood limit: 8,000 10,000

• Relief value: 6,400 5,000

• New DFS3428W warning message at 80% and 5% increments until relief

• Enhanced DFS4388W is issued when the limit is reached and the new

18

• Enhanced DFS4388W is issued when the limit is reached and the newsupport to reject input is not active

– Actions when global flood control has not been requested/activated

• Warning messages

– Enhancements to request global flood control (0-99999 new max)

• New meaning: /STA TMEMBER ALL INPUT ####

• New “global” OTMA Client descriptor: M DFSOTMA INPT=


/STA TMEMBER ALL INPUT ####

– Command enhancement for global message flood control

• IMS version 10 introduced the INPUT value

– Overrides the default of 5000 messages for an OTMA member instance

– The IMS 13 ALL parameter provides a global value for all members

• Default was changed from 8000 to 10000

19

• Default was changed from 8000 to 10000

• When the global value is reached

– WTO and MTO messages are issued

– Action message is sent to all OTMA members

– All of the new OTMA input transactions are rejected with NAK X’30’ reason X’02’

/DISPLAY OTMA enhancement

– New global message flood warning level display under the INPT column ofthe OTMA Server name

– New “SERVER+FLOOD” status under the user-status column


A special new client descriptor (optional)

– Using existing ‘M’ descriptor type in DFSYDTx member of IMS.PROCLIB.

M client-name keywordsWhere:

client-name is DFSOTMA

20

client-name is DFSOTMAkeywords are:

INPT= <VALID>DRU= <Ignored>T/O= <Ignored>MAXTP= <VALID>

M DFSOTMA INPT=22222

– New system client name for all the OTMA members, DFSOTMA, isintroduced to set the global flood limit via INPT parameter.

For example:

OTMA Global Flood Control Enhancement...

Global flood control enhancements ...

– What happens when the global flood control is activated

• Warning at 80% of limit – DFS3428W

• At 100% of limit: OTMA rejects all new input from any OTMA member– Sense code x’0030’, reason code x’0002’

– Sends protocol message with command type set to X’3C’

• With “unavailable for work” status instead of previous “warning” status

21

• With “unavailable for work” status instead of previous “warning” status

– New DFS3429E error message is sent to the system console and MTO

– /DISPLAY OTMA shows “SERVER+FLOOD” in user status

– Global flood relief occurs when unprocessed input drops to 50% of limit

– Enhanced message DFS0793I is sent to IMS MTO and system console

– OTMA member clients receive protocol messages reflecting a good status

Member flood control limit continues to be 9999

• OTMA rejects all new input from any OTMA member– Sense code x’0030’, reason code x’0001’

OTMA Global Flood Control Enhancement - Migration

Migration considerations

– Messages

• Enhancements to DFS4388W and DFS0793I messages– Possible changes to automation programs that deal with DFS4388W and

DFS0793I messages

• New messages DFS3428W and DFS3429E

– Changes to the default values

22

– Changes to the default values

• OTMA global flood limit: 8,000 10,000

• Relief value: 6,400 5,000

– /STA TMEMBER ALL INPUT ####

• In previous releases resulted in warning messages

• Now turns on global control and will reject new input– IMPACT if you change the value to be below what is currently queued

– Use of DFSOTMA descriptor reduces the total entries for OTMA clients ormembers to 254 (instead of 255)

OTMA Global Flood Control Enhancement – Migration ...

Migration considerations

– Pre-IMS 13:

• Changing the value with: /START TMEMBER ALL INPUT 200 command

– Does not trigger the flood status update in the /DIS OTMA output even if there aremore messages than the limit until a new OTMA transaction is entered

– New input continues to be accepted warning messages are issued

23

– IMS 13:

• Changing the value with: /START TMEMBER ALL INPUT 200 command

• Immediately takes effect

– If there are more messages waiting to be processed than the value

• DFS3429E THE TOTAL OTMA INPUT MESSAGES(TIB) HAVE REACHEDTHE GLOBAL LIMIT ZZZZ

• /DIS OTMA shows a status of SERVER+FLOOD

• New input is rejected


ACTION points (pre-IMS 13)

Member

Individual

(at 5% incr)

80% 85%-95% 100% ReliefDefault WTO 3C WTO 3C WTO 3C WTO 3C

Threshold MTO MTO MTO MTO

at 50%

24

Member

Level 5000 X X X X X X Xat 80%

Global Level

- All Members 8000 X X X X

Member level

– At 100% of the member threshold, messages are rejected until level is relieved at 50%

– /DIS TMEMBER shows a FLOOD condition at 100%

Global level

– At 100% of the global threshold, a warning is sent but messages continue to be accepted


ACTION points (IMS 13)

Member

Individual

(at 5% incr)

80% 85%-95% 100% ReliefDefault WTO 3C WTO 3C WTO 3C WTO 3C

Threshold MTO MTO MTO MTO

at 50%Member

Level 5000 X X X X X X X

25

Member level– At 100% of the member threshold, messages are rejected until level is relieved at 50%– /DIS TMEMBER shows a FLOOD condition at 100%

Global level– At 100% of the global threshold, a warning is sent but messages continue to be accepted

• this is the default– BUT: if a global flood limit has been specified in client descriptor or /START TMEMBER ALL INPUT

command, an error will be sent instead and new trans messages will be rejected.

Level 5000 X X X X X X X

Global level at 50%

-All Members 10000 X X X X X X X

®

IMS TM Performance Enhancements


With THANKS to IMS system expert – Tom Bridgesto IMS fastpath expert – Judy Tse

IMS Transaction Rate with Three Fast Path Data Entry Databases

27

Roadblocks, Limitations and TM related Solutions

28

XCF Message Rate Limitations

Observation:

– Initial IMS Connect/OTMA runs showed an upper limit 25,000 transaction persecond, which was far fewer than with SNA.

Analysis:

– OTMA table trace and IMS Connect recorder trace indicated that there was adelay occurring in the transfer of the XCF message.

29

delay occurring in the transfer of the XCF message.

XCF Message Rate Limitations…

Solution:

– XCF development was able to determine that code within XCF was limiting thenumber of message transfers per second to a given member of the XCF group.This was initially done to avoid having some XCF member dominate all theresources within a system, but with the ever-increasing processing capability ofthe System z hardware, a change was integrated into z/OS 2.1 to allow moremessages to flow.

z/OS 2.1

30

messages to flow.

• It used to be 16 messages per SRB per schedule before waiting for 10ms tobegin again. It is now 64 messages.

Results:

– The effect of this change was to immediately increase our throughput by morethan 100%, which then exposed additional challenges to be diagnosed andultimately resolved.

IMS Fast Path Syncpoint Processing

Problem:

– We hit a point around 70K where we could not get the transaction rate toincrease.

Analysis:

– For OTMA, the write of the syncpoint record under the IFP is followed by anIMS logger function called a “check write” (CHKW). A CHKW call waits for the

31

IMS logger function called a “check write” (CHKW). A CHKW call waits for thelogger to write the targeted log record to either the OLDS or the WADS loggerdata set. This wait holds up the dependent region until the syncpoint log recordis written. After the CHKW returns, the IFP issues the OTMA send-deallocateback to the inputting client, and only then is free to execute the nexttransaction. Thus, for OTMA, the capacity of each IFP is reduced because ofthis extra waiting and processing, which is absent for SNA.

IMS Fast Path Syncpoint Processing…

Solution:

– The logger write of the final syncpoint record for OTMA under the IFP is nowissued with a parameter that tells the logger to send a notification to Fast Pathcode in the control region when the log record has been physically written todisk. The dependent region is then able to immediately process the nexttransaction, without waiting for the log write to complete. A new ITASK thenprocesses the logger notification. The ITASK runs under a new Fast Path TCB– TCB type FP2 – to minimize any interference with the existing XFP Fast PathTCB processing.

IMS V13

32

TCB processing.

Results:

– Removing the CHKW call from the dependent region improved IFP transactioncapacity by about 30%, and allowed us to get past the 70K TPS limit that wehad previously been hitting.

®

ISC Over TCP/IP

IMS V13


With THANKS to IMS ISC expert – Khiet Nguyen

ISC Topologies

Current ISC VTAM connection between IMS and CICS continues to besupported

– Uses SNA protocols (LU6.1)

New ISC TCP/IP connection between IMS and CICS

– Requires CICS 5.1 (Oct. 3 announcement)

3434

– Requires CICS 5.1 (Oct. 3 announcement)

– IMS Connect provides the TCP/IP communication to CICS from IMS

– Uses new protocols

Both VTAM and TCP/IP topologies can co-exist

INPUT

INPUT

REPLY

ISC Topologies - ISC TCP/IP and ISC VTAM

IMSUSER

CICSIMSCONNECT TCP/IP

CICS

SCI

New connectiontype IMS

3535

REPLY

CICSCLIENT

VTAM

CICSCLIENT

IMSUSER

Existing connectiontype

INPUT

REPLY INPUT

REPLY

CICS IPIC (IP Interconnectivity) provides START / RETRIEVE(asynchronous processing) support

– When CICS is a front-end system:

• IMS response mode transactions are not supported

• IMS conversational transactions are not supported

Functionality

3636

• IMS conversational transactions are not supported

• CICS application program cannot use SEND/RECEIVE

– When IMS is a front-end system:

• Transaction support is the same for both ISC VTAM and ISC TCP/IP

• Transaction flow is always asynchronous

– No change to existing programs on either side of the connection

Functionality – Support and Restrictions

Functions And Transactions Existing in LU6.1 Supported in TCP/IP

CICS transaction – START/RETRIEVE Yes Yes

IMS non-response mode transaction Yes Yes

IMS recoverable transaction Yes Yes

IMS non-recoverable transaction Yes Yes

IMS message switch Yes Yes

IMS operator command Yes Yes

Dynamic terminal Yes Yes

3737

Dynamic terminal Yes Yes

Static terminal Yes Yes

CICS transaction – SEND(INVITE)/RECV Yes No

CICS transaction – SEND(LAST)/RECV Yes No

IMS response mode transaction (including FP) Yes No

IMS conversational mode transaction Yes No

Front-End Switch (FES) Yes No

Message Format Service (MFS) Yes No

IMSplex Terminal Management (STM) Yes No

VTAM Generic Resources (VGR) Yes No

Extended Recovery Facility (XRF) Yes No

Functionality …

Either side can initiate the request

IMS

12 3

456

INPUT INPUT Transaction

REPLY REPLY

IMSConnect

CICS

SCI TCP/IP

INPUT

REPLY

tranOR

tran

Msg SwitchIMS

End User Processtransaction

38

Initiating a CICS transaction from IMS using an ISC TCP/IP connection

REPLY

IMS

23

4 5REPLY REPLY

IMSConnect CICS

SCI TCP/IP

Initiating an IMS transaction from CICS using an ISC TCP/IP connection

CICSEnd UserProcess

transaction

Tx.

1Tx. (Start/Retrieve)INPUT

Transaction

6

REPLY

38

ISC TCP/IP Support: IMS Definitions

IMS terminal definitions

– Static terminals:

• TYPE, TERMINAL, VTAMPOOL and SUBPOOL macros in Stage 1 gen

– Continue to be required for static ISC terminals (VTAM or TCP/IP)

• New keyword: ISCTCPIP in DFSDCxxx

– Specifies that an ISC terminal is to use the TCP/IP support

3939

– Specifies that an ISC terminal is to use the TCP/IP support

– Addition, modification, deletion of the ISCTCPIP parameter requires a cold start

– Dynamic terminals (ETO):

• New Logon descriptor information in the DFSDSCMx or DFSDSCTyPROCLIB member

– DFSDSCTy overrides DFSDSCMx if the same descriptor is defined in both

• User descriptors are optional

– Default user descriptor of DFSUSER will be used if there is no user descriptorbeing defined.

ISC TCP/IP Support: IMS Definitions…

Static terminals: DFSDCxxx

– New keyword ISCTCPIP=(nodename, imsconnect_name)

– Only used for static ISC TCP/IP terminal definitions

• Nodename is a static LU6.1 parallel terminal defined in the stage1 sysgen

• Imsconnect_name is the name of the local IMS Connect in the IMSplex

4040

– Example:

DFSDCxxx:

ISCTCPIP=(CICSA1,ICON1)

Where CICSA1 is defined in the stage1 definition as a UNITYPE=LUTYPE6:

Stage 1 sysgen:

TYPE UNITYPE=LUTYPE6

TERMINAL NAME=CICSA1,SESSION=3…VTAMPOOL

SUBPOOL NAME=SSN1,MSGDEL=SYSINFO

NAME SSNA1,COMPT=2,ICOMPT=1


Static terminals …

– System definition macros have not been changed

• TYPE UNITYPE=LUTYPE6– Existing keywords applicable to ISC TCP/IP: EDIT and OPTIONS parameters

• TERMINAL NAME=– Existing: COMPTn, EDIT=, FPBUF=, MSGDEL, OUTBUF, SEGSIZE, SESSION,

OPTIONS: [AUTOSIGN|NOAUTOSIGN, FORCRESP|NORESP|TRANRESP,

NOMTOMSG|MTOMSG, NOPNDST|OPNDST]

4141

NOMTOMSG|MTOMSG, NOPNDST|OPNDST]

• VTAMPOOL statement for parallel session support

• One or more SUBPOOL macros– Optionally, one or more NAME macros

TYPE UNITYPE=LUTYPE6TERMINAL NAME=CICSA1,MSGDEL=SYSINFO,EDIT=(NO,NO), X

SESSION=3,OPTIONS=NOMTOMSG,COMPT1=(SINGLE1,VLVB), XCOMPT2=(SINGLE2,VLVB), COMPT3=MULT1 X

VTAMPOOLSUBPOOL NAME=SSN1,MSGDEL=SYSINFO

NAME SSNA1,COMPT=2,ICOMPT=1SUBPOOL NAME=SSN2

NAME SSNA2SUBPOOL NAME=SSN3

NAME SSNA3


Dynamic (ETO) Terminals: DFSDSCTx

– LOGON descriptor specifications

• Define ISCTCPIP value for UNITYPE= keyword

• Add keyword LCLICON= imsconnect_name in the IMSplex

– Example:

L LUTYPE61 UNITYPE=ISCTCPIP LCLICON=ICON1

4242

L LUTYPE61 UNITYPE=ISCTCPIP LCLICON=ICON1

• Other existing descriptor parameters that continue to apply:

– COMPTn, EDIT, OUTBUF, SEGSIZE,

– OPTIONS: [FORCRESP|NORESP|TRANRESP, NOMTOMSG|MTOMSG,

NOPNDST|OPNDST]

– USER descriptors

• Optional – defaults to DFSUSER

ISC TCP/IP Support: CSL for IMS – IMS Connect

The Common Service Layer (CSL) provides the Structured CallInterface (SCI) for communications

• Each IMS and its local ISC-routing IMS Connect system must be part of thesame IMSplex– IMSPLEX= plexname parameter in the Common Layer Section of the DFSDFxxx

of IMS PROCLIB

– Must match the IMSPLEX parameter in IMS Connect

4343

• The Operations Manager (OM) provides type-2 command support

IMSIMS Connect

HWSCFGxx

ISC()IMSPLEX=(MEMBER=lcliconname,

TMEMBER=IMSplexname)...

DFSDFxxx

IMSPLEX =IMSplexname...

SCI

Static:ISCTCPIP=(node,lcliconname)

Dynamic/ETOLogon descriptor:

L descname UNITYPE=ISCTCPIPLCLICON=lcliconname

OR

ISC TCP/IP Support: IMS Connect Definitions

IMS Connect’s HWSCFGxx configuration member

– New RMTCICS statement (for send sockets)

– New ISC statement (for receive sockets)

– New CICSPORT parameter in TCPIP statement (for receive sockets)

4444

ISC TCP/IP Support: IMS Connect Definitions …

HWSCFGxx …

– New RMTCICS statement (CICS partner)

45

ÊÊ¬¬RMTCICS¬(¬ID=stmt identifier,¬¬HOSTNAME=hostname,¬¬PORT=portid,¬¬¬¬¬¬¬¬¬¬¬¬¬¬Ê

Ê¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬)¬¬¬¬¬¬¬¬¬¬ÊÍ ~ 0 ¬¬¬¬¬® •¬RESVSOC=¬¬¬¬¬¬¬¬¬¬,¬¯

45

HWSCFGxx …

– New ISC statement

ÊÊ¬¬ISC¬(¬ID=isc_id,¬¬NODE=nodename,¬¬LCLIMS=lclimsid,¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬Ê

Ê¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬Ê


46

Ê¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬Ê•¬IMSPLEX=(¬MEMBER=mbrname,¬¬TMEMBER=tmbrname¬),¬¯

46

Ê¬¬¬¬RMTCICS=rmtcics,¬CICSPORT=portid,¬CICSAPPL=applid, ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬)¬ÊÍ•¬CICSNETID=networkid¬¯

• IMSPLEX

– Defines the SCI information for communicating with the local IMS

• RMTCICS

– Defines the CICS information

HWSCFGxx configuration member

– New CICSPORT parameter in the TCPIP statement

ÊÊ¬¬TCPIP(¬HOSTNAME=tcpipjobname,¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬Ê~¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬®


47

~¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬®Ê¬¬¬PORT=(¬ID=portid,KEEPAV=keepalivevalue,EDIT=editexitname¬),¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬Ê

~¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬®Ê¬¬¬CICSPORT=(¬ID=portid,KEEPAV=keepalivevalue¬),¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ

47

HWSCFGXX Configuration sample

TCPIP=(HOSTNAME=TCPIP,PORTID(9996,9997,9998,9999),RACFID=GOFISHIN,MAXSOC=5000,CICSPORT=(ID=9991),CICSPORT=(ID=9992),CICSPORT=(ID=9993),CICSPORT=(ID=9994),CICSPORT=(ID=9995),…)


4848

RMTCICS(ID=CICS1,PORT=8891,

HOSTNAME=HOSTB.COM,RESVSOC=10)

ISC(ID=ISC1,NODE=CICSA1,LCLIMS=IMS1,CICSPORT=9991,RMTCICS=CICS1,CICSAPPL=CICSA1,CICSNETID=CICSNET,

IMSPLEX=(MEMBER=ICON1,TMEMBER=PLEX1))

ISC TCP/IP Support: CICS

CICS: leverages existing IPIC definitions

– TCPIPSERVICE statement

TCPIPSERVICE (name of service, e.g TS1) TCPIPSERVICE (TS1)

PORT (port number to listen on) PORT (8891)

PROTOCOL (IPIC) PROTOCOL(IPIC)

– IPCONN statements for both session and APPLID levels

Example:

49

IPCONN(name of this definition

e.g. for IMS: IMSsubpoolName)

APPLID(= IPCONNname e.g., IMSubpoolName )

HOST(targetTCPIP )

PORT(target port)

TCPIPSERVICE(associated service)

SENDCOUNT ()

RECEIVECOUNT ()

AUTOCONNECT()

49

– IPCONN statements for both session and APPLID levels

NOTE: For a complete set of parameters, review the CICS documentation

IPCONN(SSN1)

APPLID(SSN1)

HOST(HOSTA.COM)

PORT(9991)

TCPIPSERVICE(TS1)

SENDCOUNT (1)

RECEIVECOUNT (1)

AUTOCONNECT (Y)

ISC TCP/IP Support CICS…

Takes advantage of existing CICS IPIC message formats and support

– 2 socket connections per parallel session

• 1 for send and 1 for receive on each side

• From IMS to CICS:

50

• From IMS to CICS:

– IMS Connect uses its SEND socket to send a message to CICS

– CICS uses it RECEIVE socket to receive the message and uses its definitions toroute the message to the CICS destination

• From CICS to IMS:

– CICS uses its SEND socket to send a message to IMS Connect

– IMS Connect uses it RECEIVE socket to receive the message and uses itsdefinition to route the message to the IMS destination

IMS-CICS ISC TCP/IP Communications

IMS1 CICS1

Parallel session 1w/ Security context 1

TERMINALNAME=CICSA1

SUBPOOLNAME=SSN1

APPLID=APPL8

TCPIPSERVICE(TS1)PORT(8891)PROTOCOL(IPIC)

ICON1

TCPIP…CICSPORT(9991)

RMTCICS(CICS1)HOST(hostb.com)PORT(8891)USERID(userid)APPL(applname) IPCONN(SSN1)

APPLID(SSN1)HOST(hosta.com)

hostb.comhosta.com

APPLID=CICSA1

ISCTCPIP(CICSA1,ICON1)

VTAMPOOL

TYPE UNITYPE=LUTYPE6

TCP/IPSCI

5151

NAME=SSN1

SUBPOOLNAME=SSN2

Parallel session 2w/ Security context 2

ISC(ISC1)NODE(CICSA1)RMTCICS(CICS1)CICSPORT(9991)CICSAPPL(CICSA1)LCLIMS=IMS1

HOST(hosta.com)PORT(9991)TCPIPSERVICE(TS1)AUTOCONN (Y)

IPCONN(SSN2)APPLID(SSN2)HOST(hosta.com)PORT(9991)TCPIPSERVICE(TS1)AUTOCONN (Y)

Initiate session from IMS : /OPN NODE CICSA1 USER SSN1

OR

Initiate session from CICS: F CICSA1, CEMT S IP (SSN1) ACQ

Message Flow Example: 1 IMS and 1 CICS

hosta.com

hostb.com

ICON1

CICS1

PORT

8891PORT(8891)PROTOCOL(IPIC)

TCPIPSERVICE(TS1)

HOST(hostb.com)

PORT(8891)

RMTCICS(CICS1)

HOST(hosta.com) PORT(9991)SENDCOUNT

IPCONN(SP1)

TCPIPSERVICE(TS1)RECEIVECOUNT

APPLID(SP1)

ISC(ISC1)SP1

/OPN NODE CICSA1 USER SP1



APPLID=CICSA1ISCTCPIP(CICSA1,ICON1)

IMS1

5252

PORT(A)

PORT(D)

PORT(A) PORT

9991

RECEIVECOUNT

LCLIMS (IMS1)

ISC(ISC1)SP1

SP2

SP3


IPCONN(SP2)


APPLID(SP2)


IPCONN(SP3)


APPLID(SP3)

IMS1CICSPORT(9991)

CICSAPPL(CICSA1)RMTCICS(CICS1)

PORT(A)

Message Flow Example: Multiple IMS’s and 1 CICS

hosta.com hostb.com

ICON1 CICS1

PORT

8891

PORT(8891)PROTOCOL(IPIC)

TCPIPSERVICE(TS1)


IPCONN(SP1)


APPLID(SP1)

ISC(ISC1)

IMS1SP1SP2

HOST(hostb.com)

PORT(8891)

RMTCICS(CICS1)

PORT

SP1, SP2

SP3, SP4

5353

PORT(A)

PORT(A)

PORT9992RMTCICS(CICS1)

ISC(ISC2)

RECEIVECOUNTRMTCICS(CICS1)SP2

IMS2SP3SP4


IPCONN(SP3)


APPLID(SP4)

CICSPORT(9992)

CICSPORT(9991)

PORT9991

LCLIMS(IMS1) PORT(9991)HOST(hosta.com)

IPCONN(SP2)

APPLID(SP2)

,,,

PORT(9992)HOST(hosta.com)

IPCONN(SP4)

APPLID(SP4)

,,,

LCLIMS(IMS2)

Message Flow Example: 1 IMS and multiple CICS’s

hosta.com

hostb.com

ICON1

CICS2 APPLID=CICSB1

PORT

PORT

8891PORT(8891)PROTOCOL(IPIC)

TCPIPSERVICE(TSB)

HOST(hostb.com)PORT(8891)

RMTCICS(CICS2)

HOST(hosta.com) PORT(9991)

IPCONN(SP1)

TCPIPSERVICE(TSB)

APPLID(SP1)

ISC(ISC2)

IPCONN(SP2)APPLID(SP2)

/OPN NODE CICSB1 USER SP1

/OPN NODE CICSB1 USER SP2

ISCTCPIP(CICSB1,ICON1)

ISCTCPIP(CICSC1,ICON1)

5454

PORT(A)

PORT(D)

PORT(A)PORT9991

PORT8893


TCPIPSERVICE(TSC)

HOST(hostc.com)PORT(8893)RMTCICS(CICS3)


IPCONN(SP3)

TCPIPSERVICE(TSC)

APPLID(SP3)

RMTCICS(CICS2)

ISC(ISC2)

RMTCICS(CICS3)

ISC(ISC3)

PORT9993

PORT(9991)

PORT(9993)

hostc.com

CICS3 APPLID=CICSC1

IMS1SP1SP2SP3SP4

HOST(hosta.com) PORT(9991)TCPIPSERVICE(TSB)

APPLID(SP2)


IPCONN(SP4)

TCPIPSERVICE(TSC)

APPLID(SP4)

/OPN NODE CICSC1 USER SP3

/OPN NODE CICSC1 USER SP4

CICSAPPL(CICSB1)

CICSAPPL(CICSC1)

PORT(A)

Message Flow Example: Multiple IMS and Multiple CICS

hosta.com

hostb.com

ICON1

CICS1

PORT9991

PORT

8891


TCPIPSERVICE(TSB)

HOST(hostb.com)PORT(8891)

RMTCICS(CICS1)HOST(hosta.com) PORT(9991)

IPCONN(SP1)

TCPIPSERVICE(TSB)

APPLID(SP1)

RMTCICS(CICS1)

ISC(ISC1)

PORT(9991)

HOST(hosta.com)PORT(9992)

IPCONN(SP3(APPLID(SP3)

IMS1SP1SP2

IMS2


IPCONN(SP2)

TCPIPSERVICE(TSB)

APPLID(SP2)

LCLIMS(IMS1)

5555

PORT(A)

PORT(D)

PORT8892

RMTCICS(CICS1)

ISC(ISC2)

HOST(hostc.com)PORT(8892)RMTCICS(CICS2)

RMTCICS(CICS2)LCLIMS(IMS3)

ISC(ISC3)PORT9993

PORT(9992)PORT

9992

TCPIPSERVICE(TSB)

PORT(9993)

IMS2SP3SP4

IMS3SP5SP6


IPCONN(SP4)

TCPIPSERVICE(TSB)

(APPLID(SP4)


TCPIPSERVICE(TSC)


IPCONN(SP5)

TCPIPSERVICE(TSC)

APPLID(SP5)

hostc.comCICS2


IPCONN(SP6)

TCPIPSERVICE(TSC)

APPLID(SP6)

LCLIMS(IMS1)

LCLIMS(IMS2)

ims tm updates - ims ug may 2014 san ramon

Technology

ims ims

terminal ims

ims tm ims user group

ims sign command

ibm products

password phrase enhancements

ibm logo

use of ibm software