MVSFORUMS.com

[misi01]

I've seen two basic coding examples of the above. One is to do a perform of the OPEN cursor section, followed by a perform on the FETCH cursor section.

I've also seen an example where the user does a perform on the FETCH section, which in turn contains a test for a "has the cursor been opened yet, if not, then FIRST open the cursor", THEN do the FETCH.

What does it look like in your installations?

(Personally, I think the second example is an abomination, but that's my taste)
_________________
Michael

[kolusu]

misi01,

The standard should ALWAYS be

[haatvedt]

[misi01]

Chuck. Your code example is interesting inasmuch as I've NEVER seen anyone here in Sweden code "perform ....... thru ......"

People here ONLY code a simple "perform ......".

Not sure if that's because people here write the code as something like

WA-OPEN-CSR100 SECTION.
_________________
Michael

[haatvedt]

Michael,

This is not to start a flame war about coding styles. I've always found that organizations produce better code if they have some coding standards and attempt to adhere to them.

I started coding professionally in 1978, the first IBM shop that I worked at had a standard that all PERFORM verbs must include the THRU option. Also GO TO statements were allowed but only to the EXIT of the current paragraph. SECTION's were to be avoided except for internal SORT INPUT / OUTPUT PROCEDURES (at the time, that was required but not so any longer).

I have encountered programs which mixed coding styles, some PERFORM's / some PERFORM THRU's / and some GO TO statements. That lead to some very challenging maintenance issues.

So what ever style / coding convention is used by your employer, I would recommend that it should be adhered to.
_________________
Chuck Haatvedt

email --> clastnameatcharterdotnet

(replace lastname, at, dot with appropriate
characters)