|
midrange.com
Forgot to mention, the cool part is if I cut and past the submit job
command, which looks like:
SBMJOB CMD(CALL QDEVTOOLS/QRBPGMBLD PARM(Q000000025)) JOBD(QGPL/MADDEV)
into an interactive session and run it, works like a charm
Mark Dame
mark.dame@xxxxxxxxxxxxxx
Phone: (330) 926-5407
Fax: (330) 926-5421
|---------+---------------------------->
| | Mark.Dame@matcoto|
| | ols.com |
| | Sent by: |
| | wdsci-l-bounces@m|
| | idrange.com |
| | |
| | |
| | 11/11/2003 02:50 |
| | PM |
| | Please respond to|
| | Websphere |
| | Development |
| | Studio Client for|
| | iSeries |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx> |
| cc: Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>, wdsci-l-bounces@xxxxxxxxxxxx |
| Subject: Re: [WDSCI-L] iSeries Project Build
|
>------------------------------------------------------------------------------------------------------------------------------|
This worked fine yesterday, what'd I mess up now? I changed the connection
job description and was happily compiling yesterday. Except that I needed
it to use a different job queue. So today, I copied the job description I
used that worked, changed the jobq and tweaked the library list. I
submitted the build. It failed, requiring source files that now weren't in
the library list. OK, put back the one that was working yesterday. Still
fails. Deleted and re-created the connection. Still doesn't get the right
list. 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.
Mark Dame
|---------+---------------------------->
| | David Dykstal |
| | <david_dykstal@us|
| | .ibm.com> |
| | Sent by: |
| | wdsci-l-bounces@m|
| | idrange.com |
| | |
| | |
| | 11/10/2003 12:56 |
| | 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 Project Build
|
>
------------------------------------------------------------------------------------------------------------------------------|
iSeries Projects uses the Remote System Explorer connection you specified
in the project's definition to submit its jobs. You can change the job
description by going to the connection definition in RSE and changing the
properties of the iSeries Objects Subsystem.
_______________________
David Dykstal
_______________________________________________
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 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.
