We help IT Professionals succeed at work.

chmod and Sun Workshop Teamware

lhgarrett asked
Last Modified: 2013-12-27
I'm using sccs commands with Sun Workshop Teamware.  I have Unix scripts that I have written for C shell.

How do I configure the file under sccs so that it retains execuatble permissions when I check the file out, and then back in?

Currently I'm doing a chmod +x every time I check the file back in because sccs (at least for now) removes the execute permissions (similar to chmod 444)
Watch Question

Top Expert 2005

It looks to me that if you change the mode of the sccs file (chmod ugo+x SCCS/s.some-file), then from then on the file will check out as executable.
As you said the execute permissions will not be retained once you check out
A silly answer i can suggest you now to avoid "chmod +x" every time is to write a wrapper or a shell script or a perl script to do the chmod +x for you every time.

This is what i follow now.I also faced the same problem like u.Now the chmod is done automatically by my script every time whne i check out.


Top Expert 2005

Not so fast cartoon... I've just checked what I suggested with Teamware and the executable mode is preserved across checkin/checkout cycles. If your instance is not behaving that way it sounds like an sccs or Teamware bug. Is your's up to date patch wise?


> write a script to do the chmod +x for you every time

I'd like to allow sccs to maintain the executable mode on a file-by-file basis for me. Ideally, I should only have to set the mode once.


> chmod ugo+x SCCS/s.some-file

Is there an sccs command (or a workspace command) that I should use to perform this function?
Top Expert 2005

I can't find any sccs command that will do it, nor can I find any way from within Workshop to do it. What I did was to use a terminal window and cd to the "Workspace" directory and run the "chmod ugo +x SCCS/s.some-file" there.

One other thing to note is that if the file is executable when it is first checked in, it retains that mode.


> If your instance is not behaving that way it sounds like an sccs or Teamware bug

My version of sccs only retains the permissions on the SCCS/s.* files. The actual files' execute permission is destroyed (on delget or unedit). I get the same problem from the Teamware GUI, or if I checkout and checkin on the commandline with the following commands:

    % sccs edit filename
    % sccs delget filename

How can I determine which version of sccs I'm using. When I do help from Teamware, I get:

   Teamware 2.0 10/31/96

What version are you using? Thanks!
Top Expert 2005

Mine is Teamware 2.1 12/15/98 on Solaris 2.7. Relevant patches installed include:

106748-04 - /usr/ccs/bin/sccs and /usr/ccs/bin/make patch
107354-01 - Patch for Teamware 21

So far as I know you can't ask sccs for it's version. Which Solaris are you using? Knowing the version I can tell you what sccs and Teamware patches exist.


I am running Solaris 2.6:

   % uname -X
   System = SunOS
   Release = 5.6
   KernalID = Generic_105181-05

Top Expert 2005

I haven't forgotten about this. I've managed to duplicate your problem on a 2.6 system. The interesting thing is that it looks like it may not actually be an sccs problem. I can use the binaries from a 2.7 system (export /usr/ccs from 2.7 where it works correctly & nfs mount it on 2.6) and still have the problem. The only thing that I can see at this point that might explain it is some difference in libc between 2.6 & 2.7.

More soon, I hope...
Top Expert 2005
This one is on us!
(Get your first solution completely free - no credit card required)


> I've done everything that I can think of, including bringing a 2.6 box totally up to date w/respect to patches

Thanks! I guess that's the way it is... If you have the ability to (or desire to ) write a bug report, I appreciate it.

In the mean time it's appropriate to award points for all of you hard research! Thanks again!
Top Expert 2005

I'm in the process of filling a bug report. The initial response was "sccs can't do that, see bug ID nnnnn". Then when I explained that it works in Solaris 8 and that the binaries from 8 worked properly on 2.6 & 2.7, there was this really long pause and an "let me check on that and call you back", so we'll see.


> I'm in the process of filling a bug report

Thanks, I'm glad they are checking into it... From a user's perspective, persistence of execute permissions across checkin/checkout is about as basic as it gets; it should be supported.  :-)

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.