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



Hello Rob,

Am 25.10.2021 um 20:36 schrieb Rob Berendt <rob@xxxxxxxxx>:

WRKMBRPDM
F18=Change defaults
Been forever since I've used PDM so I had to hunt around. I had a custom job description.

CRTUSRPRF DUMMY
Signed on as DUMMY.
WRKMBRPDM ...
F18
Oh, the job description here is defaulted to QBATCH and not QDFTJOBD, or *USRPRF or some such thing.

Glad you could duplicate my finding. :-)

Strange thought, but isn't someone using PDM generally USRCLS(*PGMR)?

I see no reason for that. You could easily program without being a "*PGMR". I guess the special authorities are for the cases when you need to run online debugging facilities. That compile jobs are run as QPGMR hints towards my assumption. Also, it ensures that compiled objects belong to the QPGMR user profile, so multiple programmers can sign on with their personal profile, and still compile/overwrite objects from other programmers.

Or are you using PDM for the masses?

Haha, given that I'm (still) the sole user of my machine, "masses" isn't exactly applicable.

If so, simply have them use F18 to set their job description to one they will have access to.
If this is tough to communicate with them then run this command for those users:
CHGPDMDFT USER(...) JOBD(QDFTJOBD)
https://www.ibm.com/docs/en/i/7.4?topic=ssw_ibm_i_74/cl/chgpdmdft.htm

Again, something learned. I wasn't aware of CHGPDMDFT. Thanks!

:wq! PoC


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.