Re: Batch Compile as member name . . .

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 05/29/2019
02:32:00 PM:

----- Message from Steve Ferrell via WDSCI-L <wdsci-
l@xxxxxxxxxxxxxxxxxx> on Wed, 29 May 2019 18:00:44 +0000 -----

To:

Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>

cc:

Steve Ferrell <Steve.Ferrell@xxxxxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] Batch Compile as member name . . .

Hi Michael,

There are no new preferences. If the member name can be used as a
simple name, the jobname should be the same as the member name.

Is it possible that you've have a compile command override? IE go
into properties for your connection -> select the Subsystems filter
-> look at properties for Batch compiles, commands, and user action
variables. If you override it on this panel, we honor that. If not
we ensure the member name is a valid *SNAME and use it on the SBMJOB

command.

If you don't have something overriding the command, please contact
IBM support so we can take a peek at what the issue may be.

Steve Ferrell

-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
MichaelQuigley@xxxxxxxxxx
Sent: Wednesday, May 29, 2019 12:38 PM
To: Midrange.com, WDSc <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: [WDSCI-L] Batch Compile as member name . . .

I applied 9.6.0.6 as I was excited to see how the delivery of RFE
69324 ( Batch Compile as member name if the member name is a simple
name (*SNAME), like PDM does) works--I opened the RFE. There must be
a setting somewhere or something to enable it as I still get all my
batch compile jobs named after the JOBD. Anyone have any clues?

Thanks,
Michael Quigley
Computer Services
The Way International

Hi Steve,

I have nothing in the connection properties. But we do use a custom
compile command. It's similar to the STRPREPRC (sp?) distributed with
iSphere. It reads the source member looking for special comments at the
start of the member and uses these to store compile command options. Our
command used the name of the object as the default name for the source
member. I modified it to specify the SRCMBR parameter and the jobs are now
submitting named after the source member. This is cool.

However, an old bug has resurfaced. The compile commands listed under the
Compile menu are doubled up--i.e., I see CRTBNDCL, CRTCLMOD, Compile with
PARMS (our custom command), CRTBNDCL, CRTCLMOD, and Compile with PARMS. I
think the APAR was SE63511. Although that might just be a similar issue.
I'll probably open a PMR--Mike Hockings helped me out the last couple of
times this was occurring.

Thanks,
Michael Quigley
Computer Services
The Way International