On 11/4/2013 8:59 PM, Paul Gilmartin wrote:
On Mon, 4 Nov 2013 20:21:38 -0700, Steve Comstock wrote:
To do that has nothing to do with COBOL: it's JCL you need to
brush up on. Point LKED.SYSLMOD to a PDS/PDSE that contains
load modules or program objects.
Be very careful doing that! When I
Paul Gilmartin wrote:
Be very careful doing that! When I was very young I tried something similar
without understanding that the following GO step contained:
//STEPLIB DD DISP=(OLD,DELETE),DSN=*.LKED.SYSLMOD
Oops!
A common trap. RACF can help you to protect your dataset with access =
Have a look at
http://www-01.ibm.com/support/docview.wss?uid=swg27036733
and pick your compiler version release and have a look at the
Programming Guide chapter that discusses cataloged procedures.
For example, for Enterprise COBOL for z/OS 4.2, see Chapter 14 Compiling
under z/OS, section
On 11/4/2013 8:21 PM, Steve Comstock wrote:
On 11/4/2013 7:49 PM, Cameron Seay wrote:
All:
I am a re-newbie to COBOL (learned it years ago but it's very rusty). I am
teaching it to my students because it's a great job skill now. Below is job that
contains the source code inline and runs
Cameron:
I can't help you with your COBOL (not one of my languages), but what you
need is some JCL help. Retired Mainframer set you on the the right
direction by saying you should look for another procedure. As he said,
language (assembler and compiler) procedures usually come in three
The CLG at the end of your proc name stands for compile, link, and go. You
should have a corresponding CL proc (for compile and link) that should be
set up to let you specify a permanent library via a symbolic parameter. You
will then need to add Binder (nee Linkage Editor) control cards (or
On 11/4/2013 7:49 PM, Cameron Seay wrote:
All:
I am a re-newbie to COBOL (learned it years ago but it's very rusty). I am
teaching it to my students because it's a great job skill now. Below is job that
contains the source code inline and runs great. It compiles, links and runs
error free.
With Cobol Installation, your shop should have loaded many IGYW* procs. You
are using IGYWCLG.
In the JESMSGLOG you should see a message that states
PROC IGYWCLG Expanded from x Library.
Go to that Library and see if you have other IGYW* procs there. One of them
should have an IEWL or
On Mon, 4 Nov 2013 20:21:38 -0700, Steve Comstock wrote:
To do that has nothing to do with COBOL: it's JCL you need to
brush up on. Point LKED.SYSLMOD to a PDS/PDSE that contains
load modules or program objects.
Be very careful doing that! When I was very young I tried something
similar
