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



Correction - system profiles impacted by this API, cannot and should not be
changed by user in any way.
So this API is always safe to use.
This is a list of user-profiles impacted by this API, taken from
Information Center:
     QAUTPROF    QCLUMGT     QCLUSTER    QCOLSRV
     QDBSHR      QDBSHRDO    QDFTOWN     QDIRSRV
     QDLFM       QDOC        QDSNX       QFNC
     QGATE       QIPP        QLPAUTO     QLPINSTALL
     QMSF        QNTP        QPM400      QSNADS
     QSPL        QSPLJOB     QTCP        QTFTP
     QTSTRQS     QYPSJSVR

You do not normally have

    Alexei Pytel


----- Forwarded by Alexei Pytel/Rochester/IBM on 11/09/2001 10:53 AM -----

                    Alexei Pytel
                                         To:     Midrange-L@midrange.com
                    11/09/2001           cc:
                    10:17 AM             From:   Alexei 
Pytel/Rochester/IBM@IBMUS
                                         Subject:     Re: V5R1 Job Q1PPMSUB 
User QPM400







The Reset Profile Attributes (QSYRESPA) API will fix the QPM400 profile.
API is documented in Information Center, but here is some information:
The Reset Profile Attributes (QSYRESPA) API resets four attributes of
system-supplied user profiles. Only system-supplied user profiles that
cannot be changed using the Change User Profile (CHGUSRPRF) command are
modified by the QSYRESPA API. The following user profile attributes are
reset:
          The password value is set to *NONE.
          The status value is set to *ENABLED.
          The password expired value is set to *NO
          The special authorities will be set to the appropriate values for
          the each system supplied profile.
The QSYRESPA  API requires one output parameter for the API return code.
An easy way to call the API is to create a CL program that calls QSYRESPA.
A sample CL program is listed below.

           PGM
         DCL &RC *CHAR 8 X'0000000000000000'

         /* CALL THE RESET API.  THE ALL ZERO RETURN CODE INDICATES TO THE
        */
         /* API IT SHOULD SIGNAL AN EXCEPTION IF AN ERROR IS TAKEN.
        */
         /*
        */
         /* IF THE API DOES NOT RETURN ANY MESSAGES, IT WAS SUCCESSFUL.
        */
         CALL QSYRESPA (&RC)

         ENDPGM

   After the API runs, QPM400 should have *JOBCTL and *IOSYSCFG special
authority.  This should get you up and running again.

But be careful - API will reset ALL system profiles. You may need to adjust
passwords etc.

Alexei Pytel


                    jmoreno@militarycar
                    s.com                     To:     Midrange-L@midrange.com
                    Sent by:                  cc:
                    midrange-l-admin@mi       Subject:     V5R1 Job Q1PPMSUB 
User QPM400
                    drange.com


                    11/01/2001 09:07 AM
                    Please respond to
                    midrange-l





Hello all,

We recently upgraded one of our AS400s to V5R1M0 and there is a Performance
Monitor
Job Q1PPMSUB that runs in QSYSWRK and it finds a security conflict when
starts
running

These are the details:
-----------------------------------------------------------------------------------


 Job . . :   Q1PPMSUB      User . . :   QPM400
  >> CALL PGM(QSYS/Q1PBATCH) PARM('CALL QSYS/Q1PPMSUB')

     QYPSCOLL       QSYS        *STMT    Q1PPMS
     From module . . . . . . . . :   QYPSCHGSYS
     From procedure  . . . . . . :   QypsChgSysCollectorAttributes
     Statement . . . . . . . . . :   1696

     *JOBCTL special authority is required.
     Function check. CPF222E unmonitored by Q1PPMSUB at statement *N,
       instruction X'0061'.
     CPF222E received by Q1PPMSUB at *N. (C D I R) ...


------------------------------------------------------------------------------------


When I try to grant *JOBCTL authority to the QPM400 User Profile I get the
following message

The system user profile is required by the system. The definition of this
profile cannot be changed.

Oh well ..

I checked the Licence Key Information for the Performance Tools Product and
the
System tells me that we have a licence for the following products

Product 5722PT1 Version V5R1M0 Feature 5050 - Performance Tools for AS/400
- Base
Product 5722PT1 Version V5R1M0 Feature 5101 - Performance Tools - Manager
Feature

Has someone come across something like this before ?

I will be very appreciative of your advice

Regards

Jorge Moreno
Systems Analyst
Woodbury, New York





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

















As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.