ISV SCRT Report Validation error

Products

• COMMON SERVICES FOR Z/OS

Issue/Introduction

When working in the 3270 Emulator with Code Pages different from IBM-037 (US) or IBM-500 (International), we have found several issues during the file transfer of the ISV SCRT Report file to the Broadcom SCRT Report Management site that deals with validation error messages.

This is the error message: 

>>>
Validation error
The report(s) did not pass validation. File(s) modified or missing required data. File(s): file-name
<<<

OR

>>>
IBM validation failed. See the Frequently Asked Questions in the online help.
<<<

Environment

Release : 15.0

Component : SCRT REPORT MANAGEMENT APPLICATION

Resolution

The issue is related to character encoding. When the CAISCRT Job invokes the Sub-Capacity Reporting Tool (SCRT), which is a Java program, the default Code Page for Java is IBM-1047. For most characters, the encoding is the same between the two Code Pages, the Code Page defined in the 3270 Emulator and the default Code Page for Java IBM-1047. However one exception is the @ symbol, which appears in the 'Contact_EMail' parameter in the input //PARMS DD. 

The @ symbol in the IBM-1047 Code Page is X'7C'. When the Code Page defined in the 3270 Emulator does not have the @ symbol defined as X'7C' you will find this problem and you will get the validation error message during the upload of the ISV SCRT Report file to the Broadcom SCRT Report Management site.

Note the input parameters in the //PARMS DD in the CAISCRT JCL are encoded in the Code Page that is defined in the 3270 Emulator. To fix the problem you have to enforce the Java program to work with the same Code Page that is defined in the 3270 Emulator, you can use the '-Dfile.encoding=IBM-XXX' statement for this purpose. 

Steps to add the '-Dfile.encoding=IBM-XXX' statement to the Java options:

In the CAISCRT JCL, you can add this to the IJO variable, something like IJO="$IJO -Dfile.encoding=IBM-XXX". The statement has to be added just before the export IBM_JAVA_OPTIONS="$IJO" statement. The XXX value depends on the Code Page you work in the 3270 Emulator, for example the following ones are for Sweden (IBM-278) or France (IBM-297) Code Pages.

IJO="$IJO -Dfile.encoding=IBM-278"
export IBM_JAVA_OPTIONS="$IJO" 

IJO="$IJO -Dfile.encoding=IBM-297"
export IBM_JAVA_OPTIONS="$IJO" 

You can know the Code Page you are working in the 3270 Emulator session from TSO/ISPF with the following steps: 
  
ISPF option 7.3
ZTERMCID variable value.

If you find any error message in the Broadcom SCRT Report Management site please do not hesitate to open a Case in the  Broadcom Support Portal with CA Common Services product and we can assist you updating the CAISCRT JCL with the appropriate statements.

Additional Information

If your upload fails due to an XML format error, have a look at KB Article Id: 264711