Search results for query: *

I suggest you overcome this problem by using a CDATA tag for XML. See your XML documentation for details.

From the Chairman of J4, and the COBOL working group (WG4): Call for Papers Members of the COBOL standards community (INCITS/J4 and ISO/IEC JTC1/SC22/WG4) together with COBOL Expo 2003 would like to know what your vision is for the COBOL language 5 years from now. There will be a workshop on...

Seems a bit self serving... but... get my book - Sams Teach Yourself COBOL in 24 Hours. It comes with a full functioning compiler and is written in a tutorial style so you can follow the steps to enter your source, compile, and run your programs.

DEC COBOL sticks very close to the Ansi 85 standard. In fact, I have not worked with any other COBOL that is so close. You should not have significant issues.

Which Oracle LIB files are you linking with? I'll check those (once you tell me what they are) for the appropriate entry points. Could be you need a calling convention to eliminate the leading underscore and to keep the case of the call the same.

I suspect that they pro*COBOL precompiler will work with IBM Visual Age COBOL - you just have to link in the proper LIB files. Give it a shot. I think it's not listed simply because it was untested.

I too am curious - did any of the suggestions I posted help?

Crox, I'd be interested in that same program. Can you email it to me? - T H A N E @ S O F T W A R E S I M P L E . C O M (Collapse the spaces, obviously). Thanks

To answer the question recently asked: "My question however is: can you not define a table under a 01-level (and said table is the only item under said 01-level) and then INITIALIZE the 01-level dataname?" The answer is: Yes. 01 Some-Table. 03 Table-Entries Occurs 10 times...

Another alternative is to use the LIB command to put the obj files in a library. Then you can link with the LIB instead of the individual OBJ files.

Maybe we have a language issue here. Crox asked about conversion from COBOL to C# and I said - no reason, because the only environment C# lives in is .NET and COBOL can exist in that environment - so there's no reason for such a conversion. One could better argue a conversion from COBOL to...

Yes - I have such code. I need to know your compiler and operating system.

It's taking a little while for MicroFocus to unmesh themselves from Merant - be patient, it will happen.

A C# conversion from COBOL makes NO Sense. Because Fujitsu has a .NET COBOL compiler - the only place C# lives is in .NET - you can interoperate between C# and COBOL SEAMLESSLY - you can even inherit C# objects from COBOL and COBOL objects from C#. The whole conversion is a silly idea.

A caution - The method of concatenating WS entries with large occurs so you can "walk out of the table" is not a good idea with modern IBM compilers. There is no guarentee that the data items will remain next to each other in storage.

Please note - there is significant syntax difference between START on NT/2000 and START on Windows 9x/ME.

Are you using a select statement to access the table? Select camp from table1.....

Have you updated your compiler, or are you still using the MicroFocus (Microsoft) compiler?

Make that - SEED read. Not see read...

Well, if you read my book you'll see I teach a method that does not use the "priming read" or "see read". I've seen more problems caused by these than they solve - especially in maintenance. Often maintenance programmers miss one or the other read - even when the read is...