ims version 8 sysplex terminal management -...

IMS Version 8 Sysplex Terminal Management

Bill StillwellIMS Advanced Technical Support

Dallas Systems Center

IBM Corporation 2003 1

AbstractAbstract

This presentation looks atSysplex Terminal Management- IMS's exploitation of the

Resource Management infrastructure provided by Version 8 when using

Shared Queues with the Common Service Layer (CSL), including the

Resource Manager, and a Resource Structure.

2

Applies to VTAM terminal and user resourcesNodes, lterms, users, userids, etc.BTAM and OTMA resources not supported

Addresses complexities of managing an IMSplex

RequiresShared queuesCSL with the Resource ManagerResource Structure

Resource names and status saved in resource structureShared by all IMSs in IMSplex

Sysplex Terminal ManagementSysplex Terminal Management

3

Each IMS puts messages on a destination queue in a shared queue list structure in the CF.

Once on the structure, that IMS, or any other IMS, can retrieve it and process it.

Deliver messageSchedule transaction

Destination queue names and status become critical

Who delivers message for LTERM1? Who receives it? NodeA or NodeB?How should PRSNL be queued? Transaction? Lterm?

Transactions

Lterms

Msnames

CouplingFacility

Shared Message QueuesShared Message Queues

SharedData

IMS1 IMS2

PRSNL

NODEB

LTERM1

NODEA

PRSNL

LTERM1

NODEB

NODEANAME LTERM1

NODEBNAME PRSNL

NODEBNAME LTERM1

TRANSACT PRSNL 4

RM InfrastructureRM Infrastructure

ResourceList Structure

LOGRList Structures

SMQList Structures

OSAMCache Structure

VSAMCache Structure

Shared VSOCache Structures

IRLMLock Structure

VGRList Structure

MNPSList Structure

OperationsManager

(OM)

SCI

StructuredCall

Interface

SCI

SCICommunications

IMSControlRegion

SCI

ResourceManager

(RM)

SCI

SCI

CommonQueueServer(CQS)

SPOC

End Users

MTO

Automation

CSL address spacesCF resource structure

STM

Network

IMS Ctl Ctr

5

Resource StructureResource StructureResource structure implemented as a list structure in the Coupling Facility

Contains global resource information (e.g., type, name, owner, status) for uniquely named resources

Types of resources

Transactions, lterms, msnames, APPC descriptor names

Nodes, users, userids

Global processes

IMSplex local and global information

STM addressesthese resources

6

List Entry

LIST ENTRY

List Entry Controls LISTNUM ENTRYID(LEID) ENTRYKEY VERSION

Adjunct Area Owner Recoverable Status 1 Reserved

Data Entry 0 or more data elements Recoverable Status 2

List Headers Resource

List Structure

Transactions

Lterms

Msnames

Users

Nodes

Userids

Processes

.....

Resource Structure ...Resource Structure ...

Type+Name

Owner

Status

ENTRYKEY 02LTERM1

.... ....

OWNER IMS1

DATA Rcvbl Status

Example

7

Objectives

Enforce global resource type consistency Prevent naming inconsistencies between IMSs

PRSNL cannot be defined as transaction on IMS1 and as Lterm on IMS2

Enforce global resource name uniquenessPrevent multiple logons / signons within the IMSplex

Lterm1 cannot be active on both IMS1 and IMS2

Enable global terminal and user resource status recovery Resume significant status on another IMS after failure

Conversation, fast path response, STSN sequence numbersCommand status (e.g., stopped, assigned, ...)

Reduce need for IMS-managed VGR affinity

Sysplex Terminal Management ...Sysplex Terminal Management ...

8

STM prevents the same resource name from being used for different message destination resource types

Applies to message destinations Transaction names - static and CPI-CLterm names - static and dynamicMsnamesAPPC descriptor (lterm) names

Does not apply toNodes, users, useridsThese are not message queue "destinations"

For example, OK to have node name and lterm name the same

Resource Type ConsistencyResource Type Consistency

These are all Shared Queue destination

names.!

9

IMS1 IMS2

TRANQ

LTERMQ

APPLCTN ...TRANSACT PRSNL

TERMINAL NODEBNAME PRSNL

Shared QueueStructure

?PRSNL Data

