From: rfengineer55 on
On Jun 11, 2:01 am, glen herrmannsfeldt <g...(a)ugcs.caltech.edu> wrote:
> rfengineer55 <rfenginee...(a)aol.com> wrote:
>
> (snip)
>
> > No, the error is not happening with print statements. Here is the line
> > in te code where the Intel compiler zeros in on -
> >      WRITE ( UNFDAT,IREC ) FREQ, SIG(II),
> >     +D1( JJ ), UMVM(II,JJ), D2( JJ ), BMVM(II,JJ)
> > IREC is the variavle that the compiler says is not
> > assigned to a label.
>
> The IBM form of unformatted direct access I/O looks like:
>
>       WRITE ( UNFDAT'IREC ) FREQ, SIG(II),
>      +D1( JJ ), UMVM(II,JJ), D2( JJ ), BMVM(II,JJ)
>
> Someone might have missed that apostrophe and replaced
> it with a comma.
>
> The name IREC looks like a record number, not an ASSIGNed
> format label.  The more modern form is:
>
>       WRITE ( UNFDAT,REC=IREC ) FREQ, SIG(II),
>      +D1( JJ ), UMVM(II,JJ), D2( JJ ), BMVM(II,JJ)
>
> -- glen

Glen,

You nailed it! I tried your suggestion and the compiler is happy, and
so is my program :-)

Thanks for the great tip. Thanks to all others here who also made
suggestions that helped lead to the ultimate resolution.

Jeff

RF ENGINEER55

From: mecej4 on
glen herrmannsfeldt wrote:

