agentsvn SccCheckout appears to have failed in PB12

[michfranceschini]

I just installed Agent SVN, trial version 2.73c in a clean VMware Windows 7 workstation with Powerbuilder 12.1.
For this test, I used the Example applications of Powerbuilder 12.1 under C:\Sviluppo\ExampleAppLoc.
I configured the agent SVN to work in C:\Sviluppo\Example App_loc_svn: the configuration procedure has created the repository successfully.
I added 3 objects to the repository: target, application and a datawindow successfully.
When, I try to checkout the datawindow, I get the following error:
SccCheckout for C:\Sviluppo\ExampleAppLoc\d_event_list.srd appears to have failed.
The Powerbuilder IDE doesn't show any error or checkout information of the datawindow.

In attachment, I send You the log file and a word document with the screenshot of the powerbuilder SCC configuration window, the AGENT SVN configuration window and 2 windows of the SVN repository information.
Can You help me to fix this error ?
Regards.
Michele.

[jussij]

> In attachment, I send You the log file and a word document
The first issue is your log file is in word document format and not as a text log file.

Agent SVN will create a text log file showing the issues so you need to make sure you submit a text log file if you are seeing an issue.

Here is a link that describes how to create a text log file to identify an issue:

viewtopic.php?f=11&t=7552

Follow the reply to that message to see how to create a Agent SVN log file.

> Can You help me to fix this error ?
As a possible fix would suggest trying this PowerBuilder tutorials found here:

https://www.zeusedit.com/agent/ide/pb/classic.html

If you follow those tutorials you should see that Agent SVN will work with PowerBuilder.

That will also show you how Agent SVN actually works with PowerBuilder.

Cheers Jussi

[michfranceschini]

Dear Jussi,
thank You for the prompt answer, I appreciated Your suggestions.

First of all, about the format of the log file, I've sent in attachment 2 files: the file named pbscc120.7z contains a log file in txt format that's what I found in the application workspace directory. The other attachment, is in word format because I described in it the configuration of the installation.
About the PowerBuilder tutorials, I read it and that's is a little bit old because the AGENTSVN configuration window I'm using is showing more other fields and checkboxes than what I can see in the tutorial.
Awaiting You're help, I'll read one more time the tutorial to see if I can sort out from this issue.
In the meantime, I greet You.
Yours.
Michele.

> In attachment, I send You the log file and a word document
The first issue is your log file is in word document format and not as a text log file.

Agent SVN will create a text log file showing the issues so you need to make sure you submit a text log file if you are seeing an issue.

Here is a link that describes how to create a text log file to identify an issue:

viewtopic.php?f=11&t=7552

Follow the reply to that message to see how to create a Agent SVN log file.

> Can You help me to fix this error ?
As a possible fix would suggest trying this PowerBuilder tutorials found here:

https://www.zeusedit.com/agent/ide/pb/classic.html

If you follow those tutorials you should see that Agent SVN will work with PowerBuilder.

That will also show you how Agent SVN actually works with PowerBuilder.

Cheers Jussi

[michfranceschini]

Hi Jussi,
following Your suggestions, I found the reason of that error:
the checkbox "lock files on check out" had not been selected.
I just selected it and the error desappeared: I'm sending You in attachment the log with many other activities I could ended successfully.

Before closing the issue, I would like to ask You one more question:
Could You explain the meaning of the checkbox "lock files on check out" and tell me if it could affect any activity in a shared environment ?
Awaiting an answer, I remain.
Best regards.
Michele.

> In attachment, I send You the log file and a word document
The first issue is your log file is in word document format and not as a text log file.

Agent SVN will create a text log file showing the issues so you need to make sure you submit a text log file if you are seeing an issue.

Here is a link that describes how to create a text log file to identify an issue:

viewtopic.php?f=11&t=7552

Follow the reply to that message to see how to create a Agent SVN log file.

