That was it.  I have not done or looked at COBOL in a LONG time, so I
was not sure where to look.  Not I have to figure out who changed this
to not work, but that's my cross to bear. 

Thanks for the quick help. 

C. Todd Burrell
Senior z/OS Systems Programmer
ITSO
(404) 498-3299
(404) 723-2017 (cell)
 
Please visit the ITSO Customer Satisfaction Survey 
and tell us about your recent experiences with ITSO.
 
This survey is for internal CDC use only and the results 
will be used to improve business services.  
Anyone working for CDC in any capacity is invited to participate in our
survey.
 
 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Peter X. DeFabritus
Sent: Wednesday, August 15, 2007 12:21 PM
To: [email protected]
Subject: Re: Weird COBOL issue

Todd, they probably compiled the program with the ADV compiler option.
The quote from the Enterprise COBOL Programmer's Guide is:

"With ADV in effect, the compiler adds 1 byte to the record length to
account for the printer control character".

ADV is the default option.  This is a common point of confusion in
COBOL.  
Recompiling with NOADV should solve the problem.

On Wed, 15 Aug 2007 11:09:34 -0500, Todd Burrell <[EMAIL PROTECTED]> wrote:

>All:
>We have a strange COBOL issue occurring, and I cannot remember what is 
>causing this.  Starting a few days ago, when our programmers compile a 
>cobol program and try to run it, their print files that should be 133 
>characters in length (RECFM=FBA) are failing with basically the old 
>S001 abend, but in this case it is the message IGZ0201W about the 
>record length mismatch, and then the job abends with a U4038 with 
>additional message IGZ0035S indicating the file status 39 error.
>
>They can get the job to run by changing the LRECL to 134 instead of 
>133,
and
>when I compare the current 134 length file with the old production run 
>from last week that worked (LRECL 133) the only difference I see is an 
>extra characer inserted before the first character of the record.  So 
>the old record looks like this (PRINT CONTROL CHARACTER INCLUDED):
>
>1REPORT HEADER
>
>The new one where I had to make the LRECL 134 to avoid the abend looks 
>like
>this:
>
>1 REPORT HEADER
>
>Does anyone know what can cause this (compiler option or PTF)?  I seem 
>to remember this happening a long time ago, but I have long forgotten 
>what caused this, and how I fixed it.
>
>We are currently z/OS 1.8, and have been for about 7 weeks, and this 
>issue started around a week ago.  So I don't think it's an upgrade
issue.
>
>Thanks
>
>Todd Burrell
>
>----------------------------------------------------------------------
>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

----------------------------------------------------------------------
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