|
|
| Author |
Message |
senjay
Active User
Joined: 10 May 2007
Posts: 85
Location: India
|
|
|
|
Hi,
I have one requirement in COBOL compile JCL. We pass PARM parameters in compilation step as below.
//COB3 EXEC PGM=IGYCRCTL,
// COND=(4,LT),
// PARM=('LANG(UE),F(I,I),NODBCS,OFF,NOLIST',
and so on.
Since the length of PARM parameters is restricted to 100 bytes, i want to store the PARM parameters in a PS file and use it in the same compilation step like below.
//mystep dd dsn=myparm.file,disp=shr
Could you let me know how to achieve this? |
|
| Back to top |
|
 |
References
|
|
 |
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 1199
Location: At my desk
|
|
|
|
Wouldn't that require changing the compiler to read the dataset rather than the parm?
There are other ways to Specify compiler options...... |
|
| Back to top |
|
|
senjay
Active User
Joined: 10 May 2007
Posts: 85
Location: India
|
|
|
|
Hi CICS GUY,
It may. I saw the similar option in PL/1 compiler. So i asked about it.
Anyways is it possible in COBOL compiler? I am having 3.4 version. |
|
| Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 1199
Location: At my desk
|
|
| Back to top |
|
|
senjay
Active User
Joined: 10 May 2007
Posts: 85
Location: India
|
|
|
|
Hi CICS Guy,
Yes. I looked in to it. I have already looked in to PROCESS statement but looking for the alternate solution also. |
|
| Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 1199
Location: At my desk
|
|
|
|
| senjay wrote: |
| Yes. I looked in to it. I have already looked in to PROCESS statement but looking for the alternate solution also. |
An alternate solution? What kind of requirement is driving that? |
|
| Back to top |
|
|
enrico-sorichetti
Global Moderator
Joined: 14 Mar 2007
Posts: 3153
Location: italy
|
|
|
|
both pl/i and COBOL compilers are clear about that...
You set the options by regenerating the appropriate option modules,
You specify the option thru the "PARM" jcl keyword
You specify them thru the language "PROCESS" statement
what else are You looking for  |
|
| Back to top |
|
|
senjay
Active User
Joined: 10 May 2007
Posts: 85
Location: India
|
|
|
|
Hi CICS Guy and enricho,
I was asked to work out on this requirement (Passing PARM parameters through PS). But I am going to propose the 'PROCESS' statement method. Just curious enough to know whether is this possible to give PARM parameters through PS file |
|
| Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 1199
Location: At my desk
|
|
|
|
| senjay wrote: |
| Just curious enough to know whether is this possible to give PARM parameters through PS file |
Yes, it is posssible, but only for programs that are coded to accept them from a PS file, like Sort for one.
Since the compiler can accept the COBOL statements from a PS file, I guess that if you concatinated the PARM file (in the form of the PROCESS statements) before the COBOL statements file, you could get what you wish. |
|
| Back to top |
|
|
senjay
Active User
Joined: 10 May 2007
Posts: 85
Location: India
|
|
|
|
enricho told:
| Quote: |
You set the options by regenerating the appropriate option modules
|
I couldn't get it. Could you throw more light on this? |
|
| Back to top |
|
|
dick scherrer
Global Moderator
Joined: 23 Nov 2006
Posts: 8723
Location: 221 B Baker St
|
|
|
|
Hello,
| Quote: |
| I couldn't get it. Could you throw more light on this? |
If you believe there is a real reason for all of the parms you want to specify, you should change the defult compiler options.
The PARM values are intended to override the standard settings. It sounds like your system would benefit from setting new default/standard values. |
|
| Back to top |
|
|
senjay
Active User
Joined: 10 May 2007
Posts: 85
Location: India
|
|
|
|
Hi Dick,
Thanks. I understood. |
|
| Back to top |
|
|
|
|