LOGON IMS2

Consistency ...Consistency ...

ResourceStructure

PRSNL

PRSNL

CF

TRANMSNAMELTERMAPPC DESCIMS1 will create PRSNL

Transaction entry inResource Structure during IMS initialization.

LTERM PRSNL cannot log on to IMS2 since it is already defined asa transaction on theresource structure.

Rejected

LOGON IMS1

PRSNL Data

PRSNL Data

NODEA NODEB

10

Resource Name UniquenessResource Name UniquenessSTM prevents some resource types from being active in more than one IMS

These resources are owned by one IMS while activeOwnership maintained in structure

Applies toSingle session VTAM Nodes, static and ETO Users, LtermsUserids

Only if single signon requested (SGN ¬= M)

Does not apply toTransactionsParallel session VTAM nodesMsnamesAPPC descriptor namesUserids if SGN=M

ENTRYKEY 02LTERM1

.... ....

OWNER IMS1

DATA Rcvbl Status

11

IMS1 IMS2

TRANQ

LTERMQ

TERMINAL NODEBNAME PRSNL

PRSNL Data

Shared Queue Structure

LOGON IMS2

Uniqueness ...Uniqueness ...

ResourceStructure

PRSNL IMS1

CF

TRANMSNAMELTERMAPPC DESC

IMS1 will create PRSNLlogical terminal entry inResource Structure. IMS1 is the owner.

NODEB/PRSNL cannot log on to IMS2 since it is owned by IMS1.

Rejected

TERMINAL NODEANAME PRSNL

LOGON IMS1

NODEA NODEB

NodeB:LOGON IMS2Logon rejected

ENTRYKEY 02PRSNL

.... ....OWNER IMS1

DATA Rcvbl Status

NodeA:LOGON IMS1

1 2

12

Applies to ...NodesUsersLterms

Recoverable resource status Kept the resource entry

No recoverable status for ...TransactionsMsnamesAPPC descriptorsUserids

Resource Status RecoveryResource Status Recovery

LIST ENTRY

List Entry Controls LISTNUM ENTRYID(LEID) ENTRYKEY VERSION

Adjunct Area Owner Recoverable Status 1 Reserved

Data Entry 0 or more data elements Recoverable Status 2

ResourceList Structure

Transactions

Lterms

Msnames

Users

Nodes

Userids

Processes

.....

13

Significant StatusSignificant StatusSignificant status

Recoverable terminal or user status that prevents deletion of resource entry at signoff, logoff, or IMS restart

Command significant statusTerminal or user status normally set via commandAlways maintained globally if RM structure is used

End-user significant statusWork-related terminal or user statusMaintained locally, globally, or not at all depending on Status Recovery Mode

Non-significant statusAny other terminal or user status

14

Significant Status ...Significant Status ...Command significant status

VTAM terminal or user status normally set by command/TEST MFS (node, user)/STOP (node, user, lterm)/EXCLUSIVE (node, user)/TRACE (node)/CHANGE USER AUTOLOGON SAVE (user)/ASSIGN LTERM|USER xxx TO yyy SAVE (lterm)

Command significant status always kept globally if ...Resource structure exists

ExampleFrom IMS1: /STOP NODE NODEANODEA status is STOPPED in resource structure; cannot log on to any IMS

15

Significant Status ...Significant Status ...End-user (e-u) significant status (nodes and users)

Work-related statusConversation (active and held )Fast path response modeSTSN sequence numbers (last input and output )

May be kept globally or locallyDepends on Status Recovery Mode (SRM)

If a resource has significant status at session termination or ETO user signoff

Resource entry will not be deleted from resource structureUnless SRM=NONE or RCVYxxxx=NO (status recovery not wanted)

If resource not deletedRecoverable status will be recovered at next logon, signon, or restart by any IMS in IMSplex

16

Status recovery mode (SRM) applies to e-u statusDefines scope of end-user status recovery

Command significant status always globalGLOBAL

Recoverable status kept in RM structureAvailable from any IMS in IMSplex

Status restored at next logon/signon to any IMSCopied to local control blocks when resource becomes active

LOCALRecoverable status kept in local control blocks and log records

System default if not using RM, resource structure, and SQStatus restored at next logon/signon only if logging on to same IMS

