RE: RE: Getting errors back from CRTICFF

Bruce- Thanks for the link. I had already used info from the article to
get my custom compile commands working. At this point, I am not planning
to write my own events file. Just don't have time. I will make do with
looking at spool files in WDSC. 

Thanks,
Sarah


> -----Original Message-----
> From: Bruce Guetzkow [mailto:bruceg@xxxxxxxxxxxxxxxxxxxxxxx] 
> Sent: Friday, January 21, 2005 9:19 AM
> To: wdsci-l@xxxxxxxxxxxx
> Subject: [WDSCI-L] 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
> 
> 
> -- 
> This is the Websphere Development Studio Client for iSeries  
> (WDSCI-L) mailing list To post a message email: 
> WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change 
> list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.
>