|
Hi , I have a problem here with the compilation of a logical when compiling on V4R1 machine which gets compiled normally on V3R2 . The logical(JOIN) code segment for V4R1 machine and the V3R2 machine is as below 0332.00 A TMPCHG 7S 0 RENAME(CHRG#) 0333.00 A CDEPT# SST(TMPCHG 1 2) 0334.00 A* 0335.00 A* KEY FIELDS 0336.00 A* 0337.00 A K CDEPT# 0338.00 A K CDSC The field CHRG# 7P 0 is renamed as TMPCHG and then the first two digits are Substring to CDEPT#. This logical gets compiled in V3R2 but it does not compile on V4R1 machine. This a join logical A* RECORD FORMAT A* A JDFTVAL A R PHLCHPZA JFILE(PHPCHRG PHPPRIC) A TEXT('CHARGES AND PRICING A J JOIN(PHPCHRG PHPPRIC) A JFLD(CHRG# PMCHG#) A JDUPSEQ(PMSEQ#) A* The physical files and the logical have exactly same field definitions in both V3R2 and V4R1. This is the compiler listing of the error message. 33200 TMPCHG 7S 0I JREF(1) + TEXT('CHARGE PROCEDURE ' COLHDG('CHARGE' 'NUMBE 33200 RENAME(CHRG#) 33300 CDEPT# 2A I JREF(1) COLHDG('CDEPT# 33300 SST(TMPCHG 1 2) 33700 K CDEPT# 33800 K CDSC * * * * * E N D O F E X P A N D E D S O U R C E * * 5716SS1 V4R1M0 970829 Data Description QTEMP/ Messages ID Severity Number * CPF3225 40 1 Message . . . . : Attributes of field CDEPT# in record format PHLCHPZA not correct. 5716SS1 V4R1M0 970829 Data Description QTEMP/ Message Summary Total Informational Warning Error Severe (0-9) (10-19) (20-29) (30-99) 1 0 0 0 1 * CPF7302 40 Message . . . . : File PHLCHPL not created is not created. Thank you, Chella Prabhu. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.