Messages BMCAMA00100 through BMCAMA00199

This group includes messages for the BMC AMI DevOps for Db2 and BMC AMI SQL Assurance for Db2 products.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

Number	Description
BMCAMA00100E	*Destination member name memberName* cannot be more than 8 characters long Explanation: The destination member name you entered has more than 8 characters. User response:** Enter a valid destination member name that has 8 or less characters.
BMCAMA00101E	*Destination PDS pdsName* is invalid because qualifiers cannot be more than 8 characters long Explanation: The destination PDS you entered is invalid because it contains a qualifier that has more than 8 characters. User response:** Enter a valid destination PDS for which each qualifier has 8 or less characters.
BMCAMA00102E	*Source PDS name pdsName* is invalid Explanation: The source PDS name you entered is invalid because of one of the following reasons: The source PDS name does not contain any file extension. For example, `ABC` is an invalid source PDS name. The source PDS name contains two or more successive periods (.. or ...). For example, `ABC..DEF` is an invalid source PDS name. The first character of the source PDS name is not a letter or one of the following special characters (#, @ or $). Note The other seven characters of the source PDS name can include letters, numbers, the following special characters (#, @ or $), or a hyphen (-)). User response:** Enter a source PDS name that has the correct format.
BMCAMA00103E	*Source PDS name pdsName* cannot be more than 44 characters long Explanation: The source PDS name you entered has more than 44 characters. User response:** Enter a valid source PDS name that has 44 characters or less.
BMCAMA00104E	*Source member memberName* is invalid Explanation: The source member you entered is invalid because of one of the following reasons: The source member contains a period (.) or hyphen (-). The first character of the source member is not a letter or one of the following special characters (#, @ or $). Note The other characters of the source member can include letters, numbers, and the following special characters: #, @ or $. User response:** Enter a source member that has the correct format.
BMCAMA00106E	*Source PDS pdsName* is invalid because qualifiers cannot be more than 8 characters long Explanation: The source PDS you entered is invalid because it contains a qualifier that has more than 8 characters. User response:** Enter a valid source PDS for which each qualifier has 8 or less characters.
BMCAMA00107E	*JCL PDS pdsName* is invalid Explanation:** When configuring the BMC AMI-DevOps for Db2 JCL Execution step, you have selected the Execute JCL from Mainframe PDS check box but the Execution JCL PDS or Directory Name field does not contain a valid PDS. The Execute JCL from Mainframe PDS check box determines whether the JCL is executed from the PDS or local directory. User response: Enter a valid PDS in the Execution JCL PDS or Directory Name field if you have selected the Execute JCL from Mainframe PDS check box.
BMCAMA00108E	Acceptable Return Code must be a 4-digit number between 0000 and 9999 Explanation: The acceptable return code you entered is not a number between 0000 and 9999. User response: Enter an acceptable return code between 0000 and 9999.
BMCAMA00109E	Job Wait Time is not between 1 and 60 Explanation: You must enter a job wait time between 1 and 60 minutes User response: Enter a job wait time between 1 and 60 minutes.
BMCAMA00111E	Product password decryption has failed Explanation: The product password decryption process has failed. User response: Rerun the project or pipeline. If the problem persists, contact BMC Support.
BMCAMA00112E	I/O error while writing to mainframe data set Explanation: An I/O error occurred when writing to the mainframe data set. User response: Rerun the project or pipeline. If the problem persists, contact BMC Support.
BMCAMA00113E	I/O error while closing the output stream Explanation: An I/O error occurred when closing the output stream. User response: Rerun the project or pipeline. If the problem persists, contact BMC Support.
BMCAMA00114E	JCL record cannot be more than 80 bytes long Explanation: The JCL used to submit the job to the mainframe contains a record that is more than 80 bytes long. User response: Correct the JCL record so that it is less than 80 bytes long and rerun the job. If the problem persists, contact BMC Support.
BMCAMA00115E	Invalid client certificate Explanation: An error occurred during client certificate validation for one of the following reasons: The RACF user ID associated with the client certificate has been revoked. The certificate file format is unsupported. Only PKCS#12 client certificates with DER encoded in binary format are supported. The password for the client certificate is incorrect. The client certificate has expired. User response: Enter a valid client certificate and rerun the pipeline or workflow. If the problem persists, contact BMC Support.
BMCAMA00116E	Invalid input specified for client certificate Explanation: An error occurred because of one of the following invalid inputs for the client certificate: The certificate file format is unsupported. Only PKCS#12 client certificates with DER encoded in binary format are supported. The password for client certificate is incorrect. User response: Enter a valid input for the client certificate and rerun the pipeline or workflow. If the problem persists, contact BMC Support.
BMCAMA00120E	Invalid value found for the following fields: workIdOwner exceeds 8 characters workIdOwner starts with number workIdOwner contains invalid special character(s) workIdName exceeds 18 characters workIdName starts with number workIdName contains invalid special character(s) Explanation: The value that you entered is invalid for one of the following reasons: The first character is not a letter or one of the allowed special characters (#, @, _, or $). It is longer than the maximum permitted length (8 characters for workIdOwner and 18 characters for workIdName). The other characters of the value may include alphanumerical characters and the following special characters: #, @, _, and $. User response: Enter a valid value in the correct format.
BMCAMA00121I	<field name> is activated therefore no processing was performed Explanation: You have selected the <field name> check box. User response: No action is required.
BMCAMA00122I	No CDL was generated after comparison in the previous Compare step therefore no further processing was performed. Explanation: In the previous Compare step, you entered identical input for Compare1 and Compare2 fields or properties, so no CDL was generated in the previous step and this step was not run. User response: If RC=0001 was not expected in the previous Compare step, verify the Compare inputs in the previous Compare step and, if necessary, correct them. Otherwise, no action is required.
BMCAMA00123I	Plug-in Variables File: Update the file for variable fieldName Explanation: You have not entered a value for a mandatory variable in the plug-in variables file. User response: Update the plug-in variables file with a value for the variable.
BMCAMA00124I	Source and target schema are identical. No CDL was generated Explanation: The source and target schema are identical. The comparison did not find any differences in the schema and therefore did not generate any CDL. User response: No action is required.
BMCAMA00125E	Work file could not be found Explanation: The work file or the location where the work file is created could not be found. User response: Rerun the job. If the problem persists, contact BMC Support and provide the Console Output log.
BMCAMA00126W	*Host name host* not found in mainframe server certificate Explanation: The host name in the mainframe server certificate does not match the host name you entered in the Mainframe (host name or IP address)** field of the BMC AMI-DevOps for Db2 Authentication build step. User response: Ensure that the host name you enter in the Mainframe (host name or IP address) field of the BMC AMI-DevOps for Db2 Authentication build step matches the mainframe server certificate.
BMCAMA00127E	SSL handshake error, valid certification path for requested target server not found *Explanation:* The execution environment truststore does not contain the z/OSMF server root CA certificate. The execution environment that runs the project or pipeline, which might be the master or the slave, must contain the root CA certificate. The execution environment process runs the following searches sequentially to identify the truststore: If the javax.net.ssl.trustStore system property is defined, the truststore is the file with the specified file name. If the javax.net.ssl.trustStorePassword system property is also defined, the password for the truststore is the specified value of this system property. If the javax.net.ssl.trustStore system property is defined but specifies a file that does not exist, the process runs the next search to identify the truststore. The execution environment process searches for the following file: java-home/lib/security/jssecacerts Important The java-home variable identifies the directory in which the Java Runtime Environment (JRE) is installed. If this file exists, it is the truststore. If this file does not exist, the process runs the next search to identify the truststore. The execution environment process searches for the following file: java-home/lib/security/cacerts This file is the truststore. *User response:* Install the root CA certificate in the truststore.
BMCAMA00128E	SSL truststore error, no truststore found in javax.net.ssl.trustStore system property, java-home/lib/security/jssecacerts or java-home/lib/security/cacerts Explanation: The execution environment truststore does not contain the CA certificate for z/OSMF server. The execution environment process runs the following searches sequentially to identify the truststore: If the javax.net.ssl.trustStore system property is defined, the truststore is the file with the specified file name. If the javax.net.ssl.trustStorePassword system property is also defined, the password for the truststore is the specified value of this system property. If the javax.net.ssl.trustStore system property is defined but specifies a file that does not exist, the process runs the next search to identify the truststore. The execution environment process searches for the following file: java-home/lib/security/jssecacerts Important The java-home variable that identifies the directory in which the Java Runtime Environment (JRE) is installed. If this file exists, it is the truststore. If this file does not exist, the process runs the next search to identify the truststore. The execution environment process searches for the following file: java-home/lib/security/cacerts This file is the truststore. User response: Install the CA certificate of the z/OSMF server in one of the following truststores: java-home/lib/security/jssecacerts java-home/lib/security/cacerts For more information, see Installing topic in the BMC AMI DevOps for Db2 documentation.
BMCAMA00129E	ACMAuth: Re-enter password as encryption/decryption scheme is upgraded Explanation: Your password was encrypted using a different encryption/decryption scheme. The current version of BMC AMI-DevOps for Db2 uses an upgraded version of the encryption/decryption scheme. The upgraded scheme cannot decrypt your password because it was encrypted by the previously-used scheme. User response: Re-enter your password and save the project.
BMCAMA00130E	ACMAuth: Password cannot be more than 63 characters long Explanation: The password you entered has more than 63 characters. A password longer than 63 characters is considered as invalid input and causes project build failure. User response: Enter a password that has 63 or less characters.
BMCAMA00131E	JCL execution response was not found Explanation: The JCL execution returned a null value or improper response from the mainframe. User response: Rerun the job. If the problem persists, contact BMC Support and provide the Console Output log.
BMCAMA00133I	The Mainframe Password field was ignored because you selected Mainframe Password via Property Parameter Explanation: When you select Mainframe Password via Property Parameter, this field does not require Mainframe Password value. User response: No action is required.
BMCAMA00134I	The Mainframe Password via Property Parameter field was ignored because you selected Mainframe Password Explanation: When you select Mainframe Password, this field does not require Mainframe Password via Property Parameter value. User response: No action is required.
BMCAMA00135E	*Invalid File Path: <Variable message text>* The value you entered is invalid because of one of the following reasons: Variable message text: <field name>: Illegal character: <field value> Explanation: You have entered a path that contains invalid characters. Note Illegal characters are specific to the operating system of the execution environment. Variable message text: <field label>: <field value> Explanation: You have entered a path in Plug-in Variables File Path that does not contain a period(.) and file extension. Variable message text: <system generated message> Explanation: The system is unable to obtain a valid directory/file path according to the operating system of the execution environment. User response: Enter a valid directory/file path and rerun the process. If the problem persists, contact BMC Support and provide the Output log.
BMCAMA00136E	Directory/File does not exist: <field name>: <field value> Explanation: The path you entered in the field does not exist. User response: Enter a valid path and rerun the process.
BMCAMA00137E	Not a valid file: <field name>: <field value> Explanation: You have entered a directory instead of a valid file name. User response: Enter a valid file name and rerun the process.
BMCAMA00138E	File is empty: <field name>: <field value> Explanation: The file name you entered in the field does not contain any data. User response: Enter a valid file name that contains data.
BMCAMA00139W	Job Log could not be saved: *<Variable message text>* The Job Log could not be saved because of one of the following reasons: Variable message text: <system generated message>: while writing job log to workspace: <workspace path> Explanation: A write operation failure occurred when writing Job Log/Files (specific DDs) to the workspace. Variable message text: <system generated message>: while writing job log to working directory: <working directory path> Explanation: A write operation failure occurred when writing Job Log/Files (specific DDs) to the working directory. User response: Review the output log and the job output on the mainframe for any error that occurred. Take appropriate action and rerun the job. If the problem persists, contact BMC Support.
BMCAMA00140E	Field Generate CDL to Rollback Schema Changes value is invalid for Select Baseline Type Before Execution Explanation: The Generate CDL to Rollback Schema Changes (generateCdlRollbackSchemaChanges) selection does not allow Select Baseline Type Before Execution (preExecutionBaselineType) with None. User response: As applicable, clear the Generate CDL to the Rollback Schema Changes field or set generateCdlRollbackSchemaChanges property to false when the Select Baseline Type Before Execution field or preExecutionBaselineType property is set to None and rerun the process.
BMCAMA00141E	Load operation has failed: <system generated message>: while loading work file: <working directory path> Explanation: An I/O error occurred when loading the work file. *User response:* Rerun the process. If the problem persists, contact BMC Support and provide the Output log.
BMCAMA00142E	File creation has failed: <system generated message>: while creating empty work file: <working directory path> Explanation: An I/O error occurred when creating empty work file. User response: Rerun the process. If the problem persists, contact BMC Support and provide the Output log.
BMCAMA00143E	Write operation has failed: *<Variable message text>* The Write operation has failed because of one of the following reasons: Variable message text: <system generated message>: while writing to work file: <working directory path> Explanation: An I/O error occurred when writing to work file. Variable message text: <system generated message>: while writing generated JCL to working directory: <working directory path> *Explanation:* An I/O error occurred when writing generated JCL to working directory. Variable message text: <system generated message>: while updating output properties file: <output prop file name> *Explanation:* An I/O error occurred when writing field ‘compareRC’ into UCD output properties file. Variable message text: <system generated message>: while writing generated JCL to workspace: <workspace path> *Explanation:* An I/O error occurred when writing to workspace. Variable message text: <system generated message> Explanation: During the file download process, an I/O error occurred when writing the mainframe file data into the destination file name. User response: Take the necessary action based on system generated message and rerun the process. If the problem persists, contact BMC Support and provide the Output log.
BMCAMA00144E	Working Directory <working directory path> does not have write permissions Explanation: The working directory path you entered does not have write permissions. User response: Provide the permissions into the working directory and rerun the process. If the problem persists, contact BMC Support and provide the Output log.
BMCAMA00145E	Not a valid directory: <field name>: <field value> Explanation: You have entered an invalid directory name. User response: Enter a valid directory name.
BMCAMA00146E	Required authentication information not found Explanation: The InfoVal default value is altered and does not match the required information. User response: Update the InfoVal field to the default value ((${p:<Authentication step name>/infoVal}) and rerun the process. If the problem persists, contact BMC Support and provide the Output log.
BMCAMA00147E	Enter values for the following mandatory fields: <List of mandatory fields> Explanation: You have not entered the values for the mandatory fields on the UI. *User response:* Enter the valid values in the listed mandatory fields and rerun the process.
BMCAMA00148E	Illegal File Name: <field name> contains illegal character: <field value> Explanation: The file name you entered contains an illegal character. Note Illegal characters are specific to the operating system of the execution environment. User response: Enter a valid file name and rerun the process.
BMCAMA00149E	Invalid File Name: <field name> contains invalid characters [<prefix char>]: <field value> Explanation: The file name you entered starts with an invalid character for relative path. The characters which are not supported for relative path are (./, ../, .\ and ..\). User response: Enter a valid relative path file name and rerun the process.
BMCAMA00150E	<field name> was not selected Explanation: The comparison type or object type you selected is not valid or has default value. *User response:* Select a valid comparison type or object type from the drop down and rerun the process.
BMCAMA00151E	Variable <variable> is missing from the plug-in variables file <plugin var file path> Explanation: The variable is not defined in plug-in variables file. *User response:* Add the variable in plug-in variables file and rerun the process.
BMCAMA00152W	A value is not defined for the variable <variable> in the plug-in variables file <plugin var file path> Explanation: Either the variable is blank, or a value is not associated with the variable in plug-in variables file. *User response:* Enter a valid value for the variable and rerun the process.
BMCAMA00153E	<field name>: Invalid data set- <message>: <field value> Explanation: The PDS data set you entered does not match the mainframe naming standards: The PDS data set is missing a period (.). The PDS data set length exceeds 44 characters. The PDS data set contains two successive periods (.. or …). A qualifier of the PDS data set exceeds 8 characters. A qualifier of the PDS data set does not begin with a letter or special character (@, #, or $). Note The other seven characters of a PDS qualifier can include letters, numbers or special characters (#, @, $ or hyphen (-)). User response: Enter a valid PDS data set and rerun the process.
BMCAMA00154E	<field name>: Invalid member name- <message>: <field value> Explanation: The PDS member you entered does not match the mainframe naming standards: The PDS member contains a hyphen (-) or period (.). The PDS member length exceeds 8 characters. The first character of the PDS member is not a letter or one of the following special characters: #, @, or $. Note The other seven characters of the PDS member can include letters, numbers, and the following special characters (#, @, or $). User response: Enter a valid PDS member name and rerun the process.
BMCAMA00155E	<field name>: Member name is missing: <field value> Explanation: The member name is not defined in the PDS field. User response: Enter a valid member name and rerun the process.
BMCAMA00156E	Entered value does not match the default Execution Identifier value Explanation: The Execution Identifier default value is altered and does not match the required information. User response: Enter the default value in the Execution Identifier field and rerun the process. If the problem persists, contact BMC Support and provide the Output log. Note The default value is: (App=${p:application.name},Comp=${p:component.name},Env=${p:environment.name},App_Process=${p:applicationProcess.name},Comp_Process=${p:componentProcess.name})
BMCAMA00157I	Generate JCL Only option is activated therefore no processing was performed Explanation: You have selected the Generate JCL Only check box. *User response:* No action is required. Note If you want to execute the JCL, then remove the Generate JCL Only check box selection and rerun the job.
BMCAMA00158E	Enter value for either PRIMAUTH or Age of Cached Statement field to build the project Explanation: You have not entered the value for either PRIMAUTH or Age of Cached Statement field, for Auto Generated WHERE clause. *User response:* Enter a valid value for at least one field and rerun the job.
BMCAMA00159E	Select operator for field < field name> Explanation: You have not selected the operator for the Age of Cached Statement (CACHED_TS) field for Auto Generated WHERE clause. *User response:* Select the operator and rerun the job.
BMCAMA00160E	<field name> must begin with leading spaces, letter or number followed by letters, numbers or trailing spaces Explanation: The delimited value you entered is invalid because of one of the following reasons: The first character of delimited value is not a leading space, letter or number. The other characters of the delimited value are not letters, numbers, and trailing spaces. *User response:* Enter a valid delimited value and rerun the job.
BMCAMA00161I	The field does not require any value for selected WHERE Clause Generation Mode. The entered value will be ignored. Explanation: The value that you entered is ignored for one of the following reasons: PRIMAUTH and Age of Cached Statement (CACHED_TS) values are ignored when the WHERE Clause Generation Mode setting is User Supplied WHERE clause. The User Supplied WHERE Clause value is ignored when the WHERE Clause Generation Mode setting is Auto Generated WHERE clause. User response: No action is required.
BMCAMA00162I	The job records are truncated because they reached the maximum limit of <maxlimit value> Explanation: The job records exceeded the maxlimit property defined in the plug-in variables file. Therefore, the job output spool file is truncated. User response: No action is required. Note If you want to view additional job records, you can increase the maxlimit value in the plug-in variables file. To view the complete job output, remove the maxlimit value.
BMCAMA00163E	Define the following unresolved variable(s): <list of unresolved ${} variables> Explanation: You have entered invalid symbolic variables, enclosed within ${}, therefore they are unresolved during execution. *User response:* Correct the unresolved symbolic variables, enclosed within ${} and rerun the job.
BMCAMA00164E	Job Card is invalid. Job name should not be blank Explanation: You have not entered the Job name in the Job Card. *User response:* Enter valid Job name and rerun the job.
BMCAMA00165E	Entered value is incorrect for the variable <maxlimit var> in the plug-in variables file <plugin var file path> Explanation: You have entered an invalid value for the variable in the plug-in variables file. User response: Enter a valid value for the variable and rerun the job.
BMCAMA00166E	Job <JobName(JobID)> not found on the mainframe spool Explanation: The mainframe job was either purged or routed to a different LPAR on the mainframe spool while deployment was still executing. Note If the error message is displayed without the Job ID and Job Name, then this message might also have the following description and explanation: Job not found on the mainframe spool Explanation: The mainframe job was purged on the mainframe spool prior to the deployment tool capturing the Job ID and Job Name. *User response:* If the job was routed to a different LPAR then increase the maximum job wait time or review the job output for issues. If the problem persists, contact BMC Support.
BMCAMA00167W	Some records in the Object List File were ignored because the maximum limit of 100 records reached *Explanation:* The number of valid records exceeded the allowed 100 record limit defined in the Object List File. Therefore, the objects exceeding the maximum limit are not processed. User response: Build a new project with a new Object List File for the unprocessed records.
BMCAMA00168W	Some records in the Object List File were ignored due to incorrect Collection Id, Object name or Version. Refer to the List File Processing Summary for details Explanation: The object records you entered in the Object List File are incorrect and therefore ignored for processing. User response: Review the ignored objects in the List File Processing Summary in the Console Output log. Correct the object records and rerun the job.
BMCAMA00169E	Invalid object format in the Object List File *Explanation:* The object format you entered in the Object List File is invalid because of one of the following reasons: Incorrect Package format. Incorrect Plan format. More than one objects are not separated by commas. User response: Review the invalid objects in the List File Processing Summary in the Console Output log. Correct the object format and rerun the job. Note The correct object format is: For Package, "<Collection ID>"."<Package Name>"."<Version>" For Plan, "<Plan Name>" Ensure that all parts of the object name must be in double quotes.
BMCAMA00170E	Processing terminated due to error in the Object List File records. Refer to the List File Processing Summary for details Explanation: An object record error occurred in the Object List File records therefore the process has failed. User response: Review the ignored objects in the List File Processing Summary in the Console Output log. Correct the object records and rerun the job.
BMCAMA00171I	This field value is ignored because you selected either Use Object List File or Object Type Plan Explanation: You have selected either the Use Object List File or the Object Type Plan therefore no value is required for this field. User response: No action is required.
BMCAMA00172E	Invalid file name entered: <object list file>. You must enter a file name that has .txt file type for this field Explanation: You have entered an invalid file name for the Object List File Path field. User response: Enter a valid file name with the .txt file type.
BMCAMA00173E	No response was received from ZOSMF server Explanation: The ZOSMF response returned a null value or improper response from the mainframe. User response: Rerun the process. If the problem persists, contact BMC Support and provide the Output log.
BMCAMA00174W	No result set is returned by the DSN_STATEMENT_CACHE_TABLE query using the WHERE clause. Review the WHERE clause Explanation: The DSN_STATEMENT_CACHE_TABLE query returned no result when using the WHERE clause you have entered. User response: Review the query.
BMCAMA00175E	No result set is returned by the DSN_STATEMENT_CACHE_TABLE query using the WHERE clause. Review the WHERE clause and rerun the job Explanation: The DSN_STATEMENT_CACHE_TABLE query returned no result when using the WHERE clause you have entered. User response: Review the query and rerun the job.
BMCAMA00176E	Select a Source of Schema before entering a value Explanation: When you change a Source of Schema option, the existing Input for Schema Source field value is cleared. To retain the value that you provide for the Input for Schema Source, select a Source of Schema option before entering value. User response: Select a Source of Schema option first and then enter value.
BMCAMA00177E	Input for Schema Source must provide a two-part value separated by a period Explanation: You entered a value that is not a two-part name separated by a period. User response: Enter a valid value with a two-part name separated by a period.
BMCAMA00178E	Review the details of the following message IDs in the mainframe output (JES job log) from the workspace to determine the issue: message ID Explanation: The listed message(s) were received during the Schema Standards processing. The messages require investigation and resolution. User response: View the JES job log output in the workspace to determine the error messages noted in the Console Log. Take the necessary action to resolve the error and rerun the process.
BMCAMA00179W	Review the details of the following message IDs in the mainframe output (JES job log) from the workspace for more information: <message ID> Explanation: The listed message(s) were received during the Schema Standards processing. The messages should be reviewed for explanation or potential resolution. User response: View the JES job log output in the workspace to determine the warning or informational messages noted in the Console Log. If corrective action is needed, make the change(s) and rerun the process.
BMCAMA00180E	Incompatible product version found. BMC AMI DevOps plugin and BMC AMI Change Manager must have same base version. Plugin Base Version: baseVersion Change Manager Base Version: baseVersion Explanation: The base version of BMC AMI DevOps and BMC AMI Change Manager is not matching. User response: Rerun the project or pipeline with the correct base version.
BMCAMA00181W	ALUPRINT is empty or not found for varMessage Explanation: The Compare or Import step of the Schema Migration or the SCHSTDS step of the Schema Standards job did not run successfully and the ALUPRINT DD did not create or populate with data. Here, varMessage for Schema Migration = IMPORT/COMPARE step of Schema Migration, and var message for Schema Standards = SCHSTDS step of Schema Standards. User response: Review the output log and the job output on the mainframe for any error that occurred. Take appropriate action and rerun the project or pipeline.

Messages BMCAMA00100 through BMCAMA00199

Comments