JREPORT 8 job does not find Transactions ids over 2100000000 using the following syntax:
SELECT TRANSACT-ID EQ 3402146951
This job results with zero records were found, however entering the Transaction IDs as negative values or Hexadecimal works.
Apparently, over a period of years, apars have been written to add definitions of the SEQ, TRANSACT-ID and DB-KEY fields in JREPORT-000 so that alphanumeric compares could be done against hexadecimal literals. These fields were never documented nor the fact that the comparison against hexadecimal literals were required if the value exceeds 2,147,483,647 or x'7FFFFFFF'.
A documentation change in the CA IDMS Reports manual in Section 8 Producing Journal reports is required. The following paragraph will be added to the end of the SELECT/BYPASS section
When the value for sequence number, transaction id, or dbkey exceeds 2,147,483,647 (or x'7FFFFFFF') the selection criteria comparison value must be specified as a hexadecimal literal for the evaluation to be performed properly. The following fields have been added to JREPORT-000 for these comparisons: SEQ-A, TRANSACT-IDC, and DBKEY-A.
This example prints JREPORT 008 (Formatted Record Dump). The report includes only the BFOR and AFTR records for run unit 2,147,483,649. Since this value is larger than x'7FFFFFFF' the compare needs to be done using a hexadecimal literal against field TRANSACT-IDC.
INPUT 19068 19068 UM(CULLJRNL)
SEL WHEN TYPE EQ ('BFOR' 'AFTR')
* AND TRANSACT-IDC EQ X'80000001'
Problem IDMS 5009 Title: DOCUP COMPARING LARGE VALUES IN JREPORT SELECT