Re: COBOL Compile time Question
On Mon, 6 Feb 2006 08:55:48 -0600, Rob Wunderlich [EMAIL PROTECTED] wrote: If using the CICS or DB2 preprocessor, see APAR PQ81622. We had to revert to using the pre-processor to get large programs to compile. Correction, should be DB2 *co*processor. -- 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
Re: COBOL Compile time Question
On Thu, 2 Feb 2006 16:31:47 -0600, Alan C. Field [EMAIL PROTECTED] wrote: Now we have it back and some of the source won't compile. Enterprose 3.3.1 compiler. By that I mean the 140,000 source line program blows the compiler. We're seeing the following abend now: IEA705I ERROR DURING GETMAIN SYS CODE = 804-10 xxx COB STEP010 00 IEA705I 00F89280 00AC9C48 00AC9C48 1200 0FA0 If using the CICS or DB2 preprocessor, see APAR PQ81622. We had to revert to using the pre-processor to get large programs to compile. -Rob -- 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
Re: COBOL Compile time Question
Thanks to the list for all the advice. We have changed the JCL to use a separate precompile step and are making progress. PQ81622 (Thanks Rob) explains at least one of the problems. Alan -- 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
Re: COBOL compile time Question
I can't believe this JCL would work as you miss the DBRMLIB DD-Statement. Perhaps you miss this one. For the U3002 I would like to see the msgs. Do you know Enterprise Cobol 3.3.1 is required for DB2 V8 integrated precompiler? Roland -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mike Bell Sent: Friday, February 03, 2006 3:49 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: COBOL compile time Question This jcl and cblopt works with DB2 V7 and enteprise cobol 3.3 and it works with either region = 0M or region = 8M I tried the same options and JCL with DB2 V8 and got an abend - didn't examine it closely (u3002). The quickest way out is what was already suggested - change to the stand alone precompiler Mike //COB2COMP EXEC PGM=IGYCRCTL,REGION=0M, // PARM='TEST(NONE,SYM),NOSEQUENCE' //STEPLIB DD DISP=SHR,DSN=IGY330.SIGYCOMP // DD DISP=SHR,DSN=DSN710.SDSNLOAD //SYSUT1 DD SPACE=(460,(800,200)),UNIT=SYSDA //SYSUT2 DD SPACE=(460,(800,200)),UNIT=SYSDA //SYSUT3 DD SPACE=(460,(800,200)),UNIT=SYSDA //SYSUT4 DD SPACE=(460,(800,200)),UNIT=SYSDA //SYSUT5 DD SPACE=(460,(800,200)),UNIT=SYSDA //SYSUT6 DD SPACE=(460,(800,200)),UNIT=SYSDA //SYSUT7 DD SPACE=(460,(800,200)),UNIT=SYSDA //SYSPRINT DD SYSOUT=* -- 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
Re: COBOL Compile time Question
-Original Message- From: IBM Mainframe Discussion List On Behalf Of Bill Klein First, I agree with you that a 140,000 line program is NOT a good thing - but it certainly does occur in the real world. If this is a CICS (or possibly DB2) program, make certain that you are NOT using the SIZE(MAX) compiler option (as there needs to be room for the coprocessors). ... or do it the old way using separate-step precompilers. -jc- -- 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
Re: COBOL compile time Question
Thanks for all the responses.
We tried 0M, we tried 64M, never considered 128M but we'll try.
As Roland suggested its looking for X'FA0' 4000dec below the line.
Available region below is about 10.5Mb
Here are the compiler options:
PP 5655-G53 IBM ENTERPRISE COBOL FOR Z/OS 3.3.1
INVOCATION PARAMETERS:
TEST,LIB,NODYNAM,RENT,TRUNC(BIN),SQL(APOST,APOSTSQL),SIZE(8192K),BUFSIZE(2048)
OPTIONS IN EFFECT:
NOADATA
ADV
APOST
ARITH(COMPAT)
NOAWO
BUFSIZE(2048)
NOCICS
CODEPAGE(1140)
NOCOMPILE(S)
NOCURRENCY
DATA(31)
NODATEPROC
DBCS
NODECK
NODIAGTRUNC
NODLL
NODUMP
NODYNAM
NOEXIT
NOEXPORTALL
FASTSRT
FLAG(I,I)
NOFLAGSTD
INTDATE(ANSI)
LANGUAGE(UE)
LIB
LINECOUNT(60)
NOLIST
MAP
NONAME
NSYMBOL(NATIONAL)
NONUMBER
NUMPROC(NOPFD)
OBJECT
OFFSET
NOOPTIMIZE
OUTDD(SYSOUT)
PGMNAME(COMPAT)
RENT
RMODE(AUTO)
NOSEQUENCE
SIZE(8388608)
SOURCE
SPACE(1)
SQL('APOST,APOSTSQL')
SSRANGE
NOTERM
TEST(ALL,SYM,NOSEPARATE)
NOTHREAD
TRUNC(BIN)
NOVBREF
WORD(NOOO)
XREF(SHORT)
YEARWINDOW(1900)
* STATISTICS FOR COBOL PROGRAM xx:
*SOURCE RECORDS = 376159
*DATA DIVISION STATEMENTS = 21589
*PROCEDURE DIVISION STATEMENTS = 90916
RETURN CODE 16
--
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
Re: COBOL compile time Question
This jcl and cblopt works with DB2 V7 and enteprise cobol 3.3 and it works
with either region = 0M or region = 8M
I tried the same options and JCL with DB2 V8 and got an abend - didn't
examine it closely (u3002).
The quickest way out is what was already suggested - change to the stand
alone precompiler
Mike
//COB2COMP EXEC PGM=IGYCRCTL,REGION=0M,
// PARM='TEST(NONE,SYM),NOSEQUENCE'
//STEPLIB DD DISP=SHR,DSN=IGY330.SIGYCOMP
// DD DISP=SHR,DSN=DSN710.SDSNLOAD
//SYSUT1 DD SPACE=(460,(800,200)),UNIT=SYSDA
//SYSUT2 DD SPACE=(460,(800,200)),UNIT=SYSDA
//SYSUT3 DD SPACE=(460,(800,200)),UNIT=SYSDA
//SYSUT4 DD SPACE=(460,(800,200)),UNIT=SYSDA
//SYSUT5 DD SPACE=(460,(800,200)),UNIT=SYSDA
//SYSUT6 DD SPACE=(460,(800,200)),UNIT=SYSDA
//SYSUT7 DD SPACE=(460,(800,200)),UNIT=SYSDA
//SYSPRINT DD SYSOUT=*
TEST(NONE,SYM),NOSEQUENCE
PROCESS(CBL) statements:
CBL SQL('HOST(IBMCOB),QUOTE,APOSTSQL,ATTACH(CAF),VERSION(AUTO)')
CBL LIB,SOURCE,SIZE(8192K)
CBL APOST,NOXREF,RENT,DECK,MAP
Options in effect:
NOADATA
ADV
APOST
ARITH(COMPAT)
NOAWO
BUFSIZE(4096)
NOCICS
CODEPAGE(1140)
NOCOMPILE(S)
NOCURRENCY
DATA(31)
NODATEPROC
DBCS
DECK
NODIAGTRUNC
NODLL
NODUMP
NODYNAM
NOEXIT
NOEXPORTALL
NOFASTSRT
FLAG(I,I)
NOFLAGSTD
INTDATE(ANSI)
LANGUAGE(EN)
LIB
LINECOUNT(60)
NOLIST
MAP
NONAME
NSYMBOL(NATIONAL)
NONUMBER
NUMPROC(NOPFD)
OBJECT
NOOFFSET
NOOPTIMIZE
OUTDD(SYSOUT)
PGMNAME(COMPAT)
RENT
RMODE(AUTO)
NOSEQUENCE
SIZE(8388608)
SOURCE
SPACE(1)
SQL('HOST(IBMCOB),QUOTE,APOSTSQL,ATTACH(CAF),VERSION(AUTO)')
NOSSRANGE
NOTERM
TEST(NONE,SYM,NOSEPARATE)
NOTHREAD
5655-G53 IBM Enterprise COBOL for z/OS 3.3.0
TRUNC(STD)
NOVBREF
NOWORD
NOXREF
YEARWINDOW(1900)
--
Mike
--
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
Re: COBOL compile time Question
On Fri, 3 Feb 2006 07:59:37 -0600, Alan C. Field wrote: We tried 0M, we tried 64M, never considered 128M but we'll try. As Roland suggested its looking for X'FA0' 4000dec below the line. Available region below is about 10.5Mb What does the IEF374I message look like for the compile step? (It is the step end CPU and storage high water mark message in the system messages file.) Does your site have a (very) limiting IEFUSI exit that is preventing you from getting virtual storage above the line? -- Tom Schmidt Madison, WI -- 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
Re: COBOL compile time Question
Have you tried with NOSSR as someone has already suggested. I have experience of trying to compile similar sized programs and the SSR option often causes problems. Jim McAlpine On 2/3/06, Alan C. Field [EMAIL PROTECTED] wrote: Thanks for all the responses. -- 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
Fw: COBOL compile time Question
I would try the doing ALL of the following (at the same time)
- do the SQL preprocessor in a separate step (if the program actually HAS
EXEC SQL statements in it - otherwise use NOSQL)
- Change to SIZE(MAX)
- Change to NOSSRANGE
If - with those 3 changes - the compile still fails, I would contact IBM
support
If those 3 changes allow you to compile, then I would see what combination
of them you could restore.
Alan C. Field [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
m...
Thanks for all the responses.
We tried 0M, we tried 64M, never considered 128M but we'll try.
As Roland suggested its looking for X'FA0' 4000dec below the line.
Available region below is about 10.5Mb
Here are the compiler options:
PP 5655-G53 IBM ENTERPRISE COBOL FOR Z/OS 3.3.1
INVOCATION PARAMETERS:
TEST,LIB,NODYNAM,RENT,TRUNC(BIN),SQL(APOST,APOSTSQL),SIZE(8192K),BUFSIZE(2
048)
OPTIONS IN EFFECT:
NOADATA
ADV
APOST
ARITH(COMPAT)
NOAWO
BUFSIZE(2048)
NOCICS
CODEPAGE(1140)
NOCOMPILE(S)
NOCURRENCY
DATA(31)
NODATEPROC
DBCS
NODECK
NODIAGTRUNC
NODLL
NODUMP
NODYNAM
NOEXIT
NOEXPORTALL
FASTSRT
FLAG(I,I)
NOFLAGSTD
INTDATE(ANSI)
LANGUAGE(UE)
LIB
LINECOUNT(60)
NOLIST
MAP
NONAME
NSYMBOL(NATIONAL)
NONUMBER
NUMPROC(NOPFD)
OBJECT
OFFSET
NOOPTIMIZE
OUTDD(SYSOUT)
PGMNAME(COMPAT)
RENT
RMODE(AUTO)
NOSEQUENCE
SIZE(8388608)
SOURCE
SPACE(1)
SQL('APOST,APOSTSQL')
SSRANGE
NOTERM
TEST(ALL,SYM,NOSEPARATE)
NOTHREAD
TRUNC(BIN)
NOVBREF
WORD(NOOO)
XREF(SHORT)
YEARWINDOW(1900)
* STATISTICS FOR COBOL PROGRAM xx:
*SOURCE RECORDS = 376159
*DATA DIVISION STATEMENTS = 21589
*PROCEDURE DIVISION STATEMENTS = 90916
RETURN CODE 16
--
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
Re: COBOL compile time Question
I just thought of something else (see below) Alan C. Field [EMAIL PROTECTED] wrote in message news:OF798E9B96.C165DDCC-ON8625710A.004C9571-8625710A.004CDEF [EMAIL PROTECTED]... Thanks for all the responses. snip * STATISTICS FOR COBOL PROGRAM xx: *SOURCE RECORDS = 376159 *DATA DIVISION STATEMENTS = 21589 *PROCEDURE DIVISION STATEMENTS = 90916 RETURN CODE 16 If you are getting a RETURN CODE 16 message, then you SHOULD be seeing a U-level IGY message somewhere. Although these often (usually?) don't help much (and basically tell you to contact IBM), can you find it in your output anywhere? If so, does it give you any clue as to what problem it was trying to report? Again, it is QUITE common to see this with SSRANGE and *very* large programs, so I sure would recommend changing that before anything else. -- 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
COBOL Compile time Question
We sent a bunch of COBOL source off-site to get it massaged. Now we have it back and some of the source won't compile. Enterprose 3.3.1 compiler. By that I mean the 140,000 source line program blows the compiler. We've been juggling with the SIZE and BUF parameters and feel we've squeezed as much as we can. Size is set to 9216K and BUF to 256. If we set SIZE any smaller the compiler terminates with the recommendation to increase the SIZE. We're seeing the following abend now: IEA705I ERROR DURING GETMAIN SYS CODE = 804-10 xxx COB STEP010 00 IEA705I 00F89280 00AC9C48 00AC9C48 1200 0FA0 If I understand the programmer correctly the off-site folks are compiling on a PC and not having problems. So, what factors influence the amount of storage needed? Number of source statements? Size of working storage, number of unique variable names, number of FDs? I think any source program that is 140,000 lines is way too large to be comprehensible. All insight into this situation appreciated. Alan -- 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
Re: COBOL Compile time Question
Might be a dumb question but have you increased your REGION size in your JCL. We have a few programs around this size and don't have problems (well not with the compiler), even within Endevor. Mark Gozzard -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Alan C. Field Sent: Friday, 3 February 2006 9:32 AM To: IBM-MAIN@BAMA.UA.EDU Subject: COBOL Compile time Question We sent a bunch of COBOL source off-site to get it massaged. Now we have it back and some of the source won't compile. Enterprose 3.3.1 compiler. By that I mean the 140,000 source line program blows the compiler. We've been juggling with the SIZE and BUF parameters and feel we've squeezed as much as we can. Size is set to 9216K and BUF to 256. If we set SIZE any smaller the compiler terminates with the recommendation to increase the SIZE. We're seeing the following abend now: IEA705I ERROR DURING GETMAIN SYS CODE = 804-10 xxx COB STEP010 00 IEA705I 00F89280 00AC9C48 00AC9C48 1200 0FA0 If I understand the programmer correctly the off-site folks are compiling on a PC and not having problems. So, what factors influence the amount of storage needed? Number of source statements? Size of working storage, number of unique variable names, number of FDs? I think any source program that is 140,000 lines is way too large to be comprehensible. All insight into this situation appreciated. Alan -- 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
COBOL Compile time Question
First, I agree with you that a 140,000 line program is NOT a good thing - but it certainly does occur in the real world. If this is a CICS (or possibly DB2) program, make certain that you are NOT using the SIZE(MAX) compiler option (as there needs to be room for the coprocessors). As someone else has already indicated, make certain that your JCL region is large enough. Finally, TRY using NOSSRANGE and NOOPT and see if this works. using these non-optimal compiler options can reduce (sometimes by a LOT) the size required to compile LARGE COBOL programs. Alan C. Field [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] m... We sent a bunch of COBOL source off-site to get it massaged. Now we have it back and some of the source won't compile. Enterprose 3.3.1 compiler. By that I mean the 140,000 source line program blows the compiler. We've been juggling with the SIZE and BUF parameters and feel we've squeezed as much as we can. Size is set to 9216K and BUF to 256. If we set SIZE any smaller the compiler terminates with the recommendation to increase the SIZE. We're seeing the following abend now: IEA705I ERROR DURING GETMAIN SYS CODE = 804-10 xxx COB STEP010 00 IEA705I 00F89280 00AC9C48 00AC9C48 1200 0FA0 If I understand the programmer correctly the off-site folks are compiling on a PC and not having problems. So, what factors influence the amount of storage needed? Number of source statements? Size of working storage, number of unique variable names, number of FDs? I think any source program that is 140,000 lines is way too large to be comprehensible. All insight into this situation appreciated. Alan -- 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
Re: COBOL Compile time Question
Hmmm.. On second thoughts, we have programs approaching that size (60-80k lines). The Limits section of the COBOL manual says it can handle 999,999 lines, about 4 million bytes of literals etc. etc. all of which seem extremely generous. One wonders if they actually tested the limits or if they're based on the field sizes within the compiler. Mark Gozzard. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Alan C. Field Sent: Friday, 3 February 2006 9:32 AM To: IBM-MAIN@BAMA.UA.EDU Subject: COBOL Compile time Question We sent a bunch of COBOL source off-site to get it massaged. Now we have it back and some of the source won't compile. Enterprose 3.3.1 compiler. By that I mean the 140,000 source line program blows the compiler. We've been juggling with the SIZE and BUF parameters and feel we've squeezed as much as we can. Size is set to 9216K and BUF to 256. If we set SIZE any smaller the compiler terminates with the recommendation to increase the SIZE. We're seeing the following abend now: IEA705I ERROR DURING GETMAIN SYS CODE = 804-10 xxx COB STEP010 00 IEA705I 00F89280 00AC9C48 00AC9C48 1200 0FA0 If I understand the programmer correctly the off-site folks are compiling on a PC and not having problems. So, what factors influence the amount of storage needed? Number of source statements? Size of working storage, number of unique variable names, number of FDs? I think any source program that is 140,000 lines is way too large to be comprehensible. All insight into this situation appreciated. Alan -- 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
Re: COBOL Compile time Question
On Feb 2, 2006, at 4:31 PM, Alan C. Field wrote: We sent a bunch of COBOL source off-site to get it massaged. Now we have it back and some of the source won't compile. Enterprose 3.3.1 compiler. By that I mean the 140,000 source line program blows the compiler. We've been juggling with the SIZE and BUF parameters and feel we've squeezed as much as we can. Size is set to 9216K and BUF to 256. Grin... I won't even go there... Ed --SNIP--- -- 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
Re: COBOL Compile time Question
Alan, Please post the line from the system messages beginning with 'IEF374I' for the compile step so that we can see how much region it used. What is the REGION specification for the compile step? Does the COBOL source include any 'EXEC CICS' translator statements? I would personally expect to run a compile of that size in at least REGION=64M and perhaps REGION=128M or more (if I were doing it myself). On Thu, 2 Feb 2006 16:31:47 -0600, Alan C. Field wrote: We sent a bunch of COBOL source off-site to get it massaged. Now we have it back and some of the source won't compile. Enterprose 3.3.1 compiler. By that I mean the 140,000 source line program blows the compiler. We've been juggling with the SIZE and BUF parameters and feel we've squeezed as much as we can. Size is set to 9216K and BUF to 256. If we set SIZE any smaller the compiler terminates with the recommendation to increase the SIZE. We're seeing the following abend now: IEA705I ERROR DURING GETMAIN SYS CODE = 804-10 xxx COB STEP010 00 IEA705I 00F89280 00AC9C48 00AC9C48 1200 0FA0 If I understand the programmer correctly the off-site folks are compiling on a PC and not having problems. So, what factors influence the amount of storage needed? Number of source statements? Size of working storage, number of unique variable names, number of FDs? I think any source program that is 140,000 lines is way too large to be comprehensible. Maybe, but if the structure flows very well... maybe not? (It might need a logic/flow analyzer to decipher it.) -- Tom Schmidt Madison, WI -- 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
