× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. WDSCI-L
  3. January 2004

Re: iSeries search update

Greg,   I would have to check with the folks who support the fndstrpdm 
command regarding the behavior you see and get back to you directly. 

Dave Cheng, 
905-413-4063  cheng@xxxxxxxxxx




"Gregg Willow" <gregg.willow@xxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/13/2004 03:26 PM
Please respond to
Websphere Development Studio Client for iSeries 


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] iSeries search update






Dave,

The job description to my user profile is QDFTJOBD. The values for printer
device and output queue are both *USRPRF. The values in my user profile 
for
printer device and output queue are PRTDUMMY and GLW007 respectively.

After running an iSeries Search, I go to Work with All Spooled Files, and
under the Device or Queue column it reads PRTDUMMY.

I then created a new output queue named GLWTEST and changed my job
description for my user profile to that output queue. I ran a 5250 PDM
search to print. In Work with All Spooled Files, under Device or Queue, it
reads GLWTEST.

I then logged out of WDSC and back on again and changed the job 
description
to all of my server jobs to point to output queue GLWTEST. Ran the iSeries
Search and the spooled file still reads PRTDUMMY under Device or Queue.

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: "Dave Cheng" <cheng@xxxxxxxxxx>
To: "Websphere Development Studio Client for iSeries" 
<wdsci-l@xxxxxxxxxxxx>
Sent: Tuesday, January 13, 2004 10:47 AM
Subject: Re: [WDSCI-L] iSeries search update


>
>
>
>
> Greg,
>    What is the outq value specified in your job description? If you 
create
> an output queue and specify that in the outq of your job description,
would
> your search result go to that queue?
>
> Dave Cheng,
> 905-413-4063  cheng@xxxxxxxxxx
>
>
>
>
>              "Gregg Willow"
>              <gregg.willow@mci
>              s.cog.mn.us> To
>              Sent by:                  "Websphere Development Studio
>              wdsci-l-bounces@m         Client for iSeries"
>              idrange.com               <wdsci-l@xxxxxxxxxxxx>
> cc
>
>              01/12/2004 04:38 Subject
>              PM                        Re: [WDSCI-L] iSeries search 
update
>
>
>              Please respond to
>                  Websphere
>                 Development
>              Studio Client for
>                   iSeries
>
>
>
>
>
>
> Mark,
>
> I have looked at everyone of my server jobs and each one lists OUTQ as 
my
> default output queue. *DEV is not defaulted. We had created a PRTDUMMY
> print
> queue and changed my user profile to that print queue. Logged off and on
so
> that it would take effect. My output queue has remained unchanged. I
> performed another "small" search and the spooled files reside in the
> PRTDUMMY print queue. This is telling me that in this scenario, the OUTQ
is
> not being used.
>
> 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 2:53 PM
> Subject: Re: [WDSCI-L] iSeries search update
>
>
> > 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.
> > _______________________________________________
> > 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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.