> (snip)
>
> The IBM form of unformatted direct access I/O looks like:
>
> WRITE ( UNFDAT'IREC ) FREQ, SIG(II),
> +D1( JJ ), UMVM(II,JJ), D2( JJ ), BMVM(II,JJ)
>
> Someone might have missed that apostrophe and replaced
> it with a comma.
>
> The name IREC looks like a record number, not an ASSIGNed
> format label. The more modern form is:
>
> WRITE ( UNFDAT,REC=IREC ) FREQ, SIG(II),
> +D1( JJ ), UMVM(II,JJ), D2( JJ ), BMVM(II,JJ)
>
> -- glen

I cannot find the non-standard version <unitno>'<recno> in my copy of the
IBM VS Fortran manual of 1982. The closest mention of something like this
is under LANGLVL(66) FEATURES NOT IN VS FORTRAN,

. IBM direct-access READ and WRITE

Is it the case that DEC replicated this non-standard feature into VAX
Fortran after IBM itself had abandoned it?

-- mecej4
From: rfengineer55 on
On Jun 11, 2:01 am, glen herrmannsfeldt <g...(a)ugcs.caltech.edu> wrote:
> rfengineer55 <rfenginee...(a)aol.com> wrote:
>
> (snip)
>
> > No, the error is not happening with print statements. Here is the line
> > in te code where the Intel compiler zeros in on -
> >      WRITE ( UNFDAT,IREC ) FREQ, SIG(II),
> >     +D1( JJ ), UMVM(II,JJ), D2( JJ ), BMVM(II,JJ)
> > IREC is the variavle that the compiler says is not
> > assigned to a label.
>
> The IBM form of unformatted direct access I/O looks like:
>
>       WRITE ( UNFDAT'IREC ) FREQ, SIG(II),
>      +D1( JJ ), UMVM(II,JJ), D2( JJ ), BMVM(II,JJ)
>
> Someone might have missed that apostrophe and replaced
> it with a comma.
>
> The name IREC looks like a record number, not an ASSIGNed
> format label.  The more modern form is:
>
>       WRITE ( UNFDAT,REC=IREC ) FREQ, SIG(II),
>      +D1( JJ ), UMVM(II,JJ), D2( JJ ), BMVM(II,JJ)
>
> -- glen

Glen,

I'm also the dirty bird that replaced the apostrophe with a comma. I
could not find such a construct listed in by VAX fortran book so I
wrongfully concluded that the statement was invalid and changed it.

So just for fun, I changed the statement back to the orignal
construct, apostrophe and the whole nine yards, and it compiled and
ran fine that way too.

I changed it back to what ou suggested because it's more clear as to
what's intended.

So I shot myself in the foot o this one :-(

RF ENGINEER55
From: mecej4 on
dpb wrote:

> glen herrmannsfeldt wrote:
> ...
>
>> After a while you get used to how different people respond.
> ...
>
> Indeed, I tend to try to add the "teach to fish" viewpoint, particularly
> where a specific issue has already been addressed (in this case at least
> two times previously that hadn't seem to have had much effect).
>
> In some cases it's almost preordained to be a failure; still we must
> try... :)

Not when the candidate adheres to Sarah Palin's Principle: "only dead fish
go with the flow". :)

-- mecej4

> (I'd think "flailing" is a pretty apt description of simply doing a
> blanket substitution of "," for "'" in direct access READ/WRITE
> statements and that pausing to consider what one was actually doing
> first would be a way to gain on the objective rather than simply
> compiling and posting over and over, but that's just me...what do I know
> after 40 years? :( )
>
> --

From: rfengineer55 on
On Jun 11, 5:22 pm, glen herrmannsfeldt <g...(a)ugcs.caltech.edu> wrote:
> rfengineer55 <rfenginee...(a)aol.com> wrote:
>
> (snip)
>
> > You of course are responsible for your interpretation. The poster did
> > not say anything that was offensive, you are quite right. His
> > mentioning that i'm ranting, flailing, etc., is simply useless
> > information.  What is the useful purpose of such comments then? From
> > my perspective, it is a waste of time. So your words are not at all
> > helpful.
>
> After a while you get used to how different people respond.
>
> There is someone who posts to another group that I read that
> often uses the term 'stupident' in replies.  Some might take
> it personally, but after a while you find that he treats everyone
> about the same.  Also, most often he does know what he is
> talking about, technically.   (If you google for stupident and
> newsgroup it probably won't take too long to find.)
>
> Somewhere I have seen a recommendation that people read a newsgroup
> for six months before writing their first post.  It seems likely
> that the fraction that actually follow that is near zero, but
> it would give you time to understand the different types of
> answers you get from different people, and what you should
> and should not take personally.
>
> -- glen

Glen,

Quite true. I don't have that kind of time to monitor a news group.

My experience here is not at all about taking thinjgs personally. It's
about
reasonable limits. It's not reasonable to intermix meaningless
comments along
with helpful suggestions, or worse, post a message that, in the case
of this
board, has nothing to do with fortran troubleshooting. but is
meaningless information
such as tha's what you get for messing around with old code, as a
hypothetical example.
That might very well be what I get. I understand that. But pinting
things like that
out, minus any actual usable information is useless.

All I can do is pint out that uselessness of such information when
it's posted, and if
it continues, that's certainly the poster's right. It's also on the
record that the
information is useless and unwelcome. And I have made such comments to
postings hat were
in direct response to my posts.

I couldn not care less what these types of listmembers post elsewhere
in response
to other member's posts.

It's no big deal to me, and that's why I don't take it personally.
It's like not voting
then bitching whn the government isn't doing things right. Well, you
gotta speak up :-)

So I speak up. It might not help, but I've done all I can.

If course, we can't get to where we take NOTHING personally because
that's neither healthy nor human. You just can't
internalize things, feel singled out, or believe that others' opinions
of you (collectivel) equals your reality.

There should of course be a half dozen or so people whose personal
opinion of you, matters. But not many beyond that. Everyone is
entitled to their own opinion and I'm entitled to disagree with it and
vice versa. Many people get into trouble when they take a
difference of opinion personally. Become offended, huffy, and so on.
It's no more than what it is; a difference of opinion, where
the operative term is difference. Different is not bad, it's just
different.

Interesting stuff.

Jeff

RF ENGINEER55