NONERecoverable status kept locally only while resource activeDeleted at signoff, logoff, or IMS restart

Default set in DFSDCxxx (SRMDEF=xxx)Can be overridden at logon/signon time

Status Recovery ModeStatus Recovery Mode

17

End-user Status RecoverabilityEnd-user Status RecoverabilityWhen SRM is Global or Local

Recoverability can be set for each type of end-user status

Parameter in DFSDCxxxConversation

RCVYCONV=YES|NOSTSN

RCVYSTSN=YES|NOFast Path

RCVYFP=YES|NO

If NOEnd-user status not kept in resource structureEnd-user status discarded locally at session termination or IMS restartBut ... command status is always recoverable

18

Examples of Status RecoveryExamples of Status Recovery

Status Recovery ModeStatus Recovery ModeGLOBAL

LOCALNONE

If time permits

19

Status RecoveryStatus Recovery

VTAM (Generic Resources)

CF

ResourceStructure

VGRStructure

Shared QueuesStructure

SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS2

SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

Two IMSs in z/OS 1.2 IMSplex (IMS1 and IMS2)[note: z/OS 1.2 support VTAM GR session level affinity]

Both have NodeA and Lterm1 definedVTAM generic resources enabled (GRSNAME=IMSX)

NODEALTERM1

NODEALTERM1

NODEA

20

Status Recovery - SRM=GLOBALStatus Recovery - SRM=GLOBAL


CF

ResourceStructure

VGRStructure


SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS2

SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

LOGON IMSX User logs on using generic logon IMSXVTAM routes logon to IMS1; sets VGR affinity to IMS1IMS1 sets VGR affinity management to VTAMIMS1 sets SRM=GLOBAL; RCVYCONV=YESResource entries created: node, lterm, user Owner=IMS1, SRM=GLOBAL

NODEALTERM1

NODEALTERM1

Owner=IMS1SRM=GLOBAL

VGR affinityset to IMS1;VTAM-managed

SRM=GLOBAL

21

Status Recovery - SRM=GLOBAL ...Status Recovery - SRM=GLOBAL ...


ResourceStructure

VGRStructure


SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS2

SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

CONV TRAN

User enters conversational transactionIMS1 creates local CCBIMS1 queues SPA+MSG on SQIMS1 updates user resource with Conversational status

NODEALTERM1

NODEALTERM1

SRM=GLOBAL

RecoverableMessage

Recoverable Status

Recoverable Status


CF


22



CF

ResourceStructure

VGRStructure


SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS2

SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

IMS1 fails; IMS2 queries RM for IMS1 entriesIMS2 does not delete resource entry (in conversation)IMS2 clears ownership (SRM=GLOBAL)VTAM deletes VGR affinitySPA+MSG still on SQ

NODEALTERM1

NODEALTERM1

Ownership clearedSRM=GLOBAL

VGR affinitydeleted

SRM=GLOBAL

RecoverableMessage

Recoverable Status

Recoverable Status

Rats!

23



CF

ResourceStructure

VGRStructure


SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS2

SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

LOGON IMSX User logs on using generic logon IMSXVTAM routes logon to IMS2; sets VGR affinity to IMS2IMS2 sets ownership to IMS2IMS2 recovers conversation from Resource Structureand Shared Queue Structure

NODEALTERM1

NODEALTERM1


SRM=GLOBAL

RecoverableMessage

Recoverable Status

Recoverable Status

Recoverable Status


Whew

24



CF

ResourceStructure

VGRStructure


SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

IMS1 restarts; discovers recoverable status for SRM=GLOBAL resourceIMS1 deletes local recoverable status

NODEALTERM1

NODEALTERM1


VGR affinityset to IMS2

SRM=GLOBAL

RecoverableMessage

Recoverable Status

Recoverable Status

Recoverable Status

SCI

CQS

OM

SCI

RMSCI

SCISCI

SCI

IMS2

IMSCTL

SCI

25

Status Recovery - SRM=LOCALStatus Recovery - SRM=LOCAL


CF

ResourceStructure

VGRStructure Shared Queues

Structure

LOGON IMSX

NODEALTERM1

NODEALTERM1

Owner=IMS1SRM=LOCAL

