At 11:20 PM -0500 6/9/02, Forrest Cahoon wrote:
>I didn't realize that VMS::Process already did this, but I'd still
>rather put my simple check inside of VMS::Logical than require another
>module that's only peripherally related.
Makes sense.
>status = %X00000001 mode = 0
>iosb.lo = %X00000001 modelen = 4
>
>I'm not sure what the iosb is supposed to look like, so I output it as
>hex. The result looks the same as a straight call from C (except for
>the mode, of course).
Looks good. The first longword of the iosb is a status value (but
don't confuse this type of iosb with the ones for $QIO, which have an
entirely different structure). Looks like you are getting what you
thought you were getting, so wackiness in the item list, iosb, etc.,
can probably be ruled out.
Dan is probably right about "other" being the right answer. You
could verify this by running "MMK test" and capturing the exact Perl
command used to execute the test and then running it outside the
context of MMK. This does surprise me a bit since a spawned process
is still interactive if it attaches to your terminal:
$ write sys$output f$getjpi("","MODE")
INTERACTIVE
$ spawn write sys$output f$getjpi("","MODE")
%DCL-S-SPAWNED, process BERRYC_1 spawned
%DCL-S-ATTACHED, terminal now attached to process BERRYC_1
INTERACTIVE
%DCL-S-RETURNED, control returned to process BERRYC
but a quick look at the MMK source suggests it's just defining a
mailbox and doing I/O through that rather than grabbing the PPFs of
the parent.
> > >This is with Perl 5.6.0 on OpenVMS Alpha V7.3.
>>
>> Any reason not to use 5.6.1?
>
>I'm doing my non-work-related development on a publically-accessible
>machine so I can share with you all.
Understood and appreciated; I just have a reflex to steer people
toward more stable releases.
--
________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
