Updates to Tools Base IMS Tools Knowledge Base V1.3 User's Guide

Product documentation


Abstract

Updates that apply to Tools Base IMS Tools Knowledge Base V1.3 User's Guide (SC19-3397-00)

Content

The most recent update is listed first.


Update 4
Date of change:
April 24, 2012
Topic: Chapter 2. Configuring an initial installation of IMS Tools KB -> Defining IMS Tools Knowledge Base to the operating system
Change description:
Updated the statement in step 3 of Updating SYS1.PARMLIB.


Defining IMS Tools Knowledge Base to the operating system

You must define IMS™ Tools Knowledge Base to the operating system of every system that hosts either a server or an application that either reads or writes to the IMS Tools Knowledge Base server (including the IMS Tools Knowledge Base ISPF user interface).

Updating SYS1.PARMLIB

Update the SYS1.PARMLIB file with the appropriate information that defines IMS Tools Knowledge Base to the operating system that hosts the participating IMS tool.

This procedure stages the configuration settings. These changes take effect at the next initial program load (IPL).

Note: To use the IMS Tools Knowledge Base product immediately, you can dynamically define IMS Tools Knowledge Base, as explained in the next topic of this section.

To update the SYS1.PARMLIB file, complete the following steps:

  1. Authorize the LOAD library that is used by the server for the authorized program facility (APF) by adding the following statement to the PROGxx PARMLIB member:
    APF ADD DSNAME(hlq.SHKTLOAD) VOL(volser)

    Substitute the hlq variable with the installation data set high level qualifier.
  2. Add two server modules to LPA by adding the following statement to the IEALPAxx PARMLIB member:
    INCLUDE LIBRARY(hlq.SHKTLOAD)
    MODULES(FPQCSSI2,FPQCXCF2)

    Substitute the hlq variable with the installation data set high level qualifier.
  3. Define a subsystem for the server by adding the following statement to the IEFSSNxx PARMLIB member:
    SUBSYS SUBNAME(FPQ2) INITRTN(FPQCSSI2)
  4. Message FPQ3001I STACKING PC - FPQ2 SUBSYSTEM INSTALLED is issued during the next IPL, indicating that the subsystem started.


Update 3
Date of change:
April 17, 2012
Topic: Chapter 12. Conversion Utility -> Conversion Utility commands
Change description:
Moved topic from Chapter 12. Conversion Utility to Chapter 6. Repository administration, and changed name from "Conversion Utility commands" to "IMS Tools KB server commands," added usage examples, and updated descriptions.

IMS Tools KB server commands.pdfIMS Tools KB server commands.pdf


Update 2
Date of change:
March 27, 2012
Topic: Chapter 3. Configuring an existing installation of IMS Tools
KB (migration)
Change description:
Added information to clarify the requirement to convert all IMS Tools KB V1.1 or V1.2 Input, Output, Sensor, and Registry data sets to the IMS Tools KB V1.3 repository. Added information regarding the deprecation of the DELETE and RESTORE functions in IMS Tools KB V1.3.

Configuring an existing installation of IMS Tools KB (migration)

IMS™ Tools Knowledge Base provides common services for storing and viewing resources (such as RECON IDs, IMS RECON data set names, reports, sensor data, Autonomics Director objects, Discovery Utility data, policies, and rules) that are generated or used by other participating IMS Tools products.

The following topics describe the procedures that are required to configure, start, and test the migration of an existing installation of IMS Tools KB.

Important:

  • You must convert all IMS Tools KB V1.1 or V1.2 Input, Output, Sensor, and Registry data sets to the IMS Tools KB V1.3 repository format by using the IMS Tools KB V1.3 Conversion Utility. Additionally, you must connect the IMS Tools KB V1.3 server to the IMS Tools KB V1.3 ISPF interface. The IMS Tools KB server, ISPF interface, and other IMS Tools must all use the IMS Tools KB V1.3 repository. There is no support for a mixture of repository versions.
  • The DELETE and RESTORE functions are disabled in IMS Tools KB V1.3. If a RECON ID was deleted in IMS Tools KB V1.1 or V1.2 and you want to restore that RECON ID, you must restore the RECON ID before moving to IMS Tools KB V1.3.
You have two options for migrating an existing IMS Tools KB V1.1 or V1.2 installation to V1.3:
.
.


Update 1
Date of change:
March 27, 2012
Topic: Chapter 11. IMS Tools Discovery Utility -> Using the Discovery Utility
Change description:
Updated the sample member to correct syntax.


Using the Discovery Utility

You can run the Discovery Utility by modifying and submitting the JCL.

Procedure
1. Copy the HKTDISCO member from smphlq.SHKTSAMP and modify it.
//HKTDISCO  JOB  <JOB CARD PARAMETERS>
//STEP1    EXEC PGM=HKTDDSC0,                      
//             PARM=('ITKBSRVR=yourITKBservername',
//             'RECONID=yourRECONID',              
//             'FUNC=CREATE|DELETE')               
//STEPLIB  DD  DISP=SHR,DSN=smphlq.SHKTLOAD       
//         DD  DISP=SHR,DSN=ims.reslib            
//SYSPRINT DD  SYSOUT=*                            
//SYSABEND DD  SYSOUT=H                          
//

 

Rate this page:

(0 users)Average rating

Document information


More support for:

Tools Base for z/OS
IMS Tools Knowledge Base

Software version:

1.3.0

Operating system(s):

z/OS

Reference #:

7023771

Modified date:

2012-04-24

Translate my page

Machine Translation

Content navigation