× 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: program/file data structure
  • From: bmorris@xxxxxxxxxx
  • Date: Fri, 1 Oct 1999 12:42:07 -0400




>Date: Thu, 30 Sep 1999 23:16:24 -0400
>From: John P Carr <jpcarr@tredegar.com>

John, good idea to do this, but you've got a couple of fields with wrong
descriptions, if not wrong names.  Pos 1-10 (your P1PGM) is the main-procedure
name (if NOMAIN, the name the main procedure WOULD be, i.e. the module name at
compile time).  Pos 334-343 is the program name (your P1PROC).

You're missing the module name in positions 344-353 and the current user-profile
name in positions 358-367.   (The job/user/num user-profile field in pos 254-263
stays the same even if you switched user profiles before the program ran).

Warning: Filling up the entire PSDS can be costly at initialization time - some
of the information is costly to calculate.  If you don't need all the fields at
the end of the ds, it might be a good idea to have some smaller versions of the
PSDS (maybe using logical files?).

Barbara Morris


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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 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.