RE: QINACTITV does not appear to be working -- SECURITY400

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

Subject: RE: [Security400] QINACTITV does not appear to be working
From: Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>
Date: Thu, 30 Aug 2001 14:30:22 -0400
List-Archive: <http://archive.midrange.com/security400/>
List-Help: <mailto:security400-request@midrange.com?subject=help>
List-Id: Security Administration on the AS400 / iSeries <security400.midrange.com>
List-Post: <mailto:security400@midrange.com>
List-Subscribe: <http://lists.midrange.com/cgi-bin/listinfo/security400>,<mailto:security400-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/security400>,<mailto:security400-request@midrange.com?subject=unsubscribe>

>To enable access to particular individuals during the
>backup I starts a second subsystem that has
>workstation entries included in it and only allow
>people with a particular routing entry to sign on.

An alternative is to secure access to jobq(qctl) and allow only authorised
individuals the ability to TFRJOB QCTL.  In the era of randomly assigned
QPADEVxxxx, it's easier to restrict by user ID than by device ID.  A second
(private) subsystem is a very good idea.

Buck

As an Amazon Associate we earn from qualifying purchases.

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.