Re: Check existence of a directory? -- MIDRANGE-L

Issue is not so much who created as who owns the spooled file. There are some things that cause a spooled file to be owned by someone other than the original user of the job you are in. The default on CRTPRTF is *CURUSRPRF, which might not be who started the job. There are lots of ways to swap profiles. We sometimes use OVRPRTF SPLFOWN(*JOB) before printing something programmatically, in order to have access to it with DLTSPLF or CHGSPLFA.

The other alternative is to use an API to list spooled files. Lots of selection criteria available. Too much fun.

HTH
Vern

At 12:39 PM 7/9/2004, you wrote:

Sure it's the same user issuing the DLTSPLF as the user that created the
spooled file?
On Fri, 9 Jul 2004 13:27:30 -0400, "Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx> said: > The dltsplf doesn't work. When we run it by hand from command line, it > says > "no files named qsysprt are active" even though we still see it sitting > in > the prt01 queue. > > ----- Original Message ----- > From: <michaelr_41@xxxxxxxxxxxxxx> > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > Sent: Friday, July 09, 2004 10:48 AM > Subject: Re: Check existence of a directory? > > > > Well...you could always do a DSPLNK OBJ('/asdf') OUTPUT(*PRINT) and > > monitor for a CPFA0A9. You would probably want to delete the spooled > > file if you didn't get the error with a DLTSPLF FILE(QSYSPRT) > > SPLNBR(*LAST). > > > > On Fri, 9 Jul 2004 10:33:20 -0400, "Adam Lang" > > <aalang@xxxxxxxxxxxxxxxxxxxx> said: > > > I have a CL program that uses CHKDLO to determine the existence of a > > > folder. > > > We are changing things around to use directories. What would the > > > equivalent > > > command be to check for the existence of a directory? I assume we can't > > > use > > > wrklnk, because that will actually display the screen. Also, what would > > > the > > > correct msgid be? > > > > > > Adam Lang > > > Systems Engineer > > > Rutgers Casualty Insurance Company > > > http://www.rutgersinsurance.com > > > > > > -- > > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > > > list > > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > > To subscribe, unsubscribe, or change list options, > > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > > Before posting, please take a moment to review the archives > > > at http://archive.midrange.com/midrange-l. > > > > > -- > > > > michaelr_41@xxxxxxxxxxxxxx > > > > -- > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > --
  michaelr_41@xxxxxxxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.