[Info-vax] Command Procedure pass value to program READ

[HCorte]

A quinta-feira, 10 de fevereiro de 2022 à(s) 17:10:11 UTC, abrsvc escreveu:
> On Thursday, February 10, 2022 at 12:02:23 PM UTC-5, HCorte wrote: 
> > A terça-feira, 8 de fevereiro de 2022 à(s) 20:40:48 UTC, Dennis Boone escreveu: 
> > > > Well the project that am working multiple executables the source code is 
> > > > using in the WRITE statements unit=5 instead of correct unit=6 that 
> > > > originates the following error when running the script to inject the 
> > > > params needed for the input's... 
> > > Is this program being ported from some non-VMS origin platform? 
> > > 
> > > De 
> > No, its all been in OpenVMS. Nerver the less its a project with quite some time and in Fortran77.
> As I stated, this was a very common "feature" in many FORTRAN programs that provided prompts to users. Both channel 5 and 6 were the screen for interactive applications and often the programmers would differentiate prompts from "output" this way. I didn't agree, but it was a convention in some places. With direct execution, there was no problem. As you found, command procedure wrappers create problems. I believe that you can get around this by assigning both FOR005 and FOR006 to TT: (I haven't tried this, but it may work.) 
> 
> Dan

Yes @Dan it seems to be the case where direct execution there isn't any probleam only now that am trying to wrapping in command procedure that arised this situation, thanks for the feedback about this being a convention. 

Gona Try to see if there exists a symbol to differentiate when this subroutine is called from a script or the normal direct execution. 

what do you mean by assigning both FOR005 and FOR006 to TT?