Subject: | |
From: | |
Reply To: | |
Date: | Tue, 19 Jun 2012 08:38:16 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
You might want to use the link Francois just gave and get a copy of the
"Using KSAM XL and KSAM 64" manual (or google for it...)
Chapters 3 and 4 seems to cover the areas you have questions about.
Listfile,5 seems to be a rightly nifty thing ;-)
Rather than beat yourself silly trying to get devise a pure cobol solution,
you might be well advised to *augment* what you're doing with some CI
scripts that you call from your program. - d
Donna Hofmeister
Allegro Consultants, Inc.
408-252-2330
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of John Pollard
Sent: Tuesday, June 19, 2012 8:08 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] Cobol: Cobol and HPFOPEN
Thanks for the response.
The reason I need the intrinsics is that Cobol requires that the file be
correctly defined in order to use Cobol to open it.
To open a KSAM file, for example, you must define all the keys for the file
in the Cobol program.
I want to be able to open any input file (or almost any file) without the
program knowing any of the file characteristics until it is opened.
Then I want the Cobol program to be able to create a new output file from
scratch, using only the characteristics of the input file.
So I can't build the file characteristics into the program using Cobol
constructs.
Think of it as similar to what FCOPY does.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|