Skip to main content

6 posts tagged with "sprint"

View All Tags

· One min read

Objectives​

Accomplishments​

  • Team walked through some of ADDI's functionality with the client

In Progress​

  • L2 and L3 support are continuing to investigate the build client connecting to Db2.
  • The team discussed JCL Diagrams within ADDI.

Next Steps​

  • Troubleshoot build client connecting to Db2.
  • Work to produce Job Callgraph from JCL.

Tracking (Issues)​

  • Error occurred in build client connecting to Db2 on Cloud. Looking through the logs there was an error An unexpected token "SELECT" was found following "SELECT * FROM ".". Ticket TS015590124 was opened on this error.
  • Programs were missing in the Job Callgraph. Ticket TS015590124 was opened on this.

Cases open: 3

  • Case TS015664878 - Unable to produce Job Callgraph for JCL
  • Case TS015590124 - Db2 error during build client project build
  • Case TS015519419 - Refactor Assistant is throwing an intermittent error when attempting to slice

Cases closed: 3

  • Case TS015519060 - Graphs not populating in IBM Developer for Z
  • Case TS015447064 - Unable to use the host name instead of IP address in client's Windows VM
  • Case TS015362785

· One min read

Objectives​

Accomplishments​

  • Client's environment was able access Db2 on Cloud.
  • Team showed Client how to delete a project in GenApp.

In Progress​

  • Client is working to get Git setup within their VM to move forward with the GenApp transform.
  • During this setup we encountered an error in build client connecting to Db2 on Cloud.

Next Steps​

  • Continue to work with client to get GenApp prepared and test transforms
  • Troubleshoot build client connecting to Db2

Tracking (Issues)​

  • Error occurred in build client connecting to Db2 on Cloud. Looking through the logs there was an error An unexpected token "SELECT" was found following "SELECT * FROM ".". Ticket TS015590124 was opened on this error.

Cases open: 2

  • Case TS015590124 - Db2 error during build client project build
  • Case TS015519419 - Refactor Assistant is throwing an intermittent error when attempting to slice

Cases closed: 3

  • Case TS015519060 - Graphs not populating in IBM Developer for Z
  • Case TS015447064 - Unable to use the host name instead of IP address in client's Windows VM
  • Case TS015362785

· 2 min read

Objectives​

  • Get IDZ up and running in client's environment

Accomplishments​

  • Setup java keystore within client's environment

Work in Progress​

  • The team made contact with the client and they said that they think they have resolved things on their side that should allow outbound connectivity to the DB.
  • Another one of the clients local machines was experiencing the same Cannot connect Mainframe Projects service (URL is null)! Please check settings from CCS error that we troubleshooted in a previous session
  • After further conversation with the client, they discovered that the machine that was encountering this error had multiple Java versions and JAVA_HOME was not set. After setting the correct Java and clearing the cache they were able to see the list of projects in IDZ.
  • The team is continuing to work with support to resolve Case TS015519419. Recent feedback on the ticket suggested collecting logs from Podman ad-core-server, refactoring-assistant, and refactoring-assistant-u if the client encounters this issue again.

Currently Tracking​

  • The team will work with the client in tomorrows working session to test and verify the outbound connectivity to the DB.

  • Team will continue to work with support on the Refactor Assistant issue.

    • This flight log is being submitted via PR "02/28/2024 Documentation"

Tracking​

Cases open: 1

  • Case TS015519419 - Refactor Assistant is throwing an intermittent error when attempting to slice.

Cases closed: 3

  • Case TS015519060 - Graphs not populating in IBM Developer for Z
  • Case TS015447064 - Unable to use the host name instead of IP address in client's Windows VM
  • Case TS015362785

· 2 min read

Objectives​

  • Get IDZ up and running in client's environment

Accomplishments​

  • Team was was able to get graphs enabled within IDZ
  • Setup client's local machines to work with IDZ

Work in Progress​

  • The team had a trouble shooting session with the client (2/22/24). The focus of this session was to resolve the issue of graphs not populating in IBM Developer for Z (IDZ) and to resolve connecting from a client's local machine to IDZ.
  • After some investigation, the team discovered that the port needed for the OrientDB connection was being used by another java process. Once that other java process was stopped and the graphDB service started, the graphs began to populate in the client's IDZ.
  • Next the team moved to resolve connecting the client's local machine to IDZ. After some troubleshooting the team identified the issue was the keystore. IDZ has its own java environment and the issue was resolved by adding the keystore to the java environment being used by IDZ. Once the keystore was added the client was able to use IDZ from their local machine.
  • The team had another session (2/23/24). There was an attempt to reproduce the splicing error, however the client was unable to reproduce it during this session. The team then conversed about the outbound connectivity to the firewall for accessing IBM DB Cloud DB2. The client said they expected this to be resolved by next Monday (2/26/24).

Currently Tracking​

  • The team will work with the client to setup the outbound connectivity to the firewall for accessing IBM DB Cloud DB2.

  • Team will continue to work with support on the Refactor Assistant issue.

    • This flight log is being submitted via PR "02/23/2024 Documentation"

Tracking​

Cases open: 1

  • Case TS015519419 - Refactor Assistant is throwing an intermittent error when attempting to slice.

Cases closed: 3

  • Case TS015519060 - Graphs not populating in IBM Developer for Z
  • Case TS015447064 - Unable to use the host name instead of IP address in client's Windows VM
  • Case TS015362785

· 2 min read

Objectives​

  • Get IDZ up and running in client's environment

Accomplishments​

  • Team was able to launch IDZ within customer's environment.

Work in Progress​

  • The team experienced an issue within IBM Developer for Z where some graphs were not appearing. The team had a troubleshooting session on this issue and has opened a ticket TS015519060.
  • The customer was also encountering an issue with Refactor Assistant. The error was Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is java.lang.NullPointerException] with root cause java.lang.NullPointerException: null. The team opened ticket TS015519419 on this error.
  • The team met with the client and had an app walkthrough session with the client.

Currently Tracking​

  • The team will work with the client to setup the outbound connectivity to the firewall for accessing IBM DB Cloud DB2.

  • Team will continue to work with support on the graphs and Refactor Assistant issues.

    • This flight log is being submitted via PR "02/22/2024 Documentation"

Tracking​

Cases open: 2

  • Case TS015519060 - Graphs not populating in IBM Developer for Z
  • Case TS015519419 - Refactor Assistant is throwing an intermittent error when attempting to slice.

Cases closed: 2

  • Case TS015447064 - Unable to use the host name instead of IP address in client's Windows VM
  • Case TS015362785

· 2 min read

Objectives​

  • Get IDZ up and running in client's environment

Accomplishments​

  • Team resolved network errors within the client's environment
  • Resolved pod errors within the clients environment

Work in Progress​

  • The team experienced some difficulty using host names instead of IP addresses due to IT issues on client’s side.
  • The problem stemmed from how the client was provisioning system was configured, which did not allow for the use of fully qualified domain names.
  • The team opened ticket TS015447064. This issue was resolve by changing priority to IPv4 instead of IPv6.
  • The client was having issues related to container management. The team explained using the stop.sh --all command ensures that all containers are stopped. And the client was able to restart pods with out issues.
  • Inconsistencies and errors were observed in the client's environment, particularly regarding certificate errors.
  • The team suspected that these issues were related to the network provisioning for client's systems.

Currently Tracking​

  • The team will work with the client to setup the outbound connectivity to the firewall for accessing IBM DB Cloud DB2.

    • This flight log is being submitted via PR "02/20/2024 Documentation"

Tracking​

Cases open: 0

Cases closed: 2

  • Case TS015447064 - Unable to use the host name instead of IP address in client's Windows VM

  • Case TS015362785