You'll discover that there's no real NEED for correspondence between Image's
descriptions and COBOL's descriptions. Before Adager, it was such a pain to
change a database that you'd commonly see stuff like
SET CARDFILE
ITEM KEY X10
ITEM OTHERSTUFF X80
with otherstuff defined any which way for COBOL. How does that work?
Typical COBOL programs use Image's @ list, thus getting a buffer containing
the entire record image, which the COBOL program can describe / manipulate
any way it desires.
And it works just fine until you try to do any Image-hip utility activity.
While on this subject, does anybody have the magic cobol program that will
read a copybook and write a program to produce comma-delimited-values
output? (I'll pay cash!)
Tracy Pierce
> -----Original Message-----
> From: Lynn Price [mailto:[log in to unmask]]
> Sent: Wednesday, August 14, 2002 12:13 PM
> To: [log in to unmask]
> Subject: COBYLIB vs ADAGER
>
>
> When I look into my coplib using COBEDIT, I see some fields
> defined as =
> Pic X(1). I needed them to be PIC X(2) so I decided to use Adager's =
> Change Item command, but when it shows me the current definiton for =
> these fields, each are already defining it as a PIC X(2). Why would =
> listing the dataset in COBEDIT show a different definition
> than I see =
> when I try to change the item in Adager?
>
> Also, I have a field that I would like to define as S9(6)V99 in my =
> copylib (which is currently Pic X(8)), but Adager won't let
> me use S9. I =
> looks like I am suppose to use J, but I am not sure what
> S9(6)V99 will =
> equate to using the J character (or why Adager won't let me
> use S9. Any =
> suggestions? Perhaps I don't need to use adager, but I am not
> sure what =
> else to use. Thanks!
>
>
> Lynn Price
>
> * 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 *
|
