The ABCs of IMS Managed ACBs - GSE Young Professionals of IMS Managed ACBs V2.pdf · databases, routing codes, transactions, OSAM buffer pools, VSAM share pools, MSC physical links,

5.1

The ABCs of IMS Managed ACBs

GSE BeNeLux IMS User Group

Clive HarrissIBM Early Experience Program Manager (eXp) – [email protected]

With acknowledgements to Deepak Kohli

© Copyright IBM Corporation 2018

mailto:[email protected]

Please note• IBM’s statements regarding its plans, directions, and intent are subject to

change or withdrawal without notice at IBM’s sole discretion.• Information regarding potential future products is intended to outline our general

product direction and it should not be relied on in making a purchasing decision.• The information mentioned regarding potential future products is not a commitment,

promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract.

• The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

• Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

© Copyright IBM Corporation 2018 2

Statement of Direction• IBM IMS has evolved into a more dynamic system, based on continuous redesign

that will ultimately eliminate the need for system generation. This redesign currently includes dynamic definition for resources such as application programs, databases, routing codes, transactions, OSAM buffer pools, VSAM share pools, MSC physical links, logical links, logical link paths, and remote logical terminals.

• IMS 14 delivered optional support allowing IMS to dynamically manage application control blocks (ACBs). IMS-managed ACBs allows for the use of DDL to replace DBD and PSB generation processes. Databases and program views can be dynamically defined using SQL DDL statements instead of generation utilities, such as ACBGEN.

• IBM intends to require IMS management of ACBs in the future. IMS and the IMS catalog must be set up to support ACB management. IMS provides a utility for this.

• At a later date, after the requirement for IMS-managed ACBs is in place, IBM also intends to remove the generation processes for PSBLIB, DBDLIB and ACBLIB. At that time, the IMS catalog, SQL, and DDL become the interface to IMS database management.

• These planned changes to IBM IMS will enhance availability, free up DBA resources, improve productivity, simplify operations, testing, and debugging, and accelerate time-to-value for new business solutions.

• Statements regarding IBM’s future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.


Presenter

Presentation Notes

So why do we think this solution has value. If is continue step towards making IMS a “Gen-less” system. Other major subsystems to not have gen processes and because of this and Because of our proprietary syntax/processes, IMS appears out of date even though we constantly deliver capabilities that are cutting edge with the current IT trends. Because IMS is managed differently that most other DBMS, it can be harder to learn; By providing industry standard interfaces (such as DDL), the same skills someone learns to manage DB2 or Oracle or … can more easily be applied to managing IMS IF lays the foundation for significantly simplifying operations, Since the process is managed by an online IMS, we can do things more dynamically and we can also consolidate processes. More on that in the demo. Also, we employ modern data sets such as PDSEs which removed limits and are easier to manage. Finally all of this can lead to increased productivity for you which can lead to more revenue as you can rollout new applications quicker

TOPICS

IMS Catalog Review

IMS Managed ACBs

Enablement and Transition to IMS Managed ACBs

Utilities


So why and what is the IMS Catalog?


Why have a Catalog?• Enables scalable and flexible IMS Open Database solution• Allow direct access to IMS databases from Java• Introduced the Single Source of Truth Concept with IMS v12• Natural next step for IMS Users with long-term IMS plans• Provides a trusted online source for two types of metadata

– IMS Database– IMS Application

6© Copyright IBM Corporation 2018

IMS Catalog is not the same as IMS Repository DB

• PSB/DBD resources‒ Database structure

definitions‒ Physical database definitions‒ Segment definitions‒ Field definitions

• Application‒ Data types‒ Application defined fields‒ Encodings‒ Redefines‒ User defined types‒ Structures

TM• MODBLKS resources

‒ Program definitions‒ Transaction definitions‒ Database definitions

• MSC resources

Catalog

VSAM Data Sets

RepositorySpare

RepositorySecondary

