Patrick,
Although I agree with Vince, I like your enthusiasm, never loose
that!
As of lately (the last 5 years), I've been doing migration work,
migrating HP3000 applications to Windows, Linux and HPUX (Unix).
Like IBM, HP, specifically the HP3000 has it's own version of JCL.
Many of the programmers I work with jump right into converting the
JCL to some local scripting language. On windows it would be BAT
files or Power-hell, on Linux its bash scripts, on HPUX its ksh
scripts, and so on......
Much of the JCL originated from batch the processing days, then
the OLTP machines made it more interactive, and on HP MPE/iX
platforms it grew into a very advanced scripting language. So, for
me (to emulate the JCL environment) the replacement for Batch/JCL
is Tcl. For a minute I thought about using NodeJS instead of Tcl.
In the end I choose Tcl, mostly because I can call "TclEval"
directly from Cobol, or C.
Converting all JCL to Tcl makes more sense, because the exact same
Tcl syntax can be used on any of the most popular platforms,
including Windows, Mac, and all flavours of Unix.
Now with GNU being my platform of choice, and becoming more
aligned with the Richard Stallman philosophy, I ponder, should I
trade Tcl, for Guile?
--
Mike.
On 09/19/2013 08:13 AM, Chris Geldenhuis wrote:
On 09/19/2013 02:17 PM, Vincent Coen
wrote:
On Wednesday 18 Sep 2013 22:03:06 Patrick
wrote:
> After reading one today, it sounds
like people invented the scripting
> language I was considering long ago,
job control language.
>
> This sounds like it should be the
easiest language to implement, is it
> really inconsistent and weird? How
could something so simple have gone
> wrong.
>
>
> Would JCL or something like it be good
for open Cobol ?
JCL is exactly that a Job control system
for executing/starting jobs on a m/f (mainframe) it links any
resources needed by a specific program or group of programs,
e.g., files and their access type, printers etc.
Yes, some of the commands in it are
inconsistent but that is more the fact that various
programmers have coded the new stuff without sticking to some
standards in format etc.
Under Linux such a process is NOT required
as it is all dealt with inside the existing tools of Linux.
There is no need for it and more
importantly the old saying
"If it is not broken don't fix it"
comes seriously to mind.
It is a wasted exercise.
Vince
+1
ChrisG
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
open-cobol-list mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/open-cobol-list
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
open-cobol-list mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/open-cobol-list
|