I'm looking for some WebFOCUS coding standards/guidelines and heard that there was a 2007 Summit presentation on this topic. Are Summit presentations available online or does someone have a copy of this presentation?

Thanks,
Ted

This message has been edited. Last edited by: Kerry,

I have a copy of the presentation. It was written by:

Francis Mariani
Susannah Jones
Anthony Alsford

If you would like I can send it to you.

I would love a copy of that also actually. Especially since it was written by the those three gurus!

All I need is an email address and it's yours.

Actually, it was written only by Susannah Jones and Anthony Alsford, Francis was otherwise occupied.

T

Yes, I wasn't involved in this interesting topic.

Sorry guys. I was just relaying what the power point indicated.

I would like to receive the power point of the WebFOCUS coding standards/guidelines.
Can any one mail to this mail aeswararao@gmail.com

Thank you in advance

Could you please forward a copy to me also. We are in the process of implementing Webfocus. My email is: sfernan2@ford.com

thanks!

Could I please get a copy as well? I'm new to WebFOCUS and something like this would really help me out. My e-mail is: rpuno@bchousing.org

Time for a Susannah/Tony roadshow!

i was involved with a Focus coding standards committee at Ford Motor back in the mainframe days, and would be very interested in seeing a copy of that document too !

Thanks,

Good News!

I sent Kerry a copy and she is going to post it to the presentation section on the developer center and it will be available for all to download and review.

Thanks Glenda for sending me the file.

To all, this PowerPoint file is now in the Presentations section on the Developer Center. Here is the link to download it. We also have many other presentations that may be of interest to you:
http://www.informationbuilders...s/presentations.html

Cheers,

Kerry

This message has been edited. Last edited by: Kerry,

Thanks to Glenda, Kerry, Susannah and Tony for making this presentation available to us !

Interesting that, even through Focus has changed a lot, the same code formatting guidelines are still there from the early mainframe days

quote:

Interesting that, even through Focus has changed a lot, the same code formatting guidelines are still there from the early mainframe days

Dave,

As you may have guessed, that is where I first used FOCUS, on a 4381 running VM followed by a 3081 running MVS - as many MIPS as a modern calculator

T

I live by those code formatting guidelines, plus some of my own additions. In fact, I can't really read code well, unless it is properly formatted. I reformat a lot of OP code !

Maybe that is a failing, not being flexible, but I have internalized that text structure so deeply, it is how I understand code.

But I find it amazing that so few programmers use the formatting ! I don't know how they can manage to troubleshoot their own work ?

I don't recall what particular IBM CPU was running the MVS/TSO I learned on back in '85. And it's MIPS were probably about the same, but they were efficient machines and OS's, and could run LOTS of terminals and batch jobs. So I don't look down my nose at them , even now

Well, Thomas Jefferson had a point but it is very "New World". I think that Talleyrand, the "Prince of Diplomats" had it better when he proferred:
Appuyez-vous solidement sur vos principes, ils finiront bien par ceder.

For those who have difficulty with the brogue of Voltaire, here is a rough translation:
Lean solidly on your priciples, in the end they will collapse.

But that doesn't allow anyone to write sloppy code!

quote:

I don't know how they can manage to troubleshoot their own work

I am not sure that even appears on their radar Dave, but then we of the "old ways" did a lot of things differently and have kept the traits into our middle years

T

Francesco indeed contributed, albeit remotely. and i just taught a class this morning using one of his lessons. Check your focus errors after every paragraph (ie DEFINE->END,JOIN->END,TABLE->END)
..some fex paragraph
-RUN
-IF &FOCERRNUM EQ 0 GOTO continue.1;
-TYPE i blew it focerror is &FOCERRNUM
? &FOCERRNUM
-GOTO eoj ;
-continue.1

I don't know why those aren't the most popular lines of FOCUS code...

Those lines should be mandatory code for any FOCUS programmer.

The last thing any one wants is to have a report run and get nasty code and error messages come back, it should always be handled.

In our reports we have a standard block for error handling.

At each logical point in the code we test for errors and if found pass the flow to one of the labels below.

Other Code...

-GOTO RPT_OK

-*******************************************************************************
-RPT_ER1

-SET &RPT_MSG ='(XX00002) Report terminated - insufficient parameters entered';
-GOTO RPT_END
-*******************************************************************************
-RPT_ER2

-SET &RPT_MSG = '(XXX00002) Error - No Report Generated' ;
-GOTO RPT_END
-*******************************************************************************
-RPT_ER3

-SET &RPT_MSG = '(XXXO00003) Error - ' | &ERR_MSG ;
-GOTO RPT_END
-*******************************************************************************
-RPT_FERR

-SET &RPT_MSG = '(XXX00003) Error - Focus Error Number ' 
-             | &FOCERRNUM | ' Encountered' ;
-GOTO RPT_END
-*******************************************************************************
-RPT_0RECS

-SET &NoReport = 'YES' ;
-SET &RPT_Type = 'XXX_PDF' ;
-SET &OUT_FMT001 = 'PDF' ;
-SET &RPT_Format   = &OUT_FMT001

-INCLUDE PARM_PAGE

-INCLUDE OUTPUT_HANDLER

-RUN

-IF &FOCERRNUM GT 0 THEN GOTO RPT_FERR ;

-*******************************************************************************
-RPT_OK

-INCLUDE TIME_STAMP

-SET &RPT_MSG = '(XXX00001) Report completed successfully' ;

-RPT_END

-INCLUDE ERROR_HANDLER

for us,
the dba's make teeny changes to files that affect the masters oh so slightly , with the 'oh it should have no effect on you'
and of course it knocks us slam out of the water!

Please send it also to Mark.Swanson@fmr.com

Kerry: Thanks for the link. Ira

Hi Glenda,

Curious if you still have a copy of the presentation mentioned below and would be willing to send to me. I just tried the User Forum Presentation link provided by Kerry Zhan back on April 2009 and couldn't find the presentation.

Thanks,

Amy
boydad@ncat.edu

quote:

Originally posted by Glenda:
I have a copy of the presentation. It was written by:

Francis Mariani
Susannah Jones
Anthony Alsford

If you would like I can send it to you.

Glenda,

I would also like a copy of the presentation mentioned above. I also looked for the presentation on the User Forum Presentation link and did not see it.

email: Mike.Rodriguez@ejgallo.com

Thanks,
prodrigu

quote:

Originally posted by Waz:
Those lines should be mandatory code for any FOCUS programmer.

The last thing any one wants is to have a report run and get nasty code and error messages come back, it should always be handled.

In our reports we have a standard block for error handling.

At each logical point in the code we test for errors and if found pass the flow to one of the labels below.

Other Code...

-GOTO RPT_OK

-*******************************************************************************
-RPT_ER1

-SET &RPT_MSG ='(XX00002) Report terminated - insufficient parameters entered';
-GOTO RPT_END
-*******************************************************************************
-RPT_ER2

-SET &RPT_MSG = '(XXX00002) Error - No Report Generated' ;
-GOTO RPT_END
-*******************************************************************************
-RPT_ER3

-SET &RPT_MSG = '(XXXO00003) Error - ' | &ERR_MSG ;
-GOTO RPT_END
-*******************************************************************************
-RPT_FERR

-SET &RPT_MSG = '(XXX00003) Error - Focus Error Number ' 
-             | &FOCERRNUM | ' Encountered' ;
-GOTO RPT_END
-*******************************************************************************
-RPT_0RECS

-SET &NoReport = 'YES' ;
-SET &RPT_Type = 'XXX_PDF' ;
-SET &OUT_FMT001 = 'PDF' ;
-SET &RPT_Format   = &OUT_FMT001

-INCLUDE PARM_PAGE

-INCLUDE OUTPUT_HANDLER

-RUN

-IF &FOCERRNUM GT 0 THEN GOTO RPT_FERR ;

-*******************************************************************************
-RPT_OK

-INCLUDE TIME_STAMP

-SET &RPT_MSG = '(XXX00001) Report completed successfully' ;

-RPT_END

-INCLUDE ERROR_HANDLER

Waz,

Can you send me an example of the standard block for error handling. I like what I see but is it possible if you can send or post an example with the car file.

This is a link to a working example of how we use this sort of coding.

standard_code

Ours is a little more complicated and structured, but you should get the basic idea.

You can run this with no parameter or wrong parameters, or put a coding error in the code and see what happens.

quote:

Originally posted by boydad85:
I just tried the User Forum Presentation link provided by Kerry Zhan back on April 2009 and couldn't find the presentation.

I am also seeking a copy of this and was disappointed to see it no longer available on the presentations site.