× 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'm wondering if for that one field you could just fully qualify it in the
program so you would not have to change any I specs? I don't know how many
places it is used but no matter what you do you will have to touch the
code. Sorry if I'm way off base here.


--
Doug Belcher
St Louis, MO
314-766-4461

On Wed, Jun 1, 2011 at 4:33 PM, sjl <sjl_abc@xxxxxxxxxxx> wrote:

James wrote:
I'm running into a field name collision between two files (one of which
already has a PREFIX clause that, ironically, while preventing a whole
bunch of collisions, is the cause of this one).

Is there a way, without having to I-spec an entire file, or change the
prefix (which could break an awful lot of code), to rename the one
offending field?

It's on a V6 customer box, so all the "slick new stuff" I try to avoid
in core code is available.



then Joe wrote:
Yup. I-spec for the format name, then use a second I-spec to specify
the internal and external names of the colliding field.


Joe -

Technically, the 2nd I spec (used to specify the internal and external
fields) is known by the SEU and WDSC prompters as a J spec.

To prompt it,

1) In SEU use IPJX in the sequence number field to insert and prompt it, or
2) In WDSC insert a blank line then type PJX in the sequence number column
to get the prompt screen.

Regards,
sjl


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.