sys.zOS.IMSSubsystem

IMS subsystems consist of several specialized address spaces running on a z/OS® system. Each provide different IMS services for the subsystem. Each subsystem has one address space known as the Control region which regulates the IMS subsystem as a whole. The subsystem name is also known to all address spaces in the subsystem as the IMSID.

Attributes

CDM attribute Value Example
(Subsystem) SubsystemName The 1-4 character name of the IMS subsystem. IMN3
(Subsystem) VersionString The version and release of the IMS control region 15.1
(Subsystem) CommandPrefixName A prefix used by support personnel to direct commands to the IMS subsystem. It is often the same as the IMSID. IMN3
(Subsystem) ControllingAddressSpace The Jobname of the Control region. This is needed to identify the address space to support personnel. IMN1CTL
IMSSubsysType

There are three types of IMS subsystem and this is reflected by the type of Control region, they are:

v DCCTL has only the Transaction Manager component and provides access to the IMS message queues for IMS applications.

v DBCTL has only the Database Manager component and provides IMS database functions.

v DB/DC provides Transaction Managemer and Database Manager functions for large application systems.

DCCTL DBCTL DB/DC
IRLMGroupName The XCF group name used by all CQS address spaces that share the same set of XCF structures. IMN0IRM
CQSGroupName The XCF group name used by all CQS address spaces that share the same set of XCF structures. All CQS group names have the prefix CQS. CQSIMN3
IMSPlexGroupName An IMSPLEX group name represents group of IMS components (subsystems) that share either data and/or message queues. All IMSPLEX members (for example, OM, RM, IMS, CQS) that are in the same IMSPLEX sharing group that share either databases or message queues must specify the same identifier. CSLIMN0
TransactionsChecksum Checksum for all transactions defined to the IMS.  
ProgramsChecksum Checksum for all programs defined to the IMS.  
DatabasesChecksum Checksum for all databases defined to the IMS.  

Requirements for discovery

  • IMS Subsystem book has all attributes and all relationships except to AddressSpaces.
  • ZOSTASK book has naming rules and relationships to AddressSpaces.
  • Filtering enabled (which is the default). Note that following Attribute level filters are disabled by default because they can be large at some sites. The customer needs to consciously choose to discover these: Transactions, Programs.
  • IMS subsystem and related address spaces must be active and fully initialized.
  • Attributes and relationships that are marked with an asterisk (*) are discovered only when the DLA runs in authorized mode.
  • No configuration datasets are read for this discovery, that is, no special data set authority required.

CDM specific information

CDM Naming Policy sys.zOS.IMSSubsystem
CDM Attribute Value Example
Label SubsystemName-SMFID IMN3-OMO1
id (IdML) SubsystemName-SMFID-IMSSubsystem IMN3-OMO1-IMSSubsystem
sourceToken (IdML) SubsystemName-SMFID-IMSSubsystem IMN3-OMO1-IMSSubsystem

Naming rules

SubsystemName and hostedDependency relationship to sys.zOS.zOS.

ControllingAddressSpace and hostedDependency relationship to sys.zOS.zOS.

Relationships

Link type Source Target Comment
hostedDependency sys.zOS.IMSSubsystem sys.zOS.zOS Part of primary naming rule a long with SubsystemName attribute.
federates sys.zOS.IMSSubsystem sys.zOS.AddressSpace For all related Control region, DLI, DBRC, IRLM, CQS, FDBR, CONNECT, OM, SCI, RM,
uses sys.zOS.AddressSpace sys.zOS.IMSSubsystem For all related Dependant Regions, for example, MPR, JMP, IFP, BMP, JBP, DBT
uses sys.zOS.IMSSubsystem sys.zOS.DB2Subsystem There may be 0 or 1 DB2® related to the IMS.
uses sys.zOS.IMSSubsystem sys.zOS.MQSubsystem There may be 0 or 1 MQ related to the IMS.
uses sys.zOS.IMSSubsystem sys.zOS.IMSSysplexGroup For related IRLMGROUP, CQSGROUP and IMSPLEX.
accessedVia sys.zOS.IMSSubsystem net.BindAddress

For all related federated address spaces that are listening on a TCP and UDP Port.

This relationship is used by the DLA sensor to stitch relationships with distributed resources.

uses sys.zOS.CICSRegion sys.zOS.IMSSubsystem  
Contains sys.zOS.IMSSubsystem sys.zOS.IMSTransaction  
Contains sys.zOS.IMSSubsystem sys.zOS.IMSProgram  
Contains sys.zOS.IMSSubsystem sys.zOS.IMSDatabase