Re: System/36 command from a CL?

["Charles St-Laurent" <dringpiece@xxxxxxxxxxx>]

Hi!

I was talking about converting a S/36 multiple format file to (a) native
file(s) with external description(s), that is not easier as it should be, in
my humble opinion...

Charles


"Ken Sims" <mdrg5003@xxxxxxxxxxx> a écrit dans
le message de news:4.3.2.7.2.20060410125304.00ae9b00@xxxxxxxxxxxxxx
> Hi Charles -
>
> >I don't like the way IBM allows the functionality of multiple format file
> >with X physical files simulating the X different formats of the file and
a
> >file selection program. The ideal solution IMHO is allow multiple formats
in
> >the same physical file, each definition pointing on the same data, and
let
> >the system returns the right format depending on the type code. It is not
> >possible now... The only clean way I know to convert a S/36 multiple
format
> >file to a native file with DDS is to split the S/36 file into many
physical
> >files that corresponds to the different field definitions...
> >
> >It is not what I call a pleasant and easy solution...
>
> I think you're missing the point.
>
> With DDS you can create a file that is just like the file created by
> BLDFILE.  Have one big field for all of the data before the key data.  One
> field for the key data.  And if there is data following the key data, one
> big field for that.
>
> You don't have to change the programs at all.
>
> As long as the programs used the file as internally-described, you can
> still put different formats of data in the file with no problem, just like
> you do now.
>
> Ken
> http://www.kensims.net/
> Opinions expressed are my own and do not necessarily represent the views
> of my employer or anyone in their right mind.
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>