- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Procob 1.8 to Procob 8.1 on HP UX
Operating System - HP-UX
1753500
Members
4407
Online
108794
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
12-02-2001 08:17 PM
12-02-2001 08:17 PM
Procob 1.8 to Procob 8.1 on HP UX
We run COBOL programs with embedded sql, and are currently upgrading from Oracle version 7.3.4, with Pro Cobol release 1.8.4.0.0 to Oracle 8.1.7 with Pro Cobol 8.1.7.0.0.
Under the old version, host variables containing trailing spaces have these automatically trimmed if the field is used for update or comparison with a column on the database described as VARCHAR2. Under the new version, this does not appear to be the case.
e.g.
column_name varchar2(10)
01 hv-name pic x(10) value "abc".
update table
set column_name = :hv-name
Under the old version, this results in column_name being length(3) and containing 'abc'.
The same code under the new version results in column_name being length(10) and containing 'abc '.
Our best work-around so far is to change the embedded sql statement to:
update table
set column_name = rtrim(:hv-name)
This solution is not ideal, as the changes will be time consuming, and it will be necessary to search all programs for this type of code.
Is there an easier way (such as a parameter setting) which will achieve the same result?
Your help or any suggestions would be greatly appreciated.
Under the old version, host variables containing trailing spaces have these automatically trimmed if the field is used for update or comparison with a column on the database described as VARCHAR2. Under the new version, this does not appear to be the case.
e.g.
column_name varchar2(10)
01 hv-name pic x(10) value "abc".
update table
set column_name = :hv-name
Under the old version, this results in column_name being length(3) and containing 'abc'.
The same code under the new version results in column_name being length(10) and containing 'abc '.
Our best work-around so far is to change the embedded sql statement to:
update table
set column_name = rtrim(:hv-name)
This solution is not ideal, as the changes will be time consuming, and it will be necessary to search all programs for this type of code.
Is there an easier way (such as a parameter setting) which will achieve the same result?
Your help or any suggestions would be greatly appreciated.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2001 10:33 PM
12-02-2001 10:33 PM
Re: Procob 1.8 to Procob 8.1 on HP UX
Doh !!
Found the problem before we got a reply. The Oracle meta system gave us the answer. When converting from 1.8 to 8.1 of the procobol software you may need to specify PICX-VARCHAR2.
Looks like this will do the trick.
Found the problem before we got a reply. The Oracle meta system gave us the answer. When converting from 1.8 to 8.1 of the procobol software you may need to specify PICX-VARCHAR2.
Looks like this will do the trick.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP