CODE/400 and looonnnngggg name support

[Guest.Visitor]

Violane/Mike, I spoke to Inge Weiss during the last COMMON about a problem I am having with CODE, and thought I'd follow up. The majority of our current RPG development (yes, we STILL develop in RPG!) is done using NOMAIN modules full of procedures and data elements with _VERY_ descriptive names (ex. pSetMcovrgpcRenewalRate1 (procedure name), wBusObjData.wProcessingStatus (data structure subfield), etc. The way we define these fields in RPG is to use the '...' continuation sequence, as shown below: P pSetMcovrgpcRenewalRate1... P B EXPORT *-------Procedure Interface D pSetMcovrgpcRenewalRate1... D PI LIKE(wBusObjData.wProcessingStatus) D wRenewalRate1... D LIKE(wBusObjData. D wRenewalRate1) D CONST The problem I continue to have is that CODE Navigator does not understand this notation, and all I get is a window full of blank boxes, rather than boxes with procedure names (or subroutine names), which makes the normally very useful Navigator useless. Any ideas if/when this will be fixed? John

[batthish@ca.ibm.com]

Hi John, I have reproduce your problem, and I have created APAR SE07342 to track it. Unfortunately I can't give you an ETA as of yet (all the developers I need to talk to are on vacation). Ideally I would like it to be WDSC 4.0 SP3, but it might possibly go to the following service pack. Thanks, Violaine Batthish CODE Project Lead Toronto Lab, IBM Canada

[Guest.Visitor]

Thanks Violaine. I will be anxiously awaiting this fix, as it will make my life much easier!!! JJ "Violaine Batthish" wrote in message news:ajj0b5$iu6$3@news.boulder.ibm.com... > Hi John, > > I have reproduce your problem, and I have created APAR SE07342 to track > it. > Unfortunately I can't give you an ETA as of yet (all the developers I need > to talk to are on vacation). > Ideally I would like it to be WDSC 4.0 SP3, but it might possibly go to > the following service pack. > > Thanks, > Violaine Batthish > CODE Project Lead > Toronto Lab, IBM Canada

[Guest.Visitor]

Violaine, Also the Show Procedures view does not recognise the long names - it merely shows all P-spec lines with B(egin) or E(nd) - not very useful when the long procedure name is specified on the previous P-spec without a B or E and thus not included in the view. Is there any chance that the problem will be solved in WDT/400 V5R1 as well as in WSDC 4.0? Best regards, Christian Jorgensen Violaine Batthish wrote: > Hi John, > > I have reproduce your problem, and I have created APAR SE07342 to track > it. > Unfortunately I can't give you an ETA as of yet (all the developers I need > to talk to are on vacation). > Ideally I would like it to be WDSC 4.0 SP3, but it might possibly go to > the following service pack. > > Thanks, > Violaine Batthish > CODE Project Lead > Toronto Lab, IBM Canada

[Guest.Visitor]

Christian, Actually, this has been fixed as of SP2 of WDSC, and I use it all the time now - it is an invaluable time saver! Still waiting for Navigator to be fixed, but this one definitely helped!! JJ "Christian Jorgensen" wrote in message news:apbg3o$2e36$1@news.boulder.ibm.com... > Violaine, > > Also the Show Procedures view does not recognise the long names - it merely > shows all P-spec lines with B(egin) or E(nd) - not very useful when the > long procedure name is specified on the previous P-spec without a B or E > and thus not included in the view. > > Is there any chance that the problem will be solved in WDT/400 V5R1 as well > as in WSDC 4.0? > > Best regards, > Christian Jorgensen > > > Violaine Batthish wrote: > > > Hi John, > > > > I have reproduce your problem, and I have created APAR SE07342 to track > > it. > > Unfortunately I can't give you an ETA as of yet (all the developers I need > > to talk to are on vacation). > > Ideally I would like it to be WDSC 4.0 SP3, but it might possibly go to > > the following service pack. > > > > Thanks, > > Violaine Batthish > > CODE Project Lead > > Toronto Lab, IBM Canada >

[batthish@ca.ibm.com]

Hi Christian, Unfortunately there are no more service packs scheduled for WDT/400 V5R1. We are aware of the problems with Navigator, and there is a developer working on the problem. I don't yet have a target date for when the work will be complete. Thanks, Violaine Batthish CODE Project Lead Toronto Lab, IBM Canada