Compiler



Support for OS/VS COBOL, VS COBOL II, COBOL for OS/390 & VM and Enterprise COBOL for z/OS

Compiler

Postby talhoo » Sat Feb 08, 2014 12:40 am

Does anybody have JCL for a COBOL compile where the compiler has the integrated CICS and DB2 SQL translator?
talhoo
 
Posts: 4
Joined: Sat Feb 08, 2014 12:33 am
Has thanked: 0 time
Been thanked: 0 time

Re: Compiler

 

Re: Compiler

Postby Robert Sample » Sat Feb 08, 2014 2:33 am

Even if someone provides you JCL, it is not likely to work at your site. Every site has their own requirements for JCL, their own data set names, their own processes (Endevor versus Panvalet versus Librarian for example), and hence what works at one site is not likely to work at a different site.

You need to contact someone working AT YOUR SITE -- coworker, team leader, site support group -- to get the appropriate and correct JCL for you to use.
Robert Sample
Global moderator
 
Posts: 3367
Joined: Sat Dec 19, 2009 8:32 pm
Location: Dubuque, Iowa, USA
Has thanked: 1 time
Been thanked: 222 times

Re: Compiler

Postby talhoo » Sat Feb 08, 2014 2:38 am

Thank you for the reply.

I totally understand that but a sample JCL would be nice so i can tweak it to how it would run in our system.

Would appreciate it if someone would provide the JCL.

Thank you
talhoo
 
Posts: 4
Joined: Sat Feb 08, 2014 12:33 am
Has thanked: 0 time
Been thanked: 0 time

Re: Compiler

Postby steve-myers » Sat Feb 08, 2014 5:33 am

And which compiler??? There are several Cobol compilers, and each one requires slightly different JCL.

More: the compiled code must be linked and combined with modules that are located in a separate library or libraries to produce a load module that will actually execute. As Mr. Sample indicated the data set names for these libraries vary from installation to installation. There is no way those of us here can possibly know these data set names.

Another idea: look in your PROCLIB for procedures with member names like COBxxx. A COBxC member is likely to be a compile only procedure, COBxCL is likely to be a compile and link edit procedure. But, as with all data set names, they vary from installation to installation. One place to start - and I cannot guarantee it will work at your installation - is to locate the "job" for your TSO session in SDSF or IOF or whatever you use and look in the JESYSMSG data set. Near the top you will see a line like IEFC001I PROCEDURE zzz WAS EXPANDED USING SYSTEM LIBRARY ddd. Look in that library. If you don't see any COBxxx procs, try IGYWxxx. Failing that, look for xxxCL or xxxCLG. Sooner or later you will find something of value.
steve-myers
Global moderator
 
Posts: 1886
Joined: Thu Jun 03, 2010 6:21 pm
Has thanked: 4 times
Been thanked: 197 times

Re: Compiler

Postby Robert Sample » Sun Feb 09, 2014 8:26 pm

Most of the recent COBOL compilers have data set names that start IGY (or IGYnnn where nnn is the version of the compiler); however, this is not guaranteed since each site can customize the data set names. There is a PROCLIB shipped with the compiler that includes compile, compile and link, compile and link and execute, and various other types of procedures.

However, since many sites consider it a serious violation of site standards and procedures (leading to disciplinary actions up to and including termination of the employee), you are STRONGLY urged to contact your site support group and find out from them how to use the COBOL compiler at your site. You do NOT want to be seen to be attempting to evade site standards by developing your own compile process.
Robert Sample
Global moderator
 
Posts: 3367
Joined: Sat Dec 19, 2009 8:32 pm
Location: Dubuque, Iowa, USA
Has thanked: 1 time
Been thanked: 222 times

Re: Compiler

Postby dick scherrer » Mon Feb 10, 2014 11:10 pm

Hello,

Unless you are the very first person in your organization to ever compile a COBOL/CICS/DB2 program you should NOT create your own compile/link/bind job.

Your commpiler / cics/ db2 support need to be involved with what Must become standard.

Several of my clients have dismissed people who refure to work with the system standard procedures.

Why do you believe it is ok to "tweak" this . . . :?
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times


Return to IBM Cobol

 


  • Related topics
    Replies
    Views
    Last post