Troubleshooting

General

You might encounter the following error or issue:

• If you do not enter input for a required field of a build step during configuration, BMC AMI DevOps displays an error. You can still build the project, but the project fails.
• To use an older version of the BMC AMI DevOps plug-in in Jenkins, follow these steps:
  1. Manually reinstall the .hpi file of the older version. 
  2. Restart the Jenkins server when no jobs are running.
  You cannot downgrade the BMC AMI DevOps Common and BMC AMI DevOps Schema Management for Db2 plug-ins from the Jenkins web user interface because it is a private plug-in.
• (BMC.DB2.SPE2204) If you add two consecutive authentication steps in a project, the last authentication step will be considered, along with a warning message.

BMC AMI DevOps Schema Mgmt for Db2 - Schema Change Migration

You might encounter the following issues or errors:

• During configuration, if your input in a field exceeds 8 KB of text, Jenkins displays a Bad Message 414 error in the BMC AMI DevOps Schema Mgmt for Db2 - Schema Change Migration build step. To resolve this issue, increase the Jenkins header size to 32 KB as follows:
  1. Log out of Jenkins.

  2. Navigate to the directory on your system in which Jenkins is installed.

  3. Open the jenkins.xml file.

  4. Save the jenkins.xml file with a different name to create a backup. For example, save the file as jenkins_backup.xml.

  5. Open the original jenkins.xml file.

  6. In the <arguments> statement, add the following parameters with the following values:
     

     -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500000

     --requestHeaderSize=32768

     The following example illustrates the <arguments> statement in the jenkins.xml file with the required parameters:

     <arguments>-Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle
     -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500000 -jar
     "%BASE%\jenkins.war" --httpPort=8087 --requestHeaderSize=32768
     --webroot="%BASE%\war"</arguments>

  7. Log in to Jenkins again.

• If your project build fails with the error message BMCAMA00074E: Maximum Job Wait Time exceeded, then review the job output on the mainframe to obtain the total elapsed time that the job required and increase the maximum job wait time accordingly.

  Important

  The Maximum wait time is based on the time elapsed from submission until completion and not on the CPU time used by the job. 

  The purpose of this field is to make sure that a Jenkins Build Executor is not tied up too long.

BMC AMI DevOps Schema Mgmt for Db2 - Schema Standards

(BMC.DB2.SPE2110)

• If you have a problem running your Jenkins pipeline with your rule set in the BMC AMI DevOps Schema Mgmt for Db2 - Schema Standards build step, set Violation Response to WARN. This allows the pipeline to run all steps to completion until you can correct your schema definition.
• If you receive a host variable or SQL error for your rule, you can set your rule to inactive in BMC AMI Command Center for Db2 rule editor. This allows the pipeline or project to run to completion until you can resolve the error with the rule.
  

( SPE2101 )

This section describes how to collect required information when researching issues/errors and reporting to BMC Support:

• To collect the Output process log
• To collect the Java (JDK) version used in the agent environment
• To verify if the Plug-in Variables File Path exists in the server where the Agent is installed and the Agent has access to this file
• To verify the component process type
• To collect the application process step information used to execute the component process
• To verify access to the ZOSMF server with the port number

To collect the Output process log

Each executed step of the component process generates an output process log file that contains the input properties information, environment information, and BMC plug-in versions.

Use the following procedure to download the output logs of an executed process:

1. From your application's dashboard, click the History tab.
2. Click View Request in the Actions column of the failed process on the History screen. 
3. On the application process request's dashboard, click Download All Logs. The downloaded zip file contains the log text files (stdOut.txt) of the steps in their respective folders.

To collect the Java (JDK) version used in the agent environment 

You can find the Java (JDK) version in the agent properties.

Use the following procedure to locate the properties:

1. Click the Resource tab.
2. On the resource dashboard, click the Agents tab.
3. Select the agent name.
4. On the agent dashboard, click the Configuration tab.
5. On the agent configuration dashboard, click Agent Properties.

Select the following property values:

• JAVA_HOME - installed Java home folder
• sys.java.home - installed JRE home folder
• sys.java.version/sys.java.fullversion - system java version 
• sys.java.runtime.version - system java runtime version

To verify whether the Plug-in Variables File Path exists

Use the following procedure to verify whether the Plug-in Variables File Path exists in the server on which the Agent is installed and the Agent has access to this file:

1. On the component's dashboard, click the Processes tab.
2. Select the executed process name.
3. Click Edit Properties for the BMC AMI DevOps Common - Authentication plug-in step in the process editor.
4. View the Plug-in Variables File Path properties value.
5. Verify whether the Plug-in Variables properties file exists in the server on which the Agent is installed.
6. Verify whether the Agent has access to the Plug-in Variables properties file.

To verify the component process type

Use the following procedure to verify the component process type:

1. On the component's dashboard, click the Processes tab.
2. Select the executed process name.
3. Click the Configuration tab.
4. Verify the Process Type from the Basic Settings.

To collect the application process step information used to execute the component process 

Use the following procedure to collect the application process step information used to execute the component process:

1. On your application's dashboard, click the Processes tab.
2. Select the executed process name.
3. Hover over each process step which executes the component process and get the following information for the respective steps:
   • Description
   • Drawer

To verify access to the ZOSMF server with the port number 

Use the following procedure to verify that the port is open in the ZOSMF server firewall for the communication from the agent:

1. Execute this telnet utility command in the agent server command shell prompt (Linux) or the command prompt (Windows):
   telnet <ZOSMF server hostname> <port number>
   
2. If the ZOSMF server is accessible, you will receive this message:
   'Connected to <ZOSMF server hostname>'