RTC 3.0.1 z/OS zimport issue

Hi
I'm going to ignore 'in RTC I ran into problem with performance so I ran zimport' as it does not make a lot of sense to me and does not seem to be the primary issue here.
What I suspect has happened is...
1. You ran zImport once and which created a workspace with the component (say c1) in it. Which you then delivered into a stream
2. You ran zImport again and created a second workspace and a second component with the same name.

... now if you stop and think about this for a second.... that second workspace is completely divorced from the first workspace and also the stream you delivered the first workspace to. So although the component name is the same.... it is not the same component. So when you delivered it, you delivered a second component that just happened to have the same name as the first.

Anyway, so my bet is that is the case.... the way to make zImport aware of that first component you delivered is to use the "-s" parameter and specify the stream. zImport will then aware of the stream and will see that it contains a component with the same name as the one it is going to use for it's run and it will reuse that same stream rather than create a new one.

The documentation for this can be improved... Donald can you do me a favor and open an enhancement request for this and i will get it over to our doc team so it can be improved for the next release.

Guy

Hi
I'm going to ignore 'in RTC I ran into problem with performance so I ran zimport' as it does not make a lot of sense to me and does not seem to be the primary issue here.
What I suspect has happened is...
1. You ran zImport once and which created a workspace with the component (say c1) in it. Which you then delivered into a stream
2. You ran zImport again and created a second workspace and a second component with the same name.

... now if you stop and think about this for a second.... that second workspace is completely divorced from the first workspace and also the stream you delivered the first workspace to. So although the component name is the same.... it is not the same component. So when you delivered it, you delivered a second component that just happened to have the same name as the first.

Anyway, so my bet is that is the case.... the way to make zImport aware of that first component you delivered is to use the "-s" parameter and specify the stream. zImport will then aware of the stream and will see that it contains a component with the same name as the one it is going to use for it's run and it will reuse that same stream rather than create a new one.

The documentation for this can be improved... Donald can you do me a favor and open an enhancement request for this and i will get it over to our doc team so it can be improved for the next release


I did use the -s parameter which is why I wondered why it didn't use the same component in the stream. The performance thing caused me to do the split run which came out not as expected. I believe having to run multiple zimports to get all datasets/members imported into multiple folders under a single zComponent project area will be a fairly common situation. Merging the two identically named components after the fact is problematic. So clear examples of how to approach and execute through the situation would be helpful.
Guy

If you used the -s parameter, zimport should have used the component that already existed in the stream you pointed to, instead of creating a whole new one. If it did not, please file a defect so we can collect additional information and investigate further. Thanks!

- John

If you used the -s parameter, zimport should have used the component that already existed in the stream you pointed to, instead of creating a whole new one. If it did not, please file a defect so we can collect additional information and investigate further. Thanks!

- John

After reviewing it again I see the error was mine. I used the -s parameter but had not changed it to the new stream value after I completed some zimports to another stream.

Glad to hear you got it sorted out. Thanks for following up and letting me know!

Glad to hear you got it sorted out. Thanks for following up and letting me know!

I have another question. I have zimported in 8 out of 10 PDS datasets for a specific zComponent project. I am now trying to pull in one of the last ones. In the mapping file I commented out the references to the 8 I have already loaded and then ran the zimport. Now I am getting -- CRHTC0415E Unable to create project because it already exists -- so how do I run to pick up the next PDS and have it added as a separate folder (from the other 8) to the existing zComponent project?

You're hitting a known bug -- 185931: zimport tries to create duplicate project when --stream option specified. It will be fixed in 3.0.1.3.

If you're getting close to the end of the import process and don't have too many more to do, you could try changing your mapping file to import to a new, temporary zComponent project. Once the zimport completes, you could then load the temporary zComponent project, as well as your actual zComponent project into your Eclipse workspace and move the zFolder over. You could then delete the temporary zComponent project from the repository. Please note: you must use the "Move..." context menu option to move the zFolder from the temporary zComponent project to the real one. When I tested this out, if I copied/pasted instead, all the versionable properties (where we store data set definition and language definition associations) were lost. Using "Move..." instead preserved them.

Alternatively, you could go through your support channels -- since you're running into a confirmed bug in the product, they may be able to help get you a fix early.

You're hitting a known bug -- 185931: zimport tries to create duplicate project when --stream option specified. It will be fixed in 3.0.1.3.

If you're getting close to the end of the import process and don't have too many more to do, you could try changing your mapping file to import to a new, temporary zComponent project. Once the zimport completes, you could then load the temporary zComponent project, as well as your actual zComponent project into your Eclipse workspace and move the zFolder over. You could then delete the temporary zComponent project from the repository. Please note: you must use the "Move..." context menu option to move the zFolder from the temporary zComponent project to the real one. When I tested this out, if I copied/pasted instead, all the versionable properties (where we store data set definition and language definition associations) were lost. Using "Move..." instead preserved them.

Alternatively, you could go through your support channels -- since you're running into a confirmed bug in the product, they may be able to help get you a fix early.

Ok - trying to zimport to a new zComponent project. Now I am getting the original error associated with this PDS. This is an SDF II source dataset and I had an error regarding line delimiter so I removed the language association and am now getting ---- File /MNT.SCM.SB.DGIPNL/PPIBALO has line delimiter Platform but the contents contain mixed line delimiters.
Either set the delimiter to NONE or convert the contents to one type of line
delimiter. --- If I don't associate a language - or even if I do associate a language with the input members how do I set the delimiter value? These members have no extensions in the name

Sorry, I haven't seen anything like this before or know what could be causing this. I'd recommend pursuing this through support, so we can investigate further.