|
View previous topic :: View next topic
|
| Author |
Message |
ravichand426
New User
Joined: 23 Jan 2008
Posts: 1
Location: mumbai
|
|
|
|
how to compile cobol program without jcl?
what code merge into pgm? |
|
| Back to top |
|
 |
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| Aren't most programs compiled in the foreground anyway? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello Ravi and welcome to the forums,
| Quote: |
| how to compile cobol program without jcl? |
I'd suggest you talk with your compiler support people to find out if this is acceptable on your system. If it is not, they can also provide the correct compile/link jcl for use on your project/system.
| Quote: |
| what code merge into pgm? |
Please clarify what you want to know. |
|
| Back to top |
|
|
the_gautam
Active User
Joined: 05 Jun 2005
Posts: 165
Location: Bangalore
|
|
|
|
| if you are not willing to use a jcl to compile your cobol programs, you may always compile it using the foreground options. Usually available at 5.2 in the ISPF primary menu. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10872
Location: italy
|
|
|
|
| Quote: |
| you may always compile it using the foreground options. Usually available at 5.2 in the ISPF primary menu. |
That' s a very bad advice...
most IT shops forbid foreground compilations
quite often (apart the jes2 queuing time) it will take longer
any proper goal_mode or ics/ips(old) setup will favor the short running tasks
and long running tasks like compilations will at the end get less resources
imagine 600 tso users running a foreground compilation at the same time... brrrrr... |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| enrico-sorichetti wrote: |
| most IT shops forbid foreground compilations |
I have to respectfully disagree. In 26 years of IT in many different shops, the one consistency is that working in the foreground is always encouraged, and working in the background is always discouraged. I've seen it go so far as to have the Command Center shutdown all of the test/development initiators during peak hours. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10872
Location: italy
|
|
|
|
You have the right to disagree
but those organizations encouraged the worst scenario
what I am suggesting, is still the best practice ( by any point of view )
in order to have a manageable environment, with a good control over the workload..
foreground compilations from my measurements quite often more than double the compilation runs
moreover encouraging foreground compilation they encourage bad programming habits
( programmers write and very seldom reread what they have written )
that' s the same thing that happens with debuggers,
people sitting and hitting the enter key to find out errors that 90% of the time
could have been discovered by just reading the program
again what about 600 tso users running a compilation, and sitting there doing nothing,
waiting for something swapped out to be resumed crawling like a sick turtle
those command centers would have lost all the wars 
this will be my last post on the subject of foreground vs background
( quite often it will end in a religion war )
P.S.
allowing foreground compilations is a way of faking/cheating on compliance with the SLA
(service level agreement)
reporting for batch is much more understandable by the end user
and the response time cannot be adulterated
availability of resources is easily checked ( jes2 queuing )
reporting for tso/foreground is much more complex/murky to understand by the end user
and resource availability and response times are more difficult to measure and balance
no jes2 qeuing for an initiator, but a tso swap after the compilation invocation
no queuing, but longer elapsed |
|
| Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA
|
|
|
|
| In 40 years of programming I have done 2 or 3 foreground compiles. |
|
| Back to top |
|
|
|
|
