Skip to main content

PARMGEN Configuration for OMEGAMON/TMS Products on z/OS


News


Abstract

PARMGEN Configuration for IBM Tivoli OMEGAMON XE and other Tivoli Management Services (TMS) dependent products
[Supplementary materials to the "IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS PARMGEN Reference" (official documentation found in URL: http://pic.dhe.ibm.com/infocenter/tivihelp/v61r1/index.jsp?topic=%2Fcom.ibm.itm.doc_6.3%2Fwelcome.htm under "OMEGAMON XE shared publications")]

Content

Introduction:
This is PARMGEN configuration support for configuring the IBM Tivoli OMEGAMON XE and other Tivoli Management Services (TMS) dependent products on z/OS.

The products listed below, along with their dependent configurable components, are supported to create a brand new runtime environment (RTE) using the new PARMGEN mode in lieu of using the current ICAT z/OS Configuration Tool. The following versions are listed as the minimum* versions that PARMGEN mode supports for these products:
Hide details for z/OS Product Families Supported by PARMGEN (Minimum Versions)z/OS Product Families Supported by PARMGEN (Minimum Versions)
*Products configured in ICAT RTEs that will be converted to PARMGEN RTEs would need to be at these minimum versions listed above.

  • IBM Tivoli Management Services on z/OS V6.2.2
    1. Component: Tivoli Enterprise Monitoring Server [TEMS] (KDS)
    2. Component: Common Agent configuration framework (KAG)
    3. Component: Common Persistent Datastore [PDS] configuration framework (KPD)
  • IBM Tivoli OMEGAMON XE on z/OS V4.2.0
    1. Component: OMNIMON Base V6.2.0 (KCN/KOB)
    2. Component: End-to-End V6.2.0 (KET)
    3. Component: OMEGAMON II for MVS (KOM/KM2)
    4. Component: OMEGAMON XE on z/OS (KM5)
  • IBM Tivoli OMEGAMON DE on z/OS V3.1.0
    1. Component: OMEGAVIEW (KMV)
    2. Component: OMEGAVIEW II for the Enterprise (KWO)
  • IBM OMEGAMON z/OS Management Console V4.1.0
    1. Component: OMEGAMON z/OS Management Console Agent (KHL)
  • IBM Tivoli OMEGAMON XE for IMS on z/OS V4.2.0
    1. Component: OMNIMON Base V6.2.0 (KCN/KOB)
    2. Component: End-to-End V6.2.0 (KET)
    3. Component: OMEGAMON II for IMS (KOI/KI2)
    4. Component: OMEGAMON XE for IMS on z/OS (KI5)
  • IBM Tivoli OMEGAMON XE for DB2 Performance Expert/Monitor V4.2.0
    1. Component: OMNIMON Base V6.2.0 (KCN/KOB)
    2. Component: OMEGAMON XE for DB2 PE/PM (KO2/KD2)
    3. Component: OMEGAMON XE for DB2 PE/PM Agent (KD5)
  • IBM Tivoli OMEGAMON XE for CICS on z/OS V4.2.0
    1. Component: OMNIMON Base V6.2.0 (KCN/KOB)
    2. Component: End-to-End V6.2.0 (KET)
    3. Component: OMEGAMON II for CICS (KOC/KC2)
    4. Component: OMEGAMON XE for CICS on z/OS (KC5)
    5. Component: OMEGAMON XE for CICS TG on z/OS (KGW)
  • IBM Tivoli OMEGAMON XE for CICS TG on z/OS V4.2.0
    1. Component: OMEGAMON XE for CICS TG on z/OS (KGW)
  • IBM Tivoli OMEGAMON XE for Storage on z/OS V4.2.0
    1. Component: OMNIMON Base V6.2.0 (KCN/KOB)
    2. Component: OMEGAMON II for SMS (KDF)
    3. Component: OMEGAMON XE for Storage on z/OS (KS3)
  • IBM Tivoli OMEGAMON XE for Mainframe Networks V4.2.0
    1. Component: End-to-End V6.2.0 (KET)
    2. Component: OMEGAMON II for Mainframe Networks (KON)
    3. Component: OMEGAMON XE for Mainframe Networks (KN3)
  • IBM Tivoli NetView for z/OS Agent V5.4.0
    1. Component: NetView for z/OS Agent (KNA)
  • IBM Tivoli OMEGAMON XE for Messaging on z/OS V7.0.1
    1. Component: OMEGAMON XE for WebSphere MQ Configuration (KMC)
    2. Component: OMEGAMON XE for WebSphere MQ Monitoring (KMQ)
    3. Component: OMEGAMON XE for WebSphere Message Broker Monitoring (KQI)
  • IBM Tivoli Composite Application Manager (ITCAM) for SOA V7.1.1
    1. Component: ITCAM for SOA Agent (KD4)
  • IBM Tivoli Decision Support for z/OS V1.8.1
    1. Component: Tivoli Decision Support Agent (KDO)
  • IBM Tivoli System Automation for z/OS V3.3.0
    1. Component: System Automation Monitoring Agent (KAH)
  • IBM Tivoli Advanced Audit for DFSMShsm V2.3.0
    1. Component: Advanced Audit for DFSMShsm Agent (KRG)
    2. Component: Common TEP Interface (KRS)
  • IBM Tivoli Advanced Reporting and Management for z/OS V2.3.0
    1. Component: Advanced Reporting Agent (KRH)
    2. Component: Common TEP Interface (KRS)
  • IBM Tivoli Allocation Optimizer for z/OS V3.1.0
    1. Component: Allocation Optimizer Agent (KRJ)
    2. Component: Common TEP Interface (KRS)
  • IBM Tivoli Automated Tape Allocation Manager for z/OS V3.2.0
    1. Component: Automated Tape Allocation Manager Agent (KRK)
    2. Component: Common TEP Interface (KRS)
  • IBM Tivoli Advanced Catalog Management for z/OS V2.3.0
    1. Component: Advanced Catalog Management Agent (KRN)
    2. Component: Common TEP Interface (KRS)
  • IBM Tivoli Advanced Backup and Recovery for z/OS V2.2.0
    1. Component: Advanced Backup and Recovery Agent (KRV)
    2. Component: Common TEP Interface (KRS)
  • IBM Tivoli Tape Optimizer for z/OS V2.2.0
    1. Component: Tape Optimizer for z/OS Agent (KRW)
    2. Component: Common TEP Interface (KRS)
  • IBM Tivoli Composite Application Manager (ITCAM) for Application Diagnostics on z/OS V7.1.0
    1. Component: ITCAM for Application Diagnostics, TEMA (KYN)
  • ITCAM for Transactions, File Transfer Enabler for z/OS V7.1.0
    1. Component: File Transfer Enabler for z/OS Agent (KT1)

Enablement Support:

Download the latest GA star PARMGEN PTFs and let ’ s get started!
APAR#
FMID / PTF#
Interim Feature (IF) Release Date
OA37250 OA37631 HKCI310/UA61757 HKDS623/UA62353 January 26, 2012 (1Q12A)
OA38375 OA38366 HKCI310/UA63670 HKDS623/UA63672 HKDS622/UA63671 February 26, 2012 (1Q12B)
OA39386 OA38938 HKCI310/UA65042 HKDS623/UA64408 April 26, 2012 (2Q12A)
OA38937 HKCI310/UA64407 June 15, 2012 (2Q12B)
OA39626 OA40072 OA40196 OA39630 OA40162 HKCI310/UA66338 HKDS623/UA66248 August 31, 2012 (3Q12A)
OA39890 HKCI310/UA66332 September 22, 2012 (3Q12B)
OA40035 HKCI310/UA67172 December 27, 2012 (4Q12A)
OA40649 OA41145 HKCI310/UA67787 HKDS623/UA67687 *GA* February 28, 2013 (1Q13A) star
OA41710 OA42423 HKCI310/UA69076 HKDS630/UA69363 2Q13A - ETA GA **TBD** Subscribe now!
Subscribe: http://www.ibm.com/support/electronicsupport/ Sign-up for IBM MyNotifications: https://www.ibm.com/support/mynotifications


Once the latest HKCI310/HKDSvvv configuration PTFs are applied, execute the PARMGEN code from your &gbl_target_hilev.TKANCUS** OMEGAMON/ITM SMP/E target library as shown in the example invocation below:
============================================
ISRTSO ISPF Command Shell
Enter TSO or Workstation commands below:

===> EXEC 'IBM.TARGET.TKANCUS'
============================================
(where &gbl_target_hilev = IBM.TARGET in this example)

Details:
In the "Attachments:" section of this technote is a detailed discussion of the following PARMGEN topics:
TIP: : As you navigate through the larger sections of this document, do a FIND on "Date Last Updated:" to quickly see if the frequently-subscribed Section(s) such as "Section: What's New in nQyyA/nQyyB IF?", "Section: What will be in nQyyA/nQyyB IF?" or "Section: FAQs" have been updated recently. Each applicable Section will have a " (Date Last Updated: yyyymmdd)" label for readability and ease-of-use.

  • Section: What's new? (GA) Sub-section: What's New in 1Q13A?:star *GA*<--- *** Required reading *** (Date Last Updated: 20130423)
  • Section: What will be in 2Q13A? (Date Last Updated: 20130617)
  • Section: FAQS(Date Last Updated: 20130605)
  • Section: Sample RTE Implementation Scenarios(Date Last Updated: 20130618)
  • Section: RFEs for Prioritization
  • Section: (Reference Only) Previous nQyyA/nQyyB Interim Features (IFs)(Date Last Updated: 20130505)


Presentations and Upcoming Training Sessions : ( Date Last Updated: 20130618)
=========================================== =========================================== At the IBM Pulse 2013 Conference in Las Vegas, Nevada held in March 2013, PARMGEN hosted a hands-on lab training. For your reference, Session E02 PARMGEN Hands-on Lab. Guide is also now available for downloading.

Two scenarios are supplied to get you acquainted with the PARMGEN method of configuration.
  1. Scenario PGN01: Create an SMP-sharing runtime environment (RTE) with a z/OS Hub TEMS and OMEGAMON Agents. This first scenario simulates a brand new deployment such as a new install or a deployment for a Proof of Concept (PoC) to cater to our first time users.
  2. Scenario PGN02: Convert an existing Configuration Tool (ICAT) RTE to PARMGEN and upgrade the products to the current release. This second scenario simulates a real-world upgrade for an existing customer who has a mix of products. In the real world, perhaps not all of your products would be upgraded, but all in the RTE are converted to use PARMGEN where existing configuration values established in ICAT may be harvested and re-used in PARMGEN.
=========================================== ===========================================
  • Support Technical Exchange (STE):
    Title **Part 2** Good news for maintenance windows - install, configure and upgrade OMEGAMON/ITM suite faster using JOBGEN/PARMGEN
    Course number 20121001102132516
    Date 01/09/2013 @ 10:00 a.m. - 1:00 p.m. ET (US)
    Description This Support Technical Exchange (STE) session plans to cover the following topics:
    ** Part 2 is focused on the live demonstration of creating 2 PARMGEN RTE Scenarios
    ** Part 1 covered up to slide #50 of the attached PDF
    1. What is new with PARMGEN and OMEGAMON XE V510s in 2012
    2. What will be in PARMGEN 4Q12 Interim Feature (IF)?
    3. What will be in PARMGEN 1Q13 Interim Feature (IF)?
    4. Demonstrate key RTE implementation scenarios covered in the 4Q12 refresh of the PARMGEN Reference Guide
    Note: This 3-hour recorded STE will be a live mainframe demonstration for the majority of the time to allow for a more interactive session with the audience.
    Playback Centra URL:
    Centra Password:     		https://de202.sabameeting.com:443/GP/main/00000183cb250000013b0d4e155b8283

    tiv0li (0 is a zero)
=========================================== - Slides 62-74 extracted out of the master presentations into " PARMGEN Scenarios and Best Practices .pdf" deck

===========================================
  • IBM Software for System z Events: February 23, 2012 PARMGEN Phase 2 teleconference: "Good news for maintenance windows - Install and configure OMEGAMON faster"
    1. >> Broadcast Date: February 23, 2012 at 11:00 a.m. - 12:00 p.m. ET (US)
    2. >> To obtain playback recording and materials ==> http://www.ibm.com/software/os/systemz/webcast/sysmgmt/series/
    3. >> Full version of the presentation materials (2/23/2012 webcast presentation covered a portion of the full version)
IBM System z Software Teleconference - February 23 2012 PARMGEN Phase 2.zipIBM System z Software Teleconference - February 23 2012 PARMGEN Phase 2.zip <-- based on 1Q12 PARMGEN design
  • IBM Software for System z Events: December 1, 2011 PARMGEN Phase 1 teleconference: "An Improved Approach to Configuration of Tivoli OMEGAMON" >> Broadcast Date: December 1, 2011 at 11:00 a.m. ET (US)
  • >> To obtain playback recording and materials ==> http://www.ibm.com/software/systemz/telecon/dec1/prz
===========================================

Attachments:

*** Required Reading - HOLDDATA-related information ***
Section: What's New in GA star 1Q13A?: (Date Last Updated: 20130423)
Hide details for Section: What's New in GA 1Q13A? RFEs/Issues Addressed by APAR OA40649 (HKCI310 PTF UA67787):Section: What's New in GA 1Q13A? RFEs/Issues Addressed by APAR OA40649 (HKCI310 PTF UA67787):
Section: 1Q13A Request for Enhancements (RFE)/Issues Addressed by APAR OA40649 (HKCI310 PTF UA67787):
PARMGEN 1Q13A Whats New (APAR OA40649) Interim Feature D20130423.docPARMGEN 1Q13A Whats New (APAR OA40649) Interim Feature D20130423.doc

===END "Section: What's New in GA 1Q13A? "===

Section: What will be in 2Q13A?: (Date Last Updated: 20130617)
Hide details for Section: What will be in 2Q13A? RFEs/Issues Addressed by APAR OA41710 (HKCI310 PTF UA69076):Section: What will be in 2Q13A? RFEs/Issues Addressed by APAR OA41710 (HKCI310 PTF UA69076):
Section: 2Q13A Request for Enhancements (RFE)/Issues Addressed by APAR OA41710 (HKCI310 PTF UA69076) / APAR OA42423 (HKDS630 PTF UA69363):
PARMGEN 2Q13A Whats New (APAR OA41710) Interim Feature D20130617.docPARMGEN 2Q13A Whats New (APAR OA41710) Interim Feature D20130617.doc

===END "Section: What will be in 2Q13A? "===

Section: FAQs: (Date Last Updated: 20130605)
Hide details for Section: FAQs:Section: FAQs:
Section: FAQs:

  • FAQ Index: The following "FAQ#nn QUESTION:" entries list the queries addressed in this section. Navigate to the
  • FAQ Details" section below for the detailed discussion. For ease-of-use, the FAQs have been grouped by popular search keywords that may be used and/or basic category where an FAQ may be classified under so the FAQ#nn are not in any ascending or descending order, but rather grouped by category based on when the FAQ was logged.

Next FAQ#nn:
=============================================================
FAQ#55 QUESTION : <placeholder>
=============================================================
PARMGEN FAQs D20130605.docPARMGEN FAQs D20130605.doc
===END " FAQ#nn "===
===END " Sub-section: FAQ Details "===

===END " Section. FAQs "===
===END " Section. FAQs "===

Hide details for Section: Sample RTE Implementation Scenarios Section: Sample RTE Implementation Scenarios
Section. Sample RTE Implementation Scenarios :
  • The latest version of the Common Parameter Reference Guide is also now posted in the Infocenter (prior version from February 2011).

======================================================================
===END " Section: Sample RTE Implementation Scenarios "===

Hide details for Section: Request For Enhancements (RFE) for Future Consideration/Known Limitations for Future Implementation: Section: Request For Enhancements (RFE) for Future Consideration/Known Limitations for Future Implementation:
Section. Request For Enhancements (RFE) for Future Consideration/Known Limitations for Future Implementation:
The following enhancements and issues have been queued for further consideration (for enhancements) and for further implementation (known issues/limitation in the GA release):
Parameter Generator (PARMGEN) Workflow UI - Future RFEs for Prioritization (Technote #1417935).pdf
A. Future Enhancements:
======================================================================
  • RFE: <Next>
  • DESCRIPTION: <Next>
  • STATUS: <Next>
  • Tip: <Next>
======================================================================

B. Known Issues/Limitations:
======================================================================
  • ISSUE: <Next>
  • DESCRIPTION: <Next>
  • FIX: <Next>
  • Tip: <Next>
======================================================================

===END " Section: RFEs for Prioritization (Futures) "===

Hide details for Section: (Reference Only) Previous nQyyA/nQyyB Interim Features (IFs) Section: (Reference Only) Previous nQyyA/nQyyB Interim Features (IFs)
The following Interim Features (IFs) from previous maintenance cycles are also available for reference. These PTFs below are superceded by the latest HKCI310 and HKDS623 PTFs noted in the "Enablement Support" Section of this technote. The "What's New? (GA)" Section features the latest IFs available and their contents.

Section: What's New in GA 4Q12A ( Date Last Updated: 20130505)
PARMGEN 4Q12A Whats New (APAR OA40035) Interim Feature D20130505.docPARMGEN 4Q12A Whats New (APAR OA40035) Interim Feature D20130505.doc
===END " Section: What's New in GA 4Q12A "===

Section: What's New in 3Q12B: ( Date Last Updated: 20130226)
Hide details for Section: 3Q12B Request for Enhancements (RFE)/Issues Addressed: Section: 3Q12B Request for Enhancements (RFE)/Issues Addressed:
As noted in the "Enablement Support" Section of this technote, the "What's New? (GA)" Section provides the low-level details of the latest IF available for PARMGEN. As a reference, previous IFs from earlier maintenance cycles are documented in the "Section: (Reference Only) Previous nQyyA/nQyyB Interim Features (IFs)" at the bottom of these Sections.

*** Required reading ***
Section: What's New in 3Q12B: star
Hide details for Section: What is in 3Q12B? RFEs/Issues Addressed by APAR OA39890 (HKCI310 PTF UA66332): Section: What is in 3Q12B? RFEs/Issues Addressed by APAR OA39890 (HKCI310 PTF UA66332):
Section: 3Q12B Request for Enhancements (RFE)/Issues Addressed by APAR OA39890 (HKCI310 PTF UA66332):

*** Important HOLDDATA-related Details and Notes in 3Q12B PTFs ***
  • 3Q12B Note#1: Please review "Section: What's New in 3Q12A" and "Section: What's New in 2Q12B" HOLDDATA information if you have not done so already. If you will be reconfiguring the existing PARMGEN-created RTE, then once you apply any of the xQ12* maintenance, perform step #1 and #2 at a minimum:
    1. *** Required*** Refresh your KCIJPCFG job by navigating to “1. KCIJPCFG Set up PARMGEN work environment for an RTE. “ step on the PARMGEN Workflow UI (KCIP@PG0) menu. Regenerate and resubmit the KCIJPCFG job.
    2. *** Required*** Rerun the KCIJPUP1 job ("KCIJPUP1 Update interim libraries and create profiles." option on the KCIP@PG0 menu).
    3. *** Conditional *** Depending on which RTE maintenance scenario you are performing as outlined in FAQ#5 in the "Section: FAQ" below, proceed with the applicable PARMGEN steps (rerunning $PARSE job, rerunning KCIJcLOD job on the SUBMIT option sub-menu, etc.)
  • 3Q12B Note#2: Updated WCONFIG(Kpp$*) Override Imbeds that need to be deleted or renamed so KCIJPUP1 job automatically rebuilds a new default Kpp$P* override member. *** Conditional *** Rename the following WCONFIG(Kpp$*) members prior to regenerating and resubmitting the KCIJPUP1 job. Note that these members are typically preserved so KCIJPUP1 job will not create a new&improved version if the Kpp$* exists in WCONFIG library.
- WCONFIG(KN3$SNMP) - applicable if you are configuring the OMEGAMON XE for Mainframe Networks (KN3) component.
  • Changes: Initial default IP addresses are populated by default based on the system's autodiscovered IP address in the system where you will submit the KCIJPUP1 job.
- WCONFIG(KNA$PENV) - applicable if you are configuring the NetView on z/OS Agent (KNA) component.
  • Changes: Initial CTIRA_* Agent parameters are provided for further user override as necessary.


The following enhancements and issues are addressed in the HKCI310 PARMGEN PTF UA66332 for APAR OA39890:
A. 3Q12B Enhancements:
======================================================================
Hide details for RFE: Provide PARMGEN Workflow UI improvements for PARMGEN: A. Configuration Framework Enhancements/Updates RFE: Provide PARMGEN Workflow UI improvements for PARMGEN:
A. Configuration Framework Enhancements/Updates
B. Application Configuration Enhancements/Updates
  • RFE: Provide PARMGEN Workflow UI improvements for:
A. PARMGEN Configuration Framework Enhancements/Updates :
  1. Provide support to backup the GBL_USER_JCL library as part of the &philev.&rte.WCONFIG(KCIJPUP1) "Update interim libraries and create profiles" job.
  2. Provide new standalone PARMGEN utility jobs in the &rhilev.&rte,WKANSAMU library: KCIJPCPR backup RK* production user runtime libraries job and KCIJPCPW backup WK* PARMGEN work libraries job. These jobs intend to replace WKANSAMU(KCIJPCY) backup job which currently still needs further editing to specify which set of libraries (PARMGEN WK* work libraries or RK* product execution user libraries) to copy into the back-up libraries.
  3. Update the WCONFIG(KCIJ$NDX) Job Index input to the "$JOBINDX Review PARMGEN job index." option on the "KCIP@PG0 ------ PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME" main menu to provide description of the users of the KCIJPCPR and KCIJPCPW backup jobs.
  4. Refresh read-only product libraries with latest maintenance from the SMP/E target libraries as part of the KCIJPLOD RTE Load maintenance job, although the product(s) that use these libraries may not be configured yet in a given RTE. This ensures that products that have Tivoli Enterprise Monitoring Server (TEMS) registration dependencies and/or Tivoli OMEGAMON Manager (TOM) registration dependencies have their RTE elements refreshed by default, when these products are installed in the SMP/E CSI.
===END " Sub-section: A. 3Q12B RFEs>>A. Configuration Framework Enhancements/Updates :"

B. PARMGEN-supported Application Configuration Enhancements/Updates :
  1. OMEGAMON Enhanced 3270UI: Support Tivoli OMEGAMON Manager (TOM) configuration improvements by providing the option to configure a standalone OMEGAMON Enhanced 3270ui (e3270ui) component into its own RTE along with a TEMS configuration, without the requirement to also configure the OMEGAMON XE products that ship the e3270ui FMID (HKOB700 FMID) in the same RTE. A new CONFIGURE_E3270UI_KOB flag supports this option on the "EXCLUDE PRODUCTS FROM PARMGEN CUSTOMIZATION" KCIP@PG5 panel.
  2. OMEGAMON Enhanced 3270UI: In the composite STC startup member (CANSSTRT by default) that is created by the PARMGEN's $PARSE* "Create runtime members and job" and copied to the system procedure library by the PARMGEN KCIJPSYS system copy job), update the PARMGEN process to generate the startup for the Tivoli OMEGAMON Manager (TOM) started task after the startup statements for the TEMS and the Agents to avoid "KOBCM0021E: Failure getting registered DRA" initial messages logged in the the TOM's SYSPRINT DD, if none of the address spaces that startup the TOM's KOBAGENT Data Retrieval Agent (DRA) has been fully started yet.
  3. Tivoli Enterprise Monitoring Server (TEMS): Support TEMS registration requirements of applications in the TEMS RTE even if the product is not configured in the same RTE as the TEMS. Examples of these types of TEMS registration requirements are LOADLIST(KD5LLIS1) KDP* metaprobes loadlist for OMEGAMON XE for DB2 PE/PM, DELRUN-related steps in KCIJPLOD job to clean-up any obsolete or renamed RKANDATV KppATR attribute and KppCAT catalog files for OMEGAMON XE for CICS V510, OMEGAMON XE for DB2 V511, OMEGAMON XE on z/OS V510 and OMEGAMON z/OS Management Console V410.
  4. OMEGAMON XE on z/OS V4.2.0 and V5.1.0: Provide KM5_SYSPLEX_PROXY_POSITION = "EXCLUDE" support to allow the flexibility of excluding the TEMS in an RTE to be eligible to be an OMEGAMON XE on z/OS Sysplex Proxy.
  5. OMEGAMON XE on z/OS V5.1.0: Update the KCIJPLOD RTE Load job's DELRUN step with RKANDATV KHLATR attribute and KHLCAT catalog clean-up of OMEGAMON z/OS Management Console (KHL) ODI files as OMEGAMON XE on z/OS starting in V510, has subsumed the KHL functions.
  6. OMEGAMON XE on z/OS V5.1.0: Update the High-Availability Hub TEMS configuration to not pre-load the LOADLIST(KHLLLIS2) OMEGAMON z/OS Management Console modules if OMEGAMON XE on z/OS V510 is installed in the SMP/E CSI, as OMEGAMON XE on z/OS starting in V510, has subsumed the KHL functions.
  7. OMEGAMON XE for DB2 PE/PM V5.1.1: In V511, provide the OMEGAMON Collector (CANSO2 by default) startup 'PARM='/SUB=OM'' generic subsystem name prefix support to take advantage of the OMPE Collector initialization enhanced processing of dynamically assigning an available suffix in the range of 00 to 99 to create a complete 4-character subsystem name (for example: OM32). This improvement ensures that the SUB=OMnn unique subsystem name belongs to the started OMPE Collector, and thus avoid KO2Z999E conflicts.
  8. OMEGAMON XE for DB2 PE/PM V4.2.0 and higher versions: Modify the OMPE/XCF Receive Tasks parameter(XCFTASKS=%KD2_OMPE_SUB_D2PARCVT%) configuration default from 16 to 06. The XCFTASKS=nn parameter is written in the OMPE Collector Realtime Customer Options in the &rhilev.&rte.xKD2PAR(OMPE00) member. The benefit of changing the XCFTASKS=16 to XCFTASKS=06 is that it reduces the number of member connections that are created by the XCF gateway component as well as reduce the number of XCF Gateway attached tasks by 10 in the OMPE Collector address space. Reducing the number of attached tasks improves VSCR in 24-bit virtual storage in constrained customer environments.
  9. OMEGAMON XE for DB2 PE/PM V4.2.0 and higher versions:Provide a new WCONFIG(KD2$POP1) xKD2PAR(OMPEOPTS) OMPE Collector Realtime Customer Options override imbed so customers are able to customize these typically-hardcoded parameters when in ICAT mode: XCFMODE=ACTIVE, DB2RTCPU=NO, DB2REMIO=NO, ASCBCHAP=INACTIVE MGSUBSYS=INACTIVE, and CICSCORR=NO
  10. OMEGAMON XE for DB2 PE/PM V4.2.0 and higher versions: Provide the flexibility to use a customer-supplied jobcard for the Performance Warehouse (CANSPWH) started job.
  11. OMEGAMON XE for Mainframe Networks V4.2.0: Increase the KN3_AGT_STORAGE_MINIMUM_EXTEND MINIMUM(&value,X) parameter configuration default from 256000 to 768000. This parameter equates to the MINIMUM(% KN3_AGT_STORAGE_MINIMUM_EXTEND%,X) storage parameter written out in the xKANPARU(KN3SYSIN) TMS:Engine startup member.
  12. OMEGAMON XE for Mainframe Networks V4.2.0: Increase the KN3_X_AGT_STORAGE_LIMIT_EXTEND LIMIT(&value,X) parameter configuration default from 22 to 23. This parameter equates to the LIMIT(% KN3_X_AGT_STORAGE_LIMIT_EXTEND LIMIT%,X) storage parameter written out in the xKANPARU(KN3SYSIN) TMS:Engine startup member.
  13. OMEGAMON XE for Mainframe Networks V4.2.0: Default the RTE xKANSAMU(KN3SNMP) member's user override imbed (&rte_plib_hilev.&rte.WCONFIG(KN3$SNMP)) with IP addresses populated by default based on the system's autodiscovered IP address in the system where you will submit the KCIJPUP1 job.
  14. OMEGAMON XE for Mainframe Networks V4.2.0: Provide System Variables support for KONSNMP DD and KN3SNMP DD in the OMEGAMON XE for Mainframe Networks product started tasks in order to support a generic xKANSAMU(KN3SNMP) member.
  15. IBM Tivoli NetView for z/OS Agent V6.1.0: Support customer-overridable CTIRA_* TMS:Engine common Agent parameters such as CTIRA_RECONNECT_WAIT = 60 and CTIRA_HEARTBEAT = 1 in the NetView Agent's &rte_plib_hilev.&rte.WCONFIG(KNA$PENV) override imbed member. KNA$PENV is imbedded in the NetView Agent's &rhilev.&rte.xKANPARU(KNAENV) Agent environmental member.
===END " Sub-section: A. 3Q12B RFEs>>B. Application Configuration Enhancements/Updates :"
===END " Sub-section: A. 3Q12B RFEs"
======================================================================
===END " Sub-section: A. 3Q12B Enhancements"
======================================================================

B. 3Q12B Issues:
Hide details for SYMPTOM: PARMGEN KCIJPUSS job and DS#Uxxxx ICAT USS job loggers report a condition code = 0000 although the Se SYMPTOM: PARMGEN KCIJPUSS job and DS#Uxxxx ICAT USS job loggers report a condition code = 0000 although the Self Describing Agent KDSMKDIR-related steps (PARMGEN) and DSUSS1-related steps (ICAT) encountered "BPXF134E RETURN CODE 00000075, REASON CODE 0552
======================================================================
  • SYMPTOM: PARMGEN KCIJPUSS job and DS#Uxxxx ICAT USS job loggers report a condition code = 0000 although the Self Describing Agent KDSMKDIR-related steps (PARMGEN) and DSUSS1-related steps (ICAT) encountered "BPXF134E RETURN CODE 00000075, REASON CODE 05520038 AN ERROR OCCURRED DURING THE CREATION OF DIRECTORY /rtehome.".
  • DESCRIPTION: The current IKJEFT01 TSO program used by the PARMGEN and ICAT USS jobs, does not currently process the BPXF134E RETURN CODE coming from SYSEXEC DD (SYS1.SBPXEXEC by default) SYSTSPRT output. If the PARMGEN KCIJPUSS job and the DS#Uxxxx ICAT USS job are modified to switch to use PGM=IKJEFT1A program instead, the jobs will now report a return code 12 which is ideal if the USS directories truly do not exist but the drawback to this is using IKJEFT1A stops the job altogether at the first MKDIR command failure, and does not process the rest of the commands. In a scenario where this is the second RTE being created to share the same RTE USS home directory as the first RTE (PARMGEN profile RTE_USS_RTEDIR = "/rtehome" value by default), then the RTE USS directory will already exist for the first RTE. With IKJEFT1A program, the second RTE's KCIJPUSS job will fail as the RTE USS directory home already exists so using IKJEFT1A, it will not create the second RTE's USS directories so its KCIJPUSS PARMGEN job will fail also.
  • WORKAROUND/TIP: : The PARMGEN and ICAT USS jobs will be modified further to process the MKDIR commands via a separate REXX program. For the timebeing, please review your KCIJPUSS job output for any "BPXF134E RETURN CODE" messages and verify if these USS directories already exists, and if not, verify if the TSO userid submitting the USS job, has authority to create these USS directories. In PARMGEN, the SUBMIT panel indicates "(Authorization Required)" for the KCIJPUSS job.
SDSF JOB DATA SET DISPLAY - JOB KCIJPUSS JOB16067
COMMAND INPUT ===>
NP DDNAME StepName ProcStep
JESJCLIN
$INTTEXT JES2
SYSLIN KQIPNODE
SYSTSIN KCIJPUSS
JESMSGLG JES2
JESJCL JES2
JESYSMSG JES2
SYSTSPRT KDSMKDIR
SYSTSPRT KQIMKDIR
SYSPRINT KQIPNODE
SYSTSPRT KCIJPUSS

SDSF OUTPUT DISPLAY KCIJPUSS JOB16067
COMMAND INPUT ===> SCROLL ===> CSR
********************************* TOP OF DATA **********************************
READY
mkdir '/rtehome' MODE(7,7,7)
BPXF134E RETURN CODE 00000075, REASON CODE 05520038. AN ERROR OCCURRED DURING T
READY
mkdir '/rtehome/LPAR1' MODE(7,7,7)
BPXF134E RETURN CODE 00000075, REASON CODE 05520038. AN ERROR OCCURRED DURING T
READY
mkdir '/rtehome/LPAR1/kds' MODE(7,7,7)
BPXF134E RETURN CODE 00000075, REASON CODE 05520038. AN ERROR OCCURRED DURING T
READY
mkdir '/rtehome/LPAR1/kds/support' MODE(7,7,7)
BPXF134E RETURN CODE 00000075, REASON CODE 05520038. AN ERROR OCCURRED DURING T
t.
READY
mkdir '/rtehome/LPAR1/kds/support/TEMS' MODE(7,7,7)
BPXF134E RETURN CODE 00000075, REASON CODE 05520038. AN ERROR OCCURRED DURING T
t/TEMS.
READY
mkdir '/rtehome/LPAR1/kds/support/TEMS/SDMBACKUP' MODE(7,7,7)
BPXF134E RETURN CODE 00000075, REASON CODE 05520038. AN ERROR OCCURRED DURING T
t/TEMS/SDMBACKUP.
READY
mkdir '/rtehome/LPAR1/kds/support/TEMS/META-INF' MODE(7,7,7)
BPXF134E RETURN CODE 00000075, REASON CODE 05520038. AN ERROR OCCURRED DURING T
t/TEMS/META-INF.
READY
oput 'IBM.LPAR1.RKANDATV(KDSDPROF)' '/rtehome/LPAR1/kds/support/TEMS/KDSDPROF' text
IGD103I SMS ALLOCATED TO DDNAME SYS00001
READY
oshell chmod 644 '/rtehome/LPAR1/kds/support/TEMS/KDSDPROF'
READY
END
******************************** BOTTOM OF DATA ******************************** !Note: Future APAR OA40035 will provide the resolution to this issue.
======================================================================

Hide details for SYMPTOM: PARMGEN KCIJPCNV job gets a return code 8 in the KCIRPLBC SYSTSPRT. SYMPTOM: PARMGEN KCIJPCNV job gets a return code 8 in the KCIRPLBC SYSTSPRT.
======================================================================
  • SYMPTOM: PARMGEN KCIJPCNV job gets a return code 8 in the KCIRPLBC SYSTSPRT.
  • DESCRIPTION: Product rules for SMP/E dependencies versus configuration dependencies on the product-supplied &gbl_target_hilev.TKANCUS(KppDINFO) product information members vary for the KDS (TEMS) and KOB (OMEGAMON Enhanced 3270) components depending on the product version.
Varying symptoms from the KCIJPCNV job are listed below (from the job's KCIRPLBC SYSTSPRT DD):
SDSF OUTPUT DISPLAY KCIJPCNV JOB21856
COMMAND INPUT ===> SCROLL ===> CSR
=======================================================================

Cannot exclude KDS because it is still required by:
KC5 KGW KD5 KI5 KMQ

Cannot exclude KOB because it is still required by:
KC5 KD5 KD5 KI5

Cannot exclude KMC because it is still required by:
KMQ

Determine what to configure and what not to configure.
Make appropriate changes to KCIJPCFG and rerun:
KCIJPCFG, KCIJPUP1 and KCIJPCNV.

For each of the products listed above that cannot be excluded either:
1. In KCIJPCFG set the CONFIGURE_ parm for that product to "Y".
2. In KCIJPCFG set the CONFIGURE_ parms to "N" for all of
the products listed as still requiring that product.
=======================================================================
  • WORKAROUND/TIP: : The PARMGEN KCIRPLBC ICAT->PARMGEN conversion job will be modified further to accommodate the varying dependencies on the KDS and KOB components depending on the version of the product installed. For a workaround, please contact PARMGEN Development team for a circumvention.
======================================================================

===END " Sub-section: B. 3Q12B Issues"

===END " Sub-section: 3Q12B Enhancements/Issues Addressed "===

===END " Sub-section: What's New in 3Q12B "===

Section: What's New in 3Q12A:
Hide details for Section: 3Q12A Request for Enhancements (RFE)/Issues Addressed: Section: 3Q12A Request for Enhancements (RFE)/Issues Addressed:
Section. 3Q12A Request for Enhancements (RFE)/Issues Addressed by APAR OA39626/OA40072/OA40196 (PTF UA65847/UA66106/UA66338) / OA39630/OA40162 (HKDS623 PTF UA65846/UA66248):

*** Alerts ***
  • HKCI310 PTF UA66338 supercedes previous HKCI310 PTFs UA65847 and UA66106.
  • HKDS623 PTF UA66248 supercedes previous HKDS623 PTF UA65846.

*** Important HOLDDATA-related Details and Notes ***
  • 3Q12A Note#1: Please review "Section: What's New in 2Q12B" HOLDDATA information if your existing PARMLIB or PARMGEN-created RTE was created prior to the 2Q12B/3Q12A enhancements: If you will be reconfiguring the existing PARMGEN-created RTE, then once you apply any of the xQ12* maintenance, perform step #1 and #2 at a minimum:
    1. *** Required*** Refresh your KCIJPCFG job by simply navigating to “1. KCIJPCFG Set up PARMGEN work environment for an RTE. “ step on the PARMGEN Workflow UI (KCIP@PG0) menu. Regenerate and resubmit the KCIJPCFG job.
    2. *** Required*** Rerun the KCIJPUP1 job ("KCIJPUP1 Update interim libraries and create profiles." option on the KCIP@PG0 menu).
    3. Depending on which RTE maintenance scenario you are performing as outlined in FAQ#5 in the "Section: FAQ" below, proceed with the applicable PARMGEN steps (rerunning $PARSE job, rerunning KCIJcLOD job on the SUBMIT option sub-menu, etc.)
  • 3Q12A Note#2: For existing PARMLIB or PARMGEN-created RTEs in general, if you will be reconfiguring the existing PARMGEN-created RTE, then at a minimum, invoke PARMGEN and rerun the KCIJPUP1 job ("KCIJPUP1 Update interim libraries and create profiles." option on the KCIP@PG0 menu. This job refreshes the PARMGEN templates in the PARMGEN %RTE_PLIB_HILEV%.%RTE_NAME%. IK* interim staging libraries and refreshes the IBM-supplied PARMGEN CONFIG profiles ($GBL$IBM global and $CFG$IBM LPAR RTE profile) to automatically update the profile parameters with any new default configuration parameters that product maintenance may introduce.
  • 3Q12A Note#3*** Important *** Refresh the PARMGEN CONFIG profiles as necessary: The values you specify on the KCIJPCFG series of panels, all equate to GBL_* or RTE_* profile parameters, respectively. If you change any of the KCIJPCFG values, these settings affect how the RTE is built. For example, if you change the RTE_PLIB_HILEV, RTE_HILEV, or RTE_VSAM_HILEV values, these fields equate to PARMGEN profile parameters in the WCONFIG(%RTE_NAME%) RTE LPAR profile. Refresh the PARMGEN profile by changing the values of these parameters to the new values you specified on the KCIJPCFG panels, then rebuild the RTE to reflect the latest values in the PARMGEN WKANSAMU jobs such as KCIJPALO RTE libraries allocation job, KCIJPLOD RTE Load job, and other affected jobs. To refresh the PARMGEN CONFIG profiles, adjust the corresponding PARMGEN profile parameters in the WCONFIG PARMGEN profiles by selecting the "%RTE_NAME% Customize PARMGEN configuration profiles." option on the "PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME" menu. Adjust the values accordingly (either the %RTE_NAME% LPAR user profile and/or the $GBL$USR global user profile), then rerun the WCONFIG($PARSE) or WCONFIG($PARSESV) job, and rerun the WKANSAMU jobs to rebuild the RTE PARMGEN set-up (typical if you change important values such as RTE HLQs that invalidate the current RTE when changed).
  • 3Q12A Note#4: When to refresh KCIJPCFG job: Redo the "1. KCIJPCFG Set up PARMGEN work environment for an RTE." option if you are:
    1. Upgrading the existing RTE to a new version of the product. KCIJPCFG job dynamically reads the SMP/E target libraries to know what versions of the products are installed and available for configuration and upgrade. KCIJPCFG job dynamically creates/rebuilds the $VERSION member in the WCONFIG library.
    2. Adding/Deleting product(s) into an existing RTE. KCIJPCFG job dynamically refreshes the CONFIGURE_*_Kpp product configuration flags in the KCIJPUP1 job (generated by KCIJPCFG job). KCIJPUP1 job, in turn, (re)builds the IBM-supplied $CFG$IBM IBM-supplied LPAR profile in the WCONFIG library. If you are adding or deleting a product in an RTE, submit the regenerated KCIJPCFG job, rerun the KCIJPUP1 job, edit the WCONFIG(%RTE_NAME%) LPAR profile to set the CONFIGURE_*_Kpp flag accordingly, and proceed with the remaining PARMGEN process ($PARSE* job, SUBMIT, etc.). Review the "PARMGEN RTE life cycle" help topic on the "PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME" main menu help for information if you want to exploit/override new PARMGEN profile parameter values after the initial WCONFIG(%RTE_NAME%) RTE LPAR profile has already been created, and you want WCONFIG(%RTE_NAME%) to house the newly-added PARMGEN profile parameters brought in by any new configuration maintenance, but still preserve your original customizations for the existing PARMGEN profile parameters.
    3. Changing any of the KCIJPCFG values on the "SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (n OF 3)" KCIP@PGn panels.
  • 3Q12A Note#5: Starting in 2Q12B PARMGEN maintenance, the invocation of PARMGEN has been enhanced to simply execute the %GBL_TARGET_HILEV%.TKANCUS SMP/E library. You may continue to invoke PARMGEN via the enhanced way or the original invocation of executing ===> EXEC '%GBL_TARGET_HILEV%.TKANCUS(KCIR@PG1)'
  • 3Q12A Note#6: Starting in 2Q12B PARMGEN maintenance, some of the PARMGEN panels were modified. As a result, the following publications published in 1Q12 will contain documentation steps that will not match the PARMGEN panels presented @ 2Q12B design. The publications are as follows:
    1. Tivoli® OMEGAMON XE and Tivoli Management Services on z/OS PARMGEN Reference (Chapter 2. PARMGEN Implementation Scenarios)
    2. Tivoli® OMEGAMON XE and Tivoli Management Services on z/OS Common Planning and Configuration Guide (Chapter 4. Configuring products using the PARMGEN Workflow user interface).
Plans are in place to refresh these publications in the future.
  • 3Q12A Note#7: Review "B. 3Q12A Issues:" section. If you are using OMEGAMON XE on z/OS Epilog function, if you are using System Variables in your PARMGEN RTE, and/or if you are using 7-digit JES jobnames to see if these issues addressed in 3Q12A PTF apply to your environment.

The following enhancements and issues are addressed in APARs OA39626/OA40072/OA40196 (PTF UA65847/UA66106/UA66338) and APARs OA39630/OA40162 (HKDS623 PTF UA65846/UA66248):
A. 3Q12A Enhancements:
======================================================================
Hide details for RFE: Provide PARMGEN Workflow UI improvements for PARMGEN: A. Configuration Framework Enhancements/Updates RFE: Provide PARMGEN Workflow UI improvements for PARMGEN:
A. Configuration Framework Enhancements/Updates
B. Application Configuration Enhancements/Updates
  • RFE: Provide PARMGEN Workflow UI improvements for:
A. PARMGEN Configuration Framework Enhancements/Updates :
  1. Update the WCONFIG(KCIJ$NDX) Job Index input to the "$JOBINDX Review PARMGEN job index." option on the "KCIP@PG0 ------ PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME" main menu to include the write-up of the KCIJPMNT/KCIJVMNT composite auto-SUBMIT maintenance jobs.
  2. Provide better grouping of parameters in the PARMGEN CONFIG profiles by adding "Related PARMGEN CONFIG profile parameters:" in a number of Self-Describing Agent (SDA)-related parameters, Security-related parameters, OMEGAMON Enhanced 3270UI-related parameters and cross-dependencies with the TEMS DRA, Persistent Datastore-related parameters, etc.
  3. Allocate the "RTE_X_SECURITY_EXIT_LIB" global security exit library automatically as part of the xKANSAMU(KCIJPALO) RTE Build/Allocation job, if the dataset does not already exist.
  4. Provide "Welcome to the z/OS Installation and Configuration Tools for IBM Tivoli Management Services (TMS) dependent products" JOBGEN/PARMGEN integration and checklists welcome screen enhancements as follows:
* Support printable checklists for these index topics:
Checklist: Planning and Acquisition
Checklist: Prepare the system
Checklist: Review the product components & installation steps
Checklist: Complete the post-configuration steps
About joining the community: Service Management Connect (SMC)
* Provide a help panel update to highlight:
Maintenance Level Information:
A. Installation Tool:
1. Install Job Generator (JOBGEN) - Last updated by PTF UAxxxxx
B. Configuration Tools:
1. Parameter Generator (PARMGEN) - Last updated by PTF UAxxxxx
2. ICAT - Last updated by PTF UAxxxxx
* Provide a help panel update to highlight:
- ISPF CUAATTR Consideration for Scrollable Panels
- Operational Requirements and Considerations such TSO region size, PARMGEN configuration values stored in
user's ISPF profile dataset (&&SYSUID..ISPF.ISPPROF)
===END " Sub-section: A. 3Q12A RFEs>>A. Configuration Framework Enhancements/Updates :"

B. PARMGEN-supported Application Configuration Enhancements/Updates :
  1. OMEGAMON Enhanced 3270UI: Support a faster KOBAGENT Data Retrieval Agent (DRA) startup in the z/OS TEMS address space, when the TEMS starts up the DRA. Symptom: It takes a minimum of 3 minutes and 10 seconds for the Tivoli OMEGAMON Manager (TOM) address space to start communicating with the z/OS TEMS that starts up the DRA because the TEMS has a built-in 3-minute delay for the TEMS itself to completely come up prior to starting up any of the Agents. Resolution: Modify the KDSSTART and KDSSTRT1 xKANCMDU startup members in the TEMS to invoke startup of the KOBAGENT DRA module immediately after the TEMS is initialized (CTDS STARTUP command).
  2. Tivoli Enterprise Monitoring Server (TEMS): Provide a new standalone VSAM REPRO sample job called KDSRPOJB in xKANSAMU of which function is equivalent to the REPROKMS step of the xKANSAMU(KCIJPLOD) RTE Load job.
  3. OMEGAMON XE for DB2 PE/PM V5.1.1: Provide a new standalone VSAM REPRO sample job called KD5RPOJB in xKANSAMU of which function is equivalent to the REPROKD5 step of the xKANSAMU(KCIJPLOD) RTE Load job.
  4. OMEGAMON XE for DB2 PE/PM V4.2.0 and higher versions: Increase allowable KD2_PFnn_HIS_LOGx Near-Term History (NTH) VSAM libraries from 3 to 7.
  5. OMEGAMON XE for DB2 PE/PM V4.2.0 and higher versions: Use the KD2_CUA_VTAM_VTPOOL_PREFIX value as the Virtual Terminal Pool Prefix instead of KD2_CUA_VTAM_APPL_PREFIX in the xKD2SAM VTAM major node member (CTDD2N1 by default).
  6. OMEGAMON XE on z/OS V4.2.0 and V5.1.0: Provide a new standalone VSAM REPRO sample job called KM5RPOJB in xKANSAMU of which function is equivalent to the REPROKM5 step of the xKANSAMU(KCIJPLOD) RTE Load job.
  7. OMEGAMON XE on z/OS V4.2.0 and V5.1.0: Provide a new standalone RKM2EDSn/RKM2PROF Epilog VSAM allocation sample job called KM2EALJB in xKANSAMU of which function is equivalent to the KM2JPAL5 step of the xKANSAMU(KCIJPALO) RTE Build/Allocation job.
  8. OMEGAMON XE for Messaging (WebSphere Message Broker) V7.0.1: Provide a new standalone VSAM REPRO sample job called KQIRPOJB in xKANSAMU of which function is equivalent to the REPROKQI step of the xKANSAMU(KCIJPLOD) RTE Load job.
  9. OMEGAMON XE for Messaging (WebSphere MQ Monitoring) V7.0.1: Provide an initial default copy for TKANSAM(KMQPCT00) member into the RKANSAMU user library by renaming the member to CTKMQ00 from TKANSAM to RKANSAMU (copied/renamed without replace) so customers have a convenient copy ready for customization if needed.
  10. OMEGAMON XE for IMS V4.2.0: Remove configuration support for the following xKANPARU(KI2TRFnn) runtime member parameters (NTH=%KI2_CLASSIC_TRF_NTH%, MBR=%KI2_CLASSIC_TRF_NTTS%, TOTTRANS=%KI2_CLASSIC_TRF_STOR%, ) in support of HKI5420 PTF UA65624.
  11. OMEGAMON XE for IMS V4.2.0: Increase the configuration default MINIMUM(%KI5_AGT_STORAGE_MINIMUM_EXTEND%,X) value for this MINIMUM() parameter in the xKANPARU(KI5SYSIN) TMS:Engine startup parameter for OMXE for IMS Agent to avoid storage quiesce issues.
  12. OMEGAMON XE for IMS V4.2.0: Provide a new KI5_X_ICT_IMS_CONNECT_FLAG IMS Connect function flag to ensure that the default IMS.SCEXLINK and IMS.SFUNLINK IBM-supplied default library names are not automatically concatenated in the STEPLIB DDNAME of the OMXE for IMS Agent started task when the IMS Connect function is not in use.
  13. OMEGAMON XE for IMS V4.2.0: Automatically assemble the KOIGBL&mp Global Data module in the RTE's RKANMODU library via the composite WKANSAMU(KCIJPLNK) assembly/link job or via the WKANSAMU(KI2GBL&mp) standalone KOIGBL&mp assembly job using the xKANSAMU(KOIGBL&mp) global sample.
  14. OMEGAMON XE for Mainframe Networks V4.2.0: Provide support for GBL_DSN_TCP_PROFILES $GBL$IBM/$GBL$USR global profile parameter that can be reused for product-specific paramenters such as KN3_TCPXnn_TCPIP_PROFILES_DSN of which value is used to populate the product's xKANPARU(KN3TCPMO) "Define TCP/IP monitored systems for OMEGAMON XE for Mainframe Networks Agent" runtime member.
  15. OMEGAMON XE for Mainframe Networks V4.2.0: Increase the KN3_PD_CYL Persistent Datastore cylinder size allotment for the RKN3HIS* PDS libraries allocated by the xKANPARU(KN3AL) PDS allocation member used by the composite xKANSAMU(KCIJPALO) composite RTE build/allocation job.
  16. OMEGAMON XE for CICS V4.2.0 and V5.1.0: Provide new standalone external security sample jobs for RACF, ACF2 and TopSecret under these standardized names (KOCRACFA, KOCACF2A, and KOCTOPSA) in the xKANSAMU library for consistency with the other three OMEGAMON products (OMEGAMON DB2, IMS, and z/OS) that provide similar-named jobs.
  17. OMEGAMON DE on z/OS V4.2.0 and V5.1.0 (OMEGAVIEW component): Default the KMV_PPI_* TMS:Engine Take Action parameters as null (disabled) so the OMEGAVIEW address space (KMV_CUA_STC) does not enable the SYSTCPD DD if the GBL_DSN_NETVIEW_CNMLINK parameter is not set in the RTE's WCONFIG($GBL$USR) global CONFIG profile.
===END " Sub-section: A. 3Q12A RFEs>>B. Application Configuration Enhancements/Updates :"
===END " Sub-section: A. 3Q12A RFEs"
======================================================================
===END " Sub-section: A. 3Q12A Enhancements"
======================================================================

B. 3Q12A Issues:
Hide details for SYMPTOM: In certain installations, the Tivoli Enterprise Monitoring Server (TEMS) gets the following messages SYMPTOM: In certain installations, the Tivoli Enterprise Monitoring Server (TEMS) gets the following messages in the TEMS RKLVLOG: "KDCS_UseFamily") status=1c010005, Endpoint unresponsive CT/DS:{SERVER=SRVR01 USER=OB} "Find_HUB") KOBDRA76E Unable to conne
======================================================================
  • SYMPTOM: In certain installations, the Tivoli Enterprise Monitoring Server (TEMS) gets the following messages in the TEMS RKLVLOG indicating TEMS and KOBAGENT DRA Agent timeout issues: "(001A-D3E8C823:kdcsuse.c,120,"KDCS_UseFamily") status=1c010005, "cant bind socket", ncs/KDC1_STC_CANT_BIND_SOCKET Connection failure: "ip.pipe:#x.x.x.x:1918 status=1c020006, "location server unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE Endpoint unresponsive: "ip:#x.x.x.x:1918", 1C010001:1DE0000F, 33, CT/DS RPC Error: DSR031 - CTDS_CreatePath RPC abend status=1c020006, "location server unavailable", ncs/KDC 5,"socket__inq_my_netaddr") status=10020002, "socket buffer too small", ncs/KDC1 CT/DS status returned: 155 Check local failed. status = 5 Create Path Error. status 155 path NCS:{SOCKET=sna:&netid.CTDDSLB } CT/DS:{SERVER=SRVR01 USER=OB} "Find_HUB") KOBDRA76E Unable to connect the the TEMS" .
  • DESCRIPTION: In certain cases, the KOBAGENT IRAMAN startup in &rhilev.&rte.RKANCMDU(KDSSTART) member needs to be delayed in starting the DRA before the TEMS CTDS STARTUP fully initializes. The timeout issues may occasionally happen causing the TEMS to encounter the RKLVLOG messages noted in the symptoms.
  • WORKAROUND/TIP: : The more permanent resolution will be in a future HKOB700 PTF. In the interim, a configuration change will supply a KDSSTART member with a 1-minute delay in the KOBAGENT startup instead of the current 10-second delay after CTDS STARTUP for the TEMS. The KDSSTART configuration change will be delivered in HKCI310 PTF UA66338 and HKDS623 PTF UA66248 when available. As a circumvention until the PTFs are available, perform the following steps if the TEMS/KOBAGENT timeout issues are encountered:

1. In the &rhilev.&rte.RKANCMDU(KDSSTART) TEMS startup member, increase the delay interval in starting up the KOBAGENT DRA by increasing the "DELAY=hh:mm:ss" parameter to one minute, as shown in the example below:
AT ADD ID=KOB DELAY=00:01:00 CMD='IRAMAN KOBAGENT START'
=====

2. If you have the following products installed @ these GA versions, and configured in the RTE where the TEMS is running:
- OMEGAMON XE for CICS V5.1.0
- OMEGAMON XE for DB2 V5.1.1
- OMEGAMON XE on z/OS V5.1.0

Then ensure that the following &rhilev.&rte.RKANDATV now-obsolete catalog files are removed from the TEMS RTE's RKANDATV library prior to recycling the TEMS:
===========================================================
EDIT &rhilev.&rte.RKANDATV
Command ===>
Name
_________ KC5ATR
_________ KC5CAT
_________ KD5ATR
_________ KD5CAT
_________ KHLATR
_________ KHLCAT
===========================================================

These products @ the latest GA versions either renamed their RKANDATV catalog and attribute files in the new upgraded versions or have been subsumed by another product's catalog and attribute files. The existence of these members in RKANDATV might cause slight delays in the TEMS starting up, to which the TEMS will log the following duplicate attribute messages, as shown in the example below:
===========================================================
(0001-C769FC4B:kglatrvl.c,193,"add_to_index") Warning: attribute name conflict
(0006-C769FC4B:kglatrbk.c,893,"atrblk_set_format") app <OMCICS>table <CICSEVD> column <CAPTURE> file <KC5ATR> timestamp
<1110601172956000> line <5926>
.
.
(70C6-C769FC4B:kglatrvl.c,194,"add_to_index") app <KDP> table <KDP_CFG> column <ORIGINNODE>
(70C7-C769FC4B:kglatrvl.c,194,"add_to_index") file <KDPATR> timestamp <1120426032318000> line <3>
.
.
(282F-C769FC4B:kglatrvl.c,195,"add_to_index") app <KM5> table <HLHCHKS> column <ORIGINNODE>
(2830-C769FC4B:kglatrvl.c,195,"add_to_index") file <KM5ATR> timestamp <1120502060715000> line <29579>
.
(2F99-C769FC4B:kglatrvl.c,195,"add_to_index") enum count
==========================================================

These duplicate attribute messages might contribute to the TEMS/KOBAGENT DRA timeout so remove the obsolete RKANDATV files when the RKANDATV library is available. The ICAT or PARMGEN RTE Load job (pp#2xxxx ICAT / KCIJPLOD PARMGEN) typically deletes these members via its DELRUN clean-up step but if the RTE load job is not able to get exclusive enqueue on the RKANDATV library, the RTE Load job provides a warning condition code.

Note that this should only be done after having verified that: (a) the product in question has indeed been upgraded in the RTE and (b) the above indicated messages are being written to the TEMS RKLVLOG dataset.
======================================================================

Hide details for SYMPTOM: After applying PTF UA64407, the OMEGAMON XE on z/OS Epilog started task (CANSM2HI by default) created SYMPTOM: After applying PTF UA64407, the OMEGAMON XE on z/OS Epilog started task (CANSM2HI by default) created by PARMGEN encounters an "*EC839: INPUT PARAMETERS INVALID: CORRECT AND RERUN" message ending in COND CODE 2048 at startup.
======================================================================
  • SYMPTOM: After applying PTF UA64407, the OMEGAMON XE on z/OS Epilog started task (CANSM2HI by default) created by PARMGEN encounters an "*EC839: INPUT PARAMETERS INVALID: CORRECT AND RERUN" message ending in COND CODE 2048 at startup.
  • DESCRIPTION: Modify WCONFIG(KEP$POPT) KEPOPTN override imbed member for the Epilog Collection startup member to reformat the EDSLIST() parameter syntax as required by the Epilog Collector. In the EDSLIST() parameter, append the ending ")" parenthesis in the last %KM2_HIST_DSTOR_RKM2EDS_DSNn% VSAM library as opposed to being generated on the next line separate from the last VSAM line.
  • WORKAROUND/TIP: : Apply the resolving 3Q12A HKCI310 PTF UA66106 (APAR OA39626/OA40072) when available. After applying the PTF, either implement Workaround A1 below or rename the WCONFIG(KEP$POPT) member and rerun PARMGEN KCIJPUP1 job so a new, corrected version (corrected version) of KEP$POPT member is copied to WCONFIG.

For the timebeing, there are 2 workarounds available (A or B):
A1. For a more permanent change, edit the WCONFIG(KEP$POPT) Epilog override imbed to replace the contents of lines #246 - #253 " From: " section below with lines #260 - #267 " To: " section as shown below:
From:
EDIT IBM.LPAR1.WCONFIG(KEP$POPT)
Command ===>
000243 OPTIONS EDSDATA -
000244 NOPDSDATA -
000245 EDSLIST( -
000246 %CMTM2P6%%KM2_HIST_DSTOR_RKM2EDS_DSN1%
000247 %CMTM2P7%%KM2_HIST_DSTOR_RKM2EDS_DSN2%
000248 %CMTM2P8%%KM2_HIST_DSTOR_RKM2EDS_DSN3%
000249 %CMTM2P9%%KM2_HIST_DSTOR_RKM2EDS_DSN4%
000250 %CMTM2P10%%KM2_HIST_DSTOR_RKM2EDS_DSN5%
000251 %CMTM2P11%%KM2_HIST_DSTOR_RKM2EDS_DSN6%
000252 %CMTM2P12%%KM2_HIST_DSTOR_RKM2EDS_DSN7%
000253 ) -
000254 EDSSWITCH(FULL) -

To:
EDIT IBM.LPAR1.WCONFIG(KEP$POPT)
Command ===>
000257 OPTIONS EDSDATA -
000258 NOPDSDATA -
000259 EDSLIST( -
000260 %CMTM2P6%%KM2_HIST_DSTOR_RKM2EDS_DSN1% %KM2_I_EDSPREN1% -
000261 %CMTM2P7%%KM2_HIST_DSTOR_RKM2EDS_DSN2% %KM2_I_EDSPREN2% -
000262 %CMTM2P8%%KM2_HIST_DSTOR_RKM2EDS_DSN3% %KM2_I_EDSPREN3% -
000263 %CMTM2P9%%KM2_HIST_DSTOR_RKM2EDS_DSN4% %KM2_I_EDSPREN4% -
000264 %CMTM2P10%%KM2_HIST_DSTOR_RKM2EDS_DSN5% %KM2_I_EDSPREN5% -
000265 %CMTM2P11%%KM2_HIST_DSTOR_RKM2EDS_DSN6% %KM2_I_EDSPREN6% -
000266 %CMTM2P12%%KM2_HIST_DSTOR_RKM2EDS_DSN7% %KM2_I_EDSPREN7% -
000267 EDSSWITCH(FULL) -


A2. Edit WCONFIG($PARSEPR) job to filter on regenerating the KEP* members only. You also have the option to point SYSUT2 DD directly to RKANPARU instead of the default WKANPARU PARMGEN work library.
EDIT IBM.LPAR1.WCONFIG($PARSEPR)
Command ===>
000164 CONFIG MEMBER=(WCONFIG:LPAR1)
000165 SELECT MEMBER=(KEP*)

A3. Submit WCONFIG($PARSEPR) job to regenerate the KEPOPTN member. Refresh RKANPARU with this version accordingly (if you did not point SYSUT2 DD to RKANPARU directly).

-or-

B. Backup the RTE's RKANPARU(KEPOPTN) member. Then edit the member to add a '-' continuation character at the end of each %KM2_HIST_DSTOR_RKM2EDS_DSNn% VSAM library and moving the ") -" ending parenthesis after the " IBM.LPAR1.RKM2EDS3 " statement as shown on lines #253, #254, and #255 below:
EDIT IBM.LPAR1.RKANPARU(KEPOPTN)
Command ===>
000252 EDSLIST( -
000253 IBM.LPAR1.RKM2EDS1 -
000254 IBM.LPAR1.RKM2EDS2 -
000255 IBM.LPAR1.RKM2EDS3 ) -
000256 * -
000257 * -
000258 * -
000259 * -
000260 EDSSWITCH(FULL) -

======================================================================

Hide details for SYMPTOM: If an RTE is enabled for System Variables (RTE_SYSV_SYSVAR_FLAG=Y), re-running then KCIJVMNT/KCIJPMNV SYMPTOM: If an RTE is enabled for System Variables (RTE_SYSV_SYSVAR_FLAG=Y), re-running then KCIJVMNT/KCIJPMNV jobs does not recreate the product started tasks and VTAM major node members in WKANSAMU.
======================================================================
  • SYMPTOM: If an RTE is enabled for System Variables (RTE_SYSV_SYSVAR_FLAG=Y), re-running then KCIJVMNT/KCIJPMNV jobs does not recreate the product started tasks and VTAM major node members in WKANSAMU.
  • DESCRIPTION: When submitting the KCIJVMNT job, it submits the KCIJPMNV composite job that contains the SUBMIT commands to auto-submit a series of other jobs, as shown below. KCIJPMNV job also needs to include the KCIJVUPV job:
EDIT IBM.ITM62351.LPAR1.WKANSAMU(KCIJPMNV) - 01.0 Columns 00001 0007
Command ===> Scroll ===> CSR
****** ***************************** Top of Data ****************************
000001 //KCIJPMNV JOB (ACCT),'DAY',CLASS=A,
000002 // MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M
000003 //** RTE_NAME=&SYSNAME. SYSJOBNAME=KCIJPMNV
000004 //** SYSMEMBER=KCIJPMNV
000005 //* ******************************************************************
000006 //*
000007 //* NAME: KCIJPMNV
000008 //*
000009 //* PURPOSE: *** System Variables version of KCIJPMNT job ***
000010 //* *** For RTEs enabled for System Variables support ***
000011 //*
000012 //* Submit the composite KCIJPMNV maintenance auto-SUBMIT
000013 //* job to update the runtime environment (&SYSNAME.),
000014 //* after applying maintenance. This job submits these
000015 //* additional jobs.
000016 //* 1. WCONFIG(KCIJPUP1) composite TK*->IK* IEBUPDTE job
000017 //* 2. WCONFIG($PARSESV) IK*->WK* create runtime members job
000018 //* 3. WKANSAMU(KCIJVLOD) composite TK*->RK*
000019 //* runtime library RTE load job
000020 //* 4. WKANSAMU(KCIJVUPV) System Variables IEBUPDTE job
000021 //* 5. WKANSAMU(KCIJVIVP) configuration verification job
000022 //* 6. **WKANSAMU(KCIJVCPY) backup runtime libraries job
000023 //* 7. **WKANSAMU(KCIJVW2R) WK*->RK* deployment job
000024 //* ** Note: Review the NOTES section of KCIJPMNV to
000025 //* see if certain jobs should be auto-submitted or
000026 //* not auto-submitted by KCIJPMNV.
000027 //*
000028 //* INSTRUCTIONS:
000029 //* 1. (OPTIONAL) Prior to running KCIJPMNV, review both KCIJPCPY and
000030 //* KCIJPW2R jobs, to determine if they should be auto-submitted by
000031 //* KCIJPMNT. WKANSAMU(KCIJPW2R) sample job deploys the updated
000032 //* runtime member(s) from WK* libraries to RK* production user
000033 //* libraries (RKANCMDU, RKANPARU, RKANSAMU). An alternative is to
000034 //* modify the PARMLIB-created STC's new USER%%%U PROC symbols to
000035 //* run from the WK* libraries for a quick test prior to copying
000036 //* the updated WK* runtime members to the production RK* user
000037 //* libraries.
000038 //* Tip: Each site has different change control procedures.
000039 //* Certain sites deploy these types of changes by renaming
000040 //* the current production RK* libraries to RK*.Dyymmdd
000041 //* backup, then renaming the latest WK* set to RK*. Sample
000042 //* deployment/backup jobs WKANSAMU(KCIJPCPY) and
000043 //* WKANSAMU(KCIJPW2R) provide helpful samples.
000044 //*
000045 //* If you want the KCIJPMNV job to submit them, remove the starting
000046 //* comment "/*" on columns #1-#2 of the respective SUBMIT command,
000047 //* as shown in the example below on lines #78 and #79:
000048 //* Example:
000049 //* =COLS> ----+----1----+----2----+----3----+----4----+----5----+
000050 //* 000078 /* SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVCPY
000051 //* 000079 /* SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVW2R
000052 //* 2. Submit the KCIJVMNT job and check for good condition codes.
000053 //*
000054 //* *******************************************************************
000055 //SUBMITC EXEC PGM=IEBUPDTE,PARM=NEW
000056 //SYSPRINT DD DUMMY
000057 //SYSUT2 DD DSN=&&TEMPPC,DISP=(,PASS),
000058 // UNIT=SYSDA,SPACE=(TRK,(10,10,10)),
000059 // DCB=(RECFM=FB,LRECL=80,BLKSIZE=8880)
000060 //SYSIN DD DATA,DLM=$$
000061 ./ ADD NAME=SUBMITC
000062 PROC 0
000063 CONTROL NOMSG NOFLUSH ASIS
000064 SUBMIT ('IBM.ITM62351.&SYSNAME..WCONFIG(KCIJPUP1)')
000065 SUBMIT ('IBM.ITM62351.&SYSNAME..WCONFIG($PARSESV)')
000066 SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVLOD)')
000067 SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVUPV)') <-- missing
000068 SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVIVP)')
000069 /* SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVCPY)')
000070 /* SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVW2R)')
000071 EXIT CODE(0)
000072 $$
000073 //SUBMITJB EXEC PGM=IKJEFT01,DYNAMNBR=64
000074 //SYSTSPRT DD SYSOUT=*
000075 //SYSPROC DD DISP=(OLD,DELETE),DSN=&&TEMPPC
000076 //SYSTSIN DD *
000077 %SUBMITC
000078 /*
  • WORKAROUND/TIP: : Apply the resolving 3Q12A HKCI310 PTF UA66106 (APAR OA39626/OA40072) when available. For the timebeing, prior to submitting WKANSAMU(KCIJVMNT) job, edit the KCIJPMNV job that KCIJVMNT processes. In WKANSAMU(KCIJPMNV), add the SUBMIT statement for the KCIJVUPV job as shown on line #67 in the "To:" reference below. Then submit the composite WKANSAMU(KCIJVMNT), which in turn submits the modified KCIJPMNV.
From:
000061 ./ ADD NAME=SUBMITC
000062 PROC 0
000063 CONTROL NOMSG NOFLUSH ASIS
000064 SUBMIT ('IBM.ITM62351.&SYSNAME..WCONFIG(KCIJPUP1)')
000065 SUBMIT ('IBM.ITM62351.&SYSNAME..WCONFIG($PARSESV)')
000066 SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVLOD)')
000067 SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVIVP)')
000068 /* SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVCPY)')
000069 /* SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVW2R)')
000070 EXIT CODE(0)
000071 $$


To:
000061 ./ ADD NAME=SUBMITC
000062 PROC 0
000063 CONTROL NOMSG NOFLUSH ASIS
000064 SUBMIT ('IBM.ITM62351.&SYSNAME..WCONFIG(KCIJPUP1)')
000065 SUBMIT ('IBM.ITM62351.&SYSNAME..WCONFIG($PARSESV)')
000066 SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVLOD)')
000067 SUBMIT ('IBM.&SYSNAME..WKANSAMU(KCIJVUPV)')
000068 SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVIVP)')
000069 /* SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVCPY)')
000070 /* SUBMIT ('IBM.ITM62351.&SYSNAME..WKANSAMU(KCIJVW2R)')
000071 EXIT CODE(0)
000072 $$

Notes:
  1. In a future PARMGEN IF, the "KCIJPMNT/KCIJVMNT" job option will be available for selection on the PARMGEN "KCIP@SUB -------- SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP" panel.
  2. An alternative to get to the WKANSAMU library to edit these jobs is to navigate to the "U" (Utilities) option on the "KCIP@PG0 ------ PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME" main menu, and select sub-option "3. WKANSAMU %RTE_PLIB_HILEV%.%RTE_NAME%.WKANSAMU"
======================================================================

Hide details for SYMPTOM: When submitting PARMGEN jobs, one might encounter a benign SYMPTOM: When submitting PARMGEN jobs, one might encounter a benign "PROCESS ABORTED" short message on the screen although the job gets submitted successfully.
======================================================================
  • SYMPTOM: When submitting PARMGEN jobs, one encounters a benign "PROCESS ABORTED" short message on the screen although the job gets submitted successfully, if site uses 7-digit JES Job numbers.
  • DESCRIPTION: The PARMGEN Job submitter code currently accommodates 5-digit JES Job numbers.
  • WORKAROUND/TIP: : Apply the resolving 3Q12A HKCI310 PTF UA66106 (APAR OA39626/OA40072) when available. For the timebeing, backup the KCIR@PG1 and KCIRSUB1 PARMGEN REXX execs. in your %GBL_TARGET_HILEV%.TKANCUS library. Then edit the respective REXX execs. as follows:

KCIR@PG1 - see lines #1152, #1155 - #1157
EDIT IBM.ITM62351.TKANCUS(KCIR@PG1)
Command ===> Scroll ===> CSR
****** ***************************** Top of Data ****************************
.
001149 sdate = SUBJDATE
001150 stime = SUBJTIME
001151 IF (SUBJNAME \= ""),
00 1152 & (SUBSTR(SUBJNUM,1,1) = "J") ---> updated to this
001153 THEN DO
001154 SUBJNAME = STRIP(SUBJNAME)
00 1155 IF (SUBSTR(SUBJNUM,1,3) = "JOB") ---> updated to this
00 1156 THEN SUBJNUM = SUBSTR(SUBJNUM,4) ---> updated to this
00 1157 ELSE SUBJNUM = SUBSTR(SUBJNUM,2) ---> updated to this
001158 PLBPOP1 = "Job "job" submitted."
001159 PLBPOP2 = "JOBNAME:" SUBJNAME

KCIRSUB1 - see lines #40
EDIT IBM.ITM62351.TKANCUS(KCIRSUB1)
Command ===> Scroll ===> CSR
****** ***************************** Top of Data ****************************
.
000035 DO i = 1 TO msg.0
000036 SAY z_rexx msg.i
000037 PARSE VALUE "X" msg.i WITH,
000038 . " JOB " SUBJNAME "(" SUBJNUM ")" .
000039 IF (SUBJNAME \= ""),
0000 40 & (SUBSTR(SUBJNUM,1,1) = "J") ---> updated to this
000041 THEN ADDRESS "ISPEXEC",
000042 "VPUT (SUBJNAME SUBJNUM SUBJDATE SUBJTIME) SHARED"
======================================================================

Hide details for SYMPTOM: If an RTE is enabled for System Variables and multiple KPDPROC1 jobs are submitted from the same syst SYMPTOM: If an RTE is enabled for System Variables and multiple KPDPROC1 jobs are submitted from the same system, a dataset contention may occur. Message DATA SET
&hilev.TMPSYSIN, TMPPARU, ALREADY IN USE, TRY LATER may
show up in the output.
======================================================================
  • SYMPTOM: If an RTE is enabled for System Variables and multiple KPDPROC1 jobs are submitted from the same system, a dataset contention may occur. Message DATA SET &hilev.TMPSYSIN, TMPPARU, ALREADY IN USE, TRY LATER may show up in the output.
  • DESCRIPTION: When multiple KPDPROC1 jobs are submitted from the same system, a dataset contention may occur. Message DATA SET &hilev.TMPSYSIN, TMPPARU, ALREADY IN USE, TRY LATER may show up in the output. If an RTE is enabled for System Variables ("RTE_SYSV_SYSVAR_FLAG" parameter in the CONFIG profile is set to "Y"), the KPDPROCC code executed by the KPDPROC1 started task is currently generated with common dataset allocations for &hilev.TMPSYSIN and &hilev.TMPPARU libraries. These libraries are used by the PARMGEN process to resolve the System Variables and they currently must be allocated as cataloged datasets for the duration of the KPDPROC1 execution as the Persistent Datastore code requires non-temporary datasets.
  • WORKAROUND/TIP: : Apply the resolving 3Q12A HKCI310 PTF UA66106 (APAR OA40072) when available. For the timebeing, backup the RKANSAMU(KPDPROCC) REXX exec. then edit the member as follows (note that the RTE HLQ being used in this example is "IBM.LPAR1" -- substitute to your values accordingly):

000146 len = length(IBM.LPAR1.R) - 2
000147 hilev2 = left(IBM.LPAR1.R,len)
000148 volser = VOL001
000149 unit = SYSALLDA
000150 storclas = SCLASS
000151 mgmtclas = MCLASS
.
.
000477 /* Begin - Add KCIPARSE support
000478 LEN_PDCTL = length(PDCTL)
000479 LEN_PDCTL2 = length(PDCTL2)
000480 parse var PDCTL CTLDSN "(" CTLMBR ")"
000481 parse var PDCTL2 CTL2DSN "(" CTL2MBR ")"
000482 PDCTLX = PREF".RKANPARU("CTLMBR")"
000483 PDCTL2X = PREF".RKANPARU("CTL2MBR")"
000484 LEN_PDCTLX = length(PDCTLX)
000485 LEN_PDCTL2X = length(PDCTL2X)
000486 if length(PDCTLX) \= length(PDCTL) THEN PDCTL = PDCTLX
000487 if length(PDCTL2X) \= length(PDCTL2) THEN PDCTL2 = PDCTL2X
000488 I -
000489 I - /* Delete TMPSYSIN if it exists for clean-up purposes. SYSIN will
000490 I - /* now be passed on to KCIRPLB1 PARMGEN PDS symbolic substitution
000491 I - /* code instead of a cataloged TMPSYSIN dataset.
000492 TMPSYSIN = PREF".TMPSYSIN"
000493 I - STATUS_TMPSYSIN = SYSDSN("'"TMPSYSIN"'")
000494 I - IF STATUS_TMPSYSIN = "OK" THEN "DELETE '"TMPSYSIN"'"
000495 I -
000496 I - /* Input to KCIRPLB1 KCIPARSE code that has PDS runtime members
000497 I - /* with symbolics. Values passed on to KPD* code needs to be
000498 I - /* resolved (KPD* code requirement).
000499 TMPPARI = PREF".RKANPARU"
000500 I -
000501 I - /* Use RECSUF as the basis for lowlev. but extract the last 2 chars
000502 I - /* to remove ".R" to keep the TMPPARO output unique per KPDPROC1-
000503 I - /* invoked process per started task that invokes PDS maintenance.
000504 I - LENRSUF = length(RECSUF) - 2
000505 I -
000506 I - /* RECSUF today will be an issue for PREF can be max 35 chars. so
000507 I - /* replace "Rxxxxxxn" w/ "Pxxxxxxn" (example, RGENHIS1 to PGENHIS1
000508 I - /* if RGENHIS1 will be processed for PDS maintenance).
000509 I - TMPPARX = OVERLAY("P",left(RECSUF,LENRSUF),1,1)
000510 I -
000511 I - /* Temporary output to KCIRPLB1 KCIPARSE code where resolved member
000512 I - /* are written to (example: &PREF.PGENHIS1)
000513 I - TMPPARO = PREF"."TMPPARX
000514 I -
000515 I - /* If System Variables is enabled, perform symbolic substitution
000516 D - TMPPARO = PREF".TMPPARU"
000517 D - "FREE F(KANPARU TMPPARU SYSIN)"
000518 IF sysvar_flag = "Y" THEN DO
000519 I - /* Allocate RKANPARU input
000520 D - "DELETE '"TMPSYSIN"'"
000521 D - "DELETE '"TMPPARO"'"
000522 "ALLOC F(KANPARU) DA('"TMPPARI"') SHR"
000523 I -
000524 I - /* Allocate Pxxxxxxn output if it does not exist
000525 I - STATUS_TMPPARO = SYSDSN("'"TMPPARO"'")
000526 I - IF STATUS_TMPPARO \= "OK" &,
000527 I - STATUS_TMPPARO \= "UNAVAILABLE DATASET"
000528 I - THEN DO
000529 I - "ALLOC F(TMPPARU) DA('"TMPPARO"') NEW CATALOG REUSE",
000530 I - "RECFM(F,B) LRECL(80) BLKSIZE(8800) TRACK SPACE(150,30) ",
000531 I - "DIR(88)" volspec unispec stospec mgmspec
000532 I - END
000533 I - ELSE "ALLOC F(TMPPARU) DA('"TMPPARO"') SHR REUSE"
000534 I -
000535 I - /* Allocate SYSIN temporary dataset
000536 I - "ALLOC F(SYSIN) REUSE",
000537 D - "ALLOC F(TMPPARU) DA('"TMPPARO"') NEW ",
000538 D - "LIKE('"TMPPARI"') " volspec unispec stospec mgmspec
000539 D - "ALLOC F(SYSIN) DSN('"TMPSYSIN"')",
000540 D - "NEW REUSE CATALOG RECFM(F,B)",
000541 "TRACKS SPACE(5,5) DSORG(PS) LRECL(80) ",
000542 I - "BLKSIZE(27920) "
000543 I -
000544 I - /* Perform symbolic substitution using KCIPARSE
000545 D - "BLKSIZE(27920) " volspec unispec stospec mgmspec
000546 "EX 'IBM.LPAR1.RKANCMD(KCIRPLB1)' 'KCIPRM(LV=S)",
000547 "LOADLIB(IBM.LPAR1.RKANMOD) CALLER(KPDPROCC)'"
000548 END
000549 PDCTL_ALLOC = PDCTL
000550 PDCTL2_ALLOC = PDCTL2
000551 IF sysvar_flag = "Y" THEN DO
000552 PDCTL_ALLOC = TMPPARO"("CTLMBR")"
000553 PDCTL2_ALLOC = TMPPARO"("CTL2MBR")"
000554 END
000555 /* End - Add KCIPARSE support
.
.
000899 I - /* Begin - Add KCIPARSE support
000900 I - /* Temporary output to KCIRPLB1 KCIPARSE code where resolved member
000901 I - /* are written to (example: &PREF.PGENHIS1). Delete dataset upon e
000902 I - /* if the file exists.
000903 I - "FREE F(KANPARU TMPPARU SYSIN)"
000904 I - STATUS_TMPPARO = SYSDSN(TMPPARO)
000905 I - IF STATUS_TMPPARO = "OK" THEN "DELETE '"TMPPARO"'"
000906 I - /* End - Add KCIPARSE support
000907 Say " "
000908 Say "Maintenance complete, return code = " pd_ret
000909 Say " "
000910 exit pd_ret
.
.
000932 D - /* Begin - Add KCIPARSE support
000933 D - "FREE F(KANPARU TMPPARU SYSIN)"
000934 D - /* End - Add KCIPARSE support
============================================
  • Enablement steps when the fixing PTF UA66106 is applied:
Note: See 3Q12A "What's New" section for general HOLDDATA considerations about UA66106. Specific to this KPDPROCC change:
  1. Invoke PARMGEN by executing the &gbl_target_hilev.TKANCUS library.
  2. Rerun the WCONFIG(KCIJPUP1) job (option "KCIJPUP1 Update interim libraries and create profiles." on the PARMGEN Workflow main menu KCIP@PG0 panel) in order to update the RTE's IKANSAMU library with the updated KPDPROCC PARMGEN template.
  3. Edit and submit the WCONFIG($PARSESM) job from the $PARSE option from KCIP@PG0 (option "$PARSE Create the RTE members and jobs." $PARSESM only recreates the members that get populated in the WKANSAMU library, including the KPDPROCC Persistent Datastore REXX exec.
3a. Edit the WCONFIG($PARSESM) job to filter on the specific member that needs to be regenerated, as shown on line #138:
ISREDDE2 IBM.LPAR1.WCONFIG($PARSESM)
Command ===> Scroll ===> CSR
000103 //* ===================================================================
000104 //* BEGIN - PART 2 WKANSAMU Step:
000105 //* ===================================================================
000106 //* *******************************************************************
000107 //* WKANSAMU Step: IKANSAMU-->WKANSAMU
000108 //* Process the PARMGEN members from IKANSAMU to WKANSAMU based on $CFG*
000109 //* CONFIG and/or converted PARMGEN RTE Batch deck profile settings.
000110 //* *******************************************************************
000111 //WKANSAMU EXEC PGM=KCIPARSE,
000112 // PARM='MV=32000,MAXL=32000,ML=500,MI=255,MS=20000,LV=Y,LG=10'
000113 //STEPLIB DD DISP=SHR,
000114 // DSN=TSTEST.ITM62351.TKANMOD
000115 //INPUT1 DD DISP=SHR,
000116 // DSN=IBM.LPAR1.IKANSAMU
000117 //INPUT2 DD DISP=SHR,
000118 // DSN=IBM.LPAR1.WKANSAMU
000119 //WCONFIG DD DISP=SHR,
000120 // DSN=IBM.LPAR1.WCONFIG
000121 //SYSUT2 DD DISP=SHR,
000122 // DSN=IBM.LPAR1.WKANSAMU
000123 //SYSPRINT DD SYSOUT=*
000124 //SYSVROUT DD SYSOUT=*
000125 //SYSINLST DD SYSOUT=*
000126 //SYSIN DD *
000127 * *******************************************************************
000128 * Member: KCISYSIN
000129 * Master Source: TSTEST.ITM62351.TKANSAM(KCIPRMLB)
000130 * Purpose: Customer copy of SYSIN control for overriding CONFIG MEMBER=
000131 * CONFIG profile members and SELECT MEMBER= member selection
000132 * list.
000133 * KCIJPUP1 Batch Job Output:
000134 * IBM.LPAR1.WCONFIG($SYSIN) - Customer Copy
000135 * *******************************************************************
000136 * ----------- BEGIN - USER SECTION: CONFIG/SELECT MEMBER ---------- *
000137 * *******************************************************************
000138 * USER SECTION: CONFIG/SELECT MEMBER *
000139 * *******************************************************************
000140 * $VERSION Product/component versions installed in the CSI
000141 CONFIG MEMBER=(WCONFIG:$VERSION)
000142 * 2: $CFGINIT IBM-supplied initialization member
000143 CONFIG MEMBER=(WCONFIG:$CFGINIT)
000144 * 3: $GBL$IBM IBM-supplied PARMLIB CONFIG profile (SMP-related and
000145 * other global-specific parameters)
000146 CONFIG MEMBER=(WCONFIG:$GBL$IBM)
000147 * 4. $CFG$IBM IBM-supplied PARMLIB CONFIG profile (RTE-specific)
000148 CONFIG MEMBER=(WCONFIG:$CFG$IBM)
000149 * 5. $GBL$USR Customer-overridable PARMLIB CONFIG profile (SMP-related
000150 * and other global parameters)
000151 * Note: (OPTIONAL) Customize WCONFIG:$GBL$USR accordingly. It is
000152 * ideal for copying to other WCONFIG RTEs if these global system
000153 * libraries are typically the same across LPARs.
000154 CONFIG MEMBER=(WCONFIG:$GBL$USR)
000155 * 6. MOC05 Customer-overridable PARMLIB CONFIG profile
000156 * (RTE-specific applicable to this LPAR)
000157 CONFIG MEMBER=(WCONFIG:LPAR1)
000158 SELECT MEMBER=(KDS*)
000159 * ----------- END - USER SECTION: CONFIG/SELECT MEMBER ---------- *

3b. (CONDITIONAL) If the RTE is enabled for System Variables, resubmit the WKANSAMU(KCIJVUPV) System Variables IEBUPDTE job to refresh the KPDPROCC member in WKANSAMU. On the KCIP@PG0 PARMGEN Workflow main menu, you can navigate to the KCIJVUPV job via the "SUBMIT - SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP" option>>"5> KCIJVUPV System Variables IEBUPDTE".

4. Copy the refreshed WKANSAMU(KPDPROCC) REXX exec. to the product execution user libraries (RKANSAMU) either via the KCIJPW2R or KCIJVW2R job on the "SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP" sub-menu or by simply copying the member manually.

5. Repeat for each RTE where KPDPROCC needs to be refreshed.
Tip: xKANSAMU(KPDPROCC) is unique to the RTE HLQ being used. Once you have refreshed KPDPROCC for the first RTE, you can reuse the same version for the remaining RTEs and simply change the RTE-specific values such as RTE HLQ, SMS values, etc.
======================================================================

Hide details for SYMPTOM: If the GBL_HFS_JAVA_DIR1 profile parameter is overriden in WCONFIG($GBL$USR) library to a value oth SYMPTOM: If the GBL_HFS_JAVA_DIR1 profile parameter is overriden in
WCONFIG($GBL$USR) library to a value other than the default of "/usr/lpp/java/IBM/J6.0", the
WKANSAMU(KCIJPUSP) composite
USS preparation job continues to use the default.
======================================================================
  • SYMPTOM: After applying PTF UA65847, If the GBL_HFS_JAVA_DIR1 profile parameter is overridden in WCONFIG($GBL$USR) library to a value other than the default of "/usr/lpp/java/IBM/J6.0", the WKANSAMU(KCIJPUSP) composite USS preparation job continues to use the default.
  • DESCRIPTION: The USS prep. job continues to use the default value in the KCIJPUSP job which in turns creates RKANDATV(KDSDPROF) member. Consequently, RKANDATV(KDSDPROF) will generate the TEMS_JAVA_BINPATH=/usr/lpp/java/IBM/J6.0/bin parameter pointing to the default instead of the customized value supplied for GBL_HFS_JAVA_DIR1 parameter. The PARMGEN NOTVAR checking in the WCONFIG($SYS$IBM) code requires updates to the null checking logic.
  • WORKAROUND/TIP: : Apply the resolving 3Q12A HKCI310 PTF UA66106 (APAR OA40072) when available. For the timebeing, edit the WKANSAMU(KCIJPUSP) job and make the changes on line #91 to point to the desired GBL_HFS_JAVA_DIR1 parameter :
EDIT IBM.ITM62351.LPAR1.RKANSAMU(KCIJPUSP)
Command ===> Scroll ===> CSR
000078 //***************************************************************/
000079 //* */
000080 //* CREATE KDSDPROF IN RKANDATV */
000081 //* */
000082 //***************************************************************/
000083 //KDSPRFDV EXEC PGM=IKJEFT01
000084 //SYSTSPRT DD SYSOUT=*
000085 //SYSPRINT DD SYSOUT=*
000086 //SYSPROC DD DISP=SHR,
000087 // DSN=TDITNT.ITM62351.TKANCUS
000088 //OUTDATV DD DISP=SHR,
000089 // DSN=TSTEST.CCAPI.PLB4&SYSNAME..RKANDATV(KDSDPROF)
000090 //INREC DD *
000091 /usr/lpp/java/IBM/J6.0
000092 //SYSTSIN DD *
000093 %KDSRPROF

If you have already submitted the original KCIJPUSP job that may have pointed to the IBM default instead of your preferred value, resubmit the modified KCIJPUSP job to refresh the RKANDATV(KDSDPROF) for this member, and rerun WKANSAMU(KCIJPUSS) job to recopy the member for RKANDATV(KDSDPROF) to USS.
======================================================================

===END " Sub-section: B. 3Q12A Issues"

===END " Sub-section: 3Q12A Enhancements/Issues Addressed "===
===END " Sub-section: What's New in 3Q12A "===

===END " Section: (Reference Only) Previous nQyyA/nQyyB Interim Features (IFs "===


    Native Language Translations

    Additional Language
    Technotes:    		 This is not a required field. Use these fields to specify the DocNumber of native version translations of this content Doc Link
    Japanese
    Cross reference information
    Segment Product Component Platform Version Edition
    Systems and Asset Management Tivoli OMEGAMON XE for CICS on z/OS z/OS 5.1.0
    Systems and Asset Management Tivoli OMEGAMON XE for DB2 Performance Expert for z/OS z/OS 5.1.0
    Systems and Asset Management Tivoli OMEGAMON XE for DB2 Performance Monitor for z/OS z/OS 5.1.0
    Systems and Asset Management Tivoli OMEGAMON XE for IMS on z/OS z/OS 4.2.0
    Systems and Asset Management Tivoli OMEGAMON XE on z/OS z/OS 5.1.0
    Systems and Asset Management Tivoli Management Server for Distributed Systems on z/OS z/OS 6.2.2
    Systems and Asset Management Tivoli Monitoring Version 6 z/OS 6.2.2
    Systems and Asset Management Tivoli OMEGAMON DE on z/OS 5.1.0
    Systems and Asset Management Tivoli OMEGAMON XE for Mainframe Networks ITCAM for RT Enabler for z/OS 5698-B01 v620 z/OS 4.2.0
    Systems and Asset Management IBM OMEGAMON z/OS Management Console z/OS 4.1.0
    Systems and Asset Management Tivoli OMEGAMON XE for Messaging for z/OS z/OS 7.0.1
    Storage Management Tivoli OMEGAMON XE for Storage on z/OS z/OS 4.2.0
    Systems and Asset Management Tivoli System Automation for z/OS z/OS 3.3
    Systems and Asset Management Tivoli NetView for z/OS z/OS V6R1
    Systems and Asset Management Tivoli Composite Application Manager for Transactions for z/OS z/OS
    Systems and Asset Management Tivoli Composite Application Manager for SOA Platform z/OS 7.1.1
    Systems and Asset Management Tivoli Composite Application Manager for Application Diagnostics on z/OS z/OS 7.1
    Storage Management Tivoli Advanced Audit for DFSMShsm z/OS 2.1
    Storage Management Tivoli Advanced Backup and Recovery for z/OS z/OS 2.1
    Storage Management Tivoli Advanced Catalog Management for z/OS z/OS 2.1
    Storage Management Tivoli Advanced Reporting for DFSMShsm z/OS 2.1
    Storage Management Tivoli Advanced Allocation Management z/OS 3.1
    Storage Management Tivoli Automated Tape Allocation Manager for z/OS z/OS 3.1
    Storage Management Tivoli Tape Optimizer on z/OS z/OS 2.2
    Systems and Asset Management Tivoli Decision Support for z/OS z/OS 1.8.1

    Product Alias/Synonym

    z/OS ICAT Installation and Configuration Assistance Tool - Configuration Tool for z/OS-based OMEGAMON/ITM suite of products.

    Rate this page:

    (0 users)Average rating

    Copyright and trademark information

    IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., 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.

    Rate this page:


    (0 users)Average rating

    Add comments

    Document information

    Tivoli Monitoring Version 6

    Software version:
    6.2.2, 6.2.3, 6.3.0

    Operating system(s):
    z/OS

    Reference #:
    1417935

    Modified date:
    2013-06-18

    Translate my page

    Content navigation