IBMi Export List BEF/AFT commands limitation?

[LANSAfolks]

I'm building an IBMi export list with around 1500 objects (mix of Files, Functions, Forms, RP's) and needed to add around 100 Before and After commands into my Export list. It was all just fine until I entered the 30th command. After that, it won't let me add any more commands! It that a limitation? Surely we should be able to add 100+ commands into an export list??? I tested in LANSA V13 and V14, both seem to have that limitation. Has anyone else faced this limitation? How did you work around that? I don't want to start building 4 export lists, just to cater for these 100 commands.

[Dino]

Hi,

I see the limitation, but if you have that many actions, I will put them in a CLP like this (lets call it TEST):

Code: Select all

PGM        PARM(&PGMLIB)                   
DCL        VAR(&PGMLIB) TYPE(*CHAR) LEN(10)
DSPLIB     LIB(&PGMLIB) OUTPUT(*PRINT)     
/* Copy, authorize, whatever needed etc etc */
ENDPGM                                     

then in your export list if you have this sustitution variables:

Code: Select all

                                                                               
List       : TEST119 test                                                      
                                                                               
 Variable     Substitution value / Default value             Prompt user       
   Name       Prompt text to display if prompting required   When importing    
 $$DTALIB$$   *PARTDTALIB                                         Y            
       Please specify library into which data base files are to be imported ?  
 $$PGMLIB$$   *PARTPGMLIB                                         Y            
       Name of the program library?

You can call the CL from there:

Code: Select all

DC@P620012            Commands to Execute on Import       
List       : TEST119 test                                 
                                                          
Execute Sequence Ignore                                   
Bef/Aft Number   Error   IBM i  command                   
  A         1.00   Y     CALL QGPL/TEST $$PGMLIB$$ 

[LANSAfolks]

By introducing a CL program, I lose easy visibility of these commands i.e. I now have to maintain a separate CL program for all my commands. Anyway, I hope LANSA can remove this limitation, seems to be an odd one for this day and age, perhaps it made sense in the 1990's? I was able to work around this limitation my inserting all my commands into DC@F53 and they tested fine too i.e. all commands were executed successfully.

[Dino]

Suggestion, send the email to support asking for an enhancement, maybe its a quick thing.