RepositoryPrimary

IMS PHIDAM/OSAM HALDB


What is the IMS Catalog? • Introduced back in IMS V12 – optional

• IMS Catalog is a HALDB database

– Contains IMS metadata (data about the data)

– Used by IMS Universal drivers for JDBC & DL/I access to IMS Databases

– Useful for integration with tools that provide JDBC access (e.g. Datastage)

– Data Modeling

– Etc.

• IMS Catalog is required if you will implement IMS Managed ACBs


Presenter

Presentation Notes

A very brief overview of the IMS Catalog & some of its uses. Very important: an IMS Catalog is required to implement IMS Managed ACBs. Please note, even if the client has no intention of doing JDBC access to IMS data, the Catalog is required for implementing IMS Managed ACBs

http://share.org/evaluation

• Foundation for additional existing and future IMS features:– IMS 13 Database Versioning– IMS 13 IMS Native SQL support for COBOL 5.1– IMS 13 .NET access to IMS data– IMS 14 Dynamic Database Definition– IMS 14 IMS Managed ACBs

• Some IBM products which can utilize the IMS Catalog:– IMS Explorer for Development– IBM Data Studio – Rational Asset Analyzer– COGNOS– QMF– InfoSphere Data Architect, DataStage, and Metadata Asset Manager– IBM WAS Liberty Profile, IBM MobileFirst, and IMS Mobile Feature Pack

IMS Catalog Review/Background


IMS Catalog datasets

IMS HALDB Database

– PHIDAM / OSAM HALDB database with 4 Data Set Groups– Secondary Index is partitioned– Catalog DBDs and PSBs are shipped with IMS

PartitionA

PartitionB

PartitionC

PartitionA

PartitionB

Catalog Database

Catalog Secondary Index

IMS Catalog data sets house IMS database metadata


Catalog Hierarchical Structure


Using the IMS Catalog and ACBLIB• IMS database and program resource definitions start with DBD and PSB

macro coding, followed by DBDGEN and PSBGEN• Followed by “ACBGEN & Catalog Populate Utility” processing• Catalog and active ACB member are kept in sync via the ACBGEN process• IMS runtime database and program control blocks obtained from ACBLIB• IMS database and program metadata is available from the catalog

ACBLIB and Catalog

DFS3UACB


What is IMS Managed ACBs?


IMS Managed ACBs

Directory

Catalog

IMS

ACBLIB

IMS Loads ACB blocks fromthe directory & not ACBLIB


Presenter

Presentation Notes

With IMS Managed ACBs, IMS does not use the ACBLIB. It loads the ACB Blocks from what’s called the directory dataset. The Directory dataset is the runtime equivalent of the Catalog.

WHAT IS THE IMS DIRECTORY?


What is the IMS Directory?

It’s a PDSE (ACBLIB is a PDS)

IMS directory houses ACBs (just like an ACBLIB)

Directory records have a format much like the ACBs in an ACBLIB

The directory has functionality similar to an ACBLIB IMS will reference the directory to get the runtime ACBs


Why not just use ACBLIB? Any differences between ACBLIB & Directory?

Today, GSAM database control blocks stored in DBDLIB and PSBLIB, not in ACBLIB

With IMS management of ACBs, GSAM databases will be stored in the Directory

‒ IMS will use the directory to load the GSAM runtime control blocks at each dependent region schedule

Today, logical database control blocks are stored in the DBDLIB, not in ACBLIB

With IMS Management of ACBs, logical DBDs will be stored in the IMS Catalog


Why do they call it IMS Managed ACBs?IMS will self-manage the IMS directory PDSE data sets

‒ An additional data set is allocated when a directory data set becomes full

Data set names will be an extension of the HALDB catalog data set name‒ <HALDB data set prefix>.DI<suffix>• Example

o IMSTEST.DFSCD000.DI1001o IMSTEST.DFSCD000.DI1002

