Difference between Compile-link-go and compile-link

Vedam · New User Joined: 24 Apr 2007 Posts: 23 Location: India

Hi,

Can you please let me know the difference between Compile-Link-go and Compile-Link?

Thanks

revel · Posted: Thu Apr 10, 2008 12:57 pm Post subject: Hi Vedam

Hai

Is this Home Work :-)

Ok, Here is answer for your Question

To RUN Any application Program you should convert it into Machine Language(ie Executable instruction)

To do So

We will use JCL, The JCL will have 3 steps normally

1. COMPILATION STEP -
It will convert SOURCE(Say COBOL program) into OBJECT MODULE
(Its not executable intruction)

Ex; COBOL COMPILER - IGYCRCTL

2. LINAKGE STEP
This STEP will LINK EDIT OBJECT MODULE and will yield LOAD
MODULE(This is executable instruction)

3. RUN Step
This Step is used to RUN Application program(Mean in turn it will use LOAD MODULE)

Hope u clear

Aaru

revel,

You have explained how to compile-link-run a cobol program. But i think OP was something different.

He wanted to know the difference between compile-link-go and compile-link.

Gng by the terms i think

compile-link-go -> Compile+link+run

compile-link -> Just compile and link.

Vedam · New User Joined: 24 Apr 2007 Posts: 23 Location: India

Hi,

Thanks for your replies...

1. When you mean by 'Run (Go)' the application program, does it actually submit the JCl for program execution or something else?

2. During 'Link', the load module gets created permanently, right?

dbzTHEdinosauer · Posted: Thu Apr 10, 2008 3:18 pm Post subject:

Vedam,

1. compile/link/go is a job that has the three steps:
compile step
link step
exec pgm='your program'

you create the jcl and submit the job.

2. yes

dbzTHEdinosauer · Posted: Thu Apr 10, 2008 3:44 pm Post subject:

compile link and go is just an abbreviation for a job that contains the compile, link and exec program (test the program) steps.

compile & link means a job that has only the compile and link steps. an additional job with the appropriate JCL to support the invocation of your program would be needed in the case.

Aaru

Dick,

dbzTHEdinosauer · Posted: Thu Apr 10, 2008 5:27 pm Post subject:

Aaru, that is true, also depends whether the output dsn for the loadmodule is a temp (&&..) or a catlg ds.

but, if you want to be picky, which disp parm? I doubt if the OP knows what you are talking about.

Phrzby Phil · Posted: Thu Apr 10, 2008 5:54 pm Post subject:

For programs not requiring link (e.g., no subroutines), there is also compile-go, which uses the loader, rather than the link-editor.

Aaru

Dick,

revel · Posted: Fri Apr 11, 2008 12:08 pm Post subject:

Dear Phrzby Phil,

dick scherrer · Posted: Fri Apr 11, 2008 1:17 pm Post subject:

Hello,

revel · Posted: Fri Apr 11, 2008 4:11 pm Post subject:

dick scherrer,

What i meant is

enrico-sorichetti

if You bypass the link/bind step You will not have a load module !

a load module is produced only by the linkage_editor/binder
any compiler produces only object format thing ( not executable )

a load module library has a recfm U ( undefined )
an object library ( output of a compilation ) has a recfm FB ( usually )

Phrzby Phil · Posted: Fri Apr 11, 2008 6:01 pm Post subject:

Well, all I can say is that I do in fact run a compile-go proc, and it does not have a link-edit step. There is no load module as such stored in either a perm or temp dataset, as I do not need it - the loader (an IBM utility) simply creates a "load module" on the fly and runs it. Then it's gone.

If someone else says I have not been doing that, then what can I say?