|
>Thanks much for your answers to my previous question. However when I brought >it to the office, I found that I asked the wrong question, or at least the >right question in the wrong way. >The program has a compile time array in first E spec. Data is at end of >program after the **. The next E spec is an E/COPY of a program that contains >a compile time array, with data at end after the **. The problem is when it >compiles, it puts the elements from the /COPY before the first E spec >elements. Right. Instead of putting your /COPY on the E spec after the first array, try putting it on an F spec before the array, like this: F/COPY ESPEC E ARY1 2 20 It sorts OK for me when I do this; the /COPYd E spec comes before the inline E spec, and the /COPYd compile time data comes before the inline compile time data. Happy new year! Buck Calabro Commsoft +--- | 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.