IMS will use DFSDIRxx DD for directory data set allocation

IMS maintains a boot strap data set (BSDS) with information about the directory data sets


Application control blocks (ACBs) generated can be stored in a staging directory

From the IMS staging directory dataset they can be added to the IMS directory (while IMS is up) using an IMPORT command

IMPORT DEFN SOURCE(CATALOG)

Staging Directory Dataset

StagingDirectory

DirectoryIMPORT DEFN


IMPORT DEFN Command• Type 2 command

– Requires SCI & OM and a SPOC

• IMPORT DEFN SOURCE(CATALOG)– Moves members from STG directory to active directories

– Moves ALL members in STG

– Single process• Messages for problems are displayed in the output

– Command can be submitted again after corrective action taken for resources

– Imported resources are logged in 7002 log records that have the names of the resources that are changed or added


21

IMS Managed ACBs – Components / Data Sets

PartitionA

PartitionB

PartitionC

Directory

PartitionA

PartitionB

Catalog Database

Catalog Secondary Index

Directory

BSDS

Directory Directory

StagingDirectory

…

IMS Catalog data sets houseIMS database metadata

IMS directory has the runtime blocks of the IMS Catalog

The Boost Strap Data Set (BSDS)keeps track of the directory datasets

© Copyright IBM Corporation 2018

Presenter

Presentation Notes

This foil shows the various datasets for the Catalog & Directory. The Catalog is a HALDB database. So the database is made up of partitions. Each partition has up to 4 data set groups. The Catalog also has a secondary index. The IMS directory is a PDSE. The directory is created & populated using the Catalog Populate utility (DFS3PU00). More on this on the next page. IMS manages the directory datasets – meaning, if the directory data set fills up, IMS will create another directory dataset. If the second one fills up, IMS will create a third directory data set & so on. Since there can be multiple directory data sets, a Boot Strap Data set (BSDS) exists to keep track of the directory data sets. The Staging Directory data set is used an interim when importing ACB updates into the IMS directory data set.

WHAT IS THE RELATIONSHIP BETWEEN THE

IMS CATALOG & IMS DIRECTORY?


Running with IMS Catalog and Directory 1/3

PSB – IVPPSB

Repository

Directory

Catalog

TRAN – IVP

DB – IVPDBD



PSB – IVPPSB

Repository

Directory

IVPDBD ts22

IVPDBD ts22

Catalog

TRAN – IVP

DB – IVPDBD

IVPPSB ts22

IVPPSB ts22

ACBGEN ofDBD IVPDBD&PSB IVPPSB



PSB – IVPPSB

Repository

Directory

IVPDBD ts22

Catalog

TRAN – IVP

DB – IVPDBD

IVPPSB ts22

IVPPSB ts22

ACBGEN of

DBD IVPDBD IVPDBD ts23

IVPDBD ts23


Repository

Directory

IVPDBD ts23

IMS1Resident DMB

Pool

PSB Pools

IVPDB1 ts23

PSB – IVPPSB

IVPDBD ts23

• Application SQL call to IVPDBD database• IMS obtains runtime app control blocks

from ACBLIB• Catalog metadata available for use by

programs

How is the Catalog and Directory used

TRAN – IVP

DB – IVPDBD

IVPDBD ts22IVPDBD ts23

Catalog

IVPPSB ts23IVPPSB ts22

IVPPSB ts23


Difference between IMS Catalog & IMS Directory

IMS Catalog contains metadata for your DBDs & PSBs IMS Directory contains the ACBs of your DBDs & PSBs

IMS Catalog contains various instances of your DBDs & PSBs IMS Directory only contains the latest ACB of your DBD or PSB The directory is kept in sync with the catalog Both are updated

1:1 relationship between ACBs in the directory and the catalog– If the catalog is shared then Directory PDSE(s) are shared– If the catalog is non-shared then Directory PDSE(s) are non-

shared


Presenter

