> > At 8:50 PM -0500 6/9/02, Forrest Cahoon wrote: > >But 0 is JPI$K_OTHER, what I should really be getting is 3, which is > >JPI$K_INTERACTIVE. Changing this XS code into plain C, where test1() > >becomes main() and running it gives me the results I expect: > > > >status = %X00000001 mode = 3 > > > >This is with Perl 5.6.0 on OpenVMS Alpha V7.3. > > > >What the heck's going on here? > > That's odd. I vaguely remember having to jump through a hoop or two > to get VMS::Process going right, but that was ages ago. > > One thing that did strike me--you've got a lot of structure > definitions and such that aren't necessary with VMS 7.3. Might want > to yank them in favor of the ones in the header files and see if that > gets you anywhere.
I've gotten into the habit of including these definitions so the code could be compiled on a variety of systems. I could find the correct header, but I think that's where I got the structure from originally. I'm pretty sure it's right: it doesn't blow chunks or anything, just gives a weird result. > Also, are you maybe running the perl process oddly, such that 0 is > actually the right answer? You'd think that running "mmk test" on the command line would be interactive, right? I put the test in a batch job and submitted it, and got the expected mode of 2 (which is JPI$K_BATCH) in that case. -- | Forrest Cahoon | [EMAIL PROTECTED] |------------------------------| | 850 21st Ave SE |----------------------| Only unbalanced people | | Mpls MN 55414-2514 | | can tip the scales... |
