Re: MCH1001 in CGI-Program

On 28-Jul-2016 09:04 -0500, Jan Grove Vejlstrup wrote:

I'm trying to copy a physical file from a library in the library-list
to qtemp in a cgi-job running under the user profile qtmhhtp1. The
command is:

crtdupobj obj(myFile) fromlib(*libl) objtype(*file) tolib(qtemp)

The file myFile has Authority *public *all. I receive the message
MCH1001 (attempt to use permanent system object qtmhhtp1 without
authority). The file doesn't get copied.

What am I doing wrong?

Nothing wrong with the request [after correcting FROM( to FROMLIB(]; perhaps a bit safer, to have coded the other parameter specifications to avoid being impacted by any changed defaults.

What is wrong with what was offered however, is a lack of the spooled joblog and the server OS VRM level, and the T-AF audit log entry details; for the latter, I can probably safely infer the system-object QTMHHTP1 is the *USRPRF object by that name. A WRKJOB OPTION(*ALL) OUTPUT(*PRINT) taken at the time of the x0A01 exception [msg MCH1001] would be of value as well; if not taken then, then performed in a request immediately before the failing CRTDUPOBJ.

Does the following request [with appropriate SYSLIBL, CURLIB, and INLLIBL to match the failing scenario] as submitted by a user with *ALLOBJ authority, exhibit the same failure, per review of the joblog?:

sbmjob cmd(crtdupobj myFile *libl objtype(*file) tolib(qtemp)
) user(qtmhhtp1) job(tmAutTst)
logoutput(*jobend) log(4 0 *seclvl) splfacn(*keep)

Thank you very much in advance.

Note: The Create Duplicate Object (CRTDUPOBJ) tries to set all of the private authorities in the from-object into the to-object. Specific attributes of the user profile and the process making the request sometimes can make completing that work somewhat problematic.

The error suggests that perhaps the user profile QTMHHTP1 may be missing authority to itself. As obtained by a user with *ALLOBJ special authority, output from the requests DSPUSRPRF QTMHHTP1 OUTPUT(*PRINT) and DSPOBJAUT QTMHHTP1 *USRPRF may be helpful. If the failure only occurs when the job is switched to another user [i.e. the above SBMJOB does not fail], then the same two requests against the user profile under which the failing job runs, might also be of value to review.