UDP to save and process file on local client machine

[Jarus Bosman]

Good day,

This thread refers.

I have a UDP where I would like to process a Harvest item (execute a program or compiler against it, copy it to various locations etc.).

It's working for my UDP's that run on agents, because I pass the "Version" system variable and process it to get the file name. From there I'm able to process the file normally, because I keep reference directories in sync on those agent servers.

I would now like to do the same from a UDP on a local client machine. How will I achieve this, since I can't keep a reference directory on the local machine? I've thought of invoking "hco" for read (Harvest check-out for read) to the client machine as a pre-linked UDP, but I don't have a system variable for the file name (which is the problem I have in the thread mentioned above) to pass to the "hco" program.

Another option is to invoke a local batch script, passing the "version" variable, then extract the filename from the variable, then invoking hco, and then continuing with the rest of my processing, but this just seems excessive to achieve a relatively simple task. 

Regards,

------------------------------
Jarus Bosman
Senior Software Developer
State Information Technology Agency
South Africa
------------------------------

[Balakrishna Shantamurthy]

Hi Jarus,

 

Thanks for the detailed notes on the usage.

 

We have noted two problems

 

1.When you say , can't keep a reference directory on a local machine .We suggest that you can execute check out for browse on the local reference directory as a one time activity 

so that the repository files and the local file system are synchronised.

 

Later than you can execute hco -sy (Check out - synchronise) to the same folder so that only those files which got changed are updated in the local file system

This can also be done through a post link UDP which can include hco -sy

 

2.There is a system variable [file] ,which we think you might be aware

  Is it a possibility to include it as a POST LINK UDP to the Check Out for Browse (when used for sync operations ) or even browse operations

 

NOTE : system variable [file] can be used as "[file]" .

"[file]" evaluates to "file name 1 file name 2 file name 3..."

 

3.If the check out for update is performed on a REMOTE machine through an agent ,then you can just have a client file system on LOCAL machine just for synchronise operations

 

If the check out for update needs to be on SAME LOCAL MACHINE , when you may choose separate client file system for Update and Browse(Sync) operations on the LOCAL machine 

 

4. A sample execution of Check out for sync to the local file system with UDP script calling [file] as one of the arguments is shown below for example

 

Step#1 :The local file system and repository are in sync- Achieved through Check out for Browse

Step#2 :Include changes only in say ,2 files ,examples(hci10 and hci11).There are no changes to other files.

Step#3 : Execute Check out for sync with UDP referring to "[file]" arguments

Step#4 : The changed files are displayed as shown below

ARG1=" WIN-CNPB41269VU\\C:\co24\Repo2\hci10.txt WIN-CNPB41269VU\\C:\co24\Repo2\hci11.txt "

 

EXAMPLE of OUTPUT log from workbench exection

 

---------- Begin  <Check Out for Browse>  Process ---------------

I00020052:  No need to update file C:\co24\Repo2\hci41.txt from repository version \Repo2\hci41.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci50.txt from repository version \Repo2\hci50.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci1.txt from repository version \Repo2\hci1.txt;2.

I00020052:  No need to update file C:\co24\Repo2\hci34.txt from repository version \Repo2\hci34.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci36.txt from repository version \Repo2\hci36.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci37.txt from repository version \Repo2\hci37.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci31.txt from repository version \Repo2\hci31.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci5.txt from repository version \Repo2\hci5.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci23.txt from repository version \Repo2\hci23.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci32.txt from repository version \Repo2\hci32.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci4.txt from repository version \Repo2\hci4.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci28.txt from repository version \Repo2\hci28.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci39.txt from repository version \Repo2\hci39.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci16.txt from repository version \Repo2\hci16.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci8.txt from repository version \Repo2\hci8.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci46.txt from repository version \Repo2\hci46.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci29.txt from repository version \Repo2\hci29.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci2.txt from repository version \Repo2\hci2.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci30.txt from repository version \Repo2\hci30.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci14.txt from repository version \Repo2\hci14.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci0.txt from repository version \Repo2\hci0.txt;5.

I00020052:  No need to update file C:\co24\Repo2\hci17.txt from repository version \Repo2\hci17.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci12.txt from repository version \Repo2\hci12.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci42.txt from repository version \Repo2\hci42.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci24.txt from repository version \Repo2\hci24.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci43.txt from repository version \Repo2\hci43.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci40.txt from repository version \Repo2\hci40.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci49.txt from repository version \Repo2\hci49.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci19.txt from repository version \Repo2\hci19.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci13.txt from repository version \Repo2\hci13.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci15.txt from repository version \Repo2\hci15.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci44.txt from repository version \Repo2\hci44.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci35.txt from repository version \Repo2\hci35.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci45.txt from repository version \Repo2\hci45.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci47.txt from repository version \Repo2\hci47.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci38.txt from repository version \Repo2\hci38.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci9.txt from repository version \Repo2\hci9.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci25.txt from repository version \Repo2\hci25.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci33.txt from repository version \Repo2\hci33.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci48.txt from repository version \Repo2\hci48.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci20.txt from repository version \Repo2\hci20.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci22.txt from repository version \Repo2\hci22.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci3.txt from repository version \Repo2\hci3.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci6.txt from repository version \Repo2\hci6.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci27.txt from repository version \Repo2\hci27.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci18.txt from repository version \Repo2\hci18.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci7.txt from repository version \Repo2\hci7.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci26.txt from repository version \Repo2\hci26.txt;0.

I00020052:  No need to update file C:\co24\Repo2\hci21.txt from repository version \Repo2\hci21.txt;0.

I00020110: File \Repo2\hci10.txt;3 checked out to WIN-CNPB41269VU\\C:\co24\Repo2\hci10.txt.

I00020110: File \Repo2\hci11.txt;2 checked out to WIN-CNPB41269VU\\C:\co24\Repo2\hci11.txt.

C:\Windows\system32>ECHO ARG1=" WIN-CNPB41269VU\\C:\co24\Repo2\hci10.txt WIN-CNPB41269VU\\C:\co24\Repo2\hci11.txt " 

ARG1=" WIN-CNPB41269VU\\C:\co24\Repo2\hci10.txt WIN-CNPB41269VU\\C:\co24\Repo2\hci11.txt "

I00060052: UDP execution was successful.

I00060080: Check out summary: Total: 51; Success: 51; Failed: 0; Not Processed: 0.

---------- End  <Check Out for Browse>  Process ---------------

 

 

 

Kindly review  and let us know if any of this information will help you.

 

Regards,

Balakrishna

[Jarus Bosman]

Hi Balakrishna,

The "hco" action requires a viewpath parameter. The [viewpath] system variable is not available from a UDP, only check-in and check-out. When I try to use it from my UDP, Harvest responds with "Missing Option or Argument for: -vp"

------------------------------
Jarus Bosman
Senior Software Developer
State Information Technology Agency
South Africa
------------------------------

[Balakrishna Shantamurthy]

Hi Jarus,

Thanks for the response.

We are reviewing and will get back with a response on this.

Regards,

Balakrishna

[Balakrishna Shantamurthy]

Hi Jarus,

Thanks for your patience.

Can we have a quick call this week to discuss further on this and then we will try to assist you .

Please let us know and we will initiate a mail communication regarding date/timing.

Regards,

Balakrishna

[Jarus Bosman]

Hi Balakrishna,

Yes, absolutely. Let's discuss a time via email like you suggested.

Kind regards,

Jarus

------------------------------
Jarus Bosman
Senior Software Developer
State Information Technology Agency
South Africa
------------------------------

[Balakrishna Shantamurthy]

Hi Jarus,

Thanks for the response.

I have sent an e-mail communication proposing the dates to meet.

Please review and let us know.

Regards,

Balakrishna

[Balakrishna Shantamurthy]

Hi Jarus,

Thanks for joining the call today and clarifications

Please do send the snippets of your usage in a format possible for you.

It seems you are looking at viewpath system variable availability from the UDP definition scope

Presently ,it fetches value only during Check out and Check in operations

We are reviewing the possibility and will keep you posted 

Please do share the usage snippets for detailed context and next steps discussion

Regards,

Balakrishna

[Milton Huston Jr]

Is "hrefresh" still available? That utility should be able to support a reference dir on a local machine.

[Jarus Bosman]

Hi Milton, I can't find anything in the documentation about using hrefresh with a local client directory.

------------------------------
Jarus Bosman
Senior Software Developer
State Information Technology Agency
South Africa
------------------------------