Add 1 to COBOL Forum

tp-cobol-debugger

cultcha — Wed, 18 Jan 2012 18:39:31 +0000

Hi Folks,

Does anyone know if there is a guide to the use of this debugger on a linux platform?

Cheers!!!

Sorry for posting twice

tp-cobol-debugger

cultcha — Wed, 18 Jan 2012 18:37:30 +0000

Hi Folks,

Does anyone know if there is a guide to the use of this debugger on a linux platform?

Cheers!!!

ESQL – ODBC – Error

souleducation — Thu, 20 Oct 2011 01:36:50 +0000

Hello, I’ve been trying to make kiska’s ESQL binary work with a MS Access database
I have used some sample that was on OpenCobol Forum but It can’t connect to the Database.
The Access database is working fine. I tested it with another program and I was able to do a Select * from the table inside the DB.
I think I’m doing something wrong because everything related to the connection is NULL.

Thank you

Here is what I get:

C:\OpenCobol\ESQL\release>esqlOC.exe TESTSQL.sqb
esqlOC.exe: ESQL for OpenCobol Version 2 Build Jun 24 2010

C:\OpenCobol\ESQL\release>cd ..

C:\OpenCobol\ESQL>cd ..

C:\OpenCobol>REM file TESTSQL.COB copied to this folder from release

C:\OpenCobol>cobc -x -debug –version TESTSQL.cob
cobc (OpenCOBOL) 1.1.20100520
Copyright (C) 2001,2002,2003,2004,2005,2006,2007 Keisuke Nishida
Copyright (C) 2006,2007,2008,2009,2010 Roger While
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Built Nov 24 2010 20:00:03
Packaged May 19 2010 16:17:26 UTC

C:\OpenCobol>cobc -x -debug TESTSQL.cob
cob221.c

C:\OpenCobol>TESTSQL.exe
12431656 OCSQL: DB connect to DSN ‘(null)’ user = ‘(null)’
12431656 OCSQL: SQL code 0 : IM002 : [Microsoft][ODBC Driver Manager] Data sourc
e name not found and no default driver specified
12431656 OCSQL: DB connect using Native Driver to SERVER ‘(null)’ user = ‘(null)
‘
12431656 OCSQL: SQL code 0 : IM002 : [Microsoft][ODBC Driver Manager] Data sourc
e name not found and no default driver specified
SQLSTATE=IM002, SQLCODE=+000000000
SQL Error message:[Microsoft][ODBC Driver Manager] Data source name not found an
d no default driver specified
SQLSTATE=08003, SQLCODE=-000008003
SQL Error message:The connection does not exist.
SQLSTATE=08003, SQLCODE=-000008003
SQL Error message:The connection does not exist.
SQLSTATE=08003, SQLCODE=-000008003
SQL Error message:The connection does not exist.

C:\OpenCobol>

History and specification

hillaryterrio — Mon, 13 Dec 2010 22:19:04 +0000

The COBOL specification was created by Grace Murray Hopper^{[dubious – discuss-}essay^] during the second half of 1959. The scene was set on April 8, 1959 at a meeting of computer manufacturers, users, and university people at the University of Pennsylvania Computing Center. The United States Department of Defense subsequently agreed to sponsor and oversee the next activities. A meeting chaired by Charles A. Phillips was held at the Pentagon on May 28 and 29 of 1959 (exactly one year after the Zürich ALGOL 58 meeting); there it was decided to set up three committees: short, intermediate and long range (the last one was never actually formed). It was the Short Range Committee, chaired by Joseph Wegstein of the US National Bureau of Standards, that during the following months created a description of the first version of COBOL.^[2] The committee was formed to recommend a short range approach to a common business language. The committee was made up of members representing six computer manufacturers and three government agencies. The six computer manufacturers were Burroughs Corporation, IBM, Minneapolis-Honeywell (Honeywell Labs), RCA, Sperry Rand, and Sylvania Electric Products. The three government agencies were the US Air Force, the David Taylor Model Basin, and the National Bureau of Standards (now National Institute of Standards and Technology). The intermediate-range committee was formed but never became operational. In the end a sub-committee of the Short Range Committee developed the specifications of the COBOL language. This sub-committee was made up of six individuals:

William Selden and Gertrude Tierney of IBM
Howard Bromberg and Howard Discount of RCA
Vernon Reeves and Jean E. Sammet of Sylvania Electric Products

thanks for the postSixemetle

guest — Thu, 02 Dec 2010 20:21:13 +0000

Nice site, nice and easy on the eyes and great content too.

OCHTML – using copybooks for HTML

aoirthoir — Thu, 02 Dec 2010 20:02:50 +0000

With advent of being able to use OpenCOBOL (OC) as cgi in an internet application Aoirthoir and I have been discussing making OCHTML copybooks. This thread is an attempt to get things started.
I’ve been thinking this over for quite awhile and think I have an idea to get started.
Making the WS is no issue as I have found when doing this as you can see over at example.

Essentially you can setup the following:
01 HTML_TAGS. 05 TAG_INPUT PIC x(07) VALUE "".
Each HTML TAG can be setup this way. You’ll see the method to my madness in a little while. Keep reading.

Since each tag can have many attributes in many combinations I though it would be more prudent to create another working storage for the attributes:
01 HTML_ATTRIBUTES. 05 A_ID PIC x(04) VALUE "ID= ". 05 A_NAME PIC x(06) VALUE "NAME= ". 05 A_CLASS PIC x(07) VALUE "CLASS= ". 05 A_TYPE PIC x(06) VALUE "TYPE= ".
Now what if you want an HTML Input like this:

.
You can do this by displaying directly:

DISPLAY "".

Or using the WS you can do:

DISPLAY TAG_INPUT, A_ID, QUOTE, "my_id", QUOTE A_NAME, QUOTE, "my_name", QUOTE, A_CLASS, QUOTE, "my_class", QUOTE, A_TYPE, "text", CLOSE_INPUT.

That is a generic structure proposal. We can take it even further:
01 HTML_ATTRIBUTES. 05 A_ID. 10 FILLER PIC x(04) VALUE "ID= ". 10 FILLER PIC X(01) VALUE QUOTE. 10 ws_id PCI x(35) VALUE SPACES. 10 FILLER PIC X(01) VALUE QUOTE. 10 FILLER PIC X(01) VALUE SPACE. 05 A_NAME. 10 FILLER PIC x(06) VALUE "NAME= ". 10 FILLER PIC x(04) VALUE "ID= ". 10 FILLER PIC X(01) VALUE QUOTE. 10 ws_name PCI x(35) VALUE SPACES. 10 FILLER PIC X(01) VALUE QUOTE. 10 FILLER PIC X(01) VALUE SPACE. 05 A_CLASS. 10 FILLER PIC x(07) VALUE "CLASS= ". 10 FILLER PIC x(04) VALUE "ID= ". 10 FILLER PIC X(01) VALUE QUOTE. 10 ws_class PCI x(35) VALUE SPACES. 10 FILLER PIC X(01) VALUE QUOTE. 10 FILLER PIC X(01) VALUE SPACE. 05 A_TYPE. 10 FILLER PIC x(06) VALUE "TYPE= ". 10 FILLER PIC x(04) VALUE "ID= ". 10 FILLER PIC X(01) VALUE QUOTE. 10 ws_type PCI x(35) VALUE SPACES. 10 FILLER PIC X(01) VALUE QUOTE. 10 FILLER PIC X(01) VALUE SPACE.

Now you can do:
MOVE "my_id" to ws_id. MOVE "my_name" to ws_name. MOVE "my_class" to ws_class. MOVE "text" to ws_type. DISPLAY TAG_INPUT, A_ID, A_NAME, A_CLASS, A_TYPE, CLOSE_INPUT.

Thoughts? Comments? Praise, glory?

AJAX Web and OpenCOBOL

aoirthoir — Tue, 02 Nov 2010 21:21:25 +0000

We are in the process of converting an old RM-COBOL dos based program to an up to date application. We were looking at simply moving it to a GUI based application, but in this day and age the direction of applications is moving to the internet and web-based apps. In order to provide that instant feedback a GUI based application gives a user we would need to use AJAX. Well OpenCOBOL CAN support this.

If you look at the FAQ on OpenCOBOL.org you can see two examples of Web and CGI.

The first example shows a standard GET. The second example shows AJAX using a POST. Now one of the most important things to think about is security. When doing any data operations you simply should use POST not GET’s. I will get into the reasons at a later date.

This is simply to show you that you can do AJAX with OpenCOBOL very easily.

This is a testme posts

aoirthoir — Tue, 02 Nov 2010 18:37:43 +0000

This is a test post

And I like it.

Hello world!

aoirthoir — Mon, 01 Nov 2010 03:41:21 +0000

Welcome to Add 1 to Cobol Sites. This is your first post. Edit or delete it, then start blogging!