RE: program/file data structure

I am glad to see someone asking for something useful that makes sense.  I
agree,  why were these other fields in the SDS not defined with the "*".
Although I must say *rrn - for which file?  I don't think we have any
programs with only one file defined.

The program status Data Structure could give use other useful fields defined
as: *job, *user, *pgmname, *pgmlib, *errorid, *errordta, etc. would be nice.

Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

*Note to Recruiters
I nor anyone that I know of is interested in any new and/or exciting
positions. Please do not contact me.

-----Original Message-----
From: rbrightman@amclog.com [mailto:rbrightman@amclog.com]
Sent: Thursday, September 30, 1999 6:09 AM
To: RPG400-L@midrange.com
Subject: program/file data structure




Don't you think it would be nice to have more of the fields in the file and
program data structures accessed by '*' name instead of trying to remember
the
from/to positions in the data structure?

*parm is a good example. Why can't we have *rrn (relative record number),
*job
(244 - 253 of PDA), *user (254 - 263 of PDA)?

Also, do we really need to code them in the data structure at all? After
all, we
use *date without defining it in the data structure.


+---
| 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
+---
+---
| 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
+---