VGR affinityset to IMS1;IMS-managed

SRM=LOCAL User logs on using generic logon IMSXVTAM routes logon to IMS1; sets VGR affinity to IMS1IMS1 sets VGR affinity management to IMSIMS1 sets SRM=LOCALResource entries created: Owner=IMS1, SRM=LOCAL

SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

SCI

CQS

OM

SCI

RMSCI

SCISCI

SCI

IMS2

IMSCTL

SCI

26

Status Recovery - SRM=LOCAL ...Status Recovery - SRM=LOCAL ...

CF

ResourceStructure


Structure

CONV TRAN

NODEALTERM1

NODEALTERM1

Owner=IMS1SRM=LOCAL

SRM=LOCAL

RecoverableMessage

User enters conversational transactionIMS1 creates local CCBIMS1 queues SPA+MSG on SQIMS1 does not update user resource with Conversational status (status maintained locally)

Recoverable Status

SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

SCI

CQS

OM

SCI

RMSCI

SCISCI

SCI

IMS2

IMSCTL

SCI



27



CF

ResourceStructure


Structure

NODEALTERM1

NODEALTERM1

SRM=LOCAL

RecoverableMessage

IMS1 fails; IMS2 queries structure for IMS1 entriesIMS2 does not delete resource entry (SRM=LOCAL)IMS2 does not clear ownership (SRM=LOCAL)VTAM does not delete VGR affinity

NotAgain?

Owner=IMS1SRM=LOCAL

SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

SCI

CQS

OM

SCI

RMSCI

SCISCI

SCI

IMS2

IMSCTL

SCI

Recoverable Status


28



CF

ResourceStructure


Structure

LOGON IMSX

NODEALTERM1

NODEALTERM1

SRM=LOCAL

RecoverableMessage

End user logs on using generic logon IMSXVGR affinity still set to IMS1Logon fails; user must wait for IMS1 to restart

Owner=IMS1SRM=LOCAL

Recoverable Status

SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

SCI

CQS

OM

SCI

RMSCI

SCISCI

SCI

IMS2

IMSCTL

SCI


29


CF

ResourceStructure


Structure

LOGON IMS2

NODEALTERM1

NODEALTERM1

SRM=LOCAL

RecoverableMessage

Recoverable Status

If end user logs on directly to IMS2IMS2 checks resource entry for NODEALogon rejected (NODEA owned by IMS1)User must wait for IMS1 to restartLogon exit can "steal" node (status is not recoverable)

Owner=IMS1SRM=LOCAL


SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

SCI

CQS

OM

SCI

RMSCI

SCISCI

SCI

IMS2

IMSCTL

SCI


30


CF

ResourceStructure


Structure

LOGON IMS2

NODEALTERM1

NODEALTERM1


SRM=LOCAL

RecoverableMessage

Recoverable Status

If IMS2 Logon Exit steals node, logon accepted, status is non-recoverableIMS1 will delete status when it is restarted (IMS1 no longer "owner")

Owner=IMS2SRM=LOCAL


SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

SCI

CQS

OM

SCI

RMSCI

SCISCI

SCI

IMS2

IMSCTL

SCI

31

Status Recovery - SRM=NONEStatus Recovery - SRM=NONE


CF

ResourceStructure

VGRStructure


NODEALTERM1

NODEALTERM1


SRM=NONE

RecoverableMessage

Non-RecoverableStatus

Status is kept in local control blocks while user is activeIf session terminates, or IMS terminates, status is discarded

Owner=IMS1SRM=NONE

SCI

CQS

OM

SCI

IMSCTL

SCI

RMSCI

SCISCI

SCI

IMS1

SCI

CQS

OM

SCI

RMSCI

SCISCI

SCI

IMS2

IMSCTL

SCI

32

Sysplex terminal management is an IMS function which exploits the CSL infrastructure to provide ...

Resource type consistency Prevent naming inconsistencies between IMSs

Resource name uniquenessPrevent multiple logons / signons within the IMSplex

Terminal and user resource status recovery across IMSplexResume end-user and command significant status on another IMS after failure

STM requiresCSL with resource structureShared queues

Sysplex Terminal Management Sysplex Terminal Management

33

ims version 8 sysplex terminal management -...

Documents