RE: OpsNav access to IFS (was RE: Transfer file using Ops Navigator? )

["jt" <jt@xxxxxx>]

Tom,

I stand corrected.  As I said, I'm not sufficiently familiar with Ops Nav.

I'm in favor of a small memory footprint, also.  But from what I'm hearing,
Netserver isn't quite up to speed, according to what Scott Klement reports
is available on *nix.  So I dunno about only allowing edit through a share,
from a performance POV, although it sounds good from a security POV.


I stand by the rest of my comments...  We're being told:  "it's my way, or
the highway".  Ops Nav is as slow as a pig stuck in mud, but functionality
is being put in Ops Nav that you can't get to any other way.  (Just like
functionality going into SQL, but not DDS.)  This is bull-hocky.  We're
being told "it's too expensive to do it any other way".  Ya, right...  I
code programs...  Sure wish *I* had the option of telling my user's that
kind of crap...

Here's the litmus test...  Does the Ops Nav team EXCLUSIVELY use Ops Nav to
do all their day-to-day work...?!?  If the answer is "yes", then:

Their liars...  or more likely...
They don't actually manage the systems they work on
and/or
They're not familiar enough with Command Entry


I'll get more familiar with Ops Nav...

Will the Ops Nav team get more familiar with how I use a 400?  Will they get
more familiar with CL commands, so get off their "trip" that Ops Nav (or any
GUI!) is the best way to do ALL things...?!?

(BTW, I don't need a recommendation to help out by signing up to assist the
UCD...  Been there, done that...  Never even got so much as a form e-mail,
thanking me for taking the time...  ***I don't have THAT kinda time to
waste, BTW.***)


Thanks for your views.

jt

| -----Original Message-----
| From: midrange-l-admin@midrange.com
| [mailto:midrange-l-admin@midrange.com]On Behalf Of thomas@inorbit.com
| Sent: Wednesday, December 12, 2001 11:30 PM
| To: midrange-l@midrange.com
| Subject: OpsNav access to IFS (was RE: Transfer file using Ops
| Navigator? )
|
|
| Mike:
|
| On Wed, 12 December 2001, "Smith, Mike" wrote:
|
| > ok, i'll concede that, cause i wasn't aware of that, but i'm
| lazy and don't
| > wanna have to install netserver.
| > if i can see that it is there through ops nav then LET ME OPEN
| IT. i want to
| > have my cake and eat it to.
|
| I don't quite understand "install netserver". There's nothing to
| "install" unless you mean any necessary host-server options of
| OS/400 or the networking service on the PC. Of course, if you
| have never installed the host side of things nor PC networking,
| you ain't gonna be pulling anything down to PCs anyway.
|
| As for opening through OpsNav directly... I can edit it now
| (using OpsNav 5.1 at least) by selecting RMB-<Edit>. However, I'm
| not sure that should be allowed. My personal feeling is that it
| should _only_ be allowed through a defined share (mapped drive).
| I'd rather have OpsNav have as small a footprint as possible; and
| since I can map a drive through OpsNav and since I can do
| anything else needed through the mapped drive without executing
| OpsNav in the future, I'd prefer not having OpsNav include the
| support that my Windows desktop already has. Further, I might
| have a more centralized control of authorities if I can rely more
| on share permissions. And if I haven't created a share, it's a
| public way to demonstrate that objects in that directory
| shouldn't be accessed directly from a client.
|
| Tom Liotta
|
| --
| Tom Liotta
| The PowerTech Group, Inc.
| 19426 68th Avenue South
| Kent, WA 98032
| Phone  253-872-7788
| Fax  253-872-7904
| http://www.400Security.com
|
|
| ___________________________________________________
| The ALL NEW CS2000 from CompuServe
|  Better!  Faster! More Powerful!
|  250 FREE hours! Sign-on Now!
|  http://www.compuserve.com/trycsrv/cs2000/webmail/
|
|
|
|
| _______________________________________________
| This is the Midrange Systems Technical Discussion (MIDRANGE-L)
| mailing list
| To post a message email: MIDRANGE-L@midrange.com
| To subscribe, unsubscribe, or change list options,
| visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
| or email: MIDRANGE-L-request@midrange.com
| Before posting, please take a moment to review the archives
| at http://archive.midrange.com/midrange-l.
|