OMEGAMON / Suites Deployment Customer Open Q&A Calls

Cumulative Meeting Minutes from the 2015-2017 Monthly Calls

Primary References:

Master PARMGEN technote

System z Management community

OMEGAMON Shared Documentation

QQuueessttiioonnss aanndd//oorr FFeeeeddbbaacckk rreeggaarrddiinngg tthhiiss ddooccuummeenntt::

kindly contact Cecile Day (dayce@us.ibm.com) of the PARMGEN R&D team.

Table of Contents

Minutes from OMEGAMON Deployment Customer Open Q&A Web Conference Calls: ............ 9

Previous 2017 Meeting Minutes: ............................................................................................ 9

9

• Meeting Minutes: OMEGAMON / Suites Deployment Customer Open Q&A Web Conference Call held October 11, 2017 ..............................................................................................................9

A. Number of Attendees: ..................................................................................................................................... 9 B. Presentation Materials: .................................................................................................................................... 9 C. Q&A Details: ..................................................................................................................................................... 9 Q#1: “Is it right to say, that with the migration to V5.5.0, I can remove any parameter not listed in the Parameter Reference V5.5.0 table?” .................................................................................................................... 9 Q#2: “We encountered ‘Unable to open Configuration File 'khdxcfg'’ issue in the OMEGAMON for Networks Agent STC. We needed to manually increase GROUP=PDSGROUP file from 1 RN3SGRP1 to 2 more (RN3SGRP2, RN3SGRP3). Will this be supported by the products or by PARMGEN in the future?’” .................................... 10 Q#3: “What is the benefit of enabling RMF DDS for OMEGAMON for z/OS?” .................................................. 12 Q#4: “What parameters in PARMGEN do I enable for TOM near-term history?” .............................................. 15 Q#5: “If I need to use more than 7 OMEGAMON for DB2 Classic NTH VSAM RKD2VSnn datasets, how do I preserve those settings in the RKD2PAR(COPT&dbid) dataset?” ....................................................................... 15 Q#6: “Where can I find OMEGAMON for CICS planning considerations that KOCOME00 INITPARM must list CICS first before IMS?” ....................................................................................................................................... 16

.................................................................................................................................................... 17

• Meeting Minutes: OMEGAMON / Suites Deployment Customer Open Q&A Web Conference Call held September 13, 2017 ....................................................................................................... 17

A. Number of Attendees: ................................................................................................................................... 17 B. Presentation Materials: .................................................................................................................................. 17 C. Q&A Details: ................................................................................................................................................... 17 Q#1: “What version of OMEGAMON for DB2 do I need to monitor DB2 12 and is there a compatibility DB2 V12 OMEGAMON PTF for V5.3.0?” .................................................................................................................... 17 Q#2: “What could cause no data for IBM MQ Queue Managers in the OMEGAMON Enhanced 3270UI (TOM) but the same z/OS-based QMGRs show up in the TEPS?” ................................................................................. 18 Q#3: “Can I upgrade from OMEGAMON for Messaging V7.1.0 (FMID HKMQ710 GA-3) directly to the latest OMEGAMON for Messaging V7.5.0 (FMID HKMQ750)?” ................................................................................... 18 Q#4: “Does OMEGAMON enhanced 3270UI support the situation event forwarding to an EIF receiver, for example Netcool OMNIbus? Here's a screen shot of that panel from the TOM situation editor.” ................... 19

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held August 02, 2017 .................................................................. 20

A. Number of Attendees: ................................................................................................................................... 20 B. Presentation Materials: .................................................................................................................................. 20 C. Q&A Details: ................................................................................................................................................... 20 Q#1: “How do I enable OMEGAMON for DB2 thread history in PARMGEN?” ............................................................ 20 Q#2: “What do I specify for GBL_USS_TKANJAR_PATH parameter?” ............................................................... 23 Q#3: “What is PARMGEN’s FMID? What’s the latest ITM maintenance?” ........................................................ 26 Q#4: “Are there OMEGAMON product toleration PTFs needed for z14? ” ....................................................... 27 Q#5: “How do I convert my FULL RTE to SHARING Type?” ................................................................................ 28

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held June 07, 2017 ...................................................................... 29

A. Number of Attendees: ................................................................................................................................... 29 B. Presentation Materials: .................................................................................................................................. 29 C. Q&A Details: ................................................................................................................................................... 29 Q#1: “How do I quickly convert my existing RTE not currently using variables, to use best-practice symbols?” ............. 29 Q#2: “What jobs do I run after SMP/E maintenance?” ..................................................................................... 30 Q#3: “How do I enable a new CICS region ONDV VSAM in the KC2GLB OMEGAMON CICS global?” ................ 31

.................................................................................................................................................... 34

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held May 10, 2017 ...................................................................... 34

A. Number of Attendees: ................................................................................................................................... 34 B. Presentation Materials: .................................................................................................................................. 34 C. Q&A Details: ................................................................................................................................................... 34 Q#1: “I created new RTE datasets as part of my upgrade, cloning config. values from the previous version's RTE WCONFIG dataset. Where in PARMGEN do I tell it to reuse my OMEGAMON CICS globals from the other RTE globals dataset?” ......................................................................................................................................... 34 Q#2: “What are the requirements to use the PARMGEN z/OS DLA (KCIJPDLA) "Composite PARMGEN z/OS Discovery Library Adapter (DLA) job" job?” ....................................................................................................... 37 Q#3: “Does PARMGEN KCIJPDLA or KCIJPDL3 "Refresh LPAR RTE user profiles with $DLARPT data" job preserve old DB2 subsystems I specified in the profile? What if they are just not running at the time KCIJPDLA or KCIJPDL1 job was reran?” .............................................................................................................. 39 Q#4: “Can the USS directory path names be changed?” ................................................................................... 41 Q#5: “Question about the use and update of the KC2_HS table” ...................................................................... 43 Q#6: “My RTEs are enabled for variables (static system symbols, and PARMGEN best-practice user symbols). How is &SYSIPHOSTNAME. used during product startup? Would I have to reconfigure all of my RTEs given our host system IP folks changed the resolution value to the fully qualified hostname rather than the usual DNS?” ........................................................................................................................................................................... 44

.................................................................................................................................................... 47

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held April 12, 2017 ..................................................................... 47

A. Number of Attendees: ................................................................................................................................... 47 B. Presentation Materials: .................................................................................................................................. 47 C. Q&A Details: ................................................................................................................................................... 47 Q#1: “On our system that contains a Remote TEMS, we see connections from the OMEGAMON and Advanced Storage Agents connecting directly to the Hub TEMS in another LPAR and not going through the OMEGDS RTEMS in the local LPAR. Is there coding in the Agents that allows it to connect directly to the Hub (in another LPAR)?” ................................................................................................................................................. 47 Q#2: “Can z/OS monitoring Agents “bind” to more than one IP stack (we have multiple IP stacks)?” ............. 52 Q#3: “How do I create a 2nd set of base libraries for my new maintenance?” ................................................. 53 Q#4: “Does PARMGEN z/OS DLA integration support OMEGAMON CICS history configuration?” .................... 54

.................................................................................................................................................... 60

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held February 22, 2017 ............................................................... 60

A. Number of Attendees: ................................................................................................................................... 60 B. Presentation Materials: .................................................................................................................................. 60 C. Q&A Details: ................................................................................................................................................... 60

Q#1: “Are there imbeds for SET commands I need to add in the TEMS started task before the PGM=KLV program?” .......................................................................................................................................................... 60 Q#2: “What versions of the OMEGAMON products dropped the CUA interface?” .......................................... 62 Q#3: “We are a year behind in maintenance. What are best practices to upgrade?” ...................................... 63

.................................................................................................................................................... 65

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held January 11, 2017 ................................................................. 65

A. Number of Attendees: ................................................................................................................................... 65 B. Presentation Materials: .................................................................................................................................. 65 C. Q&A Details: ................................................................................................................................................... 65 Q#1: “Does PARMGEN support the KDSENV parm KDS_USERS_NO_MSGLOG=. If it does, would have to be added to each TEMS RTE one at a time?” .......................................................................................................... 65 Q#2: “We modified RKANPARU(KM2IPARM) changing PROFILE=/I to PROFILE=XE. Where in PARMGEN do I change USER_PROFILE /I to XE?” ....................................................................................................................... 67 Q#3: “We ordered the new versions of the OMEGAMON products (DB2 / JVM / Storage - V540). Are there special upgrade?” ............................................................................................................................................... 68

Previous 2016 Meeting Minutes: .......................................................................................... 70

.................................................................................................................................................... 70

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held October 26, 2016 ................................................................. 70

A. Number of Attendees: ................................................................................................................................... 70 B. Presentation Materials: .................................................................................................................................. 70 C. Q&A Details: ................................................................................................................................................... 70 Q#1: “How do I increase the history files?” .......................................................................................................71 A#1: See “How to: Change PDS file count and file size” in IBM Knowledge Center (URL: http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/howto_increase_pdsfilecount.htm) ................................................................................................................71 Q#2: “We have 2 TEPS, one for PROD and one for TEST. Is it possible to have two primary sysplex proxies running in a given Sysplex?” .............................................................................................................................. 73 Q#3: “How do I exclude a TEMS from becoming a sysplex proxy?” .................................................................. 75

.................................................................................................................................................... 77

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held August 10, 2016 .................................................................. 77

A. Number of Attendees: ................................................................................................................................... 77 B. Presentation Materials: .................................................................................................................................. 77 C. Q&A Details: ................................................................................................................................................... 77 Q#1: “How do I set-up history in enhanced 3270UI, or can the NTH datasets be used in any way in enhanced 3270UI?“ ............................................................................................................................................................ 78 Q#2: “Can I turn of the comments in the profile?” ............................................................................................ 80

.................................................................................................................................................... 82

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held June 29, 2016 ...................................................................... 82

A. Number of Attendees: ................................................................................................................................... 82 B. Presentation Materials: .................................................................................................................................. 82

C. Q&A Details: ................................................................................................................................................... 82 Q#1: “How do I enable the z/OS RTEMS to report to my FTO (Hot Standby) primary and backup Hub TEMS?“ ........................................................................................................................................................................... 82 Q#2: “Is there a way to suppress the informational “KDSMA009 User xxx logged off server SRVR01” and “KDSMA011 Logon successful to server SRVR01 user xxx ip.pipe:#%KDS_TEMS_TCP_HOST% (%KDS_TEMS_TCP_PIPE_PORT_NUM%)” repeated TEMS RKLVLOG messages?”............................................. 83 Q#3: “I need to make changes to the SMP/E target NONSMS info. – how do I reinvoke the SPECIFY GBL_TARGET_HILEV PARAMETERS (KCIP@TLV) panel?” ................................................................................... 83

.................................................................................................................................................... 85

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held May 25, 2016 ...................................................................... 85

A. Number of Attendees: ................................................................................................................................... 85 B. Presentation Materials: .................................................................................................................................. 85 C. Q&A Details: ................................................................................................................................................... 85 Q#1: “I want to create new PARMGEN work datasets and Runtime Environment Datasets for each LPAR for the new

products. How do I ensure that I bring over all of my V5.1 product configuration from the existing set up?“ ................... 85 Q#2: “How I can export the (OMCICS) region profiles, without going back to V5.1?” .................................................. 86 Q#3: “I have a member RKD2PAR(OMPEMSTS) which I manually coded with the EXCLUDEDB2SSID parameter; what

parm. preserves my updates in PARMGEN?” .......................................................................................................... 87 Q#4: “We noticed multiple messages in our SYSLOG for OMXEMQ on our development LPAR stating insufficient access

authority requiring Control access. What setting controls this?” ................................................................................ 88 Q#5: “What happens when the Java version changes (for the SDA TEMS processing)?” .................................. 89 Q#6: “Should CICS be started before OMEGAMON CICS?“ ................................................................................ 90 Q#7: “Where do I find information for compatibility for OMEGAMON with zOS 2.2? We are currently running zOS 1.13?“ ........................................................................................................................................................................... 92 Q#8: “Are there any issues if I at first only upgrade the Hub TEMS?“ ................................................................... 93

.................................................................................................................................................... 93

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held April 27, 2016 ..................................................................... 93

A. Number of Attendees: ................................................................................................................................... 94 B. Presentation Materials: .................................................................................................................................. 94 C. Q&A Details: ................................................................................................................................................... 94 Q#1: “What is loaded in RKANPARU during PARMGEN config. time?“ .............................................................. 94 Q#2: “When do I use LOADDATV?” .................................................................................................................... 95 Q#3: “How does the Agent in the local RTE and the Agents in the Remote RTEs know where the Hub TEMS is?“ ..................................................................................................................................................................... 95 Q#4: “Is there a separate line item in the selection list for OMEGAMON Monitoring for JVM or is it configured with OMEGAMON XE on z/OS?“ ...................................................................................................................... 101 Q#5: “I just applied the latest PARMGEN 1Q16 IF UA80256. Do I need to review the 65-page What’s New in PARMGEN 1Q16 IF document?“ ....................................................................................................................... 102

.................................................................................................................................................. 103

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held March 30, 2016 ................................................................. 103

A. Number of Attendees: ................................................................................................................................. 104 B. Presentation Materials: ................................................................................................................................ 104 C. Q&A Details: ................................................................................................................................................. 104 Q#1: “For a Remote TEMS, does the "KDS_HUB_TEMS_NAME_NODEID" LPAR RTE profile parameter in

WCONFIG(&rte_name) translate to a parm. in a runtime member?“ ............................................................. 105 Q#2: “What are the new PARMGEN features in UA80256, specifically the OMEGAMON enhanced 3270UI (TOM)?” ............................................................................................................................................................ 105 Q#3: “What are the 3 new XKAN* datasets allocated as part of my OMEGAMON V530 upgrade?“ ............... 108 Q#4: “What parameters are customized in PARMGEN to enable Near-term history in the OMEGAMON enhanced 3270UI?“ .......................................................................................................................................... 113

.................................................................................................................................................. 114

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held February 17, 2016 114

A. Number of Attendees: ................................................................................................................................. 115 B. Presentation Materials: ................................................................................................................................ 115 C. Q&A Details: ................................................................................................................................................. 115 Q#1: “Are there z/OS Agent PTFs required for the TEP client jar file certificates expiring in April?“ ............... 115 Q#2: “Are there PARMGEN jobs to REPRO VSAM data from the old datasets to a new RTE?” ........................ 115 Q#3: “How do I add the new OMEGAMON Monitoring for JVM Agent?“ ....................................................... 118 Q#4: “How do I get PDFs for the OMEGAMON product manuals?“................................................................. 122

.................................................................................................................................................. 123

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held January 20, 2016 123

A. Number of Attendees: ................................................................................................................................. 124 B. Presentation Materials: ................................................................................................................................ 124 C. Q&A Details: ................................................................................................................................................. 125 Q#1: “Does ITM support Java 8?“ .................................................................................................................... 125 Q#2: “Our shop runs out of the SMP/E targets (we do SYSRES cloning). I always loaded the RTEs in ICAT – do I need to do that in PARMGEN?”........................................................................................................................ 125 Q#3: “We created a new RTE from the original one but some values were still pointing to the old RTE values. What steps were missed?” ............................................................................................................................... 125 Q#4: “In the cloning scenario covered for the CLONTO RTE (modeled from WCONFIG(CLONFROM) for the demo (from Q#3), when I upgrade to the V530s/V730s, do I perform something similar?” ........................... 125 Q#5: “We currently are running the ICAT version of OMEGAMON XE monitoring products (z/OS, CICS, DB2 & TEMS) versions 4.2.0 & 6.2.2. I have received & applied the updates for HKCI310 & am ready to start the conversion to PARMGEN. What are my next steps? ” ...................................................................................... 126 Q#6: "How do I update KMQUSER member (for OMEGAMON XE for Messaging – MQ Monitor Agent)?" .... 126 Q#7: "We are upgrading from SA V3.4 to V3.5 - does SA have integration to the OMEGAMON/ITM CSI?" .... 128

Previous 2015 Meeting Minutes: ........................................................................................ 131

.................................................................................................................................................. 131

Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held November 18, 2015.................................................................................................................................................. 131

A. Number of Attendees: ................................................................................................................................. 131 B. Presentation Materials: ................................................................................................................................ 132 C. Q&A Details: ................................................................................................................................................. 132 Q#1a: “Are the z/OS 2.2 PARMGEN toleration PTFs (UA76016 and later) backward compatible? That is, can they be applied while we are still running z/OS 2.1? Assuming the answer is yes, I know I need to port the 32 read-only shared BASE libraries to the other sysplexes. But do I also need to reconfigure each RTE itself namely, starting over with Option 1 of PARMGEN s Quick Configuration?”..................................................... 132 Q#1b: “Can you still stage deployment of the RTE runtime members if the RTE was staged in a z/OS 2.1 LPAR

for a remote LPAR that will be upgraded to z/OS 2.2 if the GBL_* parms. indicate that this system that PARMGEN staging jobs were ran on indicate "z/OS 2.1"? ................................................................................ 133 Q#2: “We missed changing KD2_DBnn_DB2_VER from 91 to 11 resulting in .RKD2SAM not get fully populated. The VALIDATE step should generate a RC=08 when a DB2 version is no longer supported. ”. ..... 134 Q#3: "How do I update KMQUSER member (for OMEGAMON XE for Messaging – MQ Monitor Agent)?" .... 137 Q#4: “How do I quickly delete/reallocate PDS files?” ...................................................................................... 138 Q#5: “How many VSAM files can be allocated for (thread) NTH for OMXE for DB2?” ..................................... 139 Q#6: “What are the differences in NTH storage?” ........................................................................................... 140

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held October 7, 2015 141

A. Number of Attendees: ................................................................................................................................. 141 B. Presentation Materials: ................................................................................................................................ 141 C. Q&A Details: ................................................................................................................................................. 142 Q#1: Question about “OMEGAMON STC dumps when trying to use RKANCMDU” with KCIRPLB1 – E Running KCIPARSE” message. ......................................................................................................................................... 142 Q#2: “Do I need to convert the ICAT Base RTE first to PARMGEN? ” ............................................................... 142 Q#3: For table parms. in the WCONFIG(&rte_name) profile, do they have to be placed within the Kpp$ BEGIN/END product indicator or within the Kpp_xx table BEGIN/END indicator? .......................................... 142 Q#4: Is there one place that tracks what versions of the products are configured in each RTE? .................... 143 Q#6: “Can you update the parmgen profile without rerun all parmgen setup batch jobs?" ........................... 143

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held September 9, 2015 144

A. Number of Attendees: ................................................................................................................................. 144 B. Presentation Materials: ................................................................................................................................ 145 C. Q&A Details: ................................................................................................................................................. 145 Q#1: Question about MAXIMUM() in OMEGAMON XE for DB2 ‘s CUA KD2SYSIN runtime member. .............. 145 Q#2: Question about what to use if site does not use a DNS name for their z/OS hosts (not set up in DNS). 145 Q#3: How to apply maintenance with PARMGEN after the initial install is complete. .................................... 145 Q#4: During normal RTE maint., why would you have to run the KCIJPCFG job? ............................................ 146

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held July 29, 2015 147 A. Number of Attendees: ................................................................................................................................. 147

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held June 24, 2015 147

A. Number of Attendees: ................................................................................................................................. 147

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held May 20, 2015 148

A. Number of Attendees: ................................................................................................................................. 148 B. Presentation Materials: ................................................................................................................................ 149 C. Q&A Details: ................................................................................................................................................. 149 Q#1: How do we change the number of OMXE for DB2 (thread) near term history VSAM dataset (RKD2VSnn)? ......................................................................................................................................................................... 149 Q#2: How are OMXE for DB2 KD2_OMPE_CHECKSYS and KD2_OMPE_USE_MODEL parms. used? .............. 150 Q#3: What are the migration considerations if I want to use a new PARMGEN global JCL library for managing my existing RTEs (during PARMGEN processing)? ............................................................................................ 151 Q#4: What are the migration considerations if I want to use a new PARMGEN global JCL library for my product started tasks enabled for variables (during product startup)? ......................................................................... 152 Q#5: How do I redirect my standalone Agent running in its own agent address space to point to a different Primary TEMS? ................................................................................................................................................. 153

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held April 15, 2015 155

A. Number of Attendees: ................................................................................................................................. 155 B. Presentation Materials: ................................................................................................................................ 155 C. Q&A Details: ................................................................................................................................................. 155 Q#1: Can I use &SYSIPHOSTNAME. and &SYSIPADDRESS. for the PARMGEN LPAR RTE WCONFIG(&rte_name) profile parameter value? .................................................................................................................................. 155 Q#2: In ICAT, I specified static values for my RKANPARU(KC5ENV) KDEB_INTERFACELIST=sy9. Once converted to PARMGEN, can this be made a user symbol instead of a static value. ......................................................... 156 Q#3: My RKANPARU(KD5ENV) OMXE DB2 Agent's CT_CMSLIST points to IP:PIPE:&SYSIPHOSTNAME. - how do I get the Agent to connect to a different TEMS? .............................................................................................. 156 Q#4: We currently have a local TEMS configured in the RTE but our Agents configured in the same RTE are connecting to a primary distributed TEMS and a backup distributed TEMS. If I want to follow best-practice and have the z/OS Agents connect to the local z/OS RTEMS configured in the RTE, what parms. do I need to change? ............................................................................................................................................................ 157 Q#5: How does the Agent in Q#4 still find the z/OS local RTEMS if I configured PARMGEN to have the Agent connect to 2 distributed TEMS for the primary TEMS and backup TEMS values. ............................................ 157

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held March 18, 2015 159

A. Number of Attendees: ................................................................................................................................. 159 B. Presentation Materials: ................................................................................................................................ 159 C. Q&A Details: ................................................................................................................................................. 159 Q#1. How do I quickly merge the new best-practice user symbols supplied in TKANSAM($MDLVARS) for my existing PARMGEN RTE that is enabled for variables but only using the minimum system variables (&SYSNAME., &SYSCLONE.)? ............................................................................................................................ 159

Minutes from OMEGAMON Deployment Customer Open Q&A Web Conference Calls:

Previous 2017 Meeting Minutes:

• Meeting Minutes: OMEGAMON / Suites Deployment Customer Open Q&A Web Conference Call held October 11, 2017

• 10/11/2017 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in System z Management community: URL: http://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=709e6809-4af3-48cb-9ccb-d633a3840376

C. Q&A Details:

• October 11, 2017 Q&A:

Q#1: “Is it right to say, that with the migration to V5.5.0, I can remove any parameter not listed in the Parameter Reference V5.5.0 table?”

• A#1: OMEGAMON for z/OS V5.5.0 Knowledge Center’s (KC) Parameter Reference (http://www.ibm.com/support/knowledgecenter/SS2JNN_5.5.0/com.ibm.omegamon_xezos.doc_5.5.0/parmref/overview_omxezos_parmref.htm) has a list of KM2 and KM5 LPAR

RTE profile parameters applicable for this new version. Deprecated parameters for which functions are no longer applicable in this version are no longer listed so this Parameter Reference topic is a good reference. There are other OMEGAMON products’ KCs for which they may still be listing the old CUA parameters and other deprecated functions’ respective parameters for migration purposes.

• Tips: • For a definitive list of parameters that the PARMGEN KCIJPCFG/KCIJPPRF RTE profile

refresh job will no longer regenerate in the WCONFIG(%RTE_NAME%) LPAR RTE user profile, see the RTE’s %RTE_PLIB_HILEV%.%RTE_NAME%.IKANSAMU(Kpp$DCFG) members. In an upgrade scenario, one must follow SMPE04, SMPE05, or SMPE06 upgrade scenarios in order to refresh the RTE user profile with only the parameters applicable to the upgraded version(s) starting with OMEGAMON V5.4.0s and higher (provided one has the minimum PARMGEN PTF maintenance @ 3Q17 IF level (PTF UA91953) that provide the parameter streamlining enhancements. See the presentation materials presented in the Sept. 13th and Oct. 11th calls.

• For any new LPAR RTE user profile or $GBL* global user profile parameters added, those are always called in out the IF-specific “What’s New in PARMGEN yyqq” topic in the OMEGAMON Shared KC. Similar info. Is in the PARMGEN main welcome screen:

• (See option “I” in the on-line README on the "Welcome to the z/OS Installation and Configuration Tools for z Systems Management Suites" main welcome panel.)

Q#2: “We encountered ‘Unable to open Configuration File 'khdxcfg'’ issue in the OMEGAMON for Networks Agent STC. We needed to manually increase GROUP=PDSGROUP file from 1 RN3SGRP1 to 2 more (RN3SGRP2, RN3SGRP3). Will this be supported by the products or by

PARMGEN in the future?’”

A#2: The issue is currently under investigation. The strategic solution requires an update to the z/OS ITM (FMID HKDSvvv) infrastructure. The short-term solution would necessitate a PARMGEN configuration enhancement to programmatically increase the allocation of the GROUP=PDSGROUP files for the TEMS and the monitoring Agents (3 RppSGRPn sequential files per TEMS and per Agent) where pp = PD (for TEMS), C5 (for OMCICS), D5 (for OMDB2), GW (for OMCICSTG), I5 (for OMIMS), JJ (for OMJVM), MQ (for OMMQ). N3 (for OMNetworks), QI (for OMMQ-IIB), etc.. ============================================================= Circumvention instructions: 1. Back-up the existing %RTE_HILEV%.%RTE_NAME%.RKANPARU dataset. 2. Modify RKANPARU(KppAL) to add 2 more entries (model after the first ALLOC

statements for RppSGRP1 as shown on lines #190-#191). In this case, this is the KN3AL runtime member for OMEGAMON for Networks Agent’s persistent datastore allocation file called KN3AL in the RTE’s xKANPARU dataset: ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss

VIEW TDITN.OMEG.SP22.RKANPARU(KN3AL) Command ===> 000190 ALLOC DSN:TDITN.OM&OMVER..&SYSNAME..RN3SGRP1 SIZE=8M + 000191 WINDOW=4 000192 ALLOC DSN:TDITN.OM&OMVER..&SYSNAME..RN3SGRP2 SIZE=8M + 000193 WINDOW=4 000194 ALLOC DSN:TDITN.OM&OMVER..&SYSNAME..RN3SGRP3 SIZE=8M + 000195 WINDOW=4 ****** **************************** Bottom of Data ***********

3. Modify RKANPARU(KppPG) to add 2 more entries (model after the first GROUP statement for RppSGRP1 as shown on lines #12-#13). In this case, this is the KN3PG runtime member for OMEGAMON for Networks Agent’s persistent datastore group assignment file called KN3PG in the RTE’s xKANPARU dataset: VIEW TDITN.OMEG.SP22.RKANPARU(KN3PG) Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************** 000001 * ****************************************************************** 000002 * Member: KN3PG 000003 * Master Source: TDITNT.DEV.ITM63055.TKANPAR(KN3PRMLB) 000004 * KCIJPUP1 Batch Job Output: 000005 * TDITN.OMEG.&SYSNAME..IKANPARU(KN3PG) 000006 * $PARSE Batch Job Output: 000007 * TDITN.OMEG.&SYSNAME..WKANPARU(KN3PG) 000008 * ****************************************************************** 000009 * This member is processed by xKANSAMU(KCIJPALO/KN3JPALP) PDS alloc. job 000010 * and RKPDIN DD/RKPDLOG DD of the TMS:Engine Agent started task 000011 OVERRIDE TABLE=GENHISTORY APPL=PDSSTATS WRAP=0 GROUP=PDSGROUP 000012 GROUP=PDSGROUP + 000013 FILE=DSN:TDITN.OM&OMVER..&SYSNAME..RN3SGRP1 000014 GROUP=PDSGROUP + 000015 FILE=DSN:TDITN.OM&OMVER..&SYSNAME..RN3SGRP2 000016 GROUP=PDSGROUP + 000017 FILE=DSN:TDITN.OM&OMVER..&SYSNAME..RN3SGRP3

4. When ready to deploy the manual edits to the KppAL/KppPG persistent datastore runtime members, shutdown the started task.

5. Rename the existing %RTE_PDS_HILEV%.RppSGRP1 dataset. 6. Rerun the RTE’s xKANSAMU(KppPDALP) standalone persistent datastore allocation job

to allocate the new RppSGRP1 files. Note: Expect return code 0008 in this case as some of the other non-PDSGROUP sequential files could be in use. This is an acceptable condition.

7. Restart the started task. Ensure that the RKPDLOG DD is properly using the new RppSGRPn sequential files and no khd* errors are encountered.

8. Please repeat enablement steps when the KppAL/KppPG runtime members are refreshed by any jobs ($PARSE*/KCIJPW2R) that copies members to the RTE’s RKANPARU dataset.

To our valued customer who brought up this requirement, thank you and kindly open a RFE (Request for Enhancement) so our IBM Offering Management can prioritize accordingly. Thank you.

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

Q#3: “What is the benefit of enabling RMF DDS for OMEGAMON for z/OS?”

A#3: The OMEGAMON for z/OS leverages the RMF data for reatime collection data. From our OMEGAMON for z/OS development team, with OMEGAMON for z/OS V5.5.0, this version has even more dependencies on RMF data for realtime Coupling Facility information. See PARMGEN WCONFIG LPAR RTE profile parameter called KM5_RMF_DDS_COLLECTION: ISREDDE2 TDITN.OMEG.SP22.WCONFIG(SP22) - 01.00 Columns 00001 00072 Command ===> Scroll ===> CSR 007782 ** (CF), cross-system coupling facility (XCF), and system lock data from 007783 ** the RMF Distributed Data Server (DDS) instead of collecting its own 007784 ** data. Using RMF data can eliminate duplicate data collection and 007785 ** provide you with consistent metrics. It can also result in some 007786 ** overhead savings. RMF data is collected at a shorter monitoring 007787 ** interval than the corresponding OMEGAMON for z/OS data. Use of RMF 007788 ** can be enabled via the KM5_RMF_DDS_COLLECTION configuration 007789 ** parameter. Valid values are as follows: 007790 ** 1. NO - Disables RMF data collection. CF and XCF data is collected 007791 ** from the OMEGAMON Subsystem. 007792 ** 2. ALL - CF, XCF, and lock data is collected from RMF. 007793 ** Starting in PARMGEN 4Q17 IF (APAR OA53974), the default is 007794 ** "ALL". 007795 ** 3. CF/XCF - CF and XCF data is collected from RMF. 007796 ** 4. LOCK - Spin and suspend lock data is collected from RMF. 007797 ** 007798 ** The KM5_RMF_DDS_COLLECTION=&value parameter is written out as 007799 ** o KDS_KM5_DDS=%KM5_RMF_DDS_COLLECTION% 007800 ** parameter in the xKANPARU(KDSENV) member. 007801 ** 007802 ** If RTE_KCN_CACHE_KM5_RMF_DDS value is specified, KDS_KM5_DDS 007803 ** parameter is written out as 007804 ** o KDS_KM5_DDS=%RTE_KCN_CACHE_KM5_RMF_DDS%,%KM5_RMF_DDS_COLLECTION% 007805 ** parameter in the xKANPARU(KDSENV) member. 007806 ** 007807 ** RTE_KCN_CACHE_KM5_RMF_DDS value contains your preferred RMF DDS 007808 ** network address (IP address or IP hostname format) and RMF DDS port 007809 ** number that you want the OMEGAMON Subsystem RMF cache to retrieve 007810 ** the data from, rather than the autodiscovered RMF DDS. 007811 ** 007812 ** RTE_KCN_CACHE_KM5_RMF_DDS Enablement Support: 007813 ** Refer to OMEGAMON for z/OS HKM5530 PTF UA82561 (or later 007814 ** maintenance) for the RTE_KCN_CACHE_KM5_RMF_DDS enablement 007815 ** support if you exploit this feature. 007816 ** 007817 ** Important: See "Enable RMF data collection" section in the 007818 ** "Completing the configuration" chapter of the product 007819 ** configuration guide for more information on RMF components 007820 ** that must be activated if you enable this option. 007821 ** Note: Related PARMGEN CONFIG profile parameters: 007822 ** - RTE_KCN_CACHE_KM5_RMF_DDS

007823 ** ----------------------------------------------------------------- - 007824 KM5_RMF_DDS_COLLECTION &KM5_RMF_DDS. * NO,ALL,CF/XCF,LOCK

For history in the OMEGAMON enhanced 3270UI, using RMF also is used for history data. See PARMGEN WCONFIG LPAR RTE profile parameter for setting to control using RMF DDS to supply history data. 000764 ** ----------------------------------------------------------------- - 000765 ** (Conditional) Modify OMEGAMON Subsystem options: 000766 ** 1. Specify the values for the xKANPARU(KCNSTR00) runtime member 000767 ** which is generated with the following KCNSTR00 startup 000768 ** parameters pointing to the PARMGEN LPAR profile parameter values 000769 ** you specify: 000770 ** - SSID=%RTE_KCNSTR00_SSID% 000771 ** - XCF=%RTE_KCNSTR00_XCFGROUP% 000772 ** - KCN_WTO=%RTE_KCNSTR00_WTO% 000773 ** - REFRESH=%RTE_X_KCNSTR00_REFRESH% 000774 ** - PLEXCOLLECT=%RTE_X_KCNSTR00_PLEXCOLLECT% 000775 ** 2. OMEGAMON Subsystem (OMEGCN) 000776 ** started task has an APPL= (logon APPLID) parameter that points 000777 ** to the RTE_KCN_VTAM_APPL_LOGON parameter value. This logon APPLID 000778 ** is created in the: 000779 ** - OMEGAMON Subsystem VTAM major node (RTE_KCN_VTAM_NODE) 000780 ** - Global VTAM major node (RTE_VTAM_GBL_MAJOR_NODE) 000781 ** Note: Related PARMGEN CONFIG profile parameters: 000782 ** - RTE_VTAM_GBL_MAJOR_NODE 000783 ** - RTE_CANSCN_* 000784 ** - RTE_KCN_VTAM_* 000785 ** - RTE_KM5_NTH 000786 ** - RTE_KCN_CACHE_KM5_NTH_* 000787 ** 3. (Conditional) Applicable to OMEGAMON for z/OS V5.3.0 or later: 000788 ** OMEGAMON for z/OS Resource Measurement Facility (RMF) cache 000789 ** parameters generated in the following RTE xKANPARU runtime 000790 ** members: 000791 ** o Both xKANPARU(KDSENV) TEMS and xKANPARU(KOBENV) enhanced 000792 ** 3270UI runtime members: 000793 ** - KM5_NTH=%RTE_KM5_NTH% 000794 ** - KM5_NTH_CACHE=%RTE_KCN_CACHE_KM5_NTH% 000795 ** 000796 ** o xKANPARU(KDSENV) TEMS runtime member only: 000797 ** - KDS_KM5_DDS=%RTE_KCN_CACHE_KM5_RMF_DDS%,\ 000798 ** %KM5_RMF_DDS_COLLECTION% 000799 ** 000800 ** o xKANPARU(KOBENV) enhanced 3270UI runtime member only: 000801 ** - KM5_NTH_CACHE_RANGE=%RTE_KCN_CACHE_KM5_NTH_RANGE% 000802 ** - KM5_NTH_DDS=%RTE_KCN_CACHE_KM5_RMF_DDS% 000803 ** 000804 ** These parameters control when the OMEGAMON for z/OS RMF cache 000805 ** will be active. 000806 ** - KM5_NTH=Y|YES|N|NO (default is Y). 000807 ** KM5_NTH=Y|YES results in this OMEGAMON Subsystem instance 000808 ** (OMEGCN) being eligible to run an RMF cache and the 000809 ** OMEGAMON for z/OS Agent to retrieve near-term historical data. 000810 ** One OMEGAMON Subsystem per group per Sysplex will run an RMF 000811 ** cache. Others in the group will be on standby to start an RMF 000812 ** cache if the active RMF cache is stopped. The RMF cache can be

000813 ** dynamically started or stopped using a MODIFY (F) command: 000814 ** Ex.: Command ==> /F &rte_canscn_stc,NTHCACHE RESUME 000815 ** or 000816 ** Command ==> /F &rte_canscn_stc,NTHCACHE SUSPEND 000817 ** 000818 ** You can identify the OMEGAMON Subsystem that is running an RMF 000819 ** cache by issuing a MODIFY command to any OMEGAMON Subsystem in 000820 ** a group: 000821 ** Command ==> /F &rte_canscn_stc,NTHCACHE LOCATE 000822 ** 000823 ** - KM5_NTH_CACHE="" (default is null). 000824 ** The unique name that identifies a group of OMEGAMON Subsystems 000825 ** in a sysplex. The name must not be used by other WLM servers 000826 ** using the z/OS Sysplex Routing Services. The OMEGAMON 000827 ** Subsystems and OMEGAMON for z/OS Agents use a default group 000828 ** name of "KM5WMSRS" if a name is not specified. The OMEGAMON 000829 ** Subsystems use this name as a minor ENQ name; the OMEGAMON 000830 ** Subsystem that holds the ENQ will start the RMF cache and 000831 ** register itself for discovery. The OMEGAMON for z/OS Agents 000832 ** will use this name to discover the OMEGAMON Subsystem running 000833 ** the RMF cache. 000834 ** Important: All OMEGAMON Subsystems in the sysplex must have 000835 ** the same group name coded in this parameter to be 000836 ** eligible to become the RMF cache for the group. 000838 ** - KM5_NTH_CACHE_RANGE=nnn (default is 24 hours). 000839 ** The number of hours of RMF historical data that will be 000840 ** initially retrieved from the RMF Distributed Data Server (DDS) 000841 ** by the OMEGAMON Subsystem. The valid range is from 0-120 hours. 000842 ** 000843 ** - KM5_NTH_DDS="" (default is null). 000844 ** If RTE_KCN_CACHE_KM5_RMF_DDS value is specified, KM5_NTH_DDS 000845 ** parameter contains your preferred RMF DDS network address (IP 000846 ** address or IP hostname format) and RMF DDS port number that 000847 ** you want the OMEGAMON Subsystem RMF cache to retrieve the data 000848 ** from, rather than the autodiscovered RMF DDS. 000849 ** 000850 ** RTE_KCN_CACHE_KM5_RMF_DDS Enablement Support: 000851 ** Refer to OMEGAMON for z/OS HKM5530 PTF UA82561 (or later 000852 ** maintenance) for the RTE_KCN_CACHE_KM5_RMF_DDS enablement 000853 ** support if you exploit this feature. 000854 ** 000855 ** Note: Related PARMGEN CONFIG profile parameters: 000856 ** - RTE_CANSCN_* 000857 ** - RTE_KCN_VTAM_* 000858 ** - RTE_KM5_NTH 000859 ** - RTE_KCN_CACHE_KM5_NTH 000860 ** - RTE_KCN_CACHE_KM5_RMF_RANGE 000861 ** - RTE_KCN_CACHE_KM5_RMF_DDS 000862 ** - KM5_RMF_DDS_COLLECTION 000863 ** Related PARMGEN Kpp$* WCONFIG override imbed: 000864 ** - WCONFIG(KOB$PENV) 000865 ** ----------------------------------------------------------------- - 000866 RTE_CANSCN_STC OMEGCN 000867 RTE_KCN_VTAM_APPL_LOGON K&SYSCLONE.CNAP * Cache APPL 000868 RTE_KCN_VTAM_NODE K&SYSCLONE.CNN * Cache Node 000869 RTE_KM5_NTH &KM5_NTH. * Enablement Parameter *

000870 RTE_KCN_CACHE_KM5_NTH &KM5_CACHE_NTH. * <group name> 000871 RTE_KCN_CACHE_KM5_NTH_RANGE &KM5_CACHE_NTH_RANGE. * 0-120 hours 000872 RTE_KCN_CACHE_KM5_RMF_DDS "&KM5_NTH_DDS."

Enablement of these parameters in PARMGEN updates the RTE’s xKANPARU(KDSENV) and xKANPARU(KOBENV) runtime members via the $PARSE* “Create runtime members” job/KCIJPW2R job. See the product’s Complete the configuration steps in KC as there are post-configuration enablement steps and passticket security requirements with RMF DDS configuration with respect to OMEGAMON for z/OS post-configuration implementation.

Q#4: “What parameters in PARMGEN do I enable for TOM near-term history?”

A#4: Most products store the history data rendered via the OMEGAMON enhanced 3270UI in the z/OS ITM persistent datastore sequential files. See RTE_PDS_* and Kpp_PDS_CYL parameters in the PARMGEN WCONFIG LPAR RTE profile. Note that the Kpp_PDS_CYL total cylinder count is divided by the RTE_PDS_FILE_COUNT (6 product-specific sequential files per TEMS, per Agent). The product started task’s respective RKPDIN DD reads the product-specific persistent datastore runtime members created by $PARSE*/KCIJPW2R jobs in the RTE’s RKANPARU dataset. These members are KppPCTL/KppPCTL2/KppDEFIN. The allocation and grouping of the PDS sequential files are read in the KppAL/KppPG runtime members (also in the RTE’s RKANPARU dataset). PARMGEN’s composite KCIJPALO allocation job, or the product-specific standalone KppJPALP allocation job allocates these sequential files. See Q#2 for related information from the October 11th meeting. ➢ Other TOM NTH considerations:

o For OMEGAMON for z/OS, history data is stored levering RMF DDS. See Q#3 for related information from the October 11th meeting.

o For OMEGAMON for Db2, thread history data is stored in new VSAM %KD2_OMPE_VSAM_DSHLQ%.%DB%.RKTHnnnn VSAMs introduced by OMEGAMON for DB2 V5.3.0 HKDB530 PTF UI50913. See HKDBvvv APAR PI82090 for availability of support for other versions of OMEGAMON for DB2. PARMEN PTF UA91952 (2Q17 IF PTF) and later cumulative PTFs provide full configuration support of the OMEGAMON enhanced 3270UI thread history feature. See “What’s New in PARMGEN 2Q17 IF PTF UA91952” for more information.

Q#5: “If I need to use more than 7 OMEGAMON for DB2 Classic NTH VSAM RKD2VSnn datasets, how do I preserve those settings in the RKD2PAR(COPT&dbid) dataset?”

A#5: See new WCONFIG(KD2$PCOP) imbed introduced starting in PARMGEN 2Q17 IF PTF

UA91952 and later HKCI310 PTF maintenance. See SMPE02 through SMPE06 maintenance or upgrade scenarios, and select one scenario that fits your deployment, to have this new imbed exist in the RTE’s WCONFIG dataset. Rerunning WCONFIG(KCIJPUP1) job also refreshes the WCONFIG dataset with IBM default imbeds and LPAR RTE $CFG$IBM / $GBL$IBM default profiles. Customize the imbed accordingly then rerun the $PARSEPR and KCIJPW2R jobs to start preserving additional RKD2VSnn > 7 VSAMs in the RTE’s COPT&dbid Classic NTH history options (application history for OMEGAMON for DB2). Also, see Q#1 for related information from the August 2, 2016 meeting.

Q#6: “Where can I find OMEGAMON for CICS planning considerations that KOCOME00 INITPARM must list CICS first before IMS?”

A#6: This needs to be researched further as there are currently no sequencing or ordering priority requirements in OMEGAMON for CICS’ CICS region JCL post-configuration steps. From the OMEGAMON for CICS development test LPAR set-up, the DBCTL-to-CICS INITPARM (DFHDBCON) set-up lists IMS first before the OMEGAMON for CICS INITPARM in the test SIT. To our valued customer who encountered this issue and raised this query in the October 11th meeting, kindly open a PMR so this can be investigated further. Thank you.

• Meeting Minutes: OMEGAMON / Suites Deployment Customer Open Q&A Web Conference Call held September 13, 2017

• 09/13/2017 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in System z Management community: URL: http://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=716788c6-c1fe-470a-8b84-f6bfbbdc2c33

C. Q&A Details:

• September 13, 2017 Q&A:

Q#1: “What version of OMEGAMON for DB2 do I need to monitor DB2 12 and is there a compatibility DB2 V12 OMEGAMON PTF for V5.3.0?”

• A#1: OMEGAMON for DB2 V5.4.0 provides the DB2 V12 exploitation. This is the minimum version of the product that will monitor DB2 V12. This version GA’d on Dec. 9, 2016. For more information, pls. review Section A2 of the master PARMGEN technote’s Enablement Support Section A2 which documents the OMEGAMON for DB2 PTFs required along with the upgraded GA Base FMID HKDB540. This link also provides a cross-reference to the product’s IBM Knowledge Center documentation. Pls. review the product’s PSP bucket to see if there are additional HKDB540 PTFs to apply.

Section A2. Download any cross-product dependency application PTFs relating to product deployment: ( Date Last Updated: 20170908)

Post-SMP/E considerations : At a minimum, the product PTFs listed require that the PARMGEN KCIJPLOD "Copy SMP/E members from TK*->RK* read-only (RO) libraries" maintenance job is rerun to deploy any updated RO elements to the applicable product started task(s) for each monitored LPAR. Also refer to the respective PTFs for additional HOLDDATA information and check the IBM Support website if there are later superceding product PTFs.

APAR# FMID / PTF# / RSU

yymm or PUT

yymm

Interim Feature (IF) Release Date

PI69924 PI69926

HKDB540 / UI41675 / PUT1612 HKDB540 / UI41948 / PUT1612 HKDB540 / UI42901 / PUT1612

*GA* December 09, 2016 Note: These HKDB540 PTFs must be applied if you plan to exploit the new IBM OMEGAMON for DB2 Performance Expert (PE) / Performance Monitor (PM) V5.4.0 Agent features delivered in a new V5.4.0 version of OMEGAMON for DB2 PE/PM. For more information, refer to the OMEGAMON for DB2 PE/PM V5.4.0 IBM Knowledge Center documentation "What's New & PDFs" topic (URL:http://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/com.ibm.omegamon.xe.pe_db2.doc_5.4.0/ko299/ko299_pe_about.htm http://www.ibm.com/support/knowledgecenter/SSUSPA_5.4.0/com.ibm.omegamon.xe.pm_db2.doc_5.4.0/ko299/ko299_pm_about.htm).

Pls. also review the OMEGAMON Shared Documentation’s Basic Upgrade Requirements topic, which calls out the new GBL_* parameters needed for DB2 V12.

Q#2: “What could cause no data for IBM MQ Queue Managers in the OMEGAMON Enhanced 3270UI (TOM) but the same z/OS-based QMGRs show up in the TEPS?”

A#2: TOM L3 team recommends opening a PMR and send the TOM STC log. The SYSPRINT would reveal what could be causing. This may be a situation where there are new product tables. Cecile recommends to also check if the RTE was reloaded (KCIJPLOD job under the PARMGEN Workflow UI’s SUBMIT option) after the SMP/E update to HKMQvvv FMID. Product tables (KppCAT catalog, KppATR attribute and other xKANDATV SMPE/E elements) are stored in SMP/E &gbl_target_hilev.TKANDATV by the product FMID, and PARMGEN reloads then to RKANDATV (runtime copy of the SMP/E target).

Q#3: “Can I upgrade from OMEGAMON for Messaging V7.1.0 (FMID HKMQ710 GA-3) directly to the latest OMEGAMON for Messaging V7.5.0 (FMID HKMQ750)?”

A#3: Yes. The product’s OMEGAMON for Messaging program directory and documentation may be found in this link http://www.ibm.com/support/knowledgecenter/SSRLD6_7.5.0/whatsnew.html

Q#4: “Does OMEGAMON enhanced 3270UI support the situation event forwarding to an EIF receiver, for example Netcool OMNIbus? Here's a screen shot of that panel from the TOM situation editor.”

A#4: Not at this time. TOM L3 team recommends opening an enhancement via the Request for Enhancement (RFE) tool http://www.ibm.com/developerworks/rfe/execute?use_case=changeRequestLanding

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held August 02, 2017

• 08/02/2017 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=95a17aa0-dafa-4d4d-a755-bfd6ce04c196

C. Q&A Details:

• August 2, 2017 Q&A:

Q#1: “How do I enable OMEGAMON for DB2 thread history in PARMGEN?”

• A#1: See “What’s New in PARMGEN 2Q17 IF?” documentation in the IBM Knowledge Center’s OMEGAMON Shared documentation or in the PARMGEN on-line README option “I” (I)nfo on the “Welcome to the z/OS Installation and Configuration Tools for z Systems Management Suites” panel. The OMEGAMON for DB2 thread history PARMGEN configuration support details are under the “Section B. Product-specific enhancements>IBM Tivoli OMEGAMON XE for DB2 PE/PM V5.3.0 and later” entry.

For planning purposes, enabling OMEGAMON for DB2 thread history for the OMEGAMON enhanced 3270UI in an RTE requires:

• (Preinstallation Requirement) When available, review the product PTF HOLDDATA from FMID HKDBvvv for OMEGAMON for DB2 APAR PI82090 enablement support.

• (SMP/E Requirement) From FMID HKCI310: Install PARMGEN 2Q17 PTF UA91952 (or later maintenance).

• (SMP/E Requirement) From FMID HKDBvvv: Install OMEGAMON for DB2 product PTF that will be released as tracked in OMEGAMON for DB2 APAR PI82090

• (Configuration) Follow the SMPE03 maintenance scenario topic in the IBM Knowledge Center’s OMEGAMON Shared documentation to exploit the feature. Review the new KD2_* LPAR RTE profile parameters and new runtime members and jobs, as well as updated runtime members in support of the new feature.

• (Post-configuration) When available, review the product PTF HOLDDATA from FMID HKDBvvv for OMEGAMON for DB2 APAR PI82090 enablement support. APAR PI82090 will provide the links to access the product's "Monitoring Performance from the OMEGAMON Enhanced 3270 User Interface" documentation. Latter documentation includes the post-configuration requirements such as rerunning the OMEGAMON for DB2 OM* bind jobs per DB2 subsystem monitored as well as enablement for the updated TKANDATV KDP* elements if the Self-describing Agent feature is not enabled.

The PARMGEN “What’s New in PARMGEN 2Q17 IF PTF UA91952” entry documents as follows:

2.IBM Tivoli OMEGAMON XE for DB2 PE/PM V5.3.0: o Enable the configuration of thread history in the OMEGAMON Enhanced 3270 User Interface (enhanced 3270UI). OMEGAMON for DB2 "Thread history" on the enhanced 3270UI is the same capability as what's known as 'near-term history' in the OMEGAMON for DB2 Classic interface. OMEGAMON for DB2 APAR PI82090 delivers this same capability to the enhanced 3270UI for OMEGAMON for DB2. Both Near-Term History (Classic) and Thread History (enhanced 3270UI) data is stored in VSAM. The following parameters represent the valid values for storage type: - (New) THVSAM - Store the data to VSAM datasets for enhanced 3270UI Thread history support.

- (New) VSAMSEQTHVSAM - Store the data to VSAM datasets, sequential files for OMEGAMON DB2 Classic NTH support and VSAM datasets for enhanced 3270UI Thread history support. - (New) SEQTHVSAM - Store the data to sequential files for OMEGAMON for DB2 Classic NTH support and VSAM datasets for enhanced 3270UI Thread history support. - (New) VSAMTHVSAM - Store the data to VSAM datasets for OMEGAMON DB2 Classic NTH support and VSAM datasets for enhanced 3270UI Thread history support. Summary of near-term-history related configuration enhancements (applicable to both TOM thread history and Classic history): o New PARMGEN parameters enable configuration of thread history The following new parameters allow you to specify how thread history will be collected: THRDLOG (PARMGEN parameter KD2_PFnn_THRDHIS_LOG_NUM) THRDSQL (PARMGEN parameter KD2_PFnn_THRDHIS_DYN_SQL) THRDSCAN (PARMGEN parameter KD2_PFnn_THRDHIS_SCAN_SUMM) THRDSORT (PARMGEN parameter KD2_PFnn_THRDHIS_SORT_SUMM) THRDSUSP (PARMGEN parameter KD2_PFnn_THRDHIS_LOCK_SUSP) THRDCONT (PARMGEN parameter KD2_PFnn_THRDHIS_LOCK_CNTN) o To support thread history in the OMEGAMON Enhanced 3270UI, new COPT&dbid parameter values that are THVSAM-related have been added to the WRITEOPTION parameter of the %RTE_HILEV%.%RTE_NAME%.RKD2PAR(COPT&dbid) runtime member. In addition, several new parameters, THRDSQL, THRDCONT, THRDSUSP, THRDSCAN, and THRDSORT, have been added for data collection. o Two new COPT&dbid parameters, THRDLOG and THRDDATASET, can be used to control VSAM datasets. The maximum number of VSAM datasets is 60 for Enhanced 3270UI thread history. The PARMGEN LPAR RTE profile parameters supporting the new COPT&dbid parameters are: - THRDLOG(%KD2_PFnn_THRDHIS_LOG_NUM%) - THRDDATASET(%KD2_OMPE_VSAM_DSHLQ%.%DB%.RKTH*) o New VSAM dataset allocation logic: The general logic of allocating VSAM data sets for Near Term History has changed. Now, the selected types of datasets are allocated only if the thread history flag (%KD2_PFnn_HIS_START%) is set to Y. If this flag is set to N, no data sets are allocated and WRITEOPTION() is changed to NONE. For staging purposes, new standalone VSAM allocation jobs are provided in %RTE_HILEV%.%RTE_NAME%.RKD2SAM dataset as follows: * Standalone Job Versions: Applicable if KD2_PFnn_HIS_START = "Y": - RKD2SAM(TCRV&dbid) for OMEGAMON enhanced 3270UI thread history o THRDDATASET(%KD2_OMPE_VSAM_DSHLQ%.%DB%.RKTH*) VSAM LDS - RKD2SAM(HCRV&dbid) for Classic NTH: o H2DATASET(%KD2_PF_HIS_LOGn%) VSAM LDS o New imbed increases allowable VSAM datasets: A new WCONFIG(KD2$PCOP) imbed has been added to the H2DATASET() parameter in the COPT&dbid member. This allows you to enable more than seven Classic RKD2VSnn thread history VSAM datasets. The limit for the VSAM datasets number for thread history is now 1024. Only seven datasets can be set via PARMGEN and only 3 datasets can be set via ICAT configuration tool; the others should be specified in WCONFIG(KD2$PCOP) prior to submitting the WCONFIG($PARSE*)-related "Create runtime members" and WKANSAMU(KCIJPW2R) "Copy runtime mbrs

from WK*->RK* RW libs" jobs. o New default sizes and units for memory: The default size and memory measurement units are changed from 10 Cylinders (CYLS) to 900 MegaBytes (MB) when allocating the thread history datasets. The value is controlled via two profile parameters: - KD2_PFnn_HIS_VSAM_SU (new default=MB) - KD2_PFnn_HIS_VSAM_MB (new default=900) Existing RTEs are not impacted; new defaults take effect for new RTEs. OMEGAMON for DB2-related allocation jobs such as RKD2SAM(ALLOCDS) composite OMEGAMON for DB2 NTH allocation job, new RKD2SAM(TCRV&dbid) standalone RKTH* enhanced 3270UI thread history dataset allocation job, existing RKD2SAM(HCRV&dbid) standalone RKD2VS* Classic NTH VSAM dataset allocation job, are all modified to support the new MEGABYTES(%KD2_PFnn_HIS_VSAM_MB%) parameter value. o Add support for a new GRANT command for the SYSIBM.SYSCOLUMNS table in the %RTE_HILEV%.%RTE_NAME%.RKD2PAR(OMGR&dbid) member: GRANT SELECT ON SYSIBM.SYSCOLUMNS to %KD2_CLASSIC_DB2PM_PLANPKG_OWNER%; o Change the default values of DB2RTCPU and DB2REMIO parameters to YES in the %RTE_HILEV%.%RTE_NAME%.RKD2PAR(OMPEOPTS) runtime member applicable to new runtime environments (RTEs) that configure OMEGAMON for DB2. Existing RTEs are not impacted. For more information, refer to OMEGAMON for DB2 HKDBvvv APAR PI82090, which provides the links to access the product's "Monitoring Performance from the OMEGAMON Enhanced 3270 User Interface" documentation.

[Source: Query from our OMEGAMON enhanced 3720UI webcast (Featured topic: "Modernizing your OMEGAMON Environment: Monitoring DB2 with the Enhanced 3270UI" presented by Paul Kenney) held July 26th]

Q#2: “What do I specify for GBL_USS_TKANJAR_PATH parameter?”

• A#2: See GBL_USS_TKANJAR_PATH details in the “Common parameters” topic in the OMEGAMON shared publications in IBM Knowledge Center or review the corresponding PARMGEN on-line help panels:

If you did not perform the SMP/E installation of the OMEGAMON for JVM product (FMID HKJJ540) or the OMEGAMON for CICS TG component (FMID HKGW530), check the %GBL_TARGET_HILEV%.CSI’s TKANJAR DDDEF setting: ---------------------- SMP/E PRIMARY OPTION MENU ---------------- SMP/E 36.78

===> 3

0 SETTINGS - Configure settings for the SMP/E dialogs

1 ADMINISTRATION - Administer the SMPCSI contents

2 SYSMOD MANAGEMENT - Receive SYSMODs and HOLDDATA

and install SYSMODs

3 QUERY - Display SMPCSI information

4 COMMAND GENERATION - Generate SMP/E commands

5 RECEIVE - Receive SYSMODs, HOLDDATA and

support information

6 MIGRATION ASSISTANT- Generate Planning and Migration Reports

7 ORDER MANAGEMENT - Manage ORDER entries in the global zone

D DESCRIBE - An overview of the dialogs

T TUTORIAL - Details on using the dialogs

W WHAT IS NEW - What is New in SMP/E

Specify the name of the CSI that contains the global zone:

SMPCSI DATA SET ===> 'TDITNT.DEV.ITM63055.CSI'

QUERY SELECTION MENU

===> 2

1 CSI QUERY - Display SMPCSI entries

2 CROSS-ZONE QUERY - Display status of an entry in

The value in the “PATH” is what you would specify for the GBL_USS_TKANJAR_PATH value in the RTE’s WCONFIG($GBL$USR) user profile. If this value is not supplied if PARMGEN detects that the products that have TKANJAR DDDEF requirement is being configured, the WCONFIG($PARSE*)-related job’s VALIDATE step, or the standalone WCONFIG(KCIJPVAL) validation job will provide the following protective prereq. checker:

After the $PARSE*-related “Create runtime members and jobs” generate the KCIJ* jobs to complete the PARMGEN set-up for the OMEGAMON products that have TKANJAR USS requirement, review the KCIJPUSP and KCIJPUSS jobs to learn more about what USS files and directories are processed.

Q#3: “What is PARMGEN’s FMID? What’s the latest ITM maintenance?”

• A#3: PARMGEN PTFs are delivered under the common HKCI310 FMID.

Tip: PARMGEN’s main welcome screen logs the latest PARMGEN maintenance:

Welcome screen’s help menu also provides important help topics that describe:

Master PARMGEN technote’s Section A1 also documents the PARMGEN PTFs under HKCI310 FMID:

For the ITM maintenance query, the Master PARMGEN technote’s Section B1 also documents important deployment technotes – the recommended product family maintenance technote is noted below. z/OS ITM infrastructure is comprised of the z/OS TEMS (FMID HKDS630) and z/OS TMS:Engine infrastructure (FMID HKLV630). The z/OS ITM FMIDs along with the PARMGEN FMID (HKCI310) are hard SMP/E requisites to all z/OS TMS:Engine-based products, including the OMEGAMON Family of monitoring Agents and other z/OS monitoring Agents in the Service Management Suite for z/OS and Advanced Storage Management Suite. z/OS ITM’s latest maintenance is ITM630 FP7. The corresponding PTFs are noted in this technote below ("Recommended Maintenance

Service Levels for IBM OMEGAMON and Advanced Storage Reporting products on ITM

V6.x ”: URL:http://www.ibm.com/support/docview.wss?uid=swg21290883:)

Q#4: “Are there OMEGAMON product toleration PTFs needed for z14? ”

• A#4: Not at this time. The OMEGAMON Family V5.3.0 releases (and higher versions) can run on z14 hardware. Related z/OS 2.3 currency support needed for the OMEGAMONs is documented in this common technote (also cross-referenced in Master PARMGEN

technote’s Section B1 ) URL (FIXCAT

ZOS0203T/K):http://www.ibm.com/support/docview.wss?uid=swg22003860

Q#5: “How do I convert my FULL RTE to SHARING Type?”

• A#5: See “How to: Convert a full RTE to a sharing RTE” topic in OMEGAMON Shared documentation in IBM Knowledge Center.

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held June 07, 2017

• 06/07/2017 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=1ac3ba09-136a-4b39-9057-862c957e56f7

C. Q&A Details:

• June 7, 2017 Q&A:

Q#1: “How do I quickly convert my existing RTE not currently using variables, to use best-practice

symbols?”

• A#1: See “Using best practice variables in PARMGEN configuration profiles” technote for detailed information. For planning purposes, enabling variables in an RTE requires:

• rebuilding the product runtime members a number of the parameter contents in these members now contain system symbols or best-practice user symbols

• refreshing product started tasks in system procedure library, and product VTAM major node members in system VTAMLST (if system symbols are used in VTAM-related profile parameters).

Please plan accordingly when enabling variables.

Q#2: “What jobs do I run after SMP/E maintenance?”

• A#2: See “SMP/E maintenance and upgrade scenarios” topic in the OMEGAMON shared publications in IBM Knowledge Center or review the corresponding PARMGEN on-line help panels:

Additional considerations: o If reconfiguring an RTE, see Maintenance Scenarios F1=Help topic on the "PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU" or review the SMPEnn maintenance scenarios in the IBM Knowledge Center publication. o If you will be reconfiguring the existing PARMGEN-created RTE, please review the SMP/E maintenance scenarios and decide which to follow depending on how much you want to exploit the new feature or function. o Tip: ***xKANSAMU(KCIJ*) Job Refresh*** Important PARMGEN KCIJP* maintenance considerations:

- if product PTFs have HOLDDATA to refresh their &gbl_target_hilev.TKANDATV Object Definition Information (ODI) SMP/E elements: o You typically would need to rerun the KCIJPLOD job per RTE (or LOADALL KCIJ@LOD cross-RTE job). - if product PTFs have HOLDDATA to refresh their &gbl_target_hilev.TKANSAM SMP/E product security exits and/or &gbl_target_hilev.TKANMOD SMP/E product security modules for currency support: o You typically would need to rerun the KCIJPSEC composite security job per RTE (or SECALL KCIJ@SEC cross-RTE job). - if product PTFs have HOLDDATA to refresh their TKANJAR USS SMP/E elements: o You typically would need to rerun the KCIJPUSP and KCIJPUSS composite USS jobs per RTE. In most cases, rerunning the existing KCIJ* job in the RTE's W/RKANSAMU dataset is sufficient unless the product requires changes to the structure of the job itself (for example, new datasets to reload for the KCIJPLOD job, new security exits or new security modules to assemble/link for the KCIJPSEC job, etc.). If the product PTF HOLDDATA calls for these new element support that requires the KCIJ* jobs to be recreated, perform the following SMPE02 maintenance scenario steps:

- Rerun the WCONFIG(KCIJPUP1) "Refresh IK* templates/WCONFIG *$IBM profiles" job.

- Rerun the WCONFIG($PARSE*)-related job. - Rerun the WKANSAMU(KCIJ*) job identified by the product PTF HOLDDATA to be rerun.

- Rerun the WKANSAMU(KCIJPW2R) job.

Q#3: “How do I enable a new CICS region ONDV VSAM in the KC2GLB OMEGAMON CICS global?”

• A#3: To allocate a new OMEGAMON for CICS RKC2HIST VSAM dataset for the new CICS region, refer to the KC2_HS* LPAR RTE profile parameters. Tip: Use the F16=CLNESECT (Clone Section) PF Key macro as shown during the demo. If you plan to use the new PARMGEN KCIJPDLA job to autodiscover the on-line CICS regions, see Q#4 (“Does PARMGEN z/OS DLA integration support OMEGAMON CICS history configuration?”) in the April 12, 2017 Q&A Section. To enable the new RKC2HIST VSAM dataset in the existing KC2GLB global used in the OMEGAMON for CICS Classic started task’s RKC2GLBL DD, edit the global via PARMGEN by selecting option 10 in the PARMGEN Utilities panel. Option 10 allows one to manage the OMEGAMON globals (KC2GLB* for OMEGAMON for CICS and KIPGLB* for OMEGAMON for IMS).

From: KCIPGLB1 - CCAPI.DLA310.SP22.RKANPARU(KC2GLB) - 01.00----- COLUMNS 00001 00072 Command ===> Scroll ===> CSR For in-context HELP: Place cursor on selected line then press F1 000044 <DATABASE_COLLECTION> 000045 * 000046 <<VSAM>> 000047 AUTO_START=YES 000048 ONDV_WRITE=YES 000049 SMF_WRITE=NO … 000411 <ONLINE_VIEWER> 000412 DATA_STORE_TYPE=DSPACE 000413 DATA_STORE_SIZE=956 000414 RESERVED_SIZE=25

To:

Refer to the OMEGAMON for CICS IBM Knowledge Center documentation about KC2GLB globals management for more information.

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held May 10, 2017

• 05/10/2017 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=3be58bf5-3c37-4b2f-ae56-9a1f9f00d93c

C. Q&A Details:

• May 10, 2017 Q&A:

Q#1: “I created new RTE datasets as part of my upgrade, cloning config. values from the previous version's RTE WCONFIG dataset. Where in PARMGEN do I tell it to reuse my OMEGAMON CICS globals from the other RTE globals dataset?”

• A#1: See RTE_CLONE_* parameters in the RTE’s WCONFIG(&rte_name) LPAR RTE profile.

Customize these parameters prior to rerunning the WCONFIG($PARSE)-related “Create runtime members and jobs”.

The parameters are used in the KCIJPCLN job which is accessible in the RTE’s xKANSAMU datasets or in the PARMGEN Utilities panel:

Its use cases are noted in the job comments, as well as in the PARMGEN post-configuration step: ISREDDE2 CCAPI.DLA310.SP22.WKANSAMU(KCIDFINL) Command ===> Scroll ===> CSR 001056 Step 9 - (Conditional) Clone or migrate customized data from another 001057 RTE.

001058 001059 In general, the "Clone customized data from another RTE" job 001060 (KCIJPCLN) on the "UTILITIES" panel can be used to copy the data 001061 from the original RTE datasets to a new set of RTE datasets (VSAM, 001062 Non-VSAM) regardless if this is an upgrade of a product version 001063 configured in this RTE, and this new RTE is using a new set of 001064 datasets to preserve the "production" RTE datasets at the previous 001065 version, while this new upgrade RTE is in test, or this is simply a 001066 clone of another RTE within the same product version. 001067 ================================================================ 001068 | The steps in the KCIJPCLN job follow this naming convention: | 001069 |--------------------------------------------------------------| 001070 | CPDATFpp - if the RTE has customized Non-VSAM data to clone | 001071 | such as profiles, screenspaces, etc. | 001072 | CPEXITpp - if the RTE has sample members to clone | 001073 | such as security exits, etc. | 001074 | CPGLBLpp - if the RTE has customized globals to clone | 001075 | CPMODUpp - if the RTE has customized modules to clone | 001076 | such as security modules, globals, etc. | 001077 | CPNVSMpp - if the RTE has customized Non-VSAM data to clone | 001078 | such as profiles, screenspaces, workspaces, etc. | 001079 | CPSEQUpp - if the RTE has sequential data to clone | 001080 | CPVSAMpp - if the RTE has customized VSAM data to clone | 001081 | such as product situations, SDA status, etc. | 001082 | CPWENUpp - if the RTE has customized Non-VSAM data to clone | 001083 | such as workspaces, etc. | 001084 ================================================================ 001085 001086 KCIJPCLN's "CPMODUxx" step copies the product's customized 001087 security modules 001088 from: CCAPI.DLA310.LPAR1.RKANMODU 001089 to: CCAPI.DLA310.SP22.RKANMODU user load library 001090 001091 These dataset HLQ values are based on your customization settings 001092 in the LPAR RTE profile WCONFIG(SP22): 001093 o You are cloning the datasets from the runtime datasets that 001094 start with these RTE HLQs: 001095 ========================== =================================== 001096 PARMGEN CONFIG User PARMGEN CONFIG Value 001097 Parameter 001098 ========================== =================================== 001099 RTE_CLONE_FROM_HLQRTE CCAPI.DLA310.LPAR1 001100 RTE_CLONE_FROM_VSAM_HLQRTE CCAPI.DLA310.LPAR1 001101 001102 o You are cloning the datasets to the runtime datasets that 001103 start with these RTE HLQs: 001104 ========================== =================================== 001105 PARMGEN CONFIG User PARMGEN CONFIG Value 001106 Parameter 001107 ========================== =================================== 001108 RTE_HILEV CCAPI.DLA310 001109 RTE_VSAM_HILEV CCAPI.DLA310 001110 001111 Depending on your upgrade deployment phase, you may need to rerun 001112 the KCIJPSEC "Run product security steps" job after submitting 001113 KCIJPCLN job. 001114 001115 If you are submitting the KCIJPCLN job as part of upgrading the 001116 OMEGAMON products that support Classic commands (OMEGAMON for CICS, 001117 DB2, IMS and z/OS) and part of the upgrade includes product PTF 001118 maintenance that includes PTF HOLDDATA instructions to enable new 001119 commands to the OMEGAMON Classic Interface, then ensure that you 001120 rerun the KCIJPSEC "Run product security steps" job on the "SUBMIT 001121 BATCH JOBS TO COMPLETE PARMGEN SETUP" (KCIP@SUB) panel. The 001122 KCIJPSEC job in the RTE's xKANSAMU dataset will pickup the new 001123 commands and security.

001124 001125 Review the KCIJPCLN job for other upgrade considerations. 001126

The OMEGAMON shared documentation also provides additional details: https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/howto_clone_custom_data.htm

Q#2: “What are the requirements to use the PARMGEN z/OS DLA (KCIJPDLA) "Composite PARMGEN z/OS Discovery Library Adapter (DLA) job" job?”

• A#2: See “Preinstallation Requirements and Instructions” technote for more details on the PARMGEN KCIJPDLA job. Tip: Search on the HIZD310 FMID SMP/E requirement topic. The PARMGEN KCIJPDLA job comments (Section A2) also provide important details on the SMP/E and system requirements prior to usage: ISREDDE2 CCAPI.DLA310.SP22.WCONFIG(KCIJPDLA) Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************** 000001 //CCAPIDLA JOB (ACCT),'PARMGEN KCIJPDLA',CLASS=A, 000002 // MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M 000003 //** 0 0 RTE_NAME=SP22 SYSMEMBER=KCIJPDLA 000004 //** \_~_/ SYSJOBNAME=CCAPIDLA JOBPARM SYSAFF=SP22 000005 //* ******************************************************************* 000006 //* 000007 //* NAME: KCIJPDLA 000008 //* 000009 //* PURPOSE: This composite KCIJPDLA job performs these functions: 000010 //* 000011 //* A. DLADISC STEP (KCIJPDL1 JOB FUNCTION): 000012 //* This autodiscovery step executes the z/OS Discovery 000013 //* Library Adapter (DLA) code in FMID HIZD310 to build 000014 //* the DLA IDML books, which contain autodiscovered 000015 //* properties about on-line subsystems and system values 000016 //* for this SP22 LPAR RTE or 000017 //* for a target LPAR that this RTE will be deployed to. 000018 //* 000019 //* B. DLARPGEN STEP (KCIJPDL2 JOB FUNCTION): 000020 //* This report generator step takes a z/OS Discovery 000021 //* Library Adapter (DLA) IDML dataset as input to create 000022 //* a PARMGEN DLA report ($DLARPT) for SP22 000023 //* LPAR RTE or for a target LPAR that this RTE will be 000024 //* deployed to. 000025 //* 000026 //* C. DLABKPRF/DLAJPPRF STEP (KCIJPDL3 JOB FUNCTION): 000027 //* This user profile backup/refresh step refreshes the 000028 //* PARMGEN LPAR RTE user profile (SP22 000029 //* in the RTE WCONFIG dataset), and the global user 000030 //* profile ($GBL$USR in the RTE WCONFIG dataset) with 000031 //* extracted DLA autodiscovered data from the $DLARPT 000032 //* report for this SP22 LPAR RTE. 000033 //* It also updates certain WCONFIG override imbeds such 000034 //* as KMQ$CUSR, KQI$XML imbeds for OMEGAMON for 000035 //* Messaging product, and KJJ$DL* imbeds for OMEGAMON 000036 //* for JVM product, and applicable product 000037 //* post-configuration READMEs such as KJJDFINL for 000038 //* OMEGAMON for JVM and KQIDFINL for OMEGAMON for 000039 //* Messaging with PARMGEN $DLARPT DLA extracted data.

000040 //* This job also generates a $DLAMAP cross-mapping 000041 //* report of $DLARPT parameters that map to the profile 000042 //* parameters in the SP22 LPAR RTE user profile 000043 //* and the $GBL$USR global user profile. 000044 //* 000045 //* USAGE NOTES: 000046 //* A. DLADISC STEP (KCIJPDL1 JOB FUNCTION): 000047 //* Standalone Job Version: WCONFIG(KCIJPDL1) job 000048 //* 000049 //* A1. DLADISC step dynamically creates the DLA IDML dataset as: 000050 //* - CCAPI.DLA310.SP22.IZD.IDML 000051 //* 000052 //* Important Refresh Considerations: 000053 //* DELIDML step deletes any existing IDML dataset by this dataset 000054 //* name then (re)creates the DLA IDML books: 000055 //* - CCAPI.DLA310.SP22.IZD.IDML 000056 //* 000057 //* (Conditional) Override the 000058 //* IDMLDSN=CCAPI.DLA310.SP22.IZD.IDML parameter 000059 //* if you are not using the default PARMGEN IDML dataset name. 000060 //* The IDML dataset name used in both DLADISC and DLARPGEN steps 000061 //* must match. 000062 //* 000063 //* A2. (Required) Modify the %GBL_TARGET_IZDHLQ% reference in this job 000064 //* to point to the SMP/E high-level qualifier where you installed 000065 //* the z/OS DLA FMID HIZD310. 000066 //* 000067 //* Important System Requirements: 000068 //* 2a. This job must run authorized. Dynamic SETPROG APF 000069 //* statement has been included in this job. 000070 //* 000071 //* (Required) If the z/OS DLA SMP/E target load library 000072 //* (%GBL_TARGET_IZDHLQ%.SIZDLOAD) 000073 //* resides in a NONSMS-managed volume, the dynamic SETPROG 000074 //* APF statement must specify the VOL() volume parameter. 000075 //* 000076 //* For example: 000077 //* // SETPROG APF,ADD, 000078 //* // DSN=TDITNT.DEV.ITM63053.SIZDLOAD,VOL(VOL001) 000079 //* =========== 000080 //* If you supplied a GBL_TARGET_VOLUME value during KCIJPCFG 000081 //* "Set up/Refresh PARMGEN work environment" processing 000082 //* (KCIP@PG2 panel), then the KCIJPDLA job's SETPROG 000083 //* statement will include the tailored VOL() parameter. If 000084 //* this is not the volume that the SIZDLOAD dataset resides 000085 //* on, customize the VOL() parameter accordingly. Otherwise, 000086 //* the DLADISC step will encounter the following error 000087 //* message: 000088 //* "IZD0021E APF Discovery requested but not running APF 000089 //* Authorized" 000090 //* 000091 //* (Best practice) Plan ahead when it is ideal to run the 000092 //* DLADISC discovery function (KCIJPDL1 job function of the 000093 //* KCIJPDLA composite job) when the z/OS resources you plan 000094 //* to monitor are active. 000095 //* 000096 //* 2b. If you are staging the IDML datasets on behalf of other 000097 //* LPARs, you have the option to use the "/*JOBPARM SYSAFF=" 000098 //* parameter as shown in the examples below: 000099 //* /*JOBPARM SYSAFF=SP22 000100 //* /*JOBPARM SYSAFF=* 000101 //* 000102 //* If you use the SYSAFF parameter, it requires that the LPAR 000103 //* belongs in the same JES Multi-Access Spool (MAS) Complex. 000104 //* 000105 //* If the system is not in the same MAS, an alternative is to

000106 //* route the job using the "/*ROUTE XEQ" parameter as shown 000107 //* in the example below: 000108 //* /*ROUTE XEQ SP22 000109 //* 000110 //* 2c. The user ID that runs the KCIJPDLA or KCIJPDL1 job must 000111 //* also have the following RACF authorities: 000112 //* 000113 //* o READ access is recommended for all the data sets in the 000114 //* system PARMLIB concatenation used during IPL. 000115 //* 000116 //* o READ access is required to profiles in the MQCMDS class 000117 //* (if active) to allow the z/OS DLA to issue MQ DISPLAY 000118 //* commands via the MQ command interface. 000119 //* 000120 //* o If RACF is used to protect DB2 resources, then authority 000121 //* is required to issue DB2 DISPLAY commands and to access 000122 //* (READ) SYSIBM resources using dynamic SQL. In addition, 000123 //* for the DB2 version autodiscovery, the z/OS DLA extracts 000124 //* the DB2 version via the Instrumentation Facility 000125 //* Interface (IFI). 000126 //* 000127 //* The IZDPDISC PROC and the auth. ID that runs the 000128 //* KCIJPDLA or KCIJPDL1 job must have the appropriate 000129 //* authorization to issue the DB2 commands for each DB2 000130 //* subsystem. 000131 //* 000132 //* - DB2 Authorities for each DB2 subsystem: 000133 //* Example SQL statements to authorize &user="IZDPDISC" 000134 //* 000135 //* GRANT DISPLAY,MONITOR1,MONITOR2 TO "IZDPDISC"; 000136 //* GRANT SELECT ON SYSIBM.SYSDATABASE TO "IZDPDISC"; 000137 //* GRANT SELECT ON SYSIBM.SYSTABLESPACE TO "IZDPDISC"; 000138 //* GRANT SELECT ON SYSIBM.SYSTABLES TO "IZDPDISC"; 000139 //* GRANT SELECT ON SYSIBM.SYSINDEXES TO "IZDPDISC"; 000140 //* GRANT SELECT ON SYSIBM.SYSCOLUMNS TO "IZDPDISC"; 000141 //* GRANT EXECUTE ON PROCEDURE SYSPROC.DSNWZP TO "IZDPDISC"; 000142 //* 000143 //* Note: Ensure that DB2 stored procedures (for example, 000144 //* DSNWZP) are loaded and running before submitting 000145 //* the KCIJPDLn job. 000146 //* 000147 //* o READ access is recommended to WebSphere configuration 000148 //* files. An OMVS segment with authority to issue the 000149 //* netstat, host and home commands. 000150 //*

Q#3: “Does PARMGEN KCIJPDLA or KCIJPDL3 "Refresh LPAR RTE user profiles with $DLARPT data" job preserve old DB2 subsystems I specified in the profile? What if they are just not running at the time KCIJPDLA or KCIJPDL1 job was reran?”

• A#3: Yes, if the new PARMGEN z/OS DLA job output in the RTE’s WCONFIG dataset such as the z/OS DLA IDML dataset, the $DLARPT DLA report, and the backup RTE profile $DLARTBK have subsystem rows no longer captured in the latest KCIJPDLA run, then the KCIJPDLA job ensures that those LPAR RTE profile parameters in the WCONFIG*&rte_name) profile are generated as commented out (placeholder rows) with the comment label that these rows were from the old $DLARPT profile: ISREDDE2 CCAPI.DLA310.SP22.WCONFIG(SP22) - 01.00 Columns 00001 00072 Command ===> Scroll ===> CSR ****** ***************************** Top of Data ******************************

- - - - - - - - - - - - - - - - - - 2305 Line(s) not Displayed 002306 KC2_HS01_CLASSIC_CICS_REGION "CICSAM42" * from $DLARPT - - - - - - - - - - - - - - - - - - - 3 Line(s) not Displayed 002310 KC2_HS02_CLASSIC_CICS_REGION "CICSAM43" * from $DLARPT - - - - - - - - - - - - - - - - - - - 4 Line(s) not Displayed 002315 KC2_HS03_CLASSIC_CICS_REGION "CICSDE02" * from $DLARPT - - - - - - - - - - - - - - - - - - - 4 Line(s) not Displayed 002320 KC2_HS04_CLASSIC_CICS_REGION "CICSDE03" * from $DLARPT - - - - - - - - - - - - - - - - - - - 4 Line(s) not Displayed 002325 KC2_HS05_CLASSIC_CICS_REGION "CICSMH03" * from $DLARPT - - - - - - - - - - - - - - - - - - - 4 Line(s) not Displayed 002330 KC2_HS06_CLASSIC_CICS_REGION "CICSWT22" * from $DLARPT - - - - - - - - - - - - - - - - - - 557 Line(s) not Displayed 002888 KGW_SA01_CTG_DAEMON_STC "CTGDEV01" * from $DLARPT - - - - - - - - - - - - - - - - - - - 5 Line(s) not Displayed 002894 KGW_SA02_CTG_DAEMON_STC "CTGDEV02" * from $DLARPT - - - - - - - - - - - - - - - - - - 1301 Line(s) not Displayed 004196 KD2_DB01_DB2_SSID DA1C * from $DLARPT 004197 KD2_DB01_DB2_VER 11 * from $DLARPT - - - - - - - - - - - - - - - - - - - 15 Line(s) not Displayed 004213 KD2_DB01_DB2_SYSNAME SP22 * from $DLARPT - - - - - - - - - - - - - - - - - - - 3 Line(s) not Displayed 004217 KD2_DB01_DB2_LOADLIB "DSN.VAR1M0.SDSNLOAD" * from $DLARPT 004218 KD2_DB01_DB2_RUNLIB "DSN.VAR1M0.SDSNLOAD" * from $DLARPT - - - - - - - - - - - - - - - - - - - 22 Line(s) not Displayed 004241 KD2_DB01_PWH_LOADLIB "DSN.VAR1M0.SDSNLOAD" * from $DLARPT 004242 KD2_DB01_PWH_EXITLIB "DSN.VAR1M0.SDSNEXIT" * from $DLARPT - - - - - - - - - - - - - - - - - - - 64 Line(s) not Displayed … 004862 KD2_DB07_DB2_SSID DC1D * from $DLARPT 004863 KD2_DB07_DB2_VER 12 * zDLA $DLARPT job no DB2 auth. - - - - - - - - - - - - - - - - - - - 15 Line(s) not Displayed 004879 KD2_DB07_DB2_SYSNAME SP22 * from $DLARPT - - - - - - - - - - - - - - - - - - - 3 Line(s) not Displayed 004883 KD2_DB07_DB2_LOADLIB "DSN.V12R1M0.SDSNLOAD" * from $DLARPT 004884 KD2_DB07_DB2_RUNLIB "DSN.V12R1M0.SDSNLOAD" * from $DLARPT - - - - - - - - - - - - - - - - - - - 22 Line(s) not Displayed 004907 KD2_DB07_PWH_LOADLIB "DSN.V12R1M0.SDSNLOAD" * from $DLARPT 004908 KD2_DB07_PWH_EXITLIB "DSN.V12R1M0.SDSNEXIT" * from $DLARPT - - - - - - - - - - - - - - - - - - - 64 Line(s) not Displayed 004973 **KD2_DB08_DB2_SSID DC1C * from $DLARPT 004974 **KD2_DB08_DB2_VER 12 * from old $DLARPT/RTE profile. - - - - - - - - - - - - - - - - - - - 15 Line(s) not Displayed 004990 **KD2_DB08_DB2_SYSNAME SP22 * from $DLARPT - - - - - - - - - - - - - - - - - - - 3 Line(s) not Displayed 004994 **KD2_DB08_DB2_LOADLIB "DSN.V12R1M0.SDSNLOAD" * from $DLARPT 004995 **KD2_DB08_DB2_RUNLIB "DSN.V12R1M0.SDSNLOAD" * from $DLARPT - - - - - - - - - - - - - - - - - - - 22 Line(s) not Displayed 005018 **KD2_DB08_PWH_LOADLIB "DSN.V12R1M0.SDSNLOAD" * from $DLARPT 005019 **KD2_DB08_PWH_EXITLIB "DSN.V12R1M0.SDSNEXIT" * from $DLARPT - - - - - - - - - - - - - - - - - - 1520 Line(s) not Displayed 006622 KI2_I101_CLASSIC_IMSID IC1D * from $DLARPT 006623 KI2_I101_CLASSIC_MPREFIX M1 * from $DLARPT - - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed 006625 KI2_I101_CLASSIC_STC OMEGOI1 * from $DLARPT 006626 KI2_I101_CLASSIC_VTAM_NODE K&SYSCLONE.OI1N * from $DLARPT 006627 KI2_I101_CLASSIC_VTAM_APPL_LOGON K&SYSCLONE.OI1 * from $DLARPT 006628 KI2_I101_CLASSIC_IMS_RESLIB IMS.VCRC.SDFSRESL * from $DLARPT - - - - - - - - - - - - - - - - - - 3230 Line(s) not Displayed 009859 KN3_TCPX02_SYS_NAME SP22 * from $DLARPT 009860 KN3_TCPX02_TCP_STC "TCPIP22" * from $DLARPT 009861 KN3_TCPX02_TCPIP_PROFILES_DSN "DCHSS.TCPIP.PROFILES" * from $DLARPT 009862 KN3_TCPX02_TCPIP_PROFILES_MBR "SP22" * from $DLARPT - - - - - - - - - - - - - - - - - - - 17 Line(s) not Displayed 009880 KN3_TCPX03_SYS_NAME SP22 * from $DLARPT 009881 KN3_TCPX03_TCP_STC "TCPIP22B" * from $DLARPT

009882 KN3_TCPX03_TCPIP_PROFILES_DSN "DCHSS.TCPIP.PROFILES" * from $DLARPT 009883 KN3_TCPX03_TCPIP_PROFILES_MBR "SP22B" * from $DLARPT - - - - - - - - - - - - - - - - - - 3953 Line(s) not Displayed ****** **************************** Bottom of Data ****************************

In this SP22 RTE example, DC1C DB2 subsystem was previously being monitored but a subsequent rerun of the KCIJPDLA job showed that the DC1CMSTR STC was not active at the time the KCIJPDLA job (or the KCIJPDL1 function #1 of KCIJPDLA composite job) was submitted – either due to DC1C DB2 was in the process of getting maintenance applied or the DB2 subsystem itself perhaps moved to another LPAR. In this case, PARMGEN ensures that those rows are still generated but just commented out so you have the option to uncomment the KD2_* profile parameters if DC1C DB2 needs to continue to be monitored. In this particular example, DC1C still needs to be monitored in this sample RTE LPAR.

• Tip: Stage when to run the DLADISC (Function #1 of the KCIJPDLA composite job) portion of the KCIJPDL* jobs. Review the KCIJPDLA job for more information.

Q#4: “Can the USS directory path names be changed?”

• A#4: Yes, the common RTE_USS_RTEDIR LPAR RTE profile parameter is customizable. ISREDDE2 CCAPI.DLA310.SP22.WCONFIG(SP22) Command ===> Scroll ===> CSR 000607 ** ----------------------------------------------------------------- - 000608 ** (Conditional) If any products in this RTE require Unix System 000609 ** Services (USS) directories be created, specify the RTE HFS/zFS home 000610 ** directory (#rtedir): 000611 ** Notes: 000612 ** 1. Specify the main RTE HFS/zFS home directory name if one of the 000613 ** following conditions is true: 000614 ** - you are enabling the Self-Describing Agent (SDA) functionality 000615 ** in the z/OS TEMS and Agents. SDA is applicable to Tivoli 000616 ** Management Services V6.2.3 and higher versions. 000617 ** - you are configuring one of these products that have SMP/E 000618 ** TKANJAR DDNAME Install directory USS requirements: 000619 ** o OMEGAMON for CICS TG (FMID HKGWvvv) 000620 ** o OMEGAMON for JVM (FMID HKJJvvv) 000621 ** and you are creating a Full RTE (RTE_TYPE=FULL) or a sharing 000622 ** RTE (except for SMP/E-sharing RTEs) (RTE_TYPE=SHARING / 000623 ** RTE_SHARE <> "SMP"). 000624 ** 000625 ** 2. System preparation planning considerations: 000626 ** o Set up required authorizations and files: 000627 ** - If you do not already have a user ID with superuser authority 000628 ** (TSO ID with an OMVS segment defined to it), then set-up one. 000629 ** 000630 ** 2A. SDA authorization requirements: 000631 ** Product configuration USS jobs (KCIJPUSP/KCIJPUSS) that use 000632 ** the RTE_USS_RTEDIR home directory parameter must be run by a 000633 ** user ID that has superuser authority (UID=0) or read access to 000634 ** resource BPX.SUPERUSER under the FACILITY class profile and 000635 ** superuser authority must be activated. 000636 ** 000637 ** Both the user ID of the KCIJPUS* USS job submitter and the 000638 ** %KDS_TEMS_STC% TEMS started task name must have superuser 000639 ** authority.

000640 ** 000641 ** 2B. Additional authorizations for SMP/E TKANJAR USS requirement: 000642 ** The user ID also requires read access to FACILITY class 000643 ** profiles: 000644 ** Note: Even a superuser (UID=0) also needs access to those 000645 ** profiles to allow pax -ppx or BPXCOPY APF PROGCTL or 000646 ** the extattr command for these options: 000647 ** o BPX.FILEATTR.PROGCTL 000648 ** o BPX.FILEATTR.APF 000649 ** 000650 ** As you are defining users, you might want to define some of them 000651 ** with appropriate superuser privileges. There are three ways to 000652 ** assign superuser authority. 000653 ** 1. Using the UNIXPRIV class profiles, the preferred way. See 000654 ** "Using UNIXPRIV class profiles." 000655 ** 2. Using the BPX.SUPERUSER resource in the FACILITY class. See 000656 ** "Using the BPX.SUPERUSER resource in the FACILITY class." 000657 ** 3. Assigning a UID of 0. 000658 ** 000659 ** For more information, see "Superusers in z/OS UNIX" publication: 000660 ** http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm. 000661 ** zos.v2r2.bpxb200/seca.htm?lang=en 000662 ** - Choose an existing file system or create a new one for 000663 ** products that use the RTE_USS_RTEDIR home directory parameter. 000664 ** This file system must be created, mounted, and in read/write 000665 ** mode before the UNIX System Services jobs that define the file 000666 ** system paths are submitted. Select a name for your RTE that 000667 ** establishes or fits a naming convention that can be used as 000668 ** you install additional RTEs. See KCIUSSJB sample job in the 000669 ** TDITNT.DEV.ITM63053.TKANSAM SMP/E target library. 000670 ** - In the MOUNT FILESYSTEM command, the MOUNTPOINT() parameter 000671 ** equates to the value you will specify for the RTE_USS_RTEDIR 000672 ** parameter. For example: 000673 ** "MOUNT FILESYSTEM('&hlq_rte_home') TYPE(ZFS) MODE(RDWR) 000674 ** MOUNTPOINT('/rtehome') PARM('AGGRGROW')" 000675 ** So an example of this using RTE name TSTEST might be: 000676 ** "MOUNT FILESYSTEM('OMVS.TSTEST.ZFS') TYPE(ZFS) MODE(RDWR) 000677 ** MOUNTPOINT('/tstest') PARM('AGGRGROW')" 000678 ** 3. The RTE_USS_RTEDIR value (#rtedir) is used in this TEMS parameter: 000679 ** "TEMS_MANIFEST_PATH=\ 000680 ** #rtedir/SP22/kds/support/TEMS" 000681 ** in xKANPARU(KDSENV). The TEMS_MANIFEST_PATH parameter is the 000682 ** name of the USS home directory where agent-uploaded jar files 000683 ** and other application support files will be stored by the TEMS. 000684 ** The #rtedir value is also used in KDS* members in RKANDATV and 000685 ** these KDS* members contain the commands to create the USS 000686 ** directories and send files to the USS sub-directories. 000687 ** 4. Customize RTE_USS_MKDIR_MODE parameter if you need to secure 000688 ** access mode to be used in the PARMGEN composite USS-related jobs 000689 ** (KCIJPUSP/KCIJPUSS). The default is "775" which translates to 000690 ** generating "MODE(7,7,5)" in the mkdir commands to create the new 000691 ** TEMS SDA directories. PARMGEN KCIJPUSP USS preparation job 000692 ** creates the RTE RKANDATV(KDSRMKDB) TEMS Self-Describing Agent 000693 ** (SDA) member that contains the SDA USS RTEDIR mkdir commands. 000694 ** MODE() is customized to site's security audit requirements based 000695 ** on the value supplied in the RTE_USS_MKDIR_MODE parameter. 000696 ** The RTE_USS_MKDIR_MODE parameter is only applicable to creating 000697 ** new USS directories. If the USS directories already exist and 000698 ** you want a different access mode for the directories and files, 000699 ** use the CHMOD command or delete the old directories before 000700 ** regenerating and rerunning the KCIJPUSS/KCIJPUSP jobs. 000701 ** For additional security considerations, see "Checklist: Prepare 000702 ** the system" on-line README topic on the "Welcome to the z/OS 000703 ** Installation and Configuration Tools for IBM Tivoli Management 000704 ** Services (TMS) dependent products" KCIP@PGW panel. 000705 ** 5. Related PARMGEN CONFIG profile parameters:

000706 ** - GBL_HFS_JAVA_DIRn (typically in WCONFIG($GBL$USR)) 000707 ** - GBL_DSN_SYS1_SBPXEXEC (typically in WCONFIG($GBL$USR)) 000708 ** - GBL_USS_TKANJAR_PATH (for products that deliver TKANJAR) 000709 ** - KDS_KMS_SDA 000710 ** - KDS_KMS_SDA_NO_GRANULAR (applicable to ITM6.3.0+ only) 000711 ** - KDS_TEMA_SDA 000712 ** - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA) 000713 ** ----------------------------------------------------------------- - 000714 RTE_USS_RTEDIR "/rtehome" 000715 RTE_USS_MKDIR_MODE "775"

The default is /rtehome. As noted in the profile comments, this value can be used for all your RTEs. The KCIJPUSP and KCIJPUSS composite jobs are tailored to generate the RTE name, as well as the product-specific sub-directories &rte_uss_rtedir/&rte_name/kds for TEMS SDA processing, &rte_uss_rtedir/&rte_name/kan for TKANJAR processing for products that ship SMP/E TKANJAR DDDEF, etc. It is not currently possible to change the directory structure of how this is named (for example, /&rte_name/&rte_uss_rtedir). Latter structure is not supported due to how the products use the RKANDATV values read @ product startup, respective to the products that have USS requirements. The PARMGEN “Submit batch jobs to complete PARMGEN setup” panel on-line helps provide more information as to how these values are used in the composite KCIJPUSP and KCIJPUSS jobs:

Q#5: “Question about the use and update of the KC2_HS table”

• A#5: These LPAR RTE profile parameters are used to define the OMEGAMON for CICS Classic ONDV application history VSAM LDS. Enabling these table parms. is PARMGEN’s trigger to allocate the RKC2HIST VSAM per CICS region. If you customized the OMEGAMON for CICS KC2GLB* globals read by the product at startup (via RKC2GLBL DD), to override the default dataspace to use these RKC2HIST VSAM as the application history

storage instead, then these datasets must exist prior to OMEGAMON for CICS Classic STC (KC2_CC01_CLASSIC_STC=&rte_stc_prefix.OC0 by default) startup. For more information regarding KC2_HS* table parameters available for customization during the PARMGEN “Customize PARMGEN configuration profiles”, refer to question #4 in the April 12, 2017 meeting minutes.

Q#6: “My RTEs are enabled for variables (static system symbols, and PARMGEN best-practice user symbols). How is &SYSIPHOSTNAME. used during product startup? Would I have to reconfigure all of my RTEs given our host system IP folks changed the resolution value to the fully qualified hostname rather than the usual DNS?”

• A#6: &SYSIPHOSTNAME. resolves to the value derived by an TCP/IP gethostname call. At product startup, the PARMGEN-generated started tasks enabled for variables (RTE_SYSV_SYSVAR_FLAG=Y) are resolved by the KCIPARSE symbolic substitution step based on what the system values are. During PARMGEN configuration work, values that typically point to &SYSIPHOSTNAME. are LPAR RTE product profile parameters that end in TCP_HOST. For example:

These values would resolve to where the primary TEMS that the Agents will report to. These parameters populate the following RKANPARU runtime members: - KppENV environmental file (KDSENV for TEMS, KC5ENV for the OMEGAMON for CICS

Agent, KD5ENV for OMEGAMON for DB2, KAHENV for System Automation monitoring Agent, KI5ENV for OMEGAMON for IMS, KJJENV for OMEGAMON for JVM, KMQENV for OMEGAMON for Messaging – MQ monitoring Agent, KNAENV for NetView

monitoring Agent, KN3ENV for OMEGAMON for Networks, KRGENV for Advanced Audit for DFSMShsm monitoring Agent, etc.). For an Agent, this contains where its primary or secondary TEMS that this Agent reports to.

- KDCSSITE z/OS RTEMS file which contains the communication values where its Hub TEMS that the z/OS RTEMS reports to.

- KSHXHUBS TEMS SOAP Server (Hub) Example of the product STC SYSPRINT DD resolution report looks like: SDSF OUTPUT DISPLAY OMEGDSR STC23629 DSID 102 LINE CHARS 'KDSENV' FOUND COMMAND INPUT ===> SCROLL ===> CSR PROCESSING MEMBER KDSENV LINES:00548 _____________________________________________________________ 00005 BEFORE * TSTEST.CCAPI.OM&LEV.&SYSNAME..IKANPARU(KDSENV) 00005 AFTER * TSTEST.CCAPI.OM4SYSG.IKANPARU(KDSENV) 00007 BEFORE * TSTEST.CCAPI.OM&LEV.&SYSNAME..WKANPARU(KDSENV) 00007 AFTER * TSTEST.CCAPI.OM4SYSG.WKANPARU(KDSENV) 00016 BEFORE KDS_VTAMID=K&SYSCLONE.DSDS 00016 AFTER KDS_VTAMID=KXXDSDS 00029 BEFORE HTTP:&HTTP_PORT. USE:Y \ 00029 AFTER HTTP:1920 USE:Y \ 00030 BEFORE IP.PIPE PORT:&KDS_HUB_PORT. \ 00030 AFTER IP.PIPE PORT:1918 \ 00031 BEFORE &KDS_KDETP_POOL_OPTIONS. &KDS_KDETP_OPTIONS. \ 00031 AFTER \ .. 00034 BEFORE IP.UDP PORT:&RTE_PORT. \ 00034 AFTER IP.UDP PORT:1918 \ .. 00035 BEFORE &KDS_KDETP_POOL_OPTIONS. &KDS_KDETP_OPTIONS. \ 00035 AFTER \ .. 00037 BEFORE IP6.PIPE PORT:&KDS_HUB_PORT. \ 00037 AFTER IP6.PIPE PORT:1918 \ 00038 BEFORE &KDS_KDETP_POOL_OPTIONS. &KDS_KDETP_OPTIONS. \ 00038 AFTER \ 00040 BEFORE IP6.UDP PORT:&RTE_PORT. \ 00040 AFTER IP6.UDP PORT:1918 \ 00041 BEFORE &KDS_KDETP_POOL_OPTIONS. &KDS_KDETP_OPTIONS. \ 00041 AFTER \ 00052 BEFORE KDCFC_ALIAS=K&SYSCLONE.DSLB 00052 AFTER KDCFC_ALIAS=KXXDSLB 00073 BEFORE KDS_XCFPLEXGROUP=&XCFPLEXGROUP. 00073 AFTER KDS_XCFPLEXGROUP=CCDPLEX 00074 BEFORE *KDS_KOS_PLEXNAME=&XCFPLEXGROUP. 00074 AFTER *KDS_KOS_PLEXNAME=CCDPLEX 00077 BEFORE KDS_KM5_DDS=&KM5_NTH_DDS.,&KM5_RMF_DDS. 00077 AFTER KDS_KM5_DDS=,NO 00080 BEFORE KM5_DXL_APPLID=K&SYSCLONE.M2RC

00080 AFTER KM5_DXL_APPLID=KXXM2RC 00086 BEFORE IP.PIPE:&SYSIPHOSTNAME.;\ 00086 AFTER IP.PIPE:SYSX;\ 00088 BEFORE &SYSVTAMNETID..\ 00088 AFTER IBMNETID.\ 00089 BEFORE K&SYSCLONE.DSLB.\ 00089 AFTER KXXDSLB.\ 00094 BEFORE *CTIRA_SYSTEM_NAME=&SYSIPHOSTNAME. 00094 AFTER *CTIRA_SYSTEM_NAME=SYSX ….. SDSF OUTPUT DISPLAY OMEGDSR STC23629 DSID 107 LINE CHARS 'IPV4' FOUND COMMAND INPUT ===> SCROLL ===> CSR interface_discovery") IPV4 interface(s): 'SYSX', mask=0x04:0x00 1.2.3.4: source=list(SYSX):0, seq=0, mask=0x26, default : source=hostname:0, seq=1 . BSS1_GetEnv") CT_CMSLIST="IP.PIPE:SYSX;SNA:IBMNETID.KXXDSLB.CANCTDCS.SNASOCKETS; =======================================================================

In the case of the IP hostname resolution value changing, there is no need to reconfigure the RTEs as the product started tasks will use the resolved IP hostname value. The RKANPARU runtime members have no further changes needed as inside those KppENV, KDCSSITE, etc. that use &SYSIPHOSTNAME. value, already point to the symbolic.

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held April 12, 2017

• 04/12/2017 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=eaf4b474-6eb4-42ec-ac71-19a90251dd08

C. Q&A Details:

• April 12, 2017 Q&A:

Q#1: “On our system that contains a Remote TEMS, we see connections from the OMEGAMON and Advanced Storage Agents connecting directly to the Hub TEMS in another LPAR and not going through the OMEGDS RTEMS in the local LPAR. Is there coding in the Agents that allows it to connect directly to the Hub (in another LPAR)?”

• A#1: Yes, the advanced Agent-specific Kpp_TEMS_BKUP1_* LPAR RTE profile parameters provide a secondary set of CT_CMSLIST connections based on the priority of the ordering of enabled protocols specified in the Kpp_AGT_COMM_PROTOCOLn LPAR RTE profile parameters. These CT_CMSLIST settings allow the Agent to connect to a

backup TEMS in the event that the primary TEMS is not available due to scheduled or unscheduled maintenance. These Kpp_TEMS_BKUP1_* parameters in the RTE’s &rte_plib_hilev.&rte_name.WCONFIG(&rte_name) LPAR RTE profile are disabled by default (commented out). Uncomment out the parameters for each Agent that will enable the backup TEMS feature. The sample below is for an RTE used during the demo, and this RTE has various z/OS monitoring Agents configured from the IBM Service Management Suite for z/OS (which includes the IBM OMEGAMON Performance Management Suite) and IBM Advanced Storage Management Suite. The PLB4SYSG RTE is enabled for variables (RTE_SYSV_SYSVAR_FLAG=Y).

If your RTE is not enabled for variables, specify the static IP hostname value of where the backup TEMS is running (if the Agent is connecting via an IP-related protocol such as IPPIPE, IPSPIPE, etc.). If the Agent is connecting via SNA, then specify the VTAM-related values used for the backup TEMS. For the RTE featured in our demo., we enabled the backup TEMS feature for the OMEGAMON for CICS Agent as shown below: ISREDDE2 TSTEST.CCAPI.PLB4SYSG.WCONFIG(PLB4SYSG) Command ===> Scroll ===> CSR

002639 ** ----------------------------------------------------------------- - 002640 ** (Optional) Secondary TEMS configuration: 002641 ** Note: Specify the Backup TEMS (KC5_TEMS_BKUP1_*) parameter values 002642 ** that the Agent will connect to if the Primary TEMS 002643 ** (KC5_TEMS_TCP_*/KC5_TEMS_VTAM_* parameters) is not available. The 002644 ** Agent's Primary and Backup TEMS parameter values are used in the 002645 ** CT_CMSLIST parameter in the Agent's xKANPARU(KC5ENV) member. 002646 ** ----------------------------------------------------------------- - 002647 002648 ** ----------------------------------------------------------------- - 002649 ** (Optional) Secondary TEMS TCP/IP information: 002650 ** ----------------------------------------------------------------- - 002651 KC5_TEMS_BKUP1_TCP_HOST "&AGT_TEMS_BKUP1_TCP_HOST." 002652 002653 ** ----------------------------------------------------------------- - 002654 ** (Optional) Secondary TEMS VTAM information: 002655 ** ----------------------------------------------------------------- - 002656 KC5_TEMS_BKUP1_VTAM_LU62_DLOGMOD &AGT_TEMS_BKUP1_VTAM_LU62_DLOGMOD. 002657 KC5_TEMS_BKUP1_VTAM_APPL_LLB_BKR &AGT_TEMS_BKUP1_VTAM_APPL_LLB_BKR. 002658 KC5_TEMS_BKUP1_VTAM_NETID &AGT_TEMS_BKUP1_VTAM_NETID.

Next, we customized those AGT_* best-practice user symbols in the PARMGEN global JCL’s PLB4SYSG variables RTE user profile to customize the resolution values of the user symbols. The variables RTE user profile is read by the product started task @ startup in the KCIPARSE step/CONFIG DD of the STC. In the case of this RTE, we customized the user symbols to point to a backup TEMS running in the SP22 IP hostname via IPPIPE, and if the backup TEMS is not available via IP connections, we also specified the VTAM values of the backup TEMS:

Next, we reran the $PARSEPR job to recreate the KppENV runtime members in the staging RTE’s WKANPARU dataset. The KC5ENV runtime member was recreated to add the 2nd set of CT_CMSLIST connection

values:

Next, we reran the KCIJPW2R job to refresh the KppENV runtime members to the product execution RKANPARU dataset, where the product started tasks run out of. When ready to deploy these changes, recycle the product started task to pick-up the newly enabled backup TEMS feature. Here is SYSPRINT DD of the OMEGAMON CICS Agent started task showing that KC5ENV has now enabled a backup TEMS feature: SDSF OUTPUT DISPLAY TSS4C5 STC20875 DSID 102 LINE CHARS 'KC5ENV' FOUND COMMAND INPUT ===> SCROLL ===> CSR PROCESSING MEMBER KC5ENV LINES:00466 _____________________________________________________________ 00005 BEFORE * TSTEST.CCAPI.PLB&LEV.&SYSNAME..IKANPARU(KC5ENV) 00005 AFTER * TSTEST.CCAPI.PLB4SYSG.IKANPARU(KC5ENV) 00007 BEFORE * TSTEST.CCAPI.PLB&LEV.&SYSNAME..WKANPARU(KC5ENV) 00007 AFTER * TSTEST.CCAPI.PLB4SYSG.WKANPARU(KC5ENV) 00010 BEFORE &KAG_KDETP_GBL_OPTIONS. \ 00010 AFTER \ 00011 BEFORE &KAG_KDETP_HTTP_OPTIONS. \ 00011 AFTER \ 00012 BEFORE IP.PIPE PORT:&KDS_HUB_PORT. \ 00012 AFTER IP.PIPE PORT:14731 \ 00013 BEFORE &KAG_KDETP_POOL_OPTIONS. &KAG_KDETP_OPTIONS. \ 00013 AFTER \ 00016 BEFORE IP.UDP PORT:&RTE_PORT. \ 00016 AFTER IP.UDP PORT:14731 \ 00017 BEFORE &KAG_KDETP_POOL_OPTIONS. &KAG_KDETP_OPTIONS. \ 00017 AFTER \ 00019 BEFORE IP6.PIPE PORT:&KDS_HUB_PORT. \ 00019 AFTER IP6.PIPE PORT:14731 \ 00020 BEFORE &KAG_KDETP_POOL_OPTIONS. &KAG_KDETP_OPTIONS. \ 00020 AFTER \

00022 BEFORE IP6.UDP PORT:&RTE_PORT. \ 00022 AFTER IP6.UDP PORT:14731 \ 00023 BEFORE &KAG_KDETP_POOL_OPTIONS. &KAG_KDETP_OPTIONS. \ 00023 AFTER \ 00026 BEFORE &KAG_KDETP_POOL_OPTIONS. &KAG_KDETP_OPTIONS. \ 00026 AFTER \ 00029 BEFORE &KAG_KDETP_POOL_OPTIONS. &KAG_KDETP_OPTIONS. \ 00029 AFTER \ 00032 BEFORE &KDEB_INTERFACELIST. 00032 AFTER !* 00036 BEFORE KDCFC_ALIAS=TS&SYSCLONE.C5NC 00036 AFTER KDCFC_ALIAS=TSSGC5NC 00044 BEFORE IP.PIPE:&SYSIPHOSTNAME.;\ 00044 AFTER IP.PIPE:WLAG;\ 00045 BEFORE IP.PIPE:&AGT_TEMS_BKUP1_TCP_HOST.;\ 00045 AFTER IP.PIPE:SP22;\ 00047 BEFORE &SYSVTAMNETID..\ 00047 AFTER USCACO01.\ 00048 BEFORE TS&SYSCLONE.DSLB.\ 00048 AFTER TSSGDSLB.\ 00051 BEFORE &AGT_TEMS_BKUP1_VTAM_NETID..\ 00051 AFTER USCACO01.\ 00052 BEFORE &AGT_TEMS_BKUP1_VTAM_APPL_LLB_BKR..\ 00052 AFTER TS1DSLB.\ 00053 BEFORE &AGT_TEMS_BKUP1_VTAM_LU62_DLOGMOD..SNASOCKETS; 00053 AFTER CANCTDCS.SNASOCKETS; 00058 BEFORE RTE_SECURITY_CLASS=&OMEGSAF. 00058 AFTER RTE_SECURITY_CLASS= 00179 BEFORE ** (ex.:KDE_LOOPBACK_POOL=&KDE_LOOPBACK_POOL., 00179 AFTER ** (ex.:KDE_LOOPBACK_POOL=55000-56023, 00180 BEFORE ** ZOSWTO_DESCRIPTOR_CODE=&KAG_ZOSWTO_DESCRIPTOR_CODE 00180 AFTER ** ZOSWTO_DESCRIPTOR_CODE=12), 00184 BEFORE ** TDITNT.COMMON.PARMGEN.JCL(PLB&LEV.&SYSNAME.) for this R 00184 AFTER ** TDITNT.COMMON.PARMGEN.JCL(PLB4SYSG) for this RTE

Here is RKLVLOG DD of the OMEGAMON CICS Agent started task showing that KC5ENV has now enabled a backup TEMS feature. If the primary TEMS in the local LPAR (WLAG IP hostname) is not available, the Agent will try the backup TEMS in the SP22 IP hostname:

Tips:

• If you are creating a brand new RTE, create it from the predefined QCFnn RTE models that are set-up for variables. For more information, see the Implementation Scenarios in the OMEGAMON shared publications: https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/PARMGEN_scenarios_intro.htm?pos=2

• If you want to reconfigure your existing RTE to enable variables, see the “Using best

practice variables in PARMGEN configuration profiles":

URL:http://www.ibm.com/support/docview.wss?uid=swg21683976 technote cross-referenced in Section B1 of the master PARMGEN technote (http://www.ibm.com/support/docview.wss?uid=swg21417935). For planning purposes, enabling variables in existing RTEs require product STC changes to include the symbolic substitution KCIPARSE step and RKANPAR/RKANCMD DD changes to include the temporary datasets where variable substitution processed members are concatenated. Please plan accordingly when integrating with your change controls scheduling.

•

Q#2: “Can z/OS monitoring Agents “bind” to more than one IP stack (we have multiple IP stacks)?”

• A#2: From our ITM Development team, a z/OS TMS:Engine address space (z/OS TEMS or z/OS monitoring Agent) binds to one IP stack. For IP load balancing, review your current LPAR RTE profile settings for the following parameters. Sample below is for the PLB4SYSG RTE used during the demo: ISREDDE2 TSTEST.CCAPI.PLB4SYSG.WCONFIG(PLB4SYSG) - 01.00 Columns 00001 00072 Command ===> Scroll ===> CSR 001267 ** ----------------------------------------------------------------- - 001268 ** Local z/OS TEMS communication protocols (TCP/IP information): 001269 ** Notes: 001270 ** 1. If this is a High-Availability Hub TEMS, KDS_TEMS_TCP_HOST

001271 ** parameter must be set to the DVIPA <dvipa_address> hostname. 001272 ** 2. The KDS_TEMS_TCP_STC parameter is used in the WKANPARU(KLXINTCP) 001273 ** member's "TCP/IP_USERID=&tcp_stc_value" parameter. The default 001274 ** value for the TCP/IP started task name is an asterisk (*). This 001275 ** default, which uses the first TCP/IP stack that was started, is 001276 ** suitable if the LPAR contains a single TCP/IP stack. If the 001277 ** LPAR contains more than one TCP/IP stack, you can specify the 001278 ** started task name of the TCP/IP stack you want to use; or you 001279 ** can specify the number sign (#), which is translated to a blank 001280 ** and allows the TCP/IP environment to choose the stack to use, 001281 ** either through TCP/IP definitions or through the use of the 001282 ** SYSTCPD DD statement. 001283 ** Related PARMGEN CONFIG profile parameters: 001284 ** - GBL_DSN_TCP_SYSTCPD_TCPDATA (typically in WCONFIG($GBL$USR)) 001285 ** - KAG_X_STC_SYSTCPD_INCLUDE_FLAG 001286 ** - KDS_X_STC_SYSTCPD_INCLUDE_FLAG 001287 ** - KDS_TEMS_KLX_TCP_TOLERATERECYCLE 001288 ** - KDS_HUB_* (z/OS Remote TEMS' primary Hub values) 001289 ** - KDS_X_HUB_* (z/OS Remote TEMS' standby Hub values) 001290 ** ----------------------------------------------------------------- - 001291 KDS_TEMS_TCP_HOST "&SYSIPHOSTNAME." 001292 KDS_TEMS_TCP_STC "#" 001293 001294 ** ----------------------------------------------------------------- - 001295 ** Local z/OS TEMS communication protocols (TCP/IP information): 001296 ** xKANPARU(KLXINTCP) TEMS runtime member IP-related settings: 001297 ** Note: 001298 ** Related PARMGEN CONFIG profile parameter: 001299 ** - KDS_TEMS_TCP_STC 001300 ** ----------------------------------------------------------------- - 001301 KDS_TEMS_KLX_TCP_TOLERATERECYCLE Y

Q#3: “How do I create a 2nd set of base libraries for my new maintenance?”

• A#3: See the following PARMGEN-tailored KCIJPBSA and KCIJPBSL jobs in the PARMGEN Utilities panel (or directly in the RTE’s xKANSAMU dataset). Samples are also provided in the SMP/E target dataset &gbl_target_hilev.TKANSAM):

Q#4: “Does PARMGEN z/OS DLA integration support OMEGAMON CICS history configuration?”

• A#4: Yes, KC2_HSnn_CICS_* OMEGAMON for CICS On-line Data Viewer (ONDV) application history configuration is full supported by the PARMGEN z/OS DLA autodiscovery function. The new PARMGEN z/OS DLA KCIJPDLA composite autodiscovery job is available for use during profile customization on step 2 of the PARMGEN process:

One may invoke the DLAJOB command:

Or access the jobs via PARMGEN Utilities:

For planning purposes, the only system preparation step is the SMP/E installation of the IBM Discovery Library Adapter for z/OS FMID (HIZD310) and the APF-authorizations needed, as documented in the job comments of the KCIJPDLA job: ========================================================================== ISREDDE2 CCAPI.DLA310.SP22.WCONFIG(KCIJPDLA) Command ===> Scroll ===> CSR 000056 //* A2. (Required) Modify the %GBL_TARGET_IZDHLQ% reference in this job 000057 //* to point to the SMP/E high-level qualifier where you installed 000058 //* the z/OS DLA FMID HIZD310. 000059 //* 000060 //* Important System Requirements: 000061 //* 2a. This job must run authorized. Dynamic SETPROG APF 000062 //* statement has been included in this job. 000063 //* 000064 //* (Required) If the z/OS DLA SMP/E target load library 000065 //* (%GBL_TARGET_IZDHLQ%.SIZDLOAD) 000066 //* resides in a NONSMS-managed volume, the dynamic SETPROG 000067 //* APF statement must specify the VOL() volume parameter. 000068 //* 000069 //* For example: 000070 //* // SETPROG APF,ADD, 000071 //* // DSN=TDITNT.DEV.ITM63053.SIZDLOAD,VOL(VOL001) 000072 //* =========== 000073 //* If you supplied a GBL_TARGET_VOLUME value during KCIJPCFG 000074 //* "Set up/Refresh PARMGEN work environment" processing 000075 //* (KCIP@PG2 panel), then the KCIJPDLA job's SETPROG 000076 //* statement will include the tailored VOL() parameter. If 000077 //* this is not the volume that the SIZDLOAD dataset resides 000078 //* on, customize the VOL() parameter accordingly. Otherwise, 000079 //* the DLADISC step will encounter the following error 000080 //* message:

000081 //* "IZD0021E APF Discovery requested but not running APF 000082 //* Authorized" 000083 //* 000084 //* (Best practice) Plan ahead when it is ideal to run the 000085 //* DLADISC discovery function (KCIJPDL1 job function of the 000086 //* KCIJPDLA composite job) when the z/OS resources you plan 000087 //* to monitor are active. 000088 //* 000089 //* 2b. If you are staging the IDML datasets on behalf of other 000090 //* LPARs, you have the option to use the "/*JOBPARM SYSAFF=" 000091 //* parameter as shown in the examples below: 000092 //* /*JOBPARM SYSAFF=SP22 000093 //* /*JOBPARM SYSAFF=* 000094 //* 000095 //* If you use the SYSAFF parameter, it requires that the LPAR 000096 //* belongs in the same JES Multi-Access Spool (MAS) Complex. 000097 //* 000098 //* If the system is not in the same MAS, an alternative is to 000099 //* route the job using the "/*ROUTE XEQ" parameter as shown 000100 //* in the example below: 000101 //* /*ROUTE XEQ SP22 000102 //* 000103 //* 2c. The user ID that runs the KCIJPDLA or KCIJPDL1 job must 000104 //* also have the following RACF authorities: 000105 //* 000106 //* o READ access is recommended for all the data sets in the 000107 //* system PARMLIB concatenation used during IPL. 000108 //* 000109 //* o READ access is required to profiles in the MQCMDS class 000110 //* (if active) to allow the z/OS DLA to issue MQ DISPLAY 000111 //* commands via the MQ command interface. 000112 //* 000113 //* o If RACF is used to protect DB2 resources, then authority 000114 //* is required to issue DB2 DISPLAY commands and to access 000115 //* (READ) SYSIBM resources using dynamic SQL. In addition, 000116 //* for the DB2 version autodiscovery, the z/OS DLA extracts 000117 //* the DB2 version via the Instrumentation Facility 000118 //* Interface (IFI). 000119 //* 000120 //* The IZDPDISC PROC and the auth. ID that runs the 000121 //* KCIJPDLA or KCIJPDL1 job must have the appropriate 000122 //* authorization to issue the DB2 commands for each DB2 000123 //* subsystem. 000124 //* 000125 //* - DB2 Authorities for each DB2 subsystem: 000126 //* GRANT DISPLAY,MONITOR1,MONITOR2 TO "IZDPDISC"; 000127 //* 000128 //* o READ access is recommended to WebSphere configuration 000129 //* files. An OMVS segment with authority to issue the 000130 //* netstat, host and home commands. ==========================================================================

When the KCIJPDLA job is submitted, the following functions are accomplished: A. DLADISC STEP (KCIJPDL1 JOB FUNCTION): This autodiscovery step executes the z/OS Discovery Library Adapter (DLA) code in FMID HIZD310 to build the DLA IDML books, which contain autodiscovered properties about on-line subsystems and system values for this SP22 LPAR RTE or for a target LPAR that this RTE will be deployed to.

B. DLARPGEN STEP (KCIJPDL2 JOB FUNCTION): This report generator step takes a z/OS Discovery Library Adapter (DLA) IDML dataset as input to create a PARMGEN DLA report ($DLARPT) for SP22 LPAR RTE or for a target LPAR that this RTE will be deployed to. C. DLABKPRF/DLAJPPRF STEP (KCIJPDL3 JOB FUNCTION): This user profile backup/refresh step refreshes the PARMGEN LPAR RTE user profile (SP22 in the RTE WCONFIG dataset), and the global user profile ($GBL$USR in the RTE WCONFIG dataset) with extracted DLA autodiscovered data from the $DLARPT report for this SP22 LPAR RTE. It also updates certain WCONFIG override imbeds for certain applications like OMEGAMON for Messaging Agents' KMQ$CUSR and KQI$XML imbeds if the product is configured in this RTE. The PARMGEN user profiles (LPAR RTE and $GBL$USR user profiles) are refreshed from autodiscovered data from the WCONFIG($DLARPT) DLA report. Here is an example of an LPAR RTE user profile refreshed with autodiscovered CICS, CICS TG and DB2 related system values on a test LPAR called SP22:

Here is an example of $GBL$USR global user profile refreshed with autodiscovered system libraries required for the product started tasks; STEPLIB DD concatenation, etc. for the various subsystems being monitored on a test LPAR called SP22:

PARMGEN KCIJPDLA autodiscovery job generates the parameters as enabled except for the OMEGAMON for CICS ONDV LPAR RTE profile KC2_HS Table BEGIN/END parameters. The CICS region per VSAM LDS dataset is autodiscovered so that customers simply need to uncomment out the main KC2_HS BEGIN/END table indicators to enable the allocation of the RKC2HIST VSAM per CICS region, in the PARMGEN KCIJPALO composite allocation job, or in the KC2HISJB standalone RKC2HIST allocation job. Enabling the KC2_HS table parameters enable the ONDV configuration. This is working as designed because the OMEGAMON for CICS product’s default application history ONDV storage is dataspace rather than the RKC2HIST VSAM LDS so PARMGEN does not allocate these VSAMs by default, unless the KC2_HS* parameters are enabled. See “Tip:” for more information:

General PARMGEN KCIJPLA enablement tips:

• See the PARMGEN KCIJPDLA videos in the master PARMGEN technote’s Section B2 PARMGEN Video Gallery.

• If you are licensed for the various product suites that PARMGEN helps deploy, the

4Q16 refresh of these suites include the IBM Discovery Library Adapter for z/OS FMID (HIZD310 FMID). This is the only SMP/E requirement prior to using the new PARMGEN KCIJPDLA jobs.

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held February 22, 2017

• 02/22/2017 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=70e42148-744d-457b-8fa1-052717f3c9e2

C. Q&A Details:

• February 22, 2017 Q&A:

Q#1: “Are there imbeds for SET commands I need to add in the TEMS started task before the PGM=KLV program?”

• A#1: See WCONFIG(KCI$SST1) imbed. For reference, other product-started task imbeds are available, as follows. ISREDDE2 CCAPI.DLA310.SP22SHBS.WCONFIG($MBDINDX) - 01.00 Columns 00001 00072 Command ===> Scroll ===> CSR

****** ***************************** Top of Data ****************************** 000001 ====================================================================== 000002 PARMGEN Maintenance Level: FMID HKCI310 PTF UA83283 APAR OA51503 000003 ====================================================================== 000004 ====================================================================== 000005 * * * P A R M G E N W C O N F I G I m b e d * * * 000006 ====================================================================== 000007 Imbed Library Imbed 000008 Name Type Purpose 000009 ======== ======== =================================================== 000113 KCI$SLOG xKANSAMU Common RKLVLOG DD/RKLVSNAP DD/ABNLIGNR DD imbed 000114 for all product started tasks that support these 000115 log/dump-related DDs. 000116 000124 KCI$SAPF xKANSAMU Common imbed to INCLUDE MEMBER 000125 %RTE_X_STC_INAPF_MEMBER_NAME% APF member's SET 000126 VARIABLES section. The composite INAPF INCLUDE 000127 statement is generated in all product started 000128 tasks (STCs) if RTE_X_STC_INAPF_INCLUDE_FLAG is 000129 overridden as Y. 000130 000131 Kpp$SDMP xKANSAMU Product-specific SYS%DUMP DD override in product 000132 started tasks that support these log/dump-related 000133 DDs. 000134 000135 KAG$SST1 xKANSAMU Common Agent STEPLIB DD override in all Agents 000136 started tasks. 000137 000138 KAG$SST2 xKANSAMU Common Agent RKANMODL DD override in all Agents' 000139 started tasks. 000140 000141 KAG$SST3 xKANSAMU Common Agent additional DD override in all 000142 Agents' started tasks (for example, add SYSMDUMP 000143 DD, etc. in each of the Agent started tasks 000144 (default xKANSAMU(IBMpp)). 000145 000146 Kpp$SST1 xKANSAMU Product-specific STEPLIB DD override in the 000147 product started task. 000148 000149 Kpp$SST2 xKANSAMU Product-specific RKANMODL DD override in product 000150 started task. 000151 000152 Kpp$SST3 xKANSAMU Product-specific additional DD override in 000153 product started tasks (for example, add SYSMDUMP 000154 DD, etc. in the product started task (default 000155 xKANSAMU(IBMpp)). 000156 . 000175 ====================================================================== 000176 Note: The list of WCONFIG override imbeds is also documented in the 000177 KCIJ$MBD member in the following datasets: 000178 - &rte_plib_hilev.&rte_name.WCONFIG($MBDINDX) 000179 - RTE's &rte_hilev.&rte_name.RKANSAMU(KCIJ$MBD)

000180 ====================================================================== 000181 ====================================================================== 000182 * * * P A R M G E N W C O N F I G I m b e d * * * 000183 ================================ END ================================= ****** **************************** Bottom of Data **************************** Tip: ▪ Customize these imbeds prior to running the $PARSE “Create runtime members and

jobs” so product started tasks have the user customizations when $PARSE creates the product started tasks in the RTE’s WKANSAMU dataset. You can use the WKANSAMU(KCIJPSYS) system copy job to copy the product started tasks from WKANSAMU to the dataset you specified in the GBL_DSN_SYS1_PROCLIB parameter in WCONFIG($GBL$USR).

Q#2: “What versions of the OMEGAMON products dropped the CUA interface?”

• A#2: OMEGAMON XE for Storage V5.4.0 (GA 11/11/2016) and OMEGAMON XE for DB2 PE/PM V5.4.0 (GA 12/09/2016). https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/com.ibm.omegamon.xe.pe_db2.doc_5.4.0/ko299/ko299_pe_about.htm

https://www-01.ibm.com/common/ssi/printableversion.wss?docURL=/common/ssi/rep_sm/2/872/ENUS5698-T02/index.html

Q#3: “We are a year behind in maintenance. What are best practices to upgrade?”

• A#3: See “Checklist: System preparation checklists”>”1. Checklist: Planning and Acquisition” write up on using Tivoli Serverpac as a maintenance strategy.

Tips:

• Use the Serverpac approach if you are upgrading some of the product versions as well as applying a lot of maintenance. If you are current on maintenance, it would be ideal to order the latest RSUyymm and simply reload the RTEs (KCIJPLOD job). See SMPE01 maintenance scenario (http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/scenarios_parmgen_maint_scenario.htm)

• If you use a Serverpac approach, when you invoke PARMGEN, execute the SMP/E TKANCUS that has the updated maintenance. You can stage each RTE at a time to point to the new GBL_TARGET_HILEV. You will be prompted by PARMGEN that it detected a new set of SMP/E target HLQ that you invoked. Navigate through “1. KCIJPCFG Set-up/Refresh” for each RTE and specify the new GBL_TARGET_HILEV on the KCIP@PG2 panel, then also specify a backup profile member as prompted, then Confirm=Y to regenerate and resubmit the KCIJPCFG job/KCIJPPRF profile refresh job. You would need to rerun the $PARSE job to recreate the runtime members and jobs to ensure that the new set of GBL_TARGET_HILEV is updated in various jobs and members. Finally, SUBMIT the KCIJP* jobs on the “Submit batch jobs to complete PARMGEN setup.”.

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held January 11, 2017

• 01/11/2017 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=54cf27c2-d825-4add-84bb-159e44c7c662

C. Q&A Details:

• January 11, 2017 Q&A:

Q#1: “Does PARMGEN support the KDSENV parm KDS_USERS_NO_MSGLOG=. If it does, would have to be added to each TEMS RTE one at a time?”

• A#1: See PARMGEN technote’s Section C2. What's New in 2Q16 PARMGEN IF? of the PARMGEN technote attachment. – see new KDS_USERS_NO_MSGLOG parameter. Add this parameter in the RTE’s WCONFIG(KD$PENV) prior to rerunning $PARSEPR job and KCIJPW2R job.

EDIT CCAPI.DLA310.SP22.WCONFIG(KDS$PENV) - 01.00 Columns 00001 00072 Command ===> Scroll ===> CSR 000166 ** o KDS_USERS_NO_MSGLOG=&userid parameter is used to suppress the 000167 ** z/OS TEMS RKLVLOG DD messages if the &userid TMS component is 000168 ** contained in a list. The list is provided by KDS_USERS_NO_MSGLOG 000169 ** KDSENV variable that the customer can modify as needed. When any 000170 ** IBM Tivoli Monitoring component does a logon or a logoff to the 000171 ** z/OS TEMS, the respective KDSMA009 and KDSMA011 messages are 000172 ** recorded in RKLVLOG MSG2/Operation log file. There can be use 000173 ** cases that result in large numbers of these KDSMA009 and 000174 ** KDSMA011 messages being recorded to RKLVLOG output. The large 000175 ** volumes of KDSMA009 and KDSMA011 messages result in excessive 000176 ** growth of RKLVLOG. Usage of KDS_USERS_NO_MSGLOG provides an 000177 ** ideal solution in that we should still be able to see these 000178 ** messages in most cases while suppressing the messages for 000179 ** "userids" that generate excessive numbers. Refer to FMID HKDS630 000180 ** APAR OA45650 for more information. 000181 ** Example usage: 000182 ** o z/OS TEMS RKLVLOG captured KDSMA* informational messages: 000183 ** KDSMA011 Logon successful to server SRVR01 user KMVCCC 000184 ** ====== 000185 ** ip.pipe:#&SYSIPADDRESS.(%RTE_TCP_PORT_NUM%). 000186 ** KDSMA009 User KMVCCC logged off server SRVR01. 000187 ** ====== 000188 ** o To suppress these KDSMA* messages for user=KMVCCC, specify: 000189 ** KDS_USERS_NO_MSGLOG=KMVCCC 000238 ** ****************************************************************** 000252 KDS_USERS_NO_MSGLOG=SRVR01,sysadmin 000253 *KDS_USERS_NO_MSGLOG=&KDS_USERS_NO_MSGLOG. Tips: ▪ If you will add the KDS_USERS_NO_MSGLOG parameter directly into each z/OS TEMS’

RTE’s RKANPARU outside PARMGEN controls, just ensure that you synchronize/add the same parameter in the PARMGEN RTE’s WCONFIG(KDS$PENV) member, so the next rerun of the following deployment jobs are performed, that PARMGEN preserves the RKANPARU(KDSENV) manual updates: ✓ $PARSE* job rerun (imbeds WCONFIG(KDS$PENV) into WKANPARU(KDSENV)

staging copy) ✓ KCIJPW2R job rerun (copies refreshed WKANPARU(KDSENV) into the product

execution RKANPARU(KDSENV) when you are ready to deploy the change) ▪ If you are enabled for RTE variables and you plan to enable

KDS_USERS_NO_MSGLOG=&KDS_USERS_NO_MSGLOG. Parameter using the user symbol, you can use &gbl_user_jcl(KCI$GBLV) to define the KDS_USERS_NO_MSGLOG

user symbol. Refer to the KCI$GBLV discussion in the PARMGEN 2Q16 IF “What’s New” discussion.

Q#2: “We modified RKANPARU(KM2IPARM) changing PROFILE=/I to PROFILE=XE. Where in PARMGEN do I change USER_PROFILE /I to XE?”

• A#2: If you will modify the OMEGAMON on z/OS RKANPARU(KM2IPARM) runtime member to change the PROFILE parameter from the default “/I” to “XE” customer override, ensure that you synchronize/update the KM2_CLASSIC_USER_PROFILE LPAR RTE profile parameter in the PARMGEN WCONFIG(&rte_name) RTE profile.

$PARSE (re)creates the KM2IPARM member’s PROFILE= parm. with this value.

Tips: ▪ If you will edit the PROFILE parameter directly in the RTE’s RKANPARU outside

PARMGEN controls, just ensure that you synchronize/update KM2_CLASSIC_USER_PROFILE parameter in the PARMGEN RTE’s WCONFIG(&rte_name) LPAR RTE profile, so the next rerun of the following deployment jobs are performed, then PARMGEN preserves the RKANPARU(KM2IPARM) manual updates: ✓ $PARSE* job rerun (recreates the WKANPARU(KM2IPARM) staging copy)

✓ KCIJPW2R job rerun (copies refreshed WKANPARU(KM2IPARM) into the product execution RKANPARU(KM2IPARM) when you are ready to deploy the change)

Q#3: “We ordered the new versions of the OMEGAMON products (DB2 / JVM / Storage - V540). Are there special upgrade?”

• A#3: See the slides in the “OMEGAMON Performance Management Suite V5.4 Deployment Chat (Presentation) - D20170111.pdf” presentation deck. Recommended and/or required PTFs: if upgrading to the latest OMEGAMON V540s or exploiting some of the recent OMEGAMON product Interim Features, we recommend reviewing Sections A1 and A2 in the master PARMGEN technote where the various PTFs are listed, along w/ the deployment considerations. Depending on how the customer site will roll-out the new versions (upgrading in place w/ regards to the SMP/E environment as well as the runtime environments -or- upgrading into brand new SMP/E environments and brand new product execution runtime datasets), review the SMP/E maintenance and upgrade scenarios in the OMEGAMON shared publications to decide whether you would want to do SMPE05 or SMPE06 upgrade scenario. We would recommend SMPE06 upgrade scenario as site is not just upgrading existing product versions (from OMEGAMON for DB2 V530 to OMEGAMON for DB2 V540, and from OMEGAMON for Storage V530 to OMEGAMON for Storage V540) but it is also installing, configuring and deploying a new OMEGAMON for JVM V5.4.0 product to be deployed in the existing RTEs and the same SMPE06 4 main steps will cover the upgrade steps needed for the other products (some being upgraded to V540, and some remaining at the current existing versions V530/V730), at the same time. We would also recommend reviewing the Planning an upgrade or installation section in the OMEGAMON shared publications. Some of the deployment considerations called out are as follows: ▪ For OMEGAMON for JVM V5.4.0, a new GBL_USS_TKANJAR_PATH parm. in

WCONFIG($GBL$USR) will be required for customization based on the features included in this new product version (health center agent-related packaging requirements). In customer's case, this will be similar to adding a new product in an existing RTE as the OMEGAMON for JVM (KJJ) Agent has not been previously configured so it's business as usual as far as deployment considerations when adding new subsystems to monitor. After the PARMGEN work, review the post-configuration steps if enabling detailed monitoring depending on the type of JVM to do detailed monitoring on. The OMEGAMON for JVM Knowledge Center has a good coverage of what the post-configuration effort entails. Similar info. is avail. in the PARMGEN OMEGAMON for JVM KJJ post-configuration tailored README. We also recommend reviewing the USS auth. requirements prior to the SMP/E work; similar USS authorizations are needed for the runtime equivalent of the TKANJAR installation USS

directory. GBL_USS_TKANJAR_PATH upgrade requirement is called out in the Basic Upgrade Requirement.

▪ For OMEGAMON for DB2 V5.4.0, if site will be exploiting DB2 V12, then a new set DB2 V12-related GBL_DSN_DB2_*_V12 2 parameters will be required for customization in the WCONFIG($GBL$USR). During PARMGEN reconfiguration, it would be ideal to run the new KCIJPDLA job as part of customizing the LPAR RTE profile and $GBL$USR user profiles. If the z/OS DLA FMID is installed (FMID HIZD310), the PARMGEN z/OS DLA integration job (KCIJPDLA) will autodiscover the on-line subsystems running (CICS, DB2, IMS, JVMs, CTG, etc.) and will refresh the PARMGEN user profiles’ respective profle parameters with discovered data. After the PARMGEN work, review the post-configuration steps which outline required steps such as rerunning the DB2 bind/grant jobs.

▪ Site also has OMEGAMON on z/OS and OMEGAMON for Messaging --- these 2 products released Fixpacks/IFs in 4Q16 (respective PTFs listed in Section A2 of the master PARMGEN technote) -- if enabling some of the features, see the links in the technote if you want to customize the new LPAR RTE profile parameters.

▪ To review what other product features and functions are now available, review the respective PARMGEN, enhanced 3270UI, and product-specific "What's New"/"New in this Release" topics as referenced in Section A1/A2 of the master PARMGEN technote or in the PARMGEN main welcome screen (for product new versions and Ifs that introduced new PARMGEN profiles parameters or updates to existing jobs):

Previous 2016 Meeting Minutes:

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held October 26, 2016

• 10/26/2016 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: http://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=db5f581f-f470-41a4-9818-7dc4dddd086e

C. Q&A Details:

• October 26, 2016 Q&A:

Q#1: “How do I increase the history files?”

A#1: See “How to: Change PDS file count and file size” in IBM Knowledge Center (URL: http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/howto_increase_pdsfilecount.htm)

This is also related to Q#1 from August 10, 2016 Q&A call. See slides #53-#55 in Section C3. What's New in 3Q15 PARMGEN IF? Of the PARMGEN technote attachment as shown below. Specific to OMEGAMON XE for DB2 where this query was posed for, the PARMGEN RTE profile parameters of RTE_PDS_* common persistent datastore RTE settings and the product’s KD5_PD_CYL parameters control the allocation and set-up of the %RTE_PDS_HILEV%.RKD5HISn ITM persistent datastore sequential files used by the OMEGAMON for DB2 Agent (KD5) started task (KD5_AGT_STC) to record the near-term history data for enhanced 3270UI NTH use, or distributed TEPS use to render history data. The OMEGAMON for DB2 application history for thread near-term-history (NTH) store its data in the DB2-specific RKD2VSnn VSAM datasets, of which dataset names are customized in the PARMGEN’s “KD2_PF01_HIS_LOGn” profile parameters in the RTE’s WCONFIG(&rte_name) LPAR RTE profile.

Q#2: “We have 2 TEPS, one for PROD and one for TEST. Is it possible to have two primary sysplex proxies running in a given Sysplex?”

• A#2: Yes as long as the PROD RTE TEMS that is eligible to become a primary or a backup sysplex proxy is using a different set of persistent datastore sequential files to collect PLEXDATA-level data (RKM5PLXn) and a different KDS_XCFPLEXGROUP value in the respective RTE’s RKANPARU(KDSENV), from the TEST RTE TEMS that is also eligible to act as a sysplex proxy.

To illustrate using the PLB1SP22 RTE example showcased during the October 26th webcast: PLB1SP22 RTE – TEMS in this RTE is eligible to be a sysplex proxy and it is collecting OMEGAMON XE on z/OS persistent datastore history data in TSTEST.CCAPI.CCDPLEX.RKM5PLXn sequential files. The PARMGEN WCONFIG(PLB1SP22) LPAR RTE profile parameters are set-up as follows: ISREDDE2 TSTEST.CCAPI.PLB1SP22.WCONFIG(PLB1SP22) Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************** 000878 RTE_PDS_HILEV TSTEST.CCAPI.PLB1SP22.PDS 000884 RTE_PDS_FILE_COUNT 6 * xKANPARU(KppAL) option 008701 KM5_SYSPLEX_PROXY_POSITION PRIMARY * Primary, Backup, Exclude 008740 GBL_SYSPLEX_NAME_XCFPLEXGROUP CCDPLEX 008765 KM5_PDS_RKM5PLX_PLEXDATA_HILEV TSTEST.CCAPI.CCDPLEX 008792 KM5_PD_HISTCOLL_DATA_IN_TEMS_STC Y 008793 KM5_PD_CYL_LPARDATA 605 * GROUP=LPARDATA 008794 KM5_PD_CYL_PLEXDATA 190 * GROUP=PLEXDATA

PARMGEN $PARSE “Create runtime members” job sets up the following OMEGAMON z/OS and TEMS runtime members based on these parameter values:

• TEMS KDSENV runtime member’s KDS_RUN statement has the KFAXCF parameter that determines if a TEMS is eligible to become a sysplex proxy @ TEMS startup. See "KOSKFA00: KOS101I CMS &RTE_TEMS_NAME_NODEID IS NOW THE SYSPLEX PROXY" messages in the TEMS RKLVLOG to determine if a TEMS is acting as the primary sysplex proxy, which means this TEMS is writing the data to the RKM5PLXn PLEXDATA seq. files.

ISREDDE2 TSTEST.CCAPI.PLB1SP22.WKANPARU(KDSENV) Command ===> 000069 KDS_XCFPLEXGROUP=CCDPLEX . 000191 KDS_RUN=\ . 000196 KFAXCF.FAXCSRV PRIMARY,PLEX;\

• PARMGEN KCIJPALO job allocates the OMEGAMON z/OS persistent datastore files for both the LPARDATA seq. files (RKM5LPRn) and PLEXDATA seq. files (RKM5PLXn). The RKM5PLXn seq. files are allocated if KM5_SYSPLEX_PROXY_POSITION is set to “PRIMARY“

ISREDDE2 TSTEST.CCAPI.PLB1SP22.WKANPARU(KM5AL)

Command ===> Scroll ===> CSR

****** ***************************** Top of Data ******************************

000001 * ******************************************************************

000002 * Member: KM5AL

000003 * Master Source: TDITNT.DEV.ITM63053.TKANPAR(KM5PRMLB)

000004 * KCIJPUP1 Batch Job Output:

000005 * TSTEST.CCAPI.PLB1SP22.IKANPARU(KM5AL)

000006 * $PARSE Batch Job Output:

000007 * TSTEST.CCAPI.PLB1SP22.WKANPARU(KM5AL)

000008 * ******************************************************************

000009 * This member is processed by xKANSAMU(KCIJPALO/KM5JPALP) PDS alloc. job

000010 ALLOC +

000011 DSN:TSTEST.CCAPI.PLB1SP22.PDS.RKM5LPR1 +

000012 SIZE=85M +

000013 STORCLAS=SCTSTEST MGMTCLAS=MCSTD +

000014 WINDOW=8

.

000036 DSN:TSTEST.CCAPI.PLB1SP22.PDS.RKM5LPR6 +

000037 SIZE=85M +

000038 STORCLAS=SCTSTEST MGMTCLAS=MCSTD +

000039 WINDOW=8

.

000190 ALLOC +

000191 DSN:TSTEST.CCAPI.CCDPLEX.RKM5PLX1 +

000192 SIZE=26M +

000193 STORCLAS=SCTSTEST MGMTCLAS=MCSTD +

000194 WINDOW=8

.

000215 ALLOC +

000216 DSN:TSTEST.CCAPI.CCDPLEX.RKM5PLX6 +

000217 SIZE=26M +

000218 STORCLAS=SCTSTEST MGMTCLAS=MCSTD +

000219 WINDOW=8

Q#3: “How do I exclude a TEMS from becoming a sysplex proxy?”

• A#3: Set the “KM5_SYSPLEX_PROXY_POSITION” LPAR RTE profile parameter to an EXCLUDE value.

To illustrate using the PLB4SYSG TEMS RTE example showcased during the October 26th webcast: PLB4SYSG RTE – TEMS in this RTE is not eligible to become a sysplex proxy @ TEMS startup. The PARMGEN WCONFIG(PLB4SYSG) LPAR RTE profile parameters are set-up as follows. Note that this RTE is set-up for variables: ISREDDE2 TSTEST.CCAPI.PLB4SYSG.WCONFIG(PLB4SYSG) Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************** 000878 RTE_PDS_HILEV TSTEST.CCAPI.PLB&LEV.&SYSNAME..PDS 000884 RTE_PDS_FILE_COUNT 6 * xKANPARU(KppAL) option 008701 KM5_SYSPLEX_PROXY_POSITION &XCFPROXY. * Primary, Backup, Exclude 008792 KM5_PD_HISTCOLL_DATA_IN_TEMS_STC Y 008793 KM5_PD_CYL_LPARDATA 605 * GROUP=LPARDATA 008794 KM5_PD_CYL_PLEXDATA 190 * GROUP=PLEXDATA PARMGEN Variables profile for this PLB4SYSG RTE needs to define the resolution value for the XCFPROXY user symbol – “EXCLUDE” in this case. ISREDDE2 PARMGEN.JCL(PLB4SYSG) Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************** 000104 XCFPROXY EXCLUDE Tip: If your variables profile was built before PARMGEN 2015 IF PTFs introduced a number of the best practice user symbols, refer to KCI$RTEV default IBM variables profile in the PARMGEN global JCL library for a full list of user symbols that you can use. PARMGEN $PARSE “Create runtime members” job sets up the following OMEGAMON z/OS and TEMS runtime members based on these parameter values:

• TEMS KDSENV runtime member’s KDS_RUN statement has the KFAXCF parameter that determines if a TEMS is eligible to become a sysplex proxy @ TEMS startup. User symbol &XCFPROXY. Is used as the KM5_SYSPLEX_PROXY_POSITION &XCFPROXY. value. You will not see "KOSKFA00: KOS101I CMS &RTE_TEMS_NAME_NODEID IS NOW THE SYSPLEX PROXY" messages in the TEMS RKLVLOG since this TEMS is not a sysplex proxy so it will not be collecting data in the RKM5PLXn PLEXDATA seq. files.

ISREDDE2 TSTEST.CCAPI.PLB1SP22.WKANPARU(KDSENV) Command ===> 000191 KDS_RUN=\

. 000196 KFAXCF.FAXCSRV &XCFPROXY.,PLEX;\ At TEMS startup, KCIPARSE step reads CONFIG DD to find the resolution value for XCFPROXY user symbol in the order of CFG() parm. which points to the default variables profile first (KCI$RTEV), then looks in the RTE user variables profile (PLB4SYSG RTE), then looks in the advanced global user variables profile, if enabled. SDSF OUTPUT DISPLAY TSS0DSR2 STC02382 DSID 3 LINE 394

COMMAND INPUT ===>

13 XXKCIPARSE EXEC PGM=IKJEFT1A,REGION=0M,

XX PARM=('KCIRPLB1 CFG(KCI$RTEV &SYS KCI$GBLV)',

XX 'KCIPRM(LV=S,MX=32000,MS=25000,LI=Y)')

XX* SYSPRINT resolves the user symbols – see SYSPRINT: 00199 BEFORE KFAXCF.FAXCSRV &XCFPROXY.,PLEX;\ 00199 AFTER KFAXCF.FAXCSRV EXCLUDE,PLEX;\ So when the TEMS comes up in KLV step, KDSENV uses “EXCLUDE” value: SDSF OUTPUT DISPLAY TSS0DSR2 STC02382 DSID 107 LINE 2,268 COLUMNS 23- 102 COMMAND INPUT ===> SCROLL ===> CSR (0029-D636B67B:kbbssge.c,72,"BSS1_GetEnv") KDS_RUN="KRANDREG; KSHCMS.WEBSQL; SRV EXCLUDE,PLEX; KOSSTART; KDFCINIT; KS3CINIT; KSMOMS; KT1CTL00.T Tip: It is ideal to set this as a user symbol so if this TEMS becomes eligible to become a sysplex proxy again, as long as the OMEGAMON z/OS persistent datastore files are allocated via KCIJPALO job or the standalone KM5JPALP job, then one can switch the resolution value for XCFPROXY user symbol to PRIMARY or BACKUP, then simply recycle the TEMS – no PARMGEN $PARSE rerun necessary.

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held August 10, 2016

• 08/10/2016 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: http://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=eb6c7ba0-b27e-49ee-874a-21dc4c18f494

C. Q&A Details:

• August 10, 2016 Q&A:

Q#1: “How do I set-up history in enhanced 3270UI, or can the NTH datasets be used in any way in enhanced 3270UI?“

• A#1: See slides #53-#55 in Section C3. What's New in 3Q15 PARMGEN IF? Of the PARMGEN technote attachment as shown below. Specific to OMEGAMON XE for DB2 where this query was posed for, the PARMGEN RTE profile parameters of RTE_PDS_* common persistent datastore RTE settings and the product’s KD5_PD_CYL parameters control the allocation and set-up of the %RTE_PDS_HILEV%.RKD5HISn ITM persistent datastore sequential files used by the OMEGAMON for DB2 Agent (KD5) started task (KD5_AGT_STC) to record the near-term history data for enhanced 3270UI NTH use, or distributed TEPS use to render history data. The OMEGAMON for DB2 application history for thread near-term-history (NTH) store its data in the DB2-specific RKD2VSnn VSAM datasets, of which dataset names are customized in the PARMGEN’s “KD2_PF01_HIS_LOGn” profile parameters in the RTE’s WCONFIG(&rte_name) LPAR RTE profile.

Q#2: “Can I turn of the comments in the profile?”

• A#2: Yes, one may use the F15=HIDECMNT (PF Key Hide Comments macro) as shown in the sample below, during “2. CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS” step:

Once in ISPF EDIT mode of any of the members presented on this panel, press F15 (or SHIFT key plus F3 key on your keyboard), and this will turn-off the comments:

Type RES or RESET to restore the comments back:

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held June 29, 2016

• 06/29/2016 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: http://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=250f5f5f-a9be-40f9-93d2-b69cd101db4c

C. Q&A Details:

• June 29, 2016 Q&A:

Q#1: “How do I enable the z/OS RTEMS to report to my FTO (Hot Standby) primary and backup Hub TEMS?“

• A#1: See the following parameters below in the WCONFIG LPAR RTE profile in order to set-up the KDSENV and KDCSSITE runtime members of the z/OS RTEMS to enable Hot Standby set-up for its distributed Hub TEMS (primary) and its standby Hub TEMS.

** Related PARMGEN CONFIG profile parameters:

** - KDS_TEMS_TCP_HOST (for IP-related protocols) ** - KDS_TEMS_TCP_*_PORT_NUM (for IP-related protocols) ** - KDS_TEMS_VTAM_* (for SNA-related protocol) ** - KDS_HUB_* (z/OS Remote TEMS' primary Hub values) ** - KDS_X_HUB_* (z/OS Remote TEMS' standby Hub values) ** ----------------------------------------------------------------- - Other references:

- PARMGEN technote’s Section C1. What's New in 2Q16 PARMGEN IF? of the PARMGEN technote attachment. – see new KDS_X_CMS_FTO_FLAG parameter introduced in UA81228 PTF

or add the CMS_FTO=YES parameter in the RTE’s WCONFIG(KD$PENV) prior to rerunning $PARSEPR job and KCIJPW2R job.

- How to: http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/howto_config_fto.htm

-

Q#2: “Is there a way to suppress the informational “KDSMA009 User xxx logged off server SRVR01” and “KDSMA011 Logon successful to server SRVR01 user xxx ip.pipe:#%KDS_TEMS_TCP_HOST% (%KDS_TEMS_TCP_PIPE_PORT_NUM%)” repeated TEMS RKLVLOG messages?”

• A#2: See PARMGEN technote’s Section C1. What's New in 2Q16 PARMGEN IF? of the PARMGEN technote attachment. – see new KDS_USERS_NO_MSGLOG parameter. Add this parameter in the RTE’s WCONFIG(KD$PENV) prior to rerunning $PARSEPR job and KCIJPW2R job.

Q#3: “I need to make changes to the SMP/E target NONSMS info. – how do I reinvoke the SPECIFY GBL_TARGET_HILEV PARAMETERS (KCIP@TLV) panel?”

• A#3: See new PARMGEN INIT option that can be passed on to the PARMGEN invocation.

For more information, see:

- PARMGEN technote’s Section C2. What's New in 1Q16 PARMGEN IF? of the PARMGEN technote attachment. – see new INIT option you can pass on to the PARMGEN invocation.

- For a list of what’s new in 1Q16 IF (UA80256), see OMEGAMON XE shared documentation’s “What’s New”: http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/common/new_parmgen_ptfua80256_aparoa48678.htm

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held May 25, 2016

• 05/25/2016 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: List of customer attendees can be furnished upon request.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: http://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=6b34e611-be6c-4f4c-9c68-185aad6e5493

C. Q&A Details:

• May 25, 2016 Q&A:

Q#1: “I want to create new PARMGEN work datasets and Runtime Environment Datasets for each LPAR for the

new products. How do I ensure that I bring over all of my V5.1 product configuration from the existing set

up?“

• A#1: See 1/20/2016 Q&A Q#4: “In the cloning scenario covered for the CLONTO RTE (modeled from WCONFIG(CLONFROM) for the demo (from Q#3), when I upgrade to the V530s/V730s, do I perform something similar?” You have the option to clone the PARMGEN global JCL library (%GBL_USER_JCL%) and copy its contents to the new dataset so you continue to have an inventory of

the same RTEs. This is ideal in scenarios where this is not an upgrade in place whereby new SMP/E target datasets, new PARMGEN work and product runtime datasets will be used. Especially in cases where product HLQs are versionized, and variables are enabled in the RTE, the PARMGEN global JCL library carries the LPAR RTE profiles and PARMGEN global JCL library are read @ product startup (via CONFIG DD). If the new RTEs will manipulate the resolution values of system symbol overrides and/or user symbol resolution values, it is best to clone the PARMGEN global JCL library so resolution values for the product STCs running while staging the RTE datasets and runtime members for the new versions.

Q#2: “How I can export the (OMCICS) region profiles, without going back to V5.1?”

• A#2: See the xKANSAMU(KCIJPCLN) job referenced in PARMGEN post-configuration on-line tailored README file under “KCI” common component entry. OMEGAMON CICS region profiles are stored in the &rte_vsam_hilev.&rte_name.RKC2TD00 VSAM so the customized data needs to be REPRO’d from the old VSAM to the new RTE’s VSAM when not upgrading the RTE in place (i.e., using new RTE read-only and user datasets for Non-VSAM, VSAM and SEQ RTE datasets). For more information, Q&A 2/17/2016 Q#2: “Are there PARMGEN jobs to REPRO VSAM data from the old datasets to a new RTE?” also posed similar query. Review the previous Q&A for detailed information about KCIJPCLN usage.

ISREDDE2 TDITN.OMEGV530.LPARRTE.WKANSAMU(KCIDFINL)

Command ===> Scroll ===> CSR

001033 Step 9 - Clone or migrate customized data from another RTE.

001034

001035 In general, the "Clone customized data from another RTE" job

001036 (KCIJPCLN) on the "UTILITIES" panel can be used to copy the data

001037 from the original RTE datasets to a new set of RTE datasets (VSAM,

001038 Non-VSAM) regardless if this is an upgrade of a product version

001039 configured in this RTE, and this new RTE is using a new set of

001040 datasets to preserve the "production" RTE datasets at the previous

001041 version, while this new upgrade RTE is in test, or this is simply a

001042 clone of another RTE within the same product version.

001043 ================================================================

001044 | The steps in the KCIJPCLN job follow this naming convention: |

001045 |--------------------------------------------------------------|

001046 | CPDATFpp - if the RTE has customized Non-VSAM data to clone |

001047 | such as profiles, screenspaces, etc. |

001048 | CPEXITpp - if the RTE has sample members to clone |

001049 | such as security exits, etc. |

001050 | CPGLBLpp - if the RTE has customized globals to clone |

001051 | CPMODUpp - if the RTE has customized modules to clone |

001052 | such as security modules, globals, etc. |

001053 | CPNVSMpp - if the RTE has customized Non-VSAM data to clone |

001054 | such as profiles, screenspaces, workspaces, etc. |

001055 | CPSEQUpp - if the RTE has sequential data to clone |

001056 | CPVSAMpp - if the RTE has customized VSAM data to clone |

001057 | such as product situations, SDA status, etc. |

001058 | CPWENUpp - if the RTE has customized Non-VSAM data to clone |

001059 | such as workspaces, etc. |

001060 ================================================================

Q#3: “I have a member RKD2PAR(OMPEMSTS) which I manually coded with the EXCLUDEDB2SSID parameter;

what parm. preserves my updates in PARMGEN?”

• A#3: RKD2PAR(OMPESTMS) DB2SSID/EXCLUDEDB2SSID parameter is controlled by the KD2_DBnn_MONITOR_START profile parameter. This profile parameter controls settings used in 2 runtime members: RKD2PRF(DB2PROF)’s MONITOR_START=Y/N runtime parameter and RKD2PAR(OMPEMSTS) DB2SSID/EXCLUDEDB2SSID=(&dbid) runtime parameter. The PARMGEN profile parameter provides the following comments which illustrate how this is processed by the PARMGEN deployment jobs. A future HKDBvvv PTF will also help supply an updated parameter on-line help text for KD2_DBnn_DB2_MONITOR_START:

ISREDDE2 TDITN.OMEGV530.LPARRTE1.WCONFIG(LPARRTE1)

Command ===> Scroll ===> CSR

003003 KD2_DB BEGIN * Table begin *

003004

003005 ** BEGIN KD2_DB01 - DB2 subsystem ID: SS01 (KD2_DBxx_ROW #1)

003006 ** CURRENCY NOTES:

003007 ** 1. DB2 V9.1 is applicable to OMEGAMON XE for DB2 PE/PM V5.2.0

003008 ** and earlier versions only.

003009 ** 2. DB2 V11 is applicable to OMEGAMON XE for DB2 PE/PM V5.2.0

003010 ** and higher versions.

003011 **

003012 ** Profile Parameter Notes:

003013 ** 1. KD2_DBnn_DB2_VER = 91 is valid for OMXE for DB2 V5.2.0 and

003014 ** earlier versions only.

003015 ** 2. KD2_DBnn_DB2_VER = 11 is valid for OMXE for DB2 V5.2.0+ only.

003016 **

003017 ** A number of these parameters make up the xKD2PRF(DB2PROF):

003018 ** xKD2PRF(DB2PROF) must be available for generating the DB2 runtime

003019 ** members for each KD2_DBnn_DB2_SSID DB2 subsystem ID. DB2PROF

003020 ** (processed by the $PARSE*/CRTDB2* jobs) is populated with these

003021 ** parameters pointing to the value you supply for the LPAR RTE

003022 ** profile parameter per DB2 subsystem ID monitored:

003023 ** - DB2ID=%KD2_DBnn_DB2_SSID%

003024 ** - DB2_VERSION=%KD2_DBnn_DB2_VER%

003025 ** - PROFID=%KD2_DBnn_DB2_PROFID%

003026 ** - MONITOR_STARTUP=%KD2_DBnn_DB2_MONITOR_START%

003027 ** - DB2_SYSID=%KD2_CLASSIC_MVS_SYSID% * If KD2_OMPE_CHECKSYS = "N" *or*

003028 ** DB2_SYSID=%KD2_DBnn_DB2_SYSNAME% * If KD2_OMPE_CHECKSYS = "Y"

003029 ** - PECLIENT_PORT=%KD2_DBnn_DB2_PORT_NUM%

003030 ** - DSG=%KD2_DBnn_DB2_DS_GROUP%

003031 ** - PWH_ACTIVE=%KD2_DBnn_PWH_D2PWPWHA%

003032 ** - PWH_STC=%KD2_DBnn_PWH_D2PWASNM%

003033 ** - DB2_LOADLIB=%KD2_DBnn_DB2_LOADLIB%

003034 ** - DB2_RUNLIB=%KD2_DBnn_DB2_RUNLIB%

003035 ** - DB2_DSNTIAD=%KD2_DBnn_DB2_DSNTIAD%

003036 **

003037 ** KD2_DBnn_DB2_MONITOR_START updates the xKD2PAR(OMPEMSTS) runtime

003038 ** member as file-tailored by the xKD2PRF(CRTDB2*) submitted job from

003039 ** PARMGEN $PARSE*-related "Create runtime members" jobs.

003040 ** - DB2SSID=(%KD2_DBnn_DB2_SSID%) * if MONITOR_STARTUP = "Y"

003041 ** - EXCLUDEDB2SSID=(%KD2_DBnn_DB2_SSID%) * if MONITOR_STARTUP = "N"

003042 **

003043 KD2_DB01_ROW 01

003044 KD2_DB01_DB2_DESCRIPTION "SS01 DB2 Subsystem"

003045 KD2_DB01_DB2_SSID SS01 * Replace with DB2ID; no symbols*

003046 KD2_DB01_DB2_VER "" * (Required) 91,10,11 *

003047 KD2_DB01_DB2_PROFID P001 * Not eligible for symbolics *

003048 KD2_DB01_DB2_MONITOR_START Y * For xKD2PRF(DB2PROF) *

Q#4: “We noticed multiple messages in our SYSLOG for OMXEMQ on our development LPAR stating insufficient

access authority requiring Control access. What setting controls this?”

• A#4: SYMPTOM: SYSLOG has multiple messages for OMXEMQ OMEGAMON XE for Messaging – MQ Monitoring Agent STC stating insufficient access authority requiring RACF control access. Specific RACF messages: “ICH408I USER(OMXEMQ) GROUP(STC) NAME(OMXEMQ) QMGR.QUEUE.IBM CL(MQADMIN) INSUFFICIENT ACCESS AUTHORITY FROM QMGR.QUEUE.I* (G) ACCESS INTEN(CONTROL) ACCESS ALLOWED(NONE)” (where OMXEMQ = OMEGAMON XE for Messaging – MQ Monitoring Agent STC name in this example). CAUSE: These messages are caused by the KMQ monitoring agent attempt to do RESET QSTATS command which requires CONTROL level access to all the queues. This command is issued when STATISTICS(YES) is specified in SET QUEUE statement in the OMEGAMON XE for Messaging – MQ Monitoring (KMQ) Agent’s RKANCMDU(KMQSTART) or RKANCMDU(KMQUSER) startup command runtime members. RESOLUTION:

❖ Update OMEGAMON XE for Messaging V7.3.0 Knowledge Center documentation. Note that the IBM Knowledge Center’s OMEGAMON XE for Messaging documentation’s topic "Granting authorities to WebSphere MQ Monitoring agent and WebSphere MQ Configuration agent" was incomplete and should explicitly state that access is required to allow RESET QSTATS when STATISTICS(YES) is specified in RKANCMDU(KMQSTART) runtime member. This has been updated and will be available in next documentation refresh.

❖ Either grant control access to KMQ Agent task or modify RKANCMDU(KMQSTART) to set to STATISTICS(NO), depending on what customer needs. The SET QUEUE STATISTICS(%KMQ_QUEUE_STATISTICS%) setting is controlled by the PARMGEN KMQ profile parameter “KMQ_QUEUE_STATISTICS” in WCONFIG(&rte_name) LPAR RTE profile parameter. The default setting is KMQ_QUEUE_STATISTICS NO.

❖ Overrides: Regarding KMQUSER/KMQSTART order of precedence as far as usage by the running KMQ Agent STC startup. The SET QUEUE statement in KMQSTART is the default level and PARMGEN $PARSE*-related job (re)creates the SET QUEUE STATISTICS(%KMQ_QUEUE_STATISTICS%) parameter in WKANCMDU(KMQSTART) by default. When customer is ready to deploy the changes, he submits the KCIJPW2R job in WKANSAMU to copy the WKANCMDU(KMQSTART) to the product-execution copy in RKANCMDU(KMQSTART), which is the runtime member read by the running KMQ Agent STC. Some sites choose to also enable the SET QUEUE statements in the user-controlled RKANCMDU(KMQUSER) runtime member. Any specific SET QUEUE statements in KMQUSER with a specific MGRNAME keyword will override the SET QUEUE statement with GROUP keyword. So the STATISTICS(YES) in KMQUSER are the ones that are used if customer overrides the statements in the WCONFIG(KMQ$CUSR) imbed, which is imbedded by the PARMGEN $PARSE* job when rebuilding the WKANCMDU(KMQUSER) runtime member.

❖ See also related 1/20/2016 Q&A Q#6: "How do I update KMQUSER member (for OMEGAMON XE for Messaging – MQ Monitor Agent)?"

Q#5: “What happens when the Java version changes (for the SDA TEMS processing)?”

• A#5: If WCONFIG($GBL$USR)’s GBL_HFS_JAVA_DIR1 value needs to change because the Java bin path has changed in your USS environment, then WCONFIG($PARSESM) job to recreate the PARMGEN USS jobs (KCIJPUSP and KCIJPUSS). These jobs (re)create the runtime members in RKANDATV dataset and those members contain the USS commands and parameters. Specific to GBL_HFS_JAVA_DIR1 parameter value, its value is used to populate the RKANDATV(KDSDPROF) file’s TEMS_JAVA_BINPATH=%GBL_HFS_JAVA_DIR1%/bin parameter and KCIJPUSS ensures that this member is copied (oput) to the SDA USS directory.

• Tip: The SDA TEMS infrastructure code just needs a working Java regardless of version. So each LPAR has multiple Java home directories for many versions, select one that you know will always exist. You have the option to specify the same value for all your 50 LPARs if the Java bin path is the same across the 50 LPARs, or you have the option to make it RTE-specific. It's part of the reason why WCONFIG($GBL$USR) is available in each RTE-specific WCONFIG -- that way, customers that have different system values for GBL_* parms. can still choose to make the value unique per LPAR. Better yet, for RTEs enabled for variable, it is ideal to set-up GBL_HFS_JAVA_DIR1 as a user symbol instead of a static path value. For example, set up the parameter in WCONFIG($GBL$USR) as a user symbol as shown in the example below: EDIT TDITN.OMEGV530.LPARRTE1.WCONFIG($GBL$USR) Command ===> Scroll ===> CSR 000468 **** ----------------------------------------------------------------- 000469 **** Java home directory name: 000470 **** Note: This is required if you are enabling the Self-describing 000471 **** Agent (SDA) functionality in the z/OS TEMS and Agents: 000472 **** "GBL_HFS_JAVA_DIRn" value becomes part of the 000473 **** TEMS_JAVA_BINPATH parameter in the RKANDATV(KDSDPROF) member 000474 **** that is created by the WKANSAMU(KCIJPUSP) USS preparation 000475 **** job. "/bin" is added to the "GBL_HFS_JAVA_DIRn" Java home 000476 **** directory value programmatically. 000477 **** 000478 **** Related PARMGEN CONFIG profile parameters: 000479 **** - GBL_DSN_SYS1_SBPXEXEC (typically in WCONFIG($GBL$USR)) 000480 **** - RTE_USS_RTEDIR 000481 **** - RTE_USS_MKDIR_MODE 000482 **** - KDS_KMS_SDA 000483 **** - KDS_KMS_SDA_NO_GRANULAR (applicable to ITM6.3.0+ only) 000484 **** - KDS_TEMA_SDA 000485 **** - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA) 000486 **** ----------------------------------------------------------------- 000487 *GBL_HFS_JAVA_DIR1 "/usr/lpp/java/J6.0" * IBM default 000488 GBL_HFS_JAVA_DIR1 "&GBL_HFS_JAVA_DIR1." * @CD Tip: Use user symbol

For example, I am using a user symbol called "&GBL_HFS_JAVA_DIR1." Then in your &GBL_USR_JCL(&rte_name) variables profile for this RTE, add the new user symbol pointing to what the symbol will resolve to during: 1. PARMGEN KCIJ%USP job - KCIPARSE step reads CONFIG DD to know what the symbol resolves to when creating the RKANDATV USS members that contain the commands (done via KCIJVUSP job which submits KCIJPUSP job) 2. PARMGEN KCIJPUSS job - similar processing as above via KCIJVUSS job 3. %KDS_TEMS_STC% TEMS started task startup - KCIPARSE symbolic substitution step reads what the user symbol resolves to

So in our sample &GBL_USER_JCL(LPARRTE1), GBL_HFS_JAVA_DIR1 is already one of the best-practice predefined user symbols so I just commented out the default and enabled my copy on line #205: EDIT TDITNT.COMMON.PARMGEN.JCL(LPARRTE1) Command ===> Scroll ===> CSR 000203 ** ------------------------------------------------ 000204 *GBL_HFS_JAVA_DIR1 "/usr/lpp/java/J6.0" *(REQ:for SDA-default if used) 000205 GBL_HFS_JAVA_DIR1 "/Java/J8.0" *Your WCONFIG($GBL$USR) Then for initial set-up to use the new values, you would want to rerun $PARSESV job to ensure that xKANPARU and RKANDATV runtime members are updated. And also rerun KCIJPW2R to update RKANPARU. Setting up this way enables you to simply rerun KCIJPUSP/KCIJPSS jobs next time the value has to change, then simply recycle the TEMS started task.

Q#6: “Should CICS be started before OMEGAMON CICS?“

• A#6: Typically, the recommendation is start the OMEGAMON CICS (OCCI) Classic 3270 STC (%KC2_CCnn_CLASSIC_STC%) before CICS but if you plan to start CICS, IBM recommends that customers should use the KOCOME00 INITPARM RETRY parameter, which will retry the connection to the OCCI at the specified interval for the specified number of times. For more information, refer to the PARMGEN KC5 post-configuration on-line README step 1b as shown below. This info. is also available in the OMEGAMON XE for CICS Knowledge Center documentation. http://www.ibm.com/support/knowledgecenter/SSLSDR_5.3.0/com.ibm.omegamon_cics.doc_5.3.0/planning/planning_jcl_updates.htm?lang=en

VIEW TDITN.OMEGV530.LPARRTE.WKANSAMU(KC5DFINL)

Command ===>

****** ***************************** Top of Data ****

+BEGIN ---------------------------------------------------------------+

OMEGAMON XE for CICS Version 530

COMPLETE THE CONFIGURATION

+BEGIN ---------------------------------------------------------------+

COMPONENTS:

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

NAME COMPONENT CODE

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

1. OMEGAMON CICS 3270 (Classic/Menu system and CUA) KOC/KC2

2. OMEGAMON XE for CICS on z/OS Agent KC5/KCP

Note:

If you have not done so already, please review the common "Complete the

Configuration" on-line READMEs for the following common components,

prior to reviewing the post-configuration steps specific to this Agent:

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

Kpp README: post-configuration instructions

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

KCI (Required) Common to all components configured in this RTE

KAG (Required) Common Tivoli Enterprise Monitoring Agent (TEMA)

KDS (Conditional) Tivoli Enterprise Monitoring Server

KOB (Conditional) OMEGAMON Enhanced 3270 User Interface

For Step 1: TIP: Time-to-value improvement in this new version

Step 1 - Update CICS regions.

Starting in OMEGAMON XE for CICS V5.3.0, you can install OMEGAMON

with no changes to the JCL of the CICS regions that you monitor.

If you choose to implement the updates described below, during

initialization processing, OMEGAMON will dynamically allocate the

following DDnames and applicable load libraries:

//RKANMOD DD DSN=TDITN.OMEGV530.LPARBASE.RKANMOD

//RKCPXMnn DD DUMMY

//RKC2XMnn DD DUMMY

//KOCGLBcc DD DUMMY

The default for "nn" and "cc" is "00".

1a) Review the sample member

TDITNT.DEV.ITM63053.TKANSAM(KOCCSD)

(or TDITN.OMEGV530.LPARBASE.RKANSAM(KOCCSD)

if this RTE is sharing with read-only base libraries) which

includes the following updates introduced with this release:

- an updated program definition for KOCOME00.

- an updated transaction definition for OMEG.

- a new library definition for RKANMODR.

Update the KOCCSD sample member library definition for RKANMODR,

to allocate the TDITN.OMEGV530.LPARBASE.RKANMODR

load library.

For your convenience, a sample

TDITN.OMEGV530.LPARBASE.RKANSAM(KOCCSD) is provided

below, tailored to this LPARRTE RTE:

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

EDIT TDITN.OMEGV530.LPARBASE.RKANSAM(KOCCSD)

Command ===>

********************************************************

*

* OMEGAMON II for CICS on z/OS V5.3.0 CSD definitions

*

* Note: The group that contains the OMEGAMON XE for CICS

* definitions must be in a group list that is

* available during CICS startup

*

* Please make any necessary changes to this member

* before using it as input to

* TDITN.OMEGV530.LPARBASE.RKANSAM(KOCCSDJ)

********************************************************

*

DELETE PROGRAM(KOCOME00) GROUP(OMEGAMON)

DELETE TRANSACTION(OMEG) GROUP(OMEGAMON)

DELETE LIBRARY(RKANMODR) GROUP(OMEGAMON)

*

DEFINE PROGRAM(KOCOME00) GROUP(OMEGAMON)

CONCURRENCY(THREADSAFE) EXECKEY(CICS) DATALOC(ANY)

DEFINE TRANSACTION(OMEG) PROGRAM(KOCOME00) GROUP(OMEGAMON)

TASKDATAKEY(CICS) TASKDATALOC(ANY)

*

DEFINE LIBRARY(RKANMODR) GROUP(OMEGAMON) RANKING(20)

CRITICAL(NO)

DSNAME01(TDITN.OMEGV530.LPARBASE.RKANMODR)

*

*

ADD GR(OMEGAMON) LIST(XE530)

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

1b) Optionally, modify the CICS region INITPARM data to provide the

new definitions as part of the KOCOME00 parameter. For first

time users, the default settings are recommended.

For example:

INITPARM=(DFHDBCON='CC,IC1C',

KOCOME00='RETRY(tt,cc),KC2_XMIT=nn,KCP_XMIT=nn,KC2_GLOBAL=cc')

where:

RETRY(tt,cc) specifies the behavior of OMEGAMON when the common

interface is not available. OMEGAMON will attempt to connect

to the common interface every tt seconds, for a maximum of

cc times. Specifying RETRY(tt) means that the retries occur on

the specified interval, with no limit.

KC2_XMIT=nn (for example, KC2_XMIT=00)

specifies the common interface region that this CICS will

establish a monitoring session with. The value of nn must be

between 00 and 15. The default is 00. The value should match the

value given for KC2_CCnn_CLASSIC_XMIT in your PARMGEN

configuration.

KCP_XMIT=nn specifies which OMEGAMON XE for CICS on z/OS Agent

this CICS will establish a monitoring session with. The value

of nn must be between 00 and 15. The default is 00. The value

should match the value given for RKCPXMnn DD in the

IBMTSS1C5 Agent started task.

KC2_GLOBAL=cc specifies a global data area that is used to

specify the monitoring options for your CICS region or regions.

The default is 00. The value should match that given for

the global member if the default value is not used.

The values specified on the INITPARM can be dynamically changed

while CICS is running. Review the configuration sections of the

product documentation for further information.

1c) If you have existing CICS JCL, you can remove the OMEGAMON

libraries from the DFHRPL concatenation and remove the RKANMOD

DD statement as well as any RKCPXMnn, RKC2XM and KC2GLBxx DD statements.

Q#7: “Where do I find information for compatibility for OMEGAMON with zOS 2.2? We are currently running zOS

1.13?“

• A#7: See “OMEGAMON XE z/OS 2.2 product currency support PTFs” common technote URL: http://www-01.ibm.com/support/docview.wss?uid=swg21902875. See also related 10/30/2015 Q&A Q#1:

Question about “OMEGAMON STC dumps when trying to use RKANCMDU” with KCIRPLB1 – E Running KCIPARSE” message. and 11/18/2015 Q&A Q#1a: “Are the z/OS 2.2 PARMGEN toleration PTFs (UA76016 and later) backward compatible?

Q#8: “Are there any issues if I at first only upgrade the Hub TEMS?“

• A#8: If the Self Describing Agent (SDA) feature is not enabled at the TEMS, TEPS and Agents, it is required to upgrade the Hub TEMS environment first. In addition, the TEMS application support files must also be installed. For future upgrades, once SDA is enabled all around (i.e., z/OS H/RTEMS and TEPS have SDA enabled), the next upgrade allows you to start with the Remote TEMS RTEs if you choose. If we upgrade the Remote TEMS RTEs first before the Hub TEMS RTE, until the Agents on the Hub TEMS RTE gets upgraded to the future versions, (i.e., SMP/E TK* are @ the upgraded FMIDs, but Hub TEMS and Remote TEMS RKANDATV datasets are still @ previous versions as customer has not yet reloaded the RTE with the upgraded load modules and Agent catalog, attribute and other ODI files via KCIJPLOD job), then a typical FAQ is will the Hub TEMS have issues with reporting data for Agents from the Remote TEMS RTEs which are now upgraded. The answer is No. If this upgraded V540 Agent connects to an RTEMS, the RTEMS SDA process that is initiated by this V540 Agent will first ensure that the Hub TEMS SDA has the V540 product support installed. If the Hub TEMS is not at V540 level, the RTEMS SDA will initiate an SDA update to occur on the Hub TEMS. The Hub TEMS will retrieve the V540 product support from the Agent connected to the RTEMS and use these files to update its Hub TEMS to V540 product support. Once the Hub TEMS has been updated to V540, then the RTEMS will repeat the same process. So in all cases, SDA should always ensure you end up with the Hub TEMS product support being updated before anything else. For the Agents, Agent versioning should kick in at the TEPS and the TOM and handle the new SQL accordingly. If you have mixed-version Agents (V530, V540), those Agents should get the version-specific SQL query. Only the upgraded Agents would get an SQL asking for any new columns. And then only if the workspace was updated to request the new columns. TEP workspaces must be versioned manually. The TOM is automatic.

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held April 27, 2016

• 04/27/2016 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: Please let me know if I miss anyone from the attendance list. Thanks.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=6b93f9ee-5a98-4da1-af05-e326ade40504

C. Q&A Details:

• April 27, 2016 Q&A:

Q#1: “What is loaded in RKANPARU during PARMGEN config. time?“

• A#1: $PARSE Create runtime members job builds the product runtime members in the PARMGEN work datasets (WKANPARU) for file-tailored configuration members, customized to the configuration values specified by customer during WCONFIG(&rte_name)/WCONFIG($GBL$USR) user profiles. KCIJPW2R job IEBCOPY’s the configuration runtime members from WKANPARU to the RKANPARU user dataset. RKANPARU is one of the product execution datasets read @ product startup (concatenated in the RKANPAR DD of each product started task). PARMGEN also processes this dataset via the KCIJPLOD job, which implemented the KppGLB* global processing step for products that support globals (KC2GLB for OMEGAMON XE for CICS, and KIPGLB* for OMEGAMON XE for IMS starting @ V5.3.0). See GBL_DSN_GLOBAL_SOURCE_LIB profile parameter in WCONFIG($GBL*) for more information. Additional IBM Knowledge Center references:

• http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/common/overview_new_630fp2_config_0915_sept.htm

• http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/commonparmref/gbl_dsn_global_source_lib.htm

Q#2: “When do I use LOADDATV?”

• A#2: See KCIJ@ODI job description in the WCONFIG($JOBINDX) job index. You can access the $JOBINDX via UTILITIES (U/UTIL option from the PARMGEN Workflow main menu). This job is ideal for quickly loading all your RTE’s RTE-specific RKANDATV dataset for all or a subset of your RTEs that are SMP/E-sharing (RTE_TYPE=SHARING, RTE_SHARE=SMP). SMP/E-sharing RTEs are set-up by default to concatenate SMP/E target datasets directly in the different DDNAMEs generated product started tasks. In the case of the RKANDATV DD, the products that use this DDNAME use the RKANDATV dataset for both RO/RW dynamically written to @ product startup so a concatenation of TKANDATV target is not currently supported. RTEs sharing directly with target datasets currently allocate an RTE-specific RKANDATV dataset. When products deliver maintenance that update the TKANDATV elements for the Object Definition Information (ODI) elements such as the attribute (KppATR), catalog (KppCAT), SDA jars, etc., the product PTF HOLDDATA contains a ACTION to reload the RTEs via the PARMGEN KCIJPLOD job per RTE. For ease-of-use, PARMGEN also provides the LOADDATV or LOADALL cross-RTE function jobs. See write-up about UTILITIES in: https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/zcommonconfig/reference_utils_list_rtes.htm

Q#3: “How does the Agent in the local RTE and the Agents in the Remote RTEs know where the Hub TEMS is?“

• A#3: See this write-up that will be included in the next OMEGAMON XE shared publications refresh:

How to: Connect Agents on local RTE and Agents on remote RTEs to the HUB TEMS

You can configure agents on different RTEs to report to the same HUB TEMS.

Decide the primary TEMS, regardless if it is a Hub or a Remote TMES, that the agents connect to. If you enable the backup TEMS feature by changing the agent's Kpp_TEMS_BKUP1_* parameters, you must also decide the backup TEMS that the agents connect to.

Refer to the following configuration scenario among 3 RTEs in different LPARs to understand how to connect agents on different RTEs to the HUB TEMS. The LPARs are:

• LPAR 1: RTE_NAME = SYSA (&sysname = SYSA; &sysplex = TESTPLEX; &sysiphostname = SYSA) • LPAR 2: RTE_NAME = SYSB (&sysname = SYSB; &sysplex = TESTPLEX; &sysiphostname = SYSB) • LPAR 3: RTE_NAME = SYSC (&sysname = SYSC; &sysplex = TESTPLEX; &sysiphostname = SYSC)

The components and configurations on each RTE are different:

• SYSA RTE configures a Hub TEMS (KDS), OMEGAMON enhanced 3270 User Interface (KOB), OMEGAMON XE for DB2 (KD5), OMEGAMON XE for IMS (KI5), and OMEGAMON XE for Mainframe Networks (KN3). KD5, KI5, and KN3 agents report directly to the local z/OS Hub TEMS via IPPIPE and SNA protocols.

Take the default values in PARMGEN for most of the following parameters in the LPAR RTE profile in WCONFIG. You can define most of these parameter values in "1. KCIJPCFG Set up/Refresh PARMGEN

work environment" step of the quick configuration mode. The backup TEMS feature is not enabled on this RTE.

1. Specify common RTE parameters values during KCIJPCFG setup depending on preferred RTE scenario.

RTE_TEMS_CONFIGURED_FLAG y RTE_TEMS_NAME_NODEID "SYSA:CMS"

2. Specify typical z/OS TEMS common parameters. ▪ Specify the TEMS type on this RTE as HUB.

KDS_TEMS_TYPE HUB

▪ Specify the communication protocols in priority sequence to be used by the local TEMS to communicate with other ITM components such as another TEMS, Agents, TEPS, etc. Valid values are "IPPIPE", "IP", "SNA", "IP6PIPE", "IP6", "IPSPIPE", and "IP6SPIPE".

KDS_TEMS_COMM_PROTOCOL1 IPPIPE KDS_TEMS_COMM_PROTOCOL2 SNA

▪ Specify the protocol port number for the HUB TEMS, which must be used across the enterprise. Remote TEMS and Agents connecting to the Hub TEMS must use the same port numbers.

KDS_TEMS_TCP_PIPE_PORT_NUM 1918 * IP.PIPE

▪ Specify the TEMS VTAM information. You can take default values for the KDS_TEMS_VTAM_APPL_GLB_BROKER and KDS_TEMS_VTAM_APPL_LLB_BROKER parameters, or use different values. The value CTDHDSLB is used across this scenario.

KDS_TEMS_VTAM_LU62_DLOGMOD CANCTDCS KDS_TEMS_VTAM_LU62_MODETAB KDSMTAB1 KDS_TEMS_VTAM_NETID USCACO01 KDS_TEMS_VTAM_APPL_GLB_BROKER CTDHDSLB KDS_TEMS_VTAM_APPL_LLB_BROKER CTDHDSLB KDS_TEMS_VTAM_APPL_KDS_VTAMID CTDDSDS KDS_TEMS_VTAM_APPL_OPERATOR CTDDSOR KDS_TEMS_VTAM_APPL_CUA_OPER CTDDSOP KDS_TEMS_VTAM_APPL_KDSINVPO CTDDSVP KDS_TEMS_VTAM_APPL_MQ CTDDSMQ

3. Specify typical common agent parameters. Only OMEGAMON XE for DB2 (KD5) parameters are listed. Other agents have similar parameters.

▪ Specify the communication protocols in priority sequence to be used to communicate with other ITM components such as the TEMS, agents, TEPS, etc. Valid values are "IPPIPE", "IP", "SNA", "IP6PIPE", "IP6", "IPSPIPE", and "IP6SPIPE".

KD5_AGT_COMM_PROTOCOL1 IPPIPE

KD5_AGT_COMM_PROTOCOL2 SNA

▪ Specify protocol port numbers for agent to connect to TEMS.

KD5_TEMS_TCP_PIPE_PORT_NUM 1918 * IP.PIPE

▪ Specify values that describe the primary TEMS the agents connect to.

KD5_TEMS_LOCAL_CONNECT_FLAG Y KD5_TEMS_NAME_NODEID "SYSA:CMS"

▪ Specify primary TEMS TCP/IP information and agent local TCP/IP information.

KD5_TEMS_TCP_HOST "SYSA" KD5_AGT_TCP_HOST "SYSA"

▪ Specify primary TEMS VTAM information and agent's local VTAM and logon information.

KD5_TEMS_VTAM_LU62_DLOGMOD CANCTDCS KD5_TEMS_VTAM_LU62_MODETAB KDSMTAB1 KD5_TEMS_VTAM_NETID USCACO01 KD5_TEMS_VTAM_APPL_LLB_BROKER CTDHDSLB KD5_AGT_VTAM_NODE CTDD5N

▪ Specify agent's APPLIDs.

KD5_AGT_VTAM_APPL_OPERATOR CTDD5OR KD5_AGT_VTAM_APPL_KD5INVPO CTDD5VP KD5_AGT_VTAM_APPL_NCS CTDD5NC KD5_AGT_VTAM_APPL_AA CTDD5AA

Based on the customizations, the xKANPARU(KppENV) runtime members reflect the KDE_TRANSPORT parameter and CT_CMSLIST parameter based on the specified values, in the preferred order of the protocols, which is IPPIPE first and then try SNA if connection by IP wire is not available.

• SYSB RTE configures a local z/OS Remote TEMS (KDS) reporting to the z/OS Hub on SYSA, OMEGAMON XE for DB2 (KD5), OMEGAMON XE for IMS (KI5), and OMEGAMON XE for Mainframe Networks (KN3). No OMEGAMON enhanced 3270 User Interface (KOB) is configured. KD5, KI5, and KN3 agents report to the local z/OS Remote TEMS via IPPIPE and SNA protocols, not directly to the Hub to reduce the burden on the SYSA Hub TEMS.

Take the default values in PARMGEN for most of the following parameters in the LPAR RTE profile in WCONFIG. You can define most of these parameter values in "1. KCIJPCFG Set up/Refresh PARMGEN work environment" step of the quick configuration mode.

1. Specify common RTE parameters values during KCIJPCFG set-up depending on preferred RTE scenario.

RTE_TEMS_CONFIGURED_FLAG y

RTE_TEMS_NAME_NODEID "SYSB:CMS"

2. Specify typical z/OS TEMS common parameters. ▪ Specify the TEMS type on this RTE as REMOTE.

KDS_TEMS_TYPE REMOTE

▪ Specify the communication protocols in priority sequence to be used by the local TEMS to communicate with other ITM components such as another TEMS, agents, TEPS, etc. Valid values are "IPPIPE", "IP", "SNA", "IP6PIPE", "IP6", "IPSPIPE", and "IP6SPIPE".

KDS_TEMS_COMM_PROTOCOL1 IPPIPE KDS_TEMS_COMM_PROTOCOL2 SNA

▪ Specify the protocol port number for the remote TEMS same as the port number that is used by the Hub TEMS.

KDS_TEMS_TCP_PIPE_PORT_NUM 1918 * IP.PIPE

▪ Specify the TEMS VTAM information.

KDS_TEMS_VTAM_LU62_DLOGMOD CANCTDCS KDS_TEMS_VTAM_LU62_MODETAB KDSMTAB1 KDS_TEMS_VTAM_NETID USCACO01 KDS_TEMS_VTAM_APPL_GLB_BROKER CTDHSDLB KDS_TEMS_VTAM_APPL_LLB_BROKER CTDDSLB KDS_TEMS_VTAM_APPL_KDS_VTAMID CTDDSDS KDS_TEMS_VTAM_APPL_OPERATOR CTDDSOR KDS_TEMS_VTAM_APPL_CUA_OPER CTDDSOP KDS_TEMS_VTAM_APPL_KDSINVPO CTDDSVP KDS_TEMS_VTAM_APPL_MQ CTDDSMQ

▪ Specify its Hub TEMS values. These parameters are key settings for the Remote TEMS that tell PARMGEN where the HUB TEMS is and how to set up the RTEMS KDSENV and KDCSSITE runtime members. In this scenario, you must specify the values of the Hub TEMS on RTE SYSA.

KDS_HUB_TEMS_NAME_NODEID "SYSA:CMS" * Hub RTE_TEMS_NAME_NODEID KDS_HUB_TCP_HOST "SYSA" * Hub KDS_TEMS_TCP_HOST KDS_HUB_TCP_PIPE_PORT_NUM "1918" * Hub KDS_TEMS_TCP_PIPE_PORT_NUM KDS_HUB_VTAM_APPL_GLB_BROKER "CTDHDSLB" * Hub KDS_TEMS_VTAM_APPL_GLB_BROKER KDS_HUB_VTAM_NETID "USCACO01" * Hub KDS_TEMS_VTAM_NETID

3. Specify typical common agent parameters. Only OMEGAMON XE for DB2 (KD5) parameters are listed. Other agents have similar parameters.

▪ Specify the communication protocols in priority sequence to be used to communicate with other ITM components such as the TEMS, agents, TEPS, etc. Valid values are "IPPIPE", "IP", "SNA", "IP6PIPE", "IP6", "IPSPIPE", and "IP6SPIPE".

KD5_AGT_COMM_PROTOCOL1 IPPIPE KD5_AGT_COMM_PROTOCOL2 SNA

▪ Specify protocol port numbers for agent to connect to TEMS.

KD5_TEMS_TCP_PIPE_PORT_NUM 1918 * IP.PIPE

▪ Specify values that describe the primary TEMS the agents connect to.

KD5_TEMS_LOCAL_CONNECT_FLAG Y KD5_TEMS_NAME_NODEID "SYSB:CMS"

▪ Specify primary TEMS TCP/IP information and agent local TCP/IP information.

KD5_TEMS_TCP_HOST "SYSB" KD5_AGT_TCP_HOST "SYSB"

▪ Specify primary TEMS VTAM information and agent's local VTAM and logon information.

KD5_TEMS_VTAM_LU62_DLOGMOD CANCTDCS KD5_TEMS_VTAM_LU62_MODETAB KDSMTAB1 KD5_TEMS_VTAM_NETID USCACO01 KD5_TEMS_VTAM_APPL_LLB_BROKER CTDDSLB KD5_AGT_VTAM_NODE CTDD5N

▪ Specify agent's APPLIDs.

KD5_AGT_VTAM_APPL_OPERATOR CTDD5OR KD5_AGT_VTAM_APPL_KD5INVPO CTDD5VP KD5_AGT_VTAM_APPL_NCS CTDD5NC KD5_AGT_VTAM_APPL_AA CTDD5AA

4. You can enable the backup TEMS feature for the agents to report to the z/OS Hub TEMS on RTE SYSA in case the z/OS RTEMS local on RTE SYSB gets an ABEND. In this scenario, uncomment out the following parameters and specify the values of the Hub TEMS, which become the second entries in CT_CMSLIST for RKANPARU(KD5ENV).

KD5_TEMS_BKUP1_NAME_NODEID "SYSA:CMS" KD5_TEMS_BKUP1_TCP_HOST "SYSA" KD5_TEMS_BKUP1_VTAM_LU62_DLOGMOD CANCTDCS KD5_TEMS_BKUP1_VTAM_APPL_LLB_BKR CTDHDSLB KD5_TEMS_BKUP1_VTAM_NETID USCACO01

Based on the customizations, the xKANPARU(KppENV) runtime members reflect the KDE_TRANSPORT parameter and CT_CMSLIST parameter based on the specified values, in the preferred order of the

protocols, which is IPPIPE first and then try SNA if connection by IP wire is not available. The KD5 agent is configured to report to a backup TEMS, which in this scenario is the Hub TEMS on SYSA, if the local RTEMS on SYSB is not running.

• SYSC RTE configures OMEGAMON XE for DB2 (KD5), OMEGAMON XE for IMS (KI5), and OMEGAMON XE for Mainframe Networks (KN3). No TEMS (KDS) or OMEGAMON enhanced 3270 User Interface (KOB) is configured. KD5, KI5, and KN3 Agents reports to z/OS Hub TEMS configured in the other LPAR (RTE_NAME = SYSA) via IPPIPE and SNA protocols.

Take the default values in PARMGEN for most of the following parameters in the LPAR RTE profile in WCONFIG. You can enable the backup TEMS feature on this RTE to have the agents report to the HUB TEMS on SYSA or the RTEMS on SYSB. However, in this scenario the backup TEMS feature is not enabled.

1. Specify common RTE parameters values during KCIJPCFG set-up depending on preferred RTE scenario. In this scenario, no TEMS is configured in the RTE.

RTE_TEMS_CONFIGURED_FLAG N RTE_TEMS_NAME_NODEID ""

When RTE_TEMS_CONFIGURED_FLAG=N, PARMGEN ignores the KDS_* parameters in the profile.

2. Specify typical common agent parameters. Only OMEGAMON XE for DB2 (KD5) parameters are listed. Other agents have similar parameters.

▪ Specify the communication protocols in priority sequence to be used to communicate with other ITM components such as the TEMS, agents, TEPS, etc. Valid values are "IPPIPE", "IP", "SNA", "IP6PIPE", "IP6", "IPSPIPE", and "IP6SPIPE".

KD5_AGT_COMM_PROTOCOL1 IPPIPE KD5_AGT_COMM_PROTOCOL2 SNA

▪ Specify protocol port numbers for agent to connect to TEMS.

KD5_TEMS_TCP_PIPE_PORT_NUM 1918 * IP.PIPE

▪ Specify values that describe the primary TEMS the agents connect to. If the primary TEMS that this agent connects to is configured on another RTE, or running on a non-z/OS platform, specify 'N' to the KD5_TEMS_LOCAL_CONNECT_FLAG parameter, then customize the KD5_TEMS_* parameters accordingly to point to the non-local primary TEMS.

KD5_TEMS_LOCAL_CONNECT_FLAG N KD5_TEMS_NAME_NODEID "SYSA:CMS"

▪ Specify primary TEMS TCP/IP information and agent local TCP/IP information.

KD5_TEMS_TCP_HOST "SYSA" KD5_AGT_TCP_HOST "SYSC"

▪ Specify primary TEMS VTAM information and agent's local VTAM and logon information.

KD5_TEMS_VTAM_LU62_DLOGMOD CANCTDCS KD5_TEMS_VTAM_LU62_MODETAB KDSMTAB1 KD5_TEMS_VTAM_NETID USCACO01 KD5_TEMS_VTAM_APPL_LLB_BROKER CTDHDSLB KD5_AGT_VTAM_NODE CTDD5N

▪ Specify agent's APPLIDs.

KD5_AGT_VTAM_APPL_OPERATOR CTDD5OR KD5_AGT_VTAM_APPL_KD5INVPO CTDD5VP KD5_AGT_VTAM_APPL_NCS CTDD5NC KD5_AGT_VTAM_APPL_AA CTDD5AA

Based on the customizations, the xKANPARU(KppENV) runtime members reflect the KDE_TRANSPORT parameter and CT_CMSLIST parameter based on the specified values, in the preferred order of the protocols, which is IPPIPE first and then try SNA if connection by IP wire is not available.

Q#4: “Is there a separate line item in the selection list for OMEGAMON Monitoring for JVM or is it configured with OMEGAMON XE on z/OS?“

• A#4: OMEGAMON Monitoring for JVM Agent (KJJ/KJT) is a feature of the OMEGAMON XE on z/OS product. SMP/E-wise, it is shipped as a standalone FMID HKJJ530 that requires only the common infrastructure FMIDs (HKDS630 TEMS FMID, HKLV630 TMS:Engine FMID, and HKCI310 PARMGEN FMID, HKOB730 OMEGAMON enhanced 3270UI/OMEGAMON Subsystem FMID). Configuration-wise, it can be configured as a typical standalone Agent running in its own Address Space (IBMJJ, IBMJT started tasks by default):

• PARMGEN Include (Configure) Installed Product(s) In This RTE panel displaying the KJJ component when PARMGEN detects that the &gbl_target_hilev.TK* SMP/E targets have the HKJJ530 FMID installed:

• • OMEGAMON Monitoring for JVM IBM Knowledge Center documentation:

http://www.ibm.com/support/knowledgecenter/SS2JNN_5.3.0/com.ibm.omegamon_xezos.doc_5.3.0/jvm/jvm_intro.htm

• To deploy this component after PARMGEN configuration, see important documentation links:

• From master PARMGEN technote’s Section A1 Enablement Support, see HKJJ530 PTF and master OMEGAMON Monitoring for JVM technote:

• http://www-01.ibm.com/support/docview.wss?uid=swg21417935

Q#5: “I just applied the latest PARMGEN 1Q16 IF UA80256. Do I need to review the 65-page

What’s New in PARMGEN 1Q16 IF document?“

• A#5: PARMGEN Configuration tool supports the configuration of 39 components in the various IBM Service Management Suite on z/OS, OMEGAMON Performance Management Suite, etc. Any of the products that JOBGEN and PARMGEN deploy that require product configuration changes are delivered via the HKCI310 PARMGEN FMID PTFs delivered on a quarterly basis, or on the GA date of the requesting product PTFs or new product versions. As a best practice, review the OMEGAMON XE shared publications’ “What’s New in this Release” topic which cross-references the “What’s New in PARMGEN qqyy IF” low-level details document attached in Section C of the master PARMGEN technote. In the 65-page PARMGEN technote document, its size varies based on many product configuration features needed to support a product’s new version of IF. As a tip, review the Summary pages in the PARMGEN document to decide if you would be interested in exploiting the different features.

• Meeting Minutes: OMEGAMON Performance Management Suite V5.4 Deployment Customer Open Q&A Web Conference Call held March 30, 2016

From: Cecilia Day/Houston/IBM To: Date: 04/02/2016 01:22 AM Subject: Meeting Minutes: Discuss OMEGAMON Performance Management Suite V5.4 Deployment Call held March 30, 2016

Hello everyone, Thank you for your attendance of this month's PARMGEN customer open Q&A call and for the valuable feedback. A warm welcome to our new attendees! We hope that you found this month's session useful. We appreciate the ongoing collaboration in these monthly calls. I have captured the following info. during our webcast ('recap'ed the Q&A portion for reference in the 03/30/2016 Meeting Minutes:>C. Q&A Details section noted attached below, as well as Number of Attendees, presentation materials link in SMC>z Systems community and additional queries/comments posted during and after the call). For planning purposes, we will schedule our next open Q&A call on Wednesday, April 27, 2016 @ 11 a.m. US ET. Our usual Service Management Connect (SMC) System z community blog notification and broadcast calendar invitations will be sent out closer to our next PARMGEN Q&A session. For our customers who also participate in our OMEGAMON Performance Management Suite/Service Management Suite Early Access Program (EAP), thanks for your continued support attending our previous 2 PARMGEN EAP sessions in January and our OMEGAMON z Customer Advisory Council (zCAC) Vegas F2F in February. For PARMGEN EAP planning purposes, we will schedule our next OMEGAMON / SMS EAP on Thursday, April 14, 2016 @ 10 a.m. US ET. Planned agenda topic is a Demo of PARMGEN z/OS DLA exploitation @ latest March beta code as a follow-up from our zCAC F2F PARMGEN presentation. Mail notification from our new IBM Service Management Suite for z/OS EAP community

https://www.ibm.com/developerworks/servicemanagement/z/index.html and broadcast calendar invitations will be sent out closer to our next EAP.

For those interested in joining our EAP, thanks for the support -- this is a great opportunity to provide feedback on our product plans, as well as attend OMEGAMON and PARMGEN webcasts to see demos of early prototypes of the code. EAP membership lends itself to sponsored user opportunities to provide valuable feedback to affect the features and capabilities that we add into future deliverables while still in early design phases. Kindly contact our OMEGAMON EAP coordinator, Laura Rosensteel (lrosens@us.ibm.com) if you are interested in joining. Again, we appreciate this team's guidance and interactions very much. Please let me know if I may provide additional information. I welcome your additional feedback on this event, as well as on any other topics you'd like us to cover via this venue. Sincerely, Cecile Day PARMGEN L3/R&D

• 03/30/2016 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: Please let me know if I miss anyone from the attendance list. Thanks.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: http://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=80224b12-9e34-49b3-858a-f838e01bb89b

C. Q&A Details:

• March 30, 2016 Q&A:

Q#1: “For a Remote TEMS, does the "KDS_HUB_TEMS_NAME_NODEID" LPAR RTE profile parameter in WCONFIG(&rte_name) translate to a parm. in a runtime member?“

• A#1: No, this is an informational parameter only but is helpful for reference purposes as to the CMS_NODEID of the Hub TEMS that the z/OS Remote TEMS is reporting to. The KDS_HUB_TCP_HOST parameter is required as this is the IP hostname where the Hub TEMS is running. KDS_HUB_VTAM_* values are required if the Remote TEMS specifies "SNA" as one of its KDS_TEMS_COMM_PROTOCOLn as a means to communicate to the TEMS and Agents.

ISREDDE2 TDITN.FTU.$DEFAULT.WCONFIG($DEFAULT) - 01.01 Columns 00001 00072 Command ===> Scroll ===> CSR 001491 ** ------------------------------------------------------------------- 001492 ** If the TEMS is a Remote, specify its Hub TEMS values accordingly: 001493 ** Note: The KDS_HUB_* values populate the xKANPARU(KDCSSITE) member 001494 ** that Remote TEMS reads to know how to connect to its Hub. 001495 ** ------------------------------------------------------------------- 001496 KDS_HUB_TEMS_NAME_NODEID "&KDS_HUB_TEMS_NAME_NODEID." 001497 001498 ** ------------------------------------------------------------------- 001499 ** If the TEMS is a Remote, specify the network address of where its 001500 ** Hub TEMS is running: 001501 ** ------------------------------------------------------------------- 001502 KDS_HUB_TCP_HOST "&KDS_HUB_TCP_HOST." 001503 001504 ** ------------------------------------------------------------------- 001505 ** If the TEMS is a Remote, specify port numbers of its Hub TEMS: 001506 ** ------------------------------------------------------------------- 001507 KDS_HUB_TCP_PIPE_PORT_NUM &KDS_HUB_PORT. 001508 KDS_HUB_TCP_UDP_PORT_NUM "" * Hub KDS_TEMS_TCP_UDP_PORT_NUM 001509 KDS_HUB_TCP_PIPE6_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPE6_PORT_NUM 001510 KDS_HUB_TCP_UDP6_PORT_NUM "" * Hub KDS_TEMS_TCP_UDP6_PORT_NUM 001511 KDS_HUB_TCP_PIPES_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPES_PORT_NUM 001512 KDS_HUB_TCP_PIPE6S_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPE6S_PORT_NUM 001513 001514 ** ------------------------------------------------------------------- 001515 ** If the TEMS is a Remote, specify the VTAM global location broker 001516 ** APPLID and LPAR network ID of where the Hub TEMS is running, 001517 ** if the Hub TEMS is configured for SNA protocol: 001518 ** ------------------------------------------------------------------- 001519 KDS_HUB_VTAM_APPL_GLB_BROKER "&KDS_HUB_VTAM_APPL_GLB_BROKER." 001520 KDS_HUB_VTAM_NETID "&KDS_HUB_VTAM_NETID."

Q#2: “What are the new PARMGEN features in UA80256, specifically the OMEGAMON enhanced 3270UI (TOM)?”

• A#2: See the following slides:http://www-

01.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/par

mgenref/scenarios_deployment_intro.htm

• From IBM Knowledge Center:

• From Master PARMGEN Technote: Section A shows the necessary PTFs:

• From Master PARMGEN Technote: Section C shows the PARMGEN low-level details of each quarterly IF features:

• From Master PARMGEN Technote: Section C "What's New" attachment for 1Q16 IF - see OMEGAMON Enhanced 3270UI-related features

Q#3: “What are the 3 new XKAN* datasets allocated as part of my OMEGAMON V530 upgrade?“

• A#3: See RTE_XKAN_HILEV parameter in the RTE's WCONFIG(&rte_name) for more information: ISREDDE2 TDITN.FTU.$DEFAULT.WCONFIG($DEFAULT) - 01.01 Columns 00001 00072 Command ===> Scroll ===> CSR 000983 ** ------------------------------------------------------------------- 000984 ** (Optional) High-level qualifier for alternate Tivoli OMEGAMON (TOM) 000985 ** datasets for other integration products that deliver workspaces 000986 ** and other OMEGAMON enhanced 3270UI support elements. 000987 ** Notes: 000988 ** 1. (Tip) Specify the same HLQ for other RTEs that report to the 000989 ** same TOM in order to share the same XKAN* datasets. 000990 ** 2. KCIJPALO job appends the XKAN* low-level suffix to this HLQ. 000991 ** ------------------------------------------------------------------- 000992 RTE_XKAN_HILEV TDITN.FTU.&SYSPLEX. This is for products that exploit the TOM that do not install in the OMEGAMON/ITM CSI. See also PARMGEN post-configuration KOB on-line README for more information about this parameter and usage, specifically Step 3:

TDITN.FTU.$DEFAULT.WKANSAMU(KOBDFINL) ===> Scroll ===> CSR ***************************** Top of Data ****************************** +BEGIN ---------------------------------------------------------------+ OMEGAMON Subsystem Version 730 OMEGAMON Enhanced 3270 User Interface Version 730 and

additional OMNIMON Base features COMPLETE THE CONFIGURATION +BEGIN ---------------------------------------------------------------+ COMPONENTS: =============================================== ============== NAME COMPONENT CODE =============================================== ============== 1. OMEGAMON Subsystem KCN 2. OMEGAMON Enhanced 3270 User Interface KOB 3. Additional OMNIMON Base Features KOB Note: If you have not done so already, please review the common "Complete the Configuration" on-line READMEs for the following common components, prior to reviewing the post-configuration steps specific to this Agent: --- ---------------------------------------------------------- Kpp README: post-configuration instructions --- ---------------------------------------------------------- KCI (Required) Common to all components configured in this RTE This README applies to the following product components: A. Products that support both the OMEGAMON Subsystem and the OMEGAMON Enhanced 3270 User Interface features: ---- ----------------------------------------------------------- Kpp Product Name/Version ---- ----------------------------------------------------------- KC5 OMEGAMON XE for CICS on z/OS KD5 OMEGAMON XE for DB2 PE/PM KI5 OMEGAMON XE for IMS on z/OS KM5 OMEGAMON XE on z/OS KS3 OMEGAMON XE for Storage on z/OS ---- ----------------------------------------------------------- B1. Additional products that support the OMEGAMON Enhanced 3270 User Interface feature (installed in the same TDITNT.DEV.ITM63053.CSI) ---- ----------------------------------------------------------- Kpp Product Name/Version ---- ----------------------------------------------------------- KGW OMEGAMON XE for CICS TG on z/OS KJJ OMEGAMON Monitoring for JVM KMQ OMEGAMON XE for Messaging - WebSphere MQ Monitoring KQI OMEGAMON XE for Messaging - WebSphere Msg Broker (Integration Bus) KN3 OMEGAMON XE for Mainframe Networks ---- ----------------------------------------------------------- B2. Additional products that support the OMEGAMON Enhanced 3270 User Interface feature (installed in a separate CSI as the OMEGAMON enhanced 3270UI TDITNT.DEV.ITM63053.CSI)

---- ----------------------------------------------------------- Kpp Product Name/Version ---- ----------------------------------------------------------- KQQ IBM DB2 Query Monitor for z/OS V3.2 ---- ----------------------------------------------------------- C. Products that support TSO/ISPF interface OMNIMON Base feature (alternative to logging onto Classic OMEGAMON via VTAM interface): ---- ----------------------------------------------------------- Kpp Product Name/Version ---- ----------------------------------------------------------- KC5 OMEGAMON XE for CICS on z/OS KD5 OMEGAMON XE for DB2 PE/PM KI5 OMEGAMON XE for IMS on z/OS ---- ----------------------------------------------------------- +---------------------------------------------------------------------+ OMEGAMON Enhanced 3270 User Interface COMPLETE THE CONFIGURATION +---------------------------------------------------------------------+ . Step 3 - (Optional) Complete enablement of alternate XKAN* Tivoli OMEGAMON (TOM) datasets for other integration products that deliver workspaces and other OMEGAMON enhanced 3270UI support elements. In support of products that do not install in the same TDITNT.DEV.ITM63053.* OMEGAMON/ITM CSI that plan to integrate with OMEGAMON enhanced 3270UI, PARMGEN set up the TDITN.FTU.&SYSPLEX..XKAN* datasets during configuration. During $DEFAULT RTE configuration, the following steps were completed to prepare the IBMTOM OMEGAMON enhanced 3270UI set-up: a) PARMGEN allocated the following OMEGAMON enhanced 3270UI integration datasets via the PARMGEN composite KCIJPALO "Allocate runtime RO and RW (user) libs" job: - TDITN.FTU.&SYSPLEX..XKANWENU - TDITN.FTU.&SYSPLEX..XKANHENU - TDITN.FTU.&SYSPLEX..XKANEXEC RTE_XKAN_HILEV PARMGEN LPAR RTE profile parameter in TDITN.FTU.$DEFAULT.WCONFIG($DEFAULT) is available for overrides, if other than the default "TDITN.FTU.&SYSPLEX." high-level qualifier for alternate Tivoli OMEGAMON (TOM) datasets for other integration products that deliver workspaces and other OMEGAMON enhanced 3270UI support elements.

Notes: 1. (Tip) Specify the same HLQ for other RTEs that report to the same TOM in order to share the same XKAN* datasets. 2. KCIJPALO job automatically appends the XKAN* low-level suffix to this HLQ. b) PARMGEN also concatenated these XKAN* datasets in the respective OMEGAMON enhanced 3270UI IBMTOM started task DDNAMEs automatically: VIEW TDITN.FTU.$DEFAULT.xKANSAMU(IBMTOM) Command ===> //************************************************************ //* TOM workspace definitions: //************************************************************ //RKANWENU DD DISP=SHR, // DSN=&RHILEV..&SYS..UKANWENU // DD DISP=SHR, // DSN=&BASEHLEV.KANWENU // DD DISP=SHR, // DSN=TDITN.FTU.&SYSPLEX..XKANWENU //************************************************************ //* TOM help definitions: //************************************************************ //RKANHENU DD DISP=SHR, // DSN=&RHILEV..&SYS..UKANHENU // DD DISP=SHR, // DSN=&BASEHLEV.KANHENU // DD DISP=SHR, // DSN=TDITN.FTU.&SYSPLEX..XKANHENU //************************************************************ //* TOM standard REXX libraries: //************************************************************ //RKANEXEC DD DISP=SHR, // DSN=&RHILEV..&SYS..UKANEXEC // DD DISP=SHR, // DSN=&BASEHLEV.KANEXEC // DD DISP=SHR, // DSN=TDITN.FTU.&SYSPLEX..XKANEXEC c) If available in the TDITNT.DEV.ITM63053.TKANDATV, PARMGEN also copied the XKAN* exploiter's attribute and catalog files, and other object definition information (ODI) files delivered in the TKANDATV SMP/E target library, to the RTE's TDITN.FTU.$DEFAULT.RKANDATV via the PARMGEN KCIJPLOD "Copy SMP/E mbrs from TK*->RK* RO libs" IEBCOPY job. Otherwise, ensure that you copy the ODI files from the product's TKANDATV equivalent, into this RTE's TDITN.FTU.$DEFAULT.RKANDATV dataset.

If you wish to enable the XKAN* exploiter's integration support with IBMTOM OMEGAMON enhanced 3270UI, please refer to the respective product's OMEGAMON enhanced 3270UI integration post-PARMGEN-configuration steps to populate the TDITN.FTU.&SYSPLEX..XKAN* datasets and other OMEGAMON enhanced 3270UI enablement steps. For ease-of-use, PARMGEN provides a sample copy job called KOBXKNCP tailored in the following datasets below. - TDITN.FTU.$DEFAULT.WKANSAMU - TDITN.FTU.$DEFAULT.RKANSAMU Review the xKANSAMU(KOBXKNCP) job and customize accordingly to specify the XKAN* exploiter's source datasets to copy the OMEGAMON enhanced 3270UI SMP/E elements from. Submit the customized job in the following RTEs: - RTE where the OMEGAMON enhanced 3270UI is configured in - if the OMEGAMON enhanced 3270UI reports to a z/OS-based Hub TEMS, submit this job in the RTE where the z/OS Hub TEMS is configured (if other than the same local LPAR RTE where the OMEGAMON enhanced 3270UI is configured in) +---------------------------------------------------------------------+

Q#4: “What parameters are customized in PARMGEN to enable Near-term history in the OMEGAMON enhanced 3270UI?“

• A#4: See RTE_PDS_* and Kpp_PD_CYL parameters for OMEGAMON products that use ITM persistent datastore as historical storage to render data to enhanced 3270UI NTH. For OMEGAMON XE on z/OS, see RTE_CANSCN_*, RTE_KCN_VTAM_*, RTE_KCN_CACHE_KM5_NTH_*, RTE_KM5_NTH parameters to enable OMEGAMON Subsystem RMF Cache function for OMEGAMON XE on z/OS. See also helpful documentation links:

• http://www.ibm.com/support/knowledgecenter/SS2JNN_5.3.0/com.ibm.omegamon_xezos.doc_5.3.0/configuration/intro_ovu_omxezos_pcg.htm?lang=en

• Configuring the OMEGAMON XE on z/OS agent to use RMF data http://www.ibm.com/support/knowledgecenter/SS2JNN_5.3.0/com.ibm.omegamon_xezos.doc_5.3.0/configuration/cfg_parmlib_omxe_rmf_omxezos.htm?lang=en

• Enable RMF data collection http://www.ibm.com/support/knowledgecenter/SS2JNN_5.3.0/com.ibm.omegamon_xezos.doc_5.3.0/configuration/complete_enable_rmf_omxezos_pcg.htm?lang=en

• https://www.ibm.com/support/knowledgecenter/SS2JNN_5.3.0/com.ibm.omegamon_xezos.doc_5.3.0/configuration/overview_new630fp2_e3270.htm?lang=en

• http://www.ibm.com/support/knowledgecenter/SS2JNN_5.3.0/com.ibm.omegamon_xezos.doc_5.3.0/configuration/cfg_parmlib_omxe_rmf_omxezos.htm?lang=en

• http://www.ibm.com/support/knowledgecenter/SS2JNN_5.3.0/com.ibm.omegamon_xezos.doc_5.3.0/configuration/managing_nth_datacollect_omxezos_pcg.htm?cp=SS2JNN_5.3.0&lang=en

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held February 17, 2016

From: Cecilia Day/Houston/IBM To: Date: 02/17/2016 07:39 PM Subject: Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held February 17, 2016

Hello everyone, Thank you for your attendance of this month's PARMGEN customer open Q&A call and for the valuable feedback. A warm welcome to our new attendees! We hope that you found this month's session useful. We appreciate the ongoing collaboration in these monthly calls. I have captured the following info. during our webcast ('recap'ed the Q&A portion for reference in the Meeting Minutes>C. Q&A Details section noted below, as well as attendance, presentation materials link in SMC>z Systems community and additional queries/comments posted during the call). For planning purposes, we will schedule our next open Q&A call on Wednesday, March 30, 2016 @ 11 a.m. US ET. It is being scheduled a couple of weeks later than normal, to accommodate our customers' schedules; a number of our participants will also be attending upcoming IBM customer events (InterConnect 2016, AOTC, zCAC, SHARE, etc.). Our usual Service Management Connect (SMC) System z community blog notification and broadcast calendar invitations will be sent out closer to our next PARMGEN Q&A session. For our customers who also participate in our OMEGAMON Performance Management Suite/Service Management Suite Early Access Program (EAP), thanks for attending both PARMGEN EAP sessions last month. For those interested in joining our EAP, thanks for the support -- this is a great opportunity to provide feedback on our product plans, as well as attend OMEGAMON and PARMGEN webcasts to see demos of early prototypes of the code. EAP membership lends itself to sponsored user opportunities to provide valuable feedback to affect the features and capabilities that we add into future deliverables while still in early design phases. Kindly contact our OMEGAMON EAP coordinator, Laura Rosensteel (lrosens@us.ibm.com) if you are interested in joining. Again, we appreciate this team's guidance and interactions very much. Please let me know if I may provide additional information. I welcome your add'l feedback on this event, as well as on any other topics you'd like us to cover via this venue. Sincerely, Cecile Day PARMGEN L3/R&D

• 02/17/2016 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: Please let me know if I miss anyone from the attendance list. Thanks.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=d8e97d6a-4980-47bd-b78b-07d515fae30d

C. Q&A Details:

• February 17, 2016 Q&A:

Q#1: “Are there z/OS Agent PTFs required for the TEP client jar file certificates expiring in April?“

• A#1: See “Recommended Maintenance Service Levels for Tivoli OMEGAMON XE and Tivoli Advanced Reporting products on ITM V6.x” http://www-01.ibm.com/support/docview.wss?uid=swg21290883 technote, which features http://www-01.ibm.com/support/docview.wss?uid=swg21269613 (“Failed to validate expired certificate affecting all TEP browser TEP webstart”) technote. This technote lists the OMEGAMON V530/V730 (GA) PTFs / Fixpacks, and GA-1 PTFs or APARs / Fixpacks.

Q#2: “Are there PARMGEN jobs to REPRO VSAM data from the old datasets to a new RTE?”

• A#2: See PARMGEN Utilities “Clone customized data from another RTE.” option. Also see OMXE Shared publications Deployment Scenarios

(http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/scenarios_deployment_intro.htm)

In our LPARRTE demo. today, focus is on these 2 LPAR RTE profile parameters that are recommended for customization prior to generating the KCIJPCLN job:

The PARMGEN "Perform post configuration steps." step also provides the reminder about usage of KCIJPCLN if it applies to the type of cloning scenario being performed for the new RTE.

ISREDDE2 TDITN.OMEGV530.LPARRTE.WKANSAMU(KCIDFINL)

Command ===> Scroll ===> CSR

001033 Step 9 - Clone or migrate customized data from another RTE.

001034

001035 In general, the "Clone customized data from another RTE" job

001036 (KCIJPCLN) on the "UTILITIES" panel can be used to copy the data

001037 from the original RTE datasets to a new set of RTE datasets (VSAM,

001038 Non-VSAM) regardless if this is an upgrade of a product version

001039 configured in this RTE, and this new RTE is using a new set of

001040 datasets to preserve the "production" RTE datasets at the previous

001041 version, while this new upgrade RTE is in test, or this is simply a

001042 clone of another RTE within the same product version.

001043 ================================================================

001044 | The steps in the KCIJPCLN job follow this naming convention: |

001045 |--------------------------------------------------------------|

001046 | CPDATFpp - if the RTE has customized Non-VSAM data to clone |

001047 | such as profiles, screenspaces, etc. |

001048 | CPEXITpp - if the RTE has sample members to clone |

001049 | such as security exits, etc. |

001050 | CPGLBLpp - if the RTE has customized globals to clone |

001051 | CPMODUpp - if the RTE has customized modules to clone |

001052 | such as security modules, globals, etc. |

001053 | CPNVSMpp - if the RTE has customized Non-VSAM data to clone |

001054 | such as profiles, screenspaces, workspaces, etc. |

001055 | CPSEQUpp - if the RTE has sequential data to clone |

001056 | CPVSAMpp - if the RTE has customized VSAM data to clone |

001057 | such as product situations, SDA status, etc. |

001058 | CPWENUpp - if the RTE has customized Non-VSAM data to clone |

001059 | such as workspaces, etc. |

001060 ================================================================

001061

Related to 2/17/2016 Q#2 is a question posed from our Jan. 20th call:

• 1/20/2016 Q#3: “In the cloning scenario covered for the CLONTO RTE (modeled from WCONFIG(CLONFROM) for the demo (from Q#3), when I upgrade to the V530s/V730s, do I perform something similar?”

• 1/20/2016 A#3: “OMEGAMON XE shared documentation >Version 6.3.0 Fix Pack 2 and above >Scenarios and how-tos> Deployment scenarios> Cloning an existing PARMGEN runtime environment (Quick mode) ” covers if there are no changes to the HLQs of the RTE being cloned from the model. In an upgrade scenario whereby RTE HLQs are currently versionized (for example, RTE_HILEV=OMXE.V510, RTE_VSAM_HILEV=OMXE.V510, etc.) and the plan is to build a new set of RTE datasets using a new set of RTE HLQ (for example, RTE_HILEV=OMXE.V530, RTE_VSAM_HILEV=OMXE.V530, etc.) and reuse the existing RTE configuration values from WCONFIG(&rte)., then pls. also refer to the PARMGEN hands-on lab. guide attached in the master PARMGEN technote (http://www.ibm.com/support/docview.wss?uid=swg21417935). QCF11 is for an ICAT to PARMGEN conversion and an upgrade scenario from V510 to V530, but the concept is the same.

Q#3: “How do I add the new OMEGAMON Monitoring for JVM Agent?“

• A#3: See “Scenario RTE01: Adding a new product to an existing PARMGEN runtime environment” in http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/scenarios_parmgen_maint_scenario_addnewproduct.htm?cp=SSAUBV%2F1-9-2-0. This new feature of OMEGAMON XE on z/OS product was announced in the following announcement letters and SMC z Systems blog: "Introducing OMEGAMON Monitoring for JVM on z/OS" https://www.ibm.com/developerworks/community/blogs/5e65990a-9690-42e2-93b1-c2267be7620c/entry/Introducing_OMEGAMON_Monitoring_for_JVM_on_z_OS?lang=en

• A3a. Existing RTE deployment:

• If your RTE reconfiguration scenario falls under a combination of conditions such as other products configured in the RTE are also being upgraded to new version(s) of the products, and/or you have a new SMP/E environment where the new Serverpac containing the upgraded versions and additional features or components to configure, please also refer to the SMPE05 and SMPE06 upgrade scenarios in the OMEGAMON XE shared publications (http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/scenarios_parmgen_maint_scenario_post-SMPE.htm) Following these scenarios, upon reconfiguration of the RTE via option "1. Set up/Refresh PARMGEN work environment." on the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU (Quick Configuration Mode), adding the new OMEGAMON Monitoring for JVM Agent entails selecting the new component from this panel:

•

Upon confirmation on the "INCLUDE (CONFIGURE) INSTALLED PRODUCT(S) IN THIS LPAR RTE" panel, ensure that you provide a backup RTE profile member name. This ensures that the generated KCIJPCFG set-up/reconfiguration job submits the KCIJPPRF LPAR RTE profile refresh job, which preserves the previous LPAR RTE profile, and merges in any new or changed parameters introduced by this reconfiguration (in this case, the addition of the OMEGAMON Monitoring for JVM Agent, which brings in KJJ$* and KJJ_* parameters in the RTE's WCONFIG(LPARRTE) profile member, brings in additional KJJ$C*/KJJ$P*/KJJ$S* WCONFIG imbeds, and other new runtime members in support of this new Agent).

After submitting the KCIJPCFG job, follow the remaining PARMGEN reconfiguration steps as outlined in the upgrade scenario or RTE scenario.

• A3b. First-time RTE deployment:

• If the RTE scenario involves a first-time OMEGAMON RTE deployment, please follow any of the QCFnn implementation scenarios in http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/PARMGEN_scenarios_intro.htm?cp=SSAUBV%2F1-9-0following the instructions to point to predefined RTE models.

There are 20 PARMGEN-supplied predefined RTE models delivered in &gbl_target_hilev.TKANSAM that one can point to in creating a brand new RTE. One can place a question mark "?" on the first field of the "KCIPQPG1 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (1 OF 3)" panel, as shown below:

.

Following the QCFnn implementation scenario, after submitting the KCIJPCFG job, perform the remaining PARMGEN RTE set-up configuration steps as outlined in the implementation scenario featuring usage of the predefined RTE models.

Q#4: “How do I get PDFs for the OMEGAMON product manuals?“

• A#4: From our Information Development team, with the introduction of IBM Knowledge Center (KC) IBM-wide in 2014, PDFs are no longer supplied by default, for our OMEGAMON product family. Via IBM Knowledge Center, one can create his/her own KC PDF via "My Collections". See http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/common/pdf.htm. Also see PARMGEN technote's (http://www.ibm.com/support/docview.wss?uid=swg21417935) reference to the following SMC blog:Tip: IBM® Knowledge Center provides a way to create Knowledge Center PDFs via "My Collections" tab.

For more information about "My Collections", refer to System z Community Blog: "Where has the OMEGAMON documentation gone?" (URL: http://www.ibm.com/developerworks/community/blogs/5e65990a-9690-42e2-93b1-c2267be7620c/entry/omegamon_shared_documentation_ch_ch_ch_changes?lang=en)

• Also noted in the master PARMGEN technote is this helpful reference:

Reference: OMEGAMON V5.3, V7.3 releases full manual PDF links for customer requests:( Date Last Updated: 20141112)

Reference: New OMEGAMON V5.3, V7.3 releases full manual PDF links for customer requests

• Reference: From our Information Development team: These are unofficial PDF builds. For the most up-to-date information, clients should check the IBM Knowledge Center. Although we have made every effort to keep the PDF versions up-to-date, the html version in IBM Knowledge Center is the official version of the content. 1. ftp://public.dhe.ibm.com/software/tivoli/OMEGAMON/OMEGAMON_shared/ - Shared Documents for all OMEGAMONs 2. ftp://public.dhe.ibm.com/software/tivoli/OMEGAMON/OMXESTOR/ - OMEGAMON XE for Storage V530 PDFs 3. ftp://public.dhe.ibm.com/software/tivoli/OMEGAMON/OMXEZOS/ - OMEGAMON XE for z/OS V530 PDFs 4. ftp://public.dhe.ibm.com/software/tivoli/OMEGAMON/OMXECICS/530/ - OMEGAMON XE for CICS V530 PDFs 5. ftp://public.dhe.ibm.com/software/tivoli/OMEGAMON/OMXEMES/ - OMEGAMON XE for Messaging V730 PDFs 6. https://www-304.ibm.com/support/docview.wss?uid=swg27020910#omegaxepe-lib - OMEGAMON XE for DB2 V530 Performance Expert PDFs

7. https://www-304.ibm.com/support/docview.wss?uid=swg27020910 - omegaxepe-

libhttps://www-304.ibm.com/support/docview.wss?uid=swg27020910#omegaxepm-lib - OMEGAMON XE for for

DB2 Performance Monitor V530 PDFs

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held January 20, 2016

From: Cecilia Day/Houston/IBM To: Date: 01/22/2016 12:37 PM Subject: (Mail-group-A) Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held January 20, 2016

Hello everyone, Thank you for your attendance of this month's PARMGEN customer open Q&A call and for the valuable feedback. A warm welcome to our new attendees! We hope that you found this month's session useful. We appreciate the ongoing collaboration in these monthly calls. I have captured the following info. during our webcast ('recap'ed the Q&A portion for reference in the Meeting Minutes>C. Q&A Details section noted below, as well as attendance, presentation materials link in SMC>z Systems community and additional queries/comments posted during the call).

For planning purposes, we will schedule our next open Q&A call on Wednesday, February 17, 2016 @ 11 a.m. US ET. Our usual Service Management Connect (SMC) System z community blog notificationand broadcast calendar invitations will be sent out closer to our next Q&A session. For our customers who also participate in our OMEGAMON Performance Management Suite Early Access Program (EAP), thanks for attending Part 1 of the PARMGEN EAP on Jan. 21st; the broadcast invitation to our next scheduled EAP call for Thursday, January 28th @ 10 a.m. US EThas been sent out (Part 2). For those interested in joining our EAP, thanks for the support. This is a great opportunity to provide feedback on our product plans, as well as attend OMEGAMON and PARMGEN webcasts to see demos of early prototypes of the code. EAP membership lends itself to sponsored user opportunities to provide valuable feedback to affect the features and capabilities that we add into future deliverables while still in early design phases. Kindly send me a confirmation if you would like to join, and I will forward your contact info. to our EAP coordinators. Again, we appreciate this team's guidance and interactions very much. Please let me know if I may provide additional information. I welcome your add'l feedback on this event, as well as on any other topics you'd like us to cover via this venue. On behalf of the OMEGAMON/PARMGEN development teams, I wish everyone a great start to 2016! Sincerely, Cecile Day PARMGEN L3/R&D

• 01/20/2016 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from IBM Connections Cloud Web Meeting log-on: Note: Please let me know if I miss anyone from the attendance list. Thanks.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC) System z community:

URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=475222d8-57c2-4968-8a1b-a1524991b479

C. Q&A Details:

• January 20, 2016 Q&A:

Q#1: “Does ITM support Java 8?“

• A#1: Java 8 is supported starting in ITM630FP5 according to http://www.ibm.com/support/docview.wss?uid=swg21672459 ("Master list of ITM TEP/Java issues") Flash. Also see other related notes:

§http://www.ibm.com/support/docview.wss?uid=swg21290883 ("Recommended Maintenance Service Levels for Tivoli OMEGAMON XE and Tivoli Advanced Reporting products on ITM V6.x") §http://www.ibm.com/support/docview.wss?uid=swg21269613 (“Failed to validate expired certificate affecting all TEP browser TEP webstart”)

Q#2: “Our shop runs out of the SMP/E targets (we do SYSRES cloning). I always loaded the RTEs in ICAT – do I need to do that in PARMGEN?”

• A#2: Yes, see KCIJPLOD load job or the cross-RTE KCIJ@LOD (“LOADALL”) or upcoming KCIJ@ODI (“LOADDATV”) job that will be delivered in PARMGEN 1Q16 IF (HKCI310 PTF UA80256).

Q#3: “We created a new RTE from the original one but some values were still pointing to the old RTE values. What steps were missed?”

• A#3: See “OMEGAMON XE shared documentation >Version 6.3.0 Fix Pack 2 and above >Scenarios and how-tos> Deployment scenarios> Cloning an existing PARMGEN runtime environment (Quick mode) ”. See WCONFIG($VALRPT) cloning warnings.

Q#4: “In the cloning scenario covered for the CLONTO RTE (modeled from WCONFIG(CLONFROM) for the demo (from Q#3), when I upgrade to the V530s/V730s, do I perform something similar?”

• A#4: “OMEGAMON XE shared documentation >Version 6.3.0 Fix Pack 2 and above >Scenarios and how-tos> Deployment scenarios> Cloning an existing PARMGEN runtime environment (Quick mode) ” covers if there are no changes to the HLQs of the RTE being cloned from the model. In an upgrade scenario whereby RTE HLQs

are currently versionized (for example, RTE_HILEV=OMXE.V510, RTE_VSAM_HILEV=OMXE.V510, etc.) and the plan is to build a new set of RTE datasets using a new set of RTE HLQ (for example, RTE_HILEV=OMXE.V530, RTE_VSAM_HILEV=OMXE.V530, etc.) and reuse the existing RTE configuration values from WCONFIG(&rte)., then pls. also refer to the PARMGEN hands-on lab. guide attached in the master PARMGEN technote (http://www.ibm.com/support/docview.wss?uid=swg21417935). QCF11 is for an ICAT to PARMGEN conversion and an upgrade scenario from V510 to V530, but the concept is the same.

Q#5: “We currently are running the ICAT version of OMEGAMON XE monitoring products (z/OS, CICS, DB2 & TEMS) versions 4.2.0 & 6.2.2. I have received & applied the updates for HKCI310 & am ready to start the conversion to PARMGEN. What are my next steps? ”

• A#5: See “Scenario QCF11: Converting an ICAT runtime environment to PARMGEN”

Q#6: "How do I update KMQUSER member (for OMEGAMON XE for Messaging – MQ Monitor

Agent)?"

• A#6: In ICAT, see “Complete the configuration” topic on RKANCMDU(KMQUSER). In PARMGEN, see the RTE's WCONFIG(KMQ$CUSR) override imbed which preserves the advanced customization.

• Reference: These members provide the on-line list of imbeds available for advanced parms../special

customization usage:

• In PARMGEN, we want to ensure that the KMQUSER customizations are preserved (post-manual edits in ICAT) so we built this freeform imbed that can be customized before $PARSE run. The imbed can also be copied to other RTEs via WCONFIG(KCIJPCCF) job.

• In our example today, we customized WCONFIG(KMQ$CUSR) as shown in the example below, then reran $PARSECM job (filtered on SELECT MEMBER=(KMQUSER) to only rebuild WKANCMDU(KMQUSER) if one takes a shortcut approach, then when ready to deploy the changes to the running OMXE MQ Agent started task, submit the KCIJPW2R job which copies the updated WKANCMDU(KMQUSER) over to the product execution user lib. RKANCMDU(KMQUSER) - PARMGEN supports staged deployment.

Q#7: "We are upgrading from SA V3.4 to V3.5 - does SA have integration to the OMEGAMON/ITM CSI?"

• A#7: Yes, the IBM Tivoli System Automation for z/OS V3.5.0 (Program Number 5698-SA3) comes with these FMIDs HWRE350, JWRE35F, JWRE35C, JWRE35I, JWRE351, HWRE35D, HKAH35T. It's part of the Service Management Suite for z/OS. The HKAH35T FMID is the SA Monitoring Agent (TEP-enabled) Agent that PARMGEN configures when installed in the same target zone as the OMEGAMON products and z/OS ITM (TEMS) environment:

KCIP@PGI - INCLUDE (CONFIGURE) INSTALLED PRODUCT(S) IN THIS RTE Row 1 to 28

of 28

Command ===> Scroll ===> CSR

Select ("S" or "/") products to CONFIGURE those product(s) in PLB4SYSA RTE.

Select or deselect products to include or exclude from configuration.

Products configured in the model or current RTE (reconfiguring) are

preselected

When finished, change N to Y to confirm selections. Confirm ==> N (Y, N)

Kpp Component or Product Name and Version

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

/ KAH System Automation Monitoring Agent V350

/ KC5 OMEGAMON XE for CICS on z/OS V530

/ KDO Tivoli Decision Support for z/OS Agent V181

/ KDS Tivoli Enterprise Monitoring Server V630 (FP6 PTF UA79950)

/ KD4 ITCAM for SOA Agent V711

/ KD5 OMEGAMON XE for DB2 PE/PM V530

/ KGW OMEGAMON XE for CICS TG on z/OS V530

/ KI5 OMEGAMON XE for IMS on z/OS V530

/ KMC OMEGAMON XE for Messaging - WebSphere MQ Configuration V730

/ KMQ OMEGAMON XE for Messaging - WebSphere MQ Monitoring V730

/ KM5 OMEGAMON XE on z/OS V530

/ KNA NetView for z/OS Agent V621

/ KN3 OMEGAMON XE for Mainframe Networks V530

/ KOB OMEGAMON Enhanced 3270 User Interface V730

/ KQI OMEGAMON XE for Messaging - WebSphere Message Broker V730

/ KRG Advanced Audit for DFSMShsm Agent V250

/ KRH Advanced Reporting and Management for DFSMShsm Agent V250

/ KRJ Advanced Allocation Management Agent V330

/ KRK Automated Tape Allocation Manager for z/OS Agent V330

/ KRN Advanced Catalog Management Agent V260

/ KRV Advanced Backup and Recovery for z/OS Agent V240

/ KRW Tape Optimizer for z/OS Agent V220

/ KS3 OMEGAMON XE for Storage on z/OS V530

/ KWO OMEGAMON Dashboard Edition on z/OS - OMEGAVIEW V530

/ KYN ITCAM for Application Diagnostics, TEMA V710.03

End of data

For more information about SA, pls. see the product's program directory in this link: http://www.ibm.com/support/knowledgecenter/SSWRCJ_3.5.0/com.ibm.safos.doc_3.5/sa35_product_manuals.html

In the SA program directory, it recommends that HKAH35T FMID is installed in the z/OS ITM CSI:

When PARMGEN is invoked (ex '&gbl_target_hilev.TKANCUS'), if the KAH* elements exist, it will be eligible for configuration. More importantly, if the KAH monitoring Agent will report to a z/OS-based TEMS, the TEMS must have access to the Agent's ODI files (object def. ino, such as KAHCAT catalog, KAHATR attribute, KAH* jar/manifest files for SDA enablement, etc.) via the TKANDATV/RKANDATV datasets so it's best to install in the same target zone as the TEMS and other Agents (OMEGAMONs for example) so they can be deployed in the same LPAR RTE. Similar requirements for the NetView EMA piece of the NetView product. KNA is the TEP-enabled monitoring Agent on z/OS that PARMGEN also configures. IBM Tivoli NetView for z/OS Enterprise Management Agent V6.2.1 (Program Number 5697-NV6) for FMID HNV621A. Its program directory is in this link: https://www.ibm.com/support/knowledgecenter/SSZJDU_6.2.1/com.ibm.itnetviewforzos.doc_6.2.1/na621pd1.pdf?cp=SSANTA_1.3.0%2F0-7-2-0-2

_________________________________________________________

Cecile Day z/OS OMEGAMON/ITM Install/Config. - Development IBM System z | Office:(720)396-2831 | Tieline:938-2831 (phone) Service Management Connect "It’s the Easter season all year round, a time of reflection, forgiveness, and reconciliation."

Previous 2015 Meeting Minutes:

Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held November 18, 2015

Hello everyone, Thank you for your attendance of this month's PARMGEN customer open Q&A call and for the valuable feedback. A warm welcome to our new attendees! We hope that you found this month's session useful. We appreciate the ongoing collaboration in these monthly calls. I have captured the following info. during our webcast ('recap'ed the Q&A portion for reference in the Meeting Minutes: section noted below, as well as attendance, presentation materials link in SMC and add'l queries posted during the call). We will schedule our next open Q&A call on January 20, 2016. Service Management Connect (SMC) System z community blog notification and broadcast calendar invitations will be sent closer to our next Q&A session. Again, we appreciate this team's guidance and interactions very much. Please let me know if I may provide additional information. I welcome your add'l feedback on this event, as well as on any other topics you'd like us to cover via this venue. On behalf of the OMEGAMON/PARMGEN development teams, I wish everyone a happy and peaceful holiday season.

Sincerely, Cecile Day PARMGEN L3/R&D

• 11/18/2015 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from SmartCloud Web Conference log-on: Note: Please let me know if I miss anyone from the attendance list. Thanks.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC) System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=b447cab9-a014-46a6-828a-811467d059a3

C. Q&A Details:

• November 18, 2015 Q&A:

Q#1a: “Are the z/OS 2.2 PARMGEN toleration PTFs (UA76016 and later) backward compatible? That is, can they be applied while we are still running z/OS 2.1? Assuming the answer is yes, I know I need to port the 32 read-only shared BASE libraries to the other sysplexes. But do I also need to reconfigure each RTE itself namely, starting over with Option 1 of PARMGEN s Quick Configuration?”.

• A#1a: See OMEGAMON Family z/OS 2.2. currency technote (URL: https://www.ibm.com/support/docview.wss?uid=swg21902875).

• Also cross-referenced in the PARMGEN technote:

• Slides #11 and #12 of the Nov. 18th presentation materials provide additional information.

Q#1b: “Can you still stage deployment of the RTE runtime members if the RTE was staged in a z/OS 2.1 LPAR for a remote LPAR that will be upgraded to z/OS 2.2 if the GBL_* parms. indicate that this system that PARMGEN staging jobs were ran on indicate "z/OS 2.1"?

• A#1b: Yes, you can stage the RTE ahead of time. The GBL_CI* parms. in the LPAR RTE profile/$GBL* profile (ex., RTE=LPARRTE1 in this example), are for informational/diagnostic purposes so we can tell what system a particular PARMGEN job ($PARSE for example) was ran on:

• They are generated as comments in the PARMGEN Maintenance comment block of the job logger step in each PARMGEN job and product started tasks:

Q#2: “We missed changing KD2_DBnn_DB2_VER from 91 to 11 resulting in .RKD2SAM not get fully populated. The VALIDATE step should generate a RC=08 when a DB2 version is no longer supported. ”.

• A#2: See product currency topics in their Knowledge Center. Within PARMGEN, see WCONFIG($VALRPT) validation report, RTE_VALIDATION_LEVEL=W (warning mode RC=04) / RTE_VALIDATION_LEVEL=E (error mode RC=08) parameter & “CURRENCY NOTES:” in WCONFIG(&rte_name)/WCONFIG($GBL*) user profiles. RTE_VALIDATION_LEVEL=W (warning) was the consensus for downward compatibility with ICAT mode, on behalf of ICAT batch mode for products that are not yet converted to PARMGEN, or RTEs not yet converted to PARMGEN (or it will halt ICAT batch configuration if the OMEGAMON DB2 product config. dictionary TKANCUS(KD2DDICT) eliminates "91" from the valid selection list starting in OMEGAMON XE for DB2 V5.3.0 (HKDB530 FMID) where DB2 V9.1 support was dropped). Best practice tip is run through a validation test with RTE_VALIDATION_LEVEL=E to see what the PARMGEN validation report will produce prior to doing a full deploy of the runtime mbrs. RTE_VALIDATION_LEVEL=E (error mode) would generate the $PARSE* VALIDATE step and the standalone KCIJPVAL validation job with a RC=08:

•

• $PARSE job and KCIJPVAL job will flag as an error and generate Section 4 of the WCONFIG($VALPRT) validation report as follows:

TDITN.ZCAC.LPARRTE1.WCONFIG($VALRPT)

===> Scroll ===> CSR

| This report contains four sections: |

| 1. Parameter Validation Errors: |

| Application Batch Dictionary Exits |

| (Section 1 Validation Return Code = 0) |

| 2. Parameter Values Changed from Defaults |

| 3. Components Configured in this RTE |

| 4. Parameter Validation Errors: |

| Application Validation Exits |

| (Section 4 Validation Return Code = 8) |

| Note: Current RTE_VALIDATION_LEVEL set = 'E' |

+======================================================================+

+======================================================================+

| Section 4: Parameter Validation Errors: |

| Application Validation Exits |

| (Validation Return Code = 8) |

| Note: RTE_VALIDATION_LEVEL (RTEVALLEV) value is set to 'E'. |

| Change the RTE_VALIDATION_LEVEL value |

| in the WCONFIG(LPARRTE1) |

| RTE LPAR profile, if needed. |

+----------------------------------------------------------------------+

| Kpp RTEVALLEV Component Analysis Messages |

| (I/W/E) |

| --- ---------------------------------------------------------------- |

| KD2 E (DB01) 91 is an invalid value for KD2_DB_DB2_VER |

| |

| KRT I ---------------------------------------------------------- |

| W GBL_DSN_SYS1_PROCLIB parameter is set to SYS1.PROCLIB |

| value. KCIJPSYS job will copy the product started tasks to |

| this library. Customize to your own staging PROCLIB as |

| necessary, if you do not have the authorization to update |

| this dataset. Modify GBL_DSN_SYS1_PROCLIB parameter in |

| WCONFIG($GBL$USR) profile or in the WCONFIG(&rte_name) |

| profile (if this RTE member was converted from ICAT). |

| I ---------------------------------------------------------- |

| W GBL_DSN_SYS1_VTAMLST parameter is set to SYS1.VTAMLST |

| value. KCIJPSYS job will copy the product VTAM major nodes |

| to this library. Customize to your own staging VTAMLST as |

| necessary, if you do not have the authorization to update |

| this dataset. Modify GBL_DSN_SYS1_VTAMLST parameter in |

| WCONFIG($GBL$USR) profile or in the WCONFIG(&rte_name) |

| profile (if this RTE member was converted from ICAT). |

| I -------------------------------------------------------- |

| I KD2_OMPE_DSHLQ located with value TDITN.ZCAC |

| I RTE_HILEV located with value TDITN.ZCAC |

| W The KD2_OMPE_DSHLQ HLQ is typically the RTE_HILEV + |

| RTE_NAME. Review if RTE_HILEV should match the first part |

| of the KD2_OMPE_DSHLQ value (cloning consideration). |

| I -------------------------------------------------------- |

| I KD2_OMPE_VSAM_DSHLQ located with value TDITN.ZCAC |

| I RTE_VSAM_HILEV located with value TDITN.ZCAC |

| W The KD2_OMPE_VSAM_DSHLQ HLQ is typically the RTE_VSAM_HILEV |

| + RTE_NAME. Review if RTE_VSAM_HILEV should match the |

| first part of the KD2_OMPE_VSAM_DSHLQ value (cloning |

| consideration). |

+----------------------------------------------------------------------+

| |

| *** Parameter analysis messages generated. *** |

| *** Correct or adjust as necessary *** |

| *** before proceeding. *** |

| |

+======================================================================+

**************************** Bottom of Data ****************************

Q#3: "How do I update KMQUSER member (for OMEGAMON XE for Messaging – MQ Monitor Agent)?"

• A#3: In ICAT, see “Complete the configuration” topic on RKANCMDU(KMQUSER). In PARMGEN, see the RTE's WCONFIG(KMQ$CUSR) override imbed which preserves the advanced customization.

• Reference: These members provide the on-line list of imbeds available for advanced parms../special

customization usage:

• In PARMGEN, we want to ensure that the KMQUSER customizations are preserved (post-manual edits in ICAT) so we built this freeform imbed that can be customized before $PARSE run. The imbed can also be copied to other RTEs via WCONFIG(KCIJPCCF) job.

• In our example today, we customized WCONFIG(KMQ$CUSR) as shown in the example below, then reran $PARSECM job (filtered on SELECT MEMBER=(KMQUSER) to only rebuild WKANCMDU(KMQUSER) if one takes a shortcut approach, then when ready to deploy the changes to the running OMXE MQ Agent started task, submit the KCIJPW2R job which copies the updated WKANCMDU(KMQUSER) over to the product execution user lib.

RKANCMDU(KMQUSER) - PARMGEN supports staged deployment.

Q#4: “How do I quickly delete/reallocate PDS files?”

• A#4: See http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/howto_reallocate_pdsfiles.htm and http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/howto_increase_pdsfilecount.htm

• Considerations: ITM KPD* code writes to these seq. files (exclusive enqueue) when the STCs are up (see RKPDIN DD as to which files they write to). If you need to delete/reallocate the PDS files, the STCs would need to be down so stage the updates accordingly. In today's example, questions were posed regarding RTE_PDS_FILE_COUNT and how it relates to Kpp_PD_CYL. 6 files per product set of seq. files based on Kpp_PD_CYL so the total Kpp_PD_CYL amount is devied up by 6 seq. files which make up the SIZE=nnM generated in the RKANPARU(KppAL) allocation member per product.

•

Q#5: “How many VSAM files can be allocated for (thread) NTH for OMXE for DB2?”

• A#5: See KD2_PFnn_HIS_VSAM_* parms. in the WCONFIG LPAR RTE profile (you can also place your cursor on the parm. and press=F1 for the on-line help). Each VSAM_MB is for each unique VSAM per DB2 subsystem. For there are 5 KD2_DBnn_* rows being monitored all assigned to PROFID=P001 as in the case below, PARMGEN's ALLOCDS job (generated/submitted by the $PARSESV's KCIJPUPX job/$PARSE's KD2JPUPC/CRTDB2M* job automatically if KD2_OMPE_RUNALLOC=Y) will generate 5 sets of VSAMs per DB2 subsystem assigned to P001 profile.

•

Q#6: “What are the differences in NTH storage?”

• A#6: See slides #53 - #56 to give a brief overview of the differences in storage datasets used for OMEGAMON enhanced 3720UI near-term-history (some products use the ITM persistent datastore seq. files), application history (OMXE IMS ATF z/OS logger, OMEGAMON CICS Classic ONDV using CICS-region specific RKC2HIST VSAMs if not using default dataspace, OMEGAMON DB2 Classic thread NTH using DB2-specific RKD2VSnn VSAMs, etc.)

• Other feedback/request for enhancements: I. Request for PDSE version 2 to be externalized in PARMGEN: logged as an investigative item II. Request for CRTDB2* OMXE DB2 job to generate the DB2 runtime members regardless if it encounters DB2 9.1-

related SSID (ignore DB2 9.1-related OMDB2 runtime mbrs. and proceed generating DB2 10, DB2 11-related runtime members): forwarded this request to OMXE DB2 L3/dev. teams. The PARMGEN validation report drives PARMGEN infrastructure validation using PARMGEN framework code for Section 1 and Section 4 of the validation report. Certain advanced validation exits, if supplied by the products, are also called out in Section 4 of the PARMGEN WCONFIG($VALPRT) validation report. OMEGAMON XE for DB2's KD2R* advanced validation REXX exits provide the enhancements for these KD2R* SMP/e elements. Request sent to the team for consideration of this request.

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held October 7, 2015

Hello everyone, Thank you for your attendance of this month's PARMGEN customer open Q&A call and for the valuable feedback. A warm welcome to our new attendees from our existing customer accounts and new accounts! We hope that you found the session useful. We appreciate the ongoing collaboration in this month's call. I have captured the following info. during our webcast ('recap'ed the Q&A portion for reference in the Meeting Minutes: section noted below, as well as queries posted in the chat). We will schedule our next monthly open Q&A call on November 11th. Service Management Connect (SMC) System z community blog notification and broadcast calendar invitations will be sent closer to our next Q&A session. Again, we appreciate this team's guidance and interactions very much. Please let me know if I may provide additional information. I welcome your add'l feedback on this event, as well as on any other topics you'd like us to cover via this venue. Sincerely, Cecile Day PARMGEN L3/R&D

• 10/07/2015 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from SmartCloud Web Conference log-on: Note: Please let me know if I miss anyone from the attendance list. Thanks.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC) System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-

9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=60fbca38-f84d-4df2-97e5-f37fd18c9042

C. Q&A Details:

• October 7, 2015 Q&A:

Q#1: Question about “OMEGAMON STC dumps when trying to use RKANCMDU” with KCIRPLB1 – E Running KCIPARSE” message.

• A#1: See OMEGAMON Family z/OS 2.2. currency technote (URL: https://www.ibm.com/support/docview.wss?uid=swg21902875). Also cross-referenced in the PARMGEN technote:

Q#2: “Do I need to convert the ICAT Base RTE first to PARMGEN? ”

• A#2: See SMC Blog: "PARMGEN tip: Create or convert a sharing-with-Base RTE and a Base RTE in one streamlined PARMGEN process" (URL: https://www-01.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/qcf11.htm?cp=SSAUBV%2F0-9-0-10) . and see QCF11 Implementation Scenario in Knowledge Center.

Q#3: For table parms. in the WCONFIG(&rte_name) profile, do they have to be placed within the Kpp$ BEGIN/END product indicator or within the Kpp_xx table BEGIN/END indicator?

• A#3: No, the product profile parms. and table profile parms. can be placed anywhere in the user profiles. See WCONFIG($SYSIN) for how $PARSE* job reads the profiles in which ordering sequence. Last one read, values win (LIFO). The only rule about table parms. is to only have one set of Kpp_xx table BEGIN/END WITHIN an RTE profile member (for example, there cannot be multiple KDF_FM BEGIN/KDF_FM END pair of parms. within the same WCONFIG(&rte_name). See also usage of the F16=CLNESECT (clone section) to make it easier to replicate/clone table rows.

Q#4: Is there one place that tracks what versions of the products are configured in each RTE?

• A#4: See WCONFIG($VERSION). PARMGEN supports staged upgrades so this member is based on the versions of the products configured in this RTE's WCONFIG. One can also do a "P" (Product) option next to an RTE on the KCIP@RTE List of RTE panel.

•

Q#5: “We used parmgen in z/os v1r13 and we are just migrating to z/os v2r1... can I just port the

parmgen parms to the new OMEGAMON in v2r1 unchanged?”

• A#5: Yes. If this is an upgrade of the OMEGAMON products, see SMPE04, SMPE05, SMPE06, or SMPE07 scenarios in the IBM Knowledge Center's OMEGAMON XE shared publications to decide how much exploitation will be done to the new features.

Q#6: “Can you update the parmgen profile without rerun all parmgen setup batch jobs?"

• A#6: Yes. If the changes are updates to a few parms. in the WCONFIG LPAR RTE profile or $GBL$USR, and it requires a regeneration of a few runtime members, then one can simply rerun $PARSE or $PARSESV composite job, and the KCIJPW2R job under SUBMIT option to refresh the runtime members from the PARMGEN WK* work libraries to the product execution RK* user libraries. If the changes to the profiles affect product started tasks, etc., then it would be ideal to also run other jobs on the SUBMIT panel (KCIJPALO, KCIJPLOD, etc.

https://www.ibm.com/support/knowledgecenter/SSAUBV/

_________________________________________________________

Cecile Day z/OS OMEGAMON/ITM Install/Config. - Development IBM System z | Office:(720)396-2831 | Tieline:938-2831 (phone) Service Management Connect

"It’s the Easter season all year round, a time of reflection, forgiveness, and reconciliation."

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held September 9, 2015

Hello everyone, Thank you for your attendance of this month's PARMGEN customer open Q&A call and for the valuable feedback. A warm welcome to our new attendees from our existing customer accounts and new accounts! We hope that you found the session useful. We appreciate the ongoing collaboration in this month's call. I have captured the following info. during our webcast ('recap'ed the Q&A portion for reference in the Meeting Minutes: section noted below). We will schedule our next monthly open Q&A call on October 7th. Service Management Connect (SMC) System z community blog notification and broadcast calendar invitations will be sent closer to our next Q&A session. Again, we appreciate this team's guidance and interactions very much. Please let me know if I may provide additional information. I welcome your add'l feedback on this event, as well as on any other topics you'd like us to cover via this venue. Sincerely, Cecile Day PARMGEN L3/R&D

• 09/09/2015 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from SmartCloud Web Conference log-on: Note: Please let me know if I miss anyone from the attendance list. Thanks.

B. Presentation Materials:

The presentation can be downloaded from the following link in SMC) System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=7ba7ce08-da42-4506-b50f-671922e69db9

C. Q&A Details:

• September 9, 2015 Q&A:

Q#1: Question about MAXIMUM() in OMEGAMON XE for DB2 ‘s CUA KD2SYSIN runtime member.

• A#1: See WCONFIG(KD2$PSYS) override imbed and add the MAXIMUM(nnnnnn,X) parm. as provided under L2 or L3 guidance. Making the updates in this member ensures that PARMGEN preserves the updates when $PARSE job recreates WKD2PAR(KD2SYSIN). Shortcut is to add the parm. in RKD2PAR(KD2SYSIN) directly but ensure that WCONFIG(KD2$PSYS) has the updates so when $PARSE job is rerun, PARMGEN is able to preserve the manual edits. Note that WCONFIG($PARSEPR) can be used instead of the composite $PARSE job. $PARSEPR recreates runtime members in xKANPARU, xKD2PAR, and xKD2PRF (PAR-type runtime members). After making the updates, rerun WCONFIG($PARSEPR), then rerun KCIJPW2R job (under SUBMIT panel or directly from WKANSAMU dataset).

Q#2: Question about what to use if site does not use a DNS name for their z/OS hosts (not set up in DNS).

• A#2: See WCONFIG(&rte_name) LPAR profile's *_*_TCP_HOST parms. By default, PARMGEN does an autodiscovery of the IP hostname of the LPAR where you submitted the KCIJPCFG/KCIJPPRF set-up/profile build/refresh jobs. These parameters will default to the actual IP hostname discovered (if RTE is not enabled for variables), or to "&SYSIPHOSTNAME." value for variables RTE. The TCP_HOST parms. can accept the DNS, fully-qualified hostname, or the dotted-decimal format network address (enclose in quotes). The value for the TCP_HOST parms. populate the KDSENV, KppENV, KDCSSITE, etc. runtime members for ITM connectivity (TEMS, Agents).

Q#3: How to apply maintenance with PARMGEN after the initial install is complete.

• A#3: See SMPE maintenance and upgrade scenarios topic in OMEGAMON XE Shared Publications (https//www.ibm.com/support/knowledgecenter/SSAUBV/welcome)

Q#4: During normal RTE maint., why would you have to run the KCIJPCFG job?

• A#4: See answer to Q#3. KCIJPCFG/KCIJPPRF jobs help rebuild the LPAR RTE profile quickly.

_________________________________________________________

Cecile Day z/OS OMEGAMON/ITM Install/Config. - Development IBM System z | Office:(720)396-2831 | Tieline:938-2831 (phone) Service Management Connect "It’s the Easter season all year round, a time of reflection, forgiveness, and reconciliation."

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held July 29, 2015

• 07/29/2015 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from SmartCloud Web Conference log-on: Note: Please let me know if I miss anyone from the attendance list. Thanks.

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held June 24, 2015

• 06/24/2015 Meeting Minutes:

A. Number of Attendees:

Number of Attendees from SmartCloud Web Conference log-on: Note: Please let me know if I miss anyone from the attendance list. Thanks.

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held May 20, 2015

Hello everyone, Thank you for your attendance of this month's PARMGEN customer open Q&A call and for the valuable feedback. A warm welcome also to our new attendees! We appreciate the ongoing collaboration in this month's call. I have captured the following info. during our webcast - 'recapping the Q&A portion for reference in the Meeting Minutes: section noted below. We will schedule our next monthly open Q&A call on June 17th. SMC blog notification and broadcast calendar invitations will be sent closer to our meeting. Again, we appreciate this team's guidance and interactions very much. Please let me know if I may provide additional information. I welcome your add'l feedback on this event, as well as on any other topics you'd like us to cover via this venue.

Have a safe and happy Sincerely, Cecile Day PARMGEN L3/R&D

• 05/20/2015 Meeting Minutes:

A. Number of Attendees:

B. Presentation Materials:

The presentation can be downloaded from the following link in Service Management Connect System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=74f7edf1-96fe-407e-ab4a-e190dafc78c1

C. Q&A Details:

Q#1: How do we change the number of OMXE for DB2 (thread) near term history VSAM dataset (RKD2VSnn)?

• A#1: In the PARMGEN LPAR RTE profile (%RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%)), you can increase the # of VSAM files to use by modifying the KD2_PFnn_HIS_LOGx parameters as shown on lines #4240 - #4276 in the sample LPAR3 RTE below. The default # of VSAMs is 7 (starting in PARMGEN 1Q15 IF UA76016). If an RTE was converted from ICAT to PARMGEN, in ICAT, the historic ICAT default for the KD2_PFnn_HIS_LOGx parms. is 3 VSAMs so the converted RTE batch member into PARMGEN mode will have 3 set-up. To increase, uncomment out the additional LOG4-LOG7 VSAMs accordingly. The enablement flag for OMEGAMON XE for DB2 (thread) NTH is the KD2__PFnn_HIS_START. Enable the flag and customize the COPT&dbid. NTH options accordingly. After customizing the NTH options, rerun the $PARSEPR and $PARSESM jobs to refresh the xKD2PAR/xKD2PRF OMXE DB2 runtime members specific to NTH function. If you kept the default KD2_OMPE_RUNALLOC parm. setting of Y in the WCONFIG RTE profile, this flag automatically submits the ALLOCDS NTH VSAM allocation job, when $PARSE* job spawns the KD2JP* job (CRTDB2*) which creates the DB2-subsystem-specific runtime members (KD2_DBnn_* table) assigned to the DB2 profiles (KD2_PFnn_* table) Pnnn PROFID.

For more information, the OMEGAMON XE for DB2 publication may be found in this link: https://www.ibm.com/support/knowledgecenter/OMXEDB2PE520/com.ibm.omegamon.xe.pe_db2.doc_5.2.0/ko2welcome_pe.htm

Q#2: How are OMXE for DB2 KD2_OMPE_CHECKSYS and KD2_OMPE_USE_MODEL parms. used?

• A#2: These control if you want to designate one RTE to own the DB2 profile features enablement. The KD2_OMPE_USE_MODEL can be set to Y to specify if you want to use this RTE as a model for several LPARs for the DB2 profile features customizable in the KD2_PFnn_* parms. The

KD2_OMPE_CHECKSYS=Y allows you to specify DB2 subsystems in this RTE that run on different LPARs. Specify the respective z/OS system ID (SMFID) for each DB2 subsystem. When you later submit the $PARSE* 'Create DB2 runtime members' job, this configuration job checks on which LPAR it is executed and only generates the runtime members for the configured DB2 subsystems that run on this LPAR. The PARMGEN defaults are shown below in this LPAR3 RTE example (you can also place your cursor on the parameter and press F1 for help).

• If you enable KD2_OMPE_USE_MODEL=Y for this RTE LPAR1, then in the other RTEs that will share the RKD2PRF dataset of LPAR1, customize the other RTE's KD2_OMPE_SHARED_PROFILE_LIB parameter to point back to LPAR1's RTE HLQ + LPAR name, as shown from our LPAR3 example demo'd during the meeting:

• LPAR1 model settings: ISREDDE2 TDITN.FTU.LPAR1.WCONFIG(LPAR1)

Command ===>

003845 KD2_OMPE_CHECKSYS Y * For

xKD2PRF(DB2PROF) *

003846 KD2_OMPE_USE_MODEL N

003847 *KD2_OMPE_SHARED_PROFILE_LIB ""

• LPAR3 sharing-LPAR1's-RKD2PRF settings: VIEW TDITN.FTU.LPAR3.WCONFIG(LPAR3)

Command ===> Scroll

===> CSR

002813 KD2_OMPE_CHECKSYS N * For

xKD2PRF(DB2PROF) *

002814 KD2_OMPE_USE_MODEL Y

002815 KD2_OMPE_SHARED_PROFILE_LIB "TDITN.FTU.LPAR1"

Q#3: What are the migration considerations if I want to use a new PARMGEN global JCL library

for managing my existing RTEs (during PARMGEN processing)?

• A#3: You can stage using a new PARMGEN global JCL library for your existing RTEs by

specifying a new dataset on the "PARAMETER GENERATOR (PARMGEN) WORKFLOW MENU" as shown in the example from our webcast:

•

• If the goal is to carry forward all the RTE definitions and RTE variables profiles from all RTEs originally configured that used the original PARMGEN global dataset (TDITNT.COMMON.PARMGEN.JCL from our example), then one has the option to copy the contents to the new. That way, when one does a switch or list RTEs by placing a "?" on the RTE_NAME field on that panel above, you can manage your original RTEs pointing to the new PARMGEN global JCL library (TDITNT.COMMON.PARMGEN.JCL from our example). KCIDJP02 table in this table is the key member that keeps track of the configured RTE listing. More info. may be found in the SMPE07 scenario URL: https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe_07_clonedenv_upgrade_parmgenref.htm Stage each RTE by reconfiguring each one to reflect that it is now using the new dataset. GBL_USER_JCL parameter is tracked in both the WCONFIG(%RTE_NAME%) LPAR RTE profile (when you do the KCIJPCFG/KCIJPPRF profile refresh step) as well as in WCONFIG($GBL$*). WCONFIG(%RTE_NAME%) takes precedence so follow SMPE02, or SMPE03 scenario when you are staging a new dataset to use.

Q#4: What are the migration considerations if I want to use a new PARMGEN global JCL library for my product started tasks enabled for variables (during product startup)?

• A#4: For RTEs enabled for variables, the PARMGEN global JCL library is the CONFIG

DD in all product started tasks configured. You can stage the switching to the new dataset by ensuring that the new one carries forward the RTE variables profile where system symbol overrides, and any user symbols are defined w/ their resolution values. Then stage the product started tasks accordingly by modifying the CONFIG DD dataset to point to the new one. For more information about variables processing, review one of the QCFnn implementation scenarios that feature RTE variables processing (https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/PARMGEN_scenarios_intro.htm). Other helpful references are "Using

best practice variables in PARMGEN configuration profiles": URL: https://www.ibm.com/support/docview.wss?uid=swg21683976 technote as well as the second lab. scenario featured in the PARMGEN lab. guide attached in Section D2a. InterConnect 2015 PARMGEN Hands-on Lab Guide (Lab 5644) in the master PARMGEN technote in this URL: https://www.ibm.com/support/docview.wss?uid=swg21417935.

Q#5: How do I redirect my standalone Agent running in its own agent address space to point to a different Primary TEMS?

• A#5: Review the Agent's KD5_TEMS_* primary TEMS values in the WCONFIG RTE profile to see what's specified for the Kpp_TEMS_TCP_HOST (IP hostname where the TEMS that this Agent will connect to). By default, if there is a local TEMS being configured in the RTE, the primary TEMS defaults to the local IP hostname (autodiscovered by default). In a variables-enabled RTE, it defaults to &SYSIPHOSTNAME (PARMGEN does a gethostname @ startup unless user overrides what SYSIPHOSTNAME resolves to in the user PARMGEN global JCL RTE variables mbr.). This parameter becomes the CT_CMSLIST in the Agent's RKANPARU(KppENV) file. CT_CMSLIST determines which protocol will be used by the Agent to find the primary TEMS (PIPE first, then SNA by default) - this ordering is determined by the customer via the Kpp_*_COMM_PROTOCOLn and Kpp_*_PORT_NUM parms. If there is no local TEMS being configured in the RTE (CONFIGURE_TEMS_KDS=N and RTE_TEMS_CONFIGURED_FLAG=N), then ensure that you review the related PARMGEN parameters that have dependencies when the flag is N. Check that the Agent's Kpp_TEMS_LOCAL_CONNECT is set to N, then customize the Kpp_TEMS_TCP_HOST, etc. to specify the primary TEMS values that are non-local (on a non-z/OS platform or another LPAR or not configured in the local RTE).

• The next PARMGEN IF will be enhanced to add validation checking that if there is no local TEMS configured in the RTE (customer specified CONFIGURE_TEMS_KDS=N and RTE_TEMS_CONFIGURED_FLAG=N during KCIJPCFG set-up), but the Kpp_TEMS_LOCAL_CONNECT was not overridden to be N (default is Y), then PARMGEN's KCIJPVAL validation job, and the $PARSE* VALIDATE step will flag as an error in the WCONFIG($VALRPT) validation report (prototype validation error report shown below):

_________________________________________________________

Cecile Day z/OS OMEGAMON/ITM Install/Config. - Development IBM System z | Office:(720)396-2831 | Tieline:938-2831 (phone) Service Management Connect "It’s the Easter season all year round, a time of reflection, forgiveness, and reconciliation."

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held April 15, 2015

Hello everyone, Thank you for your attendance of this month's PARMGEN customer open Q&A call. Welcome to our new attendees as well!

A. Number of Attendees:

B. Presentation Materials:

The presentation can be downloaded from the following link in Service Management Connect System z community: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=42997eb7-11f2-45f7-a267-3fc4ef3fdd13 We appreciate the collaboration in this month's call. I have captured the following info. during our webcast - 'recapping the Q&A portion for reference:

C. Q&A Details:

Q#1: Can I use &SYSIPHOSTNAME. and &SYSIPADDRESS. for the PARMGEN LPAR RTE WCONFIG(&rte_name) profile parameter value?

• A#1: Yes, PARMGEN supports 3 types of symbols (#1system symbols (Type 1: ex. &SYSNAME., &SYSCLONE.), #2KCIPARSE-extracted (Type 2: ex. &SYSIPHOSTNAME. and &SYSIPADDRESS.), #3user-defined (Type 3: ex. &KDEB_INTERFACELIST. from today's example). Tip: Submit WCONFIG($PARSEDV) job and view its variables report output in WCONFIG($SYSVAR1). This shows all eligible variables that you can use in your PARMGEN LPAR RTE WCONFIG(&rte_name) profile parameter value. Please refer to "Using best practice variables in PARMGEN configuration profiles":

URL: https://www.ibm.com/support/docview.wss?uid=swg21683976 technote as well as the second lab. scenario featured in the PARMGEN lab. guide attached in Section D2a. InterConnect 2015 PARMGEN Hands-on Lab Guide (Lab 5644) in the master PARMGEN technote in this URL: https://www.ibm.com/support/docview.wss?uid=swg21417935.

Q#2: In ICAT, I specified static values for my RKANPARU(KC5ENV) KDEB_INTERFACELIST=sy9. Once converted to PARMGEN, can this be made a user symbol instead of a static value.

• A#2: Yes, after following QCF11 scenario either in the PARMGEN lab. guide attached in Section D2a. InterConnect 2015 PARMGEN Hands-on Lab Guide (Lab 5644) in the master PARMGEN technote in this URL: https://www.ibm.com/support/docview.wss?uid=swg21417935, you can exploit the best practice user symbols by customizing the LPAR RTE profile (example today is RTE=PLB4SYSA) and replace all the static "sy9" hostname value for to one of the predefined user symbols called KDEB_INTERFACELIST, as shown below. Your PARMGEN global JCL's RTE variables profile (TDITNT.COMMON.PARMGEN.JCL(PLB4SYSA) in today's example, already has KDEB_INTERFACELIST symbol defined to null by default; customize the user symbol to your preferred network interfacelist address which is "sy9" in customer's example)

Q#3: My RKANPARU(KD5ENV) OMXE DB2 Agent's CT_CMSLIST points to IP:PIPE:&SYSIPHOSTNAME. - how do I get the Agent to connect to a different TEMS?

• A#3: Review the Agent's KD5_TEMS_* primary TEMS values to see what's specified for the Kpp_TEMS_TCP_HOST (IP hostname where the TEMS that this Agent will connect to). By default, if

there is a local TEMS being configured in the RTE, the primary TEMS defaults to the local IP hostname (autodiscovered by default). In a variables-enabled RTE, it defaults to &SYSIPHOSTNAME (PARMGEN does a gethostname @ startup unless user overrides what SYSIPHOSTNAME resolves to in the user PARMGEN global JCL RTE variables mbr. In the case below, CT_CMSLIST determines which protocol will be used by the Agent to find the primar TEMS (PIPE first, then UDP then SNA) -this ordering is determined by the customer via the Kpp_*_COMM_PROTOCOLn and Kpp_*_PORT_NUM parms.

Q#4: We currently have a local TEMS configured in the RTE but our Agents configured in the same RTE are connecting to a primary distributed TEMS and a backup distributed TEMS. If I want to follow best-practice and have the z/OS Agents connect to the local z/OS RTEMS configured in the RTE, what parms. do I need to change?

• A#4: For all Agents that run in their own address space, the Kpp_TEMS_LOCAL_CONNECT_FLAG parm. determines if the Agent will report to the local TEMS; the values for CT_CMSLIST connection is based on what's specified for the primary Kpp_TEMS_TCP_HOST and Kpp_TEMS_VTAM_* (if using SNA protocol), and if the backup TEMS feature is enabled, CT_CMSLIST generates a 2nd set for backup TEMS connection based on what's configured in the Kpp_TEMS_BKUP1_* parms. Set the Kpp_TEMS_LOCAL_CONNECT_FLAG back to the default Y value and specify the primary Kpp_TEMS_TCP_HOST values accordingly to point to the local TEMS IP hostname.

Q#5: How does the Agent in Q#4 still find the z/OS local RTEMS if I configured PARMGEN to have

the Agent connect to 2 distributed TEMS for the primary TEMS and backup TEMS values.

• A#5: Check if Agent configured the SNA protocol and if the KppENV Agent's CT_CMSLIST points to SNA values that could be the local RTEMS' local location broker ( KMQ_TEMS_VTAM_APPL_LLB_BROKER parm.value in today's example) -- its a possibility how the Agent is finding the local RTEMS running in the same LPAR.

I thank you once again for the participation this week and for the valuable feedback. We will schedule our next monthly open Q&A call on May 20th. Broadcast calendar invitations will be sent closer to our meeting. For those who also participate in our OMEGAMON Performance Management Suite Early Access Program (EAP), just a reminder that the next PARMGEN EAP is planned for next Thursday, April 23rd @ 10 a.m. US ET We appreciate this team's guidance and interactions very much. Please let me know if I may provide additional information. Also, if you have other suggested topics you want us to cover at the next call, please let me know. Sincerely, Cecile Day PARMGEN R&D

_________________________________________________________

Cecile Day z/OS OMEGAMON/ITM Install/Config. - Development IBM System z | Office:(720)396-2831 | Tieline:938-2831 (phone) Service Management Connect "It’s the Easter season all year round, a time of reflection, forgiveness, and reconciliation."

• Follow-up items from PARMGEN Customer Open Q&A Install/Config. call held March 18, 2015

Hello everyone, Thank you for your attendance of this month's PARMGEN customer open Q&A call.

A. Number of Attendees:

B. Presentation Materials:

The presentation can be downloaded from the following link: URL: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=e6e4b548-0911-42ab-8ae5-1bf9195919c0 We appreciate the collaboration in this month's call. I have captured the following info. during our webcast:

C. Q&A Details:

Q#1. How do I quickly merge the new best-practice user symbols supplied in TKANSAM($MDLVARS) for my existing PARMGEN RTE that is enabled for variables but only using the minimum system variables (&SYSNAME., &SYSCLONE.)?

• A#1. Please refer to "Using best practice variables in PARMGEN configuration profiles": URL: https://www.ibm.com/support/docview.wss?uid=swg21683976 technote as well as the second lab. scenario featured in the PARMGEN lab. guide attached in Section D2a. InterConnect 2015 PARMGEN

Hands-on Lab Guide (Lab 5644) in the master PARMGEN technote in this URL: https://www.ibm.com/support/docview.wss?uid=swg21417935.

In the attached PARMGEN lab guide, three scenarios are supplied to get you acquainted with the PARMGEN Quick Configuration mode (based on the latest PARMGEN 1Q15 IF UA76016): 1.QCF10 Scenario: A sharing-with-SMP/E runtime environment (RTE) contains LPAR-specific libraries and references the read-only target libraries managed by SMP/E. Because an RTE that shares the SMP/E target libraries is updated when the SMP/E maintenance is applied, a sharing-with-SMP/E configuration is good for testing maintenance before other RTEs are updated. Because the RTE contains a hub monitoring server, it can operate by itself and show data right away. However, you do not want this type of RTE in a production environment, because you do not want maintenance to be applied without testing. You can use the IBM-provided RTE model profile @MDLHSS to configure this RTE or you can configure it from scratch. 2.How-to#5 Scenario: This second scenario extends exercise #2 and simulates converting an existing RTE that does not currently use variables to an RTE that leverages system and user variables. 3.QCF11 Scenario: The third 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 the legacy configuration tool, ICAT, are harvested and re-used in PARMGEN. The "How-to#5 Scenario" provides low-level details to answer Q#1 raised during our call. For customers in planning phases of converting from ICAT to PARMGEN and upgrading the versions of the products at the same time, I recommend reviewing QCF11 Scenario lab. scenario also, as this scenario features a number best-practice conversion tips for PARMGEN. It highlights key ICAT->PARMGEN considerations when an RTE is not being upgraded/converted in place (for staged upgrade purposes). I thank you once again for the participation this week and for the valuable feedback. We will schedule our next monthly call on April 15th. Broadcast calendar invitations will be sent closer to our meetings. We appreciate this team's guidance and interactions very much. Sincerely, Cecile Day PARMGEN R&D

_________________________________________________________

Cecile Day z/OS OMEGAMON/ITM Install/Config. - Development IBM System z | Office:(720)396-2831 | Tieline:938-2831 (phone) Service Management Connect "It’s the Easter season all year round, a time of reflection, forgiveness, and reconciliation."