|
Was going to post the following (see below the error) but then decided to try it on my sandbox - no dice. Be nice if IBM would name the text all the same! Tried it on QMSF. Message ID . . . . . . : CPD2201 Date sent . . . . . . : 01/02/07 Time sent . . . . . . : 15:51:04 Message . . . . : System user profile cannot be changed. Cause . . . . . : The system user profile is required by the system. The definition of this profile cannot be changed. -was going to post this- Is there any negative actions which could occur by changing all the IBM-supplied profiles to a consistent TEXT parameter? Most of them say "IBM-Supplied User Profile," but some don't - I'd like them to all look the same when generating reports of *USRPRF objects. Thoughts? For example, if I did a 2 on all these (these aren't all of them, but just for example's sake) and then on the command line did TEXT('IBM-supplied User Profile') QLPINSTALL IBM-supplied User Profile QMGTC IBM-supplied User Profile QMSF Mail Server Framework Profile QNETSPLF Internal Spool Network Profile QNFSANON IBM-supplied User Profile QNTP IBM-supplied User Profile QPEX IBM-supplied User Profile QPGMR Programmer and Batch User QPM400 IBM-supplied User Profile Justin C. Haase - Solution Engineer IBM Certified Systems Expert - System i Kingland Systems Corporation CONFIDENTIALITY NOTICE: This e-mail communication, including attachments, is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential, and may be legally privileged. If you are not the intended recipient or believe you received this communication in error, please reply to the sender indicating that fact and delete the copy you received. In addition, retention, dissemination, distribution, copying, or otherwise use of the information contained in this communication is strictly prohibited. Thank you.
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.