- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Runtime error in MicroFocus COBOL
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-03-2002 06:24 AM
тАО01-03-2002 06:24 AM
Object Code error : file '/visa3/step/tpb/TPB085.gnt'
error code: 153, pc=C2B5645B, call=1, seg=0
153 Subscript out of range
In the documentation of manual i seek:
4.6 Debugging Examples
...
4.6.2 UNIX Example
...
Execution error : file 'bug.int'
error code: 114, pc=29, call=2, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)
This error corresponds to the following segment of the report listing, which was generated by compiling bug.cbl with the LIST() and REF directives specified.
1 program-id. "bug". 0
2 working-storage section. 160
3 01 b pic x(20). 160
4 01 c pic x. 178
5 linkage section. 17C
6 01 a pic 9(6). 0
7 procedure division using a. 0
8 move "1" to b(a:1) 29
9 exit program. 30
...
but, in my report listing the scope of the address is different. Directives of compilation are:
cob -C 01SHUFFLE -C REF -P -u $fichero.cob
and my compilation report
...
1180 MOVE "FECHA :" TO TPL050-LITFEC-G02. C9A
1181 MOVE WS-SYS-DIA TO TPL050-FECHA-DD-G02. CA7
1182 MOVE WS-SYS-MES TO TPL050-FECHA-MM-G02. CAD
1183 MOVE WS-SYS-AAAA TO TPL050-FECHA-AA-G02. CB3
1184 MOVE "/" TO TPL050-FECHA-S1-G02 CB9
1185 TPL050-FECHA-S2-G02. CC1
1186 WRITE TPL050-R BEFORE 1. CC1
...
How can determine which is the line of the program involved in the error having pc=C2B5645B and the compilation report?
Thank you!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2002 09:58 AM
тАО01-22-2002 09:58 AM
Re: Runtime error in MicroFocus COBOL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2002 11:18 AM
тАО01-22-2002 11:18 AM
Re: Runtime error in MicroFocus COBOL
One other point, you should compile the COBOL source with -N "hpoptimize=0" as well so that the optimizer does not alter the code after the compiler.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2002 11:25 AM
тАО01-22-2002 11:25 AM
Solution- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-12-2002 07:37 AM
тАО09-12-2002 07:37 AM
Re: Runtime error in MicroFocus COBOL
I'm very interested in your response, as I'm having exactly the same problem myself. However, I can't locate either of the documents you mention (I'm using the European site, not the Americas/Asia-Pacific) and a search by Document I.D. fails to locate them either. Can you help?
Thanks in advance,
Kevin