Weird authority issue, supposedly on object in QTEMP

We have a customer who has some extremely weird things going on with one user. Here is an excerpt from the joblog:

40 06/29/12 09:51:04.842522 #auexcpt 000C18 QDBCRTFI To module . . . . . . . . . : QDBCRTFI To procedure . . . . . . . : CREATE_FCB_OBJECT Statement . . . . . . . . . : 38348 Message . . . . : Attempt to use permanent system object <user-ID> without authority. Cause . . . . . : You tried to use the permanent system object <user-ID> without having the correct authority. 40 06/29/12 09:51:04.860510 QDBCRTFI QSYS *STMT WTGOSQLR From module . . . . . . . . : QDBCRTFI From procedure . . . . . . : SEND_PMSG Statement . . . . . . . . . : 38945 To module . . . . . . . . . : WTGOSQLR To procedure . . . . . . . : WTGOSQLR Statement . . . . . . . . . : 1068 Message . . . . : Not authorized to objects needed for file WTGRPSQ in QTEMP. Cause . . . . . : The requested operation was not done for file WTGRPSQ in
library QTEMP for one of the following reasons: -- Not authorized to library QTEMP. -- Not authorized to member *N. -- Not authorized to file *N in library *N. -- The user profile of the owner of file WTGRPSQ in library QTEMP does not have *ADD authority. -- The group user profile does not have *ADD authority. If add member was requested, the member name is *N. Recovery . . . : Get the necessary authority from either the security officer or the owner of the object. Then try the job again. 40 06/29/12 09:51:04.862201 QCPCREAT QSYS 0086 WTGOSQLR WIN
To module . . . . . . . . . : WTGOSQLR To procedure . . . . . . . : WTGOSQLR Statement . . . . . . . . . : 1068 Message . . . . : Error creating file WTGRPSQ in library QTEMP. Cause . . . . . : An error occurred while creating the to-file. Recovery . . . : See the messages previously listed. Correct the errors, and then try the request again. Technical description . . . . . . . . : This message is usually displayed to indicate the file was not created. In some conditions this message is displayed to indicate an error occurred after the file was created, but before it could be allocated. 40 06/29/12 09:51:04.862211 QCPCREAT QSYS 0086 WTGOSQLR WIN
To module . . . . . . . . . : WTGOSQLR To procedure . . . . . . . : WTGOSQLR Statement . . . . . . . . . : 1068 Message . . . . : Copy command ended because of error. Cause . . . . . : An error occurred while the file was being copied. Recovery . . . : See the messages previously listed. Correct the errors,
and then try the request again. 40 06/29/12 09:51:04.867111 QMHUNMSG *N WTGOSQLR WI
To module . . . . . . . . . : WTGOSQLR To procedure . . . . . . . : WTGOSQLR Statement . . . . . . . . . : 1068 Message . . . . : Function check. CPF2817 unmonitored by WTGOSQLR at statement 0000001068, instruction X'0000'. Cause . . . . . : An escape exception message was sent to a program which did not monitor for that message. The full name of the program to which the unmonitored message was sent is WTGOSQLR WTGOSQLR WTGOSQLR. At the time the
message was sent the program was stopped at higher level language statement
number(s) 0000001068. If more than one statement number is shown, the program was a bound program. Optimization does not allow a single statement
number to be determined. If *N is shown as a value, it means the actual value was not available. Recovery . . . : See the low level messages previously listed to locate the cause of the function check. Correct any
errors, and then try the request again. 99 06/29/12 09:51:04.867227 QRNXIE QSYS *STMT QRNXIE From module . . . . . . . . : QRNXMSG From procedure . . . . . . : InqMsg Statement . . . . . . . . . : 15 To module . . . . . . . . . : QRNXMSG To procedure . . . . . . . : InqMsg Statement . . . . . . . . . : 15 Message . . . . : The call to *LIBL/QCMDEXC ended in error (C G D F). Cause . . . . . : RPG procedure WTGOSQLR in program WINTOUCH/WTGOSQLR at statement 1068 called program or procedure *LIBL/QCMDEXC, which ended in error. If the name is *N, the call was a bound call by procedure pointer.
Recovery . . . : Check the job log for more information on the cause of the error and contact the person responsible for program maintenance. Possible choices for replying to message . . . . . . . . . . . . . . . : D
-- Obtain RPG formatted dump. S -- Obtain system dump. G -- Continue processing at *GETIN. C -- Cancel. F -- Obtain full formatted dump.

The statement 1068 referred to is a simple QCMDEXC call, doing a CPYF of the file WTGRPSQ (which has *PUBLIC *ALL authority) into QTEMP.

Is it even possible for a user to NOT have authority to his or her own job's QTEMP?

--
JHHL