How a CICS or VTAM Transaction connects to a View database with XMS?

Products

• View

Issue/Introduction

How Does a CICS or VTAM Transaction Connect to a View Database, Utilizing XMS and why SUBSYS XME0 appears to be used ?

Environment

Release : 14.0

Component : View

Cause

By default, the CICS service transaction, XME0 for release 14.0, must be changed with each new release of the product.

By default The XMS address space,  the subsystem ID  SUBSYS=XME0 

Resolution

CICS or VTAM transactions connect to a View database, via a cross-memory services (XMS) task, based on a match of the SUBSYS=... parameter defined for the transaction in the EBCXMCTR table.

A sample transaction would contain:

EBCXMTRN TYPE=SAR,TRANID=tranid,INDEX=high-level-name,TIMEOUT=sec,SUBSYS=subsysid,...

Correspondingly, the XMS task parameters would contain the same SUBSYS=subsysid value.

When the EBCXMCTR table is assembled, and there are no SUBSYS=xxxx fields in the transactions, then the default of SUBSYS=XME0 (for View/Deliver 14.0) would be used.

Similarly, if there is no SUBSYS=... parameter defined in the XMS task, then the default of SUBSYS=XME0 (for View/Deliver 14.0) would be used.