Re: [WDSCI-L] iSeries search update

["Mark Phippard" <MarkP@xxxxxxxxxxxxxxx>]

The value for the OUTQ is always what will be used.  It is just that if 
you look at your server jobs that are being run for WDSC, I think you will 
find that they are currently set to OUTQ(*DEV).

Hint:  If you run the command WRKOBJLCK YOURID *USRPRF while running WDSC 
it is easy to find your server jobs.  You can also find then in the Your 
Active Jobs filter within RSE.

Mark


wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/12/2004 01:04:44 PM:

> Mark,
> 
> Just to clarify, it seems that the iSeries Search is using the PRTDEV
> parameter not the OUTQ parameter of the user profile. If it was using 
OUTQ
> we would not be having any problems.
> 
> We could have done the CHGJOB on the RSE connection but some programmers
> have not moved over to WDSc yet. So changing their user profile now, 
they
> will not encounter any problems when they first start using it. We are a
> small shop so it not too big of a deal.
> 
> Best regards,
> 
> Gregg Willow
> Programmer/Analyst
> Minnesota Counties Information Systems
> 413 SE 7th Avenue
> Grand Rapids, MN  55744
> 218-326-0381 ext: 17
> gregg.willow@xxxxxxxxxxxxxx
> ----- Original Message ----- 
> From: "Mark Phippard" <MarkP@xxxxxxxxxxxxxxx>
> To: "Websphere Development Studio Client for iSeries" 
<wdsci-l@xxxxxxxxxxxx>
> Sent: Monday, January 12, 2004 11:57 AM
> Subject: Re: [WDSCI-L] iSeries search update
> 
> 
> > I would try just adding the CHGJOB command to the connection.  Seems 
like
> > it would be less impact.  Expand your connection, right-click on 
iSeries
> > Commands and click Properties.  Then click the "Initial Library List"
> > property page and there is a place to enter a command string.
> > Unfortunately, there is no prompting that I see, so you would need to 
cut
> > & paste the correct string.  But if you entered something like this it
> > would get the same result.
> >
> > CHGJOB OUTQ(SOMELIB/SOMEQ)
> >
> > Mark
> >
> >
> > wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/12/2004 12:05:35 PM:
> >
> > > Mark,
> > >
> > > Basically we are just going to create a dummy print device and 
change
> > the
> > > programmers user profiles to go to that device. Our administrator
> > chooses
> > > not to change objects that could possibly be updated by an O/S 
upgrade.
> > Will
> > > just have to watch that dummy print queue and clean up our search
> > results.
> > > This will keep us from wasting paper. Hopefully, IBM can get a quick 
fix
> > > into the next release that will allow to print or not print.
> > >
> > > Best regards,
> > >
> > > Gregg Willow
> > > Programmer/Analyst
> > > Minnesota Counties Information Systems
> > > 413 SE 7th Avenue
> > > Grand Rapids, MN  55744
> > > 218-326-0381 ext: 17
> > > gregg.willow@xxxxxxxxxxxxxx
> > > ----- Original Message ----- 
> > > From: "Mark Phippard" <MarkP@xxxxxxxxxxxxxxx>
> > > To: "Websphere Development Studio Client for iSeries"
> > <wdsci-l@xxxxxxxxxxxx>
> > > Sent: Monday, January 12, 2004 10:32 AM
> > > Subject: Re: [WDSCI-L] iSeries search update
> > >
> > >
> > > > Gregg,
> > > >
> > > > I think the issue is that the jobs that WDSC uses that communicate
> > with
> > > > your iSeries are pre-start jobs which are started under the QUSER
> > profile.
> > > >  If I look at the jobs on my system, I see that the jobs use the
> > QDFTJOBD
> > > > *JOBD which specifies *USRPRF for the print device.  The user 
profile
> > when
> > > > the job is started is QUSER which specifies *WRKSTN for print 
device
> > in
> > > > the profile.
> > > >
> > > > I do not believe that the JT400 mechanism for using these 
pre-start
> > jobs
> > > > does anything except swap the job profile to your ID.  I think 
there
> > are a
> > > > few things you could do:
> > > >
> > > > 1)  Change the values in QDFTJOBD
> > > >
> > > > 2)  Change the values in QUSER
> > > >
> > > > 3)  In your RSE connection, you can define commands that are 
executed
> > when
> > > > the connection is made.  It seems like you could just define 
CHGJOB as
> > the
> > > > command to run and then have the job changed to the values you 
want.
> > > >
> > > > Good luck, let us know if any of this works.
> > > >
> > > > Mark
> > > >
> > > >
> > > >
> > > > wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/12/2004 11:10:24 AM:
> > > >
> > > > > Dave Cheng wrote:
> > > > >
> > > > > "Please check the output queue in your job description and make 
sure
> > it
> > > > > points to the correct queue. We actually use the FNDSTRPDM 
command
> > to
> > > > find
> > > > > the string and I would look into providing an option so that the
> > > > searching
> > > > > can be done without generating spool files."
> > > > >
> > > > > Dave,
> > > > >
> > > > > The output queue within my job description is correct. Like I 
stated
> > > > before,
> > > > > it seems it is going directly to whatever printer device that is
> > defined
> > > > > within the job description. The iSeries Search is a great 
addition
> > to
> > > > RSE
> > > > > but I would definitely appreciate an option not create a spooled
> > file of
> > > > the
> > > > > results.
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Gregg Willow
> > > > > Programmer/Analyst
> > > > > Minnesota Counties Information Systems
> > > > > 413 SE 7th Avenue
> > > > > Grand Rapids, MN  55744
> > > > > 218-326-0381 ext: 17
> > > > > gregg.willow@xxxxxxxxxxxxxx
> > > > >
> > > > > _______________________________________________
> > > > > This is the Websphere Development Studio Client for iSeries 
(WDSCI-
> > > > > L) mailing list
> > > > > To post a message email: WDSCI-L@xxxxxxxxxxxx
> > > > > To subscribe, unsubscribe, or change list options,
> > > > > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> > > > > or email: WDSCI-L-request@xxxxxxxxxxxx
> > > > > Before posting, please take a moment to review the archives
> > > > > at http://archive.midrange.com/wdsci-l.
> > > > _______________________________________________
> > > > This is the Websphere Development Studio Client for iSeries 
(WDSCI-L)
> > > mailing list
> > > > To post a message email: WDSCI-L@xxxxxxxxxxxx
> > > > To subscribe, unsubscribe, or change list options,
> > > > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> > > > or email: WDSCI-L-request@xxxxxxxxxxxx
> > > > Before posting, please take a moment to review the archives
> > > > at http://archive.midrange.com/wdsci-l.
> > > >
> > >
> > > _______________________________________________
> > > This is the Websphere Development Studio Client for iSeries  (WDSCI-
> > > L) mailing list
> > > To post a message email: WDSCI-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> > > or email: WDSCI-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/wdsci-l.
> > _______________________________________________
> > This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
> mailing list
> > To post a message email: WDSCI-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> > or email: WDSCI-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/wdsci-l.
> >
> 
> _______________________________________________
> This is the Websphere Development Studio Client for iSeries  (WDSCI-
> L) mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.