Re: Finding why a user profile gets disabled -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Finding why a user profile gets disabled
From: rob@xxxxxxxxx
Date: Mon, 22 Sep 2008 11:55:51 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Good ideas.

Another option is to CRTMSGQ QSYS/QSYSMSG. And then "critical" qsysopr
message get a copy put there also simply because that message queue now
exists. On my system if I do a DSPMSG QSYSMSG I see:
Subsystem QINTER varied off work station GDMPC21S3 for user CLUNA.
Subsystem QINTER varied off work station ELPN08S2 for user LFLOREZ.

Rob Berendt

This mailing list archive is Copyright 1997-2026 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.