I know what you're thinking - pretty straightforward... that's what I thought too...
I have a CL program that has the following at the beginning.
CPYTOIMPF FROMFILE(QTEMP/&FNAME) TOSTMF(&IFSFILE) MBROPT(*REPLACE) +
STMFCCSID(*STDASCII) RCDDLM(*CRLF) DTAFMT(*FIXED)
&IFSFILE has value of /apps/clerk/T17170427
Two lines later I have:
RMVLNK OBJLNK(&IFSFILE)
It is the RMVLNK statement that is generating the error (how can a program that creates a file, not have the authority to delete it)?
The file is owned by the user running the program and the user has *RWX data authority. The program is owned by QSECOFR with User Profile of *OWNER - how does QSECOFR NOT have authority to the object?
Color me confused...
I have a CL program that has the following at the beginning.
CPYTOIMPF FROMFILE(QTEMP/&FNAME) TOSTMF(&IFSFILE) MBROPT(*REPLACE) +
STMFCCSID(*STDASCII) RCDDLM(*CRLF) DTAFMT(*FIXED)
&IFSFILE has value of /apps/clerk/T17170427
Two lines later I have:
RMVLNK OBJLNK(&IFSFILE)
It is the RMVLNK statement that is generating the error (how can a program that creates a file, not have the authority to delete it)?
The file is owned by the user running the program and the user has *RWX data authority. The program is owned by QSECOFR with User Profile of *OWNER - how does QSECOFR NOT have authority to the object?
Color me confused...
Comment