Re: ? CTMS COBOL:

Jon Paris wrote:

>
>
> I'm also not sure how it would help - and this has nothing to do with porting
> COBOL right?
>

You can't FROMLIBR COBOL source?

Compiling programs in a S/36EE which uses a function not supported by a "real" 
S/36
only issues a warning.

My intent is not to be obtuse here, but couldn't a function like creating a data
base file of source members, with delimiters showing type and date, be easily 
done
by taking some of the syntax governors off of S/36EE commands?

It's just a minor point, but why should a command prompt override program like
FROMLIBR intentionally restrict native capability? It seems a little silly.  OK,
FROMLIBR does not fit into the naming convention but it does call some program
which could just as well be front ended with a more compatible command.  The 
called
program already exits in OS/400.

Doing so let's a user/developer take advantage of what is already existing on 
the
400 without having to jump through a Q&D hoop to get there.

Like you really needed another scoopfull on your plate ;-)

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---