RE: newbie: simple file output problem, debugging

   Jared,

   Is this ILE COBOL, or OPM? You use a different debugger with each, unless
   the OPM COBOL has been compiled with:

   CRTCBLPGM SRCFILE(LibName/FileName) SRCMBR(MemberName)
   PGM(LibName/PgmName) OPTION(*SRCDBG)

   The option(*SRCDBG) lets you debug OPM with the ILE debugger.

   ILE Debugger is started with the STRDBG command, and has some functions
   that the OPM debugger does not.  The ILE debugger also has lost some
   functions that the OPM debugger, Color coding of the source is one of
   those things.

   You should have no problem with the file-status, you just need to have a
   working storage area described as fs-thefile.  I have the following
   standard in my pgms.

          01  Fs-TheFile                       PIC X(02).
              88  IO-OK                                  VALUE '00'.
              88  EOF                                    VALUE '10'.
              88  NO-MOD-SFLRCDS                         VALUE '12'.
              88  IO-Error                               VALUE '21' '24'
                            '30' '34' '90' '91' '92' '94' '95' '9A' '9H'
                            '9I' '9K' '9M' '9N' '9P'.
              88  NO-RECORD                              VALUE '23'.
              88  RECORD-LOCKED                          VALUE '9D'.

   In ILE I use the above as a template, and make individual file status
   areas for each file as follows;

          01  FILE-STATUS     Typedef        PIC X(02).
              88  IO-OK                         VALUE "00".
              88  EOF                           VALUE "10".
              88  NO-MOD-SFLRCDS                VALUE "12".
              88  IO-ERR                        VALUE "21" "24" "30"
                   "34" "90" "91" "92" "94" "95" "9A" "9H" "9I" "9K"
                   "9M" "9N" "9P".
              88  Duplicate-Key                 VALUE "22".
              88  NO-RECORD                     VALUE "23".
              88  RECORD-LOCKED                 VALUE "9D".

          01  FS-TheFile      type File-Status.
          01  FS-AnotherFile        type File-Status.

   File status becomes a predefined field type, and then each file-status
   inherits the properties (88 level conditions) of the definition template.

   Then after an open, read, start, or write I can say
     IF IO-OK of FS-TheFile
        Do something here
     else
         Error handling stuff here
     End-IF

   HTH,

   Jim Essinger
   Senior Programmer/Analyst
   SLFI/IMA/UnLtd

   At 10:58 AM 7/15/2004, you wrote:

     thanks for the help, folks...i now think the problem is less that i'm
     unable to write to the file, and more that the data i'm trying to write
     is
     being reset to blanks when i call my C SRVPGM to hash/encrypt it.

     thanks again,

     -jared

     ps - i wasn't able to get the compiler to accept the
             file-status is fs-thefile
     line...it seemed to want the clause to end at
             acceess is sequential