Presentation Notes

So IMS Managed ACBs is where IMS loads the ACB blocks not from an ACBLIB but for the IMS Directory data set. One can think of the IMS directory as the runtime equivalent of the IMS Catalog. The IMS directory dataset does not have to be created by the client. IMS creates the IMS directory data set and if it fills up, IMS will automatically allocate another IMS directory dataset. More on this on the next page. Once IMS Managed ACBs has been implemented, optionally, the client


SETTING UP IMS MANAGED ACBS


Initially Creating & Populating the IMS Catalog / Directory

ACBLIBs

DBDLIBs

PSBLIBs

Catalog Populate Utility DFS3PU00

DFSDFxxx member

Logs

Directory

IMS Catalog

SYSPRINT

SYSINP

IMSACB01

IMSACB02

IMSACBnnMANAGEDACBS=SETUP

• MANAGEDACBS=SETUP

• LOAD PSB DFSCPL00

BSDS

Staging Directory


Presenter

Presentation Notes

Again, just a very, very high level view. The IMS directory is initially created & populated by running the Catalog Populate utility with MANAGEDACBS=SETUP specified in the SYSINP data set. If you don’t have an IMS catalog created, then the Catalog populate utility will also create the IMS Catalog for you. The Catalog Populate utility uses as input the ACBLIB to build the IMS directory & the IMS catalog.


With V15 APAR PI83500 (& V14 APAR PI91613) pre-allocate the datasets or allocate the datasets in the IMS

Catalog Populate (DFS3PU00) utility jobstep.

DD names: IMSDBSDS for Boot strap dataset IMSDSTAG for Staging Directory dataset IMSD0001, IMSD0002, IMSD0003, etc. for Directory datasets

For Catalog: An optimal blocksize is 6K or 8K You will need to decide on the number of partitions (this depends on the number of DBDs & PSBS you have)


Enabling IMS Managed ACBs

In DFSDFxxx Proclib member

<SECTION=CATALOG>

CATALOG=Y, ALIAS=DFSC,

DATACLAS=,

MGMTCLAS=,

RETENTION=(VERSIONS=010),

STORCLAS=MEDIUM,

ACBMGMT=CATALOG,


How is the directory updated?

Directory

Catalog

IMS

ACBLIB

IMS Loads ACB blocks fromthe directory & not ACBLIB


Presenter

Presentation Notes

So now that the IMS directory has been built & populated, IMS will load the ACB blocks from the directory. The question is how do we update the ACB blocks in the directory. We talk about this in the next 3 foils.

Updating the directory while IMS is up

Directory

Catalog

IMS

ACBLIB

StagingDirectory

IMPORT DEFN

DFS3UACB Utility

MANAGEDACBS=STAGECatalog Populate PSB = DFSCP001

Option 1a: Continue doing ACBGENs & use DFS3UACB with MANAGEDACBS=STAGE option to also update the Staging Directory


Presenter

Presentation Notes

After a client implements managed ACBs, they have 3 options to update the directory. Here we talk about the first option. In the beginning this is what most customers would do and what we'd recommend. Here’s option 1: The client can continue to maintain their ACBLIBs & keep doing ACBGENs. But to get the ACB info from the ACBLIB into the catalog/directory, they need to run the CATPOP utility. The CATPOP utility in this case can run with either MANAGEDACBS=STAGE or MANAGEDACBS=UPDATE. With MANAGEDACBS=STAGE, the IMS Catalog is updated & the ACB blocks are placed in a staging directory data set. The ACB blocks are then ”imported” into the Directory by issuing the type 2 IMPORT DEFN command. The MANAGEDACBS=UPDATE option requires IMS to be down. With MANGEDACBS=UPDATE the Catalog Populate utility directly updates the IMS directory data set. No staging data set comes into play here. I suspect in the beginning this is what most customers would do and what we'd recommend.

Updating the directory while IMS is down

Directory

Catalog

