A fix is available
APAR status
Closed as new function.
Error description
Implement KOBSUPDT OMEGAMON security standardization of where the KppSUPDI command table exits can be maintained for user customizations so the composite KCIJPSEC security job can take advantage of using the common RTE_X_SECURITY_EXIT_LIB as the standard user exit library. See PARMGEN technote FAQ#37 (https://www-304.ibm.com/support/docview.wss?uid=swg21417935) for more information. Additional information from the master PARMGEN technote's "What's New in 1Q13A" section: RFE: Provide PARMGEN Workflow UI improvements for: A. PARMGEN Configuration Framework Enhancements/Updates: Implement KOBSUPDT OMEGAMON security standardization (Phase 2) of where the KppSUPDI (KOCSUPDI, KO2SUPDI, KOISUPDI, and KOMSUPDI) Classic command table exits can be maintained for user customizations so the composite KCIJPSEC security job can take advantage of using the common RTE_X_SECURITY_EXIT_LIB as the standard security user exit library. In Phase 2, the security exits maintained in the RTE_X_SECURITY_EXIT_LIB library will now be automatically presented in ISPF EDIT mode if user has further customizations he wants to make to the exits, prior to PARMGEN's presenting the composite KCIJPSEC security job for submission. ØBenefit: Reduce the post-configuration security steps and give customers one place to lock-down the security exits. Provide additional global RTE options on the KCIJPCFG panels to create a more-tailored, out-of-the box PARMGEN CONFIG profiles. ØBenefit: For first-time users, one has less parameters to customize in the profile (added 490 parameters already tailored automatically out of the box, if you have all the products configured). Support a more automated PARMGEN RTE CONFIG profile refresh mechanism when common and/or global RTE configuration values are modified after initial deployment. Provide the option to refresh the PARMGEN user profiles (RTE and $GBL$USR) automatically when any global RTE values, configured product mix, etc. on the KCIJPCFG panels, are changed. ØBenefit: Reduce the profile refresh steps from 4 PARMGEN steps to 1 automated KCIJPCFG/KCIJPPRF job. In reconfiguring a System Variables-enabled RTE (RTE_SYSV_SYSVAR_FLAG=Y) that has local override for system symbols (RTE_X_SYSV_OVERRIDE_SYMBOLS=Y), submit the WKANSAMU(KCIJVUPV) job automatically when re-running the WCONFIG($PARSESV) job. ØBenefit: For ease of use, variable-named runtime members that could symbolics (*_STC started tasks, *_VTAM_NODE, etc.) are now created automatically in one job ($PARSESV) as opposed to running $PARSESV and running KCIJVUPV job, as this enhancement will detect if the local override flag is set in order to resolve the symbolics in the variable-named runtime members. Enhance KCIJPMC1/KCIJPMC2 merge LPAR profile values job to automatically use the higher values when TMS:Engine TEMS or Agent storage default values change. ØBenefit: Reduce reconfiguration requirements when required storage values change for a TEMS or Agent, and automating the KCIJPMCn merge profile processing to use the higher value reduces the exposure of any TMS:Engine started task to encounter storage quiesce startup issues. Enhance the library-specific $PARSE jobs ($PARSEPR IK*->WK* PAR*/PRF*-related "Create runtime members" job / $PARSESM IK*->WK* SAM-related "Create runtime members" job to remove IEBUPDTE steps when RTE is not enabled for System Variables. ØBenefit: File-tailoring the $PARSEPR and $PARSESM jobs to not include the IEBUPDTE-related steps of variable-named runtime members that could point to symbolic values, avoids generating a RC=4 when the job is submitted for a System Variables-enabled RTE. Enhance KCIJPSYS system set-up job to provide customer the option to include Health Check-related steps. ØBenefit: If the Health Check-related members for APF and STC will not be used, allowing the option to null out the "GBL_DSN_HZSPROC_LOADLIB" parameter generates a streamlined KCIJPSYS job without the extra COPYH* steps generated that will not be used. Provide a new KCIJPB2R/KCIJVB2R (if System Variables is enabled) fallback IEBCOPY job in WKANSAMU. This job copies the %RTE_HILEV%.%RTE_NAME%.RK*.%CLONE% backup RK* production user libraries (RKANCMDU, RKANPARU, RKANSAMU, RKD2PAR, RKD2PRF and RKD2SAM %CLONE% copies) back into the product execution user libraries (RK*). ØBenefit: If the backup libraries RK* user libraries need to be restored back to the versions prior to running the KCIJPW2R WK*-->RK* user libraries deployment job, you have a readily available job to do the restore. Provide a new KCIJVRSV System Variables resolver/wrapper job in WKANSAMU. Use this generic job to resolve any PARMGEN jobs that contain symbolics. Specify the "JB2RESLV" value to resolve and and send the job through the internal reader (INTRDR). This job is applicable to generated jobs for System Variables-enabled RTEs ("RTE_SYSV_SYSVAR_FLAG" parameter in WCONFIG(%RTE_NAME%) LPAR profile is set to "Y"). ØBenefit: The KCIJVRSV System Variables resolver job can be used for any of the special product standalone jobs that copy globals, allocate product-specific datasets, etc. Provide SMS support for KCIJPIVP job's %RTE_PLIB_HILEV%.%RTE_NAME%.WSUPERC sequential SUPERC dataset allocation based on RTE_SMS_* parameter values specified by customer in the WCONFIG LPAR profile, instead of inheriting the SMS values for the %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG library. ØBenefit: If SMS site values change, KCIJPIVP processing will always use the latest specified values in the event that volume requirements have changed since WCONFIG library was initially allocated. Present the WCONFIG($IVPRPT) automatically upon selection of the "10S" KCIJPIVP job step status on the "SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP" KCIP@SUB panel. ØBenefit: For ease of use, one has easier access to viewing the output of the KCIJPIVP configuration IVP job. ===END "Sub-section: A. 1Q13A RFEs>>A. Configuration Framework Enhancements/Updates:" B. PARMGEN-supported Application Configuration Enhancements/Updates: Tivoli Enterprise Monitoring Server (TEMS) and OMEGAMON Enhanced 3270UI: Support a benign, placeholder UKANDATV DDNAME in the TEMS started task (KDS_TEMS_STC = CANSDSST by default) for any future TEMS and Agent function exploitation. ØBenefit: Generating the started task with a benign UKANDATV DDNAME as preparation for any future functions, avoids having to recycle the TEMS to add a will-be required DDNAME. OMEGAMON Enhanced 3270UI: Support a benign, placeholder UKANDATV DDNAME in the Tivoli OMEGAMON Manager (TOM) started task (KOB_TOM_STC = CANSTOM by default) for future Agent function exploitation. ØBenefit: Generating the started task with a benign UKANDATV DDNAME as preparation for any future functions, avoids having to recycle the TOM to add a will-be required DDNAME. Common Agent configuration: Support a benign, placeholder UKANDATV DDNAME in all Agent started tasks (Kpp_AGT_STC = CANSpp by default) for any future Agent function exploitation. ØBenefit: Generating the started task with a benign UKANDATV DDNAME as preparation for any future functions, avoids having to recycle the Agent to add a will-be required DDNAME. OMEGAMON XE for Mainframe Networks V4.2.0 and higher versions: Provide support for generating the SYSTCPD DDNAME as an optional DD in the N3 Agent started task (KN3_AGT_STC = CANSN3 by default). ØBenefit: If the CANSN3 Agent does not require the SYSTCPD DD for connection, one may null out (clear out) the "GBL_DSN_TCP_SYSTCPD_TCPDATA_MFN" parameter in the WCONFIG($GBL$USR) so the PARMGEN $PARSE or $PARSESV "Create runtime members and deployment jobs" job creates the WKANSAMU(CANSN3) proc already tailored instead of updating the STC manually outside PARMGEN or ICAT controls. In ICAT, the SYSTCPD DD is not optional. OMEGAMON XE for Messaging V7.0.0 and higher versions: Enhance the RKANDATV(KQIXML) PARMGEN KCIJPUSP USS set-up job processing by supporting a new WCONFIG(KQI$XML) override imbed to accommodate additonal MonitorBroker entries. WCONFIG(KQI$XML) imbed is ideal for customizing additional broker entries as the current KQIXML template only allows for one instance. ØBenefit: Reduce the manual editing of RKANDATV(KQIXML) post-configuration by providing support for multiple broker lines as part of the PARMGEN configuration process, thus preventing overlaying user-customizations made to RKANDATV(KQIXML) outside configuration controls. OMEGAMON XE for Messaging V7.0.0 and higher versions: Increase the KMC_AGT_STORAGE_MINIMUM_EXTEND and KMQ_AGT_STORAGE_MINIMUM_EXTEND configuration default to 300000 instead of 256000, in support of Self Describing Agent (SDA) functionality and other Agent new functions. Both parameters are used in the OMEGAMON XE for Messaging's KMC/KMQ Agent's xKANPARU(KppSYSIN) MINIMUM(%Kpp_AGT_STORAGE_MINIMUM_EXTEND%,X) parameter. Existing PARMGEN RTE profile values for these respective parameters are preserved so if you want to start using the new configuration default, modify the WCONFIG LPAR profile parameter prior to rerunning the $PARSE or $PARSESV job. OMEGAMON XE for DB2 PE/PM V5.1.1: Support new IBM InfoSphere Optim Performance Manager-related LPAR profile parameters as follows: SPMON=%KD2_PFnn_READA_SPMON%, RACOPSIZE=%KD2_PFnn_READA_OPBUFSIZE% and RACOPTHRSHLD=%KD2_PFnn_READA_OPBUFTHR% (SPMON=N, RACOPSIZE=16, and RACOPTHRSHLD=6 default) in the xKD2PAR(OMPE&dbid) runtime member. For more information, please refer to the Techdoc link: http://www-01.ibm.com/support/docview.wss?uid=swg27035964. OMEGAMON XE for DB2 PE/PM V5.1.0 and higher versions: Provide EXC0&profid/EXC0&dbid "Create EXPLAIN views for subsystems of DB2 V10 - Compatibility Mode" and EXC1&profid/EXC1&dbid "Create EXPLAIN views for subsystems of DB2 V10 - New Function Mode" jobs. ===END "Sub-section: A. 1Q13A RFEs>>B. Application Configuration Enhancements/Updates:" ===END "Sub-section: A. 1Q13A RFEs" ================================================================
Local fix
See master PARMGEN technote https://www-304.ibm.com/support/docview.wss?uid=swg21417935 FAQ#37. ================================================================ ====== SYMPTOM: The KCIJPSYS system copy job gets a RC=4 when trying to IEBCOPY the OMEGAMON XE for Messaging started task ("CANSMQ" default) to the system procedure library, but the CANSMQ started task does not exist in WKANSAMU library. DESCRIPTION: The KCIJPSYS system copy job needs to check if the OMEGAMON XE for Messaging components (OMXE for MQ Configuration [KMC] / OMXE for MQ Monitoring [KMQ]) are sharing an address space in the following parameters: ** Values that describe the address space: KMC_AGT_STC CANSMC ** (Optional) Shared address space with KMQ Agent: ** If the KMC Agent is running in the KMQ started task (address space ** owner), specify the KMQ Agent started task name on the ** "KMC_AGT_STC_OWNER" parameter. This parameter is only valid when the ** KMC_AGT_CONFIG field is set to "STANDALONE", and is mutually ** exclusive with KMC_AGT_STC parameter. KMC_AGT_STC_OWNER "" ** Values that describe the address space: **KMQ_AGT_STC "CANSMQ" ** (Optional) Shared address space with KMC Agent: ** If the KMQ Agent is running in the KMC started task (address space ** owner), specify the KMC Agent started task name on the ** "KMQ_AGT_STC_OWNER" parameter. This parameter is only valid when the ** KMQ_AGT_CONFIG field is set to "STANDALONE", and is mutually ** exclusive with KMQ_AGT_STC parameter. KMQ_AGT_STC_OWNER CANSMC WORKAROUND/TIP: : Apply the resolving 1Q13A HKCI310 PTF UA67787 (APAR OA40649) when available. In the interim, the KCIJPSYS job's RC=4 warning does not prevent the job from running, but if you want a RC=0 in the KCIJPSYS job, you can choose to comment out the IEBCOPY step that copies CANSMQ started task. ================================================================ SYMPTOM: The OMEGAMON XE for DB2 PE/PM Classic VTAM major node is using the incorrect Virtual Terminal (VTPOOL) prefix for the OMEGAMON XE for DB2 PE/PM Classic VTAM major node VTPOOL APPLIDs. DESCRIPTION: The OMEGAMON XE for DB2 PE/PM Classic VTAM major node (KD2_CUA_VTAM_NODE = CTDD2N1 default) is using the incorrect Virtual Terminal (VTPOOL) prefix for the VTPOOL APPLIDs. KD2_CUA_VTAM_VTPOOL_PREFIX PARMGEN LPAR profile parameter value should be used instead of what is currently being used (KD2_CUA_VTAM_APPL_PREFIX parameter value). WORKAROUND/TIP: : Apply the resolving 1Q13A HKCI310 PTF UA67787 (APAR OA40649) when available. In the interim, one may choose to supply the same value for both the KD2_CUA_VTAM_VTPOOL_PREFIX and KD2_CUA_VTAM_APPL_PREFIX VTAM APPLID prefix parameters so when $PARSE or $PARSESV/KCIJVUPV jobs create the OMEGAMON XE for DB2 PE/PM Classic VTAM major node, the VTPOOL APPLIDs will use the correct prefix. ============================================================= SYMPTOM: The KCIJPVAL validation job or $PARSE VALIDATE step gets a RC=8 and in the WCONFIG($VALRPT) validation report, Section 1 logs "KD2_OMPE_TCPIP_NAME &CNMTCPN. Length must be <= 8" when creating a brand new PARMGEN RTE that configures the OMEGAMON XE for DB2 PE/PM product. DESCRIPTION: The PARMGEN KCIJPUP1 "Update interim libraries and create profiles" job typically autodiscovers system variables for a number of LPAR profile parameters that use system variables like &SYSNAME., &SYSPLEX., &SYSIPHOSTNAME., &SYSVTAMNETID., etc. In cases where &CNMTCPN. TCP/IP started task symbol is not defined, the PARMGEN LPAR profile's "KD2_OMPE_TCPIP_NAME" parameter value remains to be a symbolic and this does not pass the $PARSE validation step if System Variables is not enabled in an RTE (RTE_SYSV_SYSVAR_FLAG=Y). WORKAROUND/TIP: : Apply the resolving 1Q13A HKCI310 PTF UA67787 (APAR OA40649) when available. For the timebeing, modify the WCONFIG(%RTE_NAME%) LPAR profile to change the KD2_OMPE_TCPIP_NAME parameter value from "&CNMTCPNM." to the actual TCP/IP started task name (for example, "TCPIP"). Then proceed rerunning the KCIJPVAL job or the $PARSE job. ============================================================== SYMPTOM: Product started tasks are generated with a "/*JOBPARM" line in the header if your WCONFIG($JOBCARD) contains a "/*JOBPARM" statement. DESCRIPTION: The WCONFIG(KCI$SST1) started task header automatically imbeds a commented out version of your jobcard called WCONFIG(@JOBCARD). KCIJPUP1 job creates @JOBCARD from your WCONFIG($JOBCARD) but only comments out lines that start with "//" to replace with "//*" comment lines. The KCIJPUP1 job needs to modify creating WCONFIG(@JOBCARD) by searching for lines with "/*" starting on column 1. WORKAROUND/TIP: : Apply the resolving 1Q13A HKCI310 PTF UA67787 (APAR OA40649) when available. In the interim, edit the WCONFIG(KCI$SST1) started task imbed to remove the following "%IMBED%=WCONFIG:@JOBCARD" line on line#18 so that when $PARSE job imbeds this member in creating the product started tasks, it does not include the @JOBCARD that has the "/*" line. 000012 //* **************************************************************** * 000013 //* USER SECTION: Edit WCONFIG(KCI$SST1) to customize user 000014 //* accounting details accordingly. 000015 //* ****************************************************************
Problem summary
**************************************************************** * USERS AFFECTED: All PARMGEN configuration users. * **************************************************************** * PROBLEM DESCRIPTION: Implement KOBSUPDT OMEGAMON security * * standardization of where the KppSUPDI * * command table exits can be maintained * * for user customizations so the * * composite KCIJPSEC security job can * * take advantage of using the common * * RTE_X_SECURITY_EXIT_LIB as the * * standard user exit library. See * * PARMGEN technote FAQ#37 * * (https://www-304.ibm.com/support/docvie * * w.wss?uid=swg21417935) for more * * information. * **************************************************************** * RECOMMENDATION: Apply the PTF. * Implement KOBSUPDT OMEGAMON security standardization of where the KppSUPDI command table exits can be maintained for user customizations so the composite KCIJPSEC security job can take advantage of using the common RTE_X_SECURITY_EXIT_LIB as the standard user exit library. See PARMGEN technote FAQ#37 (https://www-304.ibm.com/support/docview.wss?uid=swg21417935) for more information.
Problem conclusion
Temporary fix
Comments
1. Provide PARMGEN Workflow UI improvements for PARMGEN Configuration Framework Enhancement/Updates: - (Part 2) Implement KOBSUPDT OMEGAMON security standardization of where the KppSUPDI command table exits can be maintained for user customizations so the composite KCIJPSEC security job can take advantage of using the common security exit library. In Phase 2, the security exits maintained in the RTE_X_SECURITY_EXIT_LIB library will now be automatically presented in ISPF EDIT mode, prior to PARMGEN's presenting the composite KCIJPSEC security job. Benefit: Reduce the post-configuration security steps and give customers one place to lock-down the security exits. - Provide additional global RTE options on the KCIJPCFG panels to create a more-tailored, out-of-the box PARMGEN CONFIG profiles. Benefit: For first-time users, less parameters to customize in the profile (added 490 parameters already tailored). - Support a more automated PARMGEN RTE CONFIG profile refresh mechanism when common and/or global RTE configuration values are modified after initial deployment. Benefit: Reduce the profile refresh steps from 4 PARMGEN steps to 1 automated job (new KCIJPPRF job). - In reconfiguring a System Variables-enabled RTE (RTE_SYSV_SYSVAR_FLAG=Y) that has local override for system symbols (RTE_X_SYSV_OVERRIDE_SYMBOLS=Y), submit the WKANSAMU(KCIJVUPV) job automatically when re-running the WCONFIG($PARSESV) job. Benefit: For ease of use, variable-named runtime members that could symbolics (*_STC started tasks, *_VTAM_NODE, etc.) are now created automatically in one job ($PARSESV) as opposed to running $PARSESV and running KCIJVUPV job, as this enhancement will detect if the local override flag is set in order to resolve the symbolics in the variable-named runtime members. - Enhance KCIJPMC1/KCIJPMC2 merge LPAR profile values job to automatically use the higher values when TMS:Engine TEMS or Agent storage default values change. Benefit: Reduce reconfiguration requirements when required storage values change for a TEMS or Agent, and automating the KCIJPMCn merge profile processing to use the higher value reduces the exposure of any TMS:Engine started task to encounter storage quiesce startup issues. - Enhance KCIJPSYS system set-up job to provide customer the option to include Health Check-related steps. Benefit: If the Health Check-related members for APF and STC will not be used, allowing the option to null out the "GBL_DSN_HZSPROC_LOADLIB" parameter generates a streamlined KCIJPSYS job without the extra COPYH* steps generated that will not be used. - Enhance the library-specific $PARSE jobs ($PARSEPR IK*->WK* PAR*/PRF*-related "Create runtime members" job / $PARSESM IK*->WK* SAM-related "Create runtime members" job) to remove IEBUPDTE steps when RTE is not enabled for System Variables. Benefit: File-tailoring the $PARSEPR and $PARSESM jobs to not include the IEBUPDTE-related steps of variable-named runtime members that could point to symbolic values, avoids generating a RC=4 when the job is submitted for a System Variables-enabled RTE. - Provide a new KCIJPB2R/KCIJVB2R (if System Variables is enabled) fallback IEBCOPY job that copies the %RTE_HILEV%.%RTE_NAME%.RK*.%CLONE% backup RK* production user libraries (RKANCMDU, RKANPARU, RKANSAMU, RKD2PAR, RKD2PRF and RKD2SAM %CLONE% copies) back into the product execution user libraries (RK*). Benefit: If the backup libraries RK* user libraries need to be restored back to the versions prior to running the KCIJPW2R WK*-->RK* user libraries deployment job, you have a readily available job to do the restore. - Provide SMS support for KCIJPIVP job's %RTE_PLIB_HILEV%.%RTE_NAME%.WSUPERC sequential SUPERC dataset allocation based on RTE_SMS_* parameter values specified by customer in the WCONFIG LPAR profile, instead of inheriting the SMS values for the %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG library. Benefit: If SMS site values change, KCIJPIVP processing will always use the latest specified values in the event that volume requirements have changed since WCONFIG library was initially allocated. - Present the WCONFIG($IVPRPT) automatically upon selection of the "10S" KCIJPIVP job step status on the "SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP" KCIP@SUB panel. Benefit: For ease of use, one has easier access to viewing the output of the KCIJPIVP configuration IVP job. 2. Provide PARMGEN Workflow UI improvements for PARMGEN Application Configuration Enhancements/Updates: - Tivoli Enterprise Monitoring Server (TEMS): * Support a benign, placeholder UKANDATV DDNAME in the TEMS started task (KDS_TEMS_STC = CANSDSST by default) for any future TEMS and Agent function exploitation. Benefit: Generating the started task with a benign UKANDATV DDNAME as preparation for any future functions, avoids having to recycle the TEMS to add a will-be required DDNAME. - OMEGAMON Enhanced 3270UI: * Support a benign, placeholder UKANDATV DDNAME in the Tivoli OMEGAMON Manager (TOM) started task (KOB_TOM_STC = CANSTOM by default) for future Agent function exploitation. Benefit: Generating the started task with a benign UKANDATV DDNAME as preparation for any future functions, avoids having to recycle the TOM to add a will-be required DDNAME. - All standalone agents: * Support a benign, placeholder UKANDATV DDNAME in all Agent started tasks (Kpp_AGT_STC = CANSpp by default) for any future Agent function exploitation. Benefit: Generating the started task with a benign UKANDATV DDNAME as preparation for any future functions, avoids having to recycle the Agent to add a will-be required DDNAME. - OMEGAMON XE for Mainframe Networks V4.2.0 and higher versions: * Provide support for generating the SYSTCPD DDNAME as an optional DD in the N3 Agent started task (KN3_AGT_STC = CANSN3 by default). Benefit: If the CANSN3 Agent does not require the SYSTCPD DD for connection, one may null out (clear out) the "GBL_DSN_TCP_SYSTCPD_TCPDATA_MFN" parameter in the WCONFIG($GBL$USR) so the PARMGEN $PARSE or $PARSESV "Create runtime members and deployment jobs" job creates the WKANSAMU(CANSN3) proc already tailored instead of updating the STC manually outside PARMGEN or ICAT controls. In ICAT, the SYSTCPD DD is not optional. - OMEGAMON XE for Messaging V7.0.0 and higher versions: * Increase the KMQ_AGT_STORAGE_MINIMUM_EXTEND configuration default to 300000 instead of 256000, in support of Self Describing Agent (SDA) functionality and other Agent new functions. This parameter is used in the OMEGAMON XE for Messaging's KMQ Agent's xKANPARU(KMQSYSIN) MINIMUM(%KMQ_AGT_STORAGE_MINIMUM_EXTEND%,X) parameter. Existing PARMGEN RTE profile value for this parameter is preserved so if you want to start using the new configuration default, modify the WCONFIG LPAR profile parameter prior to rerunning the $PARSE or $PARSESV job. - OMEGAMON XE for DB2 PE/PM V5.1.1: * Support new IBM InfoSphere Optim Performance Manager-related LPAR profile parameters as follows: SPMON=%KD2_PFnn_READA_SPMON%, RACOPSIZE=%KD2_PFnn_READA_OPBUFSIZE% and RACOPTHRSHLD=%KD2_PFnn_READA_OPBUFTHR% (SPMON=N, RACOPSIZE=16, and RACOPTHRSHLD=6 default) in the xKD2PAR(OMPE&dbid) runtime member. For more information, please refer to the Techdoc link: http://www-01.ibm.com/support/docview.wss?uid= swg27035964
APAR Information
APAR number
OA40649
Reported component name
CICAT CONFIG SE
Reported component ID
5608A41CC
Reported release
310
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2012-10-25
Closed date
2013-01-24
Last modified date
2013-03-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA67787
Modules/Macros
KCIPRMLB KDSPRMLB
Fix information
Fixed component name
CICAT CONFIG SE
Fixed component ID
5608A41CC
Applicable component levels
R310 PSY UA67787
UP13/02/27 P F302
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.
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRLR8","label":"Tivoli Components"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 March 2013