*USRIDX ( 0E 0A ) disadvantages? -- MI400

× 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.

Subject: [MI400] *USRIDX ( 0E 0A ) disadvantages?
From: "Hallett Scott" <scott.hallett@xxxxxxx>
Date: Tue, 15 Apr 2003 15:25:09 +0200
List-archive: <http://archive.midrange.com/mi400>
List-help: <mailto:mi400-request@midrange.com?subject=help>
List-id: MI Programming on the AS400 / iSeries <mi400.midrange.com>
List-post: <mailto:mi400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo.cgi/mi400>,<mailto:mi400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo.cgi/mi400>,<mailto:mi400-request@midrange.com?subject=unsubscribe>

Hi all,

I'm new to this,

I'm thinking of using CRTINX 0E 0A to get around the short ( char10 ) naming 
convention and so far I've not found any REAL disadvantages.
I can get around the *CMD, API & Utility dumps by isolating the permanent 
objects in a non *LIBL "context".

Am I missing something important ??? ( that is besides years of MI experiance ( 
smile ) )
Is there a better way ???

Thanks for the input.

Bye,
Scott

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.