Austin,
Then you need to find what else has changed to cause the statement numbers
to show up differently.
I have sometimes just looked a few statements before and after until I
find a statement that could throw this error and work from there. It all
depends on where the statement numbers got thrown off.
Rich Loeber - @richloeber
Kisco Information Systems
[1]
http://www.kisco.com
--------------------------------------------------------------------------
Austin, Mark wrote:
Rich,
Both are set to V5R4M0.
Best regards,
Mark
-----Original Message-----
From: [2]cobol400-l-bounces@xxxxxxxxxxxx [[3]mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: 06 July 2009 14:15
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] ILE Cobol - Find source statement
Austin,
Check the *PGM object to find out what OS version the module was compiled
to. Go to the list of modules and put a 5 next to the program in
question. The module created for is on the second panel displayed.
Rich Loeber - @richloeber
Kisco Information Systems
[1][4]
http://www.kisco.com
--------------------------------------------------------------------------
Austin, Mark wrote:
Hi Rich,
Thanks for replying so quickly.
I was aware of your first point and was checking the compilation listing for the statement number reported by the OS.
I wrote this program not so long ago and as far as I'm aware the OS hasn't been upgraded since so I don't think this is causing and complications.
Any other thoughts anyone might have would be appreciated.
Best regards,
Mark
-----Original Message-----
From: [[5]2]cobol400-l-bounces@xxxxxxxxxxxx [[3][6]mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: 06 July 2009 13:54
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] ILE Cobol - Find source statement
Mark,
A couple of things occur to me.
First, are you checking the right statement number in the compile
listing. The OS is reporting the statement number. Don't get this
confused with the statement sequence number. You have to refer to the
compile listing to get the statement number which is in the leftmost
column of the listing.
If this is not the problem, then perhaps you are compiling to a different
OS version than what was originally compiled to. I'd check that next. It
can result in different statement numbers even when your source has not
changed.
Rich Loeber - @richloeber
Kisco Information Systems
[1][4][7]
http://www.kisco.com
--------------------------------------------------------------------------
Austin, Mark wrote:
Hi everyone,
I've got an ILE Cobol program with 3 modules in it. One of the modules has aborted with a subscript out of range error at statement 2979. When I compile the module and check the source listing for the statement 2979 it isn't a statement referring to a subscripted field.
I am obviously doing something wrong. Can anyone enlighten me as to how to find the source statement that is in error?
Best regards,
Mark Austin
IT Consultant
Universal Music Publishing International
Email: [[[8]5]2]mark.austin@xxxxxxxxxx[6][9]<mailto:mark.austin@xxxxxxxxxx>
Tel: +44 (0) 208 742 5520
Fax: +44 (0) 208 742 5699
Universal Music Publishing International Limited Registered in England. Number 02050403 Registered Office: 347-353 Chiswick High Road, London W4 4HS
________________________________
"**Confidentiality**
The information contained in this e-mail is confidential, may be privileged and is intended solely for the use of the named addressee. Access to this e-mail by any other person is not authorised. If you are not the intended recipient, you should not disclose, copy, distribute, take any action or rely on it and you should please notify the sender by reply. Any opinions expressed are not necessarily those of the company.
We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you.
References
Visible links
1. [7][10]
http://www.kisco.com/
2. [8][11]mailto:mark.austin@xxxxxxxxxx
"**Confidentiality**
The information contained in this e-mail is confidential, may be privileged and is intended solely for the use of the named addressee. Access to this e-mail by any other person is not authorised. If you are not the intended recipient, you should not disclose, copy, distribute, take any action or rely on it and you should please notify the sender by reply. Any opinions expressed are not necessarily those of the company.
We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you.
References
Visible links
1. [12]
http://www.kisco.com/
2. [13]mailto:cobol400-l-bounces@xxxxxxxxxxxx
3. [14]mailto:cobol400-l-bounces@xxxxxxxxxxxx
4. [15]
http://www.kisco.com/
5. [16]mail[17]mailto:2]mark.austin@xxxxxxxxxx
6. [18]mailto:mark.austin@xxxxxxxxxx
7. [19]
http://www.kisco.com/
8. [20]mailto:mark.austin@xxxxxxxxxx
"**Confidentiality**
The information contained in this e-mail is confidential, may be privileged and is intended solely for the use of the named addressee. Access to this e-mail by any other person is not authorised. If you are not the intended recipient, you should not disclose, copy, distribute, take any action or rely on it and you should please notify the sender by reply. Any opinions expressed are not necessarily those of the company.
We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you.
References
Visible links
1.
http://www.kisco.com/
2. mailto:cobol400-l-bounces@xxxxxxxxxxxx
3. mailto:cobol400-l-bounces@xxxxxxxxxxxx
4.
http://www.kisco.com/
5. mailto:2]cobol400-l-bounces@xxxxxxxxxxxx
6. mailto:cobol400-l-bounces@xxxxxxxxxxxx
7.
http://www.kisco.com/
8. mailto:5]2]mark.austin@xxxxxxxxxx
9. mailto:mark.austin@xxxxxxxxxx
10.
http://www.kisco.com/
11. mailto:mark.austin@xxxxxxxxxx
12.
http://www.kisco.com/
13. mailto:cobol400-l-bounces@xxxxxxxxxxxx
14. mailto:cobol400-l-bounces@xxxxxxxxxxxx
15.
http://www.kisco.com/
16. mailto:2
17. mailto:mailto:2]mark.austin@xxxxxxxxxx
18. mailto:mark.austin@xxxxxxxxxx
19.
http://www.kisco.com/
20. mailto:mark.austin@xxxxxxxxxx
midrange.com
