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


  1.  Home
  2. MIDRANGE-L
  3. May 2019

RE: QNFSNLMD won't let system end to restricted state

5770-UME V1R4M0 CIM server is configured as an auto-start service when doing scratch install of IBM i 7.2 and later system.

I did a V7R1 to V7R3 upgrade, I'm not sure how it got installed, It may have been part of my DSLO image.
I definitely never configured anything for this or set it to start, so auto start was added automatically in QUSRSYS/QATOCSTART.

Display Physical File Member
File . . . . . . : QATOCSTART Library . . . . : QUSRSYS
Member . . . . . : SERVERS Record . . . . . : 20
*...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+....2....+....3
A*CIMOM *YESQUME QUMECTLCIMCIMOM QIBM_CIMOM

I did finally find it in the TCP/IP server list, it's under user defined servers.

QUMECIMOM is the only job I have running related to CIM, but I don't think it is being used for anything at this time.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Tuesday, May 28, 2019 9:02 AM
To: Midrange Systems Technical Discussion
Subject: RE: QNFSNLMD won't let system end to restricted state

How to tell if CIMOM is being used? Not really sure. However this information may be useful.
SELECT *
FROM QSYS2.NETSTAT_JOB_INFO
where job_name like '%QUME%'
;
Look up that local port name and compare that to
https://en.wikipedia.org/wiki/Web-Based_Enterprise_Management
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzatl/rzatlkickoff.htm

If IBM had this to do over I wonder if there'd be a 5770UME or if it would be an IBM repo of the open source 1.4 version?

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Tuesday, May 28, 2019 8:44 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: QNFSNLMD won't let system end to restricted state

Rob,

And failure to heed the warnings about CIMOM may result in the loss of telnet.
https://www-01.ibm.com/support/docview.wss?uid=nas8N1018955

Do you why we don't see CIMOM appear in the TCP/IP server list.
I do see it in the QUSRSYS/QATOCSTART.
QUMECIMOM is the job running on our V7R3 system.
How do I know if CIMOM is being used or not?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Tuesday, May 28, 2019 7:55 AM
To: Midrange Systems Technical Discussion
Subject: RE: QNFSNLMD won't let system end to restricted state

Some people have found that failure to end it this way can cause bad effects, even on the next IPL.
Obviously I've had some issues with the NFS stuff.
And failure to heed the warnings about CIMOM may result in the loss of telnet. But I'm sure you don't know anyone using 5250 anymore. ;-)

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Tuesday, May 28, 2019 7:46 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: QNFSNLMD won't let system end to restricted state

Keep in mind that this ain't OS/400 anymore and ENDSBS will not end everything to restricted state even if you get the QSYSOPR message saying so.
You must end TCP/IP first.
We bring it down in this fashion:
End user applications
ENDWTR *ALL
UNMOUNT TYPE(*ALL) MNTOVRDIR(*ALL)
ENDHOSTSVR *ALL
EXPORTFS OPTIONS('-U -A')
ENDNFSSVR SERVER(*ALL)
If the ENDNFSSVR fails try running it again.
ENDTCPSVR *MGTC
ENDTCPSVR *CIMOM
WRKACTJOB JOB(QUME*)
Ensure that the jobs associated with *CIMOM, the QUME* jobs, have ended. You might have to wait a little.
Write down time. __________________
ENDTCP


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Joe Pluta
Sent: Monday, May 27, 2019 8:55 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: QNFSNLMD won't let system end to restricted state

Thanks, Jack.  Yes, I tried that and ENDNFSSVR responded that it ended all the NFS servers successfully *except* the lock manager.  That didn't end "in time".

On 5/27/2019 5:02 AM, Jack Kingsley wrote:
Have you tried adding endnfssvr before the ipl.

On Mon, May 27, 2019 at 1:15 AM Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
wrote:

I suspect that's probably the case, Evan, but I don't know who might
have them. I don't remember off the top of my head whether there's a
way to get a list of the current mounts. Like I said in my previous
email, we eventually got there, it just took a little longer.

On 5/26/2019 10:15 PM, Evan Harris wrote:
Hi Joe

Do you have any NFS mounts in place ?

My recollection is I had some grief ending NFS background tasks if I
didn't
unmount the NFS shared directories first, so maybe that is the
source of the issue.

On Mon, May 27, 2019 at 8:18 AM Joe Pluta
<joepluta@xxxxxxxxxxxxxxxxx>
wrote:

I have two different machines both having the same problem: after
ENDSBS *ALL, a job in QSYSWRK won't end. The job is QNFSNLMD, which research
indicates is the Network Lock Manager for the NFS server. I'm just
wondering if anyone else has run into this.

It's not critical. We're applying PTFs, so I'm just treating the
system as if it were in restricted state and going to the next IPL.
But I'd never encountered this before.


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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com


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

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

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.