A fix is available
APAR status
Closed as program error.
Error description
The DB2 Administration Tool for z/OS' Change Management batch interface messaging for invalid parameters does not help customers identify the error. If a parameter which should be enclosed in quotes e.g. action_analyze_change = 'N' is actually coded as: action_analyze_change = 'N the Change Management batch interface will issue a message: ADBCCM: severe error called ADB0006E ADBCCM - Error(s) found. Please review output. and the output will show: IBM0023S ONCODE=670 The CONVERSION condition was raised because of unknown source attributes. From entry point GET_PARMS_LOOP at statement 6593 at compile unit offset +00000258 at entry offset +00000258 and the REPORT DD will show: ADB9703E Program ADBCCM detected an ONCODE condition in If the parameters contain x'0D' carriage return characters valid input such as: action_analyze_change = 'N' action_build_run_job = '' will result in a message: ADB0009E Invalid input from file(PARMS) is ignored. Verify input. Processing continues and further errors in input will not be reported. Invalid value is: ACTION_BUILD_RUN_JOB = '' ADB0006E ADBCCM - Error(s) found. Please review output.
Local fix
For the ONCODE620 please check the parms being passed. For the ADB0009E please check the input for non-display characters such as x'0D'.
Problem summary
**************************************************************** * USERS AFFECTED: Users of the DB2 Administration Tool * * for z/OS who use Change Management * * (CM) Batch. * **************************************************************** * PROBLEM DESCRIPTION: One of the following error messages * * were issued from CM batch while * * the program was validating parameters: * * * * 1) ONCODE=670: * * IBM0023S ONCODE=670 The * * CONVERSION ... * * From entry point GET_PARMS_LOOP * * * * 2) The following message can be issued * * for several types of invalid parameter * * input. The 'invalid value is:' portion * * message below is an example. * * * * ADB0009E Invalid input from file(PARMS) * * is ignored. Verify input. * * * * Processing continues and further errors * * in input will not be reported. * * Invalid value is: * * CHANGE_NAME = 'a' * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem was that the PL/I ONSOURCE function was not working correctly when CM batch was implemented. This prevented CM batch from being able to issue error messages that would give the user an indicator as to what caused the error. The ONSOURCE function problem was fixed by APAR PM56198. This type of error message is most likely caused by unmatched escape characters: Example of unmatched escape characters: job_card_line_1 = '//JOBNAME JOB (INFO),'CM BATCH'' This type of error message can be issued for several types of invalid parameter input. Some of which are: 2.a) A control character ('00'x, '0D'x, etc.), or other character, was detected in a location in the parameter file that is not allowed by the parameter syntax. Example: The '0D'x character existed before CHANGE_COMMENT. ADB0009E Invalid input from file(PARMS) is ignored. Verify input. Processing continues and further errors in input will not be reported. Invalid value is: CHANGE_COMMENT = 'c' 2.b) A misspelled parameter name. Example: ADB0009E Invalid input from file(PARMS) is ignored. Verify input Processing continues and further errors in input will not be reported. Invalid value is: ZZZZZZ_NAME = 'b'
Problem conclusion
The error messages have been enhanced to indicate the most likely cause of the error. The new error messages are documented in the users guide for DB2 Admin Tool. For 1), the CONVERSION condition is no longer issued and instead the following type of error message is issued: Example: ADB0017E An error occurred while reading the input parameters from the PARMS file. The most likely cause of the invalid input is unmatched escape characters for a parameter value. Invalid input is: '//JOBNAME JOB (INFO),'CM For 2), the error message is now more specific to the type of error. For 2.a), an example of the enhanced error message. In this example the '0D'x character existed before CHANGE_COMMENT. ADB0016E The input from the PARMS file is not valid. The first character of the invalid input is ( ) and the hexadecimal value of this character is (0D). If the character is not displayed, check the hexadecimal value. Invalid input is: CHANGE_COMMENT ='c' For 2.b), an example of the enhanced error message. ADB0015E The input from the PARMS file is not valid. A parameter name might bemisspelled. Invalid input is: ZZZZZZ_NAME = 'b'
Temporary fix
Comments
APAR Information
APAR number
PM78739
Reported component name
DB2 ADMIN TOOL
Reported component ID
568851500
Reported release
A20
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-12-07
Closed date
2012-12-28
Last modified date
2013-01-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK90652
Modules/Macros
ADBCCM ADB0001
Fix information
Fixed component name
DB2 ADMIN TOOL
Fixed component ID
568851500
Applicable component levels
RA20 PSY UK90652
UP13/01/01 P F212
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":"10.2.0"}]
Document Information
Modified date:
31 March 2021