IMS

ACBLIB

DFS3UACB Utility

MANAGEDACBS = UPDATECatalog Populate PSB = DFSCP001

Option 1b: Continue doing ACBGENs & update DFS3UACB with MANAGEDACBS=UPDATE to update Directory dataset directly


Presenter

Presentation Notes


Updating the directory – Option 2 – use only DDL

Option 2: Stop doing ACBGENs and start using DDL

Directory

Catalog

IMS

ACBLIB

StagingDirectory

DDLIMS Explorer

For Development

IMPORT DEFN

DDLBatch Utility


Presenter

Presentation Notes

Here is option 2 for updating the directory: To use ONLY DDL (and not do ACBGENs). Please note that even though the client is not doing ACBGENs they could still maintain their ACBLIBs and for that they would need to run the IMS Catalog Database Library Utility (DFS3LU00) to get the member update from the Catalog into the ACBLIB after they have done the DDL. They may want to do this because some of their vendor tools may still require ACBLIBs I doubt most customers will use this option because I don't think they will cut over to DDL all at once. They probably want to to do a phased approach. Try some DDL & do the rest via ACBGEN and as they get comfortable with DDL, they'll cut over more of their ACBGENs to DDL. Which leads to option 3 on the next page.

Updating the directory – option 3 – continue with ACBGENs

Directory

Catalog

IMS

ACBLIB

StagingDirectory

IMPORT DEFN

DFS3UACB Utility

MANAGEDACBS=STAGE

DDL

Option 3: Use ACBGENs & DDL – Phased cut over to DDL


Presenter

Presentation Notes


Lets be clear Implementing IMS Managed ACBs

Requires implementing the IMS Catalog & Directory

Implementing DDL

Requires implementing IMS Managed ACBs


Implementing IMS Managed ACBs is NOT …

• Change to the DBD/PSB source

• Change to DBDGEN or PSBGEN procedures

• Change to ACBGEN procedure to create what was/is the Staging ACBLIB

• - Use DFS3UACB for ACBGENs• Requirement to enhance the DBD source with Copybook

information

• Change to any DBRC procedures• Accessing IMS databases via JDBC or DL/I Universal drivers


Presenter

Presentation Notes




Change to any running DLIBATCH or BMP JCL

Change IMS STC procedures – Optionally can remove the ACBLIBA/B DD – Optionally can delete the ACBLIBA/B data sets

Change to any existing Common Service Layer address space (CSL)

Requirement to implement IMS Connect

Requirement to implement ODBM address space


Presenter

Presentation Notes




Requirement to use the IMSPLEX or CATALOG DBRC options in the RECON IMSPLEX if in use is unchanged CATALOG is optional and is not used unless you chose to remove

//IMS DD from DBRC command JCL

Requirement to use DRD instead of MODBLKS gen


Presenter

Presentation Notes



What about Batch jobs?


Batch Implications Application batch jobs do not have to be modified for IMS Managed

ACBs. They can continue to run with DBDLIBs & PSBLIBs

However, to enable batch jobs for IMS Managed ACBs

• Specify use of the IMS catalog and ACB management‒ Add JCL PARM to specifiy DFSDFxxx PROCLIB member or ‒ Use DFS3CDX0 exit as an alternative to modifying the JCL

• IMS will load application control blocks from the catalog

• If present, IMS ignores DBDLIB and PSBLIB, or ACBLIB‒ Overrides the DLI or DBB processing option specified in the JCL


UTILITIES



ACBLIBs

DBDLIBs

PSBLIBs

Catalog Populate Utility DFS3PU00

DFSDFxxx member

Logs

Directory

IMS Catalog

SYSPRINT

SYSINP

IMSACB01

IMSACB02

IMSACBnnMANAGEDACBS=SETUP

• MANAGEDACBS=SETUP

• LOAD PSB DFSCPL00

BSDS

Staging Directory


Presenter

