- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Procob compilation : NCG ERROR 5209
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
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
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
03-12-2007 07:43 AM
03-12-2007 07:43 AM
Procob compilation : NCG ERROR 5209
At the company I'm working at we have a problem with the compilation of our COBOL sources in Oracle 8 (It seems). Here's our Setup :
UNIX version (uname -a, bronze being our server name):
HP-UX bronze B.11.11 U 9000/800 103444620 unlimited-user license
Oracle version:
8.1.7
We actually have two user for this machine, one is set up to use Oracle 7 and the other for Oracle 8.
To access these databases we are using Entera 4 Logical Servers (SQL, COBOL and C servers). These servers are then called using a dedicated DLL and entera-generated functions (Stubs) in Visual Basic.
We are now trying to get rid of Oracle 7 and go full Oracle 8, so therefore we are trying to move or Entera Servers from 7 to 8.
Everything works fine except the COBOL compilation under Oracle 8. More precisely, the same command:
cob -xe "RPCMAIN" -C IBMCOMP -C NESTCALL -x -g /upcdev/stubs/shn100_s.cbl /upcdev/source/shp7000.cob /upcdev/source/shp7001.cob -L/opt/entera/tcp/lib -lrpccobol -lrpc -lvoid +lcl -o /upcdev/bin/shn100.bin
where shn100_s.cbl is generated by Entera and the .cob are actual COBOL program where we execute SQL code.
This same command works perfectly under our Oracle 7 User, but not under our Oracle 8 User, even after making the Environment exactly the same (I launched an ENV command under the Oracle 7 user and used it to do an Export script so all the variable are the same in the Oracle 8 User).
Here's the screen log of when I attempt the compilation under he Oracle 8 user:
bronze:/upcdev/script=>cob -xe "RPCMAIN" -C IBMCOMP -C NESTCALL -x -g /upcdev/stubs/shn100_s.cbl /upcdev/source/shp7000.cob /upcde
v/source/shp7001.cob -L/opt/entera/tcp/lib -lrpccobol -lrpc -lvoid +lcl -o /upcdev/bin/shn100.bin
/upcdev/stubs/shn100_s.cbl:
** NCG ERROR **
** Code generation error number 5209
cob: error(s) in code generation: RSHP7000.int
So my questions are:
1 - What is a 5209 error? (I found no data or documentation of this error code anywhere)
2 - What can be it's cause?
Any input or hint would be of course, greatly appreciated.
Luc Desjardins
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2011 09:46 PM
10-17-2011 09:46 PM
Re: Procob compilation: NCG ERROR 5209
>1 - What is a 5209 error? 2 - What can be its cause?
Assuming this is the same code generator as HP's PA compilers:
5209 Cannot open object file %s (5209)
$ CAUSE: The compiler could not open the object file.
$ This may be because:
$ (a) You do not have write permission in the group (on MPE/iX)
$ or directory (on HP-UX) that you are working in.
$ (b) You have run out of some physical disc space limits.
$ ACTION:
$ (a) Work in a group / directory in which you have write
$ permission, or get yourself write permission in the group / directory.
$ (b) Remove some unnecessary files to make room for your object file.