Re: [WDSCI-L] iSeries search update

["Gregg Willow" <gregg.willow@xxxxxxxxxxxxxx>]

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.
>