on 07-23-2007 10:15 PM
As I understand the process, during an InPlace CPC the original files are renamed to "XXXX&" and the new ASCII XXXX file is created, and the original copied to it.
We are getting very short of disk space, and it would appear both JCDS and "JCDS&" have the full amount of records in them.
At what stage in the process will the original be deleted?
Regards
Steve
Thanks Volker I can see the files being cleared now. I know my disk usage is too high but this just my QA system, newly refreshed from live and we should be getting a new iseries in a few months to start our upgrade.
Part of the problem was due to some large files. On your course I noted that for the unload the recommendation for the number of processes should equal the number of processors.
But on the reload it should be 2 times number of processors. Our QA 270 has 2 so I started 4 processes which seemed to start with the 4 biggest files. 3 of these JCDS EQUI OBJK together account for 33% of our DB! 2 copies of each of these took us up to 90%+.
When I come to do Prod on our 4 way 830, if I start 8 processes I'm not sure if our system will cope with 2 copies of our 8 biggest files.
Is the 2 times number of processors the right way to go?
Is there a way of controlling the order of the file conversions so that it doesn't do all the big ones together?
Regards
Steve
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Stephen,
you can use 1 r3load per cpu during reload as well - if youd DASD is limited perhaps a good idea. I have never seen a "real live situation" where this was necessary ...
Order change:
not official, but it would work: rename the STR files before the CMD files are created to your needs - it will be processed by alphabethe if you did patch the r3setup - but I would normally NOT recommend this change ...
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de
Hi Stephen,
very easy: when the table is converted !
no, joke, but after "CPYF", the primary key and all the indexes need to be created - if this is OK, the old table is deleted.
But, if you are not having 30%+ in this table this should never happen during an InPlace conversion, as the target AFTER conversion is 70% utilization. If you are running with 90%+ this is not very useful at all.
btw: if it hurts too much, you could use CLRPFM right now on the & table - but you would lose the recovery option, if the primary key crashes right now ....
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.