Does anyone know if Version 4.05 of BPCS is compatible with V5R3 of i5/OS?
AS/400 upgrading, BPCS, i5/OS, iSeries, iSeries applications, iSeries RPG programming, RPG Programming, V5R3
We upgraded out production machine to V5R3 of i5/OS and we are seeing an issue with BPCS programs not compiling that use to before. This includes errors with /COPY statements that were found but now showing the following errors
* QRG2001 Severity: 30 Number: 11
Message . . . . : Form-Type entry invalid or out of sequence.
Specification ignored.
* QRG7030 Severity: 30 Number: 18
Message . . . . : The Field or indicator is not defined.
the field not defined is caused by the Form-Type entry out of sequence because it contains both I specs and c specs and are at the end of the source with the /COPY command.
This never stopped the program from compiling before.
Does anyone have any suggestions?
Thanks
Lovemyi
Software/Hardware used:
Software/Hardware used:
ASKED:
June 8, 2009 8:12 PM
UPDATED:
June 19, 2009 4:16 PM
Answer Wiki:
You are describing 'normal' compiler errors, for which you need to do the usual diagnostics.
The form type error on a /copy line will mean missing lines, so fix that.
Does the referenced source exist?
Is it where the source line states it to be?
Is its library in the compile time library list.
Did you lose it in the upgrade?
Look at the intermediate source and report (option on the compile command)
When you have all the source of the code, in the locations coded, then it will compile, other bugs excepted.
To see all answers submitted to the Answer Wiki: View Answer History.
I bet that all you have to do is add the library of the copy source to your library list for compilation.
The problem is the source code that was used to compile this program originally is not the same one that we were told to look at. The library list is fine and it finds the copy file but the copy file consists of both I specs and C specs and is at the end of the source listing. There is already another /copy after the I specs and before the C specs so moving it to that location is not working either.
I agree that it is not a V5R3 compiler issue but until my application group comes back with the correct details, I told them their issue is the mismatch of source to compiled object and not a compiler issue.