× 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: Re: Literal cross-reference objects
  • From: DAsmussen@xxxxxxx
  • Date: Tue, 7 Dec 1999 02:29:32 EST

Al,

In a message dated 12/2/99 12:30:07 PM Eastern Standard Time, 
MacWheel99@aol.com writes:

> When modifying a BPCS program, often heavily filled with L number strings, 
it 
>  can be very time consuming to be looking up what this literal or that one 
>  signifies, so that I can understand what a section of code is working with 
>  before I make any changes.  When there are enough of them, I might 
remember 
>  that I looked up this one before, but not what it was.  The way the object 
>  technology plays out, a compiled program does not offer a convenient 
>  reference list of literals used in it, unlike textual clues in the naming 
of 
>  data fields associated with various files & other structures, with decent 
>  associated labeling.
<<snip>>

Try SYS708, message literals can be sorted and scanned...

Regards!

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com

"It's impossible to make anything foolproof, because fools are so ingenious." 
-- Anonymous
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.