Hello Peter,

I'm glad I could provide some ideas!

The one thing you can't guard against is people doing DD card overrides or
even worse/better, writing their own compile procs.  But if they're good
enough to write their own procs, maybe they should move into systems.  *g*
(Hey, that's what I did 20+ years ago...)

Later,
Ray 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Nuttall, Peter [CCC-OT_IT]
Sent: Wednesday December 13 2006 00:31
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: COBOL compiler options JCL PARM.

Many thanks Ray,

I may look into this as a possible long term solution. 

For the moment I have removed the options which are default at this site
(some differ from the manual because they have been overridden by the
sysproggys here) and abbreviated any that are left.

Kind Regards,
Peter

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Behalf
Of Ray Mullins
Sent: 12 December 2006 17:19
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: COBOL compiler options JCL PARM.


Having been down this path before in a galaxy far, far away:

Because you can have multiple CBL cards at the beginning, have a PDS
(SAF.PROT.CBL.DATA) whose members consist of single control cards - for
example

XREFY = CBL XREF
XREFN = CBL NOXREF
LISTY = CBL LIST
LISTN = CBL NOLIST

(of course, this is not an exhaustive list  <g>  )

Then have a proc:

//DOMYCOMP PROC XREF=Y,LIST=N,PROG=XYZ
...
//C EXEC PGM=IGYCBL00,...
//SYSIN DD DISP=SHR,DSN=SAF.PROT.CBL.DATA(XREF&XREF)
//      DD DISP=SHR,DSN=SAF.PROT.CBL.DATA(LIST&LIST)
//* THE FOLLOWING CONTAINS CBL PARMS THAT WE NEVER, EVER, EVER
//* WANT THE PROGRAMMERS TO OVERRIDE, E.G., NOSSRANGE
//      DD DISP=SHR,DSN=SAF.PROT.CBL.DATA(ALWAYS)
//      DD DISP=SHR,DSN=OUR.BIG.OLD.SOURCE.COBOL(&PROG)
...

You give the programmers the opportunity to override selected parms, and
since CBL statement processing always takes the last specification of a
keyword, the ALWAYS member contains those you want to enforce.  And SAF is
your friend preventing those pesky application programmers from creating
their own custom members.

Would this help in your situation?

Best regards,
Ray

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the
archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to