Re: Clarification - confused consultant

On 21/06/2008, at 7:34 AM, Joe Pluta wrote:

That's simply not true! SEU will behave exactly as it has in the past
when a new feature/keyword has been added to a language (possibly via
PTF) but SEU was not updated at the same time. That is; you can still
use SEU, you can use the new BIF or Op-code, SEU may flag a syntax
error but you can save the source in spite of the errors and compile.

That's what we mean by "could not use it in SEU". What do you think we
meant, Simon? The terminal would explode, killing the programmer? No,
we mean that SEU will not recognize the new syntax, and unlike your
example, it won't be fixed.

Oh right ... the Humpty Dumpty school of reasoning. "Could not use" means "could not use" but in reality you CAN use it regardless of whether SEU likes it or not. I should have expected the ubiquitous twisting argument. Makes me wish your terminal would explode! If you meant "would not recognise the syntax" then you should have said so-- that's a far cry from "could not use".

As long as the COMPILER finds nothing wrong with the source a program
will be created.

Got nothing to do with the compiler. I could enter it with UPDDTA and
get it to compile. Again, the syntax won't be recognized in SEU and
never will. It will, however, be recognized in RDi.

Has EVERYTHING to do with the compiler. It doesn't matter how you enter the source, not even whether your editor of choice understands the syntax. **ALL** that matters is whether the COMPILER accepts the syntax.

I'm still a little concerned as anybody that what happens when your
network goes down and you need to do some work on your box. At this
point, you can at least still use SEU. Several releases down the road
that might not be the case, at least not with full syntax checking.
Eventually SEU will become more like EDTF in that it won't catch
syntax
errors (or probably more likely it will see errors that don't exist).

So the network is down killing your client IDE to host connectivity.
Why would this not also kill your emulator to host connectivity? Or
are you thinking of some other form of connexion that doesn't involve
the network (such as private HMC link)?

Your primary console, in my case direct twinax.

Oh right ... so if your network is dead thus probably all users no longer have access to the host anyway what work would require access to SEU?

Console access implies emergency access and since SEU won't help bring the network back up I really can't see a problem that requires access to SEU to correct would have any bearing on whether the network is up or down--except maybe remote access and if you are relying on remote access then twinax won't help anyway.

Seems to me this is about two unrelated issues:

1) Need access to SEU from console (of some sort) and want full syntax support
and
2) Need network access to system for full IDE support

Anyway, I can see the start of the typical "Joe Pluta sliding argument" so I'm not going to continue this any further.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------