× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I've been writing some data conversion programs which read in an Old File and outputs to a New File. Many of the field names are the same, although with different definitions. I'm reading into a DS and outputting through a DS. For example:

FOldFile IF E K Disk Rename( FileF: OldFileF )
F ExtFile( ConvertFrom ) UsrOpn
FNewFile O E Disk Rename( FileF: NewFileF )
F ExtFile( ConvertTo ) UsrOpn

D ds_New DS LikeRec( NewFileF: *output )
D ds_Old DS LikeRec( OldFileF: *input )

Read CvtCdrMstP ds_Old;
Write CdrMstF ds_New;


That works fine. It creates =I specs for OldFile, but no =O specs for NewFile, so there is no field conflict.

But once I introduce a procedure into the program, it creates the =O specs for NewFile, which then causes a conflict because some fields share names between the files, but do not share the same definitions.

Is there a reason for this? All I know to do is to change the procedure to be a subroutine (shudder) and continue on my way.

I was going to create a quick tiny version of this program to test with, but of course my WDSCi crapped out (well, hung up for about 3-5 minutes, so I had to force close it, resulting in some JVM error, now I'm going to reboot to get my memory back and I'm waiting for 15 Windows updates to apply...)

I'm on v5r4.

Thanks,
Kurt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.