Subject: | |
From: | |
Reply To: | |
Date: | Tue, 17 Jun 1997 11:36:09 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
The callci problem that was originally suspected as a Perl problem turns out
to be an old known bug. The workaround is to put your non-redirectable MPE
commands into a command file, then execute the command file with callci.
Here is the HPRC call text:
> I just duplicated this on our system here, and it looks
> like there was an SR submitted on this a LONG time ago, when 5.0
> originally came out.
So fix it already! ;-)
> The SR#4701231209 was closed as a duplicate of
> 4701285247 (which doesn't appear to be a duplicate to me). Basically,
> the problem is that the shell attempts to redirect I/O on a CI command
> that can't handle it.
>
> There IS a workaound that I have tested, and it worked fine for me.
> Create a command file (ie, fooinfo) with contents:
>
> setvar foo 123
> showvar foo
>
> Change your job stream to do a callci on that command file:
>
> callci fooinfo
>
> I have submitted another SR on this that refers to the original (CLOSED)
> SR. This SR is 5003375394
Still unknown to me is why callci feels a need to do the CI redirection in
batch but not in a session. I'm attempting to post a followup comment asking
explicity about this, but us-support.external.hp.com is being exceptionally
slow/down/uncooperative today....
--
Mark Bixby E-mail: [log in to unmask]
Coast Community College Dist. Web: http://www.cccd.edu/~markb/
District Information Services 1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)
|
|
|