Re: V5R1 question

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Dennis,

I had backed off on putting people in the SDD because of my mistaken
belief that it was an old carry over from SNADS, OV/400 and other products
obsoleted in this day and age of TCP/IP.  Apparently some functions of
TCP/IP use this also.

Was it a particular TCP/IP service that was giving you the error?

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




Dennis Munro <DMunro@badgerminingcorp.com>
Sent by: midrange-l-admin@midrange.com
08/26/2002 11:55 AM
Please respond to midrange-l


        To:     "Midrange List (E-mail)" <MIDRANGE-L@midrange.com>
        cc:
        Fax to:
        Subject:        V5R1 question



Upgraded from v4r5 to v5r1 on the test machine a couple of weeks ago.  One
of the problems that I encountered was not having users defined in the
system distribution directory to control starting & stopping of TCP/IP.  I
stop IP & end various subsystems every night as part of Day End to make
sure
I have no users still attached & jobs are ended for a clean backup.

Since putting on v5r1, I get the error CPF9006 severity 40 about the user
profile I use to do these operations not being in the system distribution
directory.  Easy enough to put in but what I'm wondering is what part of
the
manual did I not look at where this was discussed?  And what other gotchas
are out there because my test & production systems are different models &
capacities & programs?

I was pretty happy that v5r1 went on without to much fuss.  Service tools
server & security being another item that was a gotcha but it had been
talked about on this list before.

Thanks - Dennis.

Dennis Munro

"I love deadlines.  I especially like the whooshing sound they make as
they
go flying by."  Dilbert's Words Of Wisdom:

Badger Mining Corporation
www.badgerminingcorp.com
dmunro@badgerminingcorp.com
(920) 361-2388


_______________________________________________
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.