Knowing how Aldon compiles I would doubt it would work well triggered
from LPEX editor. Aldon actually stores the "selected to be compiled"
member(s) in some sort of list object and then submit a single job
referencing that list object. Aldon uses the Release to setup details
for compiling like *JOBDs and *LIBLs. But I believe this type detail is
only known (from within RDi) when the compile action is performed via
the filter in RSE because the filter knows the release. I doubt LPEX
would know that.
I supposed you take Vern's suggestion to the point of making your own
compile command that inspects the objects in the Aldon system to see
their release / environment information and then select the appropriate
compile settings and *JOBD, however the Aldon compile command,
ACMSCREATE, is complex. I ended up giving up on this dream myself and
just stuck to knowing the quick access key stokes to get around views
and move through lists.
I only need a specialized version of Creates for those types of members
that do not translate into an object of the same type (SQL objects
primarily) or like with PFs and LFs the default commands do not replace.
I use the base create for most all other types.
At first I thought of the Keystroke Recorder but then I thought better
since the Keystroke Recorder as dumb as using a 5250 terminal macro, you
have to have everything set up just right to get it to function
properly.
Other things to think about with creating SQL type objects. Aldon
actually pre-compiles these into a special library to see if the Create
will actually work before dropping the real object and recreating it.
This prevents you from all of a sudden not having the prior compiled
version of the object when the newest version failes to compile. Aldon
also creates the PF object for all INDEX / LF items if you just select
INDEXs / LFs to be created. If you create your own you will want to
decide if you need to do the same type of actions.
Thanks, Matt
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert
Rogerson
Sent: Wednesday, August 13, 2014 11:08 AM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Short cut keys for a menu option...
Hi All,
I'm not sure how to word this so I couldn't find any help in the
archives.
I'm on RDi 9.1. Currently I have an LPEX Editor User Key Action set to
(s-c-b) for block fill. I want to create a key combination similar to
the User Key Action for a menu option combination.
I have a menu option (Aldon LM - Create Object (System i compile)) which
I use all the time. The shortcut key combination is a-l-j. But this
only works in the rse perspective or view.
So my normal procedure is this. Make a program change in the editor.
c-s to save the member (this step is not necessary but I do it as force
of habit). c-f7 (this may be multiple times) to change to the rse view.
a-l-j to compile the program.
I'm wondering how I would go about putting these three steps into just
one key combination (similar to the normal compile s-c-c or the User Key
Action). I'm not even sure if I can do it but I thought I'd ask.
Any suggestions are greatly appreciated.
Thanks,
Rob
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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.
midrange.com
