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



Thanks, I can hardly wait to get to team projects to try and sync them up.
What you say is true, the interactive session did have the right library
list to compile.  I guess my question boils down to, if the job description
is used for the jobq to run the submitted job, and I changed the message
logging level to *SECLVL  in the job description and that sticks, what's
the deal with the library list?

Taking a guess, I'd say I need to set the INLLIBL parameter in the SBMJOB
command to *JOBD.  How do I do that in WDSCi?

Mark Dame




|---------+---------------------------->
|         |           MichaelQuigley@Th|
|         |           eWay.org         |
|         |           Sent by:         |
|         |           wdsci-l-bounces@m|
|         |           idrange.com      |
|         |                            |
|         |                            |
|         |           11/11/2003 04:17 |
|         |           PM               |
|         |           Please respond to|
|         |           Websphere        |
|         |           Development      |
|         |           Studio Client for|
|         |           iSeries          |
|         |                            |
|---------+---------------------------->
  
>------------------------------------------------------------------------------------------------------------------------------|
  |                                                                             
                                                 |
  |       To:       wdsci-l@xxxxxxxxxxxx                                        
                                                 |
  |       cc:                                                                   
                                                 |
  |       Subject:  Re: [WDSCI-L] iSeries Project Build                         
                                                 |
  
>------------------------------------------------------------------------------------------------------------------------------|




   Mark:

   You wrote:

   "It appears to use the library list from the submitting job, QZRCSRVS.
Or
   it's using the library list associated with my signon.  Either way, it's
   not the library list of the job description."

   The default for a SBMJOB command is INLLIBL(*CURRENT).  It sounds like
the
   library list isn't set right before the build is submitted.  I've had
tons
   of trouble getting the library list set correctly.  There's a lot of
jobs
   involved-- The library list on the Interactive job associated with the
   connection (STRRSESVR), the "normal" command server, the "batch" command
   server, . . .  And if you're using anything CODE related there still can
   be STRCODE servers.  Since the command works when you cut-and-paste it
   into an interactive job, my guess is that your interactive job has the
   library list set prior to executing the pasted SBMJOB command.

   HTH.
   Michael Quigley
   Systems-Analyst
   The Way International
   www.TheWay.org
_______________________________________________
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 ...


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.