× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi James,

I was under the impression all those who like Unix like to fiddle with the
commands and make them do what they want, so why not clone the CRTBNDRPG (or
whichever) command(s) and add a program to read the spool file and send the
errors to stdout?  Should be fairly straightforward.

Regards,
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax

From: "James Rich" <james@eaerich.com>
To: <midrange-l@midrange.com>
Sent: Monday, October 15, 2001 10:05 AM
Subject: Re: QSHELL commands (was: Stmf copy with add)


> On Sun, 14 Oct 2001, Peter Dow wrote:
> > In addition to the fact that you don't have to type all that, you could
also
> > create your own version. Clone CPYF as CP, and set the default MBROPT to
> > *REPLACE, and there you have it. With F1, F4 available if you need them.
>
> Hmm... clever trojan :)
>
> > And you shouldn't be using WRKSPLF to look at your compile errors, IMHO.
You
> > should be using SEU, F15, option 2, then F *ERR.
>
> This is still looking at the generated spool file to find out what went
> wrong.  I want to be able to see compiler errors printed to stderr or
> stdout, so I can just see them without having to do anything.  Of course I
> want to be able to send the errors to a spoolfile also for when I need to
> work the way you mention above.



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.