|
the option 14 reveals public *all. <F= ONT color=#990099>-----midrange-l-bounces@xxxxxxxxxxxx wrote: ----- <B= R>To: Midrange Systems Technical Discussion <midrange-l@midrange. com> From: Pete Hall <pbhall@xxxxxxxxxxxxx> Sent by: midrang= e-l-bounces@xxxxxxxxxxxx Date: 02/27/2004 08:37PM Subject: Re: IFS - = QDLS security dilemma on the 400 A= t 19:18 2/27/2004, Rick Rayburn wrote: >An application we wrote takes= a normal database file and creates an EXCEL >.xls STMF into a direct= ory on the IFS called EXCEL. The java program is >called from a centr= al CLP to convert ebcdic to excel. > >Once the .xls is created,= the CLP executes a CPY command (parameters were, >at one time or ano= ther, *replace with *keep or *new) to create a version of >file into = the QDLS directory, folder named EXCEL. This is done because our >e-m= ailing software requires the attachments to originate out of QDLS. ><= BR>>Problem we are having is in the CPY command...it keeps failing due t= o >authority problems and nobody has been able to figure out why. Try doing a wrkflr, and option 14 (authority). As I recall, document <B R>library objects (QDLS) have their own version of object security, which I think has little to do with OS400 security. BTW, I've been told that Q DLS is going away very soon. I'm not sure if that's just doom and gloom= hype. Pete Hall pbhall@xxxxxxxxxxxxx http://www.pbhall.us/ _____ _________________________ _________________ This is the Midrange= Systems Technical Discussion (MIDRANGE-L) mailing list To post a messag= e email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change li= st options, visit: http://lists.midrange.com/mailman/listinfo/midr= ange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, = please take a moment to review the archives at http://archive.midrange.com/midran= ge-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.