Need help

( CVSSCC , PowerBuilder, UNIX )

Type: Public Status:Closed Created: 03 Mar 09 03:00 Updated: 04 Mar 09 03:00

--> Igor Pushkov (admin) at 04 Mar 09 03:00 writes

1. If you asking how easier to deploy similar changes across several
workstation then the answer will be to grab registry subtree with setting
and deploy it. If you asking about best options for PowerBuilder, then you
will find them in our help.

2. Option to use "reserved checkout mode" is mandatory for PowerBuilder. In
case you will be using concurrent checkout mode it is possible to lost
local modification under certain circumstances. So you better to work in
reserved checkout mode for all files.

3. The only way to deploy newly added object from the initial workstations
to another is manual copy of the pbl file. Unfortunately we still not know
other ways to do this.

--> Laxman Vuppala (user) at 03 Mar 09 03:00 writes

Hi
We are using your product push ok to check out and modify Power Builder
objects from repository CVS-Concurrent Version System.
We need help on these following 3 topics.
1. What is the best practice of selecting the PushOk CVS Proxy
properties?.
2. We have chosen to select or Check the Checkbox for one of the below
described Options.
Reserved checkout mode (explicitly restrict checkout of edited file)
When we did checked/selected this option by every Engineer,
In the example of same object was tried to checkout by two engineers from
two different branches we get error message
[edit aborted]: Files being edited!
What is the best practice of choosing Options in the PushOk CVS Proxy
properties?
3. When we add new power builder objects through puskok what are the best
practice we need to follow by our engineers.
If you can send any help documents on this or puskok product usage it will
be very helpful.

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Need help