A fix is available
APAR status
Closed as program error.
Error description
Setting up the parameters in ICAT for batch processing parameter 001205 KDP_D2_STC CID2H@@L 001206 KDP_AUTODETECT_INTERVAL 300 001207 KDP_STATUS_REFRESH 60 . causes the following batch error PARAMETER INPUT ERROR NAME LINE# DESCRIPTION ------------------- ----- KDP_D2_STC 1205 Invalid Parameter Sequence: Product Parameter does not belong to this Product Begin/End-Block.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - ICAT * **************************************************************** * PROBLEM DESCRIPTION: 1. The parameters for configuring the * * Server started task that the Agent * * should connect to, are always commented * * out in the generated parameter deck for * * batch mode install. When the comments * * are removed ICAT batch mode install * * causes the following error: * * Invalid parameter sequence: Product * * Parameter does not belong to this * * Begin/End-Block. * * * * 2. The allocation of additional runtime * * datasets fails when the log and output * * datasets for Automatic Exception * * Processing are not specified for all * * DB2 subsystems. * **************************************************************** * RECOMMENDATION: Apply this PTF. * **************************************************************** PROBLEM SUMMARY: 1. ICAT batch mode install causes the following error: Invalid parameter sequence: Product Parameter does not belong to this Begin/End-Block. 2. Allocation of runtime datasets fails. PROBLEM CONCLUSION: 1. In case the parameters are set during ICAT configuration the parameters will be made available for batch mode install. If the parameters are not set the parameters will be commented out. The parameters fullfil the naming conventions now and therefore batch mode install runs successfully. 2. The enabling flags for the log and output datasets are evaluated correctly.
Problem conclusion
1. In case the parameters are set during ICAT configuration the parameters will be made available for batch mode install. If the parameters are not set the parameters will be commented out. The parameters fullfil the naming conventions now and therefore batch mode install runs successfully. 2. The enabling flags for the log and output datasets are evaluated correctly. KEYWORDS :BATCH MODE INSTALL INVALID PARAMETER SEQUENCE AGENT ALLOCATION AUTO EXCEPTION PROCESSING DATASETS CANCEL THREAD PRIVILEGES
Temporary fix
Comments
APAR Information
APAR number
PK54975
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2007-10-18
Closed date
2007-10-23
Last modified date
2007-11-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK30524 UK30525
Modules/Macros
KD260CVA KD260SS3 KD261CVA KD261PY KD5BHELP KD5DDICT KD5SBATO KD531HUB KD531HUC KD531HUD KD531MCU KD5310SP KD5410SP
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310"}]
Document Information
Modified date:
31 March 2021