Presentation Notes

Again, just a very, very high level view. The IMS directory is initially created & populated by running the Catalog Populate utility with MANAGEDACBS=SETUP specified in the SYSINP data set. If you don’t have an IMS catalog created, then the Catalog populate utility will also create the IMS Catalog for you. The Catalog Populate utility uses as input the ACBLIB to build the IMS directory & the IMS catalog.

IMS Catalog Database Library Builder Utility – DFS3LU00

Used to build DBD and PSB source from the IMS catalog• Utility will read catalog metadata and transform members

into source macros‒ Similar to the IMS Enterprise Suite Explorer for

Development function• Source can be used to generate DBDLIB, PSBLIB and

ACBLIB members DFS3LU00 utility can be used until tools are updated to use

the IMS catalog instead of DBDLIB, PSBLIB and ACBLIB


IMS Catalog Database Library Builder Utility - DFS3LU00


IMS Catalog Directory Recovery Utility - DFS3RU00

IMS Catalog Directory Recovery Utility recovers (or rebuilds) the Directory from the IMS Catalog

IMS Catalog

IMSDirectory

IMS Catalog Directory Recovery Utility


IMS Catalog Record Purge Utility - DFS3PU10

IMS Catalog Record Purge utility can be used to remove older instances of metadata from the IMS Catalog

DFSDFxxx PROCLIB member provides defaults for the utility

Currently the utility does not run online – development is aware of this & will be rectifying this.


Thank You!

58

Notice and disclaimers• Copyright © 2018 by International Business Machines Corporation (IBM). No part of this document may be reproduced or

transmitted in any form without written permission from IBM.• U.S. Government Users Restricted Rights — use, duplication or disclosure restricted by GSA ADP Schedule

Contract with IBM.• Information in these presentations (including information relating to products that have not yet been announced by IBM) has

been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. This document is distributed “as is” without any warranty, either express or implied. In no event shall IBM be liable for any damage arising from the use of this information, including but not limited to, loss of data, business interruption, loss of profit or loss of opportunity. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.

• IBM products are manufactured from new parts or new and used parts. In some cases, a product may not be new and may have been previously installed. Regardless, our warranty terms apply.”

• Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.

• Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.

• References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business.

• Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.

• It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law.


Notice and disclaimers cont.• Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements

or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM’s products. IBM expressly disclaims all warranties, expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular, purpose.

• The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right.

• IBM, the IBM logo, ibm.com, AIX, BigInsights, Bluemix, CICS, Easy Tier, FlashCopy, FlashSystem, GDPS, GPFS, Guardium, HyperSwap, IBM Cloud Managed Services, IBM Elastic Storage, IBM FlashCore, IBM FlashSystem, IBM MobileFirst, IBM Power Systems, IBM PureSystems, IBM Spectrum, IBM Spectrum Accelerate, IBM Spectrum Archive, IBM Spectrum Control, IBM Spectrum Protect, IBM Spectrum Scale, IBM Spectrum Storage, IBM Spectrum Virtualize, IBM Watson, IBM Z, IBM z Systems, IBM z13, IMS, InfoSphere, Linear Tape File System, OMEGAMON, OpenPower, Parallel Sysplex, Power, POWER, POWER4, POWER7, POWER8, Power Series, Power Systems, Power Systems Software, PowerHA, PowerLinux, PowerVM, PureApplica- tion, RACF, Real-time Compression, Redbooks, RMF, SPSS, Storwize, Symphony, SystemMirror, System Storage, Tivoli, WebSphere, XIV, z Systems, z/OS, z/VM, z/VSE, zEnterprise and zSecure are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.

• Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.


http://www.ibm.com/legal/copytrade.shtml

Documents

The ABCs of IMS Managed ACBs - GSE Young Professionals of IMS Managed ACBs V2.pdf · databases, routing codes, transactions, OSAM buffer pools, VSAM share pools, MSC physical links,