|
An application we wrote takes a normal database file and creates an EXCEL .xls STMF into a directory on the IFS called EXCEL. The java program is called from a central CLP to convert ebcdic to excel. Once the .xls is created, the CLP executes a CPY command (parameters were, at one time or another, *replace with *keep or *new) to create a version of file into the QDLS directory, folder named EXCEL. This is done because our e-mailing software requires the attachments to originate out of QDLS. Problem we are having is in the CPY command...it keeps failing due to authority problems and nobody has been able to figure out why. All of the RPG and CLP programs were compiled under *OWNER and by the same person who is running the application to make the .xls file. The input work file that is fed to the java routine is also under the same user although originally it was created under a test profile...the object ownership was changed to the principle user though with chgobjown command. The EXCEL directory in the IFS root has public *all. The QDLS directory was given public *all and the freaking QDLS/EXCEL folder was given...you guessed it...public *all. When the .xls file is first created, the rights assigned to it by OS400 are *RW...and naturally when copied to QDLS/EXCEL it carries the same. It seems to need *RWX but it will not happen. When I do a wrklnk to try and delete both the IFS and QDLS version of the files, the IFS lets my usrprf do it but the QDLS will not! However, it lets the test profile do it! Where is it grabbing that? Did the chgobjown do something funky? Anyway, we are stuck as to why the cpy object will not replace what is there beforehand and we have tried deleting, re-creating, much stuff...to no avail. Same error message for non-authorization. Anyone got any ideas? Thanks much. Rick Rayburn
As an Amazon Associate we earn from qualifying purchases.
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.