× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yeah, one could use tar or jar - the latter can be run so as not to create the manifest file that Java expects, I think. Otherwise, it is essentially a zip file. With lots of levels of compression available, too.

And this can be run with QShell, too!

Vern

On 12/16/2010 8:30 PM, Dennis Lovelady wrote:
But the caveat here (and maybe someone already said it; sorry if I missed
it) is that regardless the permissions on your system, when you send them
via FTP they will be set to that system's default umask. Changes made to
permissions on your system will not carry forward elsewhere. If you're
sending another way (scp, for example, or via zip/tar file to be extracted)
things may be different.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Nothing is foolproof to a sufficiently talented fool.


You don't even have to go into the QShell environment - you can run the
qsh command simply from CL, as there

strqsh cmd('chmod 644 filename')

That's it. This always returns a QSH0005 message as a completion
message
by default. You might want to set an environment variable, so that an
error condition comes back as an escape message. The environment
variable is QIBM_QSH_CMD_ESCAPE_MSG and needs to be set to 'Y' to get
the escape message QSH0005 (when return status is> 0)

The first number is permissions for the owner of the object (read/write,
or *RW in CHGAUT, although I don't know if CHGAUT can set the unix
permissions the same way). The second number is for groups - a unix
group, there are some equivalents in IFS. It is read in this case. The
last number is for others - *PUBLIC is exactly the same - and is read
in
this case.

read = 4
write = 2
execute = 1

You add up what you want and use that number. There are several other
syntactical ways to do this in the chmod utility. There's a QShell
manual in InfoCenter.

On 12/16/2010 2:46 PM, fbocch2595@xxxxxxx wrote:
So, you think just strqsh then chmod 644 filename will do it? That's
not too painful, I guess.







-----Original Message-----
From: BMay@xxxxxxxxx
To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>
Sent: Thu, Dec 16, 2010 3:15 pm
Subject: Re: OS400/Unix authority settings


The simplest and fastest way to give them exactly what they want is
to use
he chmod command in Qshell or PASE. So you could use QP2SHELL or
STRQSH
o issue the command "chmod 644 filename"
That's of the top of my head, I am not where I can test it at the
moment.
Brian May
roject Lead
anagement Information Systems
aran, Incorporated
tarkville, Mississippi

fbocch2595@xxxxxxx
ent by: midrange-l-bounces@xxxxxxxxxxxx
2/16/2010 01:57 PM
lease respond to
idrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>

o
idrange-l@xxxxxxxxxxxx
c
Subject
S400/Unix authority settings



Hi Folks, Merry Christmas/Happy Holidays!
I'm working with a biz partner who's requiring the permissions on IFS
iles to be set to
44(rw-r--r--) on files that I send to his system from our AS400's.
What would be the IFS authority settings, if any, that would
correspond to
44(rw-r--r--)? Is there any place to find that info?
Thanks, Frank

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.