I'd like to elaborate on my last statement. When I used the term
"Logically linked", I meant for example:
Once the MIGDB database is complete, the following dataset will be
populated:
>FO DB-MSTR
DATA BASE: MIGDB .PUB .J3K TUE, NOV 3, 2009, 8:16 PM
DATA BASE LANGUAGE ATTRIBUTE: NATIVE-3000
SET NAME:
DB-MSTR,DETAIL
ITEMS:
SVR-UNIQUE, I2 <<SEARCH ITEM>>
DB-UNIQUE, I2 <<SEARCH ITEM, SORT ITEM>>
DB-NAME, X28 <<SEARCH ITEM>>
DB-CREATOR, X8
DB-ACCT, X8
DB-GROUP, X8
DB-BYTES, I4
SQL-NAME, X32
DATAPATH, X128
LOGPATH, X128
DB-SETCNT, I4
DB-RECCNT, I4
DB-MIG, X2
DB-COST, I4
CAPACITY: 60 ENTRIES: 39
>FO DS-MSTR
DATA BASE: MIGDB .PUB .J3K TUE, NOV 3, 2009, 8:16 PM
DATA BASE LANGUAGE ATTRIBUTE: NATIVE-3000
SET NAME:
DS-MSTR,DETAIL
ITEMS:
DB-UNIQUE, I2 <<SEARCH ITEM>>
DS-UNIQUE, I2 <<SEARCH ITEM, SORT ITEM>>
SVR-UNIQUE, I2 <<SEARCH ITEM>>
DS-NAME, X16 <<SEARCH ITEM>>
SQL-NAME, X32
DS-TYPE, X2
DS-RECCNT, I4
DS-RECLEN, I4
DS-BYTES, I4
DS-COST, I4
CAPACITY: 768 ENTRIES: 518
>FO DB-FIELDS
DATA BASE: MIGDB .PUB .J3K TUE, NOV 3, 2009, 8:16 PM
DATA BASE LANGUAGE ATTRIBUTE: NATIVE-3000
SET NAME:
DB-FIELDS,DETAIL
ITEMS:
DS-UNIQUE, I2 <<SEARCH ITEM>>
IFLD-UNIQUE, I2 <<SEARCH ITEM, SORT ITEM>>
DB-UNIQUE, I2 <<SEARCH ITEM>>
SVR-UNIQUE, I2 <<SEARCH ITEM>>
IFLD-NAME, X16 <<SEARCH ITEM>>
IFLD-LEN, I2
IFLD-X, I2
IFLD-Y, I2
IFLD-SUBLEN, I2
SQL-NAME, X32
IFLD-TYPE, X2
SQL-TYPE, X16
IFLD-CVT-METHD, X16
IFLD-MAX-VAL, X64
IFLD-MIN-VAL, X64
CAPACITY: 4932 ENTRIES: 4227
As you can image, with this data you can do many things, like x-ref data
items to datasets, and databases, and simple things like programatically
build batch jobs for Eloquence migrations, maybe some XML output, more
complex SQL scripts, create copylib modules, or compare against you
existing copylib contents. Actually, the these datasets were initially
designed to build SQL scripts.
Michael Anderson,
J3k Solutions
Sr.Systems Programmer/Analyst
832.515.3868
Jim Chance wrote:
> Awesome options!
> Creative and helpful.
> Thanks Tony, Craig & Michael.
> Please allow me to think about my strategy based on this feedback.
>
>
> Michael wrote:
> {snip}
>
>> Now if you compile the programs in question, and direct the coblist to a
>> disc file, you can then write a simple program that reads the coblist,
>> and then DBFINDs in MIGDB which has the image structure logically linked.
>> Michael Anderson,
>>
>
> And now I'll chip in a notion:
>
> Use Michael's suggestion of coblist, and use the MAP information which shows
> for the data division. A little creative work with a text editor and a
> spreadsheet program will at least get you a "did I do it right?" check
> document, and might get you further down the road.
>
> Cross-reference information (which you mentioned in your original post) can
> be requested in the coblist output as well.
>
> With a tab for the Query FO SETS info, and a tap for the MAP info, and
> perhaps a tab for the original COPYLIB text, you might be able to come up
> with a tab for a composite list with all the info necessary to generate the
> target system SQL text as well :)
>
> Final thought: BASIC/3000 is super for this kind of stuff as well. The
> software and manuals were available at one time on Wirt's site - you might
> search the archives if you don't find them right away.
>
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
