Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Problem with SQL(DATE=EXTERNAL) directive no longer recognized in Visual COBOL 2.1 Update 1

Problem with SQL(DATE=EXTERNAL) directive no longer recognized in Visual COBOL 2.1 Update 1

Problem

In Visual COBOL 2.1 Hotfix 2 a new OpenESQL directive called sql(date=external) was added to allow for the date format to use when accessing an Oracle database to be set using the environment variable NLS_DATE_FORMAT.

This was working fine in Hotfix 2 but after upgrading to Visual COBOL 2.1 Update 1 this no longer appears to be recognized and the following error occurs:

COBCH0801 : Compiler directive SQL(DATE = EXTERNAL) is invalid or badly sequenced - all SQL statements ignored.

What happened?

Resolution

Development has added a new directive called sql(OPTION=PROCOB) which needs to be set if the DATE=EXTERNAL directive is to be used. Actually when setting OPTION=PROCOB on it will automatically set the DATE=EXTERNAL behavior on so the DATE=EXTERNAL is no longer required.

 

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-04-19 08:49
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.