Oops. Should have been:
Thanks for this for this (and everyone else's) input.
Kevin
--- Kevin Toppenberg <[EMAIL PROTECTED]> wrote:
> This for this (and everyone else's) input.
>
> Kevin
>
> --- steven mcphelan <[EMAIL PROTECTED]>
> wrote:
>
> > One sees anomalies with using %ZIS because th
No, It was for a productivity report, that can be read
from the screen. I may come back to this again later.
Thanks for checking back.
Kevin
--- Marianne Susaanti Follingstad
<[EMAIL PROTECTED]> wrote:
> Kevin, did you ever find a solution for the problem
> you were having that
> started this t
Kevin, did you ever find a solution for the problem you were having
that started this thread? I ask since what you recounted didn't have
anything obviously wrong.
Marianne Follingstad
Kevin Toppenberg wrote:
This for this (and everyone else's) input.
Kevin
--- steven mcphelan <[EMAIL PROTECTED]>
This for this (and everyone else's) input.
Kevin
--- steven mcphelan <[EMAIL PROTECTED]> wrote:
> One sees anomalies with using %ZIS because the %ZIS
> utility may or may not
> invoke the USE command. So it may open the device
> but never use it. Thus
> the system still has the current device
Yes, you are right. That did not occur to me at the time and, frankly,
it strikes me as an "interesting" design choice, but it may actually be
better to do it this way than to complicate the rules rergarding IO
handling. In the other interpreted language I commonly use (Python)
this isn't even an i
One sees anomalies with using %ZIS because the %ZIS utility may or may not
invoke the USE command. So it may open the device but never use it. Thus
the system still has the current device as that device in use prior to
calling %ZIS. So the best procedure to follow would be some code such as
rath
Greg,
I wonder if you are getting the effect you are seeing
because you are at a command prompt. I guess that the
interpreter changes $I to ensure that the prompt etc
is shown on your screen, rather than to the device you
just specified.
Kevin
--- Greg Woodhouse <[EMAIL PROTECTED]> wrote:
> An
et
Sent: Wed, 23 Feb 2005 15:15:11 -0800 (PST)
Subject: Re: [Hardhats-members] How to properly use ^%ZIS ??
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discove
That makes sense.
Gee, being the SACC chair, you'd think I'd know that sort of thing.
:-(
--- Marianne Susaanti Follingstad <[EMAIL PROTECTED]> wrote:
> Greg, you're talking about using it from programmer mode, not within
> a routine. That is a
> totally different issue. From programmer mode
Greg, you're talking about using it from programmer mode, not within
a routine. That is a totally different issue. From programmer
mode the system would have to revert back to the original $I or it would
never return a > prompt and you'd lose control, so there, yes you have
to have the use on t
Another test:
>D ^%ZIS
DEVICE: HOME// NULL NULL DEVICE NULL
>W $P
_TNA1044:
>W $IO
_TNA1044:
>ZW IO
IO=_NLA0:
IO(0)=_TNA1044:
IO(1,"_NLA0:")=
IO(1,"_TNA1044:")=
IO("CLOSE")=USER$:[WOODHOUSE]TEST.DAT;
IO("ERROR")=
IO("HOME")=530^_TNA1044:
IO("IP")=10.6.17.62
IO("ZIO")=10.6.17.62:1998
>U IO
>W
I just looked it up, and you are correct (not that I didn't believe
you, of course). According to the standard, sec. 8.2.23:
"The specified device remains current until such a time as a new USE
command is executed. As a side effect of using expr to designate a
current device, $IO is given the valu
At a minimum, it's the behavior I observe under DSM:
>D ^%ZIS
DEVICE: HOME// HFS HOST FILE SERVER FOR BRTM V 2.0
HOST FILE NAME:
USER$:[ANONYMOUS]//USER$:[WOODHOUSE]TEST.DATINPUT/OUTPUT OPERATI
ON: N
>W "HELLO"
HELLO
>U IO
>W "HELLO"
HELLO
>U IO W "HELLO"
>D ^%ZISC
>
--- Marianne Susaanti F
I've used U IO(0) in several cases. One was when I was printing
labels that needed to be alligned so I'd get the device for the printing
and U IO(0) for promptings to the user regarding test labels and whether
they were alligned yet. There could be many cases for prompting or
informing a user w
,
Richard.
==
From: Kevin Toppenberg <[EMAIL PROTECTED]> Reply-To:
hardhats-members@lists.sourceforge.net Date: Wed, 23 Feb 2005 08:11:26 -0800
(PST) To: hardhats-members@lists.sourceforge.net Subject: Re:
[Hardhats-members] How to properly use ^%ZIS ??
Greg,
Thanks for your help.
I don'
That's just the way the language works. I don't particularly like that
"feature", either. And no, you don't need to USE IO(0). Off the top of
my head, I can't think of any reason an application programmer would
need to reference IO(0).
Incidentally, when %ZIS was designed, the primary use for devi
What is in your function? Any calls that could reset the Use?
(By the way, a Use statement takes effect regardless of line, contrary
to what others have said, until another Use intervenes.) It isn't
apparent what is going wrong from what you've said. Try saving your
IO* variables and taking a
Greg,
Thanks for your help.
I don't understand why the use only works for the current line oh well.
Do I need to put a U IO before every write in the REPORT function?
If the system reverts to the home device on the next line, do I need to U IO(0)?
Thanks
Kevin
Greg Woodhouse <[EMAIL PROTE
Very close. First of all, when you are done, you should close the
device with
D ^%ZISC
The other point is that USE only affects the current line.
U IO
D REPORT
won't work. What you need is
U IO D REPORT
--- Kevin Toppenberg <[EMAIL PROTECTED]> wrote:
> Hey all,
>
> I am writing a custom p
Hey all,
I am writing a custom program to create a report. And
yes I know that templates would do this better, but I
don't have time to figure that system out right now.
So I have my function that prints out everthing to the
screen just the way I want it (using standard
'writes',and no USE's an
20 matches
Mail list logo
