|
Here is a file feed back data structure generated from Code400 D* File Feed Back F*MYFILE IF E DISK INFDS(File_1) D* File information feedback DS for file feedback D File_1 DS D INF_FILE *FILE * File name D INF_OPEN_IND 9 9N * File open? D INF_EOF_IND 10 10N * File at eof? D INF_STATUS *STATUS * Status code D INF_OPCODE *OPCODE * Last opcode D INF_ROUTINE *ROUTINE * RPG Routine D INF_LIST_NUM 30 37 * Listing line D INF_SPCL_STAT 38 42S 0 * SPECIAL status D INF_RECORD *RECORD * Record name D INF_MSGID 46 52 * Error MSGID D INF_SCREEN *SIZE * Screen size D INF_NLS_IN *INP * NLS Input? D INF_NLS_OUT *OUT * NLS Output? D INF_NLS_MODE *MODE * NLS Mode? D* IO Feeb Back F*MYFILE IF E DISK INFDS(File_2) D* File information feedback DS for input/output feedback D File_2 DS D * 241-242 not used D INF_WRITE_CNT 243 246I 0 * Write count D INF_READ_CNT 247 250I 0 * Read count D INF_WRTRD_CNT 251 254I 0 * Write/read count D INF_OTHER_CNT 255 258I 0 * Other I/O count D INF_OPERATION 260 260 * Cuurent operation D INF_IO_RCD_FMT 261 270 * Rcd format name D INF_DEV_CLASS 271 272 * Device class D INF_IO_PGM_DEV 273 282 * Pgm device name D INF_IO_RCD_LEN 283 286I 0 * Rcd len of I/O D* Open Feed Bach\k F*MYFILE O F 132 PRINTER INFDS(File_3) D* File information feedback DS for open feedback D File_3 DS D INF_ODP_TYPE 81 82 * ODP Type D INF_FILE_NAME 83 92 * File name D INF_LIBRARY 93 102 * Library name D INF_SPOOL_FILE 103 112 * Spool file name D INF_SPOOL_LIB 113 122 * Spool file lib D INF_SPOOL_NUM 123 124I 0 * Spool file num D INF_RCD_LEN 125 126I 0 * Max record len D INF_KEY_LEN 127 128I 0 * Max key len D INF_MEMBER 129 138 * Member name D INF_TYPE 147 148I 0 * File type D INF_ROWS 152 153I 0 * Num PRT/ DSP rows D INF_COLUMNS 154 155I 0 * Num PRT/ DSP cols D INF_NUM_RCDS 156 159I 0 * Num of records D INF_ACC_TYPE 160 161 * Access type D INF_DUP_KEY 162 162 * Duplicate key? D INF_SRC_FILE 163 163 * Source file? D INF_VOL_OFF 184 185I 0 * Vol label offset D INF_BLK_RCDS 186 187I 0 * Max rcds in blk D INF_OVERFLOW 188 189I 0 * Overflow line D INF_BLK_INCR 190 191I 0 * Blk increment D INF_FLAGS1 196 196 * Misc flags D INF_REQUESTER 197 206 * Requester name D INF_OPEN_COUNT 207 208I 0 * Open count D INF_BASED_MBRS 211 212I 0 * Num based mbrs D INF_FLAGS2 213 213 * Misc flags D INF_OPEN_ID 214 215 * Open identifier D INF_RCDFMT_LEN 216 217I 0 * Max rcd fmt len D INF_CCSID 218 219I 0 * Database CCSID D INF_FLAGS3 220 220 * Misc flags D INF_NUM_DEVS 227 228I 0 * Num devs defined Steven S. Brault Technical Consultant The E-100 Group 941 Queen Street Southington, Ct 06489 (860) 628-9443 -----Original Message----- From: Smith, Nelson [mailto:NSmith@lincare.com] Sent: Friday, April 05, 2002 2:44 PM To: 'rpg400-l@midrange.com' Subject: RE: INFDS layout for Display Files Do you have an example of that? Maybe that's what I'm missing.... > In fixed format you could specify the INFDS on the post command. This > would update a separate data structure. Thus you could use two different > data structures. Therefore you could have two external definitions. > > Rob Berendt > > **************************************************************************** **************************************************************************** **************************************************** This message originates from Lincare Holdings Inc. It contains information which maybe confidential or privileged and is intended only for the individual or entity named above. It is prohibited for anyone else to disclose, copy, distribute or use the contents of this message. All personal messages express views solely of the sender, which are not to be attributed to Lincare Holdings Inc., and may not be copied or distributed without this disclaimer. If you received this message in error, please notify us immediately at MailAdmin@lincare.com or (800) 284-2006. **************************************************************************** **************************************************************************** **************************************************** _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.