OA49893: CI310 PARMGEN 2Q16 INTERIM FEATURE

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• The following enhancements and issues will be addressed in the
  HKCI310 PARMGEN PTF UA81228 for APAR OA49893:
  1.Enhanced the $PARSE* PARMGEN "Create runtime members"
  composite batch job run elapsed time-to-value savings.
  2.Provided currency support:
  - updated PARMGEN SYSCPUS pop-up panel that displays
  informational message about the number of CPU(s) / system
  hardware on the LPAR that PARMGEN is being executed on.
  Currency:  Added support for new z13s (CPC Type=2965
  Hardware=IBM z13s).
  - updated the PARMGEN KCIJPALO "Allocate runtime read-only (RO)
  and read-write (RW) user datasets" job to accommodate PDSE V1
  requirement when the RTE is enabled for PDSE support
  (RTE_SMS_PDSE_FLAG=Y).  PDSE V2 format requires DFP FMID HZD2vvv
  PTF UA81278/UA81279/UA81280 tracked in DFP APAR OA45431.  For
  more information, please review technote: URL
  http://www.ibm.com/support/docview.wss?uid=swg21984143
  - updated the default value of parameter GBL_HFS_JAVA_DIR1 (for
  global Java bin path) from /usr/lpp/java/J6.0 to
  /usr/lpp/java/J7.1 for new RTE deployments.
  3.Enhanced the RTE_USS_RTEDIR and TKANJAR DDDEF processing by
   providing a runtime version of the installation USS directory.
  4. Provided additional IVP advanced validation checks during
  PARMGEN $PARSE "Create runtime members and jobs" VALIDATE step
  or PARMGEN KCIJPVAL standalone validation job, as follows:
  - Detect a warning if the RTE is enabled for variables to review
  RTE_USS_RTEDIR parameter for more information.  If variables is
  enabled, set the corresponding KDS_KMS_SDA user symbol
  resolution value to 'Y' in the GBL_USER_JCL RTE variables
  profile.
  - Detect an error condition when OMEGAMON XE for DB2 profile
  parameter KD2_DBnn_DB2_PORT_NUM port number is not unique per
  DB2 subsystem.
  - Detect an error condition when required
  KI2_I1nn_CLASSIC_IMS_RESLIB profile table parameter is not
  supplied when configuring OMEGAMON XE for IMS product.
  5. Provided default placeholder parameter support in various
  WCONFIG(Kpp$PENV) imbeds to the xKANPARU(KppENV)
  environment runtime members:
  - KDS_USERS_NO_MSGLOG=SRVR01,sysadmin in TEMS KDS$PENV
  - *KDS_USERS_NO_MSGLOG=&KDS_USERS_NO_MSGLOG. in TEMS KDS$PENV
  - *KOE_ALLOW_ANY_UID=1 in TEMS KDS$PENV
  - *KOE_ALLOW_ANY_UID=&KOE_ALLOW_ANY_UID. in TEMS KDS$PENV
  - *KOE_ALLOW_UNDEFINED=1 in TEMS KDS$PENV
  - *KOE_ALLOW_UNDEFINED=&KOE_ALLOW_UNDEFINED. in TEMS KDS$PENV
  - *KM5ZIIPOFFLOAD=NO in TEMS KDS$PENV
  - *KM5ZIIPOFFLOAD=&KM5_KM5ZIIPOFFLOAD. in TEMS KDS$PENV
  6. Provided additional &gbl_target_hilev.TKANSAM(*MDL*)
  predefined RTE models to quickly deploy other types of RTEs and
  product combination (QCF21, QCF22).
  7. Enhanced "Set up/Refresh PARMGEN work environment" KCIJPCFG
  processing for brand new, first-time-user of PARMGEN in a new
  LPAR, by defaulting the IBM-supplied jobcard to include the
  user's accounting information (ZACCTNUM) if available on the
  system.
  8. Enhanced panel and on-line help panel updates to aid in
  deployment:
  o Enhanced the main PARMGEN "Welcome to the z/OS Installation
  and Configuration Tools for z Systems Management Suites" by
  streamlining the configuration workflow option to display a
  streamlined "Configuration Workflow (Post-installation):
  Configure z/OS products with Parameter Generator Workflow
  (PARMGEN)" selection only, rather than providing 2 modes
  (recommended Quick Configuration mode and the alternate Standard
  Configuration mode).  The welcome menu now only features the
  recommended Quick Configuration for simplicity.  Press F1=Help
  for more information about the streamlining of the panel
  options.
  o Enhanced the "R" option on the "KCIPQPGB  PARAMETER GENERATOR
  (PARMGEN) WORKFLOW - PRIMARY OPTION MENU" panel by clarifying
  the option name as "R   Create next RTE - Reset fields" and
  navigating the user automatically to the "KCIPQPGA PARAMETER
  GENERATOR (PARMGEN) WORKFLOW MENU" panel to supply the RTE name
  of the next RTE to create or clone from an existing RTE.
  o Added F1=HELP profile parameter on-line help text support for
  additional parameters in these prefixes:
  " GBL_* global profile parameters in WCONFIG($GBL*)
  " RTE_* common LPAR profile parameters in WCONFIG(%RTE_NAME%)
  " KDS_X_* TEMS profile parameters in WCONFIG(%RTE_NAME%)
  " Kpp_X_* common Agent profile parameters in WCONFIG(%RTE_NAME%)
  o Enhanced the "F16=CLNESECT CLONE SECTION" KCIP@PM2 panel to
  provide better examples and provide a complete list of Kpp
  product table profile parameters that can be cloned.  A new
  corresponding help panel was also provided.
  o Enhanced the "IMPORTANT - REFRESH THE LPAR RTE USER AND IBM
  PROFILES" KCIP@BAK panel to provide a default backup LPAR RTE
  profile name to the "%RTE_NAME% Backup member name" field that
  gets stored in the WCONBACK backup LPAR RTE profile dataset when
  refreshing the RTE profile via the KCIJPPRF LPAR RTE user
  profile job.
  o Updated existing help topics focusing on additional system
  preparation requirements for products that have USS SMP/E and
  configuration deployment requirements when SDA is enabled and
  for products that update their TKANJAR DD jar files.
  o Added help topics focusing on PARMGEN utilities such as PF
  Keys and macros such as XF "EXCLUDE FIND" and KCIRMVCP
  MOVE/COPY/ALLOCATE dataset/members macros, and PF Keys such as
  F1=PARMHELP / F15=HIDECMNT / F16=CLNESECT             (F1 to
  view parameter on-line help, F15 to hide profile comments, and
  F16 to clone parameter section for a table row).
  
  B. PARMGEN-supported Application Configuration
  Enhancements/Updates:
  1. Tivoli Management Services:Engine infrastructure common to
  TEMS and Agents:
  o (TEMS) Provided configuration support for a new
  KDS_X_HUB_CMS_FTO_FLAG profile parameter which generates the
  CMS_FTO=%KDS_X_HUB_CMS_FTO_FLAG% parameter in the TEMS
  xKANPARU(KDSENV) runtime member.  KDS_X_HUB_* parameters are
  applicable to a z/OS Remote TEMS based on these scenarios:
  " z/OS Remote TEMS connecting to a non-z/OS Hub TEMS enabled
  with the Hot Standby (FTO) feature.
  " z/OS Remote TEMS connecting to a z/OS High Availability (HA)
  Hub TEMS (Primary TEMS) and a z/OS HA Hub TEMS (Standby TEMS).
  o (TEMS) Enabled "KDS_USERS_NO_MSGLOG=SRVR01,sysadmin" parameter
  by default in the TEMS WCONFIG(KDS$PENV) imbed to
  xKANPARU(KDSENV) TEMS environmental runtime member.   The
  KDS_USERS_NO_MSGLOG=&userid parameter is used to suppress the
  z/OS TEMS RKLVLOG DD messages if the &userid TMS component is
  contained in a list. The list is provided by KDS_USERS_NO_MSGLOG
  KDSENV variable that the customer can modify as needed.  When
  any IBM Tivoli Monitoring component does a logon or a logoff to
  the z/OS TEMS, the respective KDSMA009 and KDSMA011 messages are
  recorded in RKLVLOG MSG2/Operation log file.  There can be use
  cases that result in large numbers of these KDSMA009 and
  KDSMA011messages being recorded to RKLVLOG output.  The large
  volumes of KDSMA009 and KDSMA011 messages result in excessive
  growth of RKLVLOG.  Usage of KDS_USERS_NO_MSGLOG provides an
  ideal solution in that we should still be able to see these
  messages in most cases while suppressing the messages for
  "userids" that generate excessive numbers.  Refer to FMID
  HKDS630 APAR OA45650 for more information.
  o (TEMS) Enhanced the existing WCONFIG(KDS$SDMP) for the TEMS
  SYS%DUMP DD imbed to the started task to default the DDNAME to
  an enabled SYSMDUMP DD instead of SYSUDUMP DD.  KCIJPALO job now
  allocates the SYSMDUMP dataset by default.  Having a
  readily-available SYSMDUMP sequential dataset is more useful for
  debugging as the output can be processed using IPCS, or other
  tools.  Each STC requires a unique SYSMDUMP dataset.
  o (Persistent Datastore common to TEMS and Agents) Enhanced
  persistent datastore processing by ensuring that the
  %RTE_PDS_HILEV%.KPDCTLL sequential file is allocated as DISP=OLD
  to secure the next backup file number to accommodate multiple
  %RTE_PDS_KPDPROC_PREFIX%1 maintenance procedures concurrently
  running spawned from TEMS or Agent started tasks collecting PDS
  history data of which PDS sequential datasets
  need maintenance.
  
  2. IBM OMEGAMON Monitoring for JVM V5.3.0:
  o Updated the product's post-configuration README to:
  " add a step documenting how to monitor a JVM running in a DB2
  stored procedure.
  " add a step to refresh jar files after SMP/E maintenance by
  rerunning the KCIJPUSS job.
  " add an optional step to enable %KJJ_COLLECTOR_STC% JTCOLL
  Collector trace options.
  o Added a new WCONFIG(KJJ$SDMP) SYS%DUMP DD imbed to the
  OMEGAMON Monitoring for JVM Agent's started task.  KCIJPALO job
  allocates the SYSMDUMP dataset by default.  Having a
  readily-available SYSMDUMP sequential dataset is more useful for
  debugging as the output can be processed using IPCS, or other
  tools.  Each STC requires a unique SYSMDUMP dataset.  If
  overriding the default, a placeholder SYSUDUMP DD pointing to
  spool datasets is also provided as an example, if you prefer to
  store the data in the spool, instead of the default SYSMDUMP
  sequential dataset.  If you wish to have a SYSUDUMP DD instead
  of SYSMDUMP DD, modify the DDs accordingly.  SYSMDUMP DD and
  SYSUDUMP DD are mutually      exclusive.
  
  3. OMEGAMON Enhanced 3270 User Interface V7.3.0:
  o Added a new WCONFIG(KOB$SDMP) for OMEGAMON enhanced 3270UI
  SYS%DUMP DD imbed to the TOM started task.  KCIJPALO job
  allocates the SYSMDUMP dataset by default.  Having a
  readily-available SYSMDUMP sequential dataset is more useful for
  debugging as the output can be processed using IPCS, or other
  tools.  Each STC requires a unique SYSMDUMP dataset.  If
  overriding the default, a placeholder SYSUDUMP DD pointing to
  spool datasets is also provided as an example, if you prefer to
  store the data in the spool, instead of the default SYSMDUMP
  sequential dataset.  If you wish to have a SYSUDUMP DD instead
  of SYSMDUMP DD, modify the DDs accordingly.  SYSMDUMP DD and
  SYSUDUMP DD are mutually exclusive.
  
  4. OMEGAMON Subsystem V7.3.0:
  o Added a new WCONFIG(KCN$SDMP) for OMEGAMON Subsystem SYS%DUMP
  DD imbed to the started task.  KCIJPALO job allocates the
  SYSMDUMP dataset by default.  Having a readily-available
  SYSMDUMP sequential dataset is more useful for debugging as the
  output can be processed using IPCS, or other tools.  Each STC
  requires a unique SYSMDUMP dataset.  If overriding the default,
  a placeholder SYSUDUMP DD pointing to spool datasets is also
  provided as an example, if you prefer to store the data in the
  spool, instead of the default SYSMDUMP sequential dataset.  If
  you wish to have a SYSUDUMP DD instead of SYSMDUMP DD, modify
  the DDs accordingly.  SYSMDUMP DD and SYSUDUMP DD are mutually
  exclusive.
  o Modified the OMEGAMON Subsystem default STC PROC symbols to
  better accommodate enablement of the optional
  RST=',RESTART=FORCE' keyword.   STC PROC symbols UMAX and FSCR
  are now enabled via internal code default, which is sufficient
  for OMEGAMON Subsystem usage.
  
  5. OMEGAMON XE on z/OS V5.3.0:
  o Updated dynamic ICSF configuration support for new KM5CSFSX
  ICSF monitoring module in lieu of KM5EXIT4 module to support
  FMID HKM5530 APAR OA50548 IF changes.
  o Added placeholder parameter support for the following
  parameters in the WCONFIG(KDS$PENV) imbed to the TEMS
  xKANPARU(KDSENV) environmental file, which is read at TEMS STC
  startup (OMXE on z/OS Agent runs in the TEMS address space):
  " *KOE_ALLOW_ANY_UID=1
  " *KOE_ALLOW_ANY_UID=&KOE_ALLOW_ANY_UID.
  " *KOE_ALLOW_UNDEFINED=1
  " *KOE_ALLOW_UNDEFINED=&KOE_ALLOW_UNDEFINED.
  " *KM5ZIIPOFFLOAD=NO
  " *KM5ZIIPOFFLOAD=&KM5_KM5ZIIPOFFLOAD.
  
  6. OMEGAMON XE for DB2 PE/PM V5.3.0:
  o Removed obsolete profile parameters as their value are not
  used in PARMGEN when generating the KD2VTP virtual terminal pool
  startup runtime member in the RTE's RKANCMDU dataset (standard
  KD2_CUA_VTAM_VTPOOL_PREFIX is used instead to simplify the
  VTPOOL APPLID generation starting in 01 range thru
  %KD2_CUA_VTAM_VTPOOL_NUM% number) :
  " KD2_CUA_VTAM_VTRM_APPL_LENGTH
  " KD2_CUA_VTAM_VTRM_SUFFIX
  
  7. OMEGAMON XE for Messaging (WebSphere MQ Monitoring) V7.3.0:
  o Increased the default KMQ_PD_CYL persistent datastore cylinder
  size profile parameter from 120 to 300 cylinders so the
  composite PARMGEN KCIJPALO "Allocate runtime RO and RW datasets"
  job or the KMQJPALP KMQ Agent's standalone PDS allocation job
  allocates enough space for the default 6
  %RTE_PDS_HILEV%.RKMQPDSn persistent datastore sequential files
  for history storage (for both the TEPS ITM PDS history
  collection and for OMEGAMON enhanced 3270UI near-term history).
  300 cylinder size default is divided to accommodate the default
  6 PDS files to collect data for KMQPDICT GROUP=RKMQDAT tables.
  o Provided configuration support for message monitoring summary
  enhancement in order to support the security checking for
  situations.  Refer to HKMQ730 Fix pack 2 (FP2) APAR OA50601 for
  more information.
  " KMQ_MSG_GROUP_MSGSITMON          ""    * YES, NO, STATONLY
  " KMQ_MSG_GROUP_MSGSITACCOUNT ""   * MQAGENT, USER=<&userid>
  " KMQ_MSG_QACCESS_MSGSITMON      ""   * YES, NO, STATONLY
  " KMQ_MSG_QACCESS_MSGSITACCOUNT "" * MQAGENT, USER=<&userid>
  " KMQ_MSG_QACCESS_IS_DEFAULT     NO    * YES, NO
  o Updated the KMQDFINL post-configuration on-line README to add
  a new "Grant authorities to WebSphere MQ Monitoring and
  WebSphere MQ Configuration Agents" post-configuration step.
  
  8. OMEGAMON XE for Messaging (WebSphere Message Broker
  Monitoring a.k.a. IBM Integration Bus [IIB]) V7.3.0:
  o Increased the default KQI_PD_CYL persistent datastore cylinder
  size profile parameter from 178 to 250 cylinders so the
  composite PARMGEN KCIJPALO "Allocate runtime RO and RW datasets"
  job or the KQIJPALP KQI Agent's standalone PDS allocation job
  allocates enough space for the default 6
  %RTE_PDS_HILEV%.RKQIPDSn persistent datastore sequential files
  for history storage (for both the TEPS ITM PDS history
  post-configuration step.oker Monitoring Agent parameters"
  

Local fix

• Issue#1:
  Symptom: $PARSE or $PARSESV job's VALIDATE step gets a RC=12
  when OMEGAMON XE for DB2's KD2_OMPE_DSHLQ or KD2_OMPE_VSAM_DSHLQ
  LPAR RTE profile parameter is overridden to specify one-node
  high-level qualifier:
  72 +++   xhlq = Substr(cf.KD2_OMPE_DSHLQ,1,ppos-1)
  Error running KRTREXIT, line 72: Incorrect call to routine
    1041 +++    CALL KRTREXIT
    1041 +++   INTERPRET "CALL" exit_name
      85 +++ CALL DRIVE_PARM_EXITS
  Error running KCIRPLBV, line 1041: Incorrect call to routine
  
  Workaround: Apply the 2Q16A PTF (APAR OA49893) when available.
  In the interim, you have the option to implement the following
  workaround:
  1. Backup &gbl_target_hilev.TKANCUS(KRTREXIT) validation REXX
  exec.
  2. Modify the following lines to add the "I -" inserted lines
  and deleting the "D -" old deleted lines, as shown below:
  000087 If cf.KD2_OMPE_DSHLQ <>
  '' Then Do
  000088 ppos = Lastpos('.',cf.KD2_OMPE_DSHLQ)
  000089  I -    xhlq = cf.KD2_OMPE_DSHLQ
  000090  I -    If ppos > 0 Then xhlq =
  Substr(cf.KD2_OMPE_DSHLQ,1,ppos-1)
  000091  D -    xhlq = Substr(cf.KD2_OMPE_DSHLQ,1,ppos-1)
  .
  000103      If cf.KD2_OMPE_VSAM_DSHLQ <> '' Then Do
  000104         ppos = Lastpos('.',cf.KD2_OMPE_VSAM_DSHLQ)
  000105  I -    xhlq = cf.KD2_OMPE_VSAM_DSHLQ
  000106  I -    If ppos > 0 Then xhlq =
  Substr(cf.KD2_OMPE_VSAM_DSHLQ,1,ppos-1)
  000107  D -    xhlq = Substr(cf.KD2_OMPE_VSAM_DSHLQ,1,ppos-1)
  00108         If xhlq <> cf.RTE_VSAM_HILEV Then Do
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All PARMGEN configuration tool users.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: This is PARMGEN 2Q16A IF support.       *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF.                               *
  This is PARMGEN 2Q16A IF support.
  

Problem conclusion

Temporary fix

Comments

• This is PARMGEN 2Q16 Interim Feature (IF) support.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UA81228

Modules/Macros

• KCIPRMLB KDSPRMLB
  

Fix information

• Fixed component name

  PARMGEN ICAT CO

• Fixed component ID

  5608A41CC

Applicable component levels

• R310 PSY UA81228

     UP16/07/14 P F607

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.