SCRT report upload fails with Cannot invoke "java.util.List.get(int)" or Transaction silently rolled back

Products

• Common Components and Services for z/OS
• Allocate DASD Space and Placement

Issue/Introduction

When you attempt to upload a Broadcom ISV SCRT report (CSV or TXT) to the Broadcom SCRT Repository, the upload may fail with one of the following messages: 

• Cannot invoke "java.util.List.get(int)" because "isvDocument" is null
  
  
• Transaction silently rolled back because it has been marked as rollback-only

 

Review the SCRT report looking for the following lines in the E5 section for each system being reported. Note that the following two entries may not appear in the same order.

Allocate DASD Space and Placement with Quota Manager 12.05.00 ----
12.05.00 ---- 

Environment

• Common Components and Services for z/OS
• Broadcom Product Catalog Version 16
• Allocate DASD Space and Placement with Quota Manager

Cause

The SCRT application rejects the report because it contains unexpected values generated for a specific product. This data mismatch is often associated with "Allocate DASD Space and Placement with Quota Manager" and is surfaced by changes introduced in Broadcom Product Catalog Version 16.

Resolution

To resolve this error and successfully upload your report, you must regenerate the report using an older version of the Broadcom Product Catalog.

1. Obtain Version 15 Catalog: Locate the Broadcom Product Catalog Version 15 file (CAS9SCRT) attached to this article
2. Backup Existing Catalog: Save a backup copy of the current version of the catalog in your ####.CAW0OPTV library.
3. Transfer the File: ASCII transfer the Version 15 catalog file to the ####.CAW0OPTV library on the system where you run your SCRT reports.
4. Regenerate Report: Rerun your CAISCRT JCL, ensuring that the ISVLIB DD statement points to the Version 15 catalog file.
5. Upload to Repository: Sign in to the Broadcom SCRT Repository and upload the newly generated file.
6. To prevent this issue from recurring: Ensure that Allocate PTF LU17461 is applied and implemented on all systems where the Allocate product is used.

Additional Information

The potential for this problem may exist for other reasons or other products, but for now this has only been witnessed in situations involving Allocate DASD Space and Placement 12.05.00

If you experience the problem but are not running Allocate DASD Space and Placement 12.05.00, please open a support case with the Common Components and Services for z/OS support team.