I've tried to create DDM files within the same system, that would be
nice ;-) ... but I can't get them to work. Is it possible?
What's the case:
I've got a very big physical with two logicals is library PRODDTA.
I need the same data in the libraries TESTDTA and DEVDTA.
How much space is used when a create logical with the same name and
key as the physical plus a copy of the two logicals en the libraries
TESTDTA and DEVDTA?
Ron
BTW: THIS ARTIKEL IS THE SAME AS THE ARTIKEL WITH SUBJECT: "How much
space is used when copying a logical to different libraries?"
--
Ron Kou...@IAEhv.Nl
When you create a logical file, the system searches for an existing access
path i.e. same key fields and select/omit. So if the access path exists, the
new logical file does not take so much space.
An example from our system :
PF has 2259361 records.
The first LF that owns the access path has 4 key fields without select/omit.
The object size is 47214592 bytes.
The second LF has the same access path and its object size is ..... 20480
bytes !!!!
HTH
Regards
--
Christian GSTALDER
Ron Koudijs a écrit dans le message <37b0e9e4...@nntp.iaehv.nl>...
Create two APPC-Controller´s with linktype=*LOCAL
Martin Burgsmüller
burgsm...@wiedemann.de
Ron Koudijs schrieb in Nachricht <37b0e9e4...@nntp.iaehv.nl>...
>Hello,
>
>I've tried to create DDM files within the same system, that would be
>nice ;-) ... but I can't get them to work. Is it possible?
>
>What's the case:
>I've got a very big physical with two logicals is library PRODDTA.
>I need the same data in the libraries TESTDTA and DEVDTA.
>How much space is used when a create logical with the same name and
>key as the physical plus a copy of the two logicals en the libraries
>TESTDTA and DEVDTA?
>
>Ron
>
>BTW: THIS ARTIKEL IS THE SAME AS THE ARTIKEL WITH SUBJECT: "How much
>space is used when copying a logical to different libraries?"
>
>--
>Ron Kou...@IAEhv.Nl
Yes!
Create two APPC-Controller´s with linktype=*LOCAL
Martin Burgsmüller
burgsm...@wiedemann.de
But:
Theres also a way in SQL. (without APPC)
This are DDMF , wich allow you to access to members over SQL:
create alias lib/filealiasname for lib/file(mbr)
This are DDMF .
The clou:
If you use dspddmf you can't see wich member you use. (IBM bug?)
But there's a way you can use:
select * from qsys2/systables where table_type= 'A' ...
Matthias
--
Thomas Kitze <thomas...@192.168.2.10> wrote in message
37b020a1.118769130@news...
......
>Thomas,
>With SQL I think there is no way to use different members by the same ALIAS
>definition (i.e. DDMF) depending on the process, as you can do with "normal"
>DDMF. This is why the CREATE ALIAS always defines a member in the resulting
>DDMF.
>Am I wrong?
You can optionally hard code the member name when you create the DDM
file. Then the DDM can only "see" that member.
If you do not specify a member name in the DDM create, the do a normal
file override (OVRDBF) on the source system just as if you were
dealing with a local file. The override will be passed thru the DDM
connection to the target system.
Denny
______________________________________
NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47,
Chapter 5, Subchapter II, 227
Any and all nonsolicited commercial e-mail
sent to this address is subject to a download and
archival fee in the amount of $500 US.