Anyway, that didn't work when the machine wasn't so healthy and now that it
is healthy, it still doesn't work. Since then I heard something else about
how that won't work, no matter how healthy the machine is. Anyone know for
sure?
Thanks,
Mike
The data will appear in library QS36 only if you've used the migration
assistant to go from SSP to the OS/400 environment. Otherwise they're
all contained in the M36 object.
I haven't seen anything about accessing the data via Client Access. One
of my clients have the same setup as you describe and needed their S36
data available to OS/400 for queries, etc. My solution used ODF to send
the data from the M/36 to OS/400 where it was further processed to
"de-normalize" it and place it into nice tidy files ready for query.
That solution is still running for them.
Barry
Jason Hansen
mike, in the s/36 environment of os400 "s36" data would live in a 400
library called qs36f by default.
on a 436 where the s36 is running as a guest operating system. the s36 files
do not live "on the 400".
you can use DDM to access a guest s36 file from os/400.
http://www.michsoft.com
j...@michsoft.com
Joseph H. Le Blanc, CCP
QS36F is the library you refer to, and that is only used if you
have migrated S/36 applications to the native 400 NOT using
M36. The migration method will be the only supported method
after V4r4 as I recall.
Peter Kinsman
Pat Barber <mboce...@worldnet.att.net> wrote in message
news:3A7F16FF...@worldnet.att.net...
It would be of much use and it would make you my second-biggest newsgroup
hero of all time.
Thanks,
Mike
Peter Kinsman wrote:
> Some time ago, I set up DDM files to link through the ILAN, but now I have
> written an SSP procedure that uses RUN400 to delete the OS/400 physical file
> and recreate it with the same record length as the System/36 file. It then
> deletes the S/36 file and uses COPYDATA to recreate that so that the DDM
> file on the AS/400 now sees the new data.
Stuart Meier
Priester Aviation
S...@priesterav.com