|
midrange.com
Ok, I ran the CL program under my userid ADAM.
I was sysreqed under the administrator account and did a wrksplf on ADAM.
This is what I had
File User Queue
QSYSPRT ADAM PRT01
I do a dspjob from ADAM and this is what I get
Job: DP002 User: ADAM
We have a compiled CL program that is generating the spool file and then
deleting it (or should be). It works form command line, but in the CL
program it doesn't delete it using the DLTSPLF FILE(QSYSPrt) SPLNBR(*LAST)
you mentioned from before.
----- Original Message -----
From: <michaelr_41@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Saturday, July 10, 2004 7:12 PM
Subject: Re: Check existence of a directory?
> Are you submitting the job that creates the spooled file, like maybe a
> compile or something? The spooled file that you're trying to delete is
> not in the same job as the job issuing the delete command. Do a WRKSPLF
> and determine the job that created the spooled file. Then do a DSPJOB -
> your interactive job must be different than the spooled file job.
>
> On Fri, 9 Jul 2004 15:58:39 -0400, "Adam Lang"
> <aalang@xxxxxxxxxxxxxxxxxxxx> said:
> > Interesting. When doing the dsplnk and dltsplf from command line it
> > works.
> > Any idea what the difference is?
> >
> > ----- Original Message -----
> > From: <michaelr_41@xxxxxxxxxxxxxx>
> > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> > Sent: Friday, July 09, 2004 2:52 PM
> > Subject: Re: Check existence of a directory?
> >
> >
> > > Hmmmm....do it all from the command line and see if the same thing
> > > happens.
> > >
> > > On Fri, 9 Jul 2004 14:49:05 -0400, "Adam Lang"
> > > <aalang@xxxxxxxxxxxxxxxxxxxx> said:
> > > > Yes it does. The print shows up on hold, though.
> > > > ----- Original Message -----
> > > > From: <michaelr_41@xxxxxxxxxxxxxx>
> > > > To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxx>
> > > > Sent: Friday, July 09, 2004 1:59 PM
> > > > Subject: Re: Check existence of a directory?
> > > >
> > > >
> > > > > PRT01 doesn't happen to have a writer attached to it, does it?
> > > > >
> > > > > On Fri, 9 Jul 2004 13:51:25 -0400, "Adam Lang"
> > > > > <aalang@xxxxxxxxxxxxxxxxxxxx> said:
> > > > > > It's happening in the same CL program.
> > > > > > ----- Original Message -----
> > > > > > From: <michaelr_41@xxxxxxxxxxxxxx>
> > > > > > To: "Midrange Systems Technical Discussion"
> > <midrange-l@xxxxxxxxxxxx>
> > > > > > Sent: Friday, July 09, 2004 1:39 PM
> > > > > > Subject: Re: Check existence of a directory?
> > > > > >
> > > > > >
> > > > > > > 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.
> > > > > >
> > > > > > --
> > > > > > 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.
> >
> > --
> > 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.
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.
