At 14:08 18.03.1998 -0700, James T (not Kirk) wrote:
>So we have a Turboimage database on the 3000 which needs one
>(several actually but let's keep it simple) of it's dataset's on the
>9000.  The output file created by the extract program on the 3000
>is 23GB.  The program normally outputs a disc file...

Well, not sure what I am missing here... but what trick are you using
to make the extraction program create a 23 GigaByte disc file? My current
understanding of MPE/iX is/has a 4 GB file limit... Do you already have
an early version of release 7.0 or alike??

>I have no idea of how to tell the program/Unix that the input is
>labelled.  Only labels I've worked with were IBM OS/VS blah, blah.

I do not believe that Unix knows how to deal with ANSI or IBM labeled
media types. Sounds like you would probably have to create "just another
filter/tool for the dd/cpio/ftio/etc-family.

>So, is there a simple way to move these files that I'm not aware of?

If your data extraction tools is able to write to a MSG file then you
might be able to use FCOPY to pick up chunks and direct them to tape.
Something like...

 BUILD MYMSGF;DISC=___;REC=___
 FILE MYTAPE;DEV=___;REC=___
 FCOPY FROM=*MYMSGF;TO=*MYTAPE;SUBSET=0,numrecs

Haven't tried this myself, though. Might have a number of gotchas. For
example you'd probably need to start the writing job/session before the
first FCOPY open the MYMSGF successfully. It might also need a second
reader to dummy-open then MYMSGF so that there is always at least one
potential reader (otherwise the first FCOPY closing the file might make
the writer complain instead of just block).

Lars.

PS: With IMAGE/SQL it might even be possible to UNLOAD EXTERNAL in ISQL.