×
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.
The LOGCMD object is a *CMD object, so it does not adopt authority. But
the CPP and all other called programs do. And QSECOFR is the owner of
all of them. There are no other instances of those programs on the
system. In fact, except for the *SERVICE special authority, all other
authority are given when inside the command.
If I define the user as *SECOFR, the command works
"Gary Monnier" <gary.monnier@xxxxxxxxxxxxx> 2007-10-15 16:50 >>>
Is command LOGCMD also owned by QSECOFR? What authority and ownership
does LOGCMD's CPP have? Is the CPP owned by QSECOFR? Are you positive
the command is running out of the library you expect?
If you create a profile with a user class of *SECOFR what occurs?
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.
midrange.com
