Re: QNTC

[jpcarr@xxxxxxxxxxxx]

Jeez,  that looks complicated.

Mine is generic in nature.  The calling program builds the "Record"  either
.CSV or what ever.   First time the called routine is evoked, it takes the
file name passed and creates it on the IFS, and writes the first record
passed.  2nd time onwards it just writes the record passed.  At the end the
calling program calls it one more time, and tells the routine to close the
file.

All the Unix API stuff is in the called routine(black boxed and isolated)
various application programs call the same routine.  Never have to look
inside the routine to see the API stuff.


At least it works for us.  Attendee's at COMMON have seemed to like it.

I'm also doing this session in DC in Dec. right DON ?

Reading a IFS file isn't much harder.

John Carr



-------------------
Here's a sample from an article from MC.

      * To * Compile:
      *
      *    CRTBNDRPG  PGM(XXX/PC001RG) DFTACTGRP(*NO) BNDDIR(QC2LE)
      *================================================================
     FPc001df   CF   E             Workstn
     FCstmst    UF A E           K Disk
     FCstnote   UF A E           K Disk

      /copy *LIBL/Qrpglesrc,ifsprotos

<SNIP>