¿ªÔÆÌåÓý

  1. H390-Vm
  2. Topics

DMSIPT143T ADDESSING EXCEPTION OCCURRED AT F2A6FC IN SYSTEM ROUTINE EXEC, RE-IPL CMS

 

Hello,

I'm getting DMSIPT143T on a very simple REXX program.

DMSIPT143T ADDESSING?EXCEPTION OCCURRED AT F2A6FC IN SYSTEM ROUTINE EXEC, RE-IPL CMS.
CP ENTERED; DISABLED WAIT PSW '00020000 40F8B75E'

The REXX program is:

/* */
? ? ?if RxFuncQuery( 'SysLoadFuncs' ) <> 0 then
? ? ? ? ?do
? ? ? ? ? ? call RxFuncAdd 'SysLoadFuncs', 'REXXUTIL', 'SysLoadFuncs'
? ? ? ? ? ? call SysLoadFuncs
? ? ? ? end
a = 0
do forever
? a = a + 1
? say a
? if a//20 = 0 then do
? ? 'cls'
? ? rc = syssleep(1)
? ? end
? end

Bertram Moshier

P.S. Should I open a ticket?? If so, where and against what (REXX or CMS)?
 

On Fri, 6 Jan 2023, at 02:48, Bertram Moshier wrote:
Hello,

I'm getting DMSIPT143T on a very simple REXX program.

DMSIPT143T ADDESSING EXCEPTION OCCURRED AT F2A6FC IN SYSTEM ROUTINE EXEC,
RE-IPL CMS.
CP ENTERED; DISABLED WAIT PSW '00020000 40F8B75E'

I've read the later replies on this thread, but couldn't help thinking that
it would have been useful if you'd told us if the program actually ran
at all, and if so, how far it got.

Wouldn't one at least possibly expect this program to fail at some
point, when a exceeds the maximum value of an integer at whatever
the "numeric digits" value is?

Also, I question the wisdom of

rc = syssleep(1)

as it conflates the normal use of "rc" (to represent the return
code from an issued command) with the returned value from
a function.


The REXX program is:

/* */
if RxFuncQuery( 'SysLoadFuncs' ) <> 0 then
do
call RxFuncAdd 'SysLoadFuncs', 'REXXUTIL', 'SysLoadFuncs'
call SysLoadFuncs
end
a = 0
do forever
a = a + 1
say a
if a//20 = 0 then do
'cls'
rc = syssleep(1)
end
end

--
Jeremy Nicoll - my opinions are my own.
 

I got far enough on tracing this program to see that it us failing during REXX initialization. No program statements have run yet. The interpreter is trying to reference uninitialized storage. I just started on this, so I am not very far along yet.
Bob Bolch

On Tue, Jan 10, 2023, 4:01 PM Jeremy Nicoll <yahgrp87@...> wrote:
On Fri, 6 Jan 2023, at 02:48, Bertram Moshier wrote:
> Hello,
>
> I'm getting DMSIPT143T on a very simple REXX program.
>
> DMSIPT143T ADDESSING EXCEPTION OCCURRED AT F2A6FC IN SYSTEM ROUTINE EXEC,
> RE-IPL CMS.
> CP ENTERED; DISABLED WAIT PSW '00020000 40F8B75E'


I've read the later replies on this thread, but couldn't help thinking that
it would have been useful if you'd told us if the program actually ran
at all, and if so, how far it got.

Wouldn't one at least possibly expect this program to fail at some
point, when a exceeds the maximum value of an integer at whatever
the "numeric digits" value is?

Also, I question the wisdom of

? rc = syssleep(1)

as it conflates the normal use of "rc" (to represent the return
code from an issued command) with the returned value from
a function.


> The REXX program is:
>
> /* */
>? ? ? if RxFuncQuery( 'SysLoadFuncs' ) <> 0 then
>? ? ? ? ? do
>? ? ? ? ? ? ?call RxFuncAdd 'SysLoadFuncs', 'REXXUTIL', 'SysLoadFuncs'
>? ? ? ? ? ? ?call SysLoadFuncs
>? ? ? ? ?end
> a = 0
> do forever
>? ?a = a + 1
>? ?say a
>? ?if a//20 = 0 then do
>? ? ?'cls'
>? ? ?rc = syssleep(1)
>? ? ?end
>? ?end


--
Jeremy Nicoll - my opinions are my own.
 

Hello,


>>? I've read the later replies on this thread, but
>>? couldn't help thinking that
>>? it would have been useful if you'd told us if >> the program actually ran
>> at all, and if so, how far it got.

First let me apologize to everyone for writing two confusing messages.

The DMSIPT143T occurred when I first ran the program.

The other error occurred ONLY AFTER I ADDED:

trace 'e'

To the program.? I added the trace 'e' to help determine how far the program got and specifically where it failed.


IMHO, calling a non-existing program should not cause CMS to terminate and require a reipl of CMS.

Additional having trace 'e' should not cause REXX to die as it did.

In both cases a better way of dealing with the error is needed.

I hope I helped clarify the two messages.? Again I apologize for the. Misunderstanding of the two messages.? The first was for the DMSIPT error. The second for adding trace 'e'.

Thank you.





On Tue, Jan 10, 2023, 15:01 Jeremy Nicoll <yahgrp87@...> wrote:
On Fri, 6 Jan 2023, at 02:48, Bertram Moshier wrote:
> Hello,
>
> I'm getting DMSIPT143T on a very simple REXX program.
>
> DMSIPT143T ADDESSING EXCEPTION OCCURRED AT F2A6FC IN SYSTEM ROUTINE EXEC,
> RE-IPL CMS.
> CP ENTERED; DISABLED WAIT PSW '00020000 40F8B75E'


I've read the later replies on this thread, but couldn't help thinking that
it would have been useful if you'd told us if the program actually ran
at all, and if so, how far it got.

Wouldn't one at least possibly expect this program to fail at some
point, when a exceeds the maximum value of an integer at whatever
the "numeric digits" value is?

Also, I question the wisdom of

? rc = syssleep(1)

as it conflates the normal use of "rc" (to represent the return
code from an issued command) with the returned value from
a function.


> The REXX program is:
>
> /* */
>? ? ? if RxFuncQuery( 'SysLoadFuncs' ) <> 0 then
>? ? ? ? ? do
>? ? ? ? ? ? ?call RxFuncAdd 'SysLoadFuncs', 'REXXUTIL', 'SysLoadFuncs'
>? ? ? ? ? ? ?call SysLoadFuncs
>? ? ? ? ?end
> a = 0
> do forever
>? ?a = a + 1
>? ?say a
>? ?if a//20 = 0 then do
>? ? ?'cls'
>? ? ?rc = syssleep(1)
>? ? ?end
>? ?end


--
Jeremy Nicoll - my opinions are my own.

1 - 4 of 4