From Newsgroup: comp.lang.cobol

On Friday, January 25, 2013 at 2:14:54 AM UTC+5:30, paulsali...@gmail.com wrote:

Hi,

I'm looking for some sample or public COBOL copybook and associated data

files so that I can test some code for converting COBOL data types. I've googled far and wide and can't find anything. Any help would be greatly appreciated.

Thanks.

SEEN-BY: 154/30 2320/100 0 1 227/0

From Newsgroup: comp.lang.cobol

Hello saissen!

Wednesday August 16 2017 08:51, you wrote to All:

On Friday, January 25, 2013 at 2:14:54 AM UTC+5:30,
paulsali...@gmail.com wrote:

Hi,

I'm looking for some sample or public COBOL copybook and associated
data files so that I can test some code for converting COBOL data
types. I've googled far and wide and can't find anything. Any help
would be greatly appreciated.

Converting Cobol data files from one platform to another is hardly rocket science, just create for each file that is NOT LS a convert program that
takes original file and format, creating a new LS version with all binary fields set up as display (e.g., pic 9(n) - where n = max. size of original field regardless of usage of pic or binary etc). Then transfer to new
platform and use another created convert program to do the reverse.

Same applies to replacement rdbms or DMS etc systems but those are a lot
easier if you are lucky.




Vince

SEEN-BY: 154/30 2320/100 0 1 227/0

From Newsgroup: comp.lang.cobol


[posted and e-mailed]

In article <e0a46f63-d311-4f65-b0c2-80cd3696cfff@googlegroups.com>,
<saissen.mq@gmail.com> wrote:

On Friday, January 25, 2013 at 2:14:54 AM UTC+5:30, paulsali...@gmail.com wrote:

Hi,

I'm looking for some sample or public COBOL copybook and associated

data files so that I can test some code for converting COBOL data types.

'(S)ome sample or public COBOL copybook and associated data files... so
that I can test some code'.

Different situations may benefit from different approaches. It might help
you to post to this newsgroup some of this code you already have so a
solution appropriate to the context be generated.

(ancient canine, modern prestidigitation?)

DD

SEEN-BY: 154/30 2320/100 0 1 227/0

From Newsgroup: comp.lang.cobol

In article <1502887613@f1.n250.z2.fidonet.ftn>,
Vince Coen <VBCoen@gmail.com> wrote:

Hello saissen!

Wednesday August 16 2017 08:51, you wrote to All:

On Friday, January 25, 2013 at 2:14:54 AM UTC+5:30,
paulsali...@gmail.com wrote:

Hi,

I'm looking for some sample or public COBOL copybook and associated
data files so that I can test some code for converting COBOL data
types. I've googled far and wide and can't find anything. Any help
would be greatly appreciated.

Converting Cobol data files from one platform to another is hardly rocket >science, just create for each file that is NOT LS a convert program that >takes original file and format, creating a new LS version with all binary >fields set up as display (e.g., pic 9(n) - where n = max. size of original >field regardless of usage of pic or binary etc). Then transfer to new >platform and use another created convert program to do the reverse.

Sounds like a MOVE CORR, at heart... and that's All Ya Gotta Do!

Same applies to replacement rdbms or DMS etc systems but those are a lot >easier if you are lucky.

I cannot speak for others... but for me - usually - 'the harder I work the luckier I get.'

DD

SEEN-BY: 154/30 2320/100 0 1 227/0

From Newsgroup: comp.lang.cobol

On 8/16/2017 9:14 AM, docdwarf@panix.com wrote:

[posted and e-mailed]

In article <e0a46f63-d311-4f65-b0c2-80cd3696cfff@googlegroups.com>,
<saissen.mq@gmail.com> wrote:

On Friday, January 25, 2013 at 2:14:54 AM UTC+5:30, paulsali...@gmail.com wrote:

Hi,

I'm looking for some sample or public COBOL copybook and associated

data files so that I can test some code for converting COBOL data types.

'(S)ome sample or public COBOL copybook and associated data files... so
that I can test some code'.

Different situations may benefit from different approaches. It might help you to post to this newsgroup some of this code you already have so a solution appropriate to the context be generated.

(ancient canine, modern prestidigitation?)

DD

You people do realize that was a 4 year old message you were
replying to. Looks like google is once again spewing garbage.

bill

SEEN-BY: 154/30 2320/100 0 1 227/0

From Newsgroup: comp.lang.cobol

In article <evk1d7Fs7v6U1@mid.individual.net>,
Bill Gunshannon <bill.gunshannon@gmail.com> wrote:

On 8/16/2017 9:14 AM, docdwarf@panix.com wrote:

[posted and e-mailed]

In article <e0a46f63-d311-4f65-b0c2-80cd3696cfff@googlegroups.com>,
<saissen.mq@gmail.com> wrote:

On Friday, January 25, 2013 at 2:14:54 AM UTC+5:30,

paulsali...@gmail.com wrote:

Hi,

I'm looking for some sample or public COBOL copybook and associated

data files so that I can test some code for converting COBOL data types.

'(S)ome sample or public COBOL copybook and associated data files... so
that I can test some code'.

Different situations may benefit from different approaches. It might help >> you to post to this newsgroup some of this code you already have so a
solution appropriate to the context be generated.

(ancient canine, modern prestidigitation?)

You people do realize that was a 4 year old message you were
replying to.

Pshaw... folks run code that hasn't been compiled in 20.

(yes, I know the difference between 'code' and 'executable modules')

Better late than never!

Looks like google is once again spewing garbage.

Who expects different?

DD

SEEN-BY: 154/30 2320/100 0 1 227/0

From Newsgroup: comp.lang.cobol

On 17/08/2017 11:04 AM, Bill Gunshannon wrote:

On 8/16/2017 9:14 AM, docdwarf@panix.com wrote:

[posted and e-mailed]

In article <e0a46f63-d311-4f65-b0c2-80cd3696cfff@googlegroups.com>,
-a <saissen.mq@gmail.com> wrote:

On Friday, January 25, 2013 at 2:14:54 AM UTC+5:30,
paulsali...@gmail.com wrote:

Hi,

I'm looking for some sample or public COBOL copybook and associated

data files so that I can test some code for converting COBOL data types.

'(S)ome sample or public COBOL copybook and associated data files... so
that I can test some code'.

Different situations may benefit from different approaches.-a It might
help
you to post to this newsgroup some of this code you already have so a
solution appropriate to the context be generated.

(ancient canine, modern prestidigitation?)

DD

You people do realize that was a 4 year old message you were
replying to.-a Looks like google is once again spewing garbage.

bill

Well spotted, Bill.

It's just as well really, because none of the responses understood what
he was ACTUALLY trying to do and they were about as much use as roller
skates to a steeplejack.

(Doc gets credit for spotting "all y' gotta do"... As someone who has
spent decades working with databases on different platforms and moving
between them, I can assure you, if you want it done properly, it is far
from simple. Certainly, the tools are better now than was once the case,
but there is still considerable work involved. A "one-time" solution for
this can be manufactured with hammers and long hours; a generic tool to
do it is something that is independent of the age of the dog or how
tricky it is.)

Deciding to "convert" an LS file by writing a program to convert all the numeric fields to display is not really pertinent to someone who is
building a tool that converts COBOL data types to something else.

Understanding the statement of a problem, as always, goes a long way
towards solving it.

Pete.
--
I used to write COBOL; now I can do anything...

SEEN-BY: 154/30 2320/100 0 1 227/0