HP3000-L Archives

November 2002, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bill Cadier <[log in to unmask]>
Reply To:
Bill Cadier <[log in to unmask]>
Date:
Thu, 21 Nov 2002 08:42:00 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (66 lines)
Stephen wrote:


> I have a strange error.  No matter how I try to submit a job from any login
> in a particular account, I get an error.  We use Vesoft's STREAMX for
> virtually all job sumittals, but when that did not work, I used MPE's
> STREAM (for a brief time).  Below are the two attempts and the results:
>
> SERIES 969-120\A4552.ISD: dojob altfilej.jcl
>
> **** INTERNAL TRAP
> Instruction Memory Protection Trap
> [VSM] Undecoded status.info = -37
> ABORT: STREAMX.PUB.VESOFT
> Error capturing state - CM mode - Translated
> NM address does NOT map back to trans CM code.
> Translated code may be executing CM millicode.
> CM address is unknown.  GHOST2 seg 1.13 used.
> Special CM stack marker cap.  CM was interrupted
> Cap has been removed.  ISM used to get CM state.
>
> run streamx.pub.vesoft;parm=1;info=" ? "
> Program terminated in an error state. (CIERR 976)
> SERIES 969-120\A4552.ISD:
>
> SERIES 969-120\A4552.ISD: stream altfilej.jcl
> First character in name not alphabetic. (CIERR 1434)
> SERIES 969-120\A4552.ISD:
>

<snip>

> Lastly, why does STREAMX give me a virtual space error, but STREAM only says
> it does not like the jobstream's name?
>
> I'm scratching my head on this one, so any help will be much appreciated.
>
> Steve Douglass

You probably have an non-printable character embedded in the job statement.
 I can reproduce the CI error by creating a job like this

!job [control G]foo,manager.sys

That's why the CI STREAM command reports cierr 1434.

The VSM Instruction Memory Protection Trap may be the result of some characteristic
of the erroneous job statment leading to corruption of streamx's stack. I believe
streamx does parameter substitution in job jcl so it may be tripping up on whatever this
non-printable character is. The CI stream command wouldn't be parsing the jcl in quite
the same way and it's also not a program.

If you have an editor that will display lines of files expanded as TDP will do using the
"exp" option you can list the job and see if any non-printable characters exist. If you don't
have such an editor you can take the more direct approach and delete the "job" statement
and re-enter it. It sounds like you had been modifying  this line of the file but only to try
different user names or maybe streamx does that for you too.

Hope this helps,

Bill
HP

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2