> Can You help me to fix this error ?
As a possible fix would suggest trying this PowerBuilder tutorials found here:

https://www.zeusedit.com/agent/ide/pb/classic.html

If you follow those tutorials you should see that Agent SVN will work with PowerBuilder.

That will also show you how Agent SVN actually works with PowerBuilder.

Cheers Jussi

[jussij]

Could You explain the meaning of the checkbox "lock files on check out"

What this option does is apply a file lock to the file after it has been checked out.

That lock is then automatically removed when the file is checked in.

This feature is there mimic other sources controls that offered that behaviour.

and tell me if it could affect any activity in a shared environment ?

The idea behind locking is to serialize access to a particular file.

It eliminates the chance that two or more people are editing the same file at the same time, which then means it's also impossible to create a merge conflict.

So with that option off, those two side effects then become possible.

I found the reason of that error: the checkbox "lock files on check out" had not been selected.

I would have thought this was not required but I'l take a look at the log to see what might be causing the issue.

Now this option does change the SCC_STATUS_LOCKED file status.

So it might be PowerBuilder is looking for that file locked status and rejecting the check-out if it finds that status missing.

Now I'm no PowerBuilder expert but this could be because PowerBuilder files are binary and that makes then impossible to merge.

With locking in place PowerBuilder is making sure it has eliminated that possible issue.

Cheers Jussi

[jussij]

On the PowerBuilder page found here: https://docs.appeon.com/pb2019/pbug/ch03s04.html

It states, "The PowerBuilder SCC API does not let you check out an object that you or someone else has already checked out".

This tells me PowerBuilder does not allow two people to edit the same file at the same time, which is effectively the same behaviour as the Agent SVN locking feature.

But on that same page there is this reference to a change that can be made to the PB.ini file that changes this behaviour:

SccCheckoutNoLock

0 or 1 (1 is default for MKS Source Integrity, 0 for all other providers

Based on known defaults for the SCC provider you are using, PowerBuilder determines whether locks are added in source control to
objects that you check out. You can override the default setting for some SCC providers by adding this parameter and assigning a different
value. If the SCC provider permits checkouts of objects without locking them, a value of 1 means that no locks are added for objects that
you check out. A value of 0 makes sure that locks are added for these objects.

If I'm reading this correctly, the default is zero (i.e. all other providers) meaning by default PowerBuilder is expecting the file to be locked on check-out.

So, by changing that PowerBuilder option to one should mean locks are no longer required and then a PowerBuilder check-out should be possible without needing to enable that Agent SVN locking option.

Cheers Jussi

[michfranceschini]

Hi Jussi,
about Powerbuilder 12 checkout, I was able to checkout an object from 2 different users (the users are named prova02 and prova01 in SVN).
After checked out from the second user, i received a message in Powerbuilder as follows:
>The above file is currently checked out and locked by the following user: prova02
>and the current user id for this session is : prova01
>If You continue with the ckeck out a file conflict might be created and these will need to be resolved prior to file checked in.
>If a conflict is created a merge utility will be needed to resolve the conflict.
>Do You want to break the lock and continue with the check out ?

Since I don't want to break the lock and don't want to allow anyone to check out an object if it's been already ckecked out from somebody else, can You help me to understand how can I configure Powerbuilder to solve this issue ?

Best regards.
Michele.

[jussij]

Hi Michele,

Do You want to break the lock and continue with the check out?

FYI this message is being displayed by Agent SVN and it is presenting this message as a warning to the user.

Since I don't want to break the lock and don't want to allow anyone to check out an object if it's been already ckecked out from somebody else, can you help me to understand how can I configure Powerbuilder to solve this issue?

I'm not overly familiar with how PowerBuilder works, but on this PowerBuilder page: https://docs.appeon.com/pb2019/pbug/ch03s04.html

There is mention of this option: SccMultiCheckout

I would guess this option might change that PowerBuilder behaviour.

Cheers Jussi