|
I wasn't being flippant with my reply. Once you have done one or two file switches to external from internal, it ceases to be a hard switch. The only issues I've run into is when a field is described differently from program to program. Sometimes even the length of a field may be truncated in a program because of report heading limitations or whatever. --------------------------------- Booth Martin http://www.martinvt.com --------------------------------- -------Original Message------- From: RPG programming on the AS400 / iSeries Date: 06/05/05 14:10:27 To: RPG programming on the AS400 / iSeries Subject: Re: System36 File Access in a Procedure >I an curious how much havoc would be created if you externally described this file? With the proper analysis this could be a great solution, but one needs to be careful of doing this quickly: Check every program add/updating the file for creating possible decimal errors. Reorg and/or rename/rebuilds using s36 BLDFILE. The ancient method of using #gsort to sort a file back into itself. I'm all for making files native - just be careful. jim ----- Original Message ----- From: "Booth Martin" <booth@xxxxxxxxxxxx> To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> Sent: Sunday, June 05, 2005 2:36 PM Subject: RE: System36 File Access in a Procedure I an curious how much havoc would be created if you externally described this file? --------------------------------- Booth Martin http://www.martinvt.com --------------------------------- -------Original Message------- From: RPG programming on the AS400 / iSeries Date: 06/05/05 13:27:52 To: RPG programming on the AS400 / iSeries Subject: RE: System36 File Access in a Procedure Thanks for both your replies The subproc does not have any local variables, just using the I spec's on the global definition. As this coding will ultimately run on a clients V4.3 machine, I'm not using a datastructure for the result of the chain. Can a subproc have local I spec's? I realise the S/36 file is irrelevant, just trying to provide more information. Many thanks. Andy Youens | Senior IBM Consultant | formaserve systems ltd http://www.formaserve.co.uk -----Original Message----- S/36 files are no different to any other program described file. So ....... Most likely cause is that you have local copies of the file's fields defined in the subproc but are not doing a read/chain with the DS as a result field. Unless you use the "into DS result" option, I/O will _always_ use the global fields. If the same fields are defined in the subproc then the subproc code will see the local fields but not the data. That would explain why changing it to a program works, since everything is then using the global variables. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. .. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. .
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.