zImport log
We must load a big number of members (about 2500 members) from our zOS enviroment to RTC, and for this operation we use scm zimport utility.
We run the following command:
scm zimport --hlq FESVILL --mapfile /u/F4296/mapping.txt --projectarea Findomestic -s "Stream zImport" -r https://rtc1.frontend.findomestic.local:9443/ccm -u f4296 -w "Workspace zImport" -v
Despite the -v option we can't see the load progress: we can see at the begin the library scan and to the end (after about 2 hours) the resutl of the load.
How can we see the zimport activity during the load phase?
Lorenzo
We run the following command:
scm zimport --hlq FESVILL --mapfile /u/F4296/mapping.txt --projectarea Findomestic -s "Stream zImport" -r https://rtc1.frontend.findomestic.local:9443/ccm -u f4296 -w "Workspace zImport" -v
Despite the -v option we can't see the load progress: we can see at the begin the library scan and to the end (after about 2 hours) the resutl of the load.
How can we see the zimport activity during the load phase?
Lorenzo
3 answers
We must load a big number of members (about 2500 members) from our zOS enviroment to RTC, and for this operation we use scm zimport utility.
We run the following command:
scm zimport --hlq FESVILL --mapfile /u/F4296/mapping.txt --projectarea Findomestic -s "Stream zImport" -r https://rtc1.frontend.findomestic.local:9443/ccm -u f4296 -w "Workspace zImport" -v
Despite the -v option we can't see the load progress: we can see at the begin the library scan and to the end (after about 2 hours) the resutl of the load.
How can we see the zimport activity during the load phase?
Lorenzo
Hi Lorenzo,
The zimport command does not currently offer a way to monitor the progress of the upload of the individual members being imported. If this is a feature that would be useful to you, I'd encourage you to submit an enhancement request, so it can be investigated and prioritized.
Thanks!
Hi John,
thanks for the reply.
I have another question: we have to copy our zOS enviroment to RTC every night to bring the daily zOS changes in RTC repository.
So we start zImport every night with the same parameters: same Partitioned Data Set in zOS and same Repository Workspace and Stream in RTC.
In this case, how does zImport work? It manages only the changed members in zOS enviroment or manages all the members every time?
For example: if during the day we have modified only 10 members on zOS library, how long will the nightly zImport? Always the same 2 hours or much less?
Lorenzo
Hi Lorenzo,
The zimport command does not currently offer a way to monitor the progress of the upload of the individual members being imported. If this is a feature that would be useful to you, I'd encourage you to submit an enhancement request, so it can be investigated and prioritized.
Thanks!
thanks for the reply.
I have another question: we have to copy our zOS enviroment to RTC every night to bring the daily zOS changes in RTC repository.
So we start zImport every night with the same parameters: same Partitioned Data Set in zOS and same Repository Workspace and Stream in RTC.
In this case, how does zImport work? It manages only the changed members in zOS enviroment or manages all the members every time?
For example: if during the day we have modified only 10 members on zOS library, how long will the nightly zImport? Always the same 2 hours or much less?
Lorenzo
We must load a big number of members (about 2500 members) from our zOS enviroment to RTC, and for this operation we use scm zimport utility.
We run the following command:
scm zimport --hlq FESVILL --mapfile /u/F4296/mapping.txt --projectarea Findomestic -s "Stream zImport" -r https://rtc1.frontend.findomestic.local:9443/ccm -u f4296 -w "Workspace zImport" -v
Despite the -v option we can't see the load progress: we can see at the begin the library scan and to the end (after about 2 hours) the resutl of the load.
How can we see the zimport activity during the load phase?
Lorenzo
Hi Lorenzo,
The zimport command does not currently offer a way to monitor the progress of the upload of the individual members being imported. If this is a feature that would be useful to you, I'd encourage you to submit an enhancement request, so it can be investigated and prioritized.
Thanks!
Hi Lorenzo,
The zimport subcommand was designed more for use as a one-time mass import tool, to get existing code from MVS data sets into RTC's SCM (where it could then be worked with via the RTC Eclipse client, the ISPF client on z/OS, or with an integrated RDz and RTC client) than as a tool to perform daily copies into the repository. As such, zimport will always re-share all the members specified for import.
Since you're using the "-w" option to perform these imports to the same repository workspace (rather than omitting it and having zimport create an entirely new one each time), the change sets that zimport ends up creating will be sane: if only 10 members have been modified since the last invocation of zimport, the change set created as a result of the next zimport run will only contain those 10 modifications. However, I would not expect this to manifest itself as any time savings in subsequent zimport runs.
The zimport subcommand was designed more for use as a one-time mass import tool, to get existing code from MVS data sets into RTC's SCM (where it could then be worked with via the RTC Eclipse client, the ISPF client on z/OS, or with an integrated RDz and RTC client) than as a tool to perform daily copies into the repository. As such, zimport will always re-share all the members specified for import.
Since you're using the "-w" option to perform these imports to the same repository workspace (rather than omitting it and having zimport create an entirely new one each time), the change sets that zimport ends up creating will be sane: if only 10 members have been modified since the last invocation of zimport, the change set created as a result of the next zimport run will only contain those 10 modifications. However, I would not expect this to manifest itself as any time savings in subsequent zimport runs.