Re: Defining a new compile association

Darren,

You can also associate the SQL parser with your custom source member type:

Windows, Preferences, LPEX Editor, Parsers, Parser Associations.

I usually find a default provided by IBM similar to what I want in the
list of associations on the right (e.g., SQL which associates with the
'sql' parser), click on it in then modify the 'Document type' to match my
new member type. (You can simply type your member type in the 'Document
type' box and select the appropriate Document parser in the drop down
below that.)

Click 'Set' and apply or OK. Your custom source type will tokenize.

Michael

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 02/10/2015 01:00:03 PM:

----- Message from Buck Calabro <kc2hiz@xxxxxxxxx> on Tue, 10 Feb
2015 10:09:57 -0500 -----

To:

wdsci-l@xxxxxxxxxxxx

Subject:

Re: [WDSCI-L] Defining a new compile association

On 2/10/2015 9:45 AM, darren@xxxxxxxxx wrote:

We use a change management tool that defines an SQL table definition

as

a .SQLTABL type of member. When I open this in RDI, I can't define a
compile command for this type of member. I can only run user actions.

Is

there a way to define .SQLTABL as a compilable type of member, similar

to

how .PF is available now?

Compile > Work with compile commands...
Add... (top right, next to Source type box)
New member type = SQLTABL, OK
New command
Label CRTSQLTABL (or whatever you like to think of it as)
Command CRTSQLTABL... (whatever your command is)

In order to get feedback to RDi, the command you invoke needs to do a
bit of work to populate the feedback file. Look in the Wiki
http://wiki.midrange.com/index.php/Custom_Compile_Commands but I don't
know how current that is.

--
--buck

'I had nothing to offer anybody except my own confusion' - Jack Kerouac