IBM Support

Updates to IMS Library Integrity Utilities V2.2 User's Guide

Release Notes


Abstract

Updates that apply to IMS Library Integrity Utilities V2.2 User's Guide (SC19-3979-05).

Content

The most recent updates appear at the top of the list. 

Update 2
Date of change:  June 2020
Change description: Documentation changes by APAR PH24779.
Topics: Changes apply to multiple topics.

------------------------------

Topic: IMS Library Integrity Utilities overview > Functional enhancements in IMS Library Integrity Utilities Version 2 > Functional enhancements in Version 2 Release 2

The following topic has been added as follows:

...

Start of change

Integrity Checker utility

APAR PH24779 enhances the LICON utility to use IMS directory as input.

For more information, see "Integrity Checker utility". 

End of change

Other enhancements

...

------------------------------

Topic: Integrity Checker utility > Integrity Checker overview

The following topic has been modified as follows:

DMB verification function

Start of changeIntegrity Checker supports the DMB verification function to prevent database corruptions that are caused by misuse of incorrect DBDLIB, ACBLIB, or IMS directory.

When IMS databases are accessed by IMS online applications, batch applications, utilities, or IMS Tools jobs, IMS uses the database management block (DMB) to obtain database definition. DMBs are stored in the DBD libraries (DBDLIB), ACB libraries (ACBLIB), or IMS directory as load modules.

Every IMS job requires a DBDLIB, an ACBLIB, or IMS directory. IMS loads the DMB from the DBDLIB, the ACBLIB, or the IMS directory specified by the job, obtains the DMB, and processes the database based on the information in the DMB. If the DMB is incorrect and IMS uses the incorrect DMB to update the database, the database can become corrupted. For example, database corruptions can occur in the following cases:End of change

...

How the DMB verification function works

...

Through these processes, Integrity Checker detects and prevents any access to the database that uses incorrect DMBs.

These figures illustrate the process flows in the non-BPE based DBRC environment. In the BPE-based DBRC environment, Integrity Checker runs as a DBRC Request exit routine to verify the DMBs.

Start of change
If the IMS management of ACBs is enabled and IMS application or utility program uses an incorrect IMS directory, Integrity Checker detects and prevents any access to the database that uses incorrect DMBs in the same manner.
End of change

...

------------------------------

Topic : Integrity Checker utility > Planning for Integrity Checker configuration > LICON data sets and global option modules

The following topic has been added as follows:

LICON data sets

...

Start of changeIntegrity Checker obtains the DMB information that IMS™ used to load the database, stores the information in the RDE as the correct DMB information, and refers to that DMB information to verify the DMB information obtained from the DBDLIB, ACBLIB, or IMS directory that is referenced by IMS jobs.End of change

...

------------------------------

Topic: Integrity Checker utility > Activating Integrity Checker

The following topic has been modified as follows:

...

About this task

Start of changeTo activate Integrity Checker, you first prepare the global option modules and the LICON data sets. Then by using the DBD library, ACB library, or IMS directory, register the DMB information for your databases in the LICON data set.End of change

...

------------------------------

Topic: Integrity Checker utility > Activating Integrity Checker > Setting up the LICON data sets > Creating an RDE to register DMB information

The following topic has been modified as follows:

...

Procedure

...

Ensure that you provide the following information with the JCL statements:

  • Start of changeSpecify the DBD library, the ACB library, or the IMS directory that contains the DMB information to be used in DMB verifications.End of change
...

------------------------------

Topic: Integrity Checker utility > Maintaining Integrity Checker

The following topic has been modified as follows:

Start of changeTo have Integrity checker prevent database corruption caused by using incorrect DBDLIBs, ACBLIBs, IMS directory, or RECON data sets, you must maintain the Integrity checker resources appropriately.End of change

...

------------------------------

Topic: Integrity Checker utility > Maintaining Integrity Checker > Maintaining RDEs > RDE maintenance at database reorganization

The following topic has been modified as follows:

...

Start of changeIf you use other tools to reorganize the database, before you reload the database, use the INIT.DB command of the LICON utility to manually create an RDE by specifying the updated DBDLIB and the load library that contains the user exit routine as input to the utility. If the IMS management of ACBs is enabled, use the INIT.DB command of the LICON utility to manually create an RDE by specifying the IMS directory.

If you use IMS Online Reorganization Facility with the ONLINECHANGE(N) option to reorganize the database, before you restart the database, use the INIT.DB command of the LICON utility to manually create an RDE by specifying the updated DBDLIB and the load library that contains the user exit routine as input to the utility. If the IMS management of ACBs is enabled and when IMS Online Reorganization Facility is used to reorganize the database, the ONLINECHANGE(N) option is forced. After the IMPORT DEFN SOURCE(CATALOG command activates the new database definition, use the CHANGE.DB command of the LICON utility to manually re-create the RDE by specifying the IMS directory.End of change

...

The following topic has been added as follows:

Start of change

Considerations when reorganizing databases in the IMS management of ACBs environment

After you reorganize databases to change the DBD definition by using the IMS directory staging data set, you must activate the new database definition by issuing the IMPORT DEFN SOURCE(CATALOG) command. Before you start IMS online, you need to re-create the RDE with the IMS directory by using the LICON utility.

End of change

------------------------------

Topic: Integrity Checker utility > Maintaining Integrity Checker > Maintaining RDEs > RDE maintenance at DBD or RECON change

The following topic has been modified as follows:

If you change a DBD or a RECON record, you must have Integrity Checker make change in the RDE so that Integrity Checker uses the updated DMB information to verify the DMBs.

Except for cases where RDEs are created automatically during initial database load or database reorganization, whenever you change a DBD, re-create the RDE by using the INIT.DB command of the LICON utility to reflect the updated DBD information.

Start of change
If the IMS management of ACBs is enabled, re-create the RDE by specifying the IMS directory after the IMPORT DEFN SOURCE(CATALOG) command is issued.
End of change

There might be cases where you want to roll back a DBD change and use the DBD that was used before the change.

...

------------------------------

Topic: Integrity Checker utility > Preventing database corruption with Integrity Checker > DMB mismatch in IMS online environment or application jobs

The following topic has been modified as follows:

...

Elements verified in DMB verification

Start of changeIntegrity Checker stores the DMB information that IMS used to load the database in the RDE, and refers to that information as the correct DMB information. Then, when the DMB verification process starts, it uses that information to verify whether the DMB in the DBDLIB, the ACBLIB, or the IMS directory referred to by the IMS application is correct.End of change

Integrity Checker compares the following information against the information that is stored in the RDE. When a mismatch is found, Integrity Checker determines that an incorrect DMB is used.

...

------------------------------

Topic: Integrity Checker utility > Preventing database corruption with Integrity Checker > DMB mismatch during database maintenance and operation

The following topic has been modified as follows:

...

Database reorganization

Start of changeFor a database reorganization that does not accompany a DBD change, DMB verifications run while the database is being unloaded and reloaded. If a DMB mismatch is found, it means that an incorrect DBDLIB, IMS directory, or a load library that contains incorrect user exit routine is used. To resolve the problem, see "Addressing a DMB mismatch".

For a database reorganization that accompanies a DBD change, the first DMB verification is done while the database is being unloaded. For this DMB verification, Integrity Checker uses the DMB information before the DBD change. The second DMB verification is done while the database is being reloaded. For this DMB verification, Integrity Checker uses the DMB information after the DBD change. If a DMB mismatch is found, it indicates that either a new RDE was not created or an incorrect DBDLIB, IMS directory, or a load library that contains incorrect user exit routine is used. Ensure that a new RDE is created before database reload. For a DMB mismatch caused by other errors, see "Addressing a DMB mismatch".End of change

In certain circumstances, Integrity Checker automatically creates an RDE. For more information about how Integrity Checker maintains RDEs during database reorganization, see "RDE maintenance at database reorganization".

Database recovery

Start of changeWhen you recover the database to the state that is defined by the current DBD, Integrity Checker verifies the DMB by using the latest DMB information. If a DMB mismatch is found, it means that an incorrect DBDLIB, IMS directory, or a load library that contains incorrect user exit routine is used.

If a DMB mismatch is found during a recovery to a state before a DBD change (time stamp recovery), it means that the correct RDE is not restored or an incorrect DBDLIB, IMS directory, or a load library that contains incorrect user exit routine is used. Ensure that the correct RDE is restored before recovering the database.End of change

In both cases, for a DMB mismatch caused by other errors, see "Addressing a DMB mismatch".

In certain circumstances, Integrity Checker automatically restores the RDE. For more information about how Integrity Checker maintains RDEs during database recovery, see "RDE maintenance at database recovery".

DBD change

Start of changeIf a DMB mismatch is found after a DBD change, ensure that an incorrect DBDLIB, IMS directory, incorrect RECON data sets, or a load library that contains incorrect user exit routine is not used. Also, ensure that the DBD change was done with appropriate procedures, and that the DBDLIB, IMS directory, the RECON data sets, or the user exit routine was regenerated to apply the change. If these steps are not done yet, perform the steps.

If a DMB mismatch is found after restoring a DBD change, ensure that an incorrect DBDLIB, incorrect IMS directory, incorrect RECON data sets, or a load library that contains incorrect user exit routine is not used. Also, ensure that the DBD was restored with appropriate procedures, and that the DBDLIB, the IMS directory, the RECON data sets, or the user exit routine was regenerated or restored to roll back the change. If these steps are not done yet, perform the steps.End of change

In both cases, for a DMB mismatch caused by other errors, see "Addressing a DMB mismatch".

------------------------------

Topic: Integrity Checker utility > Preventing database corruption with Integrity Checker > Addressing a DMB mismatch

The following topic has been modified as follows:

Start of changeWhen Integrity Checker notifies you about a mismatch, it means that an incorrect DBDLIB, ACBLIB, IMS directory, or RECON data sets are used or a load library that contains incorrect user exit routine is used.End of change

When a DMB mismatch is reported, investigate the cause. The cause can be, for example, errors in JCL modification or in re-creation of data sets. After you identify the cause, specify the correct data set and rerun the IMS job.

Start of changeIf a DBD change was made before the run, ensure that the DBD change was done with appropriate procedures, and that the DBDLIB, the ACBLIB, the IMS directory, the RECON data sets, or the user exit routine is regenerated to apply the change. If these steps are not done, perform the steps.End of change

You can use the following methods to identify the cause of the DMB mismatch and address the problem:

Start of changeSearch for the correct DBDLIB, ACBLIB, IMS directory, or RECON data sets that match the RDE

By using the VERIFY.DB command of the LICON utility, you can verify the DBDLIB, the ACBLIB, the IMS directory, or the RECON data sets against the DMB information in the RDE.

If you have backups of the DBDLIB or the ACBLIB, you can compare them against the RDE and identify the DBDLIB or the ACBLIB that matches the RDE. If one of the backups match the RDE, you can use that DBDLIB backup or ACBLIB backup as the correct DBDLIB or ACBLIB. If the IMS management of ACBs is enabled, you can compare active ACBs in the IMS directory or staging ACBs in the staging data set against the RDE and identify the ACB that matches the RDE.End of change

If you maintain several sets of RECON data sets, you can check them against the RDE and identify whether those RECON data sets match the RDE. If a set of RECON data sets matches the RDE, you can use that set of RECON data sets as the correct RECON data sets.

Start of changeIdentify and correct the mismatching element in DBDLIB, ACBLIB, IMS directory, or RECON data sets

Identify the mismatching element in the DBDLIB, the ACBLIB, the IMS directory, or the RECON data sets. The content of the RDE can be printed by using the LIST.DB command of the LICON utility, and the content of the DBDLIB, the ACBLIB, the IMS directory, or the RECON data sets can be obtained by either of the following methods:End of change

  • Use the DBD/PSB/ACB Reversal function to print the content of the DBDLIB or the ACBLIB.
  • From a web browser, use the DBD/PSB Map Viewer of Management Console to view the content of the DBDLIB.
  • Start of changeUse the Catalog Manager function to print the content of the IMS directory data sets or the staging data set.End of change
  • Use the DBRC LIST.DB command to print the content of the RECON data sets.

Start of changeBy comparing the two, correct the mismatching element in the DBDLIB, the ACBLIB, the IMS directory, or the RECON data sets. Then, run DBDGEN, PSBGEN, ACBGEN, or issue a DBRC command and rerun the IMS job. If the IMS management of ACBs is enabled, confirm whether active ACBs in the IMS directory are valid. If staging ACBs in the staging data set are valid, issue IMPORT DEFN SOURCE(CATALOG) and activate ACBs in the staging data set.End of change

...

------------------------------

Topic: Integrity Checker utility > LICON utility reference

The following topic has been modified as follows:

The LICON utility provides several functions for handling LICON records.
The functions included are:

  • Initialize a LICON data set. A LICON data set must be initialized before it is used.
  • Start of changeCreate RDE. You can run a single job to register the DMB information for one, some, or all of the DBD/ACBs in the DBD, ACB library, or IMS directory specified.End of change
  • Change RDE. You can change an RDE at any time after an RDE is created.
...

------------------------------

Topic: Integrity Checker utility > LICON utility reference > JCL requirements for the LICON utility

Updates were made to the "DD names for the LICON utility" table and JOBLIB or STEPLIB DD, as follows:

...

Summary of DD names

The following table summarizes the DD names for the LICON utility.

Table. DD names for the LICON utility
(Table 3 in PDF)

DDNAME Use Format Need
JOBLIB or STEPLIB Input PDS Required
DFSRESLB Input PDS Required
FABLICON Input and output KSDS Required (see Note 1)
FABLPRNT Output SYSOUT Required
FABLIN Input SYSIN Required
DBDLIB Input PDS Optional (see Note 2)
ACBLIB Input PDS Optional (see Note 2)
RECONx Input Optional (see Note 1)


Notes:
1. If dynamic allocation is used, omit the DD statement.
2. Start of changeIf IMS directory is not specified, either DBDLIB or ACBLIB DD statement is required.End of change

DD statements

Code the following DD statements to identify the source of input and the placement of output information:


JOBLIB or STEPLIB DD

Specifies the load module library, which contains the following resources:

  • The LICON utility program (FABLIU00)
  • The global option modules (installation level and IMS subsystem level)
  • The IMS load module library
  • The library that contains DFSMDA dynamic allocation members for the RECON data sets. If the RECONx DD statement is omitted, the library is required (only for HALDBs)
  • The library that contains randomizing routines, segment  edit/compression exit routines, HALDB partition selection exit, or DEDB partition selection exit when creating a new RDE or verifying a DMB against an RDE with CHKRAND=Y, CHKCOMP=Y, CHKPSEL=Y, or CHKFPSEL=Y option. Even if the exit routines are placed in the LPA and LINKLST, you must specify the library that contains them.
  • The SCI exit routine for the RECON data sets (optional)
  • Start of changeThe SGLXLOAD library of IMS Tools Base V1.6 or later if you use IMS directory (optional)End of change

...

------------------------------

Topic: Integrity Checker utility > LICON utility reference > Input for the LICON utility

Runtime options have been added as follows:

The input for the LICON utility must be provided as FABLIN parameters.

Subsections:
Start of change“Runtime options”End of change
・“Commands”
・“Control statement syntax”

Start of changeRuntime options
The following runtime options are supported:
・IMSCATHLQ=catalog_hlq
・IMSCAT=DIR_ACT|DIR_STGEnd of change

Commands

The following commands are supported:

...

------------------------------

Topic: Integrity Checker utility > LICON utility reference

The following topic has been added between "Input for the LICON utility" and "INIT.DB command".

Start of change

Runtime options

This type of statement specifies the runtime options. When you want to use IMS directory as input for the LICON utility, specify the following:

Subsections:

  • Syntax
  • Parameters

Syntax

  >>-IMSCATHLQ=catalog_hlq,IMSCAT=-+-DIR_ACT-'→

                                   '-DIR_STG-'

Note: You must specify this statement at the top of the control statement when you use IMS directory as input for the LICON utility.

Parameters

IMSCATHLQ=

Specify the high-level qualifier of the IMS directory.

IMSCAT=

Specify either of the following values to indicate whether to use active ACBs or staging ACBs in the IMS directory.

DIR_ACT

Specifies to use active ACBs in the IMS directory. This is the default value.

DIR_STG

Specifies to use staging ACBs in the IMS directory staging data set.

End of change

------------------------------

Topic: Integrity Checker utility > LICON utility reference > INIT.DB command

This topic has been updated and an example for INIT.DB command has been added as follows:

Start of changeINIT.DB command creates an RDE for one, some, or all of the DBDs or ACBs in the specified DBD or ACB library. If the LICON utility finds IMSCATHLQ and IMSCAT parameters that are specified in the FABLIN DD statement, INIT.DB command creates an RDE by using the ACBs in the specified IMS directory.End of change
::

Examples
In these examples, the following conditions are assumed:

  • The IMS ID is taken from the batch SCD module (DFSVC000) loaded by the IMS load module library IMSVS.SDFSRESL.
  • The LICON data set is dynamically allocated by the LICON utility. The data set name is provided by one of the global option modules.

INIT.DB with ACBLIB
This example creates an RDE for every DMB-type ACB member in the ACB library IMSVS.ACBLIB.

//LICJOB  JOB
//       EXEC PGM=FABLIU00
//STEPLIB  DD DISP=SHR,DSN=HPS.SHPSLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL 
//ACBLIB   DD DISP=SHR,DSN=IMSVS.ACBLIB
//FABLPRNT DD SYSOUT=*
//FABLIN   DD *
  INIT.DB DBD(*)
/*


INIT.DB with DBDLIB
This example creates an RDE for every DBD member in the DBD library IMSVS.DBDLIB.

//LICJOB  JOB
//       EXEC PGM=FABLIU00
//STEPLIB  DD DISP=SHR,DSN=HPS.SHPSLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//DBDLIB   DD DISP=SHR,DSN=IMSVS.DBDLIB
//FABLPRNT DD SYSOUT=*
//FABLIN   DD *
  INIT.DB DBD(*)
/*
Start of change

INIT.DB with active ACBs in the IMS directory
This example creates an RDE for every DBD member in the IMS directory whose high-level qualifier is IMSVS.DFSCD000.

//LICJOB  JOB
//       EXEC PGM=FABLIU00
//STEPLIB  DD DISP=SHR,DSN=HPS.SHPSLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=ITB.SGLXLOAD
//FABLPRNT DD SYSOUT=*
//FABLIN   DD *
  IMSCATHLQ=IMSVS.DFSCD000,IMSCAT=DIR_ACT
  INIT.DB DBD(*)
/*

End of change

------------------------------

Topic: Integrity Checker utility > LICON utility reference >VERIFY.DB command

This topic has been updated and an example for VERIFY.DB command has been added as follows:


Start of changeThe VERIFY.DB command verifies the DBDs or ACBs in the specified DBD or ACB libraries against the RDEs stored in the LICON data set.  If the LICON utility finds IMSCATHLQ and IMSCAT parameters that are specified in the FABLIN DD statement, VERIFY.DB command verifies the ACBs in the IMS directory against the RDEs stored in the LICON data set.End of change

...

Parameters

...
You can specify both ACBLIB and DBDLIB DD statements in your JCL.

Start of change
When you specify IMSCATHLQ and IMSCAT parameters in the FABLIN DD statement and both ACBLIB and DBDLIB DD statements are specified in your JCL, the ACBs in the DBDLIB, ACBLIB, and IMS directory are verified in the RDEs stored in the LICON data set.
End of change

Examples

VERIFY.DB with both DBDLIB and ACBLIB

//LICJOB JOB
//      EXEC PGM=FABLIU00
//STEPLIB   DD DISP=SHR,DSN=HPS.SHPSLMD0
//          DD DISP=SHR,DSN=IMSVS.SDFSRESL
//DBDLIB    DD DISP=SHR,DSN=IMSVS.DBDLIB
//ACBLIB    DD DISP=SHR,DSN=IMSVS.ACBLIB
//FABLPRNT  DD SYSOUT=*
//FABLIN    DD *
  VERIFY.DB DBD(*)
/*

Start of change
VERIFY.DB with DBDLIB, ACBLIB and IMS directory

//LICJOB JOB
//      EXEC PGM=FABLIU00
//STEPLIB   DD DISP=SHR,DSN=HPS.SHPSLMD0
//          DD DISP=SHR,DSN=IMSVS.SDFSRESL
//DBDLIB    DD DISP=SHR,DSN=IMSVS.DBDLIB
//ACBLIB    DD DISP=SHR,DSN=IMSVS.ACBLIB
//FABLPRNT  DD SYSOUT=*
//FABLIN    DD *
  IMSCATHLQ=IMSVS.DFSCD000,IMSCAT=DIR_ACT
  VERIFY.DB DBD(*)
/*

End of change

------------------------------

Topic: Troubleshooting > IMS Library Integrity Utilities messages > FABL messages

The following messages have been added:

Start of change

FABL0432E THE ORDER OF THE PARAMETER FOR THE IMS CATALOG IS INCORRECT.

Explanation:

The order of the parameter for the IMS catalog is incorrect. It must be specified at the top of the FABLIN control statement.

System action:

The LICON utility ends immediately with a job step return code of 16.

User response:

See "Control statements for the LICON utility" and correct the order of the parameter, and then rerun the utility.

End of change

Start of change

FABL0433E INCORRECT VALUE IS SPECIFIED FOR [IMSCAT|IMSCATHLQ]

Explanation:

The specified value for the indicated parameter is incorrect.

System action:

The LICON utility ends immediately with a job step return code of 16.

User response:

See "Control statements for the LICON utility" and correct the value, and then rerun the utility.

End of change

Start of change

FABL3416E IMS TOOLS BASE V1.6 OR LATER IS REQUIRED

Explanation:

The requested function requires IBM IMS Tools Base V1.6 or later. However, the load module library of IBM IMS Tools Base V1.6 or later is not found in the STEPLIB DD concatenation.

System action:

The LICON utility ends immediately with a job step return code of 16.

User response:

Specify the load module library of IBM IMS Tools Base for z/OS 1.6 or later to the STEPLIB DD concatenation.

End of change

Start of change

FABL3417E UNSUPPORTED LEVEL OF IMS IS BEING USED FOR IMS DIRECTORY: xx.x

Explanation:

The LICON utility with IMS directory is run under an unsupported version of IMS. xx.x is the version and release of IMS.

System action:

The LICON utility ends immediately with a job step return code of 16.

User response:

Check whether the version of IMS is correct. Correct the error, and rerun the utility.

End of change

Start of change

FABL3418E ACCESS TO THE IMS DIRECTORY FAILED WITH RC=rc AND RSN=rsn. FUNCTION=func

Explanation:

The LICON utility cannot access the IMS catalog. This message is issued when the utility loads ACBs from the IMS directory but fails to access the IMS directory.

System action:

The LICON utility ends immediately with a job step return code of 16.

User response:

Ensure that the following IMS catalog parameter is specified correctly, and then rerun the job:

- Parameter in the FABLIN DD data set.

End of change

Message FABL0453I has been modified as follows:

FABL0453I DATABASE: dddddddd NOT PROCESSED. REASON: text

Explanation:

Database dddddddd was not processed. The reason is shown in text.

text

Start of change

IMS SYSTEM MEMBER

   The specified ACB has an IMS system member name, which is not supported.

End of change


Update 1
Date of change:  September 2019
Change description: Documentation change by APAR PH15721.
Topic: DBD/PSB/ACB Compare utility > Output from the DBD/PSB/ACB Compare utility > SYSPRINT data set > Block-level compare reports

The "Sections in PSB Compare reports" table has been modified as follows:

...

Table. Sections in PSB Compare reports

(Table 17 in PDF)

Section
Description
PRFX PSB attributes information
TPPCB PCB (ltrmname) TP PCB information
DBPCB PCB (dbname) DB PCB information
GSPCB PCB (dbname) GSAM DB PCB information
SENSEG PCB (dbname) SEG (segname) Sensitive segment information about DB PCB
PSSPTB PCB (dbname) SEG (segname) Subset pointer information about DB PCB
SENFLD PCB (dbname) SEG (segname) FLD (fldname) Sensitive field information about DB PCB
REFTBL DB (dbname) DB information referred to by DB PCB or GSAM PCB
PCBNAME NAM (pcbname) PCB name information specified in the PCB statement
PXVECT
PXPCRT
PXPCXT
PXSSRT
PXSFRT
PXPSRT
Metadata information for PSB
Start of changePXXREF DB(dbname) DB information referred to by DB PCBEnd of change
PSBGEN IMS release level information. If the PSB was generated by IMS Version 3 or higher, the level is shown.

Publication Number

SC19-3979-05

[{"Business Unit":{"code":"BU054","label":"Systems w/TPS"},"Product":{"code":"SSAVGM","label":"IMS Library Integrity Utilities for z/OS"},"ARM Category":[{"code":"a8m0z0000000CV7AAM","label":"IMS Library Integrity Utilities for z/OS"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z/OS"}],"Version":"2.2.0"}]

Document Information

Modified date:
29 June 2020

UID

ibm16238760