RE: Getting errors back from CRTICFF

Sarah:

<snip>
I am trying to weed out which IBM commands are not capable of generating
an event file.
</snip?>

You've hit the nail on the head.  Some "compile" commands don't generate
an events file.  Until IBM changes that (if they ever choose to) you
have several options, examples of which have already been given for
most:

- use SEU and F15 to get at the compile errors (except, you probably
don't have source for your program object)
- use WRKSPLF or SoftLanding's spooled file plugin (I have it too --
nice tool)
- create your own command wrapper and your own events file

I created a service program with procedures to create an events file
which is available to you (and all) which you might find useful.  See
the following link:
        http://www.itjungle.com/fhg/fhg080404-story01.html
which also explains where the documentation for this layout can be
found.  It's really not too difficult, unless you want to be overly
fancy.  I have created commands CRTPGMX and CRTSRVPGMX for in-house use
which make use of the procedures in a very simple way:  I only wanted to
know whether it was successful or not...I still look into the source for
details.  I could probably enhance it to add specific messages, but
didn't have the time (and still don't).  If you're interested and have
any questions, let me know and I'll be happy to help.

--Bruce Guetzkow