|
Sorry my previous email was formatted properly but dont know it is reaching the List in unformatted format and making to read difficult , Iam trying to resend again. Thank you and appreciate your help... On production I can compile the program YIPXMQR in QRPGLESRC using CRTSQLRPGI into QTEMP. But when I compile the same program in development machine we get the below errors, Is this due to operating system upgrade? V5R3is development and also production is V5R3. ===================== 5722ST1 V5R3M0 040528 Create SQL ILE RPG Object YIPXMQR 12/16/04 14:03:04 Page 1 Source type...............RPG Object name...............QTEMP/YIPXMQR Source file...............YIPXC/QRPGLESRC Member....................*OBJ To source file............QTEMP/QSQLTEMP1 Options...................*XREF RPG preprocessor options..*NONE Listing option............*NONE Target release............V5R3M0 INCLUDE file..............*SRCFILE Commit....................*NONE Allow copy of data........*OPTIMIZE Close SQL cursor..........*ENDMOD Allow blocking............*ALLREAD Delay PREPARE.............*NO Generation level..........10 Printer file..............*LIBL/QSYSPRT Date format...............*JOB Date separator............*JOB Time format...............*HMS Time separator ...........*JOB Replace...................*YES Relational database.......*LOCAL User .....................*CURRENT RDB connect method........*DUW Default collection........*NONE Dynamic default collection..............*NO Package name..............*OBJLIB/*OBJ Path......................*NAMING SQL rules.................*DB2 Created object type.......*PGM Debugging view............*SOURCE User profile .............*NAMING Dynamic user profile......*USER Sort sequence.............*JOB Language ID...............*JOB IBM SQL flagging..........*NOFLAG ANS flagging..............*NONE Text......................*SRCMBRTXT Source file CCSID.........37 Job CCSID.................37 Decimal result options: Maximum precision.......31 Maximum scale...........31 Minimum divide scale....0 Compiler options..........*NONE Source member changed on 10/19/04 11:37:57 5722ST1 V5R3M0 040528 Create SQL ILE RPG Object YIPXMQR 12/16/04 14:03:04 Page 2 Record *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+... 8 SEQNBR Last change Comments 1376 C+ WHERE YTRDEX <> â â AND YOFFIC = :COFC AND YACCT = :CACT 137600 08/17/04 1399 C+ WHERE YTRDEX <> â â AND YOFFIC = :COFC AND YACCT = :CACT 139900 08/17/04 1422 C+ WHERE FTRDEX <> â â AND FOFFIC = :COFC AND FACCT = :CACT 142200 08/17/04 1445 C+ WHERE FTRDEX <> â â AND FOFFIC = :COFC AND FACCT = :CACT 144500 08/17/04 5722ST1 V5R3M0 040528 Create SQL ILE RPG Object YIPXMQR 12/16/04 14:03:04 Page 3 DIAGNOSTIC MESSAGES MSG ID SEV RECORD TEXT SQL0314 35 1376 Position 43 Host variable COFC not unique. SQL0314 35 1376 Position 61 Host variable CACT not unique. SQL0314 35 1399 Position 43 Host variable COFC not unique. SQL0314 35 1399 Position 61 Host variable CACT not unique. SQL0314 35 1422 Position 43 Host variable COFC not unique. SQL0314 35 1422 Position 61 Host variable CACT not unique. SQL0314 35 1445 Position 43 Host variable COFC not unique. SQL0314 35 1445 Position 61 Host variable CACT not unique. Message Summary Total Info Warning Error Severe Terminal 8 0 0 0 8 0 35 level severity errors found in source 1483 Source records processed but I can't get the program to compile on my development. The SQL pre-compile fails due to these errors: MSG ID SEV RECORD TEXT SQL0314 35 1380 Position 43 Host variable COFC not unique. SQL0314 35 1380 Position 61 Host variable CACT not unique. These errors seem to occur because COFC and CACCT, which are referenced in SQL statements, are defined as both input fields and within a data structure that is used to construct the key for GNA.INFO. Is there a way around this via a compiler option of something? * * * * * E N D O F L I S T I N